WO2012051903A1 - 一种多载波的切换方法和装置 - Google Patents

一种多载波的切换方法和装置 Download PDF

Info

Publication number
WO2012051903A1
WO2012051903A1 PCT/CN2011/080287 CN2011080287W WO2012051903A1 WO 2012051903 A1 WO2012051903 A1 WO 2012051903A1 CN 2011080287 W CN2011080287 W CN 2011080287W WO 2012051903 A1 WO2012051903 A1 WO 2012051903A1
Authority
WO
WIPO (PCT)
Prior art keywords
link
ran node
target
source
message
Prior art date
Application number
PCT/CN2011/080287
Other languages
English (en)
French (fr)
Inventor
郭宣羽
陈燕燕
李秉肇
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP18203904.0A priority Critical patent/EP3528539A3/en
Priority to EP11833809.4A priority patent/EP2618609B1/en
Priority to ES11833809T priority patent/ES2717452T3/es
Priority to EP20197673.5A priority patent/EP3823351A1/en
Publication of WO2012051903A1 publication Critical patent/WO2012051903A1/zh
Priority to US13/866,416 priority patent/US9445333B2/en
Priority to US15/239,546 priority patent/US9973991B2/en
Priority to US15/949,381 priority patent/US10743228B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00692—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using simultaneous multiple data streams, e.g. cooperative multipoint [CoMP], carrier aggregation [CA] or multiple input multiple output [MIMO]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00698—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using different RATs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present invention relates to mobile communication technologies, and in particular, to a multi-carrier switching method and apparatus.
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • CDMA Code Division Multiple Access 2000.
  • Radio carrier technology, RAT Multiple carrier frequency aggregation technology
  • multiple carrier frequency aggregation technology refers to the ability to simultaneously transmit data of the same user with multiple carrier frequency resources. This is called intra-system multi-carrier aggregation technology.
  • intra-system multi-carrier aggregation technology To improve the peak rate of users, the single-RAT internal multi-carrier aggregation technology has matured.
  • the peak rate of the service of the user equipment will reach another bottleneck.
  • the networks of multiple standards ie, multiple RATs
  • UMTS Universal Mobile Communications
  • GSM Global System for Mobile communications
  • CDMA2000 Code Division Multiple Access
  • LTE Long Term Evolution
  • Multimode terminals are also widely used.
  • UEs can work simultaneously.
  • the UE works in both the UTMS and the LTE system, or the UE works in both the LTE and GSM/EDGE Radio Access Network (GERAN) systems, and other systems. .
  • GERAN GSM/EDGE Radio Access Network
  • a node that aggregates/diverts data of the two or the plurality of networks is referred to as a data aggregation/diversion node, and the data aggregation/diversion node It can be used as a carrier aggregation control node or an anchor point for carrier data offload/aggregation control.
  • the link corresponding to the anchor point is the primary RAT link, and the link corresponding to the non-anchor point is the secondary RAT link.
  • the link control nodes of the UMTS and LTE systems are a Radio Network Controller (RNC) and an evolved base station (eNB), respectively, if the radio network controller of the UMTS system As an anchor point, the primary RAT link is a UMTS link, and the secondary RAT link is an LTE link.
  • RNC Radio Network Controller
  • eNB evolved base station
  • the primary RAT link is an LTE link
  • the secondary RAT link is a UMTS link.
  • the base station (evolved NodeB, eNB) of the LTE system is an anchor point
  • the primary RAT link is an LTE link
  • the secondary RAT link is a UMTS link.
  • aspects of the present invention provide a multi-carrier handover method and apparatus, which implements handover during multi-RAT link carrier aggregation, and ensures continuity of data transmission throughput.
  • An aspect of the present invention provides a method for switching multiple carriers, including:
  • a target radio access network (RAN) node corresponding to the first link receives a message including the second link information sent by the source RAN node corresponding to the first link; the target RAN corresponding to the first link And the node establishes a connection of the RAN node corresponding to the second link according to the second link information, to perform data transmission;
  • RAN radio access network
  • the first link is a link in a first radio access technology (RAT) network; the second link is a link in a second RAT network.
  • RAT radio access technology
  • Another aspect of the present invention provides a multi-carrier switching method, where the second link corresponds
  • the RAN node is an anchor point of the carrier data offloading/aggregation control, and the RAN node corresponding to the first link is the RAN node of the secondary link, and the method includes: determining, by the anchor point of the carrier data offloading/aggregation control corresponding to the second link a RAN node of the target secondary link corresponding to the first link;
  • the anchor point sends the RAN node information of the target secondary link to the RAN node of the source secondary link corresponding to the first link, to establish and the target secondary link by using the RAN node of the source secondary link.
  • the connection of the RAN is not limited to the RAN node information of the target secondary link to the RAN node of the source secondary link corresponding to the first link, to establish and the target secondary link by using the RAN node of the source secondary link.
  • a method for switching multiple carriers including:
  • the source RAN node of the first link determines a RAN node that can continue to use the multi-RAT link carrier aggregation as the target RAN node of the first link;
  • the source RAN node of the first link sends a message carrying the second link information to the target RAN node of the first link, so that the target RAN node corresponding to the first link corresponds to the second link
  • the RAN node establishes a connection and performs data transmission.
  • a multi-carrier switching apparatus including: a receiving module, configured to receive a message that includes a second link information sent by a source RAN node corresponding to the first link;
  • a establishing module configured to establish, according to the second link information, a connection between a target RAN node corresponding to the first link and a RAN node corresponding to the second link, to perform data transmission;
  • the first link is a link in a first RAT network; and the second link is a link in a second RAT network.
  • a multi-carrier switching apparatus where a RAN node corresponding to the second link is an anchor point of carrier data offloading/aggregation control, and a RAN node corresponding to the first link is a RAN of the secondary link.
  • a node where the device is located at the anchor point, the device includes: a determining module, configured to determine a RAN node of a target secondary link corresponding to the first link, and a sending module, configured to: RAN node information is sent to the first link pair
  • the RAN node of the source secondary link is to establish a connection with the RAN of the target secondary link through the RAN node of the source secondary link.
  • a multi-carrier switching apparatus including:
  • a determining module configured to determine a RAN node that can continue to use multi-RAT link carrier aggregation as a target RAN node of the first link;
  • a sending module configured to send a message carrying the second link information to the target RAN node of the first link, so that the target RAN node corresponding to the first link and the RAN node corresponding to the second link Data transfer is performed after the connection is established.
  • the multi-carrier switching method and apparatus in the embodiment of the present invention can perform the system on the first link by establishing a connection between the target RAN node corresponding to the first link and the RAN node corresponding to the second link.
  • the first link target RAN node and the second link RAN node normally transmit multi-RAT aggregate data to ensure continuity of service transmission throughput.
  • FIG. 1 is a schematic flowchart of a method for switching a multi-carrier according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a method for switching a multi-carrier according to another embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a multi-carrier switching method according to another embodiment of the present invention
  • FIG. 5 is a schematic flowchart of a multi-carrier switching method according to another embodiment of the present invention
  • 6 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention
  • FIG. 7 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention
  • FIG. 1 is a schematic flowchart of a method for switching a multi-carrier according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a method for switching a multi-carrier according to another embodiment of the present invention
  • FIG. 4 is a schematic flowchart
  • FIG. 8 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention
  • FIG. 9 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention
  • FIG. 11 is a schematic flowchart of a multi-carrier switching method according to another embodiment of the present invention
  • FIG. 12 is a schematic flowchart of a multi-carrier switching method according to another embodiment of the present invention
  • 13 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention
  • FIG. 14 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention
  • FIG. 14 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention
  • FIG. 16 is a schematic flowchart of a multi-carrier switching method according to another embodiment of the present invention
  • FIG. 17 is a schematic flowchart of a multi-carrier switching method according to another embodiment of the present invention
  • 18 is a schematic flowchart of a multi-carrier switching method according to another embodiment of the present invention
  • FIG. 19 is a schematic structural diagram of a multi-carrier switching apparatus according to an embodiment of the present invention
  • FIG. 20 is a schematic structural diagram of a multi-carrier switching apparatus according to another embodiment of the present invention
  • FIG. 21 is a schematic structural diagram of a multi-carrier switching apparatus according to another embodiment of the present invention.
  • the UMTS and the LTE system are taken as an example, and the corresponding links are respectively a UMTS link (a cylinder called a U link) and an LTE link (a cylinder is called an L link), and corresponding link control nodes respectively For the RNC and eNB.
  • the anchor point is RNC
  • the primary RAT link is the U link
  • the secondary RAT link is the L link
  • the primary RAT link is L link
  • the secondary RAT link is a U link.
  • the corresponding links are the LTE link and the GERAN link, respectively, and the corresponding link control nodes are the eNodeB and the Base Station Cotroller (BSC).
  • the anchor point is an eNodeB
  • the primary RAT link is an LTE link
  • the secondary RAT link is a GERAN link
  • the anchor point is a BSC
  • the primary RAT link is a GERAN link
  • the secondary RAT link is an LTE link.
  • the handover involved in this paper refers to the change of the link control node of the radio access network.
  • the link control node of the UMTS system is the RNC, and when the handover occurs, the UE switches from the source RNC to the target RNC;
  • the link control node of the LTE system is the eNB, and when the handover occurs, the UE switches from the source eNB to the target eNB;
  • GERAN system The link control node is an eNB, and when a handover occurs, the UE switches from the source BSC to the target BSC.
  • the name of the link control node in which the UE is switched is different according to the name of the link control node, and details are not described herein again.
  • the embodiments of the present invention can be divided into the following scenarios:
  • Scenario 1 The primary RAT link is switched, the secondary RAT link is not switched; scenario 2: the secondary RAT link is switched, and the primary RAT link is not switched; scenario 3: the primary RAT link and the secondary RAT link are switched; scenario 4: After the single RAT link is switched, it is changed to a dual RAT link.
  • Scenario 5 After the dual RAT link is switched, it is changed to a single RAT link.
  • scenario 3 scenario 1 and 2 can be comprehensively implemented.
  • the primary RAT link switching process is performed first, then the secondary RAT link switching process is performed, or the secondary RAT link switching process is performed first, and then the primary RAT chain is performed.
  • the route switching process is performed in each process according to the process of scenario 1 or scenario 2.
  • scenario 4 the single RAT before the handover can be used as the secondary RAT link, which is implemented by scenario 2. Therefore, the embodiment of the present invention mainly describes scenes one and two.
  • FIG. 1 is a schematic flowchart of a multi-carrier switching method according to an embodiment of the present invention, which may be as follows.
  • the target radio access network (RAN) node corresponding to the first link receives the message including the second link information sent by the source RAN node corresponding to the first link.
  • the first link is a link in a first radio access technology (RAT) network;
  • the second link is a link in a second RAT network.
  • RAT radio access technology
  • the first link refers to the link where the handover occurs, and the second link refers to the link that does not switch.
  • the RNC of the UMTS system is an anchor point, the primary RAT link is a U link, and the secondary RAT link is an L link; when the primary RAT link is switched and the secondary RAT link is not switched, the first link is a U link.
  • the second link is the L link; the target RAN node corresponding to the first link is the target RNC, and the source RAN node corresponding to the first link is the source RNC.
  • the second link information is L link information, for example, the L link information may be an eNB identity Identity or a cell ID (cell ID) of a cell to which the eNB belongs.
  • the RNC of the UMTS system is an anchor point, the primary RAT link is a U link, and the secondary RAT link is an L link; when the primary RAT link is not switched, and the secondary RAT link is switched, the first link is an L link.
  • the second link is a U link; the target RAN node corresponding to the first link is the target eNB, and the source RAN node corresponding to the first link is the source eNB.
  • the second link information is U link information.
  • the U link information may be: an RNC identifier RNC ID or a cell identifier Cell ID of a cell to which the RNC belongs.
  • the eNB of the LTE system is an anchor point, the primary RAT link is an L link, and the secondary RAT link is a U link; when the primary RAT link is switched, and the secondary RAT link is not switched, the first link is an L link.
  • the second link is a U link; the target RAN node corresponding to the first link is the target eNB, and the source RAN node corresponding to the first link is the source eNB.
  • the second link information is U link information, for example, the U link information may be: an RNC identifier RNC ID or a cell identifier Cell ID of a cell to which the RNC belongs.
  • the eNB of the LTE system is an anchor point, the primary RAT link is an L link, and the secondary RAT link is a U link; when the primary RAT link is not switched, and the secondary RAT link is switched, the first link is a U chain.
  • the second link is the L link; the target RAN node corresponding to the first link is the target RNC, and the source RAN node corresponding to the first link is the source RNC.
  • the second link information is L link information, for example, the L link information may be an eNB identity Identity or a cell ID (cell ID) of a cell where the eNB is located.
  • the anchor For the downlink direction, the anchor is responsible for receiving data from the core network to which the anchor belongs and is responsible for distributing the carriers on two different RATs. For the uplink direction, the anchor is responsible for transmitting data of the same UE on two different RAT carriers. Aggregate and send to the core network node to which the anchor belongs.
  • the RAN nodes corresponding to the first link are the source anchor point and the target anchor point respectively.
  • the RAN node corresponding to the second link is a secondary RAN node; when the secondary RAT is switched, the first link corresponds to The RAN node is a source secondary RAN node and a target secondary RAN node, respectively, and the RAN node corresponding to the second link is an anchor point.
  • the second link information may be directly transmitted through the interface, and the source RAN node may also send the second link information to the target RAN node through the core network.
  • the source RAN node may send the second link information to the target RAN node through the core network.
  • the source RAN node of the first link needs to simultaneously transmit the target cell information and the second link information of the first link to the destination RAN node of the first link.
  • the information of the second link may include source link information of the second link and/or destination link information of the second link.
  • the source link information refers to the information of the link to which the current serving cell of the mobile station belongs before the cell handover or link reconfiguration process occurs.
  • the destination link information refers to the information of the link to which the mobile station serving cell belongs after the cell handover or link reconfiguration process occurs.
  • the link information may include one of the following information or any combination of more than one of the following: a cell identity (CGI), or a RAN node identity (eNB id or RNC identity), or a link identity.
  • the target RAN node corresponding to the first link establishes a connection of the RAN node corresponding to the second link according to the second link information, to perform data transmission.
  • the RAN node corresponding to the first link is a link control node (for example, RNC) of the UMTS system
  • the RAN node corresponding to the second link is a link control node (for example, an eNB) of the LTE system.
  • the RAN node corresponding to the first link is a link control node (for example, an eNB) of the LTE system
  • the RAN node corresponding to the second link is a link control node (for example, an RNC) of the UMTS system.
  • the target RAN node may send a connection establishment indication to the RAN node of the second link (Connection Setup Indication message to trigger the operation of the lue interface; otherwise, the target RAN node may send a Connection Setup Request message to the RAN node of the second link, and receive the RAN node returned by the second link.
  • the Connection Setup Response message is used to establish the lue interface.
  • the source RAN node of the first link may determine that the RAN node that can continue to use the multi-RAT link carrier aggregation as the target RAN node of the first link;
  • the source RAN node of the path sends a message carrying the second link information to the target RAN node of the first link, so that the target RAN node corresponding to the first link and the RAN node corresponding to the second link Data transfer is performed after the connection is established.
  • the source RAN node of the first link may use the RAN node of the first link having carrier aggregation capability and having an interface with the RAN node of the second link as the target RAN node of the first link.
  • the target RAN node of the first link and the RAN node of the second link can normally transmit data during handover. Guarantee the continuity of service transmission throughput.
  • FIG. 2 is a schematic flowchart of a method for switching a multi-carrier according to another embodiment of the present invention.
  • the application scenario of this embodiment is as follows: RNC is an anchor point, a primary RAT link (U link), and a secondary RAT link (L) Link) No handover; there is no Iur interface between RNCs, and information needs to be transmitted through the Iu interface between the RNC and the core network; the target RNC decides whether to continue to use multi-RAT carrier aggregation (U&L Boosting).
  • U&L Boosting multi-RAT carrier aggregation
  • the multi-link switching method of this embodiment may be as follows.
  • the UE sends an RRC Measurement Report to the source RNC.
  • the source RNC performs a relocation decision.
  • the source RNC finds that there are different RNC cells stronger than the signal of the source RNC cell according to the signal strength in the RRC measurement report, and when the handover condition is satisfied, it is determined that the handover is performed.
  • the source RNC sends a message carrying the L link information to the SGSN, for example, a Relocation Required message, where the L link information, for example, the eNB ID or the cell ID of the L link, is carried.
  • the SGSN sends a message carrying the L link information to the target RNC (Target RNC), for example, a Relocation Request message, where the L link information is carried.
  • Target RNC target RNC
  • the target RNC decides whether to continue to provide multi-RAT carrier aggregation service transmission to the UE. Specifically, the target RNC may determine whether to continue carrier aggregation according to its own multi-RAT link carrier aggregation capability information, whether it has an interface with the eNB, and the load condition of the target cell.
  • the target RNC sends a Relocation Failure message to the SGSN, which carries the cause value: the target cell is congested.
  • the SGSN sends a Relocation Preparation Failure message to the source RNC, where the reason value is carried, for example, the target cell is congested.
  • an interface between the RNC and the eNB such as an Iue interface, may be established.
  • the target RNC sends a request message for establishing an interface, such as a Connection Setup Request message, to the eNB.
  • the eNB sends a corresponding response message to the target RNC, such as a Connection Setup Response message.
  • the target RNC establishes a signaling connection with the eNB.
  • the L link may be deactivated.
  • the eNB may send a deactivated L link indication to the UE to avoid L link data loss, so as to avoid the new connection establishment process. The phenomenon of data loss or the process of switching.
  • the target RNC sends the indication information that carries the carrier aggregation to the SGSN, and carries the cause value when not available, such as the RNC does not support the U & L carrier aggregation, the target RNC has no interface with the eNB (the hardware does not support), the resource is insufficient, and the like. Messages, such as Relocation Request Acknowledge messages.
  • the SGSN sends a message carrying the indication information to the source RNC, for example, a Relocation Command message.
  • the source RNC decides whether to delete the L carrier according to the indication information, and reconfigures the U carrier. For example, when the indication information indicates that carrier aggregation is not supported, the L carrier is deleted. When the L carrier is deleted, the source RNC sends an E-RAB release Indication message to the eNB, where the indication information is carried. The bearer release process (E-RAB release) is performed between the eNB and the UE.
  • E-RAB release is performed between the eNB and the UE.
  • the source RNC then transmits the data to the target RNC (Start Data Forwarding).
  • the source RNC sends a request message for releasing the resource to the eNB, for example, a Connection Release Request message.
  • the eNB returns a corresponding response message to the source RNC, such as a Connection Release Response message.
  • the source RNC sends a physical channel reconfiguration to the UE (Physical Channel
  • the steps 211-212 may be after step 213. Therefore, after the L1 synchronization is implemented, the connection between the source RNC and the eNB is deleted, so as to avoid the synchronization failure, the new link establishment is unsuccessful, and the data lost or dropped due to the deletion of the original link.
  • the layer 1 synchronization process can be performed between the UE, the source RNC and the target RNC (L1).
  • Synchronization and reception of NBAP RL Restore indication ).
  • the UE sends a Physical Channel Reconfiguration Complete (Physical Channel Reconfiguration Complete) message to the target RNC.
  • the target RNC sends a Relocation Detect message to the SGSN.
  • the target RNC sends a Relocation Complete message to the SGSN.
  • 217 The source RNC and the SGSN release the Iu interface signaling connection (Iu Release).
  • the source RNC sends the L link information to the target RNC through the core network.
  • the target RNC establishes a connection with the eNB to ensure continuity of data transmission throughput during handover.
  • FIG. 3 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention.
  • the application scenario of this embodiment is as follows: RNC is an anchor, a primary RAT link (U link), and a secondary RAT link (L). Link) does not switch; there is no lur interface between RNCs, and information needs to be transmitted through the Iu interface between the RNC and the core network; the source RNC determines that the carrier aggregation (U&L Boosting) and the RNC with the interface with the eNB can continue to be used as the target RNC. .
  • U&L Boosting carrier aggregation
  • the multi-link switching method of this embodiment may be as follows.
  • the UE sends an RRC measurement 4 report to the source RNC (Source RNC) (RRC Measurement
  • the source RNC searches for an RNC that has an interface with the eNB and supports carrier aggregation according to the OAM configuration as a target RNC for U carrier handover, and performs a relocation decision.
  • the source RNC sends a message carrying the L link information, for example, the eNB ID or the cell ID of the L link, for example, a Relocation Required message to the SGSN.
  • the SGSN sends a message carrying the L link information, such as a Relocation Request message, to the target RNC.
  • the target RNC decides whether to continue to provide the multi-RAT carrier aggregation service transmission to the UE according to the load condition of the target cell.
  • the target RNC sends a Relocation Failure message to the SGSN, where the reason value is carried: the target cell is congested.
  • the SGSN sends a Relocation Preparation Failure message to the source RNC, where the reason value is carried, for example, the target cell is congested.
  • the UE may be configured to trigger the Iue interface signaling connection when continuing to use the multi-RAT carrier aggregation:
  • the target RNC sends a message to the eNB for triggering the operation of the interface, such as a Connection Setup Indication message.
  • the L link may be deactivated.
  • the eNB may send a deactivated L link indication to the UE to avoid L link data loss, so as to avoid data loss during the establishment of the new connection. Phenomenon or the process of switching.
  • the target RNC sends an indication to the SGSN whether the carrier aggregation can continue to be used. When not available, the RNC carries a cause value, such as a message with insufficient resources, such as a Relocation Request Acknowledge message.
  • the SGSN sends a message carrying the indication information to the source RNC, for example, a Relocation Command message.
  • the source RNC decides whether to delete the L carrier according to the indication information, and reconfigures the U carrier. For example, when the indication information indicates that carrier aggregation is not supported, the L carrier is deleted. When the L carrier is deleted, the source RNC sends an E-RAB release Indication message to the eNB, where the indication information is carried. The bearer release process (E-RAB release) is performed between the eNB and the UE.
  • E-RAB release is performed between the eNB and the UE.
  • the source RNC then transmits the data to the target RNC (Start Data Forwarding).
  • the source RNC sends a message to the eNB for releasing the resource, such as a Connection Release Request message.
  • the eNB returns a corresponding response message to the source RNC, such as a Connection Release Response message.
  • the source RNC sends a physical channel reconfiguration to the UE (Physical Channel
  • the steps 310-311 may be after step 312.
  • the synchronization fails to establish a new link, and the data is lost or dropped due to the deletion of the original link.
  • the L1 Synchronization and reception of NBAP (RL Restore indication) can be performed between the UE, the source RNC, and the target RNC.
  • the UE sends a Physical Channel Reconfiguration Complete (Physical Channel Reconfiguration Complete) message to the target RNC.
  • Physical Channel Reconfiguration Complete Physical Channel Reconfiguration Complete
  • the target RNC sends a Relocation Detect message to the SGSN.
  • 315 The target RNC sends a Relocation Complete message to the SGSN.
  • 316 The source RNC and the SGSN release the Iu interface signaling connection (Iu Release).
  • the source RNC sends the L link information to the target RNC through the core network.
  • the target RNC establishes a connection with the eNB to ensure continuity of data transmission throughput during handover.
  • the source RNC determines whether the other RNC has an interface with the eNB as the handover target RNC, and avoids the secondary link deletion process caused by the target RNC not supporting UL Boosting with the local eNB, and reduces the handover preparation delay and saves the letter. Make the cost.
  • FIG. 4 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention.
  • the application scenario of this embodiment is as follows: RNC is an anchor point, a primary RAT link (U link), and a secondary RAT link (L Link) does not switch; there is a lur interface between RNCs, which can transmit information through the lur interface between RNCs.
  • the multi-link switching method of this embodiment may be as follows.
  • the UE sends an RRC Measurement Report to the source RNC.
  • the source RNC performs a relocation decision.
  • the source RNC finds that there are different RNC cells stronger than the signal of the source RNC cell according to the signal strength in the RRC measurement report, and when the handover condition is satisfied, it is determined that the handover is performed.
  • the source RNC sends an eNB carrying L link information, for example, an L carrier, to the target RNC.
  • L link information for example, an L carrier
  • a message of ID or cell ID such as an Enhanced Relocation Request message.
  • the target RNC decides whether to continue to provide multi-RAT carrier aggregation service transmission to the UE. Specifically, the target RNC may decide whether to continue to provide multi-RAT carrier aggregation service transmission to the UE according to its own carrier aggregation capability information, whether the interface exists with the eNB, and the load condition of the target cell.
  • the target RNC sends an enhanced Relocation Preparation Failure message to the source RNC, which carries the cause value, for example, the target cell is congested.
  • an Iue can be established:
  • the target RNC sends a request message for establishing an interface, such as a Connection Setup Request message, to the eNB.
  • the eNB sends a corresponding response message to the target RNC, such as a Connection Setup Response message.
  • the target RNC establishes a signaling connection with the eNB.
  • the L link may be deactivated.
  • the eNB may send a deactivation L link indication to the UE to avoid L link data loss, so as to avoid the new connection establishment process.
  • the target RNC sends, to the source RNC, indication information about whether the carrier aggregation can continue to be used, and carries the cause value when not available, for example, the RNC does not support U&L carrier aggregation, the target RNC has no interface with the eNB, and the resource is insufficient, for example, Enhanced Relocation Response (Enhanced Relocation Response) message.
  • Enhanced Relocation Response Enhanced Relocation Response
  • the source RNC decides whether to delete the L carrier according to the indication information, and reconfigures the U carrier. For example, when the indication information indicates that carrier aggregation is not supported, the L carrier is deleted. When the L carrier is deleted, the source RNC may send an E-RAB release indication (E-RAB release Indication) message to the eNB, where the indication information is carried. Bearer release process between the eNB and the UE (E-RAB release).
  • E-RAB release Indication E-RAB release Indication
  • the source RNC then transmits the data to the target RNC (Start Data Forwarding).
  • the source RNC sends a request message for releasing the resource to the eNB, for example, a Connection Release Request message.
  • the eNB returns a corresponding response message to the source RNC, such as a connection release response.
  • the source RNC sends a Physical Channel Reconfiguration message to the UE.
  • steps 409-410 may be after step 411. Therefore, after the L1 synchronization is implemented, the connection between the source RNC and the eNB is deleted, so as to avoid the synchronization failure, the new link establishment is unsuccessful, and the data lost or dropped due to the deletion of the original link.
  • the source RNC sends a message carrying the synchronization information of the aggregated data packet to the target RNC, for example, a Relocation Commit message.
  • the SGSN sends downlink data (Downlink Data) to the source RNC.
  • Downlink Data Downlink Data
  • the layer 1 synchronization process can be performed between the UE, the source RNC and the target RNC (L1).
  • the UE sends a Physical Channel Reconfiguration Complete (Physical Channel Reconfiguration Complete) message to the target RNC.
  • Physical Channel Reconfiguration Complete Physical Channel Reconfiguration Complete
  • the target RNC sends an Enhanced Relocation Complete Request message to the SGSN.
  • the target RNC sends an Enhanced Relocation Complete Response message to the SGSN.
  • the target RNC sends a resource release message (Resource Release) to the source RNC.
  • the target RNC decision is taken as an example.
  • the source RNC may also determine the RNC that can support the aggregation and the interface with the eNB as the target RNC. In this case, the target RNC needs to send the connection establishment indication message to the eNB. , signaling savings can be achieved.
  • the source RNC sends the L link information to the target RNC through the interface between the RNCs. When the U link is switched, the target RNC establishes a connection with the eNB to ensure continuity of data transmission throughput during handover.
  • FIG. 5 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention.
  • the application scenario of this embodiment is as follows: an eNB is an anchor point, a primary RAT link (L link), and a secondary RAT link (U). Link) does not switch; there is an X2 interface between eNBs, and information can be transmitted through the X2 interface between eNBs.
  • the multi-link switching method of this embodiment may be as follows.
  • the UE sends an RRC Measurement Report to the source eNB (Source eNB).
  • the source eNB performs a handover decision.
  • the source eNB finds that there are different eNB cells stronger than the signal of the source eNB cell according to the signal strength in the RRC measurement report, and when the handover condition is met, it is determined that the handover is performed.
  • the source eNB sends a message carrying the U link information, for example, the RNC ID or the cell ID of the U carrier, for example, a Handover Request message to the target eNB.
  • the target eNB decides whether to continue to provide the multi-RAT carrier aggregation service transmission to the UE. Specifically, the target eNB may decide whether to continue to provide multi-RAT carrier aggregation service transmission to the UE according to its own carrier aggregation capability information, whether the RNC has an interface with the RNC, and the load condition of the target cell.
  • the target eNB sends a Handover Relocation Preparation Failure message to the source eNB, which carries a cause value, for example, the target cell is congested.
  • an Iue can be established:
  • the target eNB sends a request message for establishing an interface to the RNC, such as a Connection Setup Request message.
  • the RNC sends a corresponding response message to the target eNB, for example, a connection establishment response. ( Connection Setup Response ) message.
  • the target eNB establishes a signaling connection with the RNC.
  • the U link may be deactivated.
  • the deactivated U link indication may be sent by the RNC to the UE to avoid U link data loss, so as to avoid the new connection establishment process.
  • the target eNB sends, to the source eNB, indication information that carries the carrier aggregation, and carries the cause value when not available, for example, the eNB does not support U&L carrier aggregation, the target eNB has no interface with the RNC, and the resource is insufficient, for example, Handover Request Acknowledge message.
  • the source RNC decides whether to delete the U carrier according to the indication information, and reconfigures the L carrier. For example, when the indication information indicates that carrier aggregation is not supported, the U carrier is deleted. When the U carrier is deleted, the source eNB sends an E-RAB release Indication message to the RNC, where the indication information is carried. The bearer release process (E-RAB release) between the RNC and the UE.
  • E-RAB release The bearer release process between the RNC and the UE.
  • the source eNB sends an RRC connection reconfiguration to the UE (RRC Connection
  • the source eNB then transmits the data to the target eNB (Data Forwarding).
  • the source eNB sends a request message for releasing the resource to the RNC, such as a Connection Release Request message.
  • the RNC returns a corresponding response message to the source eNB, such as a connection release response.
  • a Layer 1 synchronization procedure (L1 Synchronization) can be performed between the UE, the source eNB, and the target eNB.
  • the UE sends an RRC Connection Reconfiguration Complete (RRC Connection Reconfiguration Complete) message to the target eNB.
  • RRC Connection Reconfiguration Complete RRC Connection Reconfiguration Complete
  • This embodiment takes the target eNB decision as an example, similar to the third embodiment, and may also be performed by the source eNB.
  • the eNB that can support the aggregation and the interface with the RNC is used as the target eNB.
  • the target eNB needs to send a connection establishment indication message to the RNC, which can implement signaling saving.
  • the source eNB sends the U link information to the target eNB through the interface between the eNBs.
  • the target eNB establishes a connection with the RNC to ensure continuity of data transmission throughput during handover.
  • FIG. 6 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention.
  • the application scenario of this embodiment is as follows: an eNB is an anchor, a primary RAT link (L link), and a secondary RAT link (U Link) does not switch; there is no X2 interface between eNBs, and information needs to be transmitted through the S1 interface between the eNB and the core network.
  • L link primary RAT link
  • U Link secondary RAT link
  • the multi-link switching method of this embodiment may be as follows.
  • the UE sends an RRC Measurement Report to the source eNB.
  • the source eNB performs a handover decision.
  • the source eNB sends a message carrying the U link information, for example, the RNC ID or the cell ID of the U link to the MME, for example, a Handover Required message.
  • the MME sends a message carrying the U link information to the target eNB (Target eNB), for example, a 3 ⁇ 4 port handover request (Handover Request) message.
  • Target eNB target eNB
  • Handover Request 3 ⁇ 4 port handover request
  • the target eNB decides whether to continue to provide the multi-RAT carrier aggregation service transmission to the UE. Specifically, the target eNB may decide whether to continue to provide multi-RAT carrier aggregation service transmission to the UE according to its own carrier aggregation capability information, whether the RNC has an interface with the RNC, and the load condition of the target cell.
  • the target eNB sends a Handover Relocation Preparation Failure message to the source eNB, which carries a cause value, for example, the target cell is congested.
  • Iue can be established: 606: The target eNB sends a request message for establishing an interface, such as a Connection Setup Request message, to the RNC.
  • the RNC sends a corresponding response message to the target eNB, such as a Connection Setup Response message.
  • the target eNB establishes a logical connection with the RNC.
  • the U link may be deactivated.
  • the deactivated U link indication may be sent by the RNC to the UE to avoid U link data loss, so as to avoid the new connection establishment process.
  • the target eNB sends the indication information that carries the carrier aggregation to the MME, and carries the cause value when not available, for example, the eNB does not support the U & L carrier aggregation, the target eNB has no interface with the RNC, and the resource is insufficient, such as switching. Request Answer (Acknowledge) message.
  • the MME sends a message carrying the indication information to the source eNB, for example, a handover command message, where the indication information is the indication information in step 608.
  • the source RNC decides whether to delete the U carrier according to the indication information, and reconfigures the L carrier. For example, when the indication information indicates that carrier aggregation is not supported, the U carrier is deleted. When the U carrier is deleted, the source eNB sends an E-RAB release Indication message to the RNC, where the indication information is carried. The bearer release process (E-RAB release) between the RNC and the UE.
  • E-RAB release The bearer release process between the RNC and the UE.
  • the source eNB sends an RRC connection reconfiguration to the UE (RRC Connection
  • the source eNB then transmits the data to the target eNB (Data Forwarding).
  • the source eNB sends a request message for releasing the resource to the RNC, for example, a Connection Release Request message.
  • the RNC returns a corresponding response message to the source eNB, such as a connection release response.
  • L1 Synchronization (Connection Release Response ) message. Thereafter, a Layer 1 synchronization procedure (L1 Synchronization) can be performed between the UE, the source eNB, and the target eNB.
  • the UE sends an RRC Connection Reconfiguration Complete (RRC Connection Reconfiguration Complete) message to the target eNB.
  • RRC Connection Reconfiguration Complete RRC Connection Reconfiguration Complete
  • the target eNB sends a Handover Notify message to the MME.
  • the present embodiment takes the target eNB as an example. Similar to the third embodiment, the source eNB may determine the eNB that can support the aggregation and the interface with the RNC as the target eNB. In this case, the target eNB needs to send the connection establishment indication message to the RNC. , signaling savings can be achieved.
  • the source eNB sends the U link information to the target eNB through the core network.
  • the target eNB establishes a connection with the RNC to ensure continuity of data transmission throughput during handover.
  • FIG. 7 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention.
  • the application scenario of this embodiment is as follows: RNC is an anchor point, a primary RAT link (U link) is not switched, and a secondary RAT link is used. (L link) handover; there is an X2 interface between eNBs, and information can be transmitted through the X2 interface between eNBs; handover control is performed by non-anchor points (eNBs).
  • eNBs non-anchor points
  • the multi-link switching method of this embodiment may be as follows.
  • the UE sends an RRC Measurement Report to the source eNB.
  • the source eNB performs a handover decision.
  • the source eNB sends a message carrying the U link information, for example, the RNC ID or the cell ID of the U carrier, for example, a Handover Request message to the target eNB.
  • the target eNB decides whether to continue to provide multi-RAT carrier aggregation service transmission to the UE. Specifically, the target eNB may decide whether to continue to provide multi-RAT carrier aggregation service transmission to the UE according to its own carrier aggregation capability information, whether the interface between itself and the RNC exists, and the load condition of the target cell. Different from the primary link handover shown in FIG. 2-6, since the present embodiment is a secondary link handover, in order to save resources, it is possible to continue switching only when the target eNB and the RNC have an interface and have carrier capability, otherwise Returns a failure response.
  • the target eNB sends a message carrying the failure cause value to the source eNB, for example, a handover failure (Handover Failure) message carrying the cause value, for example, the target cell is congested. , does not support aggregation, no Iue interface, etc.
  • a handover failure Hawover Failure
  • the target eNB sends a message to the RNC that triggers the working of the interface, such as a Connection Setup Indication message, to trigger the Iue interface to work.
  • the U link may be deactivated during the execution of the step 705.
  • the deactivated U link indication may be sent by the RNC to the UE to avoid U link data loss, so as to avoid data loss during the establishment of the new connection. Phenomenon or the process of switching.
  • the target eNB sends a Handover Request Acknowledge message to the source eNB.
  • the source eNB sends an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message to the UE.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • the source eNB can then transmit the data to the target eNB (Data Forwarding).
  • the source eNB sends a request message for releasing the resource to the RNC, such as a Connection Release Request message.
  • the RNC returns a corresponding response message to the source eNB, such as a Connection Release Response message.
  • a Layer 1 synchronization procedure (L1 Synchronization) can be performed between the UE, the source eNB, and the target eNB.
  • the UE sends an RRC Connection Reconfiguration Complete (RRC Connection Reconfiguration Complete) message to the target eNB.
  • RRC Connection Reconfiguration Complete RRC Connection Reconfiguration Complete
  • the source eNB sends the U link information to the target eNB through the interface between the eNBs.
  • the target eNB establishes a connection with the RNC to ensure the number of handover hours. According to the continuity of transmission throughput.
  • FIG. 8 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention.
  • the application scenario of this embodiment is as follows: RNC is an anchor point, a primary RAT link (U link) is not switched, and a secondary RAT link is used. Link) handover; there is no X2 interface between eNBs, and information needs to be transmitted through the S1 interface between the eNB and the core network; handover control is performed by non-anchor points (eNBs).
  • eNBs non-anchor points
  • the method for switching multiple links in this embodiment may be as follows.
  • the UE sends an RRC Measurement Report to the source eNB.
  • the source eNB performs a handover decision.
  • the source eNB sends a message carrying the U link information, for example, the RNC ID or the cell ID of the U link to the MME, for example, a Handover Required message.
  • the MME sends a message carrying the U link information to the target eNB (Target eNB), for example, a 3 ⁇ 4 port handover request (Handover Request) message.
  • Target eNB target eNB
  • Handover Request 3 ⁇ 4 port handover request
  • the target eNB decides whether to continue to provide the multi-RAT carrier aggregation service transmission to the UE. Specifically, the target eNB may decide whether to continue to provide multi-RAT carrier aggregation service transmission to the UE according to its own carrier aggregation capability information, whether the RNC has an interface with the RNC, and the load condition of the target cell.
  • the present embodiment is a secondary link handover, in order to save resources, it is possible to continue switching only when the target eNB and the RNC have an interface and have carrier capability, otherwise Returns a failure response. That is, if the current load is overloaded, does not have the aggregation capability, and the interface does not exist, the target eNB sends a message carrying the failure cause value to the MME, for example, a Handover Preparation Failure message carrying the cause value, for example, the target cell. Congestion, no aggregation support, no Iue interface, etc. Afterwards, the MME sends a Handover Failure message to the source base station, where the above failure reason is carried.
  • the target eNB sends a message to the RNC for triggering the working of the interface, for example, connection establishment.
  • a Connection Setup Indication message is triggered to trigger the Iue interface to work.
  • the target eNB sends a handover request response to the MME (Handover Request)
  • the MME sends a Handover Command message to the source eNB.
  • the source eNB sends an RRC connection reconfiguration to the UE (RRC Connection
  • the source eNB sends a Connection Release Request message to the RNC.
  • the RNC returns a Connection Release Response message to the source eNB.
  • a Layer 1 synchronization procedure (L1 Synchronization) can be performed between the UE, the source eNB, and the target eNB.
  • the UE sends an RRC Connection Reconfiguration Complete message to the target eNB.
  • the target eNB sends a Handover Notify message to the MME.
  • the source eNB sends the U link information to the target eNB through the core network.
  • the target eNB establishes a connection with the RNC to ensure continuity of data transmission throughput during handover.
  • FIG. 9 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention.
  • the application scenario of this embodiment is as follows: an eNB is an anchor point, a primary RAT link (L link) is not switched, and a secondary RAT link is used. U link) handover; there is no Iur interface between RNCs, and information needs to be transmitted through the Iu interface between the RNC and the core network; handover control is performed by non-anchor points (eNBs).
  • eNBs non-anchor points
  • the multi-link switching method of this embodiment may be as follows.
  • the UE sends an RRC measurement 4 report to the source RNC (Source RNC) (RRC Measurement
  • the source RNC performs a relocation decision.
  • step 202 For details, see step 202.
  • the source RNC sends a message carrying the L link information, for example, the eNB ID or the cell ID of the L link, for example, a Relocation Required message to the SGSN.
  • the SGSN sends a message carrying the L link information, such as a Relocation Request message, to the target RNC.
  • the target RNC decides whether to continue to provide multi-RAT carrier aggregation service transmission to the UE. Specifically, the target RNC may decide whether to continue to provide multi-RAT carrier aggregation service transmission to the UE according to its own carrier aggregation capability information, whether it has an interface with the eNB, and its current load condition.
  • the present embodiment is a secondary link handover, in order to save resources, it is possible to continue switching only when the target RNC has an interface with the eNB and has carrier capability. Returns a failure response. That is, if the current load is overloaded, has no aggregation capability, and no interface exists, the target RNC sends a message carrying the failure cause value to the SGSN, for example, a Relocation Failure message carrying the cause value, for example, the target eNB is congested. The SGSN sends a Relocation Preparation Failure message to the source RNC, and the above-mentioned failure cause value is carried.
  • the target RNC sends a message to the eNB for triggering the operation of the interface, such as a Connection Setup Indication message.
  • the L link may be deactivated.
  • the eNB may send a deactivated L link indication to the UE to avoid L link data loss, so as to avoid data loss during the establishment of the new connection. Phenomenon or the process of switching.
  • the target RNC sends a Relocation Request Acknowledge message to the SGSN.
  • the SGSN sends a Relocation Command message to the source RNC.
  • the source RNC then transmits the data to the target RNC (Start Data Forwarding).
  • the source RNC sends a request message for releasing the resource to the eNB, such as a Connection Release Request message.
  • the eNB returns a corresponding response message to the source RNC, such as a Connection Release Response message.
  • the source RNC sends a physical channel reconfiguration to the UE ( Physical Channel
  • steps 909-910 may be after step 911. Therefore, after the L1 synchronization is implemented, the connection between the source RNC and the eNB is deleted, so as to avoid the synchronization failure, the new link establishment is unsuccessful, and the data lost or dropped due to the deletion of the original link.
  • the layer 1 synchronization process can be performed between the UE, the source RNC and the target RNC (L1).
  • the UE sends a physical channel reconfiguration complete (Physical Channel Reconfiguration Complete) message to the target RNC.
  • a physical channel reconfiguration complete Physical Channel Reconfiguration Complete
  • the target RNC sends a Relocation Detect message to the SGSN.
  • 914 The target RNC sends a Relocation Complete message to the SGSN.
  • the source RNC sends the L link information to the target RNC through the core network.
  • the target RNC establishes a connection with the eNB to ensure continuity of data transmission throughput during handover.
  • FIG. 10 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention.
  • the application scenario of this embodiment is as follows: an eNB is an anchor point, a primary RAT link (L link) is not switched, and a secondary RAT link is used. U link) handover; there is a lur interface between RNCs, which can transmit information through the lur interface between RNCs; and handover control by non-anchor points (eNBs).
  • the multi-link switching method of this embodiment may be as follows.
  • the UE sends an RRC Measurement Report to the source RNC (Source RNC) (RRC
  • Measurement Report 1002: The source RNC performs a relocation decision.
  • step 202 For details, see step 202.
  • the source RNC sends a message carrying the L link information, for example, the eNB ID or the cell ID of the L carrier, for example, an Enhanced Relocation Request message to the target RNC.
  • L link information for example, the eNB ID or the cell ID of the L carrier
  • Step 1004 The target RNC decides whether to continue to provide the multi-RAT carrier aggregation service transmission to the UE.
  • the target RNC may decide whether to continue to provide multi-RAT carrier aggregation service transmission to the UE according to its own carrier aggregation capability information, whether the interface exists with the eNB, and the load condition of the target cell.
  • the present embodiment is a secondary link handover, in order to save resources, it is possible to continue switching only when the target RNC has an interface with the eNB and has carrier capability. Returns a failure response. That is, if the current load is overloaded, has no aggregation capability, and no interface exists, the target RNC sends a message carrying the failure cause value to the SGSN, for example, a Relocation Failure message carrying the cause value, for example, the target eNB is congested. The SGSN sends a Relocation Preparation Failure message to the source RNC, and the above-mentioned failure cause value is carried.
  • the target RNC sends a message to the eNB for triggering the operation of the interface, such as a Connection Setup Indication message.
  • the L link may be deactivated.
  • the eNB may send a deactivated L link indication to the UE to avoid L link data loss, so as to avoid data loss during the establishment of the new connection. Phenomenon or the process of switching.
  • the target RNC sends an Enhanced Relocation Response message to the source RNC.
  • the source RNC then transmits the data to the target RNC (Start Data Forwarding).
  • the source RNC sends a request message for releasing the resource to the eNB, for example, the connection is released.
  • Request Connection Release Request
  • the eNB returns a corresponding response message to the source RNC, such as a Connection Release Response message.
  • the source RNC sends a Physical Channel Reconfiguration message to the UE.
  • steps 1007-1008 can be after step 1009.
  • the synchronization fails to establish a new link, and the data is lost or dropped due to the deletion of the original link.
  • the source RNC sends a message carrying the synchronization information of the aggregated data packet to the target RNC, for example, a 3 ⁇ 4 port relocation Commit message.
  • the SGSN sends downlink data (Downlink Data) to the source RNC.
  • Downlink Data Downlink Data
  • the L1 Synchronization and reception of NBAP (RL Restore indication) can be performed between the UE, the source RNC, and the target RNC.
  • the UE sends a Physical Channel Reconfiguration Complete (Physical Channel Reconfiguration Complete) message to the target RNC.
  • Physical Channel Reconfiguration Complete Physical Channel Reconfiguration Complete
  • the target RNC sends an Enhanced Relocation Complete Request message to the SGSN.
  • the target RNC sends an Enhanced Relocation Complete Response message to the SGSN.
  • the target RNC sends a resource release message (Resource Release) to the source RNC.
  • the source RNC sends the L link information to the target RNC through the interface between the RNCs.
  • the target RNC establishes a connection with the eNB to ensure continuity of data transmission throughput during handover.
  • Figure 7-10 shows the switching control with non-anchor points during switching.
  • switching can also be performed with the anchor point as the switching control.
  • the RAN node corresponding to the second link is an anchor point of the carrier data offloading/aggregation control
  • the RAN node corresponding to the first link is the RAN node of the secondary link
  • the method includes: The anchor point of the carrier data offloading/aggregation control corresponding to the second link determines the RAN node of the target secondary link corresponding to the first link; the anchor point sends the RAN node information of the target secondary link to the first link And corresponding to the RAN node of the source secondary link, to establish a connection with the RAN of the target secondary link by using the RAN node of the source secondary link.
  • FIG. 11 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention.
  • the application scenario of this embodiment is as follows:
  • the application scenario of this embodiment is as follows:
  • RNC is an anchor point, and a primary RAT link (U link) No handover, secondary RAT link (L link) handover; handover control by anchor point (RNC).
  • the multi-link switching method of this embodiment may be as follows.
  • the UE sends an RRC Measurement Report to the RNC.
  • the RRC measurement report can be obtained by heterogeneous system measurement of the L carrier.
  • step 1101 can replace step 1101 with the following:
  • the UE sends an RRC measurement report to the source eNB, where the RRC measurement report can be obtained by intra-system measurement;
  • the source eNB determines the last cell based on the RRC measurement report, and then transmits a message to the RNC indicating the best cell, such as a Best Cell Indicator.
  • the RNC performs a relocation decision to determine the target eNB.
  • the RNC may determine the target eNB according to the RRC measurement report, and the target eNB has an interface with the RNC.
  • the target eNB is determined according to the best cell indication.
  • the RNC sends the target eNB information to the source cell, for example, the eNB of the target eNB.
  • the ID message such as a Handover Indication message.
  • steps 703-710 are performed thereafter.
  • 1104 If there is no X2 interface between the source eNB and the target eNB, the source eNB sends a message for handover to the RNC, such as a Handover Required message.
  • 1105 The RNC sends a request message for establishing an interface, such as a Connection Setup Request message, to the target eNB.
  • the target eNB decides whether to continue to provide the multi-RAT carrier aggregation service transmission to the UE. Specifically, the target eNB may decide whether to continue to provide the multi-RAT carrier aggregation service transmission to the UE according to the carrier aggregation capability information of the UE and the load condition of the target cell.
  • connection setup response (Connection Setup Response) message is sent.
  • connection between the target eNB and the RNC is initiated by the RNC, and similarly to the previous embodiment, the ID of the RNC is sent to the target eNB, and the connection establishment is initiated by the target eNB.
  • the RNC sends a message corresponding to the handover request to the source eNB, for example, a Handover Request Acknowledge message.
  • the source eNB sends an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message to the UE.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • the source eNB can then transmit the data to the target eNB (Data Forwarding).
  • the source eNB sends a request message for releasing the resource to the RNC, for example, a Connection Release Request message.
  • the RNC returns a corresponding response message to the source eNB, such as a Connection Release Response message.
  • the layer 1 synchronization process (L1) can be performed between the UE, the source eNB, and the target eNB.
  • the UE sends an RRC Connection Reconfiguration Complete (RRC Connection Reconfiguration Complete) message to the target eNB.
  • RRC Connection Reconfiguration Complete RRC Connection Reconfiguration Complete
  • the RNC initiates a connection establishment request to the target eNB, and establishes a connection between the target eNB and the RNC when the L link is switched, to ensure continuity of data transmission throughput during handover.
  • FIG. 12 is a schematic flowchart of a method for switching multiple carriers according to another embodiment of the present invention.
  • the application scenario of the example is as follows:
  • the application scenario of this embodiment is as follows:
  • eNB is an anchor point, a primary RAT link (L link) does not switch, and a secondary RAT link (U link) switches; is performed by an anchor point (eNB) Switch control.
  • the multi-link switching method of this embodiment may be as follows.
  • the UE sends an RRC Measurement Report to the eNB.
  • the RRC measurement report can be obtained by heterogeneous system measurement of the L carrier.
  • step 1201 can be replaced with the following:
  • the UE sends an RRC measurement report to the source RNC, where the RRC measurement report can be obtained by intra-system measurement;
  • the source RNC determines the last cell based on the RRC measurement report, and then transmits a message to the eNB indicating the best cell, such as a Best Cell Indicator.
  • the eNB performs a handover decision to determine a target RNC.
  • the eNB may determine the target RNC according to the RRC measurement report, and the target RNC has an interface with the eNB;
  • the target RNC is determined according to the best cell indication.
  • the eNB sends, to the source cell, a message carrying the target RNC information, for example, the RNC ID of the target RNC, for example, a Handover Indication message.
  • a message carrying the target RNC information for example, the RNC ID of the target RNC, for example, a Handover Indication message.
  • step 1003-1014 If there is an Iur interface between the source RNC and the target RNC, go to step 1003-1014.
  • the source RNC sends a message for handover to the eNB, such as a Handover Required message.
  • the eNB sends a request message for establishing an interface, such as a Connection Setup Request message, to the target RNC.
  • the target RNC decides whether to continue to provide multi-RAT carrier aggregation service transmission to the UE. Specifically, the target RNC may be based on its own carrier aggregation capability information and the target cell. The load condition determines whether to continue to provide multi-RAT carrier aggregation service transmission to the UE.
  • connection setup response Connection Setup Response
  • the connection between the target RNC and the eNB is initiated by the eNB, and similarly to the previous embodiment, the ID of the eNB is sent to the target RNC, and the connection establishment by the target RNC is initiated.
  • the eNB sends a message corresponding to the handover request to the source RNC, for example, a Handover Request Acknowledge message.
  • the source RNC sends a Physical Channel Reconfiguration message to the UE.
  • the source eNB can then transmit the data to the target eNB (Data Forwarding).
  • the source RNC sends a message for releasing the resource to the eNB, such as a Connection Release Request message.
  • the eNB returns a corresponding response message to the source RNC, such as a Connection Release Response message.
  • the layer 1 synchronization process (L1 Synchronization) can be performed between the UE, the source RNC and the target RNC.
  • the UE sends a Physical Channel Reconfiguration Complete (Physical Channel Reconfiguration Complete) message to the target RNC.
  • Physical Channel Reconfiguration Complete Physical Channel Reconfiguration Complete
  • the target RNC sends a resource release message (Resource Release) to the source RNC.
  • the eNB initiates a connection establishment request to the target RNC, and establishes a connection between the target RNC and the eNB when the U link is switched, to ensure continuity of data transmission throughput during handover.
  • FIG. 13 is a schematic flowchart of a method for switching a multi-carrier according to another embodiment of the present invention.
  • the original U link is switched to the U link and the L link
  • the eNB is an anchor point.
  • the multi-link switching method of this embodiment may be as follows.
  • the UE sends an RRC Measurement Report to the RNC.
  • the RNC performs a relocation decision according to the dual-link carrier aggregation capability (U&L Boosting capability) of the RNC and whether the eNB has an interface.
  • U&L Boosting capability dual-link carrier aggregation capability
  • the RNC finds that there is an LTE cell stronger than the signal of the RNC cell according to the signal strength in the RRC measurement report, and the anchor point is an eNB.
  • the UE can be switched from the U single link to the UL Boosting in the handover process.
  • the scenario, and the original U link acts as a secondary carrier.
  • the RNC sends a message carrying the U link information to the CN, for example, a Relocation Required message, where the U link information, for example, the RNC ID or the cell ID of the U link is carried.
  • the CN sends a message carrying the U link information to the eNB, for example, a Handover Request message, where the U link information is carried.
  • the eNB decides whether to continue to use the carrier aggregation (U&LBoosting) according to the current load condition, and can use U&L Boosting to adjust the internal data allocation policy and the corresponding configuration function.
  • U&LBoosting carrier aggregation
  • the eNB sends a Handover Failure message to the CN, where the carrying cause value: the target cell is congested.
  • the CN sends a Relocation Preparation Failure message to the RNC, which carries the cause value, for example, the target cell is congested.
  • the eNB sends a message to the CN carrying indication information about whether the carrier aggregation can continue to be used, for example, a Handover Request Acknowledge message.
  • the CN sends a message to the RNC carrying an indication of whether the carrier aggregation can continue to be used, for example, a 3 ⁇ 4 port relocation command (Relocation Command) message.
  • Relocation Command 3 ⁇ 4 port relocation command
  • the RNC sends a Connection Setup Request to the eNB.
  • the eNB sends a Connection Setup Response message to the RNC.
  • the alternative steps 1308-1309 may also be determined at step 1305 to continue to use.
  • the eNB After carrier aggregation, the eNB sends a Connection Setup Indication message to the RNC.
  • the RNC reconfigures the U carrier according to whether the carrier aggregation indication can be continued.
  • 1311 The RNC sends a Physical Channel Reconfiguration message to the UE.
  • the LI Synchronization and reception of NBAP (RL Restore indication) can be performed between the UE, the RNC, and the eNB.
  • the UE sends a Physical Channel Reconfiguration Complete message to the eNB.
  • the eNB sends a Relocation Detect message to the CN.
  • the eNB sends a Relocation Complete message to the CN.
  • the RNC sends the U link information to the eNB through the core network.
  • the RNC establishes a connection with the eNB to ensure continuity of the handover data transmission throughput.
  • FIG. 14 is a schematic flowchart of a method for switching a multi-carrier according to another embodiment of the present invention.
  • the original L link is switched to the U link and the L link
  • the RNC is an anchor point.
  • the multi-link switching method of this embodiment can be as follows.
  • the UE sends an RRC Measurement Report to the eNB.
  • the eNB performs handover decision according to the known RNC U&L Boosting capability and whether the RNC is configured with an interface.
  • the eNB finds that there is an RNC cell that is stronger than the signal of the eNB cell according to the signal strength in the RRC measurement report.
  • the UE can perform the handover from the L single link to the UL Boosting scenario in the handover process, and the original L The link acts as a secondary carrier.
  • the eNB sends a message carrying the L link information to the CN, for example, a Handover Required message, where the L link information, for example, the eNB ID or the cell ID of the L link, is carried.
  • the CN sends a message carrying the L link information to the RNC, for example, a relocation request. (Relocation Request) message, which carries U link information.
  • the RNC decides whether to continue to use the carrier aggregation (U&LBoosting) according to the current load condition, and U&L Boosting can be used to adjust the internal data allocation policy and the corresponding configuration function.
  • U&LBoosting carrier aggregation
  • the RNC sends a relocation failure to the CN (Relocation).
  • the target cell is congested. Thereafter, the CN sends a Handover Preparation Failure message to the eNB, which carries the cause value, for example, the target cell is congested.
  • the RNC sends a Connection Setup Indication message to the eNB.
  • the RNC sends a message to the CN carrying the indication information of whether the carrier aggregation can continue to be used, for example, a Relocation Response message.
  • the CN sends a message to the eNB carrying indication information about whether the carrier aggregation can continue to be used, such as a Handover Command message.
  • the RNC reconfigures the L carrier according to whether the carrier aggregation indication information can be continued.
  • the eNB sends an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message to the UE.
  • the layer 1 synchronization process can be performed between the UE, the RNC and the eNB (L1).
  • the UE sends an RRC Connection Reconfiguration Complete message to the RNC.
  • the RNC sends a Handover Notify message to the CN.
  • FIG. 15 is a schematic flowchart of a multi-carrier handover method according to another embodiment of the present invention.
  • a primary link U link in dual-duplex is switched to an L-link, and converted to single-carrier transmission.
  • the UE originally performs data transmission under the dual load of the RNC as the anchor point. Later, the UMTS signal is degraded, but the L carrier signal is very good, and the data transmission can be satisfied under the single-carrier LTE. At this time, the UE can be realized through the different system handover process. Switch from U&L Boosting to L single-load scene.
  • the impact of this process on the existing protocol flow is that the target node of the existing UMTS to LTE inter-RAT handover needs to be set as the L carrier network control node.
  • the air interface reconfiguration process is delivered by the eNB to the UE.
  • Step 1501 The UE sends an RRC Measurement Report to the RNC.
  • the RNC performs a relocation decision, and the eNB of the L carrier is used as a handover target node of the different system.
  • the RNC sends a Relocation Required message to the CN.
  • the CN sends a Handover Request message to the eNB.
  • the eNB sends a Handover Request Acknowledge message to the CN.
  • the CN sends a Relocation Command message to the RNC.
  • the eNB sends an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message to the UE.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • the LI Synchronization and reception of NBAP (RL Restore indication) can be performed between the UE, the RNC, and the eNB.
  • the UE sends an RRC Connection Reconfiguration Complete message to the eNB.
  • the eNB sends a Connection Delete Request to the RNC.
  • the RNC sends a Connection Delete Response message to the eNB.
  • the eNB sends a Relocation Detect message to the CN.
  • the eNB sends a Relocation Complete message to the CN.
  • This embodiment is delivered to the UE by the eNB through the air interface reconfiguration process, and can be switched to the L link by the main link U link in the dual load, and converted into single carrier transmission to ensure the continuity of the service transmission throughput.
  • FIG. 16 is a schematic flowchart of a method for switching a multi-carrier according to another embodiment of the present invention.
  • the primary link U link in the dual-switch is switched to the L-link, and converted to single-carrier transmission.
  • the UE originally performs data transmission under the dual load of the RNC as the anchor point. Later, the UMTS signal is degraded, but the L carrier signal is very good, and the data transmission can be satisfied under the single-carrier LTE. At this time, the UE can be realized through the different system handover process. Switch from U&L Boosting to L single-load scene.
  • the impact of this process on the existing protocol flow is that the target node of the existing UMTS to LTE inter-RAT handover needs to be set as the L carrier network control node.
  • the air interface reconfiguration process is delivered by the eNB to the UE.
  • the multi-link switching method of this embodiment may be as follows.
  • 1601 The UE sends an RRC Measurement Report to the RNC.
  • 1602 The RNC performs a relocation decision, and the eNB of the L carrier is used as a handover target node of the different system.
  • the RNC sends a Relocation Required message to the eNB.
  • 1604 The eNB sends an S1 Setup Request (SI Setup Request) message to the CN.
  • the CN sends an S1 Setup Response (SI Setup Response) message to the eNB.
  • SI Setup Response S1 Setup Response
  • the eNB sends a Relocation Response message to the RNC.
  • 1607 The eNB sends an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message to the UE.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • the layer 1 synchronization process can be performed between the UE, the RNC and the eNB (LI Synchronization). And reception of NBAP: RL Restore indication ).
  • the UE sends an RRC Connection Reconfiguration Complete message to the eNB.
  • the eNB sends a Connection Delete Request to the RNC.
  • the RNC sends a Connection Delete Response message to the eNB.
  • the eNB is delivered to the UE by the air interface reconfiguration process, and can be switched to the L link by the main link U link in the dual load, and converted into a single carrier transmission.
  • FIG. 17 is a schematic flowchart of a method for switching a multi-carrier according to another embodiment of the present invention.
  • a primary link L link in dual-duplex is switched to a U-link, and converted to single-carrier transmission. Guarantee the continuity of service transmission throughput.
  • the UE originally performs data transmission under the dual load of the eNB as an anchor point, and then the LTE signal is deteriorated, but the U carrier signal is very good, and the data transmission can be satisfied under the single-load UMTS. At this time, the UE can be realized through the different system handover process. Switch from U&L Boosting to U single-load scene.
  • the impact of this process on the existing protocol flow is that the target node of the existing LTE to UMTS inter-RAT handover needs to be set as the U carrier network control node.
  • the air interface reconfiguration process is sent by the RNC to the UE.
  • the multi-link switching method of this embodiment can be as follows.
  • the UE sends an RRC Measurement Report to the eNB.
  • the eNB performs an inter-system handover decision.
  • the eNB sends a Handover Required message to the CN.
  • the CN sends a Relocation Request message to the RNC.
  • the RNC sends a Relocation Response message to the CN.
  • the CN sends a Handover Command message to the eNB.
  • RNC sends physical channel reconfiguration to the UE (Physical Channel Reconfiguration) message.
  • the layer 1 synchronization process (L1 Synchronization) can be performed between the UE, the RNC, and the eNB.
  • the UE sends a Physical Channel Reconfiguration Complete (Physical Channel Reconfiguration Complete) message to the RNC.
  • Physical Channel Reconfiguration Complete Physical Channel Reconfiguration Complete
  • the RNC sends a Connection Delete Request to the eNB.
  • the eNB sends a Connection Delete Response message to the RNC.
  • the RNC sends a Handover Notify message to the CN.
  • the RNC is sent to the UE through the air interface reconfiguration process, and can be switched to the U link by the main link L link in the dual load, and converted into single carrier transmission to ensure the continuity of the service transmission throughput.
  • FIG. 18 is a schematic flowchart of a method for switching a multi-carrier according to another embodiment of the present invention.
  • a primary link L link in a dual-carrier is switched to a U-link, and converted to a single-carrier transmission. Guarantee the continuity of service transmission throughput.
  • the UE originally performs data transmission under the dual load of the eNB as an anchor point, and then the LTE signal is deteriorated, but the U carrier signal is very good, and the data transmission can be satisfied under the single-load UMTS. At this time, the UE can be realized through the different system handover process. Switch from U&L Boosting to U single-load scene.
  • the impact of this process on the existing protocol flow is that the target node of the existing LTE to UMTS inter-RAT handover needs to be set as the U carrier network control node.
  • the air interface reconfiguration process is sent by the RNC to the UE.
  • the multi-link switching method of this embodiment may be as follows.
  • the UE sends an RRC Measurement Report to the eNB.
  • the eNB performs an inter-system handover decision.
  • the eNB sends a Handover Required message to the RNC.
  • the RNC sends a Handover Command message to the eNB.
  • 1805 The RNC sends a Physical Channel Reconfiguration message to the UE.
  • the layer 1 synchronization process (L1 Synchronization) can be performed between the UE, the RNC, and the eNB.
  • the UE sends a Physical Channel Reconfiguration Complete (Physical Channel Reconfiguration Complete) message to the RNC.
  • Physical Channel Reconfiguration Complete Physical Channel Reconfiguration Complete
  • the RNC sends a Connection Delete Request to the eNB.
  • the CN sends a Connection Delete Response to the RNC.
  • the CN sends an Enhanced Relocation Complete Request message to the RNC.
  • the RNC sends an Enhanced Relocation Complete Response message to the CN.
  • FIG. 19 is a schematic structural diagram of a multi-carrier switching apparatus according to an embodiment of the present invention, including a receiving module 191 and an establishing module 192.
  • the receiving module 191 is configured to receive a second link sent by a source RAN node corresponding to the first link.
  • the establishing module 192 is configured to establish, according to the second link information, a connection between the target RAN node corresponding to the first link and the RAN node corresponding to the second link, where the data is transmitted, where One link is a link in a first RAT network; the second link is a link in a second RAT network.
  • the receiving module 191 may be specifically configured to: receive, by using the core network and the Iu interface, the target RNC, the message that is sent by the source RNC, including the information of the LTE link; or, by using the Iur interface, the target RNC receives the LTE chain that is sent by the source RNC.
  • the target e NB receives the message including the UMTS link information sent by the source eNB; or The target eNB receives the message including the UMTS link information sent by the source eNB through the S1 interface and the core network; or the target BSC receives the message including the LTE link information sent by the source BSC through the Iur-g interface between the BSCs; Alternatively, the target BSC receives the message including the LTE link information sent by the source BSC through the core network and the A/Gb interface between the core network and the BSC.
  • the establishing module 192 may be specifically configured to establish, according to the second link information, the multi-RAT link carrier aggregation capability information, the interface status of the RAN node corresponding to the second link, and the current load situation.
  • the establishing module 192 includes a first unit 1921 and a second unit 1922; the first unit 1921 is configured to send a connection establishment request message to the RAN node corresponding to the second link; and the second unit 1922 is configured to receive the The connection establishment response message returned by the RAN node corresponding to the two links.
  • the establishing module 192 is specifically configured to send a connection establishment indication message to the RAN node corresponding to the second link, and directly establish a connection.
  • the device in this embodiment may further include a first sending module, where the first sending module is configured to send a handover request response message to the source RAN node, where the handover request response message includes an indication of whether to continue to use the multi-RAT link carrier aggregation. information.
  • the second sending module may be further configured to send a failure message to the source RAN node, where the failure cause value is carried, where the failure cause value includes: the target RAN node does not support multi-RAT link carrier aggregation, the target RAN node and the The RAN has no interface or insufficient resources corresponding to the two links, and may further include: a third sending module, configured to send a handover request response message to the source RAN node.
  • the first link target RAN node and the second link may be performed when the first link performs intra-system handover.
  • the RAN node normally transmits the multi-RAT aggregate data to ensure the continuity of the service transmission throughput.
  • FIG. 20 is a schematic structural diagram of a multi-carrier switching apparatus according to another embodiment of the present invention.
  • the RAN node corresponding to the second link is an anchor point of carrier data offloading/aggregation control
  • the RAN node corresponding to the first link is a RAN node of the secondary link
  • the device is located at the anchor point, where
  • the device includes a determining module 201 and a sending module 202; the determining module 201 is configured to determine a RAN node of the target secondary link corresponding to the first link; and the sending module 202 is configured to send the RAN node information of the target secondary link to the first
  • the RAN node of the source secondary link corresponding to the link establishes a connection with the RAN of the target secondary link by the RAN node of the source secondary link.
  • the determining module 201 may be specifically configured to determine, according to the RRC measurement report sent by the UE, the RAN node of the target secondary link; or determine the target secondary link according to the best cell indication sent by the RAN node of the source secondary link.
  • the apparatus in this embodiment may further include a switching module 203, configured to receive a handover request message sent by the RAN node of the source secondary link, and send a connection establishment request to the RAN node of the target secondary link. a message; a connection setup response message sent by the RAN node receiving the target secondary link; and a handover request response cancellation sent to the RAN node of the source secondary link
  • the embodiment may further include a release module 204, configured to receive a connection release request message sent by the RAN node of the source secondary link, and send a connection release response message to the RAN node of the source secondary link.
  • a release module 204 configured to receive a connection release request message sent by the RAN node of the source secondary link, and send a connection release response message to the RAN node of the source secondary link.
  • the first link target RAN node and the second link may be performed when the first link performs intra-system handover.
  • the RAN node normally transmits the multi-RAT aggregate data to ensure the continuity of the service transmission throughput.
  • FIG. 21 is a schematic structural diagram of a multi-carrier switching apparatus according to another embodiment of the present invention.
  • the apparatus may be located at a source RAN node of a first link.
  • the apparatus in this embodiment includes a determining module 211 and a sending module 212.
  • 211 is used to determine a RAN node that can continue to use multi-RAT link carrier aggregation as a target RAN node of the first link;
  • the sending module 212 is configured to carry The message of the second link information is sent to the target RAN node of the first link, so that the target RAN node corresponding to the first link establishes a connection with the RAN node corresponding to the second link, and performs data transmission.
  • the determining module 211 is specifically configured to use the RAN node of the first link that has the multi-RAT link carrier aggregation capability and the interface with the RAN node of the second link as the target RAN node of the first link.
  • the embodiment may further include a receiving module, configured to receive a handover response message returned by the target RAN node of the first link according to the current load condition.
  • the first link target RAN node and the second link may be performed when the first link performs intra-system handover.
  • the RAN node normally transmits the multi-RAT aggregate data to ensure the continuity of the service transmission throughput.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. You can choose which one according to your actual needs. Some or all of the units implement the objectives of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium. Based on this understanding, the form of the product is embodied.
  • the computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which may be a personal computer, a server, or a network device medium including: a USB flash drive, a mobile device)
  • a medium that can store program code such as a hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

Description

一种多载波的切换方法和装置 本申请要求于 2010 年 10 月 21 日提交中国专利局、 申请号为 201010526860.0、 发明名称为 "一种多载波的切换方法和装置" 的中国专利 申请的优先权， 其全部内容通过引用结合在本申请中。
技术领域 本发明涉及移动通信技术， 尤其涉及一种多载波的切换方法和装置。 背景技术 通用移动通信系统 ( Universal Mobile Telecommunications System , UMTS )、 长期演进（Long Term Evolution, LTE ) 系统、 码分多址（Code Division Multiple Access, CDMA ) 2000 中都引入了同一种无线接入技术 ( Radio Access Technology, RAT ) 内的多个载频的聚合技术， 多个载频的 聚合技术是指可以同时用多个载频资源传输同一个用户的数据， 这里称之 为系统内多载波聚合技术， 以提高用户峰值速率， 目前单 RAT内部多载波 聚合技术已经成熟。 伴随着载波聚合数量的增加， 用户设备 （ User Equipment, UE )的业务峰值速率又将到达另一个瓶颈， 考虑到目前无线通 信网络中， 多种制式（即多种 RAT ) 的网络同时长期共存， 比如， UMTS、 全球移动通信系统 ( Global System for Mobile communications , GSM )、 CDMA2000以及 LTE网络都将长期的共存， 多模终端的应用也已经十分广 泛， 为了进一步提高峰值速率， 可以使得 UE 同时工作于两个制式的网络 中， 例如， UE同时工作于 UTMS与 LTE系统中，或者 UE同时工作于 LTE 与 GSM/EDGE无线接入网 （ GSM EDGE Radio Access Network, GERAN ) 系统中， 以及其他系统间等。 当 UE 同时工作于两个制式或多个制式的网络中时， 将所述两个或所 述多个网络的数据进行聚合 /分流的节点称为数据聚合 /分流节点，该数据聚 合 /分流节点可以作为载波聚合控制节点或锚点， 用于进行载波数据分流 / 聚合控制， 锚点对应的链路为主 RAT链路， 非锚点对应的链路为辅 RAT 链路。 例如， 当 UE同时工作于 UMTS和 LTE系统时， UMTS和 LTE系统 的链路控制节点分别为无线网络控制器（Radio Network Controller, RNC ) 和演进基站（eNB ), 如果 UMTS系统的无线网络控制器为锚点， 则主 RAT 链路为 UMTS链路， 辅 RAT链路为 LTE链路。 反之， 如果 LTE系统的基 站（evolved NodeB, eNB ) 为锚点， 则主 RAT链路为 LTE链路， 辅 RAT 链路为 UMTS链路。
现有技术中， 当 UE在多 RAT链路载波聚合时进行切换时， 如果按照 单 RAT链路的切换方案， 只涉及源节点和目标节点， 则无法保证数据传输 吞吐率的连续性。 发明内容
本发明多个方面提供一种多载波的切换方法和装置， 实现多 RAT链路 载波聚合时的切换， 并保证数据传输吞吐量的连续性。
本发明一方面， 提供了一种多载波的切换方法， 包括：
第一链路对应的目标无线接入网 （ RAN ) 节点接收所述第一链路对应 的源 RAN节点发送的包含第二链路信息的消息； 所述第一链路对应的所述目标 RAN节点根据所述第二链路信息，建立 与第二链路对应的 RAN节点的连接， 以进行数据传输；
其中， 所述第一链路为第一无线接入技术（RAT )网络中的链路； 所述 第二链路为第二 RAT网络中的链路。 本发明的另一方面， 提供了一种多载波的切换方法， 第二链路对应的 RAN节点为载波数据分流 /聚合控制的锚点， 第一链路对应的 RAN节点为 辅链路的 RAN节点， 所述方法包括： 第二链路对应的载波数据分流 /聚合控制的锚点确定第一链路对应的目 标辅链路的 RAN节点；
所述锚点将所述目标辅链路的 RAN节点信息发送给第一链路对应的源 辅链路的 RAN节点， 以通过所述源辅链路的 RAN节点建立与所述目标辅链 路的 RAN的连接。
本发明的再一方面， 提供了一种多载波的切换方法， 包括：
第一链路的源 RAN 节点确定能够继续使用多 RAT链路载波聚合的 RAN节点作为第一链路的目标 RAN节点；
第一链路的源 RAN节点将携带第二链路信息的消息发送给所述第一链 路的目标 RAN节点， 以便所述第一链路对应的目标 RAN节点与所述第二链 路对应的 RAN节点建立连接后进行数据传输。
本发明的另一方面， 提供了一种多载波的切换装置， 包括： 接收模块，用于接收第一链路对应的源 RAN节点发送的包含第二链路 信息的消息；
建立模块，用于根据所述第二链路信息，建立第一链路对应的目标 RAN 节点与第二链路对应的 RAN节点的连接， 以进行数据传输；
其中， 所述第一链路为第一 RAT网络中的链路； 所述第二链路为第二 RAT网络中的链路。
本发明的另一方面， 提供了一种多载波的切换装置， 第二链路对应的 RAN节点为载波数据分流 /聚合控制的锚点， 第一链路对应的 RAN节点为辅 链路的 RAN节点， 所述设备位于所述锚点处， 所述设备包括： 确定模块， 用于确定第一链路对应的目标辅链路的 RAN节点； 发送模块， 用于将所述目标辅链路的 RAN节点信息发送给第一链路对 应的源辅链路的 RAN节点， 以通过所述源辅链路的 RAN节点建立与所述目 标辅链路的 RAN的连接。
本发明的再一方面， 提供了一种多载波的切换装置， 包括：
确定模块， 用于确定能够继续使用多 RAT链路载波聚合的 RAN节点 作为第一链路的目标 RAN节点；
发送模块， 用于将携带第二链路信息的消息发送给所述第一链路的目 标 RAN节点， 以便所述第一链路对应的目标 RAN节点与所述第二链路对应 的 RAN节点建立连接后进行数据传输。
由上述技术方案可知， 本发明实施例的多载波的切换方法和装置， 通 过建立第一链路对应的目标 RAN节点与第二链路对应的 RAN节点的连接， 可以在第一链路进行系统内切换时， 第一链路目标 RAN 节点和第二链路 RAN节点正常传输多 RAT聚合数据， 保证业务传输吞吐率的连续。 附图说明 为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对 实施例或现有技术描述中所需要使用的附图作一筒单地介绍， 显而易见地， 下面描述中的附图是本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。
图 1为本发明一实施例的一种多载波的切换方法流程示意图； 图 2为本发明另一实施例的一种多载波的切换方法流程示意图； 图 3为本发明另一实施例的一种多载波的切换方法流程示意图； 图 4为本发明另一实施例的一种多载波的切换方法流程示意图； 图 5为本发明另一实施例的一种多载波的切换方法流程示意图； 图 6为本发明另一实施例的一种多载波的切换方法流程示意图； 图 7为本发明另一实施例的一种多载波的切换方法流程示意图； 图 8本发明另一实施例的一种多载波的切换方法流程示意图； 图 9为本发明另一实施例的一种多载波的切换方法流程示意图； 图 10为本发明另一实施例的一种多载波的切换方法流程示意图； 图 11为本发明另一实施例的一种多载波的切换方法流程示意图； 图 12为本发明另一实施例的一种多载波的切换方法流程示意图； 图 13为本发明另一实施例的一种多载波的切换方法流程示意图； 图 14为本发明另一实施例的一种多载波的切换方法流程示意图； 图 15为本发明另一实施例的一种多载波的切换方法流程示意图； 图 16为本发明另一实施例的一种多载波的切换方法流程示意图； 图 17为本发明另一实施例的一种多载波的切换方法流程示意图； 图 18为本发明另一实施例的一种多载波的切换方法流程示意图； 图 19为本发明一实施例的一种多载波的切换装置结构示意图； 图 20为本发明另一实施例的一种多载波的切换装置结构示意图； 图 21为本发明另一实施例的一种多载波的切换装置结构示意图。 具体实舫式 为使本发明实施例的目的、 技术方案和优点更加清楚， 下面将结合本 发明实施例中的附图， 对本发明实施例中的技术方案进行清楚、 完整地描 述， 显然， 所描述的实施例是本发明一部分实施例， 而不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有做出创造性劳动前提 下所获得的所有其他实施例， 都属于本发明保护的范围。
本发明实施例将以 UMTS和 LTE系统为例，对应的链路分别为 UMTS 链路 (筒称为 U链路 )和 LTE链路（筒称为 L链路 ) , 对应的链路控制节 点分别为 RNC和 eNB。通信时锚点只能有一个，当锚点为 RNC时，主 RAT 链路为 U链路， 辅 RAT链路为 L链路； 当锚点为 eNB时， 主 RAT链路为 L链路，辅 RAT链路为 U链路。类似的，如果 UE同时工作于 LTE与 GERAN 系统中， 对应的链路分别为 LTE链路和 GERAN链路， 对应的链路控制节 点分别为 eNodeB和基站控制器（Base Station Cotroller, BSC )。 当锚点为 eNodeB时， 主 RAT链路为 LTE链路， 辅 RAT链路为 GERAN链路； 当锚 点为 BSC时， 主 RAT链路为 GERAN链路， 辅 RAT链路为 LTE链路。 本文涉及的切换， 是指无线接入网络的链路控制节点发生变化。 例如， UMTS系统的链路控制节点为 RNC, 发生切换时， UE从源 RNC切换到目 标 RNC; LTE系统的链路控制节点为 eNB, 发生切换时， UE从源 eNB 切换到目标 eNB； GERAN系统的链路控制节点为 eNB , 发生切换时， UE 从源 BSC切换到目标 BSC。 在其他制式的通信系统中， 根据链路控制节点 名称的不同， UE发生切换的链路控制节点的名称也不同， 在此不再赘述。 本发明实施例可以分为如下场景：
场景一： 主 RAT链路切换， 辅 RAT链路不切换； 场景二： 辅 RAT链路切换， 主 RAT链路不切换； 场景三： 主 RAT链路和辅 RAT链路都切换； 场景四： 单 RAT链路切换后改为双 RAT链路。 场景五： 双 RAT链路切换后改为单 RAT链路。 其中， 对于场景三可以综合利用场景一、 二来实现， 例如， 先进行主 RAT链路切换流程， 再进行辅 RAT链路切换流程， 或者先进行辅 RAT链 路切换流程， 再进行主 RAT链路切换流程， 在每个流程中分别按照场景一 或者场景二的流程进行。对于场景四， 可以将切换前的单 RAT作为辅 RAT 链路， 利用场景二实现。 因此， 本发明实施例将主要描述场景一、 二。
图 1 为本发明一实施例的一种多载波的切换方法流程示意图， 可以如 下所述。 11: 第一链路对应的目标无线接入网 （RAN, Radio Access Network ) 节点接收第一链路对应的源 RAN节点发送的包含第二链路信息的消息。 其中， 所述第一链路为第一无线接入技术（RAT ) 网络中的链路； 第 二链路为第二 RAT网络中的链路。 对于场景一或者场景二， 第一链路是指 发生切换的链路， 第二链路是指不切换的链路。 例如， UMTS系统的 RNC为锚点， 主 RAT链路为 U链路， 辅 RAT链 路为 L链路； 当主 RAT链路切换， 辅 RAT链路不切换， 则第一链路为 U 链路， 第二链路为 L链路； 第一链路对应的目标 RAN节点为目标 RNC, 第一链路对应的源 RAN节点为源 RNC。 在本发明的另一实施例中， 所述 第二链路信息为 L链路信息， 例如， 所述 L链路信息可以为 eNB 标识 Identity或者 eNB所属小区的小区 ID ( cell ID ) 。
例如， UMTS系统的 RNC为锚点， 主 RAT链路为 U链路， 辅 RAT链 路为 L链路； 当主 RAT链路不切换， 辅 RAT链路切换， 则第一链路为 L 链路， 第二链路为 U链路； 第一链路对应的目标 RAN节点为目标 eNB, 第一链路对应的源 RAN节点为源 eNB。 在本发明的另一实施例中， 所述第 二链路信息为 U链路信息，例如，所述 U链路信息可以为： RNC标识 RNC ID或者 RNC所属小区的小区标识 Cell ID。
例如， LTE系统的 eNB为锚点， 主 RAT链路为 L链路， 辅 RAT链路 为 U链路； 当主 RAT链路切换， 辅 RAT链路不切换， 则第一链路为 L链 路， 第二链路为 U链路； 第一链路对应的目标 RAN节点为目标 eNB, 第 一链路对应的源 RAN节点为源 eNB。 在本发明的另一实施例中， 所述第二 链路信息为 U链路信息， 例如， 所述 U链路信息可以为： RNC标识 RNC ID或者 RNC所属小区的小区标识 Cell ID。
例如， LTE系统的 eNB为锚点， 主 RAT链路为 L链路， 辅 RAT链路 为 U链路； 当主 RAT链路不切换， 辅 RAT链路切换， 则第一链路为 U链 路， 第二链路为 L链路； 第一链路对应的目标 RAN节点为目标 RNC, 第 一链路对应的源 RAN节点为源 RNC。 在本发明的另一实施例中， 所述第 二链路信息为 L链路信息，例如，所述 L链路信息可以为 eNB 标识 Identity 或者 eNB所在小区的小区 ID ( cell ID ) 。
对于下行方向， 锚点负责从锚点归属的核心网接收数据并负责在两个 不同 RAT的载波进行分发， 对于上行方向， 锚点负责将同一个 UE在两个 不同 RAT载波上发上来的数据进行聚合并发给锚点归属的核心网节点。 当 主 RAT切换时， 第一链路对应的 RAN节点分别为源锚点和目标锚点， 此 时， 第二链路对应的 RAN节点为辅 RAN节点； 当辅 RAT切换时， 第一链 路对应的 RAN节点分别为源辅 RAN节点和目标辅 RAN节点，第二链路对 应的 RAN节点为锚点。 另夕卜， 当源 RAN节点与目标 RAN节点之间存在接口时， 可以直接通 过该接口传输第二链路信息， 源 RAN节点也可以通过核心网将第二链路信 息发送给目标 RAN节点。当源 RAN节点与目标 RAN节点之间不存在接口 时， 源 RAN节点可以通过核心网将第二链路信息发送给目标 RAN节点。 例如， 第一链路的源 RAN节点需要将第一链路的目标小区信息和第二 链路信息同时发给第一链路的目的 RAN节点。其中第二链路的信息可以包 括第二链路的源链路信息和 /或者第二链路的目的链路信息。 源链路信息是 指发生小区切换或者链路重配置过程前， 移动台当前服务小区所属于的链 路的信息。 目的链路信息是指， 发生小区切换或者链路重配置过程后， 移 动台服务小区所属于的链路的信息。 链路信息可以包含下述的一个信息或 者一个以上的信息的任意组合： 小区标识（ cell identity或者 CGI ) , 或者 RAN节点标识（eNB id或者 RNC标识） ， 或者链路标识等。
12: 第一链路对应的目标 RAN节点根据所述第二链路信息， 建立与第 二链路对应的 RAN节点的连接， 以进行数据传输。 例如，第一链路对应的 RAN节点为 UMTS系统的链路控制节点（例如， RNC )时， 第二链路对应的 RAN节点为 LTE系统的链路控制节点（例如， eNB )。再例如，第一链路对应的 RAN节点为 LTE系统的链路控制节点（例 如， eNB )时，第二链路对应的 RAN节点为 UMTS系统的链路控制节点（例 如， RNC ) 。
其中， 当第一链路的目标 RAN节点与第二链路的 RAN节点已经存在 接口 （如 lue )时， 则该目标 RAN节点可以向该第二链路的 RAN节点发送 连接建立指示（ Connection Setup Indication )消息， 以触发该 lue接口工作； 否则， 该目标 RAN节点可以向该第二链路的 RAN节点发送连接建立请求 ( Connection Setup Request ) 消息， 并接收该第二链路的 RAN节点返回的 连接建立响应 ( Connection Setup Response ) 消息， 以建立 lue接口。
另外， 对于第一链路的源 RAN节点侧， 可以为： 第一链路的源 RAN 节点确定能够继续使用多 RAT链路载波聚合的 RAN节点作为第一链路的 目标 RAN节点； 第一链路的源 RAN节点将携带第二链路信息的消息发送 给所述第一链路的目标 RAN节点， 以便所述第一链路对应的目标 RAN节 点与所述第二链路对应的 RAN节点建立连接后进行数据传输。第一链路的 源 RAN节点可以将具有载波聚合能力且与第二链路的 RAN节点之间存在 接口的第一链路的 RAN节点作为第一链路的目标 RAN节点。
本实施例通过建立第一链路对应的目标 RAN 节点与第二链路对应的 RAN节点的连接， 可以在切换时第一链路的目标 RAN节点和第二链路的 RAN节点正常传输数据， 保证业务传输吞吐率的连续性。
图 2为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例的应用场景如下： RNC为锚点、 主 RAT链路（ U链路 )切换， 辅 RAT 链路（L链路） 不切换； RNC之间无 Iur接口， 需要通过 RNC与核心网之 间的 Iu接口传输信息； 目标 RNC判决是否继续使用多 RAT载波聚合（U& L Boosting ) 。 参见图 2, 本实施例的多链路的切换方法可以如下所述。
201： UE向源 RNC( Source RNC )发送 RRC测量报告（ RRC Measurement Report ) 。
202: 源 RNC进行重定位（ Relocation )判决。
例如， 源 RNC根据 RRC测量报告中的信号强度， 发现存在比源 RNC 小区的信号更强的不同 RNC小区， 且满足切换条件时， 判决出进行切换。
203: 源 RNC向 SGSN发送携带 L链路信息的消息， 例如， 重定位要 求（ Relocation Required )消息， 其中携带 L链路信息， 例如， L链路的 eNB ID或者 cell ID。
204: SGSN向目标 RNC ( Target RNC )发送携带 L链路信息的消息， 例如， 重定位请求（ Relocation Request ) 消息， 其中携带 L链路信息。
205:目标 RNC判决是否继续对该 UE提供多 RAT载波聚合业务传输。 具体地， 目标 RNC可以根据自身的多 RAT链路载波聚合能力信息、 自身与 eNB是否存在接口以及目标小区的负载情况， 判断是否继续进行载 波聚合。
例如， 如果目标小区的负载过载时， 目标 RNC向 SGSN发送重定位失 败（Relocation Failure )消息，其中携带原因值： 目标小区拥塞。之后， SGSN 向源 RNC发送重定位准备失败（ Relocation Preparation Failure )消息， 其中 携带原因值， 例如， 目标小区拥塞。
或者， 当目标 RNC与 eNB不存在接口时， 则可以建立 RNC与 eNB之 间的接口， 例如 Iue接口。
206: 目标 RNC向 eNB向发送用于建立接口的请求消息， 例如连接建 立请求 ( Connection Setup Request ) 消息。
207： eNB 向目标 RNC 发送相应的响应消息， 例如连接建立响应 ( Connection Setup Response ) 消息。
通过步骤 206-207, 目标 RNC与 eNB建立信令连接。 其中， 在步骤 206-207执行过程中， 可以去激活 L链路， 例如， 可以 由 eNB向 UE发送去激活 L链路指示， 避免 L链路数据丢失， 以避免新连 接的建立过程中， 出现数据丢失的现象或者筒化切换流程。
208: 目标 RNC向 SGSN发送携带是否可继续使用载波聚合的指示信 息， 当不可使用时携带原因值， 如 RNC不支持 U &L载波聚合、 目标 RNC 与 eNB没有接口 （硬件不支持） 、 资源不足等的消息， 例如重定位请求应 答 ( Relocation Request Acknowledge ) 消息。
209: SGSN 向源 RNC 发送携带指示信息的消息， 例如重定位命令 ( Relocation Command ) 消息。
210: 源 RNC根据指示信息， 判决是否删除 L载波， 并重配 U载波。 例如， 当指示信息表明不支持载波聚合时， 则删除 L载波。 当删除 L 载波时， 可以是： 源 RNC 向 eNB 发送承载释放指示 （ E-RAB release Indication ) 消息， 其中携带指示信息。 eNB与 UE之间进行承载释放过程 ( E-RAB release ) 。
之后， 源 RNC将数据传输给目标 RNC ( Start Data Forwarding ) 。
211： 源 RNC向 eNB发送用于释放资源的请求消息， 例如连接释放请 求 ( Connection Release Request ) 消息。
212 : eNB 向源 RNC 返回相应的响应消息， 例如连接释放响应 ( Connection Release Response ) 消息。
213 : 源 RNC 向 UE 发送物理信道重配置 （ Physical Channel
Reconfiguration ) 消息。
其中， 步骤 211-212可以在步骤 213之后。 以便 L1同步实现后再删除 源 RNC和 eNB的连接，从而避免同步失败新链接建立不成功， 而原链路已 删除导致的数据丢失或掉话。
之后， UE、 源 RNC 和目标 RNC之间可以进行层 1 同步流程（ L1
Synchronization and reception of NBAP: RL Restore indication ) 。 214: UE 向目标 RNC 发送物理信道重配置完成 （Physical Channel Reconfiguration Complete ) 消息。
215: 目标 RNC向 SGSN发送重定位检测 （ Relocation Detect ) 消息。
216: 目标 RNC向 SGSN发送重定位完成（ Relocation Complete )消息。 217: 源 RNC和 SGSN释放 Iu接口信令连接（ Iu Release ) 。
本实施例通过核心网使得源 RNC将 L链路信息发送给目标 RNC, 可 以在 U链路切换时， 目标 RNC建立与 eNB的连接， 保证切换时数据传输 吞吐量的连续性。
图 3 为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例的应用场景如下： RNC为锚点、 主 RAT链路（ U链路 )切换， 辅 RAT 链路（L链路） 不切换； RNC之间无 lur接口， 需要通过 RNC与核心网之 间的 Iu接口传输信息；源 RNC确定能够继续使用载波聚合（ U& L Boosting ) 及与 eNB存在接口的 RNC作为目标 RNC。
参见图 3, 本实施例的多链路的切换方法可以如下所述。
301： UE向源 RNC( Source RNC )发送 RRC测量4艮告（ RRC Measurement
Report ) 。
302: 源 RNC根据 OAM配置查找和该 eNB有接口以及支持载波聚合 的其他 RNC作为 U载波切换的目标 RNC, 进行重定位（ Relocation )判决。
303: 源 RNC向 SGSN发送携带 L链路信息， 例如， L链路的 eNB ID 或者 cell ID的消息， 例如重定位要求（ Relocation Required ) 消息。
304: SGSN向目标 RNC ( Target RNC )发送携带 L链路信息的消息， 例如重定位请求 ( Relocation Request ) 消息。
305: 目标 RNC根据目标小区的负载情况，判决是否继续对该 UE提供 多 RAT载波聚合业务传输。
例如， 如果目标小区当前的负载过载时， 目标 RNC向 SGSN发送重定 位失败（Relocation Failure )消息， 其中携带原因值： 目标小区拥塞。 之后， SGSN向源 RNC发送重定位准备失败（ Relocation Preparation Failure )消息， 其中携带原因值， 例如， 目标小区拥塞。
或者， 可以支持 UE继续使用多 RAT载波聚合时触发 Iue接口信令连 接工作：
306: 目标 RNC向 eNB发送用于触发接口工作的消息， 例如连接建立 指示 ( Connection Setup Indication ) 消息。
其中，在步骤 306执行过程中， 可以去激活 L链路， 例如， 可以由 eNB 向 UE发送去激活 L链路指示， 避免 L链路数据丢失， 以避免新连接的建 立过程中， 出现数据丢失的现象或者筒化切换流程。
307: 目标 RNC向 SGSN发送携带是否可继续使用载波聚合的指示信 息， 当不可使用时携带原因值， 如资源不足等的消息， 例如重定位请求应 答 ( Relocation Request Acknowledge ) 消息。
308: SGSN 向源 RNC 发送携带指示信息的消息， 例如重定位命令 ( Relocation Command ) 消息。
309: 源 RNC根据指示信息， 判决是否删除 L载波， 并重配 U载波。 例如， 当指示信息表明不支持载波聚合时， 则删除 L载波。 当删除 L 载波时， 可以是： 源 RNC 向 eNB 发送承载释放指示 （ E-RAB release Indication ) 消息， 其中携带指示信息。 eNB与 UE之间进行承载释放过程 ( E-RAB release ) 。
之后， 源 RNC将数据传输给目标 RNC ( Start Data Forwarding ) 。
310: 源 RNC 向 eNB 发送用于释放资源的消息， 例如连接释放请求 ( Connection Release Request ) 消息。
311 : eNB 向源 RNC 返回相应的响应消息， 例如连接释放响应 ( Connection Release Response ) 消息。
312 : 源 RNC 向 UE 发送物理信道重配置 （ Physical Channel
Reconfiguration ) 消息。 其中， 步骤 310-311可以在步骤 312之后。 以便 L1同步实现后再删除 源 RNC和 eNB的连接，从而避免同步失败新链接建立不成功， 而原链路已 删除导致的数据丢失或掉话。
之后， UE、 源 RNC 和目标 RNC之间可以进行层 1 同步流程（ L1 Synchronization and reception of NBAP: RL Restore indication ) 。
313: UE 向目标 RNC 发送物理信道重配置完成 （Physical Channel Reconfiguration Complete ) 消息。
314: 目标 RNC向 SGSN发送重定位检测 （ Relocation Detect ) 消息。 315: 目标 RNC向 SGSN发送重定位完成（ Relocation Complete )消息。 316: 源 RNC和 SGSN释放 Iu接口信令连接（ Iu Release ) 。
本实施例通过核心网使得源 RNC将 L链路信息发送给目标 RNC, 可 以在 U链路切换时， 目标 RNC建立与 eNB的连接， 保证切换时数据传输 吞吐量的连续性。 本实施例由源 RNC根据其他 RNC是否和该 eNB有接口 确定为切换目标 RNC ,避免由于目标 RNC不支持与本 eNB进行 UL Boosting 导致的辅链路删除过程， 同时减少切换准备时延， 节省信令开销。
图 4为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例的应用场景如下： RNC为锚点、 主 RAT链路（ U链路 )切换， 辅 RAT 链路 ( L链路 )不切换； RNC之间存在 lur接口， 可以通过 RNC之间的 lur 接口传输信息。
参见图 4, 本实施例的多链路的切换方法可以如下所述。
401： UE向源 RNC( Source RNC )发送 RRC测量报告（ RRC Measurement Report ) 。
402: 源 RNC进行重定位（ Relocation )判决。
例如， 源 RNC根据 RRC测量报告中的信号强度， 发现存在比源 RNC 小区的信号更强的不同的 RNC小区，且满足切换条件时，判决出进行切换。
403: 源 RNC向目标 RNC发送携带 L链路信息， 例如， L载波的 eNB ID或者 cell ID的消息，例如增强重定位请求（ Enhanced Relocation Request ) 消息。
404:目标 RNC判决是否继续对该 UE提供多 RAT载波聚合业务传输。 具体地， 目标 RNC 可以根据自身的载波聚合能力信息、 自身与 eNB 是否存在接口以及目标小区的负载情况，判决是否继续对该 UE提供多 RAT 载波聚合业务传输。
例如， 如果目标小区的负载过载时， 目标 RNC向源 RNC发送增强重 定位失败 ( Enhanced Relocation Preparation Failure )消息， 其中携带原因值， 例如， 目标小区拥塞。
或者， 当目标 RNC与 eNB不存在 Iue接口时， 则可以建立 Iue:
405: 目标 RNC向 eNB发送用于建立接口的请求消息， 例如连接建立 请求 ( Connection Setup Request ) 消息。
406： eNB 向目标 RNC 发送相应的响应消息， 例如连接建立响应 ( Connection Setup Response ) 消息。
通过步骤 405-406, 目标 RNC与 eNB建立信令连接。
其中， 在步骤 405-406执行过程中， 可以去激活 L链路， 例如， 可以 由 eNB向 UE发送去激活 L链路指示， 避免 L链路数据丢失， 以避免新连 接的建立过程中， 出现数据丢失的现象或者筒化切换流程。
407: 目标 RNC向源 RNC发送携带是否可继续使用载波聚合的指示信 息， 当不可使用时携带原因值， 如 RNC不支持 U &L载波聚合、 目标 RNC 与 eNB 没有接口、 资源不足等的消息， 例如增强重定位响应 （Enhanced Relocation Response ) 消息。
408: 源 RNC根据指示信息， 判决是否删除 L载波， 并重配 U载波。 例如， 当指示信息表明不支持载波聚合时， 则删除 L载波。 当删除 L 载波时， 可以是： 源 RNC 向 eNB 发送承载释放指示 （ E-RAB release Indication ) 消息， 其中携带指示信息。 eNB与 UE之间进行承载释放过程 ( E-RAB release ) 。
之后， 源 RNC将数据传输给目标 RNC ( Start Data Forwarding ) 。
409: 源 RNC向 eNB发送用于释放资源的请求消息， 例如连接释放请 求 ( Connection Release Request ) 消息。
410 : eNB 向源 RNC 返回相应的响应消息， 例如连接释放响应
( Connection Release Response ) 消息。
411： 源 RNC 向 UE 发送物理信道重配置 （ Physical Channel Reconfiguration ) 消息。
其中， 步骤 409-410可以在步骤 411之后。 以便 L1同步实现后再删除 源 RNC和 eNB的连接，从而避免同步失败新链接建立不成功， 而原链路已 删除导致的数据丢失或掉话。
412: 源 RNC向目标 RNC发送携带聚合数据包的同步信息的消息， 例 ^口重定位委托 ( Relocation Commit ) 消息。
此时， SGSN向源 RNC发送下行数据 ( Downlink Data ) 。
之后， UE、 源 RNC 和目标 RNC之间可以进行层 1 同步流程（ L1
Synchronization and reception of NBAP: RL Restore indication ) 。
413 : UE 向目标 RNC 发送物理信道重配置完成 （Physical Channel Reconfiguration Complete ) 消息。
414:目标 RNC向 SGSN发送增强重定位完成请求（ Enhanced Relocation Complete Request ) 消息。
415:目标 RNC向 SGSN发送增强重定位完成响应（ Enhanced Relocation Complete Response ) 消息。
416: 目标 RNC向源 RNC发送资源释放消息 （ Resource Release ) 。 本实施例以目标 RNC判决为例，类似于第三实施例，也可以由源 RNC 确定能够支持聚合且与 eNB存在接口的 RNC作为目标 RNC, 此时， 需要 目标 RNC向 eNB发送连接建立指示消息， 可以实现信令节省。 本实施例通过 RNC之间的接口使得源 RNC将 L链路信息发送给目标 RNC , 可以在 U链路切换时， 目标 RNC建立与 eNB的连接， 保证切换时 数据传输吞吐量的连续性。
图 5 为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例的应用场景如下： eNB为锚点、 主 RAT链路 ( L链路 )切换， 辅 RAT 链路 ( U链路 )不切换； eNB之间存在 X2接口， 可以通过 eNB之间的 X2 接口传输信息。
参见图 5, 本实施例的多链路的切换方法可以如下所述。
501: UE向源 eNB( Source eNB )发送 RRC测量报告（ RRC Measurement Report ) 。
502: 源 eNB进行切换判决。
例如， 源 eNB根据 RRC测量报告中的信号强度， 发现存在比源 eNB 小区的信号更强的不同 eNB小区， 且满足切换条件时， 判决出进行切换。
503: 源 eNB向目标 eNB发送携带 U链路信息， 例如， U载波的 RNC ID或者 cell ID的消息， 例如切换请求 ( Handover Request ) 消息。
504: 目标 eNB判决是否继续对该 UE提供多 RAT载波聚合业务传输。 具体地， 目标 eNB 可以根据自身的载波聚合能力信息、 自身与 RNC 是否存在接口以及目标小区的负载情况，判决是否继续对该 UE提供多 RAT 载波聚合业务传输。
例如， 如果目标小区的负载过载时， 目标 eNB向源 eNB发送切换准备 失败 ( Handover Relocation Preparation Failure ) 消息， 其中携带原因值， 例 如， 目标小区拥塞。
或者， 当目标 eNB与 RNC不存在 Iue接口时， 则可以建立 Iue:
505: 目标 eNB向 RNC发送用于建立接口的请求消息， 例如连接建立 请求 ( Connection Setup Request ) 消息。
506: RNC 向目标 eNB 发送相应的响应消息， 例如连接建立响应 ( Connection Setup Response ) 消息。
通过步骤 505-506, 目标 eNB与 RNC建立信令连接。
其中， 在步骤 505-506执行过程中， 可以去激活 U链路， 例如， 可以 由 RNC向 UE发送去激活 U链路指示，避免 U链路数据丢失， 以避免新连 接的建立过程中， 出现数据丢失的现象或者筒化切换流程。
507: 目标 eNB向源 eNB发送携带是否可继续使用载波聚合的指示信 息， 当不可使用时携带原因值， 如 eNB不支持 U &L载波聚合、 目标 eNB 与 RNC没有接口、资源不足等的消息，例如切换请求应答（ Handover Request Acknowledge ) 消息。
508: 源 RNC根据指示信息， 判决是否删除 U载波， 并重配 L载波。 例如， 当指示信息表明不支持载波聚合时， 则删除 U载波。 当删除 U 载波时， 可以是： 源 eNB 向 RNC 发送承载释放指示 （ E-RAB release Indication ) 消息， 其中携带指示信息。 RNC 与 UE之间进行承载释放过程 ( E-RAB release ) 。
509 : 源 eNB 向 UE 发送 RRC 连接重配置 （ RRC Connection
Reconfiguration ) 消息。
之后， 源 eNB将数据传输给目标 eNB ( Data Forwarding ) 。
510: 源 eNB 向 RNC发送释放资源的请求消息， 例如连接释放请求 ( Connection Release Request ) 消息。
511 : RNC 向源 eNB 返回相应的响应消息， 例如连接释放响应
( Connection Release Response ) 消息。
UE、 源 eNB 和目标 eNB 之间可以进行层 1 同步流程 （ L1 Synchronization ) 。
512: UE 向目标 eNB 发送 RRC 连接重配置完成（ RRC Connection Reconfiguration Complete ) 消息。
本实施例以目标 eNB判决为例， 类似于第三实施例， 也可以由源 eNB 确定能够支持聚合且与 RNC存在接口的 eNB作为目标 eNB, 此时， 需要 目标 eNB向 RNC发送连接建立指示消息， 可以实现信令节省。
本实施例通过 eNB之间的接口使得源 eNB将 U链路信息发送给目标 eNB可以在 L链路切换时， 目标 eNB建立与 RNC的连接， 保证切换时数 据传输吞吐量的连续性。
图 6为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例的应用场景如下： eNB为锚点、 主 RAT链路 ( L链路 )切换， 辅 RAT 链路 ( U链路 ) 不切换； eNB之间不存在 X2接口， 需要通过 eNB与核心 网之间的 S1接口传输信息。
参见图 6, 本实施例的多链路的切换方法可以如下所述。
601: UE向源 eNB( Source eNB )发送 RRC测量报告（ RRC Measurement Report ) 。
602: 源 eNB进行切换判决。
具体内容可以参见步骤 502。
603： 源 eNB向 MME发送携带 U链路信息， 例如， U链路的 RNC ID 或者 cell ID的消息， 例如切换要求 ( Handover Required ) 消息。
604: MME向目标 eNB ( Target eNB )发送携带 U链路信息的消息， 例: ¾口切换请求 ( Handover Request ) 消息。
605: 目标 eNB判决是否继续对该 UE提供多 RAT载波聚合业务传输。 具体地， 目标 eNB 可以根据自身的载波聚合能力信息、 自身与 RNC 是否存在接口以及目标小区的负载情况，判决是否继续对该 UE提供多 RAT 载波聚合业务传输。
例如， 如果目标小区的负载过载时， 目标 eNB向源 eNB发送切换准备 失败 ( Handover Relocation Preparation Failure ) 消息， 其中携带原因值， 例 如， 目标小区拥塞。
或者， 当目标 eNB与 RNC不存在 Iue接口时， 则可以建立 Iue: 606: 目标 eNB向 RNC向发送用于建立接口的请求消息， 例如连接建 立请求 ( Connection Setup Request ) 消息。
607： RNC 向目标 eNB 发送相应的响应消息， 例如连接建立响应 ( Connection Setup Response ) 消息。
通过步骤 606-607, 目标 eNB与 RNC建立逻辑连接。
其中， 在步骤 606-607执行过程中， 可以去激活 U链路， 例如， 可以 由 RNC向 UE发送去激活 U链路指示，避免 U链路数据丢失， 以避免新连 接的建立过程中， 出现数据丢失的现象或者筒化切换流程。
608: 目标 eNB向 MME发送携带是否可继续使用载波聚合的指示信 息， 当不可使用时携带原因值， 如 eNB不支持 U &L载波聚合、 目标 eNB 与 RNC没有接口、资源不足等的消息，例如切换请求应答（ Handover Request Acknowledge ) 消息。
609: MME向源 eNB发送携带指示信息的消息， 例如，切换命令消息， 该指示信息为步骤 608中的指示信息。
610: 源 RNC根据指示信息， 判决是否删除 U载波， 并重配 L载波。 例如， 当指示信息表明不支持载波聚合时， 则删除 U载波。 当删除 U 载波时， 可以是： 源 eNB 向 RNC 发送承载释放指示 （ E-RAB release Indication ) 消息， 其中携带指示信息。 RNC 与 UE之间进行承载释放过程 ( E-RAB release ) 。
611 : 源 eNB 向 UE 发送 RRC 连接重配置 （ RRC Connection
Reconfiguration ) 消息。
之后， 源 eNB将数据传输给目标 eNB ( Data Forwarding ) 。
612: 源 eNB向 RNC发送用于释放资源的请求消息， 例如连接释放请 求 ( Connection Release Request ) 消息。
613 : RNC 向源 eNB 返回相应的响应消息， 例如连接释放响应
( Connection Release Response ) 消息。 之后， UE、 源 eNB 和目标 eNB 之间可以进行层 1 同步流程（ L1 Synchronization ) 。
614: UE 向目标 eNB 发送 RRC 连接重配置完成（ RRC Connection Reconfiguration Complete ) 消息。
615: 目标 eNB向 MME发送切换通知（ Handover Notify ) 消息。
本实施例以目标 eNB判决为例， 类似于第三实施例， 也可以由源 eNB 确定能够支持聚合且与 RNC存在接口的 eNB作为目标 eNB, 此时， 需要 目标 eNB向 RNC发送连接建立指示消息， 可以实现信令节省。
本实施例通过核心网使得源 eNB将 U链路信息发送给目标 eNB可以在 L链路切换时， 目标 eNB建立与 RNC的连接，保证切换时数据传输吞吐量 的连续性。
图 7 为本发明另一实施例的一种多载波的切换方法流程示意图图， 本 实施例的应用场景如下： RNC为锚点、 主 RAT链路（U链路）不切换， 辅 RAT链路（ L链路 )切换； eNB之间存在 X2接口， 可以通过 eNB之间的 X2接口传输信息； 由非锚点 （eNB )做切换控制。
参见图 7, 本实施例的多链路的切换方法可以如下所述。
701: UE向源 eNB( Source eNB )发送 RRC测量报告（ RRC Measurement Report ) 。
702: 源 eNB进行切换判决。
具体内容可以参见步骤 502。
703: 源 eNB向目标 eNB发送携带 U链路信息， 例如， U载波的 RNC ID或者 cell ID的消息， 例如切换请求 ( Handover Request ) 消息。
704: 目标 eNB判决是否继续对该 UE提供多 RAT载波聚合业务传输。 具体地， 目标 eNB 可以根据自身的载波聚合能力信息、 自身与 RNC 是否存在接口以及目标小区的负载情况，判决是否继续对该 UE提供多 RAT 载波聚合业务传输。 与图 2-6所示的主链路切换不同的是， 由于本实施例是辅链路切换， 为 了节省资源，可以只在目标 eNB与 RNC存在接口且具有载波能力时，继续 切换， 否则直接返回失败响应。 即， 如果当前的负载过载、 不具有聚合能 力、 不存在接口时， 目标 eNB向源 eNB发送携带失败原因值的消息， 例如 切换失败（Handover Failure ) 消息， 其中携带原因值， 例如， 目标小区拥 塞、 不支持聚合、 没有 Iue接口等。
705： 目标 eNB向 RNC发送触发接口工作的消息， 例如连接建立指示 ( Connection Setup Indication ) 消息， 以触发 Iue接口工作。
其中，在步骤 705执行过程中，可以去激活 U链路，例如，可以由 RNC 向 UE发送去激活 U链路指示， 避免 U链路数据丢失， 以避免新连接的建 立过程中， 出现数据丢失的现象或者筒化切换流程。
706 : 目标 eNB 向源 eNB 发送切换请求应答 （Handover Request Acknowledge ) 消息。
707 : 源 eNB 向 UE 发送 RRC 连接重配置 （ RRC Connection Reconfiguration ) 消息。
之后， 源 eNB可以将数据传输给目标 eNB ( Data Forwarding ) 。
708: 源 eNB向 RNC发送用于释放资源的请求消息， 例如连接释放请 求 ( Connection Release Request ) 消息。
709 : RNC 向源 eNB 返回相应的响应消息， 例如连接释放响应 ( Connection Release Response ) 消息。
之后， UE、 源 eNB 和目标 eNB 之间可以进行层 1 同步流程（ L1 Synchronization ) 。
710: UE 向目标 eNB 发送 RRC 连接重配置完成（ RRC Connection Reconfiguration Complete ) 消息。
本实施例通过 eNB之间的接口使得源 eNB将 U链路信息发送给目标 eNB可以在 L链路切换时， 目标 eNB建立与 RNC的连接， 保证切换时数 据传输吞吐量的连续性。
图 8本发明另一实施例的一种多载波的切换方法流程示意图， 本实施 例的应用场景如下： RNC为锚点、 主 RAT链路 ( U链路 )不切换， 辅 RAT 链路 ( L链路 )切换； eNB之间不存在 X2接口， 需要通过 eNB与核心网 之间的 S1接口传输信息； 由非锚点 （eNB )做切换控制。
参见图 8, 本实施例的多链路的切换方法可以如下所述。
801: UE向源 eNB( Source eNB )发送 RRC测量报告（ RRC Measurement Report ) 。
802: 源 eNB进行切换判决。
具体内容可以参见步骤 502。
803： 源 eNB向 MME发送携带 U链路信息， 例如， U链路的 RNC ID 或者 cell ID的消息， 例如切换要求 ( Handover Required ) 消息。
804: MME向目标 eNB ( Target eNB )发送携带 U链路信息的消息， 例: ¾口切换请求 ( Handover Request ) 消息。
805: 目标 eNB判决是否继续对该 UE提供多 RAT载波聚合业务传输。 具体地， 目标 eNB 可以根据自身的载波聚合能力信息、 自身与 RNC 是否存在接口以及目标小区的负载情况，判决是否继续对该 UE提供多 RAT 载波聚合业务传输。
与图 2-6所示的主链路切换不同的是， 由于本实施例是辅链路切换， 为 了节省资源，可以只在目标 eNB与 RNC存在接口且具有载波能力时，继续 切换， 否则直接返回失败响应。 即， 如果当前的负载过载、 不具有聚合能 力、 不存在接口时， 目标 eNB向 MME发送携带失败原因值的消息， 例如 切换准备失败（ Handover Preparation Failure )消息，其中携带原因值，例如， 目标小区拥塞、 不支持聚合、 没有 Iue接口等。 之后， MME向源基站发送 切换准备失败（Handover Failure ) 消息， 其中携带上述的失败原因。
806: 目标 eNB向 RNC发送用于触发接口工作的消息， 例如连接建立 指示 （ Connection Setup Indication ) 消息， 以触发 Iue接口工作。
807 : 目标 eNB 向 MME 发送切换请求应答 ( Handover Request
Acknowledge ) 消息。
808: MME向源 eNB发送切换命令 ( Handover Command ) 消息。
809 : 源 eNB 向 UE 发送 RRC 连接重配置 （ RRC Connection
Reconfiguration ) 消息。
810: 源 eNB向 RNC发送连接释放请求（ Connection Release Request ) 消息。
811 : RNC向源 eNB返回连接释放响应（ Connection Release Response ) 消息。
之后， UE、 源 eNB 和目标 eNB 之间可以进行层 1 同步流程（ L1 Synchronization ) 。
812: UE 向目标 eNB 发送 RRC 连接重配置完成（ RRC Connection Reconfiguration Complete ) 消息。
813: 目标 eNB向 MME发送切换通知（ Handover Notify ) 消息。
本实施例通过核心网使得源 eNB将 U链路信息发送给目标 eNB可以在 L链路切换时， 目标 eNB建立与 RNC的连接，保证切换时数据传输吞吐量 的连续性。
图 9为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例的应用场景如下： eNB为锚点、主 RAT链路 ( L链路 )不切换，辅 RAT 链路 ( U链路 )切换； RNC之间无 Iur接口， 需要通过 RNC与核心网之间 的 Iu接口传输信息； 由非锚点 （eNB )做切换控制。
参见图 9, 本实施例的多链路的切换方法可以如下所述。
901： UE向源 RNC( Source RNC )发送 RRC测量4艮告（ RRC Measurement
Report ) 。 902: 源 RNC进行重定位（ Relocation )判决。
具体内容可以参见步骤 202。
903: 源 RNC向 SGSN发送携带 L链路信息， 例如， L链路的 eNB ID 或者 cell ID的消息， 例如重定位要求（ Relocation Required ) 消息。
904: SGSN向目标 RNC ( Target RNC )发送携带 L链路信息的消息， 例如重定位请求 ( Relocation Request ) 消息。
905:目标 RNC判决是否继续对该 UE提供多 RAT载波聚合业务传输。 具体地， 目标 RNC 可以根据自身的载波聚合能力信息、 自身与 eNB 是否存在接口以及自身当前的负载情况，判决是否继续对该 UE提供多 RAT 载波聚合业务传输。
与图 2-6所示的主链路切换不同的是， 由于本实施例是辅链路切换， 为 了节省资源，可以只在目标 RNC与 eNB存在接口且具有载波能力时，继续 切换， 否则直接返回失败响应。 即， 如果当前的负载过载、 不具有聚合能 力、 不存在接口时， 目标 RNC 向 SGSN发送携带失败原因值的消息， 例如 重定位失败（Relocation Failure ) 消息， 其中携带原因值， 例如， 目标 eNB 拥塞、 不支持聚合、 没有 Iue接口等， 之后， 由 SGSN向源 RNC发送重定 位准备失败 ( Relocation Preparation Failure )消息， 携带上述的失败原因值。
906： 目标 RNC向 eNB发送用于触发接口工作的消息， 例如连接建立 指示 ( Connection Setup Indication ) 消息。
其中，在步骤 906执行过程中， 可以去激活 L链路， 例如， 可以由 eNB 向 UE发送去激活 L链路指示， 避免 L链路数据丢失， 以避免新连接的建 立过程中， 出现数据丢失的现象或者筒化切换流程。
907: 目标 RNC 向 SGSN发送重定位请求应答 ( Relocation Request Acknowledge ) 消息。
908: SGSN向源 RNC发送重定位命令 ( Relocation Command ) 消息。 之后， 源 RNC将数据传输给目标 RNC ( Start Data Forwarding ) 。 909: 源 RNC向 eNB发送用于释放资源的请求消息， 例如连接释放请 求 ( Connection Release Request ) 消息。
910 : eNB 向源 RNC 返回相应的响应消息， 例如连接释放响应 ( Connection Release Response ) 消息。
911 : 源 RNC 向 UE 发送物理信道重配置 （ Physical Channel
Reconfiguration ) 消息。
其中， 步骤 909-910可以在步骤 911之后。 以便 L1同步实现后再删除 源 RNC和 eNB的连接，从而避免同步失败新链接建立不成功， 而原链路已 删除导致的数据丢失或掉话。
之后， UE、 源 RNC 和目标 RNC之间可以进行层 1 同步流程（ L1
Synchronization and reception of NBAP: RL Restore indication ) 。
912: UE 向目标 RNC 发送物理信道重配置完成 （Physical Channel Reconfiguration Complete ) 消息。
913: 目标 RNC向 SGSN发送重定位检测 （ Relocation Detect ) 消息。 914: 目标 RNC向 SGSN发送重定位完成（ Relocation Complete )消息。
915: 源 RNC和 SGSN释放 Iu接口信令连接（ Iu Release ) 。
本实施例通过核心网使得源 RNC将 L链路信息发送给目标 RNC, 可 以在 U链路切换时， 目标 RNC建立与 eNB的连接， 保证切换时数据传输 吞吐量的连续性。
图 10为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例的应用场景如下： eNB为锚点、主 RAT链路 ( L链路 )不切换，辅 RAT 链路 ( U链路 )切换； RNC之间存在 lur接口， 可以通过 RNC之间的 lur 接口传输信息； 由非锚点 （ eNB )做切换控制。
参见图 10, 本实施例的多链路的切换方法可以如下所述。
1001 : UE 向源 RNC ( Source RNC ) 发送 RRC 测量报告 （ RRC
Measurement Report ) 。 1002: 源 RNC进行重定位（ Relocation )判决。
具体内容可以参见步骤 202。
1003: 源 RNC向目标 RNC发送携带 L链路信息，例如， L载波的 eNB ID或者 cell ID的消息，例如增强重定位请求（ Enhanced Relocation Request ) 消息。
步骤 1004: 目标 RNC判决是否继续对该 UE提供多 RAT载波聚合业 务传输。
具体地， 目标 RNC 可以根据自身的载波聚合能力信息、 自身与 eNB 是否存在接口以及目标小区的负载情况，判决是否继续对该 UE提供多 RAT 载波聚合业务传输。
与图 2-6所示的主链路切换不同的是， 由于本实施例是辅链路切换， 为 了节省资源，可以只在目标 RNC与 eNB存在接口且具有载波能力时，继续 切换， 否则直接返回失败响应。 即， 如果当前的负载过载、 不具有聚合能 力、 不存在接口时， 目标 RNC 向 SGSN发送携带失败原因值的消息， 例如 重定位失败（Relocation Failure ) 消息， 其中携带原因值， 例如， 目标 eNB 拥塞、 不支持聚合、 没有 Iue接口等， 之后， 由 SGSN向源 RNC发送重定 位准备失败 ( Relocation Preparation Failure )消息， 携带上述的失败原因值。
1005: 目标 RNC向 eNB发送用于触发接口工作的消息，例如连接建立 指示 ( Connection Setup Indication ) 消息。
其中，在步骤 906执行过程中， 可以去激活 L链路， 例如， 可以由 eNB 向 UE发送去激活 L链路指示， 避免 L链路数据丢失， 以避免新连接的建 立过程中， 出现数据丢失的现象或者筒化切换流程。
1006: 目标 RNC向源 RNC发送增强重定位响应（ Enhanced Relocation Response ) 消息。
之后， 源 RNC将数据传输给目标 RNC ( Start Data Forwarding ) 。
1007: 源 RNC向 eNB发送用于释放资源的请求消息，例如连接释放请 求 ( Connection Release Request ) 消息。
1008 : eNB 向源 RNC 返回相应的响应消息， 例如连接释放响应 ( Connection Release Response ) 消息。
1009 : 源 RNC 向 UE 发送物理信道重配置 （ Physical Channel Reconfiguration ) 消息。
其中， 步骤 1007-1008可以在步骤 1009之后。 以便 L1 同步实现后再 删除源 RNC和 eNB的连接，从而避免同步失败新链接建立不成功， 而原链 路已删除导致的数据丢失或掉话。
1010: 源 RNC向目标 RNC发送携带聚合数据包的同步信息的消息， 例: ¾口重定位委托 ( Relocation Commit ) 消息。
此时， SGSN向源 RNC发送下行数据 ( Downlink Data ) 。
之后， UE、 源 RNC 和目标 RNC之间可以进行层 1 同步流程（ L1 Synchronization and reception of NBAP: RL Restore indication ) 。
1011 : UE 向目标 RNC发送物理信道重配置完成（Physical Channel Reconfiguration Complete ) 消息。
1012 : 目标 RNC 向 SGSN 发送增强重定位完成请求 （Enhanced Relocation Complete Request ) 消息。
1013 : 目标 RNC 向 SGSN 发送增强重定位完成响应 （Enhanced Relocation Complete Response ) 消息。
1014: 目标 RNC向源 RNC发送资源释放消息 （ Resource Release ) 。 本实施例通过 RNC之间的接口使得源 RNC将 L链路信息发送给目标 RNC , 可以在 U链路切换时， 目标 RNC建立与 eNB的连接， 保证切换时 数据传输吞吐量的连续性。
图 7-10是切换时以非锚点作切换控制， 当然， 切换时也可以是以锚点 做切换控制。 即，第二链路对应的 RAN节点为载波数据分流 /聚合控制的锚 点， 第一链路对应的 RAN节点为辅链路的 RAN节点， 所述方法包括： 第 二链路对应的载波数据分流 /聚合控制的锚点确定第一链路对应的目标辅链 路的 RAN节点； 所述锚点将所述目标辅链路的 RAN节点信息发送给第一 链路对应的源辅链路的 RAN节点， 以通过所述源辅链路的 RAN节点建立 与所述目标辅链路的 RAN的连接。 具体内容可以参见下述实施例。
图 11为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例的应用场景如下： 本实施例的应用场景如下： RNC为锚点、 主 RAT链 路（U链路） 不切换， 辅 RAT链路（L链路）切换； 由锚点 （RNC )做切 换控制。
参见图 11 , 本实施例的多链路的切换方法可以如下所述。
1101： UE向 RNC发送 RRC测量 4艮告 ( RRC Measurement Report ) 。 通过对 L载波的异系统测量可以得到该 RRC测量报告。
另外， 也可以将步骤 1101替换为如下：
UE向源 eNB发送 RRC测量报告， 该 RRC测量报告可以通过系统内 测量得到；
源 eNB根据该 RRC测量报告确定最后的小区， 之后， 向 RNC发送用 于指示最好小区的消息， 例如最好小区指示 （ Best Cell Indicator ) 。
1102: RNC进行重定位（ Relocation )判决， 确定目标 eNB。
其中， RNC可以根据该 RRC测量报告确定出目标 eNB,且该目标 eNB 与 RNC存在接口；
或者， 当源 eNB向 RNC发送最好小区指示时，根据该最好小区指示确 定目标 eNB。
1103: RNC向源小区发送携带目标 eNB信息，例如， 目标 eNB的 eNB
ID的消息， 例如切换指示 (Handover Indication)消息。
如果源 eNB与目标 eNB之间存在 X2接口， 则之后执行步骤 703-710。 1104:如果源 eNB与目标 eNB之间不存在 X2接口，则源 eNB向 RNC 发送用于切换的消息， 例如切换要求（ Handover Required ) 消息。 1105: RNC向目标 eNB发送用于建立接口的请求消息， 例如连接建立 请求 ( Connection Setup Request ) 消息。
1106:目标 eNB判决是否继续对该 UE提供多 RAT载波聚合业务传输。 具体地， 目标 eNB可以根据自身的载波聚合能力信息以及目标小区的 负载情况， 判决是否继续对该 UE提供多 RAT载波聚合业务传输。
1107:当可以继续载波聚合时，目标 eNB向 RNC发送相应的响应消息， 例^口连接建立响应 ( Connection Setup Response ) 消息。
上述的目标 eNB与 RNC之间的连接是由 RNC发起建立的， 也可以类 似与前面的实施例， 将 RNC的 ID发送给目标 eNB， 由目标 eNB发起连接 建立。
1108: RNC向源 eNB发送与切换请求对应的消息， 例如切换请求应答 ( Handover Request Acknowledge ) 消息。
1109 : 源 eNB 向 UE 发送 RRC 连接重配置 （ RRC Connection Reconfiguration ) 消息。
之后， 源 eNB可以将数据传输给目标 eNB ( Data Forwarding ) 。
1110: 源 eNB向 RNC发送用于释放资源的请求消息，例如连接释放请 求 ( Connection Release Request ) 消息。
1111 : RNC 向源 eNB 返回相应的响应消息， 例如连接释放响应 ( Connection Release Response ) 消息。
之后， UE、 源 eNB 和目标 eNB 之间可以进行层 1 同步流程（ L1
Synchronization ) 。
1112: UE向目标 eNB发送 RRC连接重配置完成（ RRC Connection Reconfiguration Complete ) 消息。
本实施例通过 RNC向目标 eNB发起连接建立请求， 可以在 L链路切 换时，建立目标 eNB与 RNC的连接，保证切换时数据传输吞吐量的连续性。
图 12为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例的应用场景如下： 本实施例的应用场景如下： eNB为锚点、 主 RAT链 路（ L链路 ) 不切换， 辅 RAT链路（ U链路 )切换； 由锚点 （ eNB )做切 换控制。
参见图 12, 本实施例的多链路的切换方法可以如下所述。
1201： UE向 eNB发送 RRC测量 4艮告 ( RRC Measurement Report ) 。 通过对 L载波的异系统测量可以得到该 RRC测量报告。
另外， 也可以将步骤 1201替换为如下：
UE向源 RNC发送 RRC测量报告， 该 RRC测量报告可以通过系统内 测量得到；
源 RNC根据该 RRC测量报告确定最后的小区， 之后， 向 eNB发送用 于指示最好小区的消息， 例如最好小区指示（ Best Cell Indicator ) 。
1202: eNB进行切换判决， 确定目标 RNC。
其中， eNB可以根据该 RRC测量报告确定出目标 RNC,且该目标 RNC 与 eNB存在接口；
或者， 当源 RNC向 eNB发送最好小区指示时，根据该最好小区指示确 定目标 RNC。
1203: eNB向源小区发送携带目标 RNC信息，例如， 目标 RNC的 RNC ID的消息， 例如切换指示 (Handover Indication)消息。
如果源 RNC 与目标 RNC 之间存在 Iur 接口， 则之后执行步骤 1003-1014。
1204:如果源 RNC与目标 RNC之间不存在 Iur接口，则源 RNC向 eNB 发送用于切换的消息， 例如切换要求（ Handover Required ) 消息。
1205: eNB向目标 RNC发送用于建立接口的请求消息， 例如连接建立 请求 ( Connection Setup Request ) 消息。
1206:目标 RNC判决是否继续对该 UE提供多 RAT载波聚合业务传输。 具体地， 目标 RNC可以根据自身的载波聚合能力信息以及目标小区的 负载情况， 判决是否继续对该 UE提供多 RAT载波聚合业务传输。
1207:当可以继续载波聚合时，目标 RNC向 eNB发送相应的响应消息， 例^口连接建立响应 ( Connection Setup Response ) 消息。
上述的目标 RNC与 eNB之间的连接是由 eNB发起建立的， 也可以类 似与前面的实施例， 将 eNB的 ID发送给目标 RNC， 由目标 RNC发起连接 建立。
1208： eNB向源 RNC发送与切换请求对应的消息， 例如切换请求应答 ( Handover Request Acknowledge ) 消息。
1209 : 源 RNC 向 UE 发送物理信道重配置 （ Physical Channel Reconfiguration ) 消息。
之后， 源 eNB可以将数据传输给目标 eNB ( Data Forwarding ) 。
1210: 源 RNC向 eNB发送用于释放资源的消息， 例如连接释放请求 ( Connection Release Request ) 消息。
1211 : eNB 向源 RNC 返回相应的响应消息， 例如连接释放响应 ( Connection Release Response ) 消息。
之后， UE、 源 RNC 和目标 RNC之间可以进行层 1 同步流程（ L1 Synchronization ) 。
1212: UE 向目标 RNC发送物理信道重配置完成（Physical Channel Reconfiguration Complete ) 消息。
1213: 目标 RNC向源 RNC发送资源释放消息 （ Resource Release ) 。 本实施例通过 eNB向目标 RNC发起连接建立请求， 可以在 U链路切 换时，建立目标 RNC与 eNB的连接，保证切换时数据传输吞吐量的连续性。
图 13为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例针对场景四， 由原 U链路切换到 U链路和 L链路， eNB为锚点。 参见 图 13 , 本实施例的多链路的切换方法可以如下所述。
1301： UE向 RNC发送 RRC测量 4艮告 ( RRC Measurement Report ) 。 1302: RNC根据本 RNC的双链路载波聚合能力（ U&L Boosting能力）、 和该 eNB是否有接口， 进行重定位 ( Relocation )判决。
例如， RNC根据 RRC测量报告中的信号强度，发现存在比 RNC小区 的信号更强的 LTE小区， 且锚点为 eNB , 此时可以进行在切换过程中实现 UE由 U单链路切换到 UL Boosting场景， 且原来的 U链路作为辅载波。
1303: RNC向 CN发送携带 U链路信息的消息， 例如， 重定位要求 ( Relocation Required )消息， 其中携带 U链路信息， 例如， U链路的 RNC ID或者 cell ID。
1304: CN 向 eNB 发送携带 U链路信息的消息， 例如， 切换请求 ( Handover Request ) 消息， 其中携带 U链路信息。
1305: eNB根据当前的负载情况判决是否继续让该 UE使用载波聚合 ( U&LBoosting ) , 可以使用 U&L Boosting则调整内部数据分配策略以及 相应配置功能。
如果 eNB的负载过载，则 eNB向 CN发送切换失败（ Handover Failure ) 消息， 其中携带原因值： 目标小区拥塞。 之后， CN向 RNC发送重定位准 备失败（ Relocation Preparation Failure ) 消息， 其中携带原因值， 例如， 目 标小区拥塞。
1306: eNB向 CN发送携带是否可继续使用载波聚合的指示信息的消 息， 例如切换请求应答 ( Handover Request Acknowledge ) 消息。
1307: CN向 RNC发送携带是否可继续使用载波聚合的指示信息的消 息， 例: ¾口重定位命令 ( Relocation Command ) 消息。
1308: RNC向 eNB发送连接建立请求（ Connection Setup Request ) 消
1309: eNB向 RNC发送连接建立响应（ Connection Setup Response )消 息。
当然， 替代步骤 1308-1309也可以是在步骤 1305判决出可以继续使用 载波聚合后，由 eNB向 RNC发送连接建立指示（ Connection Setup Indication ) 消息。
1310: RNC根据是否可继续使用载波聚合的指示信息， 重配 U载波。 1311： RNC 向 UE 发送物理信道重配置 （ Physical Channel Reconfiguration ) 消息。
之后， UE、 RNC和 eNB之间可以进行层 1同步流程（ LI Synchronization and reception of NBAP: RL Restore indication ) 。
1312 : UE 向 eNB 发送物理信道重配置完成 （ Physical Channel Reconfiguration Complete ) 消息。
1313: eNB向 CN发送重定位检测 （ Relocation Detect ) 消息。
1314: eNB向 CN发送重定位完成（ Relocation Complete ) 消息。
本实施例通过核心网使得 RNC将 U链路信息发送给 eNB, 可以在 U 链路切换时， RNC建立与 eNB的连接，保证切换数据传输吞吐量的连续性。
图 14为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例针对场景四， 由原 L链路切换到 U链路和 L链路， RNC为锚点。 参见 图 14, 本实施例的多链路的切换方法可以如下所述。
1401 : UE向 eNB发送 RRC测量 4艮告 ( RRC Measurement Report ) 。 1402: eNB根据所知的 RNC U&L Boosting能力、 是否和该 RNC配置 接口， 进行切换判决。
例如， eNB根据 RRC测量报告中的信号强度， 发现存在比 eNB小区 的信号更强的 RNC小区， 此时可以进行在切换过程中实现 UE由 L单链路 切换到 UL Boosting场景， 且原来的 L链路作为辅载波。
1403 : eNB 向 CN 发送携带 L链路信息的消息， 例如， 切换要求 ( Handover Required )消息，其中携带 L链路信息，例如， L链路的 eNB ID 或者 cell ID。
1404: CN向 RNC发送携带 L链路信息的消息， 例如， 重定位请求 ( Relocation Request ) 消息， 其中携带 U链路信息。
1405: RNC根据当前的负载情况判决是否继续让该 UE使用载波聚合 ( U&LBoosting ) , 可以使用 U&L Boosting则调整内部数据分配策略以及 相应配置功能。
如果 RNC的负载过载， 则 RNC向 CN发送重定位失败（Relocation
Failure )消息， 其中携带原因值： 目标小区拥塞。 之后， CN向 eNB发送切 换准备失败 ( Handover Preparation Failure ) 消息， 其中携带原因值， 例如， 目标小区拥塞。
1406: 如果判决出可以继续使用载波聚合， RNC向 eNB发送连接建立 指示 ( Connection Setup Indication ) 消息。
当然， 类似于图 13 , 也可以是通过连接建立请求消息和连接建立响应 消息建立 RNC和 eNB之间的连接。
1407: RNC向 CN发送携带是否可继续使用载波聚合的指示信息的消 息， 例^口重定位响应 ( Relocation Response ) 消息。
1408: CN向 eNB发送携带是否可继续使用载波聚合的指示信息的消 息， 例如切换命令 ( Handover Command ) 消息。
1409: RNC根据是否可继续使用载波聚合的指示信息， 重配 L载波。 1410： eNB 向 UE 发送 RRC 连接重配置 （ RRC Connection Reconfiguration ) 消息。
之后， UE、 RNC 和 eNB 之间可以进行层 1 同步流程 （ L1
Synchronization ) 。
1411 : UE 向 RNC 发送 RRC 连接重配置完成 （ RRC Connection Reconfiguration Complete ) 消息。
1412: RNC向 CN发送切换通知 （ Handover Notify ) 消息。
本实施例通过核心网使得 eNB将 L链路信息发送给 RNC, 可以在 L 链路切换时， RNC建立与 eNB的连接，保证切换数据传输吞吐量的连续性。 图 15为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例针对场景五， 由双载中的主链路 U链路切换到 L链路， 转换为单载传 输。
UE原来在 RNC为锚点的双载下进行数据传输，后来 UMTS信号变差， 但 L载波信号很好， 且单载 LTE下就可满足数据传输， 这时可以通过异系 统切换过程中实现 UE由 U&L Boosting双载切换到 L单载场景。
这个过程对现有协议流程的影响是， 需要将现有 UMTS 到 LTE 的 inter-RAT切换的目标节点设置为 L载波网络控制节点。 空口重配过程由 eNB下发给 UE。
参见图 15 , 本实施例的多链路的切换方法可以如下所述。 步骤 1501 : UE向 RNC发送 RRC测量 4艮告 ( RRC Measurement Report ) 。
1502: RNC进行重定位（ Relocation )判决， 将 L载波的 eNB作为异 系统切换目标节点。
1503: RNC向 CN发送重定位要求（ Relocation Required ) 消息。
1504: CN向 eNB发送切换请求（ Handover Request ) 消息。
1505: eNB向 CN发送切换请求应答（ Handover Request Acknowledge ) 消息。
1506: CN向 RNC发送重定位命令 ( Relocation Command ) 消息。
1507： eNB 向 UE 发送 RRC 连接重配置 （ RRC Connection Reconfiguration ) 消息。
之后， UE、 RNC和 eNB之间可以进行层 1同步流程（ LI Synchronization and reception of NBAP: RL Restore indication ) 。
1508 : UE 向 eNB 发送 RRC 连接重配置完成 （RRC Connection Reconfiguration Complete ) 消息。
1509: eNB向 RNC发送连接删除请求（ Connection Delete Request )消 1510: RNC向 eNB发送连接删除响应 （ Connection Delete Response ) 消息。
1511: eNB向 CN发送重定位检测 （ Relocation Detect ) 消息。
1512: eNB向 CN发送重定位完成（ Relocation Complete ) 消息。
本实施例通过空口重配过程由 eNB下发给 UE, 可以由双载中的主链 路 U链路切换到 L链路，转换为单载传输，保证业务传输吞吐量的连续性。
图 16为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例针对场景五， 由双载中的主链路 U链路切换到 L链路， 转换为单载传 输。
UE原来在 RNC为锚点的双载下进行数据传输，后来 UMTS信号变差， 但 L载波信号很好， 且单载 LTE下就可满足数据传输， 这时可以通过异系 统切换过程中实现 UE由 U&L Boosting双载切换到 L单载场景。
这个过程对现有协议流程的影响是， 需要将现有 UMTS 到 LTE 的 inter-RAT切换的目标节点设置为 L载波网络控制节点。 空口重配过程由 eNB下发给 UE。
参见图 16, 本实施例的多链路的切换方法可以如下所述。
1601： UE向 RNC发送 RRC测量 4艮告 ( RRC Measurement Report ) 。 1602: RNC进行重定位（ Relocation )判决， 将 L载波的 eNB作为异 系统切换目标节点。
1603: RNC向 eNB发送重定位要求（ Relocation Required ) 消息。 1604: eNB向 CN发送 S1建立请求（ SI Setup Request ) 消息。
1605: CN向 eNB发送 S1建立响应 （ SI Setup Response ) 消息。
1606: eNB向 RNC发送重定位响应 （ Relocation Response ) 消息。 1607： eNB 向 UE 发送 RRC 连接重配置 （ RRC Connection Reconfiguration ) 消息。
之后， UE、 RNC和 eNB之间可以进行层 1同步流程（ LI Synchronization and reception of NBAP: RL Restore indication ) 。
1608 : UE 向 eNB 发送 RRC 连接重配置完成 （ RRC Connection Reconfiguration Complete ) 消息。
1609: eNB向 RNC发送连接删除请求（ Connection Delete Request )消
1610: RNC向 eNB发送连接删除响应 （ Connection Delete Response ) 消息。
本实施例通过空口重配过程由 eNB下发给 UE, 可以由双载中的主链 路 U链路切换到 L链路， 转换为单载传输。
图 17为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例针对场景五， 由双载中的主链路 L链路切换到 U链路， 转换为单载传 输， 保证业务传输吞吐量的连续性。
UE原来在 eNB为锚点的双载下进行数据传输， 后来 LTE信号变差， 但 U载波信号很好， 且单载 UMTS下就可满足数据传输， 这时可以通过异 系统切换过程中实现 UE由 U&L Boosting双载切换到 U单载场景。
这个过程对现有协议流程的影响是， 需要将现有 LTE 到 UMTS 的 inter-RAT切换的目标节点设置为 U载波网络控制节点。 空口重配过程由 RNC下发给 UE。
参见图 17, 本实施例的多链路的切换方法可以如下所述。
1701 : UE向 eNB发送 RRC测量 4艮告 ( RRC Measurement Report ) 。
1702: eNB进行异系统切换判决。
1703: eNB向 CN发送切换要求（ Handover Required ) 消息。
1704: CN向 RNC发送重定位请求（ Relocation Request ) 消息。
1705: RNC向 CN发送重定位响应 （ Relocation Response ) 消息。
1706: CN向 eNB发送切换命令 ( Handover Command ) 消息。
1707： RNC 向 UE 发送物理信道重配置 （ Physical Channel Reconfiguration ) 消息。
之后， UE、 RNC 和 eNB 之间可以进行层 1 同步流程 （ L1 Synchronization ) 。
1708 : UE 向 RNC 发送物理信道重配置完成 （Physical Channel Reconfiguration Complete ) 消息。
1709: RNC向 eNB发送连接删除请求（ Connection Delete Request )消
1710: eNB向 RNC发送连接删除响应 （ Connection Delete Response ) 消息。
1711 : RNC向 CN发送切换通知 （ Handover Notify ) 消息。
本实施例通过空口重配过程由 RNC下发给 UE, 可以由双载中的主链 路 L链路切换到 U链路，转换为单载传输，保证业务传输吞吐量的连续性。
图 18为本发明另一实施例的一种多载波的切换方法流程示意图， 本实 施例针对场景五， 由双载中的主链路 L链路切换到 U链路， 转换为单载传 输， 保证业务传输吞吐量的连续性。
UE原来在 eNB为锚点的双载下进行数据传输， 后来 LTE信号变差， 但 U载波信号很好， 且单载 UMTS下就可满足数据传输， 这时可以通过异 系统切换过程中实现 UE由 U&L Boosting双载切换到 U单载场景。
这个过程对现有协议流程的影响是， 需要将现有 LTE 到 UMTS 的 inter-RAT切换的目标节点设置为 U载波网络控制节点。 空口重配过程由 RNC下发给 UE。
参见图 18, 本实施例的多链路的切换方法可以如下所述。
1801 : UE向 eNB发送 RRC测量 4艮告 ( RRC Measurement Report ) 。
1802: eNB进行异系统切换判决。
1803: eNB向 RNC发送切换要求（ Handover Required ) 消息。
1804: RNC向 eNB发送切换命令 ( Handover Command ) 消息。 1805： RNC 向 UE 发送物理信道重配置 （ Physical Channel Reconfiguration ) 消息。
之后， UE、 RNC 和 eNB 之间可以进行层 1 同步流程 （ L1 Synchronization ) 。
1806 : UE 向 RNC 发送物理信道重配置完成 （Physical Channel Reconfiguration Complete ) 消息。
1807: RNC向 eNB发送连接删除请求（ Connection Delete Request )消
1808: CN向 RNC发送连接删除响应（ Connection Delete Response )消
1809: CN 向 RNC 发送增强重定位完成请求 （Enhanced Relocation Complete Request ) 消息。
1810: RNC 向 CN发送增强重定位完成响应 （Enhanced Relocation Complete Response ) 消息。
本实施例通过空口重配过程由 RNC下发给 UE, 可以由双载中的主链 路 L链路切换到 U链路，转换为单载传输，保证业务传输吞吐量的连续性。 图 19为本发明一实施例的一种多载波的切换装置结构示意图， 包括接 收模块 191和建立模块 192;接收模块 191用于接收第一链路对应的源 RAN 节点发送的包含第二链路信息的消息； 建立模块 192用于根据所述第二链 路信息， 建立第一链路对应的目标 RAN节点与第二链路对应的 RAN节点 的连接， 以进行数据传输， 其中， 所述第一链路为第一 RAT网络中的链路； 所述第二链路为第二 RAT网络中的链路。 具体地，接收模块 191可以具体用于：通过核心网及 Iu接口，目标 RNC 接收源 RNC发送的包含 LTE链路的信息的消息； 或者， 通过 Iur接口， 目 标 RNC接收源 RNC发送的包含 LTE链路的信息的消息； 或者， 通过 X2 接口， 目标 eNB接收源 eNB发送的包含 UMTS链路信息的消息； 或者， 通过 S 1接口以及核心网， 目标 eNB接收源 eNB发送的包含 UMTS链路信 息的消息； 或者， 通过 BSC之间的 Iur-g接口， 目标 BSC接收源 BSC发送 的包含 LTE链路信息的消息； 或者， 通过核心网及核心网与 BSC之间的 A/Gb接口， 目标 BSC接收源 BSC发送的包含 LTE链路信息的消息。 其中， 建立模块 192可以具体用于根据所述第二链路信息， 多 RAT链 路载波聚合能力信息、与所述第二链路对应的 RAN节点的接口情况以及当 前负载情况， 建立与所述第二链路对应的 RAN节点的连接。 进一步地， 建 立模块 192包括第一单元 1921及第二单元 1922; 第一单元 1921用于向所 述第二链路对应的 RAN节点发送连接建立请求消息； 第二单元 1922用于 接收所述第二链路对应的 RAN节点返回的连接建立响应消息。 或者， 建立 模块 192具体用于向所述第二链路对应的 RAN节点发送连接建立指示消 息， 直接建立连接。 本实施例的设备还可以包括第一发送模块， 第一发送模块用于向所述 源 RAN节点发送切换请求应答消息，所述切换请求应答消息中包含是否继 续使用多 RAT链路载波聚合的指示信息。 还可以包括第二发送模块， 用于向所述源 RAN节点发送失败消息， 其 中携带失败原因值， 所述失败原因值包括： 目标 RAN节点不支持多 RAT 链路载波聚合， 目标 RAN节点与第二链路对应的 RAN无接口或者资源不 足还可以包括： 第三发送模块， 用于向所述源 RAN节点发送切换请求应答 消息。
本实施例通过建立第一链路对应的目标 RAN 节点与第二链路对应的 RAN节点的连接， 可以在第一链路进行系统内切换时， 第一链路目标 RAN 节点和第二链路 RAN节点正常传输多 RAT聚合数据， 保证业务传输吞吐 率的连续。
图 20为本发明另一实施例的一种多载波的切换装置结构示意图， 本实 施例中，第二链路对应的 RAN节点为载波数据分流 /聚合控制的锚点，第一 链路对应的 RAN节点为辅链路的 RAN节点， 所述装置位于所述锚点处， 该装置包括确定模块 201和发送模块 202;确定模块 201用于确定第一链路 对应的目标辅链路的 RAN节点； 发送模块 202用于将所述目标辅链路的 RAN节点信息发送给第一链路对应的源辅链路的 RAN节点， 以通过所述 源辅链路的 RAN节点建立与所述目标辅链路的 RAN的连接。 具体地， 确定模块 201可以具体用于根据 UE发送的 RRC测量报告， 确定目标辅链路的 RAN节点； 或者， 根据源辅链路的 RAN节点发送的最 好小区指示， 确定目标辅链路的 RAN节点。 进一步地， 本实施例的装置还可以包括切换模块 203, 切换模块 203用 于接收所述源辅链路的 RAN节点发送的切换请求消息； 向所述目标辅链路 的 RAN节点发送连接建立请求消息； 接收所述目标辅链路的 RAN节点发 送的连接建立响应消息； 向所述源辅链路的 RAN节点发送切换请求应答消
本实施例还可以包括释放模块 204,释放模块 204用于接收所述源辅链 路的 RAN节点发送的连接释放请求消息； 向所述源辅链路的 RAN节点发 送连接释放响应消息。
本实施例通过建立第一链路对应的目标 RAN 节点与第二链路对应的 RAN节点的连接， 可以在第一链路进行系统内切换时， 第一链路目标 RAN 节点和第二链路 RAN节点正常传输多 RAT聚合数据， 保证业务传输吞吐 率的连续。
图 21为本发明另一实施例的一种多载波的切换装置结构示意图， 该装 置可以位于第一链路的源 RAN节点处， 本实施例的装置包括确定模块 211 和发送模块 212; 确定模块 211用于确定能够继续使用多 RAT链路载波聚 合的 RAN节点作为第一链路的目标 RAN节点； 发送模块 212用于将携带 第二链路信息的消息发送给所述第一链路的目标 RAN节点， 以便所述第一 链路对应的目标 RAN节点与所述第二链路对应的 RAN节点建立连接后进 行数据传输。
其中， 所述确定模块 211具体用于将具有多 RAT链路载波聚合能力且 与第二链路的 RAN节点之间存在接口的第一链路的 RAN节点作为第一链 路的目标 RAN节点。 本实施例还可以包括接收模块，用于接收第一链路的目标 RAN节点根 据当前负载情况返回的切换响应消息。 本实施例通过建立第一链路对应的目标 RAN 节点与第二链路对应的 RAN节点的连接， 可以在第一链路进行系统内切换时， 第一链路目标 RAN 节点和第二链路 RAN节点正常传输多 RAT聚合数据， 保证业务传输吞吐 率的连续。 所属领域的技术人员可以清楚地了解到， 为描述的方便和筒洁， 上述 描述的系统， 装置和单元的具体工作过程， 可以参考前述方法实施例中的 对应过程， 在此不再赞述。
在本申请所提供的几个实施例中， 应该理解到， 所揭露的系统， 装置 和方法， 可以通过其它的方式实现。 例如， 以上所描述的装置实施例仅仅 是示意性的， 例如， 所述单元的划分， 仅仅为一种逻辑功能划分， 实际实 现时可以有另外的划分方式， 例如多个单元或组件可以结合或者可以集成 到另一个系统， 或一些特征可以忽略， 或不执行。 另一点， 所显示或讨论 的相互之间的耦合或直接耦合或通信连接可以是通过一些接口， 装置或单 元的间接耦合或通信连接， 可以是电性， 机械或其它的形式。
作为单元显示的部件可以是或者也可以不是物理单元， 即可以位于一个地 方， 或者也可以分布到多个网络单元上。 可以根据实际的需要选择其中的 部分或者全部单元来实现本实施例方案的目的。
另外， 在本发明各个实施例中的各功能单元可以集成在一个处理单元 中， 也可以是各个单元单独物理存在， 也可以两个或两个以上单元集成在 一个单元中。 上述集成的单元既可以采用硬件的形式实现， 也可以采用软 件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销 售或使用时， 可以存储在一个计算机可读取存储介质中。 基于这样的理解， 品的形式体现出来， 该计算机软件产品存储在一个存储介质中， 包括若干 指令用以使得一台计算机设备（可以是个人计算机， 服务器， 或者网络设 介质包括： U盘、 移动硬盘、 只读存储器（ROM, Read-Only Memory ) 、 随机存取存储器（RAM, Random Access Memory ) 、 磁碟或者光盘等各种 可以存储程序代码的介质。
最后应说明的是： 以上实施例仅用以说明本发明的技术方案， 而非对 其限制； 尽管参照前述实施例对本发明进行了详细的说明， 本领域的普通 技术人员应当理解： 其依然可以对前述各实施例所记载的技术方案进行修 改， 或者对其中部分技术特征进行等同替换； 而这些修改或者替换， 并不 使相应技术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims

权利要求
1、 一种多载波的切换方法， 其特征在于， 包括：
第一链路对应的目标无线接入网 （ RAN ) 节点接收所述第一链路对应 的源 RAN节点发送的包含第二链路信息的消息； 所述第一链路对应的所述目标 RAN节点根据所述第二链路信息，建立 与第二链路对应的 RAN节点的连接， 以进行数据传输； 其中， 所述第一链路为第一无线接入技术（RAT ) 网络中的链路； 所 述第二链路为第二 RAT网络中的链路。
2、 根据权利要求 1所述的方法， 其特征在于， 所述接收所述第一链路 对应的源 RAN节点发送的包含第二链路信息的消息， 包括：
通过核心网及 Iu接口， 目标无线网络控制器（ RNC )接收源 RNC发 送的包含长期演进（LTE )链路的信息的消息；
或者，
通过 Iur接口， 目标 RNC接收源 RNC发送的包含 LTE链路的信息的 消息；
或者，
通过 X2接口， 目标基站（ eNB )接收源 eNB发送的包含通用移动通信 系统（ UMTS )链路信息的消息；
或者，
通过 S1接口以及核心网， 目标 eNB接收源 eNB发送的包含 UMTS链 路信息的消息； 或者，
通过基站控制器（ BSC )之间的 Iur-g接口， 目标 BSC接收源 BSC发 送的包含 LTE链路信息的消息； 或者,
通过核心网及核心网与 BSC之间的 A/Gb接口， 目标 BSC接收源 BSC 发送的包含 LTE链路信息的消息。
3、 根据权利要求 1所述的方法， 其特征在于， 所述第一链路对应的目 标 RAN节点根据所述第二链路信息， 建立与第二链路对应的 RAN节点的 连接， 包括：
目标 RAN节点根据所述第二链路信息， 多 RAT链路载波聚合能力信 息、 与所述第二链路对应的 RAN节点的接口情况以及当前负载情况， 建立 与所述第二链路对应的 RAN节点的连接。
4、 根据权利要求 3所述的方法， 其特征在于， 所述建立与所述第二链 路对应的 RAN节点的连接， 包括：
向所述第二链路对应的 RAN节点发送连接建立请求消息；接收所述第 二链路对应的 RAN节点返回的连接建立响应消息；
或者，
向所述第二链路对应的 RAN节点发送连接建立指示消息， 直接建立连 接。
5、 根据权利要求 4所述的方法， 其特征在于， 还包括： 目标 RAN节点向源 RAN节点发送切换请求应答消息， 所述切换请求 应答消息中包含是否继续使用多 RAT链路载波聚合的指示信息； 或者，
目标 RAN节点向源 RAN节点发送切换请求应答消息。
6、 根据权利要求 5所述的方法， 其特征在于， 所述指示信息表明不可 以继续使用多 RAT链路载波聚合时， 携带原因值， 所述原因值包括： 目标 RAN节点不支持多 RAT链路载波聚合， 目标 RAN节点与所述第二链路对 应的 RAN节点无接口或者资源不足。
7、 根据权利要求 6所述的方法， 其特征在于， 还包括： 所述源 RAN节点向所述第二链路对应的 RAN节点发送连接释放请求， 并接收所述第二链路对应的 RAN节点返回的连接释放响应。
8、 根据权利要求 1-7任一项所述的方法， 其特征在于， 所述第一链路对应的 RAN节点为载波数据分流 /聚合控制的锚点，第二 链路对应的 RAN节点为辅链路的 RAN节点； 或
所述第二链路对应的 RAN节点为载波数据分流 /聚合控制的锚点，第一 链路对应的 RAN节点为辅链路的 RAN节点。
9、 根据权利要求 1-7任一项所述的方法， 其特征在于， 还包括： 所述第二链路的目标 RAN节点接收所述第一链路的源 RAN节点发送 的所述第一链路的目标 RAN的信息；
所述第二链路的目标 RAN节点根据所述第一链路的目标 RAN的信息， 建立与所述第一链路的目标 RAN的连接， 以进行数据传输。
10、 一种多载波的切换方法， 其特征在于， 第二链路对应的 RAN节点 为载波数据分流 /聚合控制的锚点， 第一链路对应的 RAN 节点为辅链路的 RAN节点， 所述方法包括：
第二链路对应的载波数据分流 /聚合控制的锚点确定第一链路对应的目 标辅链路的 RAN节点；
所述锚点将所述目标辅链路的 RAN节点信息发送给第一链路对应的源 辅链路的 RAN节点， 以通过所述源辅链路的 RAN节点建立与所述目标辅 链路的 RAN的连接。
11、 根据权利要求 10 所述的方法， 其特征在于， 所述目标辅链路的 RAN节点信息， 包括： 目标辅链路的 RAN节点标识。
12、 根据权利要求 10所述的方法， 其特征在于， 所述确定目标辅链路 的 RAN节点， 包括： 所述锚点根据 UE发送的 RRC测量报告， 确定目标辅链路的 RAN节 点； 或者，
所述锚点根据源辅 RAN节点发送的最好小区指示，确定目标辅链路的 RAN节点。
13、 根据权利要求 10 所述的方法， 其特征在于， 所述目标辅链路的 RAN节点建立与所述锚点的连接， 包括： 所述目标辅链路的 RAN节点向所述锚点发送连接建立请求消息，并接 收所述锚点发送的连接建立响应消息。
14、 根据权利要求 10所述的方法， 其特征在于， 还包括： 所述源辅链路的 RAN节点向所述目标辅链路的 RAN节点发送所述锚 点对应的多 RAT载波聚合主链路的信息， 目标辅链路的 RAN节点建立与 所述锚点的连接； 和 /或，
所述锚点接收所述源辅链路的 RAN节点发送的切换请求消息； 所述锚 点向所述目标辅链路的 RAN节点发送连接建立请求消息； 所述锚点接收所 述目标辅链路的 RAN节点发送的连接建立响应消息； 所述锚点向所述源辅 链路的 RAN节点发送切换请求应答消息； 和 /或，
所述锚点接收所述源辅链路的 RAN节点发送的连接释放请求消息； 所 述锚点向所述源辅链路的 RAN节点发送连接释放响应消息。
15、 一种多载波的切换方法， 其特征在于， 包括： 第一链路的源 RAN 节点确定能够继续使用多 RAT链路载波聚合的 RAN节点作为第一链路的目标 RAN节点； 第一链路的源 RAN节点将携带第二链路信息的消息发送给所述第一链 路的目标 RAN节点， 以便所述第一链路对应的目标 RAN节点与所述第二 链路对应的 RAN节点建立连接后进行数据传输。
16、 根据权利要求 15所述的方法， 其特征在于， 所述确定能够继续使 用多 RAT链路载波聚合的 RAN节点作为第一链路的目标 RAN节点，包括： 将具有多 RAT链路载波聚合能力且与第二链路的 RAN节点之间存在 接口的第一链路的 RAN节点作为第一链路的目标 RAN节点。
17、 根据权利要求 15所述的方法， 其特征在于， 还包括： 第一链路的源 RAN节点接收第一链路的目标 RAN节点根据当前负载 情况返回的切换响应消息。
18、 根据权利要求 15所述的方法， 其特征在于， 所述第一链路对应的 目标 RAN节点与所述第二链路对应的 RAN节点建立连接， 包括：
第一链路对应的目标 RAN节点向所述第二链路的 RAN节点发送连接 建立指示消息， 直接建立连接。
19、 一种多载波的切换装置， 其特征在于， 包括： 接收模块，用于接收第一链路对应的源 RAN节点发送的包含第二链路 信息的消息； 建立模块，用于根据所述第二链路信息，建立第一链路对应的目标 RAN 节点与第二链路对应的 RAN节点的连接， 以进行数据传输； 其中， 所述第一链路为第一 RAT网络中的链路； 所述第二链路为第二 RAT网络中的链路。
20、 根据权利要求 19所述的装置， 其特征在于， 所述接收模块具体用 于：
通过核心网及 Iu接口，目标 RNC接收源 RNC发送的包含 LTE链路的 信息的消息；
或者，
通过 Iur接口， 目标 RNC接收源 RNC发送的包含 LTE链路的信息的 消息；
或者，
通过 X2接口， 目标 eNB接收源 eNB发送的包含 UMTS链路信息的消 或者， 通过 S1接口以及核心网， 目标 eNB接收源 eNB发送的包含 UMTS链 路信息的消息； 或者， 通过 BSC之间的 Iur-g接口， 目标 BSC接收源 BSC发送的包含 LTE 链路信息的消息； 或者， 通过核心网及核心网与 BSC之间的 A/Gb接口， 目标 BSC接收源 BSC 发送的包含 LTE链路信息的消息。
21、 根据权利要求 19或 20所述的装置， 其特征在于， 所述建立模块 具体用于根据所述第二链路信息， 多 RAT链路载波聚合能力信息、 与所述 第二链路对应的 RAN节点的接口情况以及当前负载情况，建立与所述第二 链路对应的 RAN节点的连接。
22、 根据权利要求 21所述的装置， 其特征在于， 所述建立模块包括：
第一单元，用于向所述第二链路对应的 RAN节点发送连接建立请求消 第二单元，用于接收所述第二链路对应的 RAN节点返回的连接建立响 应消息；
或者，
所述建立模块具体用于向所述第二链路对应的 RAN节点发送连接建立 指示消息， 直接建立连接。
23、 根据权利要求 19所述的装置， 其特征在于， 还包括：
第一发送模块， 用于向所述源 RAN节点发送切换请求应答消息， 所述 切换请求应答消息中包含是否继续使用多 RAT链路载波聚合的指示信息； 和 /或，
第二发送模块， 用于向所述源 RAN节点发送失败消息， 其中携带失败 原因值， 所述失败原因值包括： 目标 RAN节点不支持多 RAT链路载波聚 合， 目标 RAN节点与第二链路对应的 RAN无接口或者资源不足； 和 /或，
第三发送模块， 用于向所述源 RAN节点发送切换请求应答消息。
24、 一种多载波的切换装置， 其特征在于， 第二链路对应的 RAN节点 为载波数据分流 /聚合控制的锚点， 第一链路对应的 RAN 节点为辅链路的 RAN节点， 所述装置位于所述锚点处， 所述装置包括： 确定模块， 用于确定第一链路对应的目标辅链路的 RAN节点； 发送模块 ,用于将所述目标辅链路的 RAN节点信息发送给第一链路对 应的源辅链路的 RAN节点， 以通过所述源辅链路的 RAN节点建立与所述 目标辅链路的 RAN的连接。
25、 根据权利要求 24所述的装置， 其特征在于， 所述确定模块具体用 于：
根据用户设备 UE发送的无线资源控制 RRC测量报告， 确定目标辅链 路的 RAN节点； 或者， 根据源辅链路的 RAN节点发送的最好小区指示， 确定目标辅链路的 RAN节点。
26、 根据权利要求 24或 25所述的装置， 其特征在于， 还包括： 切换模块， 用于接收所述源辅链路的 RAN节点发送的切换请求消息； 向所述目标辅链路的 RAN节点发送连接建立请求消息；接收所述目标辅链 路的 RAN节点发送的连接建立响应消息； 向所述源辅链路的 RAN节点发 送切换请求应答消息； 和 /或，
释放模块，用于接收所述源辅链路的 RAN节点发送的连接释放请求消 息； 向所述源辅链路的 RAN节点发送连接释放响应消息。
27、 一种多载波的切换装置， 其特征在于， 包括： 确定模块， 用于确定能够继续使用多 RAT链路载波聚合的 RAN节点 作为第一链路的目标 RAN节点；
发送模块， 用于将携带第二链路信息的消息发送给所述第一链路的目 标 RAN节点， 以便所述第一链路对应的目标 RAN节点与所述第二链路对 应的 RAN节点建立连接后进行数据传输。
28、 根据权利要求 27所述的装置， 其特征在于， 所述确定模块具体用 于将具有多 RAT链路载波聚合能力且与第二链路的 RAN节点之间存在接 口的第一链路的 RAN节点作为第一链路的目标 RAN节点。
29、 根据权利要求 27所述的装置， 其特征在于， 还包括： 接收模块，用于接收第一链路的目标 RAN节点根据当前负载情况返回 的切换响应消息。
PCT/CN2011/080287 2010-10-21 2011-09-28 一种多载波的切换方法和装置 WO2012051903A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
EP18203904.0A EP3528539A3 (en) 2010-10-21 2011-09-28 Method and device for switching of multi-carrier
EP11833809.4A EP2618609B1 (en) 2010-10-21 2011-09-28 Multi-carrier switching method and device
ES11833809T ES2717452T3 (es) 2010-10-21 2011-09-28 Método y dispositivo de conmutación de múltiples portadoras
EP20197673.5A EP3823351A1 (en) 2010-10-21 2011-09-28 Method and device for switching of multi-carrier
US13/866,416 US9445333B2 (en) 2010-10-21 2013-04-19 Method and device for switching of multi-carrier
US15/239,546 US9973991B2 (en) 2010-10-21 2016-08-17 Method and device for switching of multi-carrier
US15/949,381 US10743228B2 (en) 2010-10-21 2018-04-10 Method and device for switching of multi-carrier

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010526860.0 2010-10-21
CN201010526860.0A CN102457924B (zh) 2010-10-21 2010-10-21 一种多载波的切换方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/866,416 Continuation US9445333B2 (en) 2010-10-21 2013-04-19 Method and device for switching of multi-carrier

