CN101932051B

CN101932051B - Method for handling switch overtime in evolution network, eNode-B and network system

Info

Publication number: CN101932051B
Application number: CN200910087924.9A
Authority: CN
Inventors: 杨玉成
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2009-06-25
Filing date: 2009-06-25
Publication date: 2014-04-09
Anticipated expiration: 2029-06-25
Also published as: CN101932051A; WO2010148752A1

Abstract

The invention discloses a method for handling switch overtime in an evolution network, an eNode-B and a network system. The method comprises the following steps: after receiving a timer switch overtime message, an S-eNB sends a switch cancelling message to a D-eNB to inform the D-eNB to finish the follow-up signaling data interactive process with an Evolved Packet Core (EPC). The technical scheme of the invention can reduce the processing complexity of the D-eNB and also reduce the signaling data interaction with the EPC when the switch is abnormal.

Description

Processing method for switching overtime in evolution network, evolution base station and network system

Technical Field

The present invention relates to the field of communications, and in particular, to a method for processing handover timeout in a Long Term Evolution (LTE) network, an evolved node b, and an evolved network system.

Background

Fig. 1 is a schematic diagram of an Evolved network architecture, which includes a UE (User Equipment), an Evolved terrestrial Radio access network (E-UTRAN) (Evolved UMTS (Universal mobile telecommunications System)) and an Evolved Packet Core (EPC). The E-UTRAN consists of evolved node Bs (E-UTRAN NodeBs, eNodeBs) which are connected with each other through an X2 interface. The EPC comprises: a Mobility Management Entity (MME), a Serving SAE (System Architecture evolution) Gateway (Serving SAE Gateway), and a Packet data Network SAE Gateway (Packet data Network SAE Gateway). The MME is responsible for mobility management of a control plane, comprises user context and mobility state management, user temporary identity distribution and the like, is connected with SGSN (Serving GSN) in the existing network through an S3 interface, is connected with E-UTRAN through an S1-MME interface, and is connected with a Serving SAE gateway through an S1-U interface, and is provided with a timer; the service SAE gateway is responsible for initiating paging for downlink data in an idle state, managing and storing IP (Internet Protocol, network Protocol) bearing parameters, routing information in the network and the like; the PDN SAE gateway then acts as a user plane anchor between the different access systems. The system shown in fig. 1 further includes a Policy and Charging Rule Function (PCRF) and a Home network Server (HSS).

In the LTE system, handovers are divided into intra-eNodeB inter-cell handovers, inter-eNodeB handovers over the X2 interface, and handovers over the S1 interface. The overall flow based on inter-eNodeB handover over the X2 interface is shown in fig. 2. In the handover of the X2 interface, a base station where the UE is currently located is referred to as a source evolved base station (SourceeNodeB, S-eNB), that is, an initiator of a handover decision and handover procedure, and a base station to which the UE is to be handed over is referred to as a Destination evolved base station (Destination eNodeB, D-eNB), where the handover refers to a process in which the UE is handed over from the S-eNB to a cell controlled by the D-eNB.

If the current wireless Quality does not meet the QOS (Quality of Service) requirement of the user, in order to not affect the user experience, a source evolution base station S-eNB (also called S side) needs to make a handover decision, and when the handover condition is met, the S side forwards the UE communication context stored by the S side to a target evolution base station D-eNB (also called D side) belonging to other cells with better signal Quality through a handover request message of an X2 port, wherein the handover request message comprises the ERAB (E-UTRAN Radio Access Bearer) information serving the UE. After receiving the UE context of the S side, the D side locally prepares the required wireless resources for the UE. When the D side radio resource can accept one or more ERABSs, the D side sends a switching confirmation to the S side, which indicates that the D side resource is ready. After receiving the switching confirmation, the S side reversely transmits the UE uplink and downlink data stored by the S side to the D-eNB through the user plane, simultaneously transmits a switching command to the UE, and simultaneously starts a TX2 RELOCOVERLL timer (also called as a switching timer). And after receiving the switching command, the UE initiates a random access process in the D-side cell, and after the random access is successful, sends a switching completion message to the D-side, which indicates that the UE has been successfully accessed to the D-side cell. And after the D-eNB receives the switching completion message, the D-side control plane informs the user plane to perform downlink data channel switching, at this time, the air interface switching process is completed, and the UE can already receive downlink data at the D-eNB. Because the home eNodeB of the UE changes, the D-eNB sends a signaling PATH SWITCH request message to notify that the EPC downlink transport layer address has changed through the S1 port, after the EPC receives the PATH SWITCH request message, if the EPC path is successfully switched or the uplink transport layer address has changed, the EPC sends a PATH SWITCH acknowledgement message to notify that the D-eNB path is successfully switched, the D-eNB control plane notifies the user plane of uplink switching, the uplink data of the D-eNB may be sent to the SGW (Service gateway), at this time, the switching is completed, and the signaling flow of the entire process is shown in fig. 3.

Referring to fig. 4, in the handover procedure, after issuing a Radio Resource Control (RRC) connection reconfiguration message (handover command), the S-side starts a handover timer TX2 relooverll, as shown in step 407 of fig. 4. The TX2 RELOCOVERLL timer is used for ensuring that the S side can completely transmit user data to the D side, meanwhile, the S side sends a resource release message to the S side after the D side completes the switching, and the S side releases the local resources related to the UE when receiving the resource release message in the timer.

If the timer TX2 relooverl times out, the S-side sends a UE context release request to the EPC (step 409 in fig. 4), and requests the EPC to release NAS (Non-Access Stratum) resources related to the UE, and then the EPC and the S-eNB release contexts related to the UE, respectively (steps 411 and 412 in fig. 4). The UE and D-eNB are not aware at this time that the EPC and S-eNB have released context information related to themselves. If the UE has successfully received the random access, it will also send a re-configuration connection complete message to the D-eNB (step 413 in fig. 4), after receiving the re-configuration connection complete message and performing internal processing, the D-eNB will also send an PATH SWITCH request message to the EPC to request the EPC to update the downlink transport layer address, at this time, the context related to the UE being handed over in the EPC does not exist, only reply a PATH SWITCH failure message to the D-eNB, after receiving a PATH SWITCH failure message, the D-eNB can only send a UE context release request message to the EPC again, and request the EPC to release the context information of the UE again (step 416 in fig. 4). The D-eNB does not know whether the resources of the S-eNB are released or not, and has to send a resource release message to the S-eNB (step 417 in fig. 4), but actually the S-eNB has no UE related information.

Through the above process, it can be seen that after the TX2 relooverl timer expires, the action behaviors of the UE and the D-eNB are largely unnecessary, such as step 414, step 415, step 416, and step 417, and therefore, the processing flow of the existing scheme is relatively redundant, and the implementation complexity is increased.

Disclosure of Invention

The invention provides a processing method for switching overtime in an evolution network, an evolution base station and a network system, which can reduce the processing complexity of a target evolution base station D-eNB and reduce the signaling interaction with an evolution packet core network (EPC) device when the switching is abnormal.

The technical scheme of the embodiment of the invention is realized as follows:

a method for processing switching overtime in an evolution network comprises the following steps:

and after receiving the overtime message of the switching timer, the source evolution base station S-eNB sends a switching cancellation message to the target evolution base station D-eNB and informs the target evolution base station D-eNB to finish the subsequent signaling data interaction process with the EPC.

Preferably, the method further comprises the following steps:

the source evolution base station S-eNB sends a context release request message of User Equipment (UE) to Evolved Packet Core (EPC) equipment and informs the EPC equipment to release non-access stratum (NAS) resources related to the UE;

the source evolution base station S-eNB receives a user equipment UE context release command message sent by the Evolved Packet Core (EPC) equipment and then releases resources related to the user equipment UE;

and the source evolution base station S-eNB sends a user equipment UE context release completion message to the evolved packet core network (EPC).

a target evolution base station D-eNB receives a switching cancellation message sent by a source evolution base station S-eNB;

and the target evolution base station D-eNB finishes the subsequent signaling data interaction process with the evolved packet core network (EPC) equipment according to the switching cancellation message.

Preferably, the step of receiving the handover cancel message sent by the source evolved node b S-eNB by the target evolved node b D-eNB further includes:

the target evolution base station D-eNB sends RRC connection release information to User Equipment (UE);

and the target evolution base station D-eNB releases resources related to the user equipment UE.

An evolved base station, for a source side, comprising:

and the first sending unit is used for sending a switching cancellation message to other evolution base stations after receiving the switching timer overtime message, and informing the other evolution base stations of finishing the subsequent signaling data interaction process with the Evolved Packet Core (EPC).

Preferably, the method further comprises the following steps:

a second sending unit, configured to send a UE context release request message to the evolved packet core device EPC, where the UE context release request message notifies the evolved packet core device EPC to release non-access stratum NAS resources related to the UE;

a first receiving unit, configured to receive a UE context release command message sent by the EPC, where the UE context release command message is used to release resources related to the UE;

a third sending unit, configured to send a user equipment UE context release completion message to the Evolved Packet Core (EPC).

An evolved base station, for a destination side, comprising:

a second receiving unit, configured to receive a handover cancel message sent by another enodeb;

and the first execution unit is used for finishing the subsequent signaling data interaction process with the Evolved Packet Core (EPC) equipment according to the switching cancellation message.

Preferably, the method further comprises the following steps:

a fourth sending unit, configured to send an RRC connection release message to the UE;

a second performing unit, configured to release resources related to the user equipment UE.

An evolution network system comprises User Equipment (UE), a source evolution base station (S-eNB), a target evolution base station (D-eNB) and Evolved Packet Core (EPC) network equipment;

the source evolution base station S-eNB comprises:

a first sending unit, configured to send a handover cancel message to the target evolved node b D-eNB after receiving a handover timer timeout message, and notify the target evolved node b D-eNB to end a subsequent signaling data interaction process with the Evolved Packet Core (EPC);

the target evolution base station D-eNB comprises:

a second receiving unit, configured to receive a handover cancel message sent by the source eNB S-eNB;

a first executing unit, configured to end a subsequent signaling data interaction process with the evolved packet core device EPC according to the handover cancel message.

Preferably, the target eNB further includes:

Preferably, the source eNB further includes:

When the switching is abnormal, the source evolution base station S-eNB sends a switching cancellation message to the target evolution base station D-eNB to inform the target evolution base station D-eNB to finish the subsequent signaling data interaction process with the EPC, thereby avoiding the target evolution base station D-eNB from processing unnecessary UU port and S1 port messages, avoiding the target evolution base station D-eNB from sending unnecessary resource release messages to the source evolution base station S-eNB, reducing the signaling overhead of the system and reducing the complexity of the system.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.

FIG. 1 is a diagram of a prior art evolved network architecture;

fig. 2 is a schematic diagram of an inter-eNodeB handover based on an X2 interface in the prior art;

fig. 3 is a signaling flow diagram of a handover procedure in an evolved network in the prior art;

FIG. 4 is another signaling flow diagram of a handover procedure in an evolved network in the prior art;

fig. 5 is a signaling flowchart of a method for handling handover timeout in an evolved network according to a first embodiment of the present invention;

fig. 6 is a signaling flowchart of a method for handling handover timeout in an evolved network according to a second embodiment of the present invention;

fig. 7 is a signaling flowchart of a method for handling handover timeout in an evolved network according to a third embodiment of the present invention;

fig. 8 is a schematic structural diagram of an evolved network system according to a preferred embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The first embodiment is as follows:

the present embodiment is described with reference to fig. 5, in which a user equipment UE performs data upload and video call, and a target eNB D-eNB does not receive a Radio Resource Control (RRC) connection reconfiguration complete message due to mobility triggering handover, and a TX2 reloover timer on a S-eNB side of a source eNB is overtime, which causes an S-eNB to be abnormal in a handover process.

Assuming that the UE already has 3 services, the service IDs are 5, 6, 7, respectively. Wherein 5 is ERabId of default bearer (or default service), 6 is ERabId of FTP upload service, 7 is ERabId of video call, Uu port DrbId corresponding to these three services is set to be 3, 4, 5 respectively (this DrbId is allocated by evolved node b eNB, and the value is determined by eNB); suppose that the UE initially initiates a service in a Cell of a source eNB S-eNB, the Cell is numbered Cell1 and moves to a target eNB D-eNB, the Cell of the D-eNB is numbered Cell2, and Cell1 and Cell2 are adjacent to each other.

Step 501, the UE reports a measurement report to the S-eNB.

In the FTP uploading and video call processes, the UE meets measurement related configuration due to movement, and reports a measurement report to the S-eNB.

Step 502, S-eNB makes a switching decision.

And the S-eNB analyzes the measurement report reported by the UE, finds a cell2 to which the D-eNB belongs, and can be used as a target cell for switching, and the S-eNB makes a switching judgment.

Step 503, the S-eNB sends a handover request message to the D-eNB.

And the S-eNB sends a switching request message to the D-eNB, wherein the switching request message carries QOS information related to services with service IDs of 5, 6 and 7 and RB information with DrbId of 3, 4 and 5.

Step 504, the D-eNB sends a switching confirmation message to the S-eNB.

And after receiving the switching request message, the D-eNB prepares resources for FTP uploading service with the ERABID of 6, video service with the ERABID of 7 and signaling service which needs to be established by the D-eNB, the resources are prepared successfully, and after successful admission, the D-eNB sends a switching confirmation message to the S-eNB to wait for the UE to access to the cell of the D-eNB.

And 505, the S-eNB transmits the data received by the S-eNB back to the D-eNB.

And after receiving the switching confirmation message, the S-eNB reversely transmits the received service data packet to the D-eNB. Normally, the S-eNB needs to retransmit the downlink data packet transmitted from the EPC, and also needs to retransmit the uplink data packet of the UE. In this embodiment, the S-eNB needs to create six reverse transmission channels, two of which are used for uplink and downlink data transmission of a default bearer, two of which are used for uplink and downlink data transmission of an FTP upload service ErabId6, and the remaining two of which are used for uplink and downlink data transmission of a video service ErabId 7.

Step 506, the S-eNB sends an RRC connection reconfiguration message to the UE.

And the S-eNB sends an RRC connection reconfiguration message (switching command) to the UE according to the RRC context information in the switching confirmation message.

Step 507, starting a timer.

And starting a TX2 RELOCOVERLL timer, and after the D-eNB finishes the switching, sending a resource release message for releasing S-side resources to the S-eNB by the D-eNB.

Step 508, the S-eNB receives the TX2 RELOCOVERLL timer timeout message.

Due to the handover exception, the TX2 relooverl timer times out.

Step 509, the S-eNB sends a handover cancel message to the D-eNB.

And the S-eNB sends a switching cancellation message to the D-eNB due to the fact that the switching timer is overtime on the S side.

Step 510, the S-eNB sends a UE context release request message to the EPC.

And the S-eNB sends a UE context release request message to the EPC and requires the EPC to release NAS layer resources related to the UE to be switched.

Step 511, the EPC sends a UE context release order message to the S-eNB.

Step 512, the S-eNB sends a UE context release completion message to the EPC.

And the S-eNB receives the UE context release command message, releases the related resources of the switched UE and sends a UE context release completion message to the EPC.

Step 513, the D-eNB sends an RRC connection release message to the UE.

And when the D-eNB receives the switching cancellation message sent by the S-eNB, sending an RRC connection release message to the UE. At this time, the D-eNB does not receive the RRC connection reconfiguration complete message of the UE, the D-eNB sends the RRC connection reconfiguration complete message in order to prevent the UE from being possibly subjected to random access completion and does not receive the D-ENODEB, and in consideration of releasing the UE resources as soon as possible, the D-eNB sends the RRC connection release message to the UE, the D-eNB does not process the RRC connection reconfiguration complete message of the UE after sending the message, and the D-eNB releases any resource prepared for switching the UE.

At this time, the handover is finished, and the D-eNB does not need to perform any signaling data interaction with the EPC.

In this embodiment, the handover cancel message may be sent to the D-eNB after the S-eNB sends the UE context release message, or after the S-eNB receives the UE context release command message or sends the UE context release complete message, that is, the step 509 may be after the step 510, the step 511, or the step 512. Under normal conditions, the control plane may determine whether the transmission of the upload data and the video call data forwarded by the user plane for the UE is finished, that is, whether the data related to Erab6 and ErabId7 are successfully forwarded to the D-eNB, and if the data related to Erab6 and ErabId7 are successfully forwarded, the S-eNB local resource is released without causing a packet loss. At this time, because the TX2 relooverll timer set by the S-eNB enters the release flow earlier than normal, the time left for data reverse transmission is relatively short, the EPC side does not know whether the user is in the handover state at present, and the data transmission to the S-eNB is not terminated, thereby possibly causing loss of service data.

Example two:

as shown in fig. 6, in the process of FTP downloading by a UE, due to mobility triggering handover, a D-eNB receives an RRC connection reconfiguration complete message sent by the UE, and a TX2 relooverl timer on an S side times out, which causes an exception in the handover process, the present embodiment is described.

Assuming that the UE already has 2 services, the service IDs are 5, 6, respectively. Where 5 is ERabId of the default bearer (or default service) and 6 is ERabId of the FTP download service. The Uu port DrbId corresponding to the two services is set to be 3 and 4 respectively (DrbId is allocated by an evolved node b (eNB), and the value is determined by the eNB). Suppose that the UE initially initiates a service in an S-eNB Cell, the Cell number is Cell1, and the UE moves to the D-eNB, the Cell of the D-eNB is Cell2, and Cell1 and Cell2 are adjacent to each other.

Step 601, UE reports the measurement report to S-eNB.

In the FTP downloading process, the UE meets the measurement related configuration due to the movement, and reports a measurement report to the S-eNB.

Step 602, the S-eNB makes a handover decision.

Step 603, the S-eNB sends a switching request message to the D-eNB.

And the S-eNB sends a switching request message to the D-eNB, wherein the switching request message carries QOS information related to services with service IDs of 5 and 6, and meanwhile, a switching transparent container carries RB information with DrbId of 3 and 4.

And step 604, the D-eNB sends a switching confirmation message to the S-eNB.

And after receiving the switching request message, the D-eNB prepares resources for the FTP service with the ERABID of 6 and the signaling service which needs to be established by the D-eNB, the resources are successfully prepared, and after the successful admission, the D-eNB sends a switching confirmation message to the S-eNB to wait for the UE to access the cell of the D-eNB.

Step 605, the S-eNB transmits the data received by the S-eNB back to the D-eNB.

And after receiving the switching confirmation message, the S-eNB reversely transmits the received FTP service data packet to the D-eNB. Normally, the S-eNB needs to retransmit the downlink data packet transmitted from the EPC, and also needs to retransmit the uplink data packet of the UE.

Step 606, the S-eNB sends RRC connection reconfiguration message to the UE.

Step 607, start the timer.

Step 608, the UE sends an RRC connection reconfiguration complete message to the D-eNB.

When the D-eNB receives the RRC connection reconfiguration complete message, since the ERABID is that the downlink transport layer addresses of the 5 and 6 services change, the D-eNB needs to notify the EPC to convert the downlink transport layer addresses of the two services, and then step 609 is performed.

Step 609, the D-eNB sends PATH SWITCH a request message to the EPC.

The D-ENODEB sends PATH SWITCH a request message to the EPC, including transport layer addresses with ERABID 5 and 6 and the newly assigned Enb S1 APID.

Step 610, the S-eNB receives a TX2 RELOCOVERLL timer timeout message.

Due to the handover exception, the TX2 relooverl timer times out.

Step 611, the S-eNB sends a handover cancel message to the D-eNB.

Step 612, the S-eNB sends a UE context release request message to the EPC.

And the S-eNB sends a UE context release request message to the EPC and requires the EPC to release the NAS layer context related to the UE to be switched.

Step 613, the EPC sends a UE context release command message to the S-eNB.

Step 614, the S-eNB sends a UE context release completion message to the EPC.

Step 615, the D-eNB sends an RRC connection release message to the UE.

And D-eNB sends RRC connection release message to UE without waiting for PATH SWITCH confirmation message of EPC, enters a local resource release state and prepares to release local resources.

And the resources of the EPC, the S-eNB and the D-eNB are released, and at the moment, the switching is finished, and the D-eNB does not need to perform any signaling data interaction with the EPC.

In this embodiment, the handover cancel message may be sent to the D-eNB after the S-eNB sends the UE context release message, or after the S-eNB receives the UE context release command message or sends the UE context release complete message, that is, the step 611 may be after the step 612, the step 613, or the step 614.

Example three:

as shown in fig. 7, in the process of FTP downloading by the UE, due to mobility triggering handover, the D-eNB receives PATH SWITCH confirmation message of EPC, and the TX2 relooverll timer on S side times out, which causes an exception in the handover process, the present embodiment is described.

Step 701, the UE reports a measurement report to the S-eNB.

Step 702, the S-eNB makes a handover decision.

Step 703, the S-eNB sends a handover request message to the D-eNB.

Step 704, the D-eNB sends a switching confirmation message to the S-eNB.

And after receiving the switching request message, the D-eNB prepares resources for FTP services with ERABID 5 and 6 and signaling services which need to be established by the D-eNB, the resources are successfully prepared, and after successful admission, the D-eNB sends a switching confirmation message to the S-eNB to wait for the UE to access the cell of the D-eNB.

Step 705, the S-eNB transmits the data received by the S-eNB back to the D-eNB.

Step 706, the S-eNB sends an RRC connection reconfiguration message to the UE.

Step 707, start timer.

Step 708, the UE sends an RRC connection reconfiguration complete message to the D-eNB.

After receiving the RRC connection reconfiguration complete message, the D-eNB needs to notify the EPC to convert the downlink transport layer addresses of the two services, since the ERABID is that the downlink transport layer addresses of the 5 and 6 services change, and then step 709 is entered.

Step 709, the D-eNB sends PATH SWITCH a request message to the EPC.

710. The EPC sends PATH SWITCH an acknowledgement message to the D-eNB.

And D-eNB receives the PATH SWITCH confirmation message, stores the MME S1AP ID related to the UE and stores uplink transport layer addresses with ERABID 5 and ERABID 6.

Step 711, the S-eNB receives the TX2 RELOCOVERLL timer timeout message.

Due to the handover exception, the TX2 relooverl timer times out.

Step 712, the S-eNB sends a handover cancel message to the D-eNB.

Step 713, the S-eNB sends a UE context release request message to the EPC.

Step 714, the EPC sends a UE context release order message to the S-eNB.

Step 715, the S-eNB sends a UE context release complete message to the EPC.

Step 716, the D-eNB sends RRC connection release message to the UE.

And D-eNB sends RRC connection release message to UE, enters a local resource release state and prepares to release local resources.

Referring to fig. 8, the invention also discloses an evolved network system, which includes user equipment UE, source evolved base station S-eNB, target evolved base station D-eNB and evolved packet core network equipment EPC.

The source evolution base station S-eNB comprises:

and the first sending unit is used for sending a switching cancellation message for informing the target evolution base station D-eNB to end the subsequent signaling data interaction process with the Evolved Packet Core (EPC) equipment to the target evolution base station D-eNB after receiving the switching timer overtime message.

The target evolution base station D-eNB comprises:

and the second receiving unit is used for receiving the switching cancellation message sent by the source evolution base station S-eNB.

A first execution unit, configured to end a subsequent signaling data interaction procedure with the evolved packet core device EPC.

The target evolution base station D-eNB further comprises:

and a fourth sending unit, configured to send the RRC connection release message to the user equipment UE.

The source evolved node B S-eNB further comprises:

The working process and working principle of the evolved network system are described in detail in the embodiments described in fig. 5, fig. 6, and fig. 7, and for brevity, are not described again here.

The invention also discloses an evolution base station, which is used for the source side, and the evolution base station comprises:

Further comprising:

The invention also discloses an evolution base station, which is used for a destination side and comprises the following steps:

Further comprising:

The constituent structure and the working principle of the enodeb refer to the description of the method embodiment and the system embodiment, which are not repeated herein.

It can be understood by those skilled in the art that, in the embodiments of the methods of the present invention, the sequence numbers of the steps are not used to limit the sequence of the steps, and for those skilled in the art, the change of the sequence of the steps is also within the protection scope of the present invention without making creative efforts.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.

Claims

1. A method for processing handover timeout in an evolved network is characterized by comprising the following steps:

after receiving the overtime message of the switching timer, the source evolution base station S-eNB sends a switching cancellation message to a target evolution base station D-eNB and informs the target evolution base station D-eNB to finish the subsequent signaling data interaction process with an Evolved Packet Core (EPC) device;

wherein,

the control plane can judge whether the upload data and the video call data forwarded by the user plane for the user equipment UE are successfully forwarded, if the upload data and the video call data are successfully forwarded, the control plane:

2. A method for processing handover timeout in an evolved network is characterized by comprising the following steps:

the target evolution base station D-eNB finishes the subsequent signaling data interaction process with the evolved packet core network equipment EPC according to the switching cancellation message;

the control plane may determine whether the upload data and the video call data forwarded by the user plane for the UE are successfully forwarded, and if the upload data and the video call data are successfully forwarded, the control plane:

the method comprises the following steps that after the target evolution base station D-eNB receives the switching cancellation message sent by the source evolution base station S-eNB:

3. An evolved base station for a source side, comprising:

the first sending unit is used for sending a switching cancellation message to other evolution base stations after receiving the switching timer overtime message and informing the other evolution base stations of finishing the subsequent signaling data interaction process with the evolution packet core network equipment EPC;

a second sending unit, configured to determine whether upload data and video call data forwarded by a user plane for user equipment UE are successfully forwarded, and if so, send a UE context release request message to an Evolved Packet Core (EPC) that notifies the EPC to release NAS resources related to the UE;

4. An evolution network system is characterized by comprising User Equipment (UE), a source evolution base station (S-eNB), a target evolution base station (D-eNB) and Evolved Packet Core (EPC) network equipment;

the source evolution base station S-eNB comprises:

the target evolution base station D-eNB comprises:

a first execution unit, configured to end a subsequent signaling data interaction process with the Evolved Packet Core (EPC) according to the handover cancel message;

the target evolution base station D-eNB further comprises:

a second execution unit, configured to release resources related to the UE;

the source evolved node B S-eNB further comprises: