CN105338653A - Method and equipment supporting UE bearing recovery - Google Patents

Abstract

The present invention provides several methods for supporting UE bearer recovery and corresponding equipment. No matter SeNB or SGW loses the context of UE bearer, by applying the technical solution of this application, UE bearer can be reasonably rebuilt, transferred or deleted, so that Under the dual-connection architecture where the core network is separated, the problem of UE bearer recovery can be solved, the reliability and stability of the network are greatly improved, and the network experience of users is improved. At the same time, the solution of the present invention is very flexible and can meet the requirements of public communication services.

Description

Method and device for supporting UE bearer recovery

technical field

The present invention relates to wireless communication technology, in particular to a method and equipment for supporting UE bearer recovery.

Background technique

Modern mobile communications tend to provide users with high-speed multimedia services, as shown in Figure 1, which is a system architecture diagram of System Architecture Evolution (SAE). in:

User Equipment (UE) 101 is a terminal device for receiving data.

Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 102 is a radio access network including macro base stations (eNodeBs/NodeBs) that provide UEs with an interface to access the radio network.

Mobility Management Entity (MME) 103 is responsible for managing UE's mobility context, session context and security information.

Serving Gateway (SGW) 104 mainly provides user plane functions, and MME 103 and SGW 104 may be in the same physical entity.

The packet data network gateway (PGW) 105 is responsible for functions such as billing and lawful interception, and may also be in the same physical entity as the SGW 104 .

A Policy and Charging Rules Function (PCRF) 106 provides Quality of Service (QoS) policies and charging rules.

The General Packet Radio Service Support Node (SGSN) 108 is a network node device that provides routing for data transmission in the Universal Mobile Telecommunications System (UMTS).

The Home Subscriber Server (HSS) 109 is the home subsystem of the UE, responsible for protecting user information including the current location of the user equipment, the address of the serving node, user security information, and the packet data context of the user equipment.

In Release 12 (Rel-12), 3GPP proposed the requirement for small cell enhancement. The target scenarios for small cell enhancement include scenarios with macro cell coverage and scenarios without macro cell coverage, indoor and outdoor, ideal and non-ideal Backhaul enhancements.

In the case of macro cell coverage, a technology that can apply carrier aggregation between different base stations is proposed. Macro cells and small cells can work in different frequency bands. There are two types of architectures for applying carrier aggregation technologies between different base stations: an architecture based on separation of radio access network (RAN) for user plane data (RANSplit) and an architecture based on separation of core network (CN) (CNSplit). The architecture based on CN separation means that for the bearer established on the pico cell (pico), the data is directly sent to the Pico cell by the SGW of the core network, and the user plane data is not forwarded through the macro cell (macro).

In a small cell architecture, a UE can simultaneously transmit and receive data at two base stations, which is called dual-connectivity. Among them, only one base station is responsible for sending radio resource control (RRC) messages to the UE and interacting with the core network control plane entity MME. This base station is called the primary base station (MeNB), and the other base station is called the secondary base station (SeNB). The UE has a cell in the primary base station that is the primary cell (Pcell) of the UE, through which the RRC message is sent to the UE, and other cells are secondary cells (Scell). One cell in the Scell of the SeNB is the primary cell (pScell) of the SeNB. There is an uplink physical layer control channel on pScell, but not on other Scells. The cell group of the primary base station is called MCG, and the cell group of the secondary base station is called SCG. The configuration of the secondary cell group at the UE side is configured by the secondary base station, and the secondary base station sends the configuration of the UE to the primary base station through the RRC container, and the primary base station sends the configuration to the UE. The primary base station does not parse the RRC container. Or parse without changing the configuration inside the RRC container.

When the SGW or eNB has an error (SGWerrororeNBerror) or restarts, the bearer context will be lost. When the SGW or eNB receives a GPRS Tunneling Protocol (GTP-U) packet at the user level, but the SGW or eNB does not have the bearer context information of the GTP-U packet, the SGW or eNB will discard the packet and send a GTP error to the packet sender instruct.

When the MeNB receives a GTP error indication from the SGW from the S1-U channel (S1-UTunnel, user plane channel of the S1 interface), the MeNB needs to trigger an evolved radio access bearer (E-RAB) release process.

When the SeNB receives a GTP error indication from the SGW from the S1-U channel, the SeNB needs to delete the local S1-U channel.

When the SGW receives a GTP error indication from an eNB through the S1-U channel, the SGW will delete all tunnel endpoint identifiers (TEIDs) of the S1-U channel of the eNB, and the SGW will also send a downlink data notification message to the MME. After the MME receives the message, if the UE is in the connected state, the MME releases the S1 connection of the UE, and then executes the service request process triggered by the network.

Under the current dual-connection architecture with separate core networks, the SGW, MeNB, and SeNB still have the following problems after receiving a GTP error indication:

Problem 1: The MeNB may establish all UE bearers on the SeNB or the bearers on the MeNB are inactive. When an error occurs in the SGW and the SeNB sends a GTP-U packet to the SGW, if the SGW loses the context carried by the UE on the SeNB, the SGW will send a GTP error indication to the SeNB. After the SeNB receives the GTP error indication, it will release the local S1-U channel. The MeNB may not receive the GTP error indication sent by the SGW, and the MeNB cannot know that the release is caused by the SGW. The MeNB may also release the S1-U channel on the SeNB. The UE bearer is established on another SeNB or transferred to the MeNB. However, the UE bearer has no context in the SGW and should be released.

Question 2: When an error occurs at the SeNB, if the SGW sends a GTP-U packet to the SeNB, the SeNB will return a GTP error indication to the SGW. Since the SGW does not distinguish the SeNB or the MeNB, the SGW will release all the channel information of all bearers of the UE, and instruct the MME to release the connection of the UE. That is, an error of the SeNB will cause all the bearers on the MeNB to be released, thus causing the connection of the UE to be interrupted.

Contents of the invention

In order to solve the above-mentioned technical problems, this application proposes several methods and corresponding equipment for supporting UE bearer recovery, so as to solve the problem of UE bearer recovery under the dual-connection architecture with separate core network, and improve the reliability and stability of the network.

A method for supporting UE bearer recovery provided by this application includes:

When the secondary base station SeNB receives the user plane general packet radio service tunneling protocol GTP error indication sent by the serving gateway SGW, it sends an error indication to the primary base station MeNB;

The GTP error indication is used to instruct the MeNB to release or re-establish the corresponding UE bearer.

Preferably, the error indication includes one or more of the following indications: GTP error indication, S1-U channel release indication, SGW error indication, error user equipment UE bearer indication, request to release UE bearer indication or Indication of requesting to re-establish the UE bearer, identification and/or reason of the UE bearer corresponding to the S1-U channel receiving the GTP error indication.

A device provided by the present application includes: a first communication module and a first error processing module, wherein:

The first communication module is configured to receive a GTP error indication from the SGW;

The first error processing module is configured to generate an error indication when receiving a GTP error indication from the SGW, and send it to the MeNB through the first communication module.

A method for supporting UE bearer recovery provided by this application includes:

The MME acquires the eNB type or UE bearer type where the UE bearer is located;

The MME receives the error indication of the UE bearer sent by the SGW, and according to the eNB type or the UE bearer type where the UE bearer is located, when determining that the UE bearer with the error is the UE bearer on the SeNB, it instructs the MeNB to perform corresponding actions on the UE bearer on the SeNB. deal with;

Or the MME receives an indication that an error occurs in the UE bearer sent by the SGW, and the MME determines the UE bearer in which the error occurs.

Preferably, the corresponding processing includes: reestablishing, transferring or releasing a UE bearer on the SeNB or reestablishing, transferring or releasing an error UE bearer.

Preferably, the indication that the error occurs in the UE bearer includes one or more of the following indications: the IP address of the eNB where the UE bearer where the error occurs, identification information, eNB type, the UE bearer type, or the UE bearer where the error occurs Identification; wherein, the eNB type is SeNB or MeNB, and the UE bearer type is MCG bearer or SCG bearer.

A device provided by the present application includes: a second communication module and a second error handling module, wherein:

The second communication module is configured to obtain the eNB type or UE bearer type where the UE bearer is located, and receive an error indication of the UE bearer sent by the SGW;

The second error processing module is configured to, according to the eNB type or the UE bearer type where the UE bearer is located, when it is determined that the UE bearer with an error is a UE bearer on the SeNB, instruct the MeNB to use the second communication module for the UE bearer on the SeNB Deal with it accordingly.

A method for supporting UE bearer recovery provided by this application includes:

The SGW obtains the eNB type or UE bearer type where the UE bearer is located;

When the SGW determines that an error occurs in the SeNB or in the bearer of the UE, it performs one or more of the following operations:

The SGW does not release the S1-U channel on the MeNB;

The SGW does not release the S1-U channel on the SeNB;

SGW does not send downlink data notification to MME;

The SGW sends an indication that an error occurs in the UE bearer to the MME;

The SGW instructs the MME to reestablish, transfer or release the UE bearer on the SeNB;

The SGW sends the UE bearer identifier and/or reason corresponding to the S1-U channel receiving the GTP error indication to the MME;

The SGW instructs the MME to reestablish, transfer or release the UE bearer corresponding to the S1-U channel that received the GTP error indication.

Preferably, the SGW determining that the SeNB has an error includes: when the SGW receives a GTP error indication of the UE bearer, determining that the SeNB has an error according to the type of eNB where the UE bearer is SeNB or the UE bearer type is SCG bearer.

Preferably, the UE bearer error indication sent by the SGW to the MME includes one or more of the following indications: the IP address of the eNB where the error UE bearer is located, identification information, eNB type, UE bearer type, or error occurred UE bearer identifier; wherein, the eNB type is SeNB or MeNB, and the UE bearer type is MCG bearer or SCG bearer.

Preferably, before the SGW performs the one or more operations, it further includes:

The SGW sends an empty GTP-U packet to the MeNB of the UE carried by the UE where the error occurred, and if it does not receive the GTP error indication sent by the MeNB, it performs the one or more operations.

A device provided by the present application includes: a third communication module and a third error processing module, wherein:

The third communication module is configured to acquire the eNB type or UE bearer type where the UE bearer is located;

The third error processing module is configured to perform one or more of the following operations when it is determined that an error occurs in the SeNB or that an error occurs in the UE bearer:

Do not release the S1-U channel on the MeNB;

Do not release the S1-U channel on the SeNB;

Do not send downlink data notification to MME;

Send an indication that an error occurs in the UE bearer to the MME;

Instruct the MME to reestablish, transfer or release the UE bearer on the SeNB;

Send the UE bearer identifier and/or reason corresponding to the S1-U channel that received the GTP error indication to the MME;

Instruct the MME to reestablish, transfer or release the UE bearer corresponding to the S1-U channel that received the GTP error indication.

A method for supporting UE bearer recovery provided by this application includes:

The MeNB notifies the MME and/or the SGW of the eNB type or the UE bearer type of the UE bearer;

When the MeNB determines that an error has occurred in the SeNB, it re-establishes, transfers or deletes the UE bearer originally established on the SeNB; or when the MeNB determines that an error occurs in the UE bearer on the SeNB, it re-establishes, transfers or deletes the UE bearer in which the error occurred.

Preferably, the MeNB determining that an error occurs in the SeNB and determining that an error occurs in the UE bearer on the SeNB includes: the MeNB determines that an error occurs in the SeNB or determines that an error occurs in the UE bearer on the SeNB according to the instruction of the MME or according to the interaction between the MeNB and the SeNB; wherein:

The indication of the MME includes one or more of the following indications: the IP address of the eNB where the error UE bearer is located, identification information, eNB type, UE bearer type, or the UE bearer identity where the error occurs; where the eNB type is SeNB or MeNB, UE bearer type is MCG bearer or SCG bearer;

The interaction between MeNB and SeNB includes: MeNB receives the information of GTP-U packet sent by SeNB, MeNB confirms whether there is UE bearer context of the GTP-U packet, if there is UE bearer context, rebuilds or transfers UE bearer, if there is no UE bearer context, the MeNB informs the SeNB that the GTP-U packet has no bearer context.

Preferably, the re-establishing and transferring the UE bearer originally established on the SeNB includes: the MeNB re-establishes the UE bearer originally established on the SeNB on the recovered SeNB, or establishes it on another SeNB, or The MeNB transfers the bearer on the SeNB to the MeNB.

A device provided by the present application includes: a fourth communication module and a fourth error processing module, wherein:

The fourth communication module is configured to notify the MME and/or SGW of the eNB type or UE bearer type where the UE bearer is located;

The fourth error processing module is configured to re-establish, transfer or transfer the UE bearer that was originally established on the SeNB or the UE bearer that will cause an error when the MeNB determines that an error has occurred in the SeNB or that an error has occurred in the UE bearer on the SeNB. delete.

A method for supporting UE bearer recovery provided by this application includes:

The MeNB receives an error indication from the SeNB;

The MeNB releases or reestablishes the corresponding UE bearer.

Preferably, the error indication includes one or more of the following indications: GTP error indication, S1-U channel release indication, SGW error indication, error user equipment UE bearer indication, request to release UE bearer indication or Indication of requesting to re-establish the UE bearer, identification and/or reason of the UE bearer corresponding to the S1-U channel receiving the GTP error indication.

Preferably, the MeNB releasing or reestablishing the corresponding UE bearer includes:

The MeNB releases or re-establishes all bearers of the UE or only releases or re-establishes the UE bearers on the SeNB; or, the MeNB only releases or re-establishes the UE bearers corresponding to the S1-U channel where an error occurs.

Preferably, before the MeNB releases or reestablishes the corresponding UE bearer, it further includes:

The MeNB sends an empty GTP-U packet to the SGW. If no GTP error indication is received from the SGW, only the UE bearer on the SeNB is released or reestablished, and the UE bearer on the MeNB is not released or reestablished.

A device provided by the present application includes: a fifth communication module and a fifth error processing module, wherein:

The fifth communication module is configured to receive an error indication from the SeNB;

The fifth error handling module is configured to release or reestablish corresponding UE bearers.

A method for supporting UE bearer recovery provided by this application includes:

The eNB receives the GTP-U packet sent by the SGW;

When the eNB determines that there is no UE bearer context for the GTP-U packet, perform one or more of the following operations:

The eNB does not return a GTP error indication to the SGW;

After the eNB waits for the configured first time, it returns a GTP error indication to the SGW;

After the eNB restarts, within the configured second time, if the eNB receives a GTP-U packet and there is no corresponding UE bearer context, it will not return a GTP error indication to the SGW.

Preferably, the configured first time and second time are greater than MeNB discovering that the eNB has failed or restarted, and re-establish the UE bearer originally established on the eNB to the restarted eNB, and re-establish the eNB The time required to continue to serve as the SeNB of the UE, or greater than the time required to transfer the UE bearer originally established on the eNB to another SeNB or MeNB, or greater than the time required to delete the UE bearer, or It is longer than the time required for updating the transport layer address and TEID of the bearer to the SGW after the UE bearer is reestablished, deleted, or transferred, or longer than the time required for repairing the bearer.

A device provided by the present application includes: a sixth communication module and a sixth error processing module, wherein:

The sixth communication module is configured to receive the GTP-U packet sent by the SGW;

The sixth error processing module is configured to perform one or more of the following operations when determining that there is no UE bearer context of the GTP-U packet:

do not return a GTP error indication to the SGW;

After waiting for the configured first time, return a GTP error indication to the SGW;

After the device restarts, within the configured second time, if the eNB receives a GTP-U packet and there is no corresponding UE bearer context, it does not return a GTP error indication to the SGW;

Send the information of the GTP-U packet sent by the SGW to the MeNB.

A method for supporting UE bearer recovery provided by this application includes:

The SeNB receives the GTP-U packet sent by the SGW;

When the SeNB determines that there is no UE bearer context for the GTP-U packet, perform one or more of the following operations:

do not return a GTP error indication to the SGW;

The SeNB sends the information of the GTP-U packet sent by the SGW to the MeNB;

The SeN associates the UE with the bearer with the same address according to the source transport layer address or source IP address of the GTP-U packet, and if it is confirmed that the SeNB is the secondary base station for dual connectivity of the UE, the information of the GTP-U packet sent by the SGW is sent to MeNB for UE.

Preferably, the information of the GTP-U packet sent by the SGW includes packet header information or TEID of the GTP-U packet.

A device provided by the present application includes: a seventh communication module and a seventh error processing module, wherein:

The seventh communication module is configured to receive the GTP-U packet sent by the SGW;

The seventh error processing module is configured to perform one or more of the following operations when determining that there is no UE bearer context of the GTP-U packet:

do not return a GTP error indication to the SGW;

Send the information of the GTP-U packet sent by the SGW to the MeNB.

A method for supporting UE bearer recovery provided by this application includes:

The MME receives the identification of the wrong bearer and the cause of the error sent by the SGW, and the cause of the error is that it receives a GTP error indication from the eNB;

If the MME finds that the UE corresponding to the erroneous bearer is in the connected state, the MME releases the erroneous bearer.

Preferably, after the MME releases the erroneous bearer, it further includes:

The MME updates the transport layer address and TEID of the UE bearer to the SGW, which does not include the released bearer.

A device provided by the present application includes: an eighth communication module and an eighth error processing module, wherein:

The eighth communication module is used to receive the identification of the wrong bearer and the cause of the error sent by the SGW, and the cause of the error is to receive a GTP error indication from the eNB;

The eighth error handling module is configured to release the erroneous bearer when it is found that the UE corresponding to the erroneous bearer is in a connected state.

A method for supporting UE bearer recovery provided by this application includes:

The MME receives the identification of the wrong bearer and the cause of the error sent by the SGW, and the cause of the error is that it receives a GTP error indication from the eNB;

If the MME finds that the UE corresponding to the erroneous bearer is in the connected state, the MME sends information about the erroneous bearer to the eNB.

Preferably, the error bearer information includes one or more of the following: the identity of the error bearer, the F-TEID, transport layer address or TEID of the error bearer in the SGW, the error bearer in F-TEID, transport layer address or TEID of the base station, and UE identifier.

A device provided by the present application includes: a ninth communication module and a ninth error processing module, wherein:

The ninth communication module is configured to receive the identifier and error cause of the wrong bearer sent by the SGW, and the error reason is that a GTP error indication is received from the eNB;

The ninth error handling module is configured to send information about the bearer with the error to the eNB when it is found that the UE corresponding to the bearer with the error is in the connected state.

A method for supporting UE bearer recovery provided by this application includes:

The eNB receives the error bearer information sent by the MME;

If the eNB is the MeNB of the UE, the MeNB performs the following operations:

If the bearer information is an SCG bearer, the MeNB performs any of the following operations: 1) resend the context of the SCG bearer to the SeNB for the SeNB to perform bearer re-establishment; A SeNB establishes an SCG bearer; 3) switches the SCG bearer back to the MeNB; 4) releases the SCG bearer, and after performing the operation, the MeNB instructs the MME to repair the wrong bearer;

If the MeNB finds that the received bearer information does not exist in the bearer context of the UE or the MeNB finds that the received bearer information is inconsistent with the saved bearer context of the UE, then the MeNB ignores the received bearer information with errors and performs The UE context is released.

Preferably, the instruction indicating recovery of the wrong bearer further includes the transport layer address and TEID of the UE bearer on the base station side.

A device provided by the present application includes: a tenth communication module and a tenth error processing module, wherein:

The tenth communication module is configured to receive the information of the wrong bearer sent by the MME;

The tenth error processing module is configured to perform the following operations when the device is the MeNB of the UE:

If the information of the bearer is an SCG bearer, perform any one of the following operations: 1) resend the context of the SCG bearer to the SeNB for the SeNB to perform bearer reestablishment; 2) reselect a SeNB for the UE to establish SCG bearer; 3) switch the SCG bearer back to the MeNB; 4) release the SCG bearer, and after performing the operation, instruct the MME to repair the wrong bearer;

If it is found that the received bearer information does not exist in the UE context or the received bearer information is found to be inconsistent with the saved UE context, ignore the received error bearer information and release the UE context.

A method for supporting UE bearer recovery provided by this application includes:

MeNB finds that SeNB restarts;

MeNB sends SCG bearer information to SeNB.

Preferably, the method further comprises:

The MeNB indicates to the SeNB a valid time within which the SCG bearer context is valid, and the valid time is greater than the time required for the MeNB to repair the SCG bearer, or greater than the time required for re-establishing, transferring or deleting the SCG bearer, or greater than the time required to update the transport layer address and TEID of the bearer to the SGW after the SCG bearer is rebuilt, deleted or transferred;

The MeNB reestablishes the SCG bearer to the original SeNB, or transfers it to another SeNB or MeNB, or deletes it, and updates the bearer transport layer address and TEID to the SGW.

Preferably, the SCG bearer information includes one or more of the following: bearer identifier, F-TEID carried on the SGW, transport layer address, TEID, F-TEID carried on the base station in error, transport layer address, TEID, UE identifier.

A device provided by the present application includes: an eleventh communication module and an eleventh error processing module, wherein:

The eleventh communication module is configured to discover that the SeNB is restarted;

The eleventh error handling module is configured to send SCG bearer information to the SeNB.

A method for supporting UE bearer recovery provided by this application includes:

The SeNB receives the SCG bearer context from the MeNB;

The SeNB saves the SCG bearer context. When receiving a GTP-U packet from the SGW, if the SCG bearer context indicated by the MeNB includes the bearer context of the GTP-U packet, the SeNB does not return a GTP error indication to the SGW.

Preferably, the method further comprises:

If the SeNB receives a valid time indication from the MeNB, after the valid time expires, the SeNB deletes the SCG bearer context sent by the MeNB;

Or, a valid time is configured on the SeNB, and when the valid time expires, the SeNB deletes the context carried by the SCG sent by the MeNB.

A device provided by the present application includes: a twelfth communication module and a twelfth error processing module, wherein:

The twelfth communication module is configured to receive an SCG bearer context from a MeNB;

The twelfth error handling module is configured to save the SCG bearer context, and when receiving the GTP-U packet from the SGW, if the SCG bearer context indicated by the MeNB includes the bearer context of the GTP-U packet, it does not send The SGW returns a GTP error indication.

It can be seen from the above technical solutions that no matter the SeNB or the SGW loses the context of the UE bearer, the UE bearer can be reasonably re-established, transferred or deleted. The method provided by the present invention is suitable for solving the problem of UE bearer recovery under the dual-connection architecture with separate core networks, greatly improves the reliability and stability of the network, and improves the user's network experience. At the same time, the solution of the present invention is very flexible and can meet the requirements of public communication services.

Description of drawings

Figure 1 is a system architecture diagram of SAE;

FIG. 2 is a schematic flowchart of Method 1 for supporting UE bearer recovery in the present invention;

FIG. 3 is a schematic flowchart of a second method for supporting UE bearer recovery in the present invention;

FIG. 4 is a schematic flowchart of a third method for supporting UE bearer recovery in the present invention;

FIG. 5 is a schematic flowchart of a fourth method for supporting UE bearer recovery in the present invention;

FIG. 6 is a schematic diagram of Embodiment 1 of a method for supporting UE bearer recovery in the present invention;

FIG. 7 is a schematic diagram of Embodiment 2 of a method for supporting UE bearer recovery in the present invention;

FIG. 8 is a schematic diagram of Embodiment 3 of a method for supporting UE bearer recovery in the present invention;

FIG. 9 is a schematic diagram of Embodiment 4 of a method for supporting UE bearer recovery in the present invention;

FIG. 10 is a schematic diagram of Embodiment 5 of a method for supporting UE bearer recovery according to the present invention;

FIG. 11 is a schematic diagram of Embodiment 6 of a method for supporting UE bearer recovery in the present invention;

FIG. 12 is a schematic diagram of Embodiment 7 of a method for supporting UE bearer recovery in the present invention;

FIG. 13 is a schematic diagram of Embodiment 8 of a method for supporting UE bearer recovery in the present invention;

FIG. 14 is a schematic diagram of Embodiment 9 of a method for supporting UE bearer recovery in the present invention;

FIG. 15 is a schematic diagram of Embodiment 10 of a method for supporting UE bearer recovery in the present invention;

FIG. 16 is a schematic diagram of Embodiment 11 of a method for supporting UE bearer recovery in the present invention;

Fig. 17 is a schematic diagram of the composition and structure of the device 1 of the present application;

Figure 18 is a schematic diagram of the composition and structure of the second device of the present application;

Fig. 19 is a schematic diagram of the composition and structure of the device three of the present application;

Fig. 20 is a schematic diagram of the composition and structure of the device four of the present application;

Fig. 21 is a schematic diagram of the composition and structure of the fifth device of the present application;

Fig. 22 is a schematic diagram of the composition and structure of the device six of the present application;

FIG. 23 is a schematic diagram of Embodiment 12 of a method for supporting UE bearer recovery in the present invention;

FIG. 24 is a schematic diagram of Embodiment 13 of a method for supporting UE bearer recovery in the present invention;

FIG. 25 is a schematic diagram of Embodiment 14 of a method for supporting UE bearer recovery in the present invention;

FIG. 26 is a schematic diagram of Embodiment 15 of a method for supporting UE bearer recovery in the present invention;

FIG. 27 is a schematic diagram of Embodiment 16 of a method for supporting UE bearer recovery in the present invention;

Fig. 28 is a schematic diagram of the composition and structure of the device seven of the present application;

Figure 29 is a schematic diagram of the composition and structure of the eighth device of the present application

Fig. 30 is a schematic diagram of the composition and structure of equipment 9 of the present application;

Figure 31 is a schematic diagram of the composition and structure of the device ten of the present application

Fig. 32 is a schematic diagram of the composition and structure of the equipment eleven of the present application;

Fig. 33 is a schematic diagram of the composition and structure of the device 12 of the present application.

detailed description

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and examples.

When an error occurs in the SGW or the SeNB, the SGW, the MME, the SeNB and the MeNB need to perform different processes respectively to support the recovery of the bearer of the UE. The following describes the UE bearer processing method when an error occurs in the SGW in this application, the processing method for the UE bearer by the MME when an error occurs in the SeNB, the processing method for the UE bearer by the SGW when an error occurs in the SeNB, and the MeNB when an error occurs in the SeNB. The processing method for UE bearer.

Fig. 2 is a schematic flowchart of method 1 for supporting UE bearer recovery in the present invention. This method is a method for processing UE bearer by MeNB when an error occurs in SGW or an error occurs in the S1-U channel between SeNB and SGW. The method includes the following steps:

Step 201: After receiving the GTP error indication sent by the SGW, the SeNB sends an error indication to the MeNB.

The error indication may be one or more of the following indications: GTP error indication, S1-U channel release indication, SGW error indication, error UE bearer indication, indication of request to release UE bearer or indication of request to reestablish UE bearer .

The error indication may also be the information of the UE bearer corresponding to the S1-U channel that received the GTP error indication, and the information of the UE bearer may be the identity of the UE bearer and/or the cause of the error. The error indication may be used to notify the MeNBUE that the S1-U channel bearer is locally deleted by the SeNB or request the MeNB to re-establish or delete the indicated UE bearer. Before that, the SeNB can delete the local S1-U channel that received the GTP error indication.

In this case, the SeNB can cache the uplink data of the UE.

Step 202: The MeNB releases or re-establishes the UE bearer according to the error indication sent by the SeNB.

The MeNB may release or re-establish all bearers of the UE or only release or re-establish the UE bearers on the SeNB.

Or, when the MeNB re-establishes the bearers of the UE, it requests the MME to re-establish all the bearers of the UE. The MME may request to create a UE bearer context to the SGW that has recovered from the failure (referred to as "failure recovery SGW") or select a new SGW.

Alternatively, the MeNB only releases or reestablishes the UE bearer indicated by the UE bearer information sent by the SeNB, and the UE bearer information is the UE bearer information corresponding to the S1-U channel that received the GTP error indication.

Before this, the MeNB can send an empty GTP-U packet (for example: Dummy packet) to the SGW, and confirm that the SGW has failed or that the SGW has lost the UE bearer established on the MeNB according to whether it receives the GTP error indication sent by the SGW. context. If the GTP error indication sent by the SGW is received, it indicates that the SGW has failed or the SGW has lost the UE bearer context established on the MeNB. If the UE bearer context on the MeNB is not lost, the UE bearer on the MeNB may not be released or reestablished, but only the UE bearer on the SeNB may be released or reestablished.

Fig. 3 is a schematic flow chart of the second method for supporting UE bearer recovery in the present invention. This method is a method for processing the UE bearer by the MME when an error occurs in the SeNB or an error occurs in the S1-U channel between the SeNB and the SGW. The method includes two methods for the MME to process the bearer of the UE, which are step 301 to step 302 and step 302 respectively. The method includes the following steps:

Step 301: The MME obtains the eNB type or UE bearer type of the UE bearer sent by the MeNB.

The eNB type can be MeNB or SeNB. The UE bearer type can be MCG bearer or SCG bearer. The MME stores the eNB type or UE bearer type in the UE bearer context.

Step 302: The MME receives the indication that the UE bearer has an error sent by the SGW, and the MME determines that the UE bearer on the SeNB has an error, and instructs the MeNB to reestablish, transfer or release the UE bearer on the SeNB; or the MME determines that a certain UE bearer has an error, Instruct the MeNB to reestablish, transfer or release the specified UE bearer.

The indication of the UE bearer error may be the IP address of the eNB where the error UE bearer is located, identification information, eNB type, UE bearer type, or the identifier of the UE bearer error.

The error UE bearer ID is the UE bearer ID corresponding to the S1-U channel that received the GTP error indication. For the wrong UE bearer identifier, 1) the MME can confirm the eNB type or UE bearer type where the UE bearer is located according to the context of the corresponding bearer. Once it is confirmed that only the UE bearer on the SeNB has an error, the MME instructs the MeNB to reestablish, transfer or release the UE bearer on the SeNB. Or 2) the MME instructs the MeNB to reestablish, transfer or release the specified erroneous UE bearer.

Fig. 4 is a schematic flow chart of the third method for supporting UE bearer recovery in the present invention. This method is a method for processing the UE bearer by the SGW when an error occurs in the SeNB or an error occurs in the S1-U channel between the SeNB and the SGW. The method includes two methods for the SGW to process the bearer of the UE, which are step 401 to step 402 and step 402 respectively. The method includes the following steps:

Step 401: The SGW acquires the eNB type or UE bearer type where the UE bearer is located.

The eNB type can be MeNB or SeNB. The UE bearer type can be MCG bearer or SCG bearer.

Step 402: When the SGW determines that the SeNB has an error or the UE bearer has an error, the SGW can perform one or more of the following operations:

1) The SGW may not release the S1-U channel on the MeNB.

2) The SGW may not release the S1-U channel on the SeNB.

3) The SGW may not send a downlink data notification to the MME.

4) The SGW may send an indication of UE bearer error to the MME, where the indication may be the IP address, identification information, eNB type, UE bearer type or the identity of the UE bearer where the error UE bearer is located. At this time, the IP address or identification information of the eNB is the IP address or identification information of the SeNB, and the eNB type is the SeNB.

5) The SGW can instruct the MME to reestablish, transfer or release the UE bearer on the SeNB.

6) The SGW may send the UE bearer identifier and/or reason corresponding to the S1-U channel receiving the GTP error indication to the MME.

7) The SGW may instruct the MME to reestablish, transfer or release the UE bearer corresponding to the S1-U channel that received the GTP error indication.

The SGW can determine that the SeNB has an error based on the following information: when the SGW receives the GTP error indication of the UE bearer, it determines that the SeNB has an error based on the eNB type of the UE bearer as the SeNB, or determines that the SeNB has an error based on the UE bearer type as the SCG bearer.

The SGW can determine the UE bearer where the error occurs according to the following information: the UE bearer corresponding to the S1-U channel indicated by the received GTP error.

Before performing the above operations, the SGW can send an empty GTP-U packet (for example: Dummy packet) to the MeNB of the UE carried by the UE where the error occurred, and confirm whether the MeNB is faulty or not according to whether it receives the GTP error indication sent by the MeNB. Check whether the MeNB has lost the context carried by the UE. If the MeNB does not fail or loses the context carried by the UE, perform the above operation again.

FIG. 5 is a schematic flowchart of the fourth method for supporting UE bearer recovery in the present invention. This method is a method for processing the UE bearer by the MeNB when an error occurs in the SeNB or an error occurs in the S1-U channel between the SeNB and the SGW. The method includes two methods for the MeNB to handle the bearer of the UE, which are step 501 to step 502 and step 502 respectively. The method includes the following steps:

In step 501, the MeNB informs the MME or the SGW of the eNB type or UE bearer type where the UE bearer is located.

Step 502: After the MeNB learns that an error occurs in the SeNB or an error occurs in the UE bearer, it reestablishes, transfers or deletes the UE bearer originally established on the SeNB or the UE bearer in which the error occurred. The wrong UE bearer means that the eNB receives the GTP-U packet sent by the SGW, and the GTP-U packet has no bearer context on the eNB.

The MeNB can learn that an error occurs in the SeNB or that an error occurs in the UE bearer on the SeNB according to the instruction of the MME or the interaction with the SeNB. The indication of the MME may be the IP address, identification information, eNB type, UE bearer type or the identity of the UE bearer where the error occurred UE bearer is located. The interaction between the MeNB and the SeNB refers to: the SeNB receives the GTP-U packet sent by the SGW, and when the GTP-U packet has no bearer context on the SeNB, the SeNB sends the GTP-U packet information to the MeNB. The information of the GTP-U packet may be packet header information or TEID in the GTP-U. The MeNB confirms whether there is a UE bearer context for the GTP-U packet, and if there is a UE bearer context, rebuilds or transfers the UE bearer. If there is no UE bearer context, the MeNB informs the SeNB that the GTP-U packet has no bearer context.

Reestablishment or transfer refers to: 1) MeNB re-establishes the UE bearer originally established on the SeNB on the recovered SeNB, or establishes it on another SeNB, or the MeNB transfers the UE bearer on the SeNB to the MeNB. 2) Alternatively, the MeNB only re-establishes or transfers the UE bearer corresponding to the S1-U channel where the error occurs.

Figures 3 to 5 above describe how the MME, SGW and MeNB handle UE bearers when an error occurs in the SeNB or the S1-U channel between the SeNB and the SGW. The following describes how the SeNB handles when an error occurs in the SeNB. Since SeNB and MeNB are relative to UE, SeNB and MeNB are both eNBs in essence; and when an error occurs in SeNB, it will not be able to distinguish whether it is SeNB or MeNB. Therefore, the following description is described from the perspective of eNB. Specifically include the following steps:

Step 1, the eNB receives the GTP-U packet sent by the SGW.

Step 2, when the eNB confirms that there is no UE bearer context for the GTP-U packet, the eNB can perform one or more of the following operations:

1) The eNB does not return a GTP error indication to the SGW.

2) The eNB returns a GTP error indication to the SGW after waiting for a configured period of time. The configured time is enough for the MeNB to discover that the eNB has failed or restarted, and re-establish the UE bearer that was originally established on the eNB to the restarted eNB, and continue to use the eNB as the SeNB of the UE, or it is enough to restore the bearer that was originally established on the eNB to the restarted eNB. The UE bearer on the eNB is transferred to another SeNB or MeNB, or it is enough to delete the UE bearer, or it is enough to update the transport layer address and TEID of the bearer to the SGW after the re-establishment, deletion, and transfer of the UE bearer, or it is enough to repair The bearer. The aforementioned time sufficient to perform a certain operation refers to: greater than the time required to perform a certain operation.

3) After the eNB restarts, within a configured period of time, if the eNB receives a GTP-U packet and there is no UE bearer context, it will not return a GTP error indication to the SGW. The configured time is enough for the MeNB to discover that the eNB has failed or restarted, and re-establish the UE bearer that was originally established on the eNB to the restarted eNB, continue to use the eNB as the SeNB of the UE, or restore the UE bearer that was originally established on the eNB to the restarted eNB. The UE bearer on the eNB is transferred to another SeNB or MeNB, or the UE bearer is deleted. The aforementioned time sufficient to perform a certain operation refers to: greater than the time required to perform a certain operation.

Another processing method of the SeNB when an error occurs on the S1-U channel between the SeNB and the SGW is described below.

Specifically include the following steps:

Step 1, the SeNB receives the GTP-U packet sent by the SGW.

Step 2, when the SeNB confirms that there is no UE bearer context for the GTP-U packet, the SGW can perform one or more of the following operations:

1) The SeNB does not return a GTP error indication to the SGW.

2) The SeNB sends the received GTP-U packet information to the MeNB. The information of the GTP-U packet may be packet header information or TEID in the GTP-U. If the MeNB has the UE bearer context information corresponding to the GTP-U packet, the MeNB re-establishes or transfers the corresponding UE bearer to the SeNB, and the SeNB does not return a GTP error indication to the SGW. If the MeNB does not have the UE bearer context information corresponding to the GTP-U packet, the MeNB informs the SeNB of the fact that there is no bearer context, and the SeNB may return a GTP error indication to the SGW.

3) The SeNB can also associate the bearer UE with the same address according to the source transport layer address or source IP address of the GTP-U packet. If it is confirmed that the SeNB is the secondary base station for dual connectivity of the UE, the packet header information of the above GTP-U packet sent to the MeNB of the UE.

Another processing method of the MME when an error occurs on the S1-U channel between the SeNB and the SGW is described below.

Specifically include the following steps:

In step 1, the MME receives the identifier and cause of the errored bearer sent by the SGW. The reason for the error is that a GTP error indication is received from the eNB.

In step 2, the MME finds that the UE corresponding to the bearer with the error is in the connected state, and the MME can release the bearer with the error. The MME can further update the transport layer address and TEID of the UE bearer to the SGW, and the released bearer is not included in the update.

The following describes another processing method of the MME and the SeNB when an error occurs in the S1-U channel between the SeNB and the SGW. Specifically include the following steps:

In step 1, the MME receives the identification of the bearer with the error and the cause of the error sent by the SGW, and the cause of the error is that it receives a GTP error indication from the eNB. When the MME finds that the UE corresponding to the erroneous bearer is in the connected state, the MME may send information about the erroneous bearer to the eNB of the UE. The information of the wrong bearer can include one or more of the following: the identification of the wrong bearer, the F-TEID, transport layer address, and TEID of the wrong bearer in the SGW, and the F-TEID of the wrong bearer in the base station , transport layer address, TEID, UE identifier.

Step 2. The eNB receives information about the wrong bearer sent by the MME. If the eNB is the MeNB of the UE, the MeNB can perform the following operations:

1) The MeNB finds that the indicated bearer information is an SCG bearer, then the MeNB can 1) resend the context of the SCG bearer to the SeNB, and the SeNB performs bearer reconstruction based on it; 2) or re-select a SeNB for the UE to establish an SCG bearer; 3 ) switching the SCG bearer back to the MeNB; 4) or releasing the SCG bearer. After completion, the MeNB instructs the MME to repair the wrong bearer. The indication may also include the address of the transport layer carried by the UE on the RAN side, TEID and other information.

2) When the MeNB finds that there is no context for the received bearer, the eNB can ignore the received information that the wrong bearer has occurred, release the UE context, and return a UE context release response message to the MME.

3) If the MeNB finds that the received bearer information is inconsistent with the saved context, the eNB can ignore the received information that the wrong bearer has occurred, release the UE context, and return a UE context release response message to the MME.

Another processing method of the MeNB and the SeNB when an error occurs in the S1-U channel between the SeNB and the SGW is described below. Specifically include the following steps:

In step 1, the MeNB finds that the SeNB is restarted, and sends SCG bearer information to the SeNB.

After finding that the SeNB is restarted, the MeNB may not delete the context or process related to the SeNB at this time. The MeNB can discover that the SeNB is restarted according to the restart request sent by the SeNB. The SCG bearer information may include one or more of the following: bearer identifier, F-TEID, transport layer address, and TEID carried in the SGW, F-TEID, transport layer address, TEID carried in the base station in error, and UE identity.

The MeNB may also indicate a valid time to the SeNB, indicating that the SCG bearer context is valid within the valid time. The length of the effective time is greater than the time required for MeNB to repair the SCG bearer, or greater than the time required for re-establishment, transfer or deletion of the SCG bearer, or greater than the time required for updating the bearer transport layer address, Time required from TEID to SGW. Or, after the MeNB restores the SCG bearer, or rebuilds, transfers, or deletes the SCG bearer, or, after rebuilding, deleting, or transferring the SCG bearer, and updates the transport layer address and TEID of the bearer to the SGW, the MeNB sends a message to the SeNB Indicates to inform the SeNB that the context related to the SeNB will be deleted.

At the same time, the MeNB can re-establish the SCG bearer to the original SeNB, or transfer it to another SeNB or MeNB, or delete it, and update the bearer transport layer address and TEID to the SGW.

In step 2, the SeNB performs corresponding operations according to the SCG bearer information sent by the MeNB.

The SeNB saves the SCG bearer context. When receiving the GTP-U packet from the SGW, if the SCG bearer context indicated by the MeNB includes the received GTP-U bearer context, the SeNB will not return a GTP error indication to the SGW. If the MeNB also indicates a valid time value, when the time value expires, the SeNB deletes the context carried by the SCG sent by the MeNB. Or, a valid time is configured on the SeNB, and when the valid time expires, the SeNB deletes the context carried by the SCG sent by the MeNB.

The technical solution of the present application will be further described in detail through several preferred embodiments below.

Embodiment one:

FIG. 6 is a schematic diagram of Embodiment 1 of a method for supporting UE bearer recovery according to the present invention. The method includes the following steps:

In step 601, the SeNB sends a GTP-U packet to the SGW.

Step 602, when the SGW receives the GTP-U packet sent by the SeNB, but the SGW does not have the bearer context information of the GTP-U packet, the SGW sends a GTP error indication to the SeNB.

Step 603 , using the method described in step 201 , the SeNB sends to the MeNB a GTP error indication indicating that the SGW has an error or sends UE bearer information corresponding to the S1-U channel that has received the GTP error indication. Specifically, the SeNB may send the indication to the MeNB through a message such as a SeNB deletion request message or a SeNB modification request message.

Step 604 , the MeNB requests the MME to release the UE bearer according to the instruction of the SeNB or requests the MME to release the specified UE bearer according to or the UE bearer information. Before this, the MeNB can send an empty GTP-U packet (for example: Dummy packet) to the SGW, and confirm that the SGW is faulty or that the SGW has lost the UE bearer context established on the MeNB according to whether it receives a GTP error indication sent by the SGW . If the bearer context on the MeNB is also lost, the UE bearer on the MeNB also needs to be released.

The MeNB may indicate to the MME the reason for requesting to release the bearer of the UE.

In step 605, the MME sends an E-RAB release command or a UE context release request to the MeNB.

Embodiment two:

FIG. 7 is a schematic diagram of Embodiment 2 of a method for supporting UE bearer recovery according to the present invention. This embodiment includes two situations that cause the MeNB to request the MME to reestablish the bearer of the UE, as shown in steps 701 to 703 and steps 704 to 705 respectively. The method includes the following steps:

Situation 1: Steps 701 to 703 are the same as steps 601 to 603, and will not be repeated here.

Case 2:

In step 704, the MeNB sends a GTP-U packet to the SGW.

Step 705, when the SGW receives the GTP-U packet sent by the MeNB, but the SGW does not have the bearer context information of the GTP-U packet, the SGW sends a GTP error indication to the MeNB.

Step 706: After receiving the GTP error indication sent by the SeNB or the GTP error indication sent by the SGW, the MeNB requests the MME to reestablish the UE bearer. Or the MeNB receives the UE bearer information corresponding to the S1-U channel sent by the SeNB and receives the GTP error indication, and requests the MME to re-establish the specified UE bearer, and the re-establishment request may be included in the E-RAB modification indication message.

In step 707, the MME may request to create a UE bearer context to the failure recovery SGW or a reselected SGW, and the MME sends a session creation request to the corresponding SGW. Or the MME requests the SGW to create the UE bearer specified by the MeNB, and the MME requests the SGW to create the bearer.

In step 708, the MME receives a session creation response or a bearer creation response from the SGW.

In step 709, the MME returns an E-RAB re-establishment response to the MeNB, and the response may be included in the E-RAB modification request response message.

Embodiment three:

FIG. 8 is a schematic diagram of Embodiment 3 of a method for supporting UE bearer recovery according to the present invention. This embodiment is a process of notifying the core network of the eNB type or UE bearer type where the UE bearer is located when the UE bearer is established from the idle state to the connected state. The method includes the following steps:

In step 801, the UE connection is established, and the MME sends an initial context establishment request to the MeNB, indicating the UE bearer to be established.

In step 802, the MeNB establishes the UE bearer on the MeNB or SeNB, and sends an initial context establishment response to the MME, indicating the eNB type or UE bearer type where the UE bearer is located. The eNB type can be MeNB or SeNB. The UE bearer type can be MCG bearer or SCG bearer.

In step 803, the MME sends a modify bearer request to the SGW, indicating the eNB type or UE bearer type where the bearer is located. The eNB type can be MeNB or SeNB. The UE bearer type can be MCG bearer or SCG bearer.

In step 804, the SGW saves the eNB type or UE bearer type where the UE bearer is located in the bearer context, and returns a bearer modification response to the MeNB.

Embodiment four:

FIG. 9 is a schematic diagram of Embodiment 4 of a method for supporting UE bearer recovery according to the present invention. This embodiment is a procedure in which the target MeNB notifies the core network of the eNB type or UE bearer type where the UE bearer is located during the X2 handover. The method includes the following steps:

Step 901, the source MeNB sends a handover request to the target MeNB.

Step 902, the target MeNB sends a handover request confirmation to the source MeNB. The source MeNB instructs the UE to switch to the target MeNB.

Step 903, after the UE accesses the target MeNB, the target MeNB sends a path switching request to the MME, in which the request indicates the eNB type and UE bearer type where the UE bearer is located. The eNB type can be MeNB or SeNB. The UE bearer type can be MCG bearer or SCG bearer.

Steps 904 to 905 are consistent with steps 803 to 804, and will not be repeated here.

In step 906, the MME sends a path switching request confirmation to the MeNB.

Embodiment five:

FIG. 10 is a schematic diagram of Embodiment 5 of a method for supporting UE bearer recovery according to the present invention. This embodiment is a procedure in which the target MeNB notifies the core network of the eNB type or UE bearer type where the UE bearer is located during the S1 handover. The method includes the following steps:

Step 1001, the source MeNB sends a handover request to the MME.

Step 1002, the MME sends a handover request to the target MeNB.

Step 1003, the target MeNB returns a handover request confirmation to the MME.

Step 1004, the MME sends a handover command to the source MeNB. The source MeNB instructs the UE to switch to the target MeNB.

Step 1005, after the UE accesses the target MeNB, the target MeNB sends a handover notification to the MME, in which the handover notification indicates the eNB type or UE bearer type where the UE bearer is located. The eNB type can be MeNB or SeNB. The UE bearer type can be MCG bearer or SCG bearer.

Steps 1006 to 1007 are consistent with steps 803 to 804, and will not be repeated here.

Embodiment six:

FIG. 11 is a schematic diagram of Embodiment 6 of a method for supporting UE bearer recovery in the present invention. In this embodiment, when the MeNB controls the transfer of the UE bearer between the MeNB and the SeNB, the MeNB notifies the core network of the eNB type or UE bearer type where the UE bearer is located. The method includes the following steps:

Step 1101, the MeNB sends a SeNB addition request or a SeNB modification request to the SeNB, and transfers the UE bearer on the MeNB to the SeNB; or the MeNB sends a SeNB deletion request or a SeNB modification request to the SeNB, and transfers the UE bearer on the SeNB to the MeNB.

Step 1102, corresponding to the request sent by the MeNB, the SeNB returns a SeNB addition response, SeNB modification response or SeNB deletion response to the MeNB.

In step 1103, the MeNB sends an E-RAB modification instruction to the MME, indicating the eNB type or UE bearer type where the UE bearer is located. The eNB type can be MeNB or SeNB. The UE bearer type can be MCG bearer or SCG bearer.

Steps 1004 to 1005 are consistent with steps 803 to 804, and will not be repeated here.

Embodiment seven:

FIG. 12 is a schematic diagram of Embodiment 7 of a method for supporting UE bearer recovery according to the present invention. This embodiment is a process of UE bearer recovery after the SeNB loses the UE bearer context. The method includes the following steps:

In step 1201, the SGW sends a GTP-U packet to an S1-U channel carried by a certain UE.

Step 1202, when the SeNB receives the GTP-U packet sent by the SGW, but the SeNB does not have the bearer context information of the GTP-U packet, the SeNB sends a GTP error indication to the SGW.

Step 1203, after receiving the GTP error indication, the SGW knows that the eNB type of the UE bearer where the error occurs is only SeNB or the UE bearer type is only SCG, then the SGW continues to reserve the S1-U channel of the MeNB and does not send a downlink data notification to the MME After the MeNB re-establishes or transfers the UE bearer on the SeNB, the MeNB sends the UE bearer’s new transport layer address and TEID to the SGW through the MME or after the MeNB deletes the UE bearer on the SeNB, the MeNB requests the SGW to delete the relevant UE bearer through the MME . Before this, the SGW can send an empty GTP-U packet (for example: Dummy packet) to the MeNB of the UE carried by the UE where the error occurred, and confirm whether the MeNB is faulty or whether the MeNB is faulty according to whether it receives the GTP error indication sent by the MeNB. The context carried by the UE is lost. If it is confirmed that the MeNB is not faulty or the context carried by the UE is not lost, then perform the above operations.

In step 1204, the MeNB learns that the SeNB has failed and restarted, and re-establishes the UE bearer originally established on the SeNB on the recovered SeNB, or establishes it on another SeNB, or the MeNB transfers the UE bearer on the SeNB to the MeNB.

In step 1205, the MeNB sends an E-RAB modification instruction to the MME, instructing the UE to carry a new transport layer address and GTPTEID.

In step 1206, the MME sends a modify bearer instruction to the SGW, instructing the UE to bear the new transport layer address and GTPTEID.

Step 1207, the SGW sends a modify bearer response to the MME.

Embodiment eight:

FIG. 13 is a schematic diagram of Embodiment 8 of a method for supporting UE bearer recovery in the present invention. The method includes the following steps:

Steps 1301 to 1302 are the same as steps 1201 to 1202, and will not be repeated here.

Step 1303, after receiving the GTP error indication, the SGW learns that the eNB type of the bearer where the error occurs is only SeNB or the UE bearer type is only SCG, then the SGW continues to reserve the S1-U channel of the MeNB and does not send a downlink data notification to the MME, Instead, send a bearer re-establishment, transfer or deletion request to the MME, requesting re-establishment, transfer or deletion of the UE bearer on the SeNB where the error occurred, and the request may include the IP address, identification information, eNB type, UE bearer type, or UE bearer ID where an error occurred. The request may be contained in a modify bearer request message, a bearer delete request message or a downlink data notification.

Before this, the SGW can send an empty GTP-U packet to the MeNB of the UE with the wrong bearer, and confirm whether the MeNB is faulty or whether the MeNB also loses the context of the UE bearer according to whether it receives the GTP error indication sent by the MeNB. If the MeNB is not faulty or the context carried by the UE is not lost, perform the above operation again.

The SGW can also continue to reserve the S1-U channel of the SeNB, waiting for the modification of the MeNB.

Step 1304, the MME sends a bearer re-establishment, transfer or deletion request to the MeNB, requesting re-establishment, transfer or deletion of the UE bearer on the SeNB where the error occurred, which may include the IP address or identification information or eNB type or UE bearer of the SeNB where the error UE bearer is located. The bearer type or the UE bearer ID where the error occurred. Said request may be included in an E-RAB modification request or deletion message.

Step 1305: After receiving the bearer reestablishment or transfer request, the MeNB re-establishes the UE bearer originally established on the SeNB on the recovered SeNB, or establishes it on another SeNB, or the MeNB transfers the UE bearer on the SeNB to the MeNB .

After receiving the bearer deletion request, the MeNB identifies the UE bearer on the SeNB, and deletes the original UE bearer established on the SeNB.

After the MeNB re-establishes, transfers or deletes the UE bearer, it can further delete the SeNB where the error occurred.

Step 1306, the MeNB sends a bearer reestablishment or transfer response to the MME, instructing the UE to bear the new transport layer address and GTPTEID. The response may be contained in an E-RAB modification indication message.

The MeNB sends a bearer deletion response to the MME. The response may be contained in an E-RAB deletion response.

Step 1307, the MeNB sends a bearer reestablishment or transfer response to the MME, instructing the UE to bear the new transport layer address and GTPTEID. The response may be included in a Modify Bearer Request message.

Or, the MeNB sends a bearer deletion response to the MME. The response may be contained in a delete bearer response message.

Embodiment nine:

FIG. 14 is a schematic diagram of Embodiment 9 of a method for supporting UE bearer recovery according to the present invention. The method includes the following steps:

Steps 1401 to 1402 are the same as steps 1201 to 1202, and will not be repeated here.

Step 1403, after receiving the GTP error indication, the SGW learns that the eNB type of the bearer where the error occurs is SeNB or the UE bearer type is SCG, then the SGW continues to reserve the S1-U channel of the MeNB. The SGW sends a downlink data notification to the MME, indicating the wrong UE bearer.

SGW can also continue to reserve the S1-U channel of SeNB, waiting for the modification of MeNB

Before this, the SGW can send an empty GTP-U packet to the MeNB of the UE with the wrong bearer, and confirm whether the MeNB is faulty or whether the MeNB also loses the context of the UE bearer according to whether it receives the GTP error indication sent by the MeNB. If there is no problem with the MeNB, perform the above operations.

Step 1404, after the MME receives the downlink data notification, it recognizes that the UE bearer with the error only belongs to the SeNB, then the MME sends a bearer re-establishment, transfer or deletion request to the MeNB, requesting re-establishment, transfer or deletion of the UE bearer on the SeNB with the error. Contains the SeNB's IP address, identification information, eNB type, UE bearer type, or UE bearer identification where an error occurs. Said request may be included in an E-RAB modification request message.

Steps 1405 to 1406 are consistent with steps 1305 to 1306 and will not be repeated here.

In step 1406, the MME sends a modify bearer request to the SGW, instructing the UE to bear a new transport layer address and GTPTE ID.

Step 1407, the SGW sends a modify bearer response to the MME.

For bearer deletion, steps 1406 and 1407 do not need to be sent.

Embodiment ten:

FIG. 15 is a schematic diagram of Embodiment 10 of a method for supporting UE bearer recovery in the present invention. The method includes the following steps:

In step 1501, the SGW sends a GTP-U packet to an S1-U channel carried by a certain UE. When the SeNB receives the GTP-U packet sent by the SGW, but the SeNB does not have the bearer context information of the GTP-U packet, the SeNB does not return a GTP error indication to the SGW or pause for a configured time. The configured time is enough for the MeNB to discover that the SeNB is restarted, to re-establish the UE bearer originally established on the SeNB to the restarted SeNB, or to be transferred to another SeNB or MeNB, or to be deleted, or to be re-established, deleted, or transferred After the UE bears the bearer, update the transport layer address and TEID of the bearer to the SGW or restore the bearer.

Step 1502, the MeNB discovers that the SeNB is restarted, and decides to re-establish the UE bearer originally established on the SeNB to the restarted SeNB. The MeNB sends a UE bearer establishment request to the SeNB, and the request may be included in a SeNB addition request or SeNB modification request message.

In step 1503, the SeNB sends a UE bearer setup response to the MeNB, and the request may be included in the SeNB Add Response or SeNB Modification Response message. The SeNB finds that the established UE bearer context is the bearer context of the previously received GTP-U packet, and when the configured time expires, the SeNB may not return a GTP error indication to the SGW.

In step 1504, the MeNB sends an E-RAB modification instruction to the MME, instructing the UE to carry a new transport layer address and GTPTEID on the SeNB.

In step 1505, the MME sends a modify bearer request to the SGW, instructing the UE to bear the new transport layer address and GTPTEID on the SeNB.

Step 1506, the SGW sends a modify bearer response to the MME.

Step 1507, the SGW sends the downlink data carried by the UE to the SeNB's new transport layer address and GTPTEID.

Embodiment eleven:

FIG. 16 is a schematic diagram of Embodiment 11 of a method for supporting UE bearer recovery in the present invention. The method includes the following steps:

Step 1601 , after the SeNB-1 restarts, if it receives a GTP-U packet within a configured period of time without a corresponding UE bearer context, it does not return a GTP error indication to the SGW. The configured time is enough for the MeNB to discover that the SeNB is restarted, to rebuild the UE bearer originally established on the SeNB to the restarted SeNB, or to transfer to another SeNB or MeNB, or to delete, or to recreate, delete, or transfer After the UE bears the bearer, update the transport layer address and TEID of the bearer to the SGW or restore the bearer.

In step 1602, the MeNB discovers that SeNB-1 is restarted, and reestablishes the UE bearer originally established on SeNB-1 to the restarted SeNB, or transfers it to another SeNB or MeNB, or deletes it. Taking the transfer to another SeNB as an example here, the MeNB sends a UE bearer establishment request to SeNB-2, and the request may be included in a SeNB addition request or SeNB modification request message.

Step 1603, SeNB-2 sends a UE bearer establishment response to MeNB, and the request may be included in a SeNB addition response or SeNB modification response message.

Step 1604, the MeNB sends an E-RAB modification instruction to the MME, instructing the UE to bear the new transport layer address and GTPTEID on the SeNB-2.

In step 1605, the MME sends a modify bearer request to the SGW, instructing the UE to bear the new transport layer address and GTPTEID on SeNB-2.

Step 1606, the SGW sends a modify bearer response to the MME.

In step 1607, the SGW sends the downlink data carried by the UE to the new transport layer address and GTPTEID of the SeNB-2.

Embodiment 12:

FIG. 23 is a schematic diagram of Embodiment 12 of a method for supporting UE bearer recovery in the present invention. The method includes the following steps:

Step 2301, the SeNB receives the GTP-U packet sent by the SGW.

In step 2302, the SeNB does not have the bearer context of the GTP-U packet, and the SeNB does not return a GTP error indication to the SGW. The SeNB sends the header information of the GTP-U packet, such as TEID and F-TEID, to the MeNB or other X2-connected eNBs. The information may be carried in a SeNB modification request message, a SeNB deletion request message, a restart request message or an eNB configuration update message. The SeNB can also associate the UE with the bearer with the same address according to the source transport layer address or source IP address of the GTP-U packet, and if it is confirmed that the SeNB is the secondary base station for dual connectivity of the UE, send the packet header information of the above GTP-U packet to UE's MeNB.

Step 2303, the MeNB finds the context of the GTP-U packet, and re-establishes the UE bearer to the SeNB, which may be included in the SeNB modification request message. If the MeNB finds that there is no bearer context for the GTP-U packet, it informs the SeNB that there is no bearer context for the GTP-U packet. At this time, the SeNB can return a GTP error indication to the SGW, and the process ends.

The MeNB finds that there is a context of the GTP-U packet, and the bearer is an SCG bearer, and may re-establish or directly release the bearer in the SeNB.

If the eNB restart message received by the MeNB contains GTP-U packet information, it may not release or temporarily not release the process related to the X2 interface of the eNB sending the restart message, and the context related to the eNB sending the restart message, but first determine whether there is The context of this GTP packet.

Step 2304, SeNB sends UE bearer establishment response to MeNB, said response may be contained in SeNB modification response message.

Steps 2305 to 2308 are consistent with steps 1504 to 1507, and will not be repeated here.

Embodiment thirteen:

FIG. 24 is a schematic diagram of Embodiment 13 of a method for supporting UE bearer recovery in the present invention. The method includes the following steps:

In step 2401, the MME receives a downlink data notification sent by the SGW, instructing the UE to identify the wrong bearer and the cause of the error. The reason for the error is that a GTP error indication is received from the eNB.

In step 2402, the MME finds that the UE with the wrong bearer is in a connected state, and the MME sends a bearer release command to the eNB of the UE. The MME may simultaneously indicate to the eNB that the reason for the release is a GTP channel error.

Step 2403, the eNB receives the UE bearer release request sent by the MME. If the eNB is the MeNB of the UE, and the MeNB finds that the indicated bearer information is an SCG bearer, the MeNB may 1) release all SCG bearers; 2) or release the SCG bearer. After completion, the MeNB bears a release response to the MME.

In step 2404, the eNB sends a bearer modification instruction to the MME, excluding released bearers. The eNB may further decide whether to send a bearer modification instruction to the MME according to the GTP channel error indication sent by the MME.

In step 2405, the MME sends a bearer modification request to the SGW.

Step 2406, the SGW sends a modify bearer response to the MME.

Step 2407, the MME sends a bearer modification confirmation to the eNB.

Embodiment 14:

FIG. 25 is a schematic diagram of Embodiment 14 of a method for supporting UE bearer recovery in the present invention. The method includes the following steps:

In step 2501, the MME receives a downlink data notification sent by the SGW, instructing the UE to identify the wrong bearer and the cause of the error. The reason for the error is that a GTP error indication is received from the eNB.

In step 2502, the MME finds that the UE with the wrong bearer is in a connected state, and the MME sends a bearer release command to the eNB. At the same time, the MME requests the SGW to delete the corresponding bearer, which is step 2503 . Step 2502 and step 2503 are in no particular order. The MME may simultaneously indicate to the eNB that the reason for the release is a GTP channel error or no bearer context.

Step 2503, the MME sends a delete bearer command to the SGW.

Step 2504, the SGW sends a delete bearer command to the PGW.

Step 2505, the eNB sends a bearer release response to the MME.

In step 2506, the PGW returns a delete bearer response to the SGW.

Step 2507, the SGW sends a delete bearer response to the MME.

Step 2505 and steps 2503, 2504, 2506 and 2507 have no necessary sequence relationship.

Embodiment fifteen:

FIG. 26 is a schematic diagram of Embodiment 15 of a method for supporting UE bearer recovery in the present invention. The method includes the following steps:

In step 2601, the MME receives a downlink data notification sent by the SGW, indicating to the UE the ID of the wrong bearer and the cause of the error. The reason for the error is that a GTP error indication is received from the eNB.

In step 2602, the MME finds that the UE with the wrong bearer is in the connected state, and the MME sends a UE context release request message to the eNB of the UE. The message contains information about the bearer where the error occurred. The information of the bearer with the error may include one or more of the following: the identification of the bearer with the error, the F-TEID, transport layer address or TEID of the bearer with the error at the SGW, the F-TEID of the bearer with the error at the base station , transport layer address or TEID, UE identifier.

In step 2603, the eNB receives the UE context release request sent by the MME, which includes the error bearer information indicated in step 2602.

If the eNB is the MeNB of the UE, and the MeNB finds that the indicated bearer information is an SCG bearer, the MeNB can perform any of the following operations: 1) resend the SCG bearer context to the SeNB, and the SeNB performs bearer reconstruction based on it; 2 ) or re-select a SeNB for the UE to establish an SCG bearer; 3) switch the SCG bearer back to the MeNB; 4) or release the SCG bearer. After completion, the MeNB sends a UE Context Release Response message to the MME, indicating that the wrong bearer has been repaired. The indication may also include the address of the transport layer carried by the UE on the RAN side, TEID and other information.

If the eNB is the MeNB of the UE, and the MeNB finds that there is no context of the received bearer. Then the eNB can ignore the received information of the wrong bearer, release the UE context, and return a UE context release response message to the MME.

If the eNB is the MeNB of the UE, and the MeNB finds that the received bearer information is inconsistent with the saved context, the eNB can ignore the received error bearer information, release the UE context, and return a UE context release response message to the MME.

The MME receives the UE context release response message sent by the eNB. If the error bearer repair instruction is included in the message, the UE context is not released, and proceed to step 2604; further, or if the error bearer repair instruction also includes the transport layer address, TEID, etc. carried on the RAN side, proceed to step 2605. If the message does not contain an error bearer repair instruction, the UE context is released, and the process ends.

Step 2604, the MME receives the bearer modification instruction sent by the eNB.

In step 2605, the MME sends a bearer modification request to the SGW.

Step 2606, the SGW sends a modify bearer response to the MME.

In step 2607, the MME sends a bearer modification confirmation to the eNB.

Embodiment sixteen:

FIG. 27 is a schematic diagram of Embodiment 16 of a method for supporting UE bearer recovery in the present invention. The method includes the following steps:

In step 2701, the MeNB receives a restart request message sent by the SeNB.

Step 2702, the MeNB may not delete the X2 context first, and the MeNB sends the SCG bearer context to the SeNB through a restart response message. The MeNB may also indicate a validity time to the SeNB, indicating that the SCG bearer context is valid within the time value. The length of this time value is longer than the time required for MeNB to repair the SCG bearer, or longer than the time required for rebuilding, transferring or deleting the SCG bearer, or longer than updating the bearer transport layer address and TEID after the SCG bearer is rebuilt, deleted or transferred. It takes a long time to get to SGW.

The SeNB saves the SCG bearer context. When receiving the GTP-U packet from the SGW, if the SCG bearer context indicated by the MeNB includes the bearer context of the received GTP-U packet, the SeNB will not return a GTP error indication to the SGW. If the MeNB also indicates a valid time value, when the time value expires, the SeNB deletes the context carried by the SCG sent by the MeNB. Or a valid time value is configured on the SeNB, and when the time value expires, the SeNB may delete the context carried by the SCG sent by the MeNB.

Step 2703, at the same time, the MeNB transfers or deletes the SCG bearer, such as transferring to another SeNB or MeNB. The MeNB sends the bearer modification instruction sent by the eNB to the MME, which does not include the released bearer.

In step 2704, the MME sends a bearer modification request to the SGW.

Step 2705, the SGW sends a modify bearer response to the MME.

Step 2706, the MME sends a bearer modification confirmation to the MeNB. At this point, the MeNB may request the SeNB to delete the previously sent SCG context.

Corresponding to the above methods, the present application provides corresponding equipment, which will be briefly described below in conjunction with the accompanying drawings.

Fig. 17 is a schematic diagram of the composition and structure of device 1 of the present application, the device includes: a first communication module and a first error processing module, wherein:

The first communication module is configured to receive a GTP error indication from the SGW;

The first error processing module is configured to generate an error indication when receiving a GTP error indication from the SGW, and send it to the MeNB through the first communication module.

Fig. 18 is a schematic diagram of the composition and structure of device 2 of the present application, which includes: a second communication module and a second error processing module, wherein:

The second communication module is configured to obtain the eNB type or UE bearer type where the UE bearer is located, and receive an error indication of the UE bearer sent by the SGW;

The second error processing module is configured to, according to the eNB type or the UE bearer type where the UE bearer is located, when it is determined that the UE bearer with an error is a UE bearer on the SeNB, instruct the MeNB to use the second communication module for the UE bearer on the SeNB Treat accordingly.

Fig. 19 is a schematic diagram of the composition and structure of device three of the present application, which includes: a third communication module and a third error processing module, wherein:

The third communication module is configured to acquire the eNB type or UE bearer type where the UE bearer is located;

The third error processing module is configured to perform one or more of the following operations when it is determined that an error occurs in the SeNB:

Do not release the S1-U channel on the MeNB;

Do not release the S1-U channel on the SeNB;

Do not send downlink data notification to MME;

Send an indication that an error occurs in the UE bearer to the MME;

Instruct the MME to reestablish, transfer or release the UE bearer on the SeNB.

Fig. 20 is a schematic diagram of the composition and structure of device 4 of the present application, which includes: a fourth communication module and a fourth error processing module, wherein:

The fourth communication module is configured to notify the MME and/or SGW of the eNB type or UE bearer type where the UE bearer is located;

The fourth error handling module is configured to re-establish, transfer or delete the UE bearer originally established on the SeNB when the MeNB determines that the SeNB has an error.

Fig. 21 is a schematic diagram of the composition and structure of device five of the present application, which includes: a fifth communication module and a fifth error processing module, wherein:

The fifth communication module is configured to receive an error indication from the SeNB;

The fifth error handling module is configured to release or reestablish corresponding UE bearers.

Figure 22 is a schematic diagram of the composition and structure of device six of the present application, which includes: a sixth communication module and a sixth error processing module, wherein:

The sixth communication module is configured to receive the GTP-U packet sent by the SGW;

The sixth error processing module is configured to perform one or more of the following operations when determining that there is no UE bearer context of the GTP-U packet:

do not return a GTP error indication to the SGW;

After waiting for the configured first time, return a GTP error indication to the SGW;

After the device restarts, within the configured second time, if the eNB receives a GTP-U packet and there is no corresponding UE bearer context, it does not return a GTP error indication to the SGW.

Fig. 28 is a schematic diagram of the composition and structure of device 7 of the present application, which includes: a seventh communication module and a seventh error processing module, wherein:

The seventh communication module is configured to receive the GTP-U packet sent by the SGW;

The seventh error processing module is configured to perform one or more of the following operations when determining that there is no UE bearer context of the GTP-U packet:

do not return a GTP error indication to the SGW;

Send the information of the GTP-U packet sent by the SGW to the MeNB.

Fig. 29 is a schematic diagram of the composition and structure of the eighth device of the present application, which includes: the eighth communication module and the eighth error processing module, wherein:

The eighth communication module is used to receive the identification of the wrong bearer and the cause of the error sent by the SGW, and the cause of the error is to receive a GTP error indication from the eNB;

The eighth error handling module is configured to release the erroneous bearer when it is found that the UE corresponding to the erroneous bearer is in a connected state.

Fig. 30 is a schematic diagram of the composition and structure of device 9 of the present application, which includes: a ninth communication module and a ninth error processing module, wherein:

The ninth communication module is configured to receive the identifier and error cause of the wrong bearer sent by the SGW, and the error reason is that a GTP error indication is received from the eNB;

The ninth error processing module is configured to send information about the bearer with the error to the eNB when it is found that the UE corresponding to the bearer with the error is in the connected state.

Fig. 31 is a schematic diagram of the composition and structure of device ten of the present application, the device includes: a tenth communication module and a tenth error processing module, wherein:

The tenth communication module is configured to receive the information of the wrong bearer sent by the MME;

The tenth error processing module is configured to perform the following operations when the device is the MeNB of the UE:

If the information of the bearer is an SCG bearer, perform any one of the following operations: 1) resend the context of the SCG bearer to the SeNB for the SeNB to perform bearer reestablishment; 2) reselect a SeNB for the UE to establish SCG bearer; 3) switch the SCG bearer back to the MeNB; 4) release the SCG bearer, and after performing the operation, instruct the MME to repair the wrong bearer;

If it is found that the received bearer information does not exist in the UE context or the received bearer information is found to be inconsistent with the saved UE context, ignore the received error bearer information and release the UE context.

Figure 32 is a schematic diagram of the composition and structure of the eleventh device of the present application, which includes: an eleventh communication module and an eleventh error processing module, wherein:

The eleventh communication module is configured to discover that the SeNB is restarted;

The eleventh error handling module is configured to send SCG bearer information to the SeNB.

Fig. 33 is a schematic diagram of the composition and structure of the device 12 of the present application, the device includes: a twelfth communication module and a twelfth error processing module, wherein:

The twelfth communication module is configured to receive an SCG bearer context from a MeNB;

The twelfth error handling module is configured to save the SCG bearer context, and when receiving the GTP-U packet from the SGW, if the SCG bearer context indicated by the MeNB includes the bearer context of the GTP-U packet, it does not send The SGW returns a GTP error indication.

It can be seen from the above technical solutions that no matter the SeNB or the SGW loses the UE bearer context, the technical solution of the present application can reasonably re-establish, transfer or delete the UE bearer. The method provided by the present invention is suitable for solving the problem of UE bearer recovery under the dual-connection architecture with separate core networks, greatly improves the reliability and stability of the network, and improves the user's network experience. At the same time, the solution of the present invention is very flexible and can meet the requirements of public communication services.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the present invention. within the scope of protection.

Claims (43)

1. support that UE carries the method recovered, it is characterized in that, comprising:

When prothetic group station SeNB receives the general packet radio service tunnel agreement GTP mistake instruction of the user level that gateway SGW sends, send mistake instruction to dominant base MeNB;

Described GTP mistake instruction is used to indicate MeNB release or rebuilds corresponding UE and carries.

2. method according to claim 1, is characterized in that:

Described mistake instruction comprise in following instruction one or more: the instruction of UE carrying is rebuild in the instruction of the instruction of GTP mistake, S1-U passage release instruction, the instruction of SGW mistake, the user equipment (UE) carrying instruction made a mistake, request release UE carrying or request, receives mark and/or the reason of UE carrying corresponding to the S1-U passage of GTP mistake instruction.

3. an equipment, is characterized in that, comprising: first communication module and the first error handling module, wherein:

Described first communication module, for receiving the instruction of GTP mistake from SGW;

Described first error handling module, for when receiving the instruction of GTP mistake from SGW, generation error indicates, and sends to MeNB by first communication module.

4. support that UE carries the method recovered, it is characterized in that, comprising:

MME obtains eNB type or the UE bearer types that UE carries place;

The UE that MME receives SGW transmission carries the instruction made a mistake, and carries eNB type or the UE bearer types at place according to UE, and when determining that the UE carrying made a mistake is the UE carrying on SeNB, instruction MeNB carries the UE on SeNB and processes accordingly;

Or the UE that MME receives SGW transmission carries the instruction made a mistake, MME determines the UE carrying made a mistake.

5. method according to claim 4, is characterized in that:

Corresponding process comprises: the UE that the UE rebuilding, shift or discharge on SeNB carries or reconstruction, transfer or release make a mistake carries.

6. the method according to claim 4 or 5, is characterized in that:

Described UE carry that the instruction made a mistake comprises in following instruction one or more: the UE bearing identification that the UE made a mistake carries the IP address of the eNB at place, identification information, eNB type, UE bearer types or makes a mistake; Wherein, eNB type is SeNB or MeNB, UE bearer types is MCG carrying or SCG carrying.

7. an equipment, is characterized in that, comprising: second communication module and the second error handling module, wherein:

Described second communication module, carries eNB type or the UE bearer types at place for obtaining UE, and the UE receiving SGW transmission carries the instruction made a mistake;

Described second error handling module, for carrying eNB type or the UE bearer types at place according to UE, when the UE carrying determining to make a mistake is the UE carrying on SeNB, is processed the UE carrying on SeNB by second communication module instruction MeNB accordingly.

8. support that UE carries the method recovered, it is characterized in that, comprising:

SGW obtains eNB type or the UE bearer types that UE carries place;

When SGW determines that SeNB makes a mistake or UE carrying makes a mistake, perform following one or more operation:

SGW does not discharge S1-U passage on MeNB;

SGW does not discharge S1-U passage on SeNB;

SGW does not send downlink data notification to MME;

SGW sends UE to MME and carries the instruction made a mistake;

SGW rebuilds, shifts or discharges the UE carrying on SeNB to MME instruction;

SGW sends the S1-U passage corresponding UE bearing identification and/or reason that receive the instruction of GTP mistake to MME;

SGW rebuilds to MME instruction, shift or discharges the S1-U passage corresponding UE carrying receiving the instruction of GTP mistake.

9. method according to claim 8, is characterized in that:

Described SGW determines that SeNB makes a mistake and comprises: when SGW receives the GTP mistake instruction of UE carrying, and according to UE, to carry the eNB type at place be SeNB or UE bearer types is SCG carrying, determines that SeNB makes a mistake.

10. method according to claim 8, is characterized in that:

SGW carries to the UE that MME sends one or more that the instruction made a mistake comprises in following instruction: the UE bearing identification that the UE made a mistake carries the IP address of the eNB at place, identification information, eNB type, UE bearer types or makes a mistake; Wherein, eNB type is SeNB or MeNB, UE bearer types is MCG carrying or SCG carrying.

Method described in 11. any one of according to Claim 8 to 10, is characterized in that, at SGW before the described one or more operation of execution, comprises further:

SGW sends empty GTP-U bag to the MeNB of the UE of the UE carrying made a mistake, if do not receive the GTP mistake instruction of MeNB transmission, then performs described one or more operation.

12. 1 kinds of equipment, is characterized in that, comprising: third communication module and the 3rd error handling module, wherein:

Described third communication module, carries eNB type or the UE bearer types at place for obtaining UE;

Described 3rd error handling module, for when determining that SeNB makes a mistake or UE carrying makes a mistake, performs following one or more operation:

Do not discharge S1-U passage on MeNB;

Do not discharge S1-U passage on SeNB;

Downlink data notification is not sent to MME;

Send UE to MME and carry the instruction made a mistake;

Rebuild, shift or discharge the UE carrying on SeNB to MME instruction

The S1-U passage corresponding UE bearing identification and/or reason that receive the instruction of GTP mistake is sent to MME;

Rebuild, shift or discharge the S1-U passage corresponding UE carrying receiving the instruction of GTP mistake to MME instruction.

Support that UE carries the method recovered, it is characterized in that, comprising for 13. 1 kinds:

UE is carried eNB type or UE bearer types notice MME and/or SGW at place by MeNB;

When MeNB determines that SeNB makes a mistake, the UE carrying be originally based upon on described SeNB is carried out rebuilding, shift or deleting;

Or MeNB determines that the UE carrying on SeNB makes a mistake, and the UE made a mistake carrying is carried out rebuilding, shift or deleting.

14. methods according to claim 13, is characterized in that:

Described MeNB determines that SeNB makes a mistake or determines that the UE carrying on SeNB makes a mistake and comprises: MeNB is according to the instruction of MME or according to determining that SeNB makes a mistake or determines that the UE carrying on SeNB makes a mistake alternately between MeNB and SeNB; Wherein:

The instruction of MME comprise in following instruction one or more: the UE bearing identification that the UE made a mistake carries the IP address of the eNB at place, identification information, eNB type, UE bearer types or makes a mistake; Wherein, eNB type is SeNB or MeNB, UE bearer types is MCG carrying or SCG carrying;

Comprise alternately between MeNB and SeNB: MeNB receives the information of the GTP-U bag that SeNB sends, MeNB is confirmed whether the UE bearer context that this GTP-U wraps, if there is UE bearer context, then rebuild or transfer UE carrying, as without UE bearer context, this GTP-U bag is informed SeNB without bearer context by MeNB.

15. methods according to claim 13 or 14, is characterized in that:

Describedly the UE be originally based upon on described SeNB carrying carried out rebuild, shift and comprise: the UE carrying be originally based upon on SeNB re-establishes on the SeNB recovered or is based upon on another SeNB or the carrying on SeNB is transferred on MeNB by MeNB by MeNB.

16. 1 kinds of equipment, is characterized in that, comprising: the 4th communication module and the 4th error handling module, wherein:

Described 4th communication module, for carrying by UE of eNB type or UE bearer types notice MME and/or SGW at place;

Described 4th error handling module, during for determining that at MeNB SeNB makes a mistake or determines on SeNB UE carrying and make a mistake, is maybe undertaken rebuilding, shift or deleting by the UE made a mistake carrying by the UE be originally based upon on described SeNB carrying.

Support that UE carries the method recovered, it is characterized in that, comprising for 17. 1 kinds:

MeNB receives mistake instruction from SeNB;

MeNB discharges or rebuilds corresponding UE and carries.

18. methods according to claim 17, is characterized in that:

Described mistake instruction comprise in following instruction one or more: the instruction of UE carrying is rebuild in the instruction of the instruction of GTP mistake, S1-U passage release instruction, the instruction of SGW mistake, the user equipment (UE) carrying instruction made a mistake, request release UE carrying or request, receives mark and/or the reason of UE carrying corresponding to the S1-U passage of GTP mistake instruction.

19. methods according to claim 17, is characterized in that, described MeNB discharges or rebuilds corresponding UE carrying and comprises:

MeNB discharges or rebuilds all carryings of UE or only discharge or rebuild the UE carrying on SeNB;

Or MeNB only discharges or rebuilds UE carrying corresponding to the S1-U passage that makes a mistake.

20., according to claim 17 to the method described in 19 any one, is characterized in that, before MeNB release or rebuilding corresponding UE carrying, comprise further:

MeNB sends empty GTP-U to SGW and wraps, if do not receive the instruction of GTP mistake from SGW, then only release or the UE rebuild on SeNB carry, and do not discharge or rebuild the UE carrying on MeNB.

21. 1 kinds of equipment, is characterized in that, comprising: the 5th communication module and the 5th error handling module, wherein:

Described 5th communication module, for receiving mistake instruction from SeNB;

Described 5th error handling module, carries for discharging or rebuilding corresponding UE.

Support that UE carries the method recovered, it is characterized in that, comprising for 22. 1 kinds:

ENB receives the GTP-U bag that SGW sends;

When eNB determines the UE bearer context not having described GTP-U to wrap, perform following one or more operation:

ENB does not return the instruction of GTP mistake to SGW;

After the very first time that eNB etc. are to be configured, return the instruction of GTP mistake to SGW;

After eNB is restarted, within the second time of configuration, if when eNB receives GTP-U bag and do not have corresponding UE bearer context, do not return the instruction of GTP mistake to SGW.

23. methods according to claim 22, is characterized in that:

The very first time of described configuration and the second time are greater than MeNB and find described eNB failure or restart, and the UE bearer reconstruction be based upon by script on described eNB is on the described eNB of restarting, described eNB is continued the time needed for the SeNB as UE, or be greater than the time needed for the UE be originally based upon on described eNB carrying being transferred to other SeNB or MeNB on, or be greater than the time of deleting needed for described UE carrying, or be greater than in reconstruction, delete, after shifting described UE carrying, the more transport layer address of new bearer, time needed for TEID to SGW or be greater than time needed for described carrying of reparation.

24. 1 kinds of equipment, is characterized in that, comprising: the 6th communication module and the 6th error handling module, wherein:

Described 6th communication module, for receiving the GTP-U bag that SGW sends;

Described 6th error handling module, for when determining the UE bearer context not having described GTP-U to wrap, performs following one or more operation:

The instruction of GTP mistake is not returned to SGW;

After the very first time to be configured, return the instruction of GTP mistake to SGW;

After described equipment is restarted, within the second time of configuration, if when eNB receives GTP-U bag and do not have corresponding UE bearer context, do not return the instruction of GTP mistake to SGW;

To the information of the GTP-U bag that MeNB sends out SGW described and sends.

Support that UE carries the method recovered, it is characterized in that, comprising for 25. 1 kinds:

SeNB receives the GTP-U bag that SGW sends;

When SeNB determines the UE bearer context not having described GTP-U to wrap, perform following one or more operation:

The instruction of GTP mistake is not returned to SGW;

The information of the GTP-U bag that SeNB sends out SGW described send to MeNB;

The transport layer address, source that SeN wraps according to GTP-U or source IP address association have the UE of the carrying of identical address, if confirm that this SeNB is the prothetic group station of the dual link of UE, the information that the GTP-U sent by described SGW wraps sends to the MeNB of UE.

26. methods according to claim 25, is characterized in that: the information of the GTP-U bag that described SGW sends comprises header packet information or the TEID of described GTP-U bag.

27. 1 kinds of equipment, is characterized in that, comprising: the 7th communication module and the 7th error handling module, wherein:

Described 7th communication module, for receiving the GTP-U bag that SGW sends;

Described 7th error handling module, for when determining the UE bearer context not having described GTP-U to wrap, performs following one or more operation:

The instruction of GTP mistake is not returned to SGW;

To the information of the GTP-U bag that MeNB sends out SGW described and sends.

Support that UE carries the method recovered, it is characterized in that, comprising for 28. 1 kinds:

MME receives mark and the error reason of the carrying made a mistake that SGW sends, and error reason receives the instruction of GTP mistake from eNB;

If the UE corresponding to the carrying that MME makes a mistake is in connected state, then the carrying made a mistake described in MME release.

29. methods according to claim 28, is characterized in that, after the carrying made a mistake described in MME release, comprise further:

MME upgrades transport layer address and TEID to the SGW of UE carrying, does not wherein comprise d/d carrying.

30. 1 kinds of equipment, is characterized in that, comprising: the 8th communication module and the 8th error handling module, wherein:

Described 8th communication module, for connecing the mark and error reason of searching the carrying made a mistake that SGW sends, error reason receives the instruction of GTP mistake from eNB;

Described 8th error handling module, for when the UE corresponding to the carrying made a mistake is in connected state, the carrying made a mistake described in release.

Support that UE carries the method recovered, it is characterized in that, comprising for 31. 1 kinds:

MME receives mark and the error reason of the carrying made a mistake that SGW sends, and error reason receives the instruction of GTP mistake from eNB;

If the UE corresponding to the carrying that MME makes a mistake is in connected state, then the information of carrying that makes a mistake to eNB of MME.

32. methods according to claim 31, is characterized in that:

The packets of information of the described carrying made a mistake is containing one or more of following content: the mark of the carrying made a mistake, the F-TEID being carried on SGW made a mistake, transport layer address or TEID, the F-TEID being carried on base station made a mistake, transport layer address or TEID, UE mark.

33. 1 kinds of equipment, is characterized in that, comprising: the 9th communication module and the 9th error handling module, wherein:

Described 9th communication module, for receiving mark and the error reason of the carrying made a mistake that SGW sends, error reason receives the instruction of GTP mistake from eNB;

Described 9th error handling module, for when the UE corresponding to the carrying made a mistake is in connected state, to the information of the carrying that eNB makes a mistake.

Support that UE carries the method recovered, it is characterized in that, comprising for 34. 1 kinds:

ENB receives the information of the carrying made a mistake that MME sends;

If described eNB is the MeNB of UE, then described MeNB performs following operation:

If the information of described carrying is SCG carrying, then described MeNB performs any one in following operation: 1) resend to SeNB by the context that described SCG carries, carry out bearer reconstruction for SeNB; 2) again for UE selects a SeNB to set up SCG carrying; 3) described SCG is carried switchback MeNB; 4) discharge described SCG to carry, after executable operations, described MeNB repairs to the carrying of MME misdirection;

If the information or the MeNB that there is not the carrying received in the bearer context of described MeNB discovery UE find that the bearer context of the information of carrying and the UE of preservation received is inconsistent, then MeNB ignores the information of the carrying made a mistake received, and carries out the release of UE context.

35. methods according to claim 34, is characterized in that:

Transport layer address, the TEID that UE is carried on base station side is comprised further in the instruction that described misdirection carrying is repaired.

36. 1 kinds of equipment, is characterized in that, comprising: the tenth communication module and the tenth error handling module, wherein:

Described tenth communication module, for receiving the information of the carrying made a mistake that MME sends;

Described tenth error handling module, during for being the MeNB of UE at this equipment, performs following operation:

If the information of described carrying is SCG carrying, then perform any one in following operation: 1) resend to SeNB by the context that described SCG carries, carry out bearer reconstruction for SeNB; 2) again for UE selects a SeNB to set up SCG carrying; 3) described SCG is carried switchback MeNB; 4) discharge described SCG to carry, after executable operations, repair to the carrying of MME misdirection;

If the UE context finding not exist in UE context the information of the carrying that the information of the carrying received or discovery receive and preservation is inconsistent, then ignores the information of the carrying made a mistake received, carry out the release of UE context.

Support that UE carries the method recovered, it is characterized in that, comprising for 37. 1 kinds:

MeNB finds that SeNB is restarted;

MeNB sends SCG beared information to SeNB.

38., according to method according to claim 37, is characterized in that, the method comprises further:

MeNB indicates an effective time to SeNB, within described effective time, SCG bearer context is effective, be greater than the time needed for MeNB reparation SCG carrying described effective time, or be greater than and SCG carrying is carried out rebuilding, shift or delete the required time, or be greater than after SCG carrying is carried out rebuilding, delete or shift, the time more needed for new bearer transport layer address, TEID to SGW;

SCG bearer reconstruction to original SeNB, or is transferred to another SeNB or MeNB by MeNB, or deletes, and more new bearer transport layer address, TEID to SGW.

39. methods according to claim 37 or 38, is characterized in that:

Described SCG beared information comprises one or more of following content: bearing identification, is carried on the F-TEID of SGW, transport layer address, TEID, the F-TEID being carried on base station made a mistake, transport layer address, TEID, UE mark.

40. 1 kinds of equipment, is characterized in that, comprising: the 11 communication module and the 11 error handling module, wherein:

Described 11 communication module, for finding that SeNB is restarted;

Described 11 error handling module, for sending SCG beared information to SeNB.

Support that UE carries the method recovered, it is characterized in that, comprising for 41. 1 kinds:

SeNB receives SCG bearer context from MeNB;

SeNB preserves SCG bearer context, and when receiving the GTP-U bag from SGW, if comprise the bearer context of described GTP-U bag in the SCG bearer context of MeNB instruction, then SeNB does not return the instruction of GTP mistake to SGW.

42. methods according to claim 41, it is characterized in that, the method comprises further:

If SeNB receives instruction effective time from MeNB, then, after described effective time time-out, SeNB deletes the SCG bearer context that MeNB sends;

Or SeNB is configured with an effective time, when after described effective time time-out, SeNB deletes the context of the SCG carrying that MeNB sends.

43. 1 kinds of equipment, is characterized in that, comprising: the 12 communication module and the 12 error handling module, wherein:

Described 12 communication module, for receiving SCG bearer context from MeNB;

Described 12 error handling module, for preserving SCG bearer context, when receiving the GTP-U bag from SGW, if comprise the bearer context of described GTP-U bag in the SCG bearer context of MeNB instruction, does not then return the instruction of GTP mistake to SGW.