Publications (1)

Publication Number Publication Date
WO2012051903A1 true WO2012051903A1 (zh) 2012-04-26

Family

ID=45974681

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/080287 WO2012051903A1 (zh) 2010-10-21 2011-09-28 一种多载波的切换方法和装置

Country Status (5)

Country Link
US (3) US9445333B2 (zh)
EP (3) EP2618609B1 (zh)
CN (1) CN102457924B (zh)
ES (1) ES2717452T3 (zh)
WO (1) WO2012051903A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014021671A1 (en) * 2012-08-03 2014-02-06 Lg Electronics Inc. Method and apparatus for transmitting indication in wireless communication system
WO2014180511A1 (en) * 2013-05-10 2014-11-13 Nokia Siemens Networks Oy Method and apparatuses handling control relocation failures
EP2999267A4 (en) * 2013-06-27 2016-06-01 Huawei Tech Co Ltd METHOD FOR CONTROLLING THE DELIVERY OF USER DEVICES, BASE STATION, USER DEVICE AND SYSTEM

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10327196B2 (en) * 2012-04-09 2019-06-18 Apple Inc. Apparatus and methods for intelligent scheduling in hybrid networks based on client identity
ES2427716B1 (es) * 2012-04-24 2015-06-16 Vodafone España, S.A.U. Procedimiento para optimizar la transmisión de datos en una red de comunicación celular
CN102769882A (zh) * 2012-07-11 2012-11-07 北京大学 一种支持m2m通信的异构网络接力切换方法
CN104584463B (zh) 2012-07-26 2018-04-06 Lg 电子株式会社 使用两个或更多个无线电接入技术支持通信的方法及其装置
CN103037540B (zh) * 2012-12-25 2018-07-20 南京中兴新软件有限责任公司 群组资源释放方法、装置及系统
WO2014112917A1 (en) * 2013-01-18 2014-07-24 Telefonaktiebolaget L M Ericsson (Publ) Simultaneous handover in different domains
US9622134B2 (en) * 2013-05-06 2017-04-11 Qualcomm Incorporated Coordinating handover events across RATs
EP3016437B1 (en) * 2013-08-07 2019-01-02 Huawei Technologies Co., Ltd. Handover in dual connection mode
WO2015074678A1 (en) * 2013-11-19 2015-05-28 Telefonaktiebolaget L M Ericsson (Publ) Exchanging load information in a radio access network
US9900814B2 (en) 2014-06-09 2018-02-20 Telefonaktiebolaget Lm Ericsson (Publ) First network node, a second network node and methods relating to handover in a wireless communications network
US20170208524A1 (en) * 2014-06-19 2017-07-20 Mitsubishi Electric Corporation Base station, control station, and handover method
US10028176B2 (en) 2015-03-14 2018-07-17 Qualcomm Incorporated Carrier aggregation across different radio access technologies
CN106341846A (zh) * 2015-07-10 2017-01-18 中兴通讯股份有限公司 一种多系统聚合的方法及相应的功能组件
CN106455070B (zh) * 2015-08-12 2022-03-15 中兴通讯股份有限公司 一种控制面下行信令的传输方法及系统
CN108141879A (zh) * 2015-08-26 2018-06-08 华为技术有限公司 网络连接的切换方法及装置
US10306536B2 (en) 2017-06-15 2019-05-28 At&T Intellectual Property I, L.P. Bearer split or fast switch capability indicator
CN111052802B (zh) * 2017-09-27 2021-02-12 华为技术有限公司 一种非授权频谱上的载波切换方法、基站及终端设备
US10887072B2 (en) * 2018-03-07 2021-01-05 Nokia Solutions and Network OY Methods and apparatus for adjusting a carrier aggregation operation in a wireless communication system
EP3808122A4 (en) * 2018-06-13 2022-03-23 Sony Group Corporation SYSTEM AND METHOD FOR SUPPLYING AUXILIARY DATA TO A RADIO ACCESS NETWORK
CN111083730B (zh) * 2018-10-19 2023-01-31 中兴通讯股份有限公司 一种数据处理方法及装置、网络设备
CN111356248B (zh) * 2018-12-20 2022-05-13 大唐移动通信设备有限公司 一种接入网设备间建立连接的方法及装置
WO2021056162A1 (zh) * 2019-09-23 2021-04-01 Oppo广东移动通信有限公司 系统互操作的方法及装置
EP4009677A1 (en) * 2020-12-01 2022-06-08 Nordic Semiconductor ASA Synchronization of auxiliary activity
CN116056183A (zh) * 2021-10-28 2023-05-02 惠州Tcl移动通信有限公司 切换方法及电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1478364A (zh) * 2000-11-22 2004-02-25 ����ɭ�绰�ɷ����޹�˾ 无线接入网中的可变传输速率业务
CN101401470A (zh) * 2006-03-09 2009-04-01 交互数字技术公司 用于在两种无线接入技术之间执行切换的无线通信方法和系统
CN101860931A (zh) * 2009-04-09 2010-10-13 大唐移动通信设备有限公司 一种多载波聚合系统的小区切换方法和系统

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ATE390813T1 (de) * 2003-07-31 2008-04-15 Nokia Siemens Networks Gmbh Verfahren zur verwaltung von gemeinsame funkressourcen in einem zellularen telefonnetzwerk
FI20040280A0 (fi) * 2004-02-23 2004-02-23 Nokia Corp Menetelmä pakettikytkentäisen kanavanvaihdon suorittamiseksi matkaviestinjärjestelmässä
KR100810333B1 (ko) 2004-06-15 2008-03-04 삼성전자주식회사 광대역 무선 접속 통신 시스템에서 소프트 핸드오버 지원을 위한 장치 및 방법
AU2006267255B2 (en) * 2005-07-07 2010-03-04 Nokia Technologies Oy Handover method and apparatus between different systems
CN1909723A (zh) 2005-08-03 2007-02-07 华为技术有限公司 无线通信系统中广播邻小区系统信息的方法和装置
US8670376B2 (en) * 2008-08-12 2014-03-11 Qualcomm Incorporated Multi-carrier grant design
US20100062800A1 (en) * 2008-09-08 2010-03-11 Agere Systems Inc. Wireless communications using multiple radio access technologies simultaneously
KR101152955B1 (ko) 2008-11-12 2012-06-08 한국전자통신연구원 반송파 구성원간의 핸드오버 장치 및 방법
CN101742584B (zh) 2008-11-24 2013-08-28 华为技术有限公司 一种基站间切换的方法、系统和设备
GB2472789A (en) * 2009-08-17 2011-02-23 Nec Corp In a lte-advanced network a target enb sends a source enb information to indicate to the ue which of multiple component carriers is to be used for initail acc
US20110134831A1 (en) * 2009-12-03 2011-06-09 Nokia Corporation Architecture Providing Multi-System Carrier Aggregation
US20120314675A1 (en) * 2010-02-21 2012-12-13 Lg Electronics Inc. Method for managing carrier aggregation sets, and related devices
US8989087B2 (en) * 2010-06-15 2015-03-24 Telefonaktiebolaget L M Ericsson (Publ) Methods and devices for managing radio access in a communication system
EP2583527B1 (en) * 2010-06-15 2019-02-27 Telefonaktiebolaget LM Ericsson (publ) Methods and devices for radio access management of carrier aggregation between heterogeneous wireless networks
EP2622919B1 (en) * 2010-09-30 2020-04-08 Telefonaktiebolaget LM Ericsson (publ) Methods and nodes for handling measurements
US8989025B2 (en) * 2010-11-12 2015-03-24 Telefonaktiebolaget L M Ericsson (Publ) UE timing adjustment in a multi-RAT, carrier aggregation community system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1478364A (zh) * 2000-11-22 2004-02-25 ����ɭ�绰�ɷ����޹�˾ 无线接入网中的可变传输速率业务
CN101401470A (zh) * 2006-03-09 2009-04-01 交互数字技术公司 用于在两种无线接入技术之间执行切换的无线通信方法和系统
CN101860931A (zh) * 2009-04-09 2010-10-13 大唐移动通信设备有限公司 一种多载波聚合系统的小区切换方法和系统

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014021671A1 (en) * 2012-08-03 2014-02-06 Lg Electronics Inc. Method and apparatus for transmitting indication in wireless communication system
US9736744B2 (en) 2012-08-03 2017-08-15 Lg Electronics Inc. Method and apparatus for transmitting indication in wireless communication system
WO2014180511A1 (en) * 2013-05-10 2014-11-13 Nokia Siemens Networks Oy Method and apparatuses handling control relocation failures
EP2999267A4 (en) * 2013-06-27 2016-06-01 Huawei Tech Co Ltd METHOD FOR CONTROLLING THE DELIVERY OF USER DEVICES, BASE STATION, USER DEVICE AND SYSTEM
US10129801B2 (en) 2013-06-27 2018-11-13 Huawei Technologies Co., Ltd. Method for controlling handover of user equipment, base station, user equipment and system
EP3755053A3 (en) * 2013-06-27 2021-03-31 Huawei Technologies Co., Ltd. Method for controlling handover of user equipment, base station, user equipment, and system

Also Published As

Publication number Publication date
US20130230022A1 (en) 2013-09-05
US10743228B2 (en) 2020-08-11
EP3823351A1 (en) 2021-05-19
EP2618609B1 (en) 2019-01-09
US20180227820A1 (en) 2018-08-09
EP3528539A2 (en) 2019-08-21
ES2717452T3 (es) 2019-06-21
EP3528539A3 (en) 2019-11-06
CN102457924B (zh) 2014-12-03
EP2618609A1 (en) 2013-07-24
US9445333B2 (en) 2016-09-13
EP2618609A4 (en) 2013-12-04
US9973991B2 (en) 2018-05-15
US20160360460A1 (en) 2016-12-08
CN102457924A (zh) 2012-05-16

Similar Documents

Publication Publication Date Title
US10743228B2 (en) Method and device for switching of multi-carrier
EP2859738B1 (en) Method and system for multi-rat transmission
US10687256B2 (en) Light-weight RRC connection setup in multi-RAT network
CN109905849B (zh) 使用多连接来对业务进行多播
US9161281B2 (en) Method and apparatus for multi-rat transmission
US9510248B2 (en) Node and method for selective handover
US9781650B2 (en) Method and apparatus for performing partial handover procedure in wireless communication system
EP2774415B1 (en) Methods and network nodes for detecting short stay handover
US10412649B2 (en) Method and apparatus for performing handover procedure in wireless communication system
WO2014177090A1 (zh) 一种切换方法、主控基站及受控基站
KR20170043533A (ko) 인터/인트라 무선 액세스 기술 이동성 및 사용자 평면 스플릿 측정 구성
US20130201904A1 (en) Handover of Connection of User Equipment
WO2011006440A1 (zh) 一种切换方法和装置
EP3294003B1 (en) Cellular network relocation method and base station
JP2013535904A (ja) 情報を提供するための方法、移動局装置、基地局装置及び通信装置
WO2011088787A1 (zh) 接入点网络中的切换方法和装置
WO2012130046A1 (zh) 业务承载迁移方法及装置
WO2021088270A1 (zh) 移动性优化方法及相关装置
WO2018023544A1 (zh) 通信方法、用户设备、基站、控制面网元和通信系统
WO2017177950A1 (zh) 连接的建立方法、装置及系统
WO2017219959A1 (zh) 一种语音调度方法及装置
JP5387679B2 (ja) 基地局装置、基地局制御装置、移動端末、通信システムおよび基地局装置の制御方法
WO2013159628A1 (zh) 切换方法及设备
WO2009059556A1 (fr) Procédé, appareil et système de transfert sans coupure en liaison montante

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11833809

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2011833809

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE