WO2010088794A1 - Procédé et système de traitement de contexte dans un réseau évolutif - Google Patents

Procédé et système de traitement de contexte dans un réseau évolutif Download PDF

Info

Publication number
WO2010088794A1
WO2010088794A1 PCT/CN2009/070346 CN2009070346W WO2010088794A1 WO 2010088794 A1 WO2010088794 A1 WO 2010088794A1 CN 2009070346 W CN2009070346 W CN 2009070346W WO 2010088794 A1 WO2010088794 A1 WO 2010088794A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
network node
release
context
message
Prior art date
Application number
PCT/CN2009/070346
Other languages
English (en)
Chinese (zh)
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 PCT/CN2009/070346 priority Critical patent/WO2010088794A1/fr
Publication of WO2010088794A1 publication Critical patent/WO2010088794A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/32—Release of transport tunnels

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and system for processing context in an evolved network. Background technique
  • LTE Long Term Evolved
  • SAE System Architecture Evolved
  • the purpose of LTE or SAE networks is to provide a network that reduces latency, increases user data rates, improves system capacity and coverage, and low cost.
  • the LTE/SAE network architecture consists of three parts: User Equipment (hereinafter referred to as UE), Radio Access Network (hereinafter referred to as RAN), and Core Network (hereinafter referred to as CN). As shown in FIG.
  • EPC Evolved Universal Terrestrial Radio Access Network
  • EPC Evolved Packet
  • eNB Evolved NodeB
  • MME Mobility Management Entity
  • PDN-GW Packet Data Network Gateway
  • HSS Home Subscriber Server
  • connection The method includes: a connection between the UE and the RAN, a connection between the RAN and the CN, a connection inside the CN, and a connection between the CN and an external network.
  • the connection between the UE and the RAN is called a Radio Resource Control (hereinafter referred to as RRC) connection, and the connection is an air interface connection; the connection between the RAN and the CN is called an S1 connection.
  • RRC Radio Resource Control
  • Step 21 A UE sends an RRC connection setup request message to an eNB.
  • Step 22 The eNB receives the RRC connection setup. After the request message, if the request message is accepted, the RRC connection establishment command is sent to the UE.
  • Step 23 After receiving the RRC connection establishment command, the UE sends an RRC connection setup complete message to the eNB, thereby establishing an RRC connection, where the RRC connection is established.
  • the setup complete message carries a NAS message, for example: an attach request (ATTACH REQUEST) message, starting to store the context of the UE in the UE and the eNB, for example: RAN and/or RRC context, hereinafter referred to as: RRC context; step installation 24, eNB is The UE selects the MME, and sends the NAS message sent by the UE to the MME through the initial UE message, and starts to establish the S1 connection.
  • NAS message for example: an attach request (ATTACH REQUEST) message
  • Step 25 If the MN receives the registration of the UE, for example: accepting the attach request message, the MME saves the The S1 context related to the UE, and sending an initial context setup request message to the eNB, requesting the eNB to establish an S1 context for the UE and an evolved universal terrestrial radio access network wireless access bearer
  • the E-RAB includes a default bearer, that is, a UE, for example, an EUT ved Univer sas Terres tr ia l Radio Acces s Ne twork Radi o Acces s Bearer (hereinafter referred to as E-RAB).
  • the first bearer established when connected to the specific packet data network Step 26: The eNB informs the UE to establish the E-RAB through the RRC connection reconfiguration message; Step 27: If the UE can establish the E-RAB, the RRC connection reconfiguration is completed.
  • the MME sends an initial context setup response to the MME, and the initial context establishment result (including the E-RAB successful establishment) is fed back to the MME, and then the MME can continue to perform the related process on the EPC side.
  • the eNB cannot establish an S1 context or set a bearer for the UE, the process will fail.
  • the MN also has information about the user equipment, including the S1 context and/or resources allocated for the user equipment
  • the eNB also has information about the user equipment, including the RRC context and the ⁇ or S1 context and Or resources allocated for user devices.
  • these contexts and ⁇ or resources must be removed or released.
  • the network may also release the RRC connection and/or the S1 connection of the UE. At this time, it is also necessary to delete or release the context saved by the E and the eNB. Or resources. Summary of the invention
  • the embodiments of the present invention provide a method and system for processing contexts in an evolved network, which are used to delete or release contexts and/or resources saved on the RAN node and the CN node, and effectively improve system flexibility and system efficiency.
  • An embodiment of the present invention provides a method for processing a context in an evolved network, including: sending, to a core network node, a user equipment context release indication message for instructing the core network node to release information related to a user equipment;
  • the embodiment of the present invention further provides a method for processing a context in an evolved network, including: receiving, by a radio access network node, a user equipment context release indication message for instructing a core network node to release information related to a user equipment;
  • the embodiment of the present invention further provides a method for processing a context in an evolved network, including: sending an initial context setup failure message to a core network node, and determining to request the core network node to release information related to the user equipment;
  • a user equipment context release command message for instructing the radio access network node to release information related to the user equipment, according to the user equipment context release request message, releasing information related to the user equipment.
  • the embodiment of the present invention further provides a method for processing a context in an evolved network, including: determining, according to an initial context setup failure message sent by a radio access network node, the wireless The access network node cannot establish an S1 context and/or set a bearer for the user equipment;
  • the embodiment of the invention further provides a method for processing a context in an evolved network, comprising: sending an initial context setup failure message to a core network node;
  • the embodiment of the present invention further provides a method for processing a context in an evolved network, including: receiving an initial context setup failure message sent by a radio access network node;
  • the embodiment of the invention further provides a wireless access network node device, including:
  • a first sending module configured to send, to the core network node, a user equipment context release indication message for instructing the core network node to release information related to the user equipment;
  • the first release module is configured to release information related to the user equipment.
  • the embodiment of the invention further provides a core network node device, including:
  • a first receiving module configured to receive a user equipment context release indication message sent by the radio access network node to instruct the core network node to release information related to the user equipment;
  • a second release module configured to release information related to the user equipment according to the user equipment context release indication message.
  • the embodiment of the invention further provides a wireless access network node device, including:
  • a second sending module configured to send an initial context setup failure message to the core network node, where the second determining module is configured to determine that the release request to the core network node is related to the user equipment Information, and instructing the second sending module to send, to the core network node, a user equipment context release request message for requesting the core network node to release information related to the user equipment; and a second receiving module, configured to receive a user equipment context release command message sent by the core network node according to the user equipment context release request message for instructing the radio access network node device to release information related to the user equipment;
  • a third release module configured to: after the second receiving module receives the user equipment context release command message, release information related to the user equipment.
  • the embodiment of the invention further provides a core network node device, including:
  • a third receiving module configured to receive an initial context setup failure message sent by the radio access network node, and receive a user equipment context release request message sent by the radio access network node for requesting release of information related to the user equipment, and Receiving a user equipment context release complete message sent by the radio access network node for a user equipment context release command message;
  • a third determining module configured to determine, according to the initial context setup failure message received by the third receiving module, that the radio access network node cannot establish an S1 context and/or a configuration bearer for the user equipment;
  • a third sending module configured to return, according to the determining result of the third determining module, a user equipment context release command for instructing the radio access network node to release information related to the user equipment to the radio access network node Message
  • a fourth release module configured to release information related to the user equipment according to the user equipment context release complete message received by the third receiving module.
  • the embodiment of the invention further provides a wireless access network node device, including:
  • a fourth sending module configured to send an initial context setup failure message to the core network node, where the first selection module is configured to select a new core network node for the user equipment.
  • the embodiment of the invention further provides a core network node device, including:
  • a fifth receiving module configured to receive an initial context setup failure message sent by the radio access network node;
  • a second selection module configured to select a new core network node for the user equipment according to the initial context establishment failure message received by the fifth receiving module;
  • a fifth release module configured to: according to the initial context establishment failure message received by the fifth receiving module, release information related to the user equipment.
  • the embodiment of the present invention further provides a system for processing a context in an evolved network, including a radio access network node device and a core network node device, where the radio access network node device is configured to send to the core network node device a user equipment context release indication message indicating that the core network node device releases information related to the user equipment, releasing information related to the user equipment; and the core network node device is configured to receive the information sent by the wireless access network node device And a user equipment context release indication message indicating that the core network node device releases information related to the user equipment, and releasing information related to the user equipment according to the user equipment context release indication message.
  • the embodiment of the present invention further provides a system for processing a context in an evolved network, including a radio access network node device and a core network node device, where the radio access network node device is configured to send an initial context to the core network node device.
  • the core network node device is configured to determine, according to the initial context setup failure message sent by the radio access network node device, that the radio access network node device cannot be established for the user equipment On S1 And below, and/or setting a bearer, receiving a user equipment context release request message
  • the embodiment of the present invention further provides a system for processing a context in an evolved network, including a radio access network node device and a core network node device, where the radio access network node device is configured to send an initial context to the core network node device.
  • Establishing a failure message selecting a new core network node for the user equipment; the core network node device is configured to receive an initial context setup failure message sent by the radio access network node device, and establish a failure message according to the initial context, as a user
  • the device selects a new core network node and releases information about the user device.
  • the method and system for processing context in an evolved network provided by the embodiments of the present invention increase the control capability and flexibility of the wireless access network node, improve the processing efficiency of the wireless access network node, and thus effectively improve system flexibility and system. effectiveness.
  • FIG. 1 is a schematic diagram of a network architecture of an evolved network in the prior art
  • FIG. 2 is a flowchart of establishing an RRC connection and an S1 connection by a UE in the prior art
  • FIG. 3 is a flowchart of a first embodiment of a method for processing a context in an evolved network according to the present invention
  • FIG. 4 is a flowchart of a second embodiment of a method for processing a context in an evolved network according to the present invention
  • FIG. 6 is a flowchart of a fourth embodiment of a method for processing a context in an evolved network according to the present invention
  • FIG. 7 is a flowchart of a fifth embodiment of a method for processing a context in an evolved network according to the present invention
  • 8 is a flowchart of a sixth embodiment of a method for processing a context in an evolved network according to the present invention
  • FIG. 9 is a flowchart of a seventh embodiment of a method for processing a context in an evolved network according to the present invention
  • FIG. 11 is a flowchart of a ninth embodiment of a method for processing a context in an evolved network according to the present invention
  • FIG. 12 is a flowchart of a tenth embodiment of a method for processing a context in an evolved network according to the present invention
  • FIG. 13 is a flowchart of an eleventh embodiment of a method for processing a context in an evolved network according to the present invention.
  • FIG. 14 is a flowchart of processing an evolved network according to the present invention.
  • a flowchart of a method embodiment of the twelfth embodiment is a flowchart of a thirteenth embodiment of a method for processing a context in an evolved network according to the present invention
  • FIG. 16 is a flowchart of a fourteenth embodiment of a method for processing a context in an evolved network according to the present invention. Schematic diagram of the structure of the first embodiment;
  • FIG. 18 is a schematic structural diagram of a second embodiment of a RAN node device according to the present invention.
  • FIG. 19 is a schematic structural diagram of a first embodiment of a CN node device according to the present invention.
  • FIG. 20 is a schematic structural diagram of a second embodiment of a CN node device according to the present invention.
  • FIG. 21 is a schematic structural diagram of a third embodiment of a RAN node device according to the present invention.
  • FIG. 22 is a schematic structural diagram of a fourth embodiment of a RAN node device according to the present invention.
  • FIG. 23 is a schematic structural diagram of a third embodiment of a CN node device according to the present invention.
  • FIG. 24 is a schematic structural diagram of a fourth embodiment of a CN node device according to the present invention.
  • 25 is a schematic structural diagram of a fifth embodiment of a RAN node device according to the present invention.
  • 26 is a schematic structural diagram of a sixth embodiment of a RAN node device according to the present invention.
  • FIG. 27 is a schematic structural diagram of a fifth embodiment of a CN node device according to the present invention.
  • FIG. 28 is a schematic structural diagram of a sixth embodiment of a CN node device according to the present invention. detailed description
  • step 25 in order to delete or release these contexts and/or resources, after step 25, if the eNB finds that the S1 context cannot be established for the UE and/or the bearer is set, the eNB feeds back to the E in step 26.
  • the initial context setup failure message and then the eNB releases the RRC connection with the UE, directly deleting or releasing the UE-related information locally.
  • the set bearer may include an E-RAB and/or a default bearer.
  • the MN E After receiving the initial context setup failure message sent by the eNB, the MN E will perform the release process of the context and/or resources of the EPC side UE.
  • the MME may re-attempt to send an initial context setup request message to the eNB, and the eNB may re-attempt to establish the context of the UE and/or set the bearer according to its own situation. Therefore, this local release approach leads to a lack of flexibility in the system, allowing users to successfully access the network or establish a connection. The possibility of picking up is reduced, affecting the user's feelings.
  • the solid E re-transmits the initial context setup request message in step 25 to the eNB, requesting the eNB Re-attempt to establish an S1 context for the UE and/or set the bearer until the eNB successfully establishes the S1 context and/or sets the bearer for the UE. If the eNB fails to successfully establish an S1 context and/or a set bearer for the UE, the MME sends a UE context release command to the eNB, and after receiving the instruction, the eNB releases the RRC connection with the UE, and releases the RRC connection.
  • the information related to the UE is then sent to the MME E to release the UE context release complete message. After receiving the message, the MN E releases the information about the UE on the MME.
  • This approach while increasing the likelihood of process success, limits the capabilities of the eNB even if the eNB does not establish a context and/or set bearer for the UE, eg, if the eNB is at a particular capability and/or load and/or Or management state and/or condition, etc., the eNB cannot actively request the MME to initiate a context and/or connection release procedure, but must wait for the MME's instruction. Therefore, this MME-dependent method leads to poor system flexibility, resulting in Unnecessary signaling interactions reduce system efficiency.
  • the flowchart of the first embodiment of the method for processing a context in an evolved network according to the present invention may specifically include the following steps:
  • Step 301 The RAN node sends, to the CN node, a UE context release indication message for instructing the CN node to release information related to the UE.
  • the RAN node may release the RRC connection of the UE for network management and/or network adjustment/configuration/optimization or the UE is no longer active, or the RAN node finds that the UE has lost contact, or the UE's air interface fails.
  • the recovered error, or the RRC connection has been released/interrupted the RAN node may delete and/or release the context and/or resources related to the UE as soon as possible, and then notify or inform or inform or indicate to the CN node;
  • the UE context release indication message is not limited to being a special message, and may also be used as a parameter in other messages, or may be a network management operation or the like;
  • Step 302 The RAN node releases information related to the UE.
  • step 301 and step 302 may be reversed, that is, the RAN node.
  • the information about the UE may be released after the UE context release indication message is sent to the CN node, or may be released before the UE context release indication is sent to the CN node.
  • the RAN node can release the information related to the UE as early as possible, and then notify or inform or inform or instruct the CN node, thereby effectively improving system flexibility and system efficiency.
  • the flowchart of the second embodiment of the method for processing a context in an evolved network according to the present invention may specifically include the following steps:
  • Step 401 The CN node receives a UE context release indication message sent by the RAN node to instruct the CN node to release information related to the UE.
  • the CN node after receiving the UE context release indication message, the CN node considers that the RAN node has released the information related to the UE, and does not need to instruct the RAN node to perform the release operation, and the CN node can perform related processing on the EPC side, including releasing and Information about the UE, and notification or notification or notification or indication to the relevant network node, for example: SAE Gateway (SAE-GW), releasing information related to the user equipment;
  • SAE-GW SAE Gateway
  • Step 402 The CN node releases information related to the UE according to the UE context release indication message.
  • the CN node after receiving the UE context release indication message sent by the RAN node, releases the information related to the UE, and does not need to instruct the RAN node to perform the release operation, thereby effectively improving system flexibility and system efficiency.
  • the RAN node may be an eNB
  • the CN node may be a specific E. Including the following steps:
  • Step 41 The eNB sends an RRC connection release message to the UE, thereby releasing an RRC connection with the UE.
  • Step 42 The eNB determines to delete and/or has deleted the RRC context and/or S1 context related to the UE, and/or releases the Resources allocated by the UE;
  • step 41 the eNB may determine to release the information related to the UE after sending the RRC connection release message to the UE, or Before transmitting the RRC connection release message to the UE, determining to release information related to the UE;
  • Step 43 The eNB sends a UE context release indication message to the MME;
  • the eNB when the eNB considers it necessary to release the UE's S1 connection, delete the UE-related context, and/or release the resources allocated for the UE, the eNB may perform the deletion and/or release procedure locally, and notify or inform Or the notification or indication to the MN;
  • the UE context release indication message is not limited to a special message, and may also be used as a parameter in other messages, or may also be a network management operation or the like;
  • Step 44 The MME performs related processing on the EPC side.
  • the MME after receiving the notification of the eNB, the MME considers that the eNB has performed release of the RRC connection with the UE, deletes the RRC context and/or S 1 context related to the UE, and/or releases the resources allocated for the UE.
  • the MME may perform related processing on the EPC side, including releasing the S 1 context and/or resources allocated for the UE, and notifying other network nodes to delete and/or release the eNB.
  • the context and/or resources associated with the UE may be performed by the EPC side, including releasing the S 1 context and/or resources allocated for the UE, and notifying other network nodes to delete and/or release the eNB.
  • the RAN side node may release the connection of the UE and delete the context of the UE and/or resources allocated to the UE as soon as possible, and then notify or inform or inform or indicate to the MME, thereby effectively improving the system. Flexibility and system efficiency.
  • the flowchart of the fourth embodiment of the method for processing a context in an evolved network according to the present invention may specifically include the following steps:
  • Step 51 The eNB determines to delete and/or has deleted the RRC context and/or S 1 context related to the UE, and/or releases the resources allocated for the UE;
  • Step 52 The eNB sends a UE context release indication message to the MME.
  • the eNB when the eNB considers it necessary to release the RRC connection and/or the S1 connection of the UE, delete the context of the UE, and/or release the resources allocated for the UE, the eNB may perform a deletion and/or release procedure locally, and
  • the notification or notification or notification or indication to the EI, the UE context release indication message is not limited to a special message, may also be used as a parameter in other messages, or may be a network management operation or the like;
  • Step 5 The eNB sends an RRC connection release message to the UE.
  • the eNB may release the RRC connection and delete the RRC context
  • Step 54 The MME performs related processing on the EPC side.
  • the MME after receiving the notification of the eNB, the MME considers that the eNB has performed release of the RRC connection with the UE, deletes the RRC context and/or S 1 context related to the UE, and/or releases the resources allocated for the UE.
  • the E can perform related processing on the EPC side, including deleting the S1 context related to the UE and/or releasing the resources allocated for the UE, and notifying other network nodes. Delete and/or release UE context and/or resources.
  • step 53 there is no strict timing relationship between step 53 and step 54.
  • the RAN side node may release the connection of the UE as soon as possible and delete the context of the UE and/or resources allocated for the UE, and then notify or inform or inform or indicate to the E, thereby Effectively increase system flexibility and system efficiency, but the specific steps taken vary.
  • the flowchart of the fifth embodiment of the method for processing a context in an evolved network according to the present invention may specifically include the following steps:
  • Step 71 The RAN node sends an initial context setup failure message to the CN node, and determines to request the CN node to release information related to the UE.
  • the RAN node cannot establish an S1 context and/or a set bearer for the UE, send an initial context setup failure message to the CN node, where the set bearer may include an E-RAB and/or a default bearer;
  • Step 72 The RAN node sends, to the CN node, a UE context release request message for requesting the CN node to release information related to the UE according to the determination result;
  • Step 73 The RAN node receives a UE context release command message sent by the CN node according to the UE context release request message for instructing the RAN node device to release information related to the UE, and releases information related to the UE.
  • the RAN node determines that the CN node is requested to release the information related to the UE, and after receiving the release instruction of the CN node, releases the information related to the UE, which enhances the control capability and flexibility of the RAN node, and can prevent the CN node from re-issuing unnecessary attempts.
  • the instruction improves the processing efficiency of the RAN node, thereby effectively improving system flexibility and system efficiency.
  • the flowchart of the sixth embodiment of the method for processing a context in an evolved network according to the present invention may specifically include the following steps:
  • Step 81 The CN node establishes a failure message according to an initial context sent by the RAN node, and determines that the RAN node cannot establish an S1 context and/or set a bearer for the UE.
  • setting the bearer may include an E-RAB and/or a default bearer
  • Step 82 The CN node receives a UE context release request message sent by the RAN node for requesting release of UE-related information, and returns, according to the determination result, a UE context release command for instructing the RAN node to release UE-related information.
  • Step 83 The CN node releases the information related to the UE according to the UE context release complete message sent by the RAN node for the UE context release command message.
  • the CN node receives the request of the RAN node to release the UE-related information, and then instructs the RAN node to release the information related to the UE, The CN node releases the UE-related information, which can prevent the CN node from re-issuing unnecessary attempting instructions, improve the processing efficiency of the RAN node, thereby effectively improving system flexibility and system efficiency.
  • the flow chart of the seventh embodiment of the method for processing the context in the evolved network is different from the technical solution shown in FIG. 2, and the step 25 may specifically include the following steps:
  • Step 66 The eNB sends an initial context setup failure message to the MN.
  • the initial context setup failure message is sent to the MME, where the set bearer may include the E-RAB and/or the default bearer; Step 67, the eNB determines Requesting the MME to delete the RRC context and/or S 1 associated with the UE And, and/or release resources allocated for the UE;
  • Step 68 The eNB sends a UE context release request message to the MN.
  • the UE context release request message is not limited to a special message, and may also be used as a parameter in other messages, for example: a specific cause value, or may be a network management operation or the like;
  • Step 69 The MME sends a UE context release command message to the eNB.
  • Step 61 The eNB sends an RRC connection release request message to the UE.
  • the connection release request message may include a cause value (Caus e ) of the air interface release; the cause value may be indication information indicating that the UE performs a preset operation and/or a special cause value.
  • the indication information indicating that the UE performs the preset operation may include indication information indicating that the UE establishes an RRC connection with the RAN node; or indication information indicating that the UE establishes an RRC connection with the new RAN node; or indicating that the UE is after the preset time and/or Or indication information that establishes an RRC connection with the RAN node under the trigger of the preset instruction; or indication information indicating that the RAN node instructs the RAN node to select a new CN node.
  • the UE may abandon the retry, that is, after receiving the indication information, the UE does not retry the interaction with the RAN node within a preset time, for example, the eNB establishes a RAN connection, or only in other instructions.
  • the interaction with the RAN node may be performed again under the trigger of the indication, or may be re-tried to establish a RAN connection with the RAN node after receiving the indication information.
  • a RAN connection with the RAN node again There may be two ways to establish a RAN connection with the RAN node again: 1;) retrying to establish a RAN connection on the original RAN node, eg, the eNB; 2), the UE may reselect a new cell and/or The eNB and/or the access system retry to establish a RAN connection with the RAN node, and which retry method is selected may also depend on implementation considerations such as network planning, load, interference, and signal strength;
  • Step 61 The eNB deletes an RRC context and/or an S1 context related to the UE, and/or releases a resource allocated for the UE.
  • Step 61 The eNB sends a UE context release complete message to the MME.
  • Step 61 3 The E E deletes the S 1 context related to the UE and/or releases the resources allocated for the UE.
  • This embodiment increases the control capability and flexibility of the eNB, and can avoid the MME re-issuing
  • the attempted instruction is to improve the processing efficiency of the eNB, thereby effectively improving system flexibility and system efficiency.
  • the flowchart of the eighth embodiment of the method for processing the context in the evolved network is different from the technical solution shown in FIG. 2, and the step 25 may specifically include the following steps:
  • Step 76 The eNB sends an initial context setup failure message to the MN.
  • Step 77 The eNB determines to release the RRC connection, delete the RRC context and/or S 1 context related to the UE, and/or release the resources allocated for the UE.
  • Step 78 The eNB sends an RRC connection release request message to the UE.
  • the connection release request message may include a cause value (Caus e ) of the air interface release.
  • the cause value may be indication information indicating that the UE performs a preset operation, and may be other Special reason value.
  • the indication information indicating that the UE performs the preset operation may include indication information indicating that the UE establishes an RRC connection with the RAN node; or indication information indicating that the UE establishes an RRC connection with the new RAN node; or indicating that the UE is after the preset time and/or Or indication information that establishes an RRC connection with the RAN node under the trigger of the preset instruction; or indication information indicating that the RAN node instructs the RAN node to select a new CN node.
  • the UE may abandon the retry, that is, after receiving the indication, the UE does not retry the interaction with the RAN node within a preset time, for example: the eNB establishes a RAN connection, or only in other instructions or The interaction with the RAN node will only be performed again under the trigger of the indication.
  • the UE may retry to establish a RAN connection with the RAN node again, and retrying to establish a RAN connection with the RAN node may be performed in two ways: 1). Initiating the RAN on the original RAN node, for example, the eNB.
  • the connection reconstruction process 2), the UE may reselect a new RAN node, and establish a RAN connection with the new RAN node. If the connection is established on the new RAN node, the information on the original RAN node needs to be deleted. The deletion may be performed by the RAN node itself, or may be under the indication or request or command of other nodes or UEs. delete. Moreover, when the UE retryes again, the UE may carry specific indication information to the eNB to assist and/or direct the eNB to perform appropriate processing, for example, selecting a suitable CN node, for example, an MME. Which retry method to choose depends on implementation considerations such as network planning, load, interference, and signal strength; Step 79: The UE sends a UE context release indication message to the MME.
  • the UE context release indication message is not limited to a special message, and may also be used as a parameter in other messages, for example: a specific cause value, or may be a network management operation or the like;
  • Step 71 The MME deletes the S1 context related to the UE, and/or releases the resource allocated to the UE.
  • This embodiment increases the control capability and flexibility of the eNB, and can prevent the MME from re-issuing unnecessary command instructions, which can improve the processing efficiency of the eNB, thereby effectively improving system flexibility and system efficiency.
  • the flowchart of the ninth embodiment of the method for processing a context in an evolved network according to the present invention may specifically include the following steps:
  • Step 91 The RAN node sends an initial context setup failure message to the CN node.
  • the RAN node if the RAN node is unable to establish an S1 context and/or a set bearer for the UE, the RAN node sends an initial context setup failure message to the CN node, where the set bearer may include an E-RAB and/or a default bearer;
  • Step 92 The RAN node selects a new CN node for the UE.
  • the RAN node when the RAN node cannot establish the S1 context and/or set the bearer for the UE, the RAN node may reselect a CN node, which increases the control capability and flexibility of the RAN node, and can avoid the RAN node always
  • the failure scenario improves the UE access success rate, which effectively improves system flexibility and system efficiency.
  • the flowchart of the tenth embodiment of the method for processing a context in an evolved network according to the present invention may specifically include the following steps:
  • Step 1 01 The CN node receives an initial context setup failure message sent by the RAN node. Specifically, the CN node may determine, according to the initial context setup failure message, that the RAN node cannot establish an S1 context and/or set a bearer for the UE, where Fixed bearers may include E-RAB and/or Default bearer
  • Step 1 02 The CN node establishes a failure message according to the initial context, selects a new CN node for the UE, and releases information related to the UE. The RAN node then retryes to establish an S 1 connection with the new CN node.
  • the CN node when the RAN node cannot establish the S1 context and/or set the bearer for the UE, the CN node can reselect a CN node, which increases the control capability and flexibility of the CN node, and can avoid the RAN node always
  • the failure scenario improves the UE access success rate, which effectively improves system flexibility and system efficiency.
  • the flowchart of the eleventh embodiment of the method for processing the context in the evolved network is different from the technical solution shown in FIG. 2 , after the step 25, when the eNB receives the MME sends the After the initial context setup request message is found, it is found that the S1 context and/or the set bearer cannot be established for the UE, and the method further includes the following steps:
  • Step 86 The eNB sends an initial context setup failure message to the MN.
  • Step 87 The MME deletes the S1 context related to the UE, and/or releases the resource allocated to the UE.
  • the eNB may decide to reselect the MME;
  • Step 89 The eNB sends an initial UE message to the new MN.
  • Step 81 After receiving the initial UE message sent by the eNB, the new MN sends an initial context establishment request message to the eNB.
  • the new MN initiates the establishment process of the S1 connection to the eNB;
  • Step 81 The eNB informs the UE to establish an E-RAB through an RRC connection reconfiguration message, and if the UE can establish an E-RAB, sends an RRC connection reconfiguration complete response message to the eNB;
  • Step 81 The eNB establishes an S 1 context.
  • Step 81 3. The eNB sends an initial context setup response message to the new MN.
  • the eNB may re-initiate one or more new MME selection procedures, that is, when the eNB finds that the S1 context cannot be established for the UE through a certain E or cannot establish a set bearer for the UE, the eNB may select a new solid again.
  • the eNB when the eNB cannot establish the S1 context and/or set the bearer for the UE, the eNB may decide to reselect an EPC node.
  • the scheme substantially increases the control capability and flexibility of the eNB, can avoid the scenario where the eNB always fails, and improves the UE access success rate, thereby effectively improving system flexibility and system efficiency.
  • step 86 is performed first, and then step 89 is performed.
  • step 89 is performed.
  • Step 1 31 The MN sends a reselection indication message to the eNB according to the initial context establishment failure message, where the reselection indication message includes reselection indication information.
  • Step 88 may be specifically as follows: Step 1 32: The eNB determines, according to the reselection indication information carried in the reselection indication message, that the UE selects a new MME.
  • the eNB when the eNB cannot establish the S1 context and/or set the bearer for the UE, the eNB may reselect an EPC node under the direction of the MME.
  • the scheme substantially increases the control capability and flexibility of the eNB, can avoid the scenario where the eNB always fails, and improves the UE access success rate, thereby effectively improving system flexibility and system efficiency.
  • FIG. 15 a flowchart of a thirteenth embodiment of a method for processing a context in an evolved network according to the present invention.
  • the eNB receives the initial transmission of the E-E
  • the context setup request message After the context setup request message is found, it is found that the S1 context cannot be established for the UE and/or the bearer is set, and the following steps can also be included:
  • Step 96 The eNB sends an initial context setup failure message to the MN.
  • Step 97 The MME determines to select a new MME. After receiving the initial context setup failure message, the MME finds that the eNB cannot establish an S1 context and/or a set bearer for the UE, and the MME may determine the UE as the UE. Re-select a new MN, this re-selection can be based on capabilities such as eNB and/or MN, load, network topology or other implementation considerations;
  • Step 98 The MME sends an initial UE message to the new MME. After determining to reselect the new MME, the MME may send a request and/or an indication and/or a message to the new MME, for example: forwarding related information of the UE and/or Or message, the new EPC node (such as solid E) can initiate on the eNB if the UE is accepted
  • Step 99 The MME releases the S1 context related to the UE and/or the resource allocated for the UE.
  • Step 91 The eNB informs the UE to establish an E-RAB through an RRC connection reconfiguration message, and if the UE can establish an E-RAB, sends an RRC connection reconfiguration complete response to the eNB;
  • Step 91 2 The eNB establishes an S 1 context.
  • Step 91 The eNB sends an initial context setup response message to the new MN.
  • the EPC node when the EPC node finds that the context and/or the setup bearer cannot be established for the UE on the eNB, the EPC node may decide to reselect an EPC node, thereby increasing the control capability and flexibility of the EPC node, and avoiding The EPC node always fails, improving the UE access success rate, thereby effectively improving system flexibility and system efficiency.
  • FIG. 16 is a flowchart of a fourteenth embodiment of a method for processing a context in an evolved network according to the present invention.
  • the difference from the technical solution shown in FIG. 15 is that the initial context established by the eNB to the MME is established in step 96.
  • the failure message includes a reselection indication information.
  • step 97 may specifically be as follows:
  • Step 914 The MME determines to select a new MME according to the reselection indication information carried in the initial context establishment failure message.
  • the EPC node when the EPC node finds that the UE cannot establish a context and/or sets a load for the UE, the EPC node may decide to reselect an EPC node under the instruction of the eNB, thereby The control capability and flexibility of the EPC node are increased, and the situation that the EPC node always fails is avoided, and the UE access success rate is improved, thereby effectively improving system flexibility and system efficiency.
  • the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.
  • a schematic structural diagram of a first embodiment of a RAN node device may specifically include a first sending module 151 and a first releasing module 152, where the first sending module 151 is configured to send an indication to the CN node.
  • the UE node releases the UE context release indication message of the information related to the UE; specifically, when the RAN node device may release the RRC connection of the UE for reasons such as network management and/or network adjustment/configuration/optimization or the UE is no longer active, Or the RAN node device finds that the UE has lost contact, or the UE's air interface has an unrecoverable error, or the RRC connection has been released/interrupted, and the RAN node device can delete and/or release the UE-related context and/or resources as soon as possible.
  • the UE context release indication message is not limited to a special message, and may also be used as a parameter in other messages, or may also be a network management Operation, etc.; the first release module 152 is configured to release information related to the UE; specifically, A sending module 151 may first send a UE context release indication message to the CN node, and then the first release module 152 may release the information related to the UE, or the first release module 152 may first release information related to the UE, and the first sending module 151 The UE context release indication message is sent to the CN node.
  • the first release module 152 can release the information related to the UE as soon as possible, and the first sending module 151 notifies or informs or informs or instructs the CN node, thereby effectively improving system flexibility and system efficiency.
  • the first sending module 151 is further configured to: if the RAN node cannot establish the S1 context for the UE, / or set the bearer, send an initial context establishment failure message to the CN node.
  • the embodiment may further include a first determining module 161, configured to determine release of information related to the UE if the RAN node device is unable to establish an S1 context and/or set a bearer for the UE.
  • the first release module 152 is further configured to release information related to the UE according to the determination result of the first determining module 161.
  • the set bearer may include an E-RAB and/or a default bearer.
  • the first release module 152 may specifically include a first deleting unit 16 3 and/or a first releasing unit 164, where the first deleting unit 163 is configured to delete an RRC context and/or an S 1 context related to the UE.
  • the first release unit 164 is configured to release resources allocated for the UE.
  • the first sending module 151 is further configured to send an RRC connection release message to the UE, thereby releasing the RRC connection of the UE.
  • the RRC Connection Release message may include indication information indicating that the UE performs a preset operation.
  • the packet in the RRC Connection Release message may also include other special cause values.
  • the indication information indicating that the UE performs the preset operation may include indication information indicating that the UE establishes an RRC connection with the RAN node; or indication information indicating that the UE establishes an RRC connection with the new RAN node; or indicating that the UE is after the preset time and/or Or the indication information of establishing an RRC connection with the RAN node triggered by the preset instruction; or indicating the indication information that the RAN node instructs the RAN node to select a new CN node.
  • the UE may abandon the retry, that is, after receiving the indication information, the UE does not perform interaction with the network within a preset time, or may be executed again only when triggered by other instructions or indications.
  • an RRC Connection Request message is sent to the RAN node device.
  • the UE may initiate a retry again, and may initiate the retry again.
  • the device sends an RRC connection request message; 2), the UE may reselect a new RAN node device, and send an RRC connection request message to the new RAN node device.
  • Which retry method to choose depends on implementation considerations such as network planning, load, interference, and signal strength.
  • the first sending module 151 first sends an initial context setup failure message to the CN node, and the first determining module 161 determines to release the UE related information. Information, then the first sending module 151 indicates to the CN node to release information related to the UE, instructing the UE to release the RAN connection, and the first deleting unit 163 deletes the information with the UE.
  • the RRC context and/or the SI context; the first release unit 164 releases the resources allocated for the UE, increases the control capability and flexibility of the RAN node device, and can prevent the CN node device from re-issuing unnecessary trial commands and improve the RAN node.
  • the processing efficiency of the equipment effectively increases system flexibility and system efficiency.
  • FIG. 19 it is a schematic structural diagram of a first embodiment of a CN node device according to the present invention, which may include a first receiving module 181 and a second releasing module 182, where the first receiving module 181 is configured to receive a RAN node for sending a UE context release indication message indicating that the CN node device releases the information related to the UE; specifically, according to the UE context release indication message, the CN node device may learn that the RAN node has determined to release information related to the UE; The UE-related information is released according to the UE context release indication message.
  • the first receiving module 181 is configured to receive a RAN node for sending a UE context release indication message indicating that the CN node device releases the information related to the UE; specifically, according to the UE context release indication message, the CN node device may learn that the RAN node has determined to release information related to the UE; The UE-related information is released according to the UE context release indication message.
  • the CN node device can be prevented from re-issuing unnecessary attempting instructions, and the processing efficiency of the RAN node is improved, thereby effectively improving system flexibility and system efficiency.
  • the second release module 182 may specifically include a second deletion unit 192 and/or a second release.
  • the CN node device can be prevented from re-issuing unnecessary attempting instructions, and the processing efficiency of the RAN node is improved, thereby effectively improving system flexibility and system efficiency.
  • FIG. 21 it is a schematic structural diagram of a third embodiment of the RAN node device according to the present invention, which may specifically include a second sending module 171, a second determining module 172, a second receiving module 173, and a third releasing module 174, where the second The sending module 171 is configured to send an initial context setup failure message to the CN node. Specifically, if the RAN node device cannot establish an S1 context and/or set a bearer for the UE, the second sending module 171 sends an initial context setup failure message to the CN node.
  • the setting of the bearer may include the E-RAB and/or the default bearer.
  • the second determining module 172 is configured to determine to request the CN node to release information related to the UE, and instruct the second sending module 171 to send the information to the CN node.
  • the third release module 1 74 is configured to receive the UE context release command by the second receiving module 173. After the message, the UE-related information is released.
  • the CN node may be requested to indicate that the information related to the UE is released, to prevent the CN node from re-issuing unnecessary attempting instructions, and to improve the RAN node device. Processing efficiency, which effectively improves system flexibility and system efficiency.
  • FIG. 22 it is a schematic structural diagram of a fourth embodiment of a RAN node device according to the present invention.
  • the second sending module 171 is further configured to send, to the UE, an indication that the UE releases the RRC connection. And an RRC connection release message, where the RRC connection release message includes indication information indicating that the UE performs a preset operation.
  • the indication information indicating that the UE performs the preset operation may include indication information indicating that the UE establishes an RRC connection with the RAN node; or indication information indicating that the UE establishes an RRC connection with the new RAN node; or indicating that the UE is after the preset time and/or Or the indication information of establishing an RRC connection with the RAN node triggered by the preset instruction; or indicating the indication information that the RAN node instructs the RAN node to select a new CN node.
  • other special cause values may be included in the RRC connection release message.
  • the UE may abandon the retry, that is, after receiving the indication, the UE does not perform interaction with the network within a preset time, or may only perform again after being triggered by other instructions or instructions.
  • the interaction of the network sends an RRC Connection Request message to the RAN node device.
  • the UE may initiate a retry again. There may be two ways to initiate the retry again: 1) Initiating a connection reestablishment process on the original RAN node, for example, the eNB, and sending the connection reestablishment process to the original RAN node device.
  • the UE may reselect a new RAN node device and send an RRC Connection Request message to the new RAN node device.
  • Which retry method to choose depends on implementation considerations such as network planning, load, interference, and signal strength.
  • the third release module 174 may specifically include a third deletion unit 175 and/or a third release unit 176, where the third deletion unit 175 is configured to delete the RRC context and related to the UE. / or S 1 context; the third release unit 1 76 is used to release the allocation for the UE Resources.
  • the CN node may be requested to release the UE-related information to prevent the CN node from re-issuing unnecessary attempting instructions, and the RAN node device may also Instructing the UE to release the RAN connection improves the processing efficiency of the RAN node device, thereby effectively improving system flexibility and system efficiency.
  • a schematic structural diagram of a third embodiment of a CN node device may specifically include a third receiving module 177, a third determining module 178, a third sending module 179, and a fourth releasing module 171 0, where
  • the third receiving module 177 is configured to receive an initial context setup failure message sent by the RAN node, receive a UE context release request message sent by the RAN node for requesting release of information related to the UE, and send the RAN node to send a UE context release command message.
  • the UE Context Release Complete message is used.
  • the third determining module 178 is configured to determine, according to the initial context setup failure message received by the third receiving module, that the RAN node cannot establish an S1 context and/or set a bearer for the UE.
  • the E-RAB and/or the default bearer are included;
  • the third sending module 179 is configured to return, to the RAN node, a UE context release command message for instructing the RAN node to release information related to the UE according to the determining result of the third determining module;
  • the four release module 171 0 is configured to release the UE context according to the third receiving module Completion message, the release of information related to the UE.
  • the third determining module 178 determines that the RAN node cannot establish the S1 context and/or the setup bearer according to the initial context setup failure message sent by the RAN node, and therefore, receives the third bearer module 177.
  • the third sending module 179 sends a UE context release command message to the RAN node to instruct the RAN node device to perform a release operation, to prevent the CN node device from re-issuing unnecessary attempting instructions, and improve the RAN.
  • the processing efficiency of the nodes effectively improves system flexibility and system efficiency.
  • the fourth release module 171 0 may specifically include a fourth deletion unit 171 1 and/or The fourth release unit 1712, wherein the fourth deletion unit 171 1 is configured to delete the S 1 context related to the UE; and the fourth release unit 1712 is configured to release the resource allocated for the UE.
  • the third determining module 178 determines that the RAN node cannot establish the S1 context and/or the setup bearer according to the initial context setup failure message sent by the RAN node, and therefore, receives the third bearer module 177.
  • the third sending module 179 sends a UE context release command message to the RAN node to command the RAN node device to perform a release operation
  • the fourth deleting unit 1711 deletes the S1 related to the UE.
  • the fourth release unit 1712 releases the resources allocated for the UE, thereby preventing the CN node device from re-issuing unnecessary attempt instructions, improving the processing efficiency of the RAN node, thereby effectively improving system flexibility and system efficiency.
  • FIG. 25 it is a schematic structural diagram of a fifth embodiment of a RAN node device according to the present invention, which may specifically include a fourth sending module 21 1 and a first selecting module 212, where the fourth sending module 21 1 is configured to send an initial to the CN node.
  • Context establishment failure message specifically, if the RAN node device cannot establish the S1 context and/or set the bearer for the UE, the fourth sending module 21 1 sends an initial context setup failure message to the CN node;
  • the first selecting module 212 is configured to select a new CN node for the UE after the fourth sending module 21 1 sends the initial context setup failure message.
  • the first selection module 212 may reselect a CN node, which increases the control capability and flexibility of the RAN node device.
  • the scenario that the RAN node device always fails can be avoided, and the UE access success rate is improved, thereby effectively improving system flexibility and system efficiency.
  • FIG. 26 it is a schematic structural diagram of a sixth embodiment of a RAN node device according to the present invention.
  • the embodiment may further include a fourth receiving module 221, configured to receive a CN node for initial
  • the first selection module 222 is configured to select, according to the reselection indication information carried in the reselection indication message, the UE to select the reselection indication message that is sent by the re-selection indication information.
  • the fourth sending module 21 1 may also be configured to send an initial UE message to the new CN node, thereby requesting to establish an S1 connection with the new CN node.
  • the first selecting unit 222 may reselect a CN node under the guidance of the CN node, and increase the control capability of the RAN node device. And flexibility, can avoid the scenario where the RAN node device always fails, improve the UE access success rate, thereby effectively improving system flexibility and system efficiency.
  • FIG. 27 it is a schematic structural diagram of a fifth embodiment of a CN node device according to the present invention, which may specifically include a fifth receiving module 231, a second selecting module 232, and a fifth releasing module 233, wherein the fifth receiving module 231 is configured to receive An initial context setup failure message sent by the RAN node; the CN node device determines that the RAN node cannot establish an S1 context and/or sets a bearer for the UE according to the initial context setup failure message; wherein the set bearer includes the E-RAB and/or Or the default bearer; the second selecting module 232 is configured to select a new CN node according to the initial context setup failure message received by the fifth receiving module 231, and the fifth release module 233 is configured to receive the initial according to the fifth receiving module 231.
  • a context establishment failure message releases information related to the UE.
  • the second selection module 232 may reselect a CN node, which increases the control capability and flexibility of the RAN node, and can avoid the RAN node.
  • the scenario of always failing improves the access success rate of the UE, thereby effectively improving system flexibility and system efficiency.
  • the initial context setup failure message includes reselection indication information.
  • the second selection module 232 may specifically The second selection unit 241 is configured to select a new CN node for the UE according to the reselection indication information carried in the initial context setup failure message.
  • the embodiment may further include a fifth sending module 242, configured to send an initial UE message to the new CN node, so as to establish an S1 connection with the new CN node device.
  • a fifth sending module 242 configured to send an initial UE message to the new CN node, so as to establish an S1 connection with the new CN node device.
  • the fifth release module 233 may specifically include a fifth deletion unit 243 and/or a fifth release unit 244, where the fifth deletion unit 243 is configured to delete the S1 context related to the UE; Release the resources allocated for the UE.
  • the second selecting unit 241 can reselect a CN node under the guidance of the RAN node, which increases the control capability and flexibility of the RAN node, can avoid the scenario where the RAN node always fails, and improves the UE access success rate, thereby effectively improving the system. Flexibility and system efficiency.
  • the embodiment of the invention further provides a system for processing a context in an evolved network, including a RAN node device and a CN node device.
  • the RAN node device sends a UE context release indication message to the CN node device for instructing the CN node device to release information related to the UE, releasing information related to the UE.
  • the RAN node device may release the RRC connection of the UE for network management and/or network adjustment/configuration/optimization or the UE is no longer active, or the RAN node device finds that the UE has lost contact, or the UE's air interface occurs. An unrecoverable error, or an RRC connection has been released/interrupted, the RAN node device may delete and/or release the context and/or resources associated with the UE as early as possible, and then notify or inform or inform or indicate to the CN node device.
  • the CN node device is configured to receive a UE context release indication message sent by the RAN node device to instruct the CN node device to release information related to the UE, and release information related to the UE according to the UE context release indication message.
  • the CN node device After receiving the UE context release indication message, the CN node device considers that the RAN node device has released the information about the UE, and does not need to instruct the RAN node device to perform the release operation, and the CN node device can perform related processing on the EPC side.
  • the UE context release indication message is not limited to a special message, and may also be used as a parameter in other messages, or may be a network management operation or the like.
  • the CN node device after receiving the UE context release indication message sent by the RAN node device, releases the information about the UE, and does not need to instruct the RAN node device to perform the release operation, thereby enhancing the flexibility and flexibility of the RAN node device. And work efficiency, which effectively improves system flexibility and system efficiency.
  • releasing UE-related information includes deleting an RRC context and/or an S 1 context related to the UE; and/or releasing resources allocated for the UE.
  • the embodiment of the invention further provides a system for processing a context in an evolved network, including a RAN node device and a CN node device.
  • the RAN node device is configured to send an initial context setup failure message to the CN node device, and determine to request the CN node device to release information related to the UE, and send, according to the determination result, the CN node device to request release from the CN node device.
  • the UE context release request message of the information about the UE is used to receive the UE context release command message sent by the CN node device according to the UE context release request message for instructing the RAN node device to release the UE-related information, and release the information about the UE.
  • the CN node device is configured to determine, according to the initial context setup failure message sent by the RAN node device, that the RAN node device cannot establish an S1 context and/or set a bearer for the UE, and receive information sent by the RAN node device for requesting release of the UE.
  • a UE context release request message according to the determination result, returning, to the RAN node device, a UE context release command message for releasing the UE-related information for instructing the RAN node device to be sent according to the received RAN node device for the UE context release command message.
  • the UE context release complete message releases information related to the UE.
  • This embodiment increases the control capability and flexibility of the RAN node device, avoids the scenario where the RAN node device always fails, and improves the UE access success rate, thereby effectively improving system flexibility and system efficiency.
  • releasing information related to the UE includes deleting an RRC context and/or an S 1 context associated with the UE; and/or releasing resources allocated for the UE.
  • the embodiment further provides a system for processing a context in an evolved network, including a RAN node device and a CN node device.
  • the RAN node device is configured to send an initial context setup failure message to the CN node device, that is, the UE Select a new CN node;
  • the CN node device is configured to receive an initial context setup failure message sent by the RAN node, select a new CN node according to the initial context establishment failure message, and release information related to the UE.
  • releasing information related to the UE includes deleting an RRC context and/or an S 1 context associated with the UE; and/or releasing resources allocated for the UE.
  • This embodiment increases the control capability and flexibility of the RAN node device, avoids the scenario where the RAN node device always fails, and improves the UE access success rate, thereby effectively improving system flexibility and system efficiency.
  • all of the above retry or reselection processes can be cycled back and forth until successful, or some limit number and/or time is reached.
  • the number and/or time of retrying or reselection can be a standard specification value or dependent on the specific implementation of each device.
  • the UE-related information on the original node needs to be deleted. This deletion may be the original node deleting itself locally, or may be an indication at another node or UE. Or delete it under request or command.

Landscapes

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

Abstract

Les modes de réalisation de la présente invention se rapportent à un procédé et à un système de traitement de contexte dans un réseau évolutif. Le procédé comprend les étapes suivantes: un message d'indication de libération de contexte d'un équipement utilisateur (UE) est envoyé à un nœud de réseau central (CN) pour lui indiquer de libérer l'information se rapportant à l'UE; et l'information est libérée. Un dispositif de nœud de réseau d'accès radio (RAN) et un dispositif de nœud de réseau central (CN) sont également mis en œuvre selon les modes de réalisation de l'invention. Le dispositif de nœud RAN comprend un premier module d'envoi et un premier module de libération. Le premier module d'envoi envoie le message d'indication de libération de contexte de l'UE au nœud CN pour lui indiquer de libérer l'information se rapportant à l'UE. Le premier module de libération libère l'information se rapportant à l'UE. Les modes de réalisation de l'invention améliorent effectivement la souplesse et l'efficience du système.
PCT/CN2009/070346 2009-02-03 2009-02-03 Procédé et système de traitement de contexte dans un réseau évolutif WO2010088794A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2009/070346 WO2010088794A1 (fr) 2009-02-03 2009-02-03 Procédé et système de traitement de contexte dans un réseau évolutif

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2009/070346 WO2010088794A1 (fr) 2009-02-03 2009-02-03 Procédé et système de traitement de contexte dans un réseau évolutif

Publications (1)

Publication Number Publication Date
WO2010088794A1 true WO2010088794A1 (fr) 2010-08-12

Family

ID=42541641

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/070346 WO2010088794A1 (fr) 2009-02-03 2009-02-03 Procédé et système de traitement de contexte dans un réseau évolutif

Country Status (1)

Country Link
WO (1) WO2010088794A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108617035A (zh) * 2017-01-24 2018-10-02 展讯通信（上海）有限公司 基站及其释放终端的方法
CN110089193A (zh) * 2016-12-29 2019-08-02 Oppo广东移动通信有限公司 上下文释放方法、设备及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1052789A1 (fr) * 1999-05-13 2000-11-15 ICO Services Ltd. Système mobile de téléphonie par satellite avec service de transmission radio par packet
CN101291457A (zh) * 2008-05-30 2008-10-22 中兴通讯股份有限公司 一种ue上下文更新失败的处理方法
CN101296496A (zh) * 2007-04-29 2008-10-29 中兴通讯股份有限公司 一种跟踪区更新或切换过程中避免资源被错误释放的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1052789A1 (fr) * 1999-05-13 2000-11-15 ICO Services Ltd. Système mobile de téléphonie par satellite avec service de transmission radio par packet
CN101296496A (zh) * 2007-04-29 2008-10-29 中兴通讯股份有限公司 一种跟踪区更新或切换过程中避免资源被错误释放的方法
CN101291457A (zh) * 2008-05-30 2008-10-22 中兴通讯股份有限公司 一种ue上下文更新失败的处理方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN)", 3GPP TS 36.300 V8.7.0 3RD GENERATION PARTNERSHIP PROJECT *
"Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) (Release 8)", 3GPP TS 36.413 V8.4.0 3TD GENERATION PARTNERSHIP PROJECT, December 2008 (2008-12-01) *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110089193A (zh) * 2016-12-29 2019-08-02 Oppo广东移动通信有限公司 上下文释放方法、设备及系统
CN110089193B (zh) * 2016-12-29 2023-11-10 Oppo广东移动通信有限公司 上下文释放方法、设备及系统
CN108617035A (zh) * 2017-01-24 2018-10-02 展讯通信（上海）有限公司 基站及其释放终端的方法

Similar Documents

Publication Publication Date Title
US20230345312A1 (en) User mobility method and device
TWI722534B (zh) 協定資料單元會話切換衝突之處理方法及其使用者設備
JP7145319B2 (ja) リリースおよびリダイレクトが続く再開の要求
EP3611904B1 (fr) Gestion de session de données
US20190327659A1 (en) Handover using dual active connections
WO2018113661A1 (fr) Procédé et équipement de mobilité d'utilisateur
TW201944840A (zh) 處理qos 流的方法及使用者設備
WO2016123809A1 (fr) Procédé et dispositif d'optimisation de signalisation
TWI756725B (zh) 語音呼叫方法以及移動終端
US10587757B2 (en) Method and apparatus for processing terminal that is performing voice service, and communications system
US20150215822A1 (en) Efficient session management method and apparatus guaranteeing terminal mobility
EP2993939B1 (fr) Procédé de transfert de cellules et station de base pour le transfert d'un équipement utilisateur en mode d'agrégation de porteuses
WO2020063666A1 (fr) Équipement d'utilisateur et procédé exécuté par ce dernier, station de base et procédé exécuté par cette dernière, ainsi qu'entité de commande mobile et procédé exécuté par cette dernière
WO2018126961A1 (fr) Procédé de communication, dispositif de réseau d'accès et terminal
JP2017534216A (ja) 選択されたｉｐフロー超低レイテンシ
CN107277868B (zh) 一种电路域回退方法和设备
WO2008113235A1 (fr) Procédé pour éviter la libération erronée de ressources pendant une mise à jour de zone de suivi ou un transfert intercellulaire
US11202338B2 (en) Session establishment method and apparatus
JP7111426B2 (ja) 方法及びｕｓｅｒ ｅｑｕｉｐｍｅｎｔ
US20230143942A1 (en) Managing a ue preferred configuration
KR20170115888A (ko) 무선 통신 시스템에서 회선 교환 서비스 제공 방법 및 장치
KR20200054309A (ko) 무선 연결을 재개하기 위한 사용자 단말 및 방법
JP2023530248A (ja) セルグループ処理方法、装置及び通信機器
WO2013113159A1 (fr) Procédé de récupération de connexions sans fil, système de communication mobile, équipement utilisateur et station de base
WO2016184157A1 (fr) Procédé et appareil permettant le traitement d'un programme dans un système de communication mobile

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09839511

Country of ref document: EP

Kind code of ref document: A1