EP3288310B1 - Random access method in a handover involving carrier aggregation - Google Patents
Random access method in a handover involving carrier aggregation Download PDFInfo
- Publication number
- EP3288310B1 EP3288310B1 EP17180767.0A EP17180767A EP3288310B1 EP 3288310 B1 EP3288310 B1 EP 3288310B1 EP 17180767 A EP17180767 A EP 17180767A EP 3288310 B1 EP3288310 B1 EP 3288310B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- target
- enb
- component carrier
- component carriers
- handover
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 79
- 230000002776 aggregation Effects 0.000 title description 5
- 238000004220 aggregation Methods 0.000 title description 5
- 239000000969 carrier Substances 0.000 claims description 295
- 230000005540 biological transmission Effects 0.000 claims description 9
- 238000005259 measurement Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 8
- 230000006854 communication Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000007774 longterm Effects 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 230000036963 noncompetitive effect Effects 0.000 description 2
- 101150014328 RAN2 gene Proteins 0.000 description 1
- 230000002860 competitive effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Images
Classifications
-
- 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/0077—Transmission or use of information for re-establishing the radio link of access information of target access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/0001—Arrangements for dividing the transmission path
- H04L5/0003—Two-dimensional division
- H04L5/0005—Time-frequency
- H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
- H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0037—Inter-user or inter-terminal allocation
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
- H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
- H04W74/0833—Random access procedures, e.g. with 4-step access
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
- H04W74/0833—Random access procedures, e.g. with 4-step access
- H04W74/0838—Random access procedures, e.g. with 4-step access using contention-free random access [CFRA]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/06—Reselecting a communication resource in the serving access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
-
- 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/08—Access point devices
Definitions
- the present invention relates to the field of communication technologies, and in particular, to a random access method, an evolved Node B (eNB), and a terminal equipment.
- eNB evolved Node B
- Carrier aggregation mainly aggregates multiple component carriers into one carrier higher than 20 million hertz (M) to support high data transmission speed.
- LTE-A Long Term Evolution-Advanced
- LTE-A Long Term Evolution-Advanced
- the number of downlink component carriers is greater than the number of uplink component carriers.
- a downlink bandwidth of 80 million hertz (MHz) includes four component carriers of 20 MHz.
- An uplink bandwidth of 20 MHz includes one component carrier of 20 MHz.
- a non-competitive procedure for a User Equipment (UE) to randomly access a target eNB includes the following steps.
- the UE sends a measurement report to a source eNB, and the source eNB selects a target eNB and a target cell for the UE according to the received measurement report or other radio resource information, that is, the source eNB makes a handover decision. Then, the source eNB sends a handover request message to the target eNB. After receiving the handover request message, the target eNB executes admission control and feeds back a handover request acknowledgement message to the source eNB. When receiving the handover request acknowledgement message, the source eNB sends a handover command message to the UE.
- the UE After the UE receives the handover command message, if the UE receives a dedicated random access preamble allocated by the target eNB to the UE, the UE sends a random access request message to the target eNB through the dedicated random access preamble, that is, the UE executes non-competitive random access; if the UE does not receive the dedicated random access preamble allocated by the target eNB to the UE, the UE executes competitive random access. After receiving the random access preamble sent by the UE, the target eNB sends a random access response message to the UE.
- the inventor of the present invention finds that, in the foregoing process, when the target eNB includes multiple component carriers, after the target eNB receives the random access request message, the target eNB cannot determine the component carrier which the UE is monitoring, in order to enable the UE to receive the random access response message, the target eNB needs to send the random access response message on all component carriers, thereby resulting in a waste of downlink resources.
- Document 3GPP Standard TS 36.300, V8.8.0, March 2009 discloses a random access process which applies to communication system of single carrier in handover.
- the target eNB determines a target carrier for the UE so that to the UE is to be handed over to the carrier after the handover.
- the target eNB notifies the UE of information about the target carrier by signaling.
- the target eNB receives a dedicated random access preamble sent by the UE, it should send a random access response message on the component carrier to the UE.
- Embodiments of the present invention are disclosed in the claims and provide a random access method, a target eNB and a computer software product, so that target component carriers could be decided during the UE handover between a source eNB and the target eNB.
- an embodiment of the present invention provides a random access method, which includes:
- an embodiment of the present invention further provides a target eNB, which includes a determination unit, a notification unit and a sending unit; where the determination unit includes:
- FIG. 1 is a flow chart of a random access method according to an embodiment of the present invention. The method includes the following steps.
- Step 101 A target eNB determines target component carriers to which a UE is to be handed over, and notifies the UE of information about the target component carriers through a source eNB.
- Step 102 After receiving a dedicated random access preamble sent by the UE, the target eNB sends a random access response message on at least one component carrier in the target component carriers.
- Step 101 specifically includes the following steps.
- the target eNB After receiving a handover request message sent by the source eNB, the target eNB determines the information about the target component carriers to which the UE is to be handed over according to the handover request message, and notifies the source eNB of the information about the target component carriers through a handover request acknowledgement message, and the source eNB sends the target component carriers to the UE through a handover command.
- the target eNB receives the handover request message sent by the source eNB, where the handover request message includes the UE's capability information about the target component carriers being supported; configures the target component carriers to which the UE is to be handed over according to the handover request message; and then sends the handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes information about the configured target component carriers, to which the UE is to be handed over.
- the target eNB receives the handover request message sent by the source eNB, where the handover request message includes the UE's capability information about the target component carriers being supported and the information of the target component carriers selected by the source eNB, and the target component carriers configured are the carriers to which the UE is to be handed over.
- the target eNB determines whether to allow the target component carriers, which is selected by the source eNB and to which the UE is to be handed over; if the target eNB allows the target component carriers, which is selected by the source eNB and to which the UE is to be handed over, the target eNB sends the handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes acknowledgement information of the target component carriers selected by the source eNB, or information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over; and if the target eNB does not allow the target component carriers, which is selected by the source eNB and to which the UE is to be handed over, the target eNB configures the target component carriers to which the UE is to be handed over, and sends the handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes the information about the target component carriers configured, to which the UE is to be handed over
- the method may further include the following steps.
- new uplink and/or downlink component carriers or new component carrier pairs are allocated to the UE.
- the sending, by the source eNB, the target component carriers to the UE through the handover command specifically includes: after receiving the handover acknowledgement message sent by the target eNB, sending, by the source eNB, the handover command to the UE, where the handover command includes: the information about the target component carriers configured by the target eNB, or the information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- the handover request acknowledgement message may further include bandwidths of the target component carriers configured by the target eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- the handover command may further include bandwidths of the target component carriers configured by the target eNB, and the target component carriers are the carriers to which the UE is to be handed over, or bandwidths of the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- the target component carriers may include, but is not limited to, uplink and/or downlink target component carriers or target component carrier pairs selected by the source eNB or the target eNB for the UE, or an uplink and/or a downlink component carrier or a component carrier pair used to execute random access.
- the information about the target component carriers may include, but is not limited to, frequency information, identifiers, or sequence numbers of the uplink and/or downlink target component carriers or the target component carrier pairs, or frequency information, an identifier, or a sequence number of the uplink and/or downlink component carrier or the target component carrier pair used to execute the random access.
- FIG. 2 is a flow chart of the random access method. The method includes the following steps.
- Step 201 A terminal equipment receives a handover command sent by a source eNB, where the handover command includes information about target component carriers configured by a target eNB, or information about target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- Step 202 After sending a dedicated random access preamble to the target eNB, the terminal equipment receives a random access response message on a downlink target carrier in the target component carriers configured, to which the UE is to be handed over, or on a downlink component carrier in the target component carriers selected, to which the UE is to be handed over.
- the method may further include: after sending a handover acknowledgement message to the target eNB, receiving new uplink and/or downlink target component carriers or new uplink and/or downlink target component carrier pairs allocated by the target eNB to the UE.
- the method further includes: receiving a component carrier handover command sent by the target eNB, where the component carrier handover command includes information about component carriers or component carrier pairs re-selected, to which the UE is to be handed over; handing over the UE to the component carriers or the component carrier pairs re-selected; and transmitting data on the component carriers or the component carrier pairs re-selected after handover.
- the method further includes: when the component carrier handover command sent by the target eNB is received, receiving a new timing advance command or new timing advance information sent by the target eNB.
- the transmitting the data on the component carriers or the component carrier pairs after handover further includes: transmitting the data on the component carriers or the component carrier pairs after handover through the new timing advance command or the new timing advance information.
- the component carrier handover command further includes a handover starting time of the component carrier or the component carrier pair.
- the information about the component carriers or the component carrier pairs includes: frequency information, identifiers, or sequence number information of the component carriers or the component carrier pairs.
- FIG. 3A and FIG. 3B are a specific flow chart of a random access method according to Embodiment 1 of the present invention. Referring to FIG. 3A and FIG. 3B , the method specifically includes the following steps.
- Step 301 A UE sends a measurement report to a source eNB.
- the measurement report may include signal quality information of component carriers of neighbor eNBs, where the signal quality information is measured by the UE.
- Step 302 After receiving the measurement report, the source eNB makes a handover decision to select uplink and/or downlink target component carriers or target component carrier pairs for the UE.
- the source eNB After receiving the measurement report, the source eNB makes the handover decision based on the measurement report and other radio resource information. Specifically, the source eNB may decide, according to component carriers being supported by the UE, the uplink and/or downlink target component carriers or the target component carrier pairs used by the UE when the UE accesses a target eNB. That is, the source eNB selects the uplink and/or downlink target component carriers or the target component carrier pairs for the UE based on the measurement report.
- Step 303 The source eNB sends a handover request message to the target eNB, where the handover request message includes the UE's capability information about the supported component carriers and information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- the handover request message includes the UE's capability information about the target component carriers being supported and the information about the uplink and/or downlink target component carriers or the target component carrier pairs selected by the source eNB for the UE.
- Step 304 After receiving the handover request message, the target eNB determines whether to allow the uplink and/or downlink target component carriers or the uplink and/or downlink component carrier pairs, which is selected by the source eNB and to which the UE is to be handed over; if the target eNB allows the uplink and/or downlink target component carriers or the uplink and/or downlink component carrier pairs, which is selected by the source eNB and to which the UE is to be handed over, step 305 is executed; and if the target eNB does not allow the uplink and/or downlink target component carriers or the uplink and/or downlink component carrier pairs, which is selected by the source eNB and to which the UE is to be handed over, step 305' and step 306 are executed.
- Step 305 The target eNB sends a handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes acknowledgement information of the uplink and/or downlink component carriers or the component carrier pairs selected by the source eNB for the UE, or the handover request acknowledgement message includes the information about the uplink and/or downlink target component carriers or the target component carrier pairs selected by the source eNB for the UE.
- Step 305' The target eNB configures new uplink and/or downlink target component carriers or target component carrier pairs for the UE.
- Step 306 The target eNB sends the handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes: information about the new uplink and/or downlink target component carriers or target component carrier pairs configured by the target eNB for the UE.
- the target eNB may further include bandwidths of the new uplink and/or downlink target component carriers or target component carrier pairs selected for the UE, where the bandwidths are included in the handover request acknowledgement message.
- the embodiment of the present invention is not limited thereto.
- Step 307 The source eNB sends a handover command message to the UE.
- the handover command includes the information about the uplink and/or downlink target component carriers or the target component carrier pairs selected by the source eNB for the UE.
- the handover command may further include bandwidth information of the selected uplink and/or downlink target component carriers or target component carrier pairs.
- the handover command includes the information about the uplink and/or downlink target component carriers or the target component carrier pairs selected by the target eNB for the UE.
- the handover command may further include the bandwidth information of the selected uplink and/or downlink target component carriers or target component carrier pairs.
- Step 308 After receiving the handover command, the UE sends a random access preamble to the target eNB, where the handover command includes the information about the uplink and/or downlink target component carriers or the target component carrier pairs selected for the UE.
- the handover command may further include the bandwidth information of the selected uplink and/or downlink target component carriers or target component carrier pairs.
- a process for synchronizing with a target cell is executed to access the target cell.
- the UE monitors the uplink and/or downlink target component carriers or the target component carrier pairs according to the information about the allocated uplink and/or downlink target component carriers or target component carrier pairs, where the information is in the handover command.
- Step 309 After receiving the preamble sent by the UE, the target eNB sends a random access response message to the UE on one target component carrier in the downlink target component carriers selected for the UE.
- the information about the target component carriers specifically includes the uplink and/or downlink target component carriers or the target component carrier pairs selected by the source eNB for the UE, or frequency information, identifiers, or sequence numbers of the uplink and/or downlink target component carriers or the target component carrier pairs, but the embodiment is not limited thereto.
- FIG. 4A and FIG. 4B are a specific flow chart of a random access method according to Embodiment 2 of the present invention. The method specifically includes the following steps.
- Step 401 A UE sends a measurement report to a source eNB.
- the measurement report may include signal quality information of component carriers of neighbor eNBs, where the signal quality information is measured by the UE.
- Step 402 The source eNB makes a handover decision to select an uplink and/or a downlink component carrier or target component carrier pair for the UE to use when the UE executes a random access to a target eNB.
- the source eNB makes the handover decision based on the measurement report sent by the UE and other radio resource information. That is, the source eNB may select, according to the component carriers being supported by the UE, the uplink and/or the downlink component carrier or the target component carrier pair for the UE to use when the UE executes the random access to the target eNB.
- Step 403 The source eNB sends a handover request message to the target eNB, where the handover request message includes the UE's capability information about the supported component carriers, and/or information about the component carriers or the target component carrier pairs selected by the source eNB for the UE to use when the UE executes the random access to the target eNB.
- Step 404 After receiving the handover request message, the target eNB determines whether to allow the uplink and/or the downlink component carrier or the component carrier pair used to execute the random access and selected by the source eNB for the UE; if the target eNB allows the uplink and/or downlink component carrier or the component carrier pair used to execute the random access and selected by the source eNB for the UE, step 405 is executed; and if the target eNB does not allow the uplink and/or downlink component carrier or the component carrier pair used to execute the random access and selected by the source eNB for the UE, step 405' and step 406 are executed.
- Step 405 The target eNB sends a handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes acknowledgement information of the uplink and/or downlink component carrier or the component carrier pair selected by the source eNB for the UE to use when the UE executes the random access.
- the handover request acknowledgement message includes information about the uplink and/or downlink component carriers or the component carrier pairs selected by the source eNB for the UE to use when the UE executes the random access to the target eNB.
- Step 405' The target eNB configures a new uplink and/or downlink component carrier or component carrier pair for the UE to use when the UE executes the random access.
- Step 406 The target eNB sends the handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes information about the component carrier or the component carrier pair configured by the target eNB for the UE to use when the UE executes the random access to the target eNB.
- the target eNB may further include bandwidths of the uplink and/or downlink component carriers or the component carrier pairs selected for the UE to use when the UE executes the random access to the target eNB, where the bandwidths are included in the handover request acknowledgement message.
- Step 407 After receiving the handover request acknowledgement message, the source eNB sends a handover command message to the UE.
- the handover command includes the information about the uplink and/or downlink component carriers or component carrier pairs selected by the source eNB for the UE to use when the UE executes the random access to the target eNB. Furthermore, the handover command may further include bandwidth information of the selected uplink and/or downlink component carriers or component carrier pairs.
- the handover command includes the information about the uplink and/or downlink component carriers or component carrier pairs determined by the source eNB for the UE to use when the UE executes the random access to the target eNB. Furthermore, the handover command may further include the bandwidth information of the selected uplink and/or downlink component carriers or component carrier pairs used to execute the random access to the target eNB.
- Step 408 After receiving the handover command, the UE sends a random access preamble to the target eNB, where the handover command includes the information about the uplink and/or downlink component carriers or the component carrier pairs selected for the UE. Furthermore, the handover command may further include the bandwidth information of the selected uplink and/or downlink component carriers or component carrier pairs.
- the UE executes a process for synchronizing with a target cell to access the target cell.
- the UE monitors the downlink component carriers or the component carrier pairs according to the information about the allocated uplink and/or downlink component carriers or the component carrier pairs used to execute the random access to the target eNB, where the information is in the handover command.
- the UE sends the random access preamble to the target eNB.
- Step 409 After receiving the preamble sent by the UE, the target eNB sends a random access response message to the UE on the downlink component carrier selected for the UE to use when the UE executes the random access.
- the handover response message may include information about uplink and/or downlink component carriers or component carrier pairs capable of being newly allocated by the target eNB to the UE.
- Step 410 When the UE accesses the target cell successfully, the UE sends a handover acknowledgement message to the target eNB.
- Step 411 After receiving the handover acknowledgement message sent by the UE, the target eNB allocates new uplink and/or downlink component carriers or component carrier pairs to the UE.
- the information about the uplink and/or downlink component carriers or the component carrier pairs newly allocated to the UE may be sent to the UE in a form of a Medium Access Control (MAC) Protocol Data Unit (PDU), or a physical layer control channel (PCCH) or Radio Resource Control (RRC) message, or other messages, which is not limited by the embodiment of the present invention.
- MAC Medium Access Control
- PDU Protocol Data Unit
- PCCH physical layer control channel
- RRC Radio Resource Control
- Step 412 After receiving the information about the newly allocated uplink and/or downlink component carriers or component carrier pairs, the UE monitors the new uplink and/or downlink component carriers or component carrier pairs.
- Embodiments of the present invention further provide exemplary Embodiment 3.
- An implementation process in this embodiment is similar to that in FIG. 3A and FIG. 3B or FIG. 4A and FIG. 4B . Differences lie in step 302 to step 304 in FIG. 3A and FIG. 3B or step 402 to step 404 in FIG. 4A and FIG. 4B , which are modified respectively as follows.
- Step 302 (or step 402): The source eNB makes a handover decision to select a target eNB and a target cell for the UE.
- Step 303 (or step 403): The source eNB sends a handover request message to the target eNB, where the handover request message includes the UE's capability information about the supported component carriers.
- Step 304 After receiving the handover request message, the target eNB executes admission control. If the target eNB allows the UE to access the target eNB, the target eNB configures new uplink and/or downlink target component carriers or target component carrier pairs for the UE.
- Step 305 After receiving the handover request message, the target eNB executes the admission control. If the target eNB allows the UE to access the target eNB, the target eNB configures an uplink and/or a downlink component carrier or a component carrier pair for the UE to use when the UE executes random access.
- the target eNB after the target eNB receives the handover request message, if the target eNB allows the UE to access the target eNB, the target eNB configures the new uplink and/or downlink target component carriers or target component carrier pairs for the UE, or the target eNB configures the uplink and/or downlink component carrier or component carrier pair used to execute the random access for the UE; and then the target eNB sends a configuration result to the source eNB through a handover request acknowledgement message. Subsequent execution steps, that is, step 307 to step 309 are the same as those in FIG. 3A and FIG. 3B or step 407 to step 412 are the same as those in FIG. 4A and FIG. 4B . For details, reference may be made to the foregoing description, and the details will not be described herein again.
- the information about the target component carriers specifically includes frequency information, an identifier, or a sequence number of the uplink and/or downlink component carrier or the component carrier pair selected by the source eNB for the UE to use when the UE executes the random access, or frequency information, an identifier, or a sequence number of the uplink and/or downlink component carrier or the target component carrier pair used to execute the random access.
- the target eNB configures the target component carriers to which the UE is to be handed over according to the handover request message; and then the target eNB sends a handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes the information about the target component carriers configured, to which the UE is to be handed over.
- the UE may need to be handed over between the component carriers in the communication process before and after cell handover.
- the handover of the UE between the component carriers at the source eNB or at a new serving eNB (a target eNB before the handover is completed) is described in the following embodiment.
- Embodiment 2 when the target eNB allocates the new uplink and/or downlink component carriers or component carrier pairs for the UE after receiving the handover acknowledgement message sent by the UE, and when the UE and the target eNB transmit data on the newly allocated uplink and/or downlink component carriers or the component carrier pairs, if the target eNB can re-allocate new uplink and/or downlink component carriers or component carrier pairs for the UE according to needs (for example, the allocated component carriers are insufficient or redundant or a better component carrier exists, but the embodiment is not limited thereto). Based on the foregoing embodiment, the method may further include the following steps.
- the target eNB sends a component carrier handover command to the UE, where the component carrier handover command includes information about component carriers or component carrier pairs re-selected, to which the UE is to be handed over.
- the target eNB and the UE transmit the data on the component carriers or the component carrier pairs.
- the target eNB may perform component carrier handover according to needs.
- a specific implementation process may be implemented through any embodiment in FIG. 5 to FIG. 7 .
- the handover acknowledgement message is further referred to as an RRC (Radio Resource Control) connection reconfiguration complete message.
- RRC Radio Resource Control
- FIG. 5 is a flow chart of the component carrier handover method. The method includes the following steps.
- Step 501 Receive a component carrier handover command sent by a serving eNB, where the component carrier handover command includes information about component carriers or component carrier pairs to which the UE is to be handed over.
- the serving eNB may be a source eNB of the UE before cell handover is performed or may be an eNB of the UE after the cell handover is performed, that is, a target eNB during the handover.
- Step 502 The UE is handed over to the component carriers or the component carrier pairs.
- Step 503 Transmit data on the component carriers or the component carrier pairs after handover.
- the method may further include receiving a new timing advance command or new timing advance information sent by the serving eNB when receiving the component carrier handover command sent by the serving eNB.
- the transmitting the data on the component carriers or the component carrier pairs after handover further includes transmitting, through the new timing advance command or the new timing advance information, the data on the component carriers or the component carrier pairs after handover.
- the information about the component carriers or the component carrier pairs includes: frequency information, identifiers, or sequence number information of the component carriers or the component carrier pairs.
- the method may further include: sending a component carrier handover acknowledgement message to the serving eNB.
- the component carrier handover command further includes a handover starting time of the component carrier or the component carrier pair.
- the component carriers specifically include an uplink component carrier and a downlink component carrier
- the component carrier pair specifically includes an uplink/ a downlink component carrier pair.
- uplink component carrier handover data not yet transmitted successfully on an original uplink component carrier before the handover is transmitted to the serving eNB on a new component carrier after the handover or on a component carrier that does not undergo the handover; in downlink component carrier handover, data not yet transmitted successfully on an original downlink component carrier before the handover is transmitted to the UE on a new component carrier after the handover or on a component carrier that does not undergo the handover; and in uplink/downlink component carrier pair handover, data not yet transmitted successfully on an original uplink/downlink component carrier pairs before the handover is transmitted to the UE or the serving eNB on a new component carrier pair after the handover or on a component carrier pair that does not undergo the handover.
- the component carrier handover command may adopt an MAC layer message, a physical layer message, or an RRC layer message.
- the component carrier handover command sent by the serving eNB is received to re-select the component carrier or the component carrier pair to which the UE is to be handed over, so that the terminal may receive a random access response message on the re-selected component carrier or component carrier pair.
- FIG. 6 is a flow chart of the component carrier handover method. The method includes the following steps.
- Step 601 Send a component carrier handover command to a UE, where the component carrier handover command includes information about component carriers or component carrier pairs to which the UE is to be handed over.
- Step 602 Transmit data on the component carriers or the component carrier pairs in the component carrier handover command.
- the method further includes receiving a component carrier handover acknowledgement message sent by the UE.
- the component carrier handover command is sent to the UE, so that the UE may transmit the data on the re-selected component carriers or component carrier pair and implement a random access procedure.
- FIG. 7 For specific implementation processes in FIG. 5 and FIG. 6 , reference may be made to FIG. 7 .
- FIG. 7 is a specific flow chart of a component carrier handover method according to Embodiment 4 of the present invention. Referring to FIG. 7 , the method includes the following steps.
- Step 701 A serving eNB sends a component carrier handover command to a UE, where the component carrier handover command includes information about uplink component carriers or downlink component carriers or uplink/downlink component carrier pairs to which the UE is to be handed over, and the information may be frequency information, identifiers, or sequence number information of the component carriers or the component carrier pairs.
- the component carrier handover command may be in the form of an MAC layer message, a physical layer message, or an RRC message.
- an Information Element (IE) or an MAC PDU may be added in an RRC connection configuration message.
- a PCCH may further be adopted to instruct the UE to perform rapid component carrier handover. That is, an eNB may employ a Physical Downlink Control Channel (PDCCH) (that is, the PDCCH includes the information about the uplink component carriers or the downlink component carriers or the uplink/downlink component carrier pairs to which the UE is to be handed over) to notify the UE of the target component carriers to which the UE is to be handed over.
- the component carrier handover command shall include information about starting time of the handover for the component carrier or the component carrier pair, that is, a handover starting time of the component carrier or the component carrier pair, to ensure synchronization between the UE and the eNB.
- the eNB may further send a Timing Advance Command MAC control element or timing advance information to the UE at the time of sending the component carrier handover command, or send the component carrier handover command carrying the timing advance information to the UE, which is not limited by the embodiment of the present invention.
- Step 702 After the handover succeeds, the UE sends component carrier acknowledgement information to the eNB to indicate agreeing to be handed over to the indicated component carriers to work. This step is optional.
- Step 703 After receiving the component carrier handover command sent by a serving eNB, the component carriers used by the UE is handed over to the indicated component carriers or component carrier pairs.
- Step 704 The UE and the serving eNB transmit (that is, send and receive) data on the component carriers after handover. Specifically, when receiving the timing advance information sent by the eNB, the UE adopts the new timing advance information when sending or receiving the data on the component carriers.
- the UE may further send component carrier acknowledgement information to the eNB to indicate agreeing to be handed over to the indicated component carriers or component carrier pair to work.
- user plane data processing includes the following three situations.
- FIG. 8 is a schematic structure diagram of the eNB.
- the eNB includes a determination unit 81, a notification unit 82, and a sending unit 83.
- the determination unit 81 is adapted to determine information of the target component carriers to which the UE is to be handed over.
- the notification unit 82 is adapted to notify the UE of the information about the target component carriers through a source eNB.
- the sending unit 83 is adapted to send a random access response message on at least one component carrier in the target component carriers after a dedicated random access preamble sent by the UE is received.
- the determination unit includes a message receiving unit and a component carrier determination unit.
- the message receiving unit is adapted to receive a handover request message sent by the source eNB.
- the component carrier determination unit is adapted to determine, according to the handover request message, the target component carriers to which the UE is to be handed over, after the message receiving unit receives the handover request message.
- the notification unit 82 is specifically adapted to notify, through a handover request acknowledgement message, the source eNB of the information about the target component carriers determined by the component carrier determination unit after the component carrier determination unit determines the target component carriers to which the UE is to be handed over, so that the source eNB sends the target component carriers to the UE through a handover command.
- the message receiving unit receives the handover request message sent by the source eNB, where the handover request message includes the UE's capability information about the target component carriers being supported; the component carrier determination unit configures, according to the handover request message, the target component carriers to which the UE is to be handed over; and the notification unit sends the handover request acknowledgement message to the source eNB after the component carrier determination unit determines the information about the target component carriers to which the UE is to be handed over, where the handover request acknowledgement message includes information about the target component carriers configured, to which the UE is to be handed over.
- the message receiving unit instructs the sending unit to send the random access response message on at least one component carrier in the target component carriers after receiving the dedicated random access preamble sent by the UE.
- the determination unit may further include a massage receiving unit, a judgment unit, and a component carrier determination unit.
- the massage receiving unit receives a handover request message sent by the source eNB, where the handover request message includes the UE's capability information about the target component carriers being supported and information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- the judgment unit determines, according to the handover request message received by the massage receiving unit, whether to allow the target component carriers, which is selected by the source eNB and to which the UE is to be handed over, and sends a determination result, that is, sends an allowance determination result to the notification unit directly and sends a non-allowance determination result to the component carrier determination unit.
- the notification unit When receiving the allowance determination result, the notification unit sends a handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes acknowledgement information of the target component carriers selected by the source eNB, or the information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- the component carrier determination unit configures, according to the UE's capability information about the target component carriers being supported, the target component carriers to which the UE is to be handed over, and sends a handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes information about the target component carriers configured, to which the UE is to be handed over.
- the message receiving unit instructs the sending unit to send the random access response message on at least one component carrier in the target component carriers after receiving the dedicated random access preamble sent by the UE.
- the method further includes: after receiving the handover acknowledgement message sent by the UE, allocating new uplink and/or downlink component carriers or new component carrier pairs to the UE.
- the information of the target component carriers may include, but are not limited to, uplink and/or downlink target component carriers or target component carrier pairs selected by the source eNB for the UE; or an uplink and/or a downlink component carrier or a component carrier pair used to execute random access; or frequency information, identifiers or sequence numbers of the uplink and/or downlink target component carriers or the target component carrier pairs, or frequency information, an identifier or a sequence number of the uplink and/or downlink component carrier or the target component carrier pair used to execute the random access.
- FIG. 9 is a schematic structure diagram of the terminal equipment.
- the terminal equipment includes: a handover command receiving unit 91, a sending unit 92, and a random response receiving unit 93.
- the handover command receiving unit 91 is adapted to receive a handover command sent by a source eNB, where the handover command includes information about target component carriers configured by a target eNB, or information about target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- the sending unit 92 is adapted to send a dedicated random access preamble to the target eNB after the handover command receiving unit receives the handover command.
- the random response receiving unit 93 is adapted to receive a random access response message on a downlink target carrier in the target component carriers configured for the UE or a downlink component carrier in the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over, after the sending unit sends the dedicated random access preamble.
- the terminal equipment may further include a component carrier receiving unit.
- the component carrier receiving unit is adapted to receive new uplink and/or downlink target component carriers or new uplink and/or downlink target component carrier pairs allocated by the target eNB for the UE, after a handover acknowledgement message is sent to the target eNB.
- the terminal equipment further includes a monitoring unit, adapted to monitor the target component carriers selected by the source eNB,and the target component carriers are the carriers to which the UE is to be handed over, or adapted to monitor the target component carriers configured, according to the UE's capability information about the supported component carriers, by the target eNB, and the target component carriers are the carriers to which the UE is to be handed over, which are indicated in the handover command, after the handover command receiving unit receives the handover command.
- a monitoring unit adapted to monitor the target component carriers selected by the source eNB,and the target component carriers are the carriers to which the UE is to be handed over, or adapted to monitor the target component carriers configured, according to the UE's capability information about the supported component carriers, by the target eNB, and the target component carriers are the carriers to which the UE is to be handed over, which are indicated in the handover command, after the handover command receiving unit receives the handover command.
- FIG. 10 is a schematic structure diagram of the terminal equipment.
- the terminal equipment includes: a receiving unit 1001, a handover unit 1002, and a transmission unit 1003.
- the receiving unit 1001 is adapted to receive a component carrier handover command sent by a serving eNB, where the component carrier handover command includes information about component carriers or component carrier pairs to which the UE is to be handed over.
- the handover unit 1002 is adapted to hand over the UE to the component carriers or the component carrier pairs, after the receiving unit 1001 receives the handover command.
- the transmission unit 1003 is adapted to transmit data on the component carriers or the component carrier pairs after handover, after the handover unit 1002 successfully performs the handover.
- the receiving unit 1001 is further adapted to receive a new timing advance command or new timing advance information sent by the serving eNB when receiving the component carrier handover command.
- the transmission unit 1003 is further adapted to transmit, through the new timing advance command or the new timing advance information, the data on the component carriers or the component carrier pairs after handover.
- the terminal equipment further includes a sending unit, adapted to send a component carrier handover acknowledgement message to the serving eNB after the handover unit successfully performs the handover.
- FIG. 11 is a schematic structure diagram of the eNB.
- the eNB includes a handover command sending unit 111 and a data transmission unit 112.
- the handover command sending unit 111 is adapted to send a component carrier handover command to a UE, where the handover command includes information about component carriers or component carrier pairs to which the UE is to be handed over.
- the data transmission unit 112 is adapted to transmit data on the component carriers or the component carrier pairs after the handover command sending unit 111 sends the handover command.
- the eNB further includes a receiving unit, adapted to receive a component carrier handover acknowledgement message sent by the UE, after the handover command sending unit sends the handover command.
- the source eNB when the source eNB decides to perform the handover, the source eNB sends the handover request message to the target eNB, where the handover request message includes: the UE's capability information about the target component carriers being supported, or the UE's capability information about the target component carriers being supported and the information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- the target eNB receives the handover request, two situations occur.
- the target eNB agrees with the information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over, and sends a handover request acknowledgement message indicating agreement to the source eNB; the other is that: after receiving the handover request, the target eNB configures, according to the UE's capability information about the target component carriers being supported, the target component carriers, to which the UE is to be handed over, and sends the configuration result to the source eNB through the handover request acknowledgement message.
- the source eNB After receiving the handover request acknowledgement message, the source eNB sends the handover command to the UE, where the handover command includes the target component carriers configured by the target eNB, or the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- the UE monitors the target component carriers in the handover command, and after sending the dedicated random access preamble to the target eNB, receives the random access response message on at least one target component carrier in the target component carriers which are monitored.
- the target eNB After receiving the dedicated random access preamble sent by the UE, the target eNB sends the random access response message on at least one component carrier in the target component carriers.
- the UE learns the component carriers that are used for the target eNB to send the random access response message, so as to receive the random access response message on the component carriers, thereby reducing power consumption of the UE; and meanwhile, after receiving the dedicated random access preamble, the target eNB learns the component carriers that are used for sending the random access response message, thereby increasing utilization rate of downlink resources.
- the UE learns the information about the component carriers or the component carrier pairs, to which the UE is to be handed over, is handed over to the component carriers or the component carrier pairs, and transmits the data on the component carriers or the component carrier pairs after handover, thereby reducing the power consumption of the UE, and meanwhile, the serving eNB transmits the data on the component carriers or the component carrier pairs after sending the handover command, thereby increasing the utilization rate of downlink resources.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Description
- The present invention relates to the field of communication technologies, and in particular, to a random access method, an evolved Node B (eNB), and a terminal equipment.
- With the development of wireless communications technologies, in order to satisfy requirements of the International Mobile Telecommunication Advanced (IMT-Advanced) and to support a peak data speed being up to 1G, a Long Term Evolution system currently uses a carrier aggregation technology as a method for expanding a system bandwidth. Carrier aggregation mainly aggregates multiple component carriers into one carrier higher than 20 million hertz (M) to support high data transmission speed.
- Currently, an LTE or Long Term Evolution-Advanced (LTE-A) system needs to support asymmetric carrier aggregation. Generally, the number of downlink component carriers is greater than the number of uplink component carriers. For example, a downlink bandwidth of 80 million hertz (MHz) includes four component carriers of 20 MHz. An uplink bandwidth of 20 MHz includes one component carrier of 20 MHz.
- In the current LTE system, in a handover process, a non-competitive procedure for a User Equipment (UE) to randomly access a target eNB includes the following steps.
- The UE sends a measurement report to a source eNB, and the source eNB selects a target eNB and a target cell for the UE according to the received measurement report or other radio resource information, that is, the source eNB makes a handover decision. Then, the source eNB sends a handover request message to the target eNB. After receiving the handover request message, the target eNB executes admission control and feeds back a handover request acknowledgement message to the source eNB. When receiving the handover request acknowledgement message, the source eNB sends a handover command message to the UE. After the UE receives the handover command message, if the UE receives a dedicated random access preamble allocated by the target eNB to the UE, the UE sends a random access request message to the target eNB through the dedicated random access preamble, that is, the UE executes non-competitive random access; if the UE does not receive the dedicated random access preamble allocated by the target eNB to the UE, the UE executes competitive random access. After receiving the random access preamble sent by the UE, the target eNB sends a random access response message to the UE.
- However, the inventor of the present invention finds that, in the foregoing process, when the target eNB includes multiple component carriers, after the target eNB receives the random access request message, the target eNB cannot determine the component carrier which the UE is monitoring, in order to enable the UE to receive the random access response message, the target eNB needs to send the random access response message on all component carriers, thereby resulting in a waste of downlink resources.
- Document 3GPP Standard TS 36.300, V8.8.0, March 2009, discloses a random access process which applies to communication system of single carrier in handover. In the handover process, the target eNB determines a target carrier for the UE so that to the UE is to be handed over to the carrier after the handover. The target eNB notifies the UE of information about the target carrier by signaling. After the target eNB receives a dedicated random access preamble sent by the UE, it should send a random access response message on the component carrier to the UE.
- Document Panasonic "LTE-Advanced discussion for RAN2", 3GPP Draft, R2-092394, March 2009, discloses a carrier aggregation method, in which multiple carriers can be supported by a UE for data transmission. Each of the multiple carriers is a component carrier. Each component carrier serving the UE is corresponding to a cell having its coverage.
- Embodiments of the present invention are disclosed in the claims and provide a random access method, a target eNB and a computer software product, so that target component carriers could be decided during the UE handover between a source eNB and the target eNB.
- In order to solve the above technical problems, an embodiment of the present invention provides a random access method, which includes:
- receiving, by the target evolved Node B, eNB, a handover request message sent by a source eNB, wherein the handover request message comprises a UE's capability information about at least two target component carriers being supported and information of the at least two target component carriers selected by the source eNB, and the at least two target component carriers selected by the source eNB are carriers to use when the UE executes random access to the target eNB;
- determining, by the target eNB, whether to allow the at least two target component carriers selected by the source eNB;
- if the at least two target component carriers selected by the source eNB are allowed, sending, by the target eNB, a handover request acknowledgement message to the source eNB, wherein the handover request acknowledgement message comprises the information about the at least two target component carriers selected by the source eNB; and
- if the at least two target component carriers selected by the source eNB are not allowed, configuring, by the target eNB, the at least two target component carriers to use when the UE executes random access to the target eNB and sending, by the target eNB, the handover request acknowledgement message to the source eNB, wherein the handover request acknowledgement message comprises the information about the at least two target component carriers configured; and
- after receiving a dedicated random access preamble sent by the UE, sending, by the target eNB, a random access response message on at least one component carrier in the at least two target component carriers;
- wherein the at least two target component carriers, which are selected by the source eNB or configured, are sent by the source eNB to the UE through a handover command..
- Accordingly, an embodiment of the present invention further provides a target eNB, which includes a determination unit, a notification unit and a sending unit;
where the determination unit includes: - a message receiving unit, adapted to receive a handover request message sent by a source eNB, wherein the handover request message comprises a UE's capability information about at least two target component carriers being supported and information of the at least two target component carriers selected by the source eNB, and the at least two target component carriers selected by the source eNB are carriers to use when the UE executes random access to the target eNB;
- a judgment unit, adapted to determine, according to the handover request message received by the message receiving unit, whether to allow the at least two target component carriers selected by the source eNB, send an allowance determination result to the notification unit directly if the at least two target component carriers selected by the source eNB are allowed, and send a non-allowance determination result to a component carrier determination unit if the at least two target component carriers selected by the source eNB are not allowed; and
- the component carrier determination unit, adapted to configure the at least two target component carriers to use when the UE executes random access to the target eNB according to the UE's capability information about at least two target component carriers being supported and send the handover request acknowledgement message to the source eNB when receiving the non-allowance determination result, wherein the handover request acknowledgement message comprises the information about the at least two target component carriers configured;
- wherein the notification unit is adapted to send a handover request acknowledgement message to the source eNB when receiving the allowance determination result, wherein the handover request acknowledgement message comprises the information about the at least two target component carriers selected by the source eNB; and
- wherein the sending unit is adapted to send a random access response message on at least one component carrier in the at least two target component carriers after a dedicated random access preamble sent by the UE is received.
-
-
FIG. 1 is a flow chart of a random access method according to an embodiment of the present invention; -
FIG. 2 is a flow chart of another random access method according to an embodiment of the present invention; -
FIG. 3A andFIG. 3B are a specific flow chart of a random access method according to Embodiment 1 of the present invention; -
FIG. 4A andFIG. 4B are a specific flow chart of a random access method according to Embodiment 2 of the present invention; -
FIG. 5 is a flow chart of a component carrier handover method according to an embodiment of the present invention; -
FIG. 6 is a flow chart of another component carrier handover method according to an embodiment of the present invention; -
FIG. 7 is a specific flow chart of a component carrier handover method according to Embodiment 4 of the present invention; -
FIG. 8 is a schematic structure diagram of an eNB according to an embodiment of the present invention; -
FIG. 9 is a schematic structure diagram of a terminal equipment according to an embodiment of the present invention; -
FIG. 10 is a schematic structure diagram of another terminal equipment according to an embodiment of the present invention; and -
FIG. 11 is a schematic structure diagram of another eNB according to an embodiment of the present invention. - Exemplary embodiments of the present invention will be described in detail in the following with reference to the accompanying drawings.
- Referring to
FIG.1, FIG. 1 is a flow chart of a random access method according to an embodiment of the present invention. The method includes the following steps. - Step 101: A target eNB determines target component carriers to which a UE is to be handed over, and notifies the UE of information about the target component carriers through a source eNB.
- Step 102: After receiving a dedicated random access preamble sent by the UE, the target eNB sends a random access response message on at least one component carrier in the target component carriers.
-
Step 101 specifically includes the following steps. - After receiving a handover request message sent by the source eNB, the target eNB determines the information about the target component carriers to which the UE is to be handed over according to the handover request message, and notifies the source eNB of the information about the target component carriers through a handover request acknowledgement message, and the source eNB sends the target component carriers to the UE through a handover command.
- In an exemplary embodiment, the target eNB receives the handover request message sent by the source eNB, where the handover request message includes the UE's capability information about the target component carriers being supported; configures the target component carriers to which the UE is to be handed over according to the handover request message; and then sends the handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes information about the configured target component carriers, to which the UE is to be handed over.
- In another exemplary embodiment, the target eNB receives the handover request message sent by the source eNB, where the handover request message includes the UE's capability information about the target component carriers being supported and the information of the target component carriers selected by the source eNB, and the target component carriers configured are the carriers to which the UE is to be handed over. Then, the target eNB determines whether to allow the target component carriers, which is selected by the source eNB and to which the UE is to be handed over; if the target eNB allows the target component carriers, which is selected by the source eNB and to which the UE is to be handed over, the target eNB sends the handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes acknowledgement information of the target component carriers selected by the source eNB, or information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over; and if the target eNB does not allow the target component carriers, which is selected by the source eNB and to which the UE is to be handed over, the target eNB configures the target component carriers to which the UE is to be handed over, and sends the handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes the information about the target component carriers configured, to which the UE is to be handed over.
- In this embodiment, after sending the random access response message, the method may further include the following steps.
- After a handover acknowledgement message sent by the UE is received, new uplink and/or downlink component carriers or new component carrier pairs are allocated to the UE.
- The sending, by the source eNB, the target component carriers to the UE through the handover command specifically includes: after receiving the handover acknowledgement message sent by the target eNB, sending, by the source eNB, the handover command to the UE, where the handover command includes: the information about the target component carriers configured by the target eNB, or the information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- The handover request acknowledgement message may further include bandwidths of the target component carriers configured by the target eNB, and the target component carriers are the carriers to which the UE is to be handed over. The handover command may further include bandwidths of the target component carriers configured by the target eNB, and the target component carriers are the carriers to which the UE is to be handed over, or bandwidths of the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- In the embodiment of the present invention, the target component carriers may include, but is not limited to, uplink and/or downlink target component carriers or target component carrier pairs selected by the source eNB or the target eNB for the UE, or an uplink and/or a downlink component carrier or a component carrier pair used to execute random access. The information about the target component carriers may include, but is not limited to, frequency information, identifiers, or sequence numbers of the uplink and/or downlink target component carriers or the target component carrier pairs, or frequency information, an identifier, or a sequence number of the uplink and/or downlink component carrier or the target component carrier pair used to execute the random access.
- Accordingly, an embodiment of the present invention further provides a random access method.
FIG. 2 is a flow chart of the random access method. The method includes the following steps. - Step 201: A terminal equipment receives a handover command sent by a source eNB, where the handover command includes information about target component carriers configured by a target eNB, or information about target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- Step 202: After sending a dedicated random access preamble to the target eNB, the terminal equipment receives a random access response message on a downlink target carrier in the target component carriers configured, to which the UE is to be handed over, or on a downlink component carrier in the target component carriers selected, to which the UE is to be handed over.
- After receiving the random access response message, the method may further include: after sending a handover acknowledgement message to the target eNB, receiving new uplink and/or downlink target component carriers or new uplink and/or downlink target component carrier pairs allocated by the target eNB to the UE.
- The method further includes: receiving a component carrier handover command sent by the target eNB, where the component carrier handover command includes information about component carriers or component carrier pairs re-selected, to which the UE is to be handed over; handing over the UE to the component carriers or the component carrier pairs re-selected; and transmitting data on the component carriers or the component carrier pairs re-selected after handover.
- The method further includes: when the component carrier handover command sent by the target eNB is received, receiving a new timing advance command or new timing advance information sent by the target eNB. The transmitting the data on the component carriers or the component carrier pairs after handover further includes: transmitting the data on the component carriers or the component carrier pairs after handover through the new timing advance command or the new timing advance information.
- In this embodiment, the component carrier handover command further includes a handover starting time of the component carrier or the component carrier pair.
- The information about the component carriers or the component carrier pairs includes: frequency information, identifiers, or sequence number information of the component carriers or the component carrier pairs.
- For the convenience of understanding by persons skilled in the art, a specific embodiment is provided in the following for illustration.
-
FIG. 3A andFIG. 3B are a specific flow chart of a random access method according to Embodiment 1 of the present invention. Referring toFIG. 3A andFIG. 3B , the method specifically includes the following steps. - Step 301: A UE sends a measurement report to a source eNB.
- Specifically, the measurement report may include signal quality information of component carriers of neighbor eNBs, where the signal quality information is measured by the UE.
- Step 302: After receiving the measurement report, the source eNB makes a handover decision to select uplink and/or downlink target component carriers or target component carrier pairs for the UE.
- After receiving the measurement report, the source eNB makes the handover decision based on the measurement report and other radio resource information. Specifically, the source eNB may decide, according to component carriers being supported by the UE, the uplink and/or downlink target component carriers or the target component carrier pairs used by the UE when the UE accesses a target eNB. That is, the source eNB selects the uplink and/or downlink target component carriers or the target component carrier pairs for the UE based on the measurement report.
- Step 303: The source eNB sends a handover request message to the target eNB, where the handover request message includes the UE's capability information about the supported component carriers and information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- That is, the handover request message includes the UE's capability information about the target component carriers being supported and the information about the uplink and/or downlink target component carriers or the target component carrier pairs selected by the source eNB for the UE.
- Step 304: After receiving the handover request message, the target eNB determines whether to allow the uplink and/or downlink target component carriers or the uplink and/or downlink component carrier pairs, which is selected by the source eNB and to which the UE is to be handed over; if the target eNB allows the uplink and/or downlink target component carriers or the uplink and/or downlink component carrier pairs, which is selected by the source eNB and to which the UE is to be handed over,
step 305 is executed; and if the target eNB does not allow the uplink and/or downlink target component carriers or the uplink and/or downlink component carrier pairs, which is selected by the source eNB and to which the UE is to be handed over, step 305' and step 306 are executed. - Step 305: The target eNB sends a handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes acknowledgement information of the uplink and/or downlink component carriers or the component carrier pairs selected by the source eNB for the UE, or the handover request acknowledgement message includes the information about the uplink and/or downlink target component carriers or the target component carrier pairs selected by the source eNB for the UE.
- Step 305': The target eNB configures new uplink and/or downlink target component carriers or target component carrier pairs for the UE.
- Step 306: The target eNB sends the handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes: information about the new uplink and/or downlink target component carriers or target component carrier pairs configured by the target eNB for the UE.
- The target eNB may further include bandwidths of the new uplink and/or downlink target component carriers or target component carrier pairs selected for the UE, where the bandwidths are included in the handover request acknowledgement message. The embodiment of the present invention is not limited thereto.
- Step 307: The source eNB sends a handover command message to the UE.
- If the target eNB accepts the uplink and/or downlink target component carriers or the target component carrier pairs selected by the source eNB for the UE, the handover command includes the information about the uplink and/or downlink target component carriers or the target component carrier pairs selected by the source eNB for the UE. The handover command may further include bandwidth information of the selected uplink and/or downlink target component carriers or target component carrier pairs.
- If the target eNB cannot allow all or a part of the uplink and/or downlink target component carriers or the target component carrier pairs selected by the source eNB for the UE, the handover command includes the information about the uplink and/or downlink target component carriers or the target component carrier pairs selected by the target eNB for the UE. The handover command may further include the bandwidth information of the selected uplink and/or downlink target component carriers or target component carrier pairs.
- Step 308: After receiving the handover command, the UE sends a random access preamble to the target eNB, where the handover command includes the information about the uplink and/or downlink target component carriers or the target component carrier pairs selected for the UE. The handover command may further include the bandwidth information of the selected uplink and/or downlink target component carriers or target component carrier pairs.
- That is, after the handover command is received, a process for synchronizing with a target cell is executed to access the target cell. The UE monitors the uplink and/or downlink target component carriers or the target component carrier pairs according to the information about the allocated uplink and/or downlink target component carriers or target component carrier pairs, where the information is in the handover command.
- Step 309: After receiving the preamble sent by the UE, the target eNB sends a random access response message to the UE on one target component carrier in the downlink target component carriers selected for the UE.
- In this embodiment, the information about the target component carriers specifically includes the uplink and/or downlink target component carriers or the target component carrier pairs selected by the source eNB for the UE, or frequency information, identifiers, or sequence numbers of the uplink and/or downlink target component carriers or the target component carrier pairs, but the embodiment is not limited thereto.
-
FIG. 4A andFIG. 4B are a specific flow chart of a random access method according to Embodiment 2 of the present invention. The method specifically includes the following steps. - Step 401: A UE sends a measurement report to a source eNB. Specifically, the measurement report may include signal quality information of component carriers of neighbor eNBs, where the signal quality information is measured by the UE.
- Step 402: The source eNB makes a handover decision to select an uplink and/or a downlink component carrier or target component carrier pair for the UE to use when the UE executes a random access to a target eNB.
- That is, the source eNB makes the handover decision based on the measurement report sent by the UE and other radio resource information. That is, the source eNB may select, according to the component carriers being supported by the UE, the uplink and/or the downlink component carrier or the target component carrier pair for the UE to use when the UE executes the random access to the target eNB.
- Step 403: The source eNB sends a handover request message to the target eNB, where the handover request message includes the UE's capability information about the supported component carriers, and/or information about the component carriers or the target component carrier pairs selected by the source eNB for the UE to use when the UE executes the random access to the target eNB.
- Step 404: After receiving the handover request message, the target eNB determines whether to allow the uplink and/or the downlink component carrier or the component carrier pair used to execute the random access and selected by the source eNB for the UE; if the target eNB allows the uplink and/or downlink component carrier or the component carrier pair used to execute the random access and selected by the source eNB for the UE, step 405 is executed; and if the target eNB does not allow the uplink and/or downlink component carrier or the component carrier pair used to execute the random access and selected by the source eNB for the UE, step 405' and step 406 are executed.
- Step 405: The target eNB sends a handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes acknowledgement information of the uplink and/or downlink component carrier or the component carrier pair selected by the source eNB for the UE to use when the UE executes the random access. Alternatively, the handover request acknowledgement message includes information about the uplink and/or downlink component carriers or the component carrier pairs selected by the source eNB for the UE to use when the UE executes the random access to the target eNB.
- Step 405': The target eNB configures a new uplink and/or downlink component carrier or component carrier pair for the UE to use when the UE executes the random access.
- Step 406: The target eNB sends the handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes information about the component carrier or the component carrier pair configured by the target eNB for the UE to use when the UE executes the random access to the target eNB.
- Furthermore, the target eNB may further include bandwidths of the uplink and/or downlink component carriers or the component carrier pairs selected for the UE to use when the UE executes the random access to the target eNB, where the bandwidths are included in the handover request acknowledgement message.
- Step 407: After receiving the handover request acknowledgement message, the source eNB sends a handover command message to the UE.
- If the target eNB accepts the uplink and/or downlink component carriers or component carrier pairs selected by the source eNB for the UE to use when the UE executes the random access to the target eNB, the handover command includes the information about the uplink and/or downlink component carriers or component carrier pairs selected by the source eNB for the UE to use when the UE executes the random access to the target eNB. Furthermore, the handover command may further include bandwidth information of the selected uplink and/or downlink component carriers or component carrier pairs.
- If the target eNB cannot allow all or a part of the uplink and/or downlink component carriers or component carrier pairs selected by the source eNB for the UE to use when the UE executes the random access to the target eNB, the handover command includes the information about the uplink and/or downlink component carriers or component carrier pairs determined by the source eNB for the UE to use when the UE executes the random access to the target eNB. Furthermore, the handover command may further include the bandwidth information of the selected uplink and/or downlink component carriers or component carrier pairs used to execute the random access to the target eNB.
- Step 408: After receiving the handover command, the UE sends a random access preamble to the target eNB, where the handover command includes the information about the uplink and/or downlink component carriers or the component carrier pairs selected for the UE. Furthermore, the handover command may further include the bandwidth information of the selected uplink and/or downlink component carriers or component carrier pairs.
- That is, after receiving the handover command, the UE executes a process for synchronizing with a target cell to access the target cell. The UE monitors the downlink component carriers or the component carrier pairs according to the information about the allocated uplink and/or downlink component carriers or the component carrier pairs used to execute the random access to the target eNB, where the information is in the handover command. The UE sends the random access preamble to the target eNB.
- Step 409: After receiving the preamble sent by the UE, the target eNB sends a random access response message to the UE on the downlink component carrier selected for the UE to use when the UE executes the random access.
- The handover response message may include information about uplink and/or downlink component carriers or component carrier pairs capable of being newly allocated by the target eNB to the UE.
- Step 410: When the UE accesses the target cell successfully, the UE sends a handover acknowledgement message to the target eNB.
- Step 411: After receiving the handover acknowledgement message sent by the UE, the target eNB allocates new uplink and/or downlink component carriers or component carrier pairs to the UE.
- Here, the information about the uplink and/or downlink component carriers or the component carrier pairs newly allocated to the UE may be sent to the UE in a form of a Medium Access Control (MAC) Protocol Data Unit (PDU), or a physical layer control channel (PCCH) or Radio Resource Control (RRC) message, or other messages, which is not limited by the embodiment of the present invention.
- Step 412: After receiving the information about the newly allocated uplink and/or downlink component carriers or component carrier pairs, the UE monitors the new uplink and/or downlink component carriers or component carrier pairs.
- Embodiments of the present invention further provide exemplary Embodiment 3. An implementation process in this embodiment is similar to that in
FIG. 3A andFIG. 3B orFIG. 4A andFIG. 4B . Differences lie instep 302 to step 304 inFIG. 3A andFIG. 3B or step 402 to step 404 inFIG. 4A andFIG. 4B , which are modified respectively as follows. - Step 302 (or step 402): The source eNB makes a handover decision to select a target eNB and a target cell for the UE.
- Step 303 (or step 403): The source eNB sends a handover request message to the target eNB, where the handover request message includes the UE's capability information about the supported component carriers.
- Step 304 (or step 404): After receiving the handover request message, the target eNB executes admission control. If the target eNB allows the UE to access the target eNB, the target eNB configures new uplink and/or downlink target component carriers or target component carrier pairs for the UE.
- Step 305 (or step 405): After receiving the handover request message, the target eNB executes the admission control. If the target eNB allows the UE to access the target eNB, the target eNB configures an uplink and/or a downlink component carrier or a component carrier pair for the UE to use when the UE executes random access.
- That is, in this embodiment, after the target eNB receives the handover request message, if the target eNB allows the UE to access the target eNB, the target eNB configures the new uplink and/or downlink target component carriers or target component carrier pairs for the UE, or the target eNB configures the uplink and/or downlink component carrier or component carrier pair used to execute the random access for the UE; and then the target eNB sends a configuration result to the source eNB through a handover request acknowledgement message. Subsequent execution steps, that is,
step 307 to step 309 are the same as those inFIG. 3A andFIG. 3B or step 407 to step 412 are the same as those inFIG. 4A andFIG. 4B . For details, reference may be made to the foregoing description, and the details will not be described herein again. - In this embodiment, the information about the target component carriers specifically includes frequency information, an identifier, or a sequence number of the uplink and/or downlink component carrier or the component carrier pair selected by the source eNB for the UE to use when the UE executes the random access, or frequency information, an identifier, or a sequence number of the uplink and/or downlink component carrier or the target component carrier pair used to execute the random access.
- That is, if the handover request message includes the UE's capability information about the target component carriers being supported, the target eNB configures the target component carriers to which the UE is to be handed over according to the handover request message; and then the target eNB sends a handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes the information about the target component carriers configured, to which the UE is to be handed over.
- Other implementation processes in this embodiment are similar to the corresponding processes in the foregoing embodiment and will not be described herein again.
- In Embodiment 1 to Embodiment 3, the UE may need to be handed over between the component carriers in the communication process before and after cell handover. Specifically, the handover of the UE between the component carriers at the source eNB or at a new serving eNB (a target eNB before the handover is completed) is described in the following embodiment. Particularly, in Embodiment 2, when the target eNB allocates the new uplink and/or downlink component carriers or component carrier pairs for the UE after receiving the handover acknowledgement message sent by the UE, and when the UE and the target eNB transmit data on the newly allocated uplink and/or downlink component carriers or the component carrier pairs, if the target eNB can re-allocate new uplink and/or downlink component carriers or component carrier pairs for the UE according to needs (for example, the allocated component carriers are insufficient or redundant or a better component carrier exists, but the embodiment is not limited thereto). Based on the foregoing embodiment, the method may further include the following steps.
- The target eNB sends a component carrier handover command to the UE, where the component carrier handover command includes information about component carriers or component carrier pairs re-selected, to which the UE is to be handed over.
- After handover, the target eNB and the UE transmit the data on the component carriers or the component carrier pairs. In the subsequent transmission process, the target eNB may perform component carrier handover according to needs. A specific implementation process may be implemented through any embodiment in
FIG. 5 to FIG. 7 . - In the embodiment of the present invention, the handover acknowledgement message is further referred to as an RRC (Radio Resource Control) connection reconfiguration complete message.
- Accordingly, an embodiment of the present invention further provides a component carrier handover method.
FIG. 5 is a flow chart of the component carrier handover method. The method includes the following steps. - Step 501: Receive a component carrier handover command sent by a serving eNB, where the component carrier handover command includes information about component carriers or component carrier pairs to which the UE is to be handed over.
- The serving eNB may be a source eNB of the UE before cell handover is performed or may be an eNB of the UE after the cell handover is performed, that is, a target eNB during the handover.
- Step 502: The UE is handed over to the component carriers or the component carrier pairs.
- Step 503: Transmit data on the component carriers or the component carrier pairs after handover.
- The method may further include receiving a new timing advance command or new timing advance information sent by the serving eNB when receiving the component carrier handover command sent by the serving eNB.
- The transmitting the data on the component carriers or the component carrier pairs after handover further includes transmitting, through the new timing advance command or the new timing advance information, the data on the component carriers or the component carrier pairs after handover.
- The information about the component carriers or the component carrier pairs includes: frequency information, identifiers, or sequence number information of the component carriers or the component carrier pairs.
- The method may further include: sending a component carrier handover acknowledgement message to the serving eNB.
- The component carrier handover command further includes a handover starting time of the component carrier or the component carrier pair.
- In this embodiment, the component carriers specifically include an uplink component carrier and a downlink component carrier, and the component carrier pair specifically includes an uplink/ a downlink component carrier pair.
- In a handover process of the component carrier handover, in uplink component carrier handover, data not yet transmitted successfully on an original uplink component carrier before the handover is transmitted to the serving eNB on a new component carrier after the handover or on a component carrier that does not undergo the handover; in downlink component carrier handover, data not yet transmitted successfully on an original downlink component carrier before the handover is transmitted to the UE on a new component carrier after the handover or on a component carrier that does not undergo the handover; and in uplink/downlink component carrier pair handover, data not yet transmitted successfully on an original uplink/downlink component carrier pairs before the handover is transmitted to the UE or the serving eNB on a new component carrier pair after the handover or on a component carrier pair that does not undergo the handover.
- The component carrier handover command may adopt an MAC layer message, a physical layer message, or an RRC layer message.
- In this embodiment, the component carrier handover command sent by the serving eNB is received to re-select the component carrier or the component carrier pair to which the UE is to be handed over, so that the terminal may receive a random access response message on the re-selected component carrier or component carrier pair.
- Accordingly, an embodiment of the present invention further provides a component carrier handover method.
FIG. 6 is a flow chart of the component carrier handover method. The method includes the following steps. - Step 601: Send a component carrier handover command to a UE, where the component carrier handover command includes information about component carriers or component carrier pairs to which the UE is to be handed over.
- Step 602: Transmit data on the component carriers or the component carrier pairs in the component carrier handover command.
- The method further includes receiving a component carrier handover acknowledgement message sent by the UE.
- In this embodiment, the component carrier handover command is sent to the UE, so that the UE may transmit the data on the re-selected component carriers or component carrier pair and implement a random access procedure.
- For specific implementation processes in
FIG. 5 and FIG. 6 , reference may be made toFIG. 7 . -
FIG. 7 is a specific flow chart of a component carrier handover method according to Embodiment 4 of the present invention. Referring toFIG. 7 , the method includes the following steps. - Step 701: A serving eNB sends a component carrier handover command to a UE, where the component carrier handover command includes information about uplink component carriers or downlink component carriers or uplink/downlink component carrier pairs to which the UE is to be handed over, and the information may be frequency information, identifiers, or sequence number information of the component carriers or the component carrier pairs.
- The component carrier handover command may be in the form of an MAC layer message, a physical layer message, or an RRC message. For example, an Information Element (IE) or an MAC PDU may be added in an RRC connection configuration message. Moreover, a PCCH may further be adopted to instruct the UE to perform rapid component carrier handover. That is, an eNB may employ a Physical Downlink Control Channel (PDCCH) (that is, the PDCCH includes the information about the uplink component carriers or the downlink component carriers or the uplink/downlink component carrier pairs to which the UE is to be handed over) to notify the UE of the target component carriers to which the UE is to be handed over. Moreover, the component carrier handover command shall include information about starting time of the handover for the component carrier or the component carrier pair, that is, a handover starting time of the component carrier or the component carrier pair, to ensure synchronization between the UE and the eNB.
- Optionally, the eNB may further send a Timing Advance Command MAC control element or timing advance information to the UE at the time of sending the component carrier handover command, or send the component carrier handover command carrying the timing advance information to the UE, which is not limited by the embodiment of the present invention.
- Step 702: After the handover succeeds, the UE sends component carrier acknowledgement information to the eNB to indicate agreeing to be handed over to the indicated component carriers to work. This step is optional.
- Step 703: After receiving the component carrier handover command sent by a serving eNB, the component carriers used by the UE is handed over to the indicated component carriers or component carrier pairs.
- Step 704: The UE and the serving eNB transmit (that is, send and receive) data on the component carriers after handover. Specifically, when receiving the timing advance information sent by the eNB, the UE adopts the new timing advance information when sending or receiving the data on the component carriers.
- Optionally, before the handover moment of the component carriers or the component carrier pair arrives, the UE may further send component carrier acknowledgement information to the eNB to indicate agreeing to be handed over to the indicated component carriers or component carrier pair to work.
- In the handover process in this embodiment, user plane data processing includes the following three situations.
- (1) In downlink component carrier handover, data not yet transmitted successfully to the UE (including data not yet transmitted by the eNB to the UE and data not yet correctly received and acknowledged by the UE before handover) on a replaced serving component carrier (that is, an original serving component carrier) during the handover is transmitted or retransmitted to the UE on a component carrier that does not undergo the handover or on a new component carrier after the handover.
- (2) In uplink component carrier handover, data not yet transmitted successfully to the eNB (including data not yet transmitted by the UE to the eNB and data not correctly received and acknowledged by the eNB before handover) on a replaced serving component carrier during the handover is transmitted or retransmitted to the eNB on a component carrier that does not undergo the handover or on a new component carrier after the handover.
- (3) In uplink and downlink component carriers/component carrier pair handover, data not yet transmitted successfully (data not yet transmitted by the UE to the eNB and data not correctly received and acknowledged by the eNB before handover and data not transmitted by the eNB to the UE and data not correctly received and acknowledged by the UE before handover) on replaced serving component carriers/a component carrier pair during the handover is transmitted or retransmitted on the component carrier that does not undergo the handover or on the new component carrier after the handover.
- Based on the implementation process of the foregoing method, an embodiment of the present invention further provides an eNB.
FIG. 8 is a schematic structure diagram of the eNB. The eNB includes adetermination unit 81, anotification unit 82, and a sendingunit 83. Thedetermination unit 81 is adapted to determine information of the target component carriers to which the UE is to be handed over. Thenotification unit 82 is adapted to notify the UE of the information about the target component carriers through a source eNB. The sendingunit 83 is adapted to send a random access response message on at least one component carrier in the target component carriers after a dedicated random access preamble sent by the UE is received. - The determination unit includes a message receiving unit and a component carrier determination unit. The message receiving unit is adapted to receive a handover request message sent by the source eNB. The component carrier determination unit is adapted to determine, according to the handover request message, the target component carriers to which the UE is to be handed over, after the message receiving unit receives the handover request message. The
notification unit 82 is specifically adapted to notify, through a handover request acknowledgement message, the source eNB of the information about the target component carriers determined by the component carrier determination unit after the component carrier determination unit determines the target component carriers to which the UE is to be handed over, so that the source eNB sends the target component carriers to the UE through a handover command. - A specific implementation process is as follows.
- The message receiving unit receives the handover request message sent by the source eNB, where the handover request message includes the UE's capability information about the target component carriers being supported; the component carrier determination unit configures, according to the handover request message, the target component carriers to which the UE is to be handed over; and the notification unit sends the handover request acknowledgement message to the source eNB after the component carrier determination unit determines the information about the target component carriers to which the UE is to be handed over, where the handover request acknowledgement message includes information about the target component carriers configured, to which the UE is to be handed over. After the handover request acknowledgement message is sent, the message receiving unit instructs the sending unit to send the random access response message on at least one component carrier in the target component carriers after receiving the dedicated random access preamble sent by the UE.
- Another specific implementation process is as follows. The determination unit may further include a massage receiving unit, a judgment unit, and a component carrier determination unit.
- The massage receiving unit receives a handover request message sent by the source eNB, where the handover request message includes the UE's capability information about the target component carriers being supported and information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- The judgment unit determines, according to the handover request message received by the massage receiving unit, whether to allow the target component carriers, which is selected by the source eNB and to which the UE is to be handed over, and sends a determination result, that is, sends an allowance determination result to the notification unit directly and sends a non-allowance determination result to the component carrier determination unit.
- When receiving the allowance determination result, the notification unit sends a handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes acknowledgement information of the target component carriers selected by the source eNB, or the information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over.
- When receiving the non-allowance determination result, the component carrier determination unit configures, according to the UE's capability information about the target component carriers being supported, the target component carriers to which the UE is to be handed over, and sends a handover request acknowledgement message to the source eNB, where the handover request acknowledgement message includes information about the target component carriers configured, to which the UE is to be handed over. After the handover request acknowledgement message is sent, the message receiving unit instructs the sending unit to send the random access response message on at least one component carrier in the target component carriers after receiving the dedicated random access preamble sent by the UE.
- In this embodiment, after sending the random access response message, the method further includes: after receiving the handover acknowledgement message sent by the UE, allocating new uplink and/or downlink component carriers or new component carrier pairs to the UE.
- It should be noted that, in the embodiment of the present invention, the information of the target component carriers may include, but are not limited to, uplink and/or downlink target component carriers or target component carrier pairs selected by the source eNB for the UE; or an uplink and/or a downlink component carrier or a component carrier pair used to execute random access; or frequency information, identifiers or sequence numbers of the uplink and/or downlink target component carriers or the target component carrier pairs, or frequency information, an identifier or a sequence number of the uplink and/or downlink component carrier or the target component carrier pair used to execute the random access.
- For details of an implementation process of functions and effects of units in the eNB, reference may be made to the implementation process of the foregoing method, and the details will not be described herein again.
- Accordingly, an embodiment of the present invention further provides a terminal equipment.
FIG. 9 is a schematic structure diagram of the terminal equipment. The terminal equipment includes: a handovercommand receiving unit 91, a sendingunit 92, and a randomresponse receiving unit 93. The handovercommand receiving unit 91 is adapted to receive a handover command sent by a source eNB, where the handover command includes information about target component carriers configured by a target eNB, or information about target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over. The sendingunit 92 is adapted to send a dedicated random access preamble to the target eNB after the handover command receiving unit receives the handover command. The randomresponse receiving unit 93 is adapted to receive a random access response message on a downlink target carrier in the target component carriers configured for the UE or a downlink component carrier in the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over, after the sending unit sends the dedicated random access preamble. - After the random response receiving unit receives the random access response message, the terminal equipment may further include a component carrier receiving unit.
- The component carrier receiving unit is adapted to receive new uplink and/or downlink target component carriers or new uplink and/or downlink target component carrier pairs allocated by the target eNB for the UE, after a handover acknowledgement message is sent to the target eNB.
- The terminal equipment further includes a monitoring unit, adapted to monitor the target component carriers selected by the source eNB,and the target component carriers are the carriers to which the UE is to be handed over, or adapted to monitor the target component carriers configured, according to the UE's capability information about the supported component carriers, by the target eNB, and the target component carriers are the carriers to which the UE is to be handed over, which are indicated in the handover command, after the handover command receiving unit receives the handover command.
- For details of an implementation process of functions and effects of units in the eNB, reference may be made to the implementation process of the foregoing method, and the details will not be described herein again.
- Accordingly, an embodiment of the present invention further provides a terminal equipment.
FIG. 10 is a schematic structure diagram of the terminal equipment. The terminal equipment includes: a receivingunit 1001, ahandover unit 1002, and atransmission unit 1003. The receivingunit 1001 is adapted to receive a component carrier handover command sent by a serving eNB, where the component carrier handover command includes information about component carriers or component carrier pairs to which the UE is to be handed over. Thehandover unit 1002 is adapted to hand over the UE to the component carriers or the component carrier pairs, after thereceiving unit 1001 receives the handover command. Thetransmission unit 1003 is adapted to transmit data on the component carriers or the component carrier pairs after handover, after thehandover unit 1002 successfully performs the handover. - The receiving
unit 1001 is further adapted to receive a new timing advance command or new timing advance information sent by the serving eNB when receiving the component carrier handover command. Thetransmission unit 1003 is further adapted to transmit, through the new timing advance command or the new timing advance information, the data on the component carriers or the component carrier pairs after handover. - The terminal equipment further includes a sending unit, adapted to send a component carrier handover acknowledgement message to the serving eNB after the handover unit successfully performs the handover.
- For details of an implementation process of functions and effects of units in the terminal equipment, reference may be made to the implementation process of the foregoing method, and the details will not be described herein again.
- Accordingly, an embodiment of the present invention further provides an eNB.
FIG. 11 is a schematic structure diagram of the eNB. The eNB includes a handover command sending unit 111 and adata transmission unit 112. The handover command sending unit 111 is adapted to send a component carrier handover command to a UE, where the handover command includes information about component carriers or component carrier pairs to which the UE is to be handed over. Thedata transmission unit 112 is adapted to transmit data on the component carriers or the component carrier pairs after the handover command sending unit 111 sends the handover command. - The eNB further includes a receiving unit, adapted to receive a component carrier handover acknowledgement message sent by the UE, after the handover command sending unit sends the handover command.
- For details of an implementation process of functions and effects of units in the eNB, reference may be made to the implementation process of the foregoing method, and the details will not be described herein again.
- It can be seen that, in the embodiment of the present invention, when the source eNB decides to perform the handover, the source eNB sends the handover request message to the target eNB, where the handover request message includes: the UE's capability information about the target component carriers being supported, or the UE's capability information about the target component carriers being supported and the information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over. After the target eNB receives the handover request, two situations occur. One is that the target eNB agrees with the information about the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over, and sends a handover request acknowledgement message indicating agreement to the source eNB; the other is that: after receiving the handover request, the target eNB configures, according to the UE's capability information about the target component carriers being supported, the target component carriers, to which the UE is to be handed over, and sends the configuration result to the source eNB through the handover request acknowledgement message. After receiving the handover request acknowledgement message, the source eNB sends the handover command to the UE, where the handover command includes the target component carriers configured by the target eNB, or the target component carriers selected by the source eNB, and the target component carriers are the carriers to which the UE is to be handed over. After receiving the handover command, the UE monitors the target component carriers in the handover command, and after sending the dedicated random access preamble to the target eNB, receives the random access response message on at least one target component carrier in the target component carriers which are monitored. Similarly, after receiving the dedicated random access preamble sent by the UE, the target eNB sends the random access response message on at least one component carrier in the target component carriers. It can be seen that: after receiving the handover command, the UE learns the component carriers that are used for the target eNB to send the random access response message, so as to receive the random access response message on the component carriers, thereby reducing power consumption of the UE; and meanwhile, after receiving the dedicated random access preamble, the target eNB learns the component carriers that are used for sending the random access response message, thereby increasing utilization rate of downlink resources. Similarly, after receiving the handover command, the UE learns the information about the component carriers or the component carrier pairs, to which the UE is to be handed over, is handed over to the component carriers or the component carrier pairs, and transmits the data on the component carriers or the component carrier pairs after handover, thereby reducing the power consumption of the UE, and meanwhile, the serving eNB transmits the data on the component carriers or the component carrier pairs after sending the handover command, thereby increasing the utilization rate of downlink resources.
Claims (14)
- A random access method, comprising:receiving (403), by the target evolved Node B, eNB, a handover request message sent by a source eNB, wherein the handover request message comprises a User Equipment, UE's capability information about at least two target component carriers being supported and information of the at least two target component carriers selected by the source eNB, and the at least two target component carriers selected by the source eNB are carriers to use when the UE executes random access to the target eNB;determining (404), by the target eNB, whether to allow the at least two target component carriers selected by the source eNB;if the at least two target component carriers selected by the source eNB are allowed, sending (405), by the target eNB, a handover request acknowledgement message to the source eNB, wherein the handover request acknowledgement message comprises the information about the at least two target component carriers selected by the source eNB; andif the at least two target component carriers selected by the source eNB are not allowed, configuring (405'), by the target eNB, the at least two target component carriers to use when the UE executes random access to the target eNB and sending (406), by the target eNB, the handover request acknowledgement message to the source eNB, wherein the handover request acknowledgement message comprises the information about the at least two target component carriers configured; andafter receiving a dedicated random access preamble sent by the UE, sending (102, 409), by the target eNB, a random access response message on at least one component carrier in the at least two target component carriers;wherein the at least two target component carriers, which are selected by the source eNB or configured, are sent by the source eNB to the UE through a handover command.
- The method according to claim 1, wherein after the sending (102, 409) the random access response message, the method further comprises:
after receiving a handover acknowledgement message sent by the UE, allocating (411), by the target eNB, at least one of the following elements to the UE: a new uplink component carrier, a new downlink component carrier and a new component carrier pair. - The method according to claim 1 or 2, wherein when the target eNB is required to re-allocate at least one of the following elements to which the UE is to be handed over for the UE: a new uplink component carrier, a new downlink component carrier and a new component carrier pair, the method further comprises:sending (601), by the target eNB, a component carrier handover command to the UE, wherein the component carrier handover command comprises information about the at least one of the elements re-allocated; andtransmitting (602), by the target eNB, data on the at least one of the elements re-allocated after handover.
- The method according to any one of claims 1 to 3, wherein the sending (407), by the source eNB, the at least two target component carriers to the UE through the handover command comprises:
after receiving a handover acknowledgement message sent by the target eNB, sending, by the source eNB, the handover command to the UE, wherein the handover command comprises: the information about the at least two target component carriers configured by the target eNB or selected by the source eNB. - The method according to any one of claims 1 to 4, wherein the handover request acknowledgement message further comprises bandwidths of the at least two target component carriers configured by the target eNB; and
the handover command further comprises the bandwidths of the at least two target component carriers configured by the target eNB, or bandwidths of the at least two target component carriers selected by the source eNB. - The method according to any one of claims 1 to 5, wherein the at least two target component carriers comprises at least one of a uplink target component carrier, a downlink target component carrier and a target component carrier pair selected for the UE; and
the information about the at least two target component carriers comprises: frequency information, an identifier, or a sequence number of the at least one of the uplink target component carrier, the downlink target component carrier and the target component carrier pair selected for the UE. - A target evolved Node B, eNB, wherein the target eNB comprises a determination unit (81), a notification unit (82) and a sending unit (83);
wherein the determination unit (81) comprises:a message receiving unit, adapted to receive a handover request message sent by a source eNB, wherein the handover request message comprises a User Equipment, UE's capability information about at least two target component carriers being supported and information of the at least two target component carriers selected by the source eNB, and the at least two target component carriers selected by the source eNB are carriers to use when the UE executes random access to the target eNB;a judgment unit, adapted to determine, according to the handover request message received by the message receiving unit, whether to allow the at least two target component carriers selected by the source eNB, send an allowance determination result to the notification unit (82) directly if the at least two target component carriers selected by the source eNB are allowed, and send a non-allowance determination result to a component carrier determination unit if the at least two target component carriers selected by the source eNB are not allowed; andthe component carrier determination unit, adapted to configure the at least two target component carriers to use when the UE executes random access to the target eNB according to the UE's capability information about at least two target component carriers being supported and send a handover request acknowledgement message to the source eNB when receiving the non-allowance determination result, wherein the handover request acknowledgement message comprises the information about the at least two target component carriers configured;wherein the notification unit (82) is adapted to send a handover request acknowledgement message to the source eNB when receiving the allowance determination result, wherein the handover request acknowledgement message comprises the information about the at least two target component carriers selected by the source eNB; andwherein the sending unit (83) is adapted to send a random access response message on at least one component carrier in the at least two target component carriers after a dedicated random access preamble sent by the UE is received. - The target eNB according to claim 7, wherein the target eNB further comprises a module for allocating at least one of the following elements to the UE after receiving a handover acknowledgement message sent by the UE: a new uplink component carrier, a new downlink component carrier and a new component carrier pair.
- The target eNB according to claim 7 or 8, wherein the target eNB is required to re-allocate at least one of the following elements to which the UE is to be handed over for the UE: a new uplink component carrier, a new downlink component carrier and a new component carrier pair; the target eNB further comprising:a handover command sending unit (111), adapted to send a component carrier handover command to the UE, wherein the component carrier handover command comprises information about the at least one of the elements re-allocated; anda data transmission unit (112), adapted to transmit data on the at least one of the elements re-allocated after handover.
- The target eNB according to any one of claims 7 to 9, wherein the handover request acknowledgement message further comprises bandwidths of the at least two target component carriers configured by the target eNB; and
the handover command further comprises the bandwidths of the at least two target component carriers configured by the target eNB, or bandwidths of the at least two target component carriers selected by the source eNB. - The target eNB according to any one of claims 7 to 10, wherein the at least two target component carriers comprises at least one of a uplink target component carrier, a downlink target component carrier and a target component carrier pair selected for the UE; and
the information about the at least two target component carriers comprises: frequency information, an identifier, or a sequence number of the at least one of the uplink target component carrier, the downlink target component carrier and the target component carrier pair selected for the UE. - A system comprising a source eNB and a target eNB according to any one of claims 7 to 11.
- The system according to claim 12, wherein the source eNB is further adapted to send the handover command to the UE after the source eNB receives a handover acknowledgement message sent by the target eNB, wherein the handover command comprises: the information about the at least two target component carriers, which are selected by the source eNB or configured by the component carrier determination unit in the target eNB.
- A computer software product, comprising software codes used for performing the method according to any one of claims 1-6.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP19162440.2A EP3589017B1 (en) | 2009-04-09 | 2009-04-09 | Random access method, evolved node b, and terminal equipment |
EP17180767.0A EP3288310B1 (en) | 2009-04-09 | 2009-04-09 | Random access method in a handover involving carrier aggregation |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP09842865.9A EP2418907B1 (en) | 2009-04-09 | 2009-04-09 | Random access method in a handover in a lte system using carrier aggregation |
PCT/CN2009/071200 WO2010115304A1 (en) | 2009-04-09 | 2009-04-09 | A method for random accessing, evolution-node b and terminal equipment |
EP17180767.0A EP3288310B1 (en) | 2009-04-09 | 2009-04-09 | Random access method in a handover involving carrier aggregation |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP09842865.9A Division EP2418907B1 (en) | 2009-04-09 | 2009-04-09 | Random access method in a handover in a lte system using carrier aggregation |
EP09842865.9A Division-Into EP2418907B1 (en) | 2009-04-09 | 2009-04-09 | Random access method in a handover in a lte system using carrier aggregation |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP19162440.2A Division EP3589017B1 (en) | 2009-04-09 | 2009-04-09 | Random access method, evolved node b, and terminal equipment |
EP19162440.2A Division-Into EP3589017B1 (en) | 2009-04-09 | 2009-04-09 | Random access method, evolved node b, and terminal equipment |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3288310A1 EP3288310A1 (en) | 2018-02-28 |
EP3288310B1 true EP3288310B1 (en) | 2019-06-12 |
Family
ID=42935620
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP19162440.2A Active EP3589017B1 (en) | 2009-04-09 | 2009-04-09 | Random access method, evolved node b, and terminal equipment |
EP17180767.0A Active EP3288310B1 (en) | 2009-04-09 | 2009-04-09 | Random access method in a handover involving carrier aggregation |
EP09842865.9A Active EP2418907B1 (en) | 2009-04-09 | 2009-04-09 | Random access method in a handover in a lte system using carrier aggregation |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP19162440.2A Active EP3589017B1 (en) | 2009-04-09 | 2009-04-09 | Random access method, evolved node b, and terminal equipment |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP09842865.9A Active EP2418907B1 (en) | 2009-04-09 | 2009-04-09 | Random access method in a handover in a lte system using carrier aggregation |
Country Status (4)
Country | Link |
---|---|
US (5) | US8411642B2 (en) |
EP (3) | EP3589017B1 (en) |
CN (1) | CN102396280B (en) |
WO (1) | WO2010115304A1 (en) |
Families Citing this family (50)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8165090B2 (en) * | 2008-05-15 | 2012-04-24 | Nix John A | Efficient handover of media communications in heterogeneous IP networks |
CN101860929B (en) * | 2009-04-13 | 2013-06-12 | 中兴通讯股份有限公司 | Inter-base station switching method |
US9386593B2 (en) * | 2009-06-19 | 2016-07-05 | Sharp Kabushiki Kaisha | Systems and methods for component carrier selection in a wireless communication system |
US9014138B2 (en) * | 2009-08-07 | 2015-04-21 | Blackberry Limited | System and method for a virtual carrier for multi-carrier and coordinated multi-point network operation |
JP5446823B2 (en) * | 2009-12-16 | 2014-03-19 | ソニー株式会社 | Method for handover, terminal device, base station, and radio communication system |
EP2469916B1 (en) * | 2010-12-21 | 2015-10-28 | Innovative Sonic Corporation | Method and apparatus for Log reporting in a wireless communication system for minimisation of drive tests |
CN102612088B (en) * | 2011-01-18 | 2016-01-27 | 华为技术有限公司 | Based on the communication means of carrier convergence technology and system, base station in heterogeneous network |
US8395985B2 (en) | 2011-07-25 | 2013-03-12 | Ofinno Technologies, Llc | Time alignment in multicarrier OFDM network |
EP2747483A4 (en) * | 2011-08-19 | 2015-10-07 | Lg Electronics Inc | Method and apparatus for performing handover in wireless communication system |
US8526389B2 (en) | 2012-01-25 | 2013-09-03 | Ofinno Technologies, Llc | Power scaling in multicarrier wireless device |
US9237537B2 (en) | 2012-01-25 | 2016-01-12 | Ofinno Technologies, Llc | Random access process in a multicarrier base station and wireless device |
US8995405B2 (en) | 2012-01-25 | 2015-03-31 | Ofinno Technologies, Llc | Pathloss reference configuration in a wireless device and base station |
US20130259008A1 (en) | 2012-04-01 | 2013-10-03 | Esmael Hejazi Dinan | Random Access Response Process in a Wireless Communications |
US11943813B2 (en) | 2012-04-01 | 2024-03-26 | Comcast Cable Communications, Llc | Cell grouping for wireless communications |
EP2835023B1 (en) | 2012-04-01 | 2021-09-01 | Comcast Cable Communications, LLC | Cell group configuration in a wireless device and base station with timing advance groups |
US9210664B2 (en) | 2012-04-17 | 2015-12-08 | Ofinno Technologies. LLC | Preamble transmission in a wireless device |
US11825419B2 (en) | 2012-04-16 | 2023-11-21 | Comcast Cable Communications, Llc | Cell timing in a wireless device and base station |
US8971280B2 (en) | 2012-04-20 | 2015-03-03 | Ofinno Technologies, Llc | Uplink transmissions in a wireless device |
US11582704B2 (en) | 2012-04-16 | 2023-02-14 | Comcast Cable Communications, Llc | Signal transmission power adjustment in a wireless device |
US11252679B2 (en) | 2012-04-16 | 2022-02-15 | Comcast Cable Communications, Llc | Signal transmission power adjustment in a wireless device |
WO2013158511A1 (en) | 2012-04-16 | 2013-10-24 | Dinan Esmael Hejazi | Cell group configuration for uplink transmission in a multicarrier wireless device and base station with timing advance groups |
US8964593B2 (en) | 2012-04-16 | 2015-02-24 | Ofinno Technologies, Llc | Wireless device transmission power |
US9179425B2 (en) | 2012-04-17 | 2015-11-03 | Ofinno Technologies, Llc | Transmit power control in multicarrier communications |
US9674760B2 (en) * | 2012-04-27 | 2017-06-06 | Lg Electronics Inc. | Method and device for performing device-to-device communication in wireless communication system |
US11622372B2 (en) | 2012-06-18 | 2023-04-04 | Comcast Cable Communications, Llc | Communication device |
US9084228B2 (en) | 2012-06-20 | 2015-07-14 | Ofinno Technologies, Llc | Automobile communication device |
US8971298B2 (en) | 2012-06-18 | 2015-03-03 | Ofinno Technologies, Llc | Wireless device connection to an application server |
US9113387B2 (en) * | 2012-06-20 | 2015-08-18 | Ofinno Technologies, Llc | Handover signalling in wireless networks |
US11882560B2 (en) | 2012-06-18 | 2024-01-23 | Comcast Cable Communications, Llc | Carrier grouping in multicarrier wireless networks |
US9107206B2 (en) | 2012-06-18 | 2015-08-11 | Ofinne Technologies, LLC | Carrier grouping in multicarrier wireless networks |
US9210619B2 (en) | 2012-06-20 | 2015-12-08 | Ofinno Technologies, Llc | Signalling mechanisms for wireless device handover |
US9179457B2 (en) | 2012-06-20 | 2015-11-03 | Ofinno Technologies, Llc | Carrier configuration in wireless networks |
WO2014007697A1 (en) * | 2012-07-04 | 2014-01-09 | Telefonaktiebolaget L M Ericsson (Publ) | A radio network node, a user equipment and methods therein |
EP2882238B1 (en) * | 2012-07-31 | 2017-12-27 | Huawei Technologies Co., Ltd. | Method, apparatus, device, and network system for adding secondary cell |
EP2876932B1 (en) * | 2012-08-07 | 2019-02-20 | Huawei Technologies Co., Ltd. | Handover processing method and enb |
GB2506917B (en) | 2012-10-12 | 2015-06-03 | Samsung Electronics Co Ltd | Re-establishment of a connection with a mobile terminal |
EP3031268B1 (en) * | 2013-08-09 | 2023-10-04 | Telefonaktiebolaget LM Ericsson (publ) | Resource allocation for mobile terminal configured for dual connectivity |
US20170078933A1 (en) * | 2014-03-14 | 2017-03-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and Apparatus for a Handover using Dedicated Random Access Resource |
EP3180939A4 (en) * | 2014-08-14 | 2017-06-21 | Telefonaktiebolaget LM Ericsson (publ) | Methods and apparatuses for performing a handover in a high-speed traffic environment |
US20170303182A1 (en) * | 2015-02-20 | 2017-10-19 | Ntt Docomo, Inc. | User apparatus, and uplink transmission switching method |
US9986482B2 (en) * | 2015-11-18 | 2018-05-29 | Verizon Patent And Licensing Inc. | Managing carrier restrictions in a wireless network |
US10798627B2 (en) * | 2016-02-09 | 2020-10-06 | Qualcomm Incorporated | User equipment centric mobility (UECM) in radio resource control (RRC) dedicated mode |
KR20190025819A (en) * | 2016-07-01 | 2019-03-12 | 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 | Wireless communication method and apparatus |
EP3606163A1 (en) * | 2017-04-18 | 2020-02-05 | Huawei Technologies Co., Ltd. | Synchronization method, apparatus, and system for terminal monitoring information |
CN108810944B (en) * | 2017-05-04 | 2021-04-20 | 华为技术有限公司 | Method for switching uplink carrier, network equipment and terminal equipment |
US10893540B2 (en) * | 2017-07-28 | 2021-01-12 | Qualcomm Incorporated | Random access channel procedures with multiple carriers |
CN109561489B (en) * | 2017-09-26 | 2021-01-29 | 华为技术有限公司 | Method, device and equipment for arranging wide-width parts |
CN117715231A (en) * | 2017-10-30 | 2024-03-15 | 北京小米移动软件有限公司 | Random access method and device |
US10602418B2 (en) | 2018-06-11 | 2020-03-24 | Google Llc | Handover of a wireless connection based on uplink and downlink signal qualities |
US11018750B2 (en) | 2019-01-03 | 2021-05-25 | Qualcomm Incorporated | Recovery mechanism for secondary cell |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100640344B1 (en) * | 2003-03-08 | 2006-10-30 | 삼성전자주식회사 | System and method for handover of base station in a broadband wireless access communication system |
KR100651430B1 (en) * | 2003-11-07 | 2006-11-28 | 삼성전자주식회사 | System and method for handover in a communication system |
KR100827105B1 (en) * | 2004-02-13 | 2008-05-02 | 삼성전자주식회사 | Method and apparatus for ranging to support fast handover in broadband wireless communication system |
KR101100157B1 (en) * | 2004-06-08 | 2011-12-28 | 엘지전자 주식회사 | A Method for Handover between Frequency Allocation in Broadband Wireless Access System |
CN100441045C (en) | 2005-08-17 | 2008-12-03 | 鼎桥通信技术有限公司 | Method for selecting random access channel by user terminal in radio mobile communication system |
CN100428850C (en) | 2005-08-17 | 2008-10-22 | 鼎桥通信技术有限公司 | Method for adding random access channel in radio mobile communication system |
CN100563231C (en) * | 2006-03-09 | 2009-11-25 | 华为技术有限公司 | A kind of pilot code generation method of OFDM access system and device |
TWI530133B (en) | 2006-06-09 | 2016-04-11 | 進化無線責任有限公司 | Method and apparatus of transmitting data in a mobile communicaiton system |
WO2007149290A2 (en) | 2006-06-19 | 2007-12-27 | Interdigital Technology Corporation | Method and apparatus for performing random access in a wireless communication system |
ES2456690T3 (en) * | 2006-06-20 | 2014-04-23 | Interdigital Technology Corporation | Transfer in a wireless communication system |
CN101170812A (en) * | 2006-10-24 | 2008-04-30 | 中兴通讯股份有限公司 | A signal receiving method for base station receiver |
WO2008096407A1 (en) | 2007-02-05 | 2008-08-14 | Fujitsu Limited | Terminal, method for transmitting random access signal, and base station |
US9516580B2 (en) | 2007-03-19 | 2016-12-06 | Texas Instruments Incorporated | Enabling down link reception of system and control information from intra-frequency neighbors without gaps in the serving cell in evolved-UTRA systems |
US20080268850A1 (en) | 2007-04-30 | 2008-10-30 | Motorola, Inc. | Method and apparatus for handover in a wireless communication system |
CN101340707A (en) * | 2007-07-04 | 2009-01-07 | 鼎桥通信技术有限公司 | Random access method, network control unit, base station unit and user terminal |
CN101340714B (en) | 2007-07-05 | 2012-01-11 | 中兴通讯股份有限公司 | Stochastic access method of TD-SCDMA uplink enhancing system |
US8773968B2 (en) | 2007-08-06 | 2014-07-08 | Texas Instruments Incorporated | Signaling of random access preamble sequences in wireless networks |
KR101382748B1 (en) * | 2008-01-25 | 2014-04-08 | 엘지전자 주식회사 | Method for performing random access process in wireless communication system |
US8280375B2 (en) | 2008-01-25 | 2012-10-02 | Texas Instruments Incorporated | System and method for managing radio link failures |
CN104244345A (en) * | 2008-06-30 | 2014-12-24 | 交互数字专利控股公司 | Method of executing switching from source cell to target cell, and WTRU |
TWI442794B (en) * | 2009-03-12 | 2014-06-21 | Interdigital Patent Holdings | Method and apparatus for performing component carrier-specific reconfiguration |
CN102246573B (en) | 2009-03-30 | 2014-07-30 | 华为技术有限公司 | Random access method, enodeb and terminal equipment |
-
2009
- 2009-04-09 EP EP19162440.2A patent/EP3589017B1/en active Active
- 2009-04-09 EP EP17180767.0A patent/EP3288310B1/en active Active
- 2009-04-09 EP EP09842865.9A patent/EP2418907B1/en active Active
- 2009-04-09 WO PCT/CN2009/071200 patent/WO2010115304A1/en active Application Filing
- 2009-04-09 CN CN2009801173202A patent/CN102396280B/en active Active
-
2011
- 2011-10-05 US US13/253,709 patent/US8411642B2/en active Active
-
2012
- 2012-03-21 US US13/426,263 patent/US8488560B2/en active Active
-
2013
- 2013-06-18 US US13/920,668 patent/US8908646B2/en active Active
-
2014
- 2014-11-20 US US14/549,387 patent/US9036606B2/en active Active
-
2015
- 2015-04-07 US US14/680,888 patent/US9554310B2/en active Active
Non-Patent Citations (1)
Title |
---|
None * |
Also Published As
Publication number | Publication date |
---|---|
EP3288310A1 (en) | 2018-02-28 |
US20120177009A1 (en) | 2012-07-12 |
US9036606B2 (en) | 2015-05-19 |
US20130294408A1 (en) | 2013-11-07 |
US9554310B2 (en) | 2017-01-24 |
EP3589017A1 (en) | 2020-01-01 |
US8411642B2 (en) | 2013-04-02 |
CN102396280A (en) | 2012-03-28 |
CN102396280B (en) | 2013-04-17 |
EP3589017B1 (en) | 2021-08-18 |
US20120026976A1 (en) | 2012-02-02 |
US20150078338A1 (en) | 2015-03-19 |
US8908646B2 (en) | 2014-12-09 |
EP2418907B1 (en) | 2017-09-06 |
US20150215829A1 (en) | 2015-07-30 |
US8488560B2 (en) | 2013-07-16 |
WO2010115304A1 (en) | 2010-10-14 |
EP2418907A4 (en) | 2012-03-28 |
EP2418907A1 (en) | 2012-02-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3288310B1 (en) | Random access method in a handover involving carrier aggregation | |
CN105940753B (en) | Random access method and apparatus in mobile communication system | |
EP2468039B1 (en) | Communications system | |
US20190394819A1 (en) | Communication control method, user terminal, processor, and base station | |
EP2884798B1 (en) | Method, system and device for cell management | |
EP3614615A2 (en) | Method and apparatus for transmitting and receiving data using plurality of carriers in wireless communication system | |
JP6416424B2 (en) | Base station, processor, and communication method | |
US9706578B2 (en) | Scheduling signaling transmission method and device | |
US20150319798A1 (en) | Communication control method, user terminal, processor, and storage medium | |
JP6101486B2 (en) | Buffer status report transmission control method, user apparatus, and radio communication system | |
US20150237616A1 (en) | Communication control method, base station, user terminal, processor, and storage medium | |
KR102301836B1 (en) | Method and apparatus for controlling SCell in a mobile communication system | |
US9713159B2 (en) | Communication control method and base station | |
WO2014101671A1 (en) | Data transmission method, system and device | |
WO2011050564A1 (en) | Method, system and device for transmitting system information |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED |
|
AC | Divisional application: reference to earlier application |
Ref document number: 2418907 Country of ref document: EP Kind code of ref document: P |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK TR |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20180828 |
|
RBV | Designated contracting states (corrected) |
Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK TR |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 72/00 20090101ALI20180913BHEP Ipc: H04W 36/00 20090101AFI20180913BHEP Ipc: H04L 5/00 20060101ALN20180913BHEP Ipc: H04W 72/04 20090101ALI20180913BHEP Ipc: H04W 88/08 20090101ALI20180913BHEP Ipc: H04W 48/08 20090101ALI20180913BHEP Ipc: H04W 36/06 20090101ALI20180913BHEP Ipc: H04W 74/08 20090101ALI20180913BHEP |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 48/08 20090101ALI20180920BHEP Ipc: H04W 72/04 20090101ALI20180920BHEP Ipc: H04W 88/08 20090101ALI20180920BHEP Ipc: H04L 5/00 20060101ALN20180920BHEP Ipc: H04W 74/08 20090101ALI20180920BHEP Ipc: H04W 72/00 20090101ALI20180920BHEP Ipc: H04W 36/00 20090101AFI20180920BHEP Ipc: H04W 36/06 20090101ALI20180920BHEP |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
INTG | Intention to grant announced |
Effective date: 20181107 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 48/08 20090101ALI20181023BHEP Ipc: H04W 72/04 20090101ALI20181023BHEP Ipc: H04L 5/00 20060101ALN20181023BHEP Ipc: H04W 36/06 20090101ALI20181023BHEP Ipc: H04W 88/08 20090101ALI20181023BHEP Ipc: H04W 36/00 20090101AFI20181023BHEP Ipc: H04W 72/00 20090101ALI20181023BHEP Ipc: H04W 74/08 20090101ALI20181023BHEP |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AC | Divisional application: reference to earlier application |
Ref document number: 2418907 Country of ref document: EP Kind code of ref document: P |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1144190 Country of ref document: AT Kind code of ref document: T Effective date: 20190615 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602009058761 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20190612 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190912 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190912 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190913 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1144190 Country of ref document: AT Kind code of ref document: T Effective date: 20190612 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191014 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191012 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602009058761 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 |
|
26N | No opposition filed |
Effective date: 20200313 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200224 Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 |
|
PG2D | Information on lapse in contracting state deleted |
Ref country code: IS |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 602009058761 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20200409 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20200430 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20200430 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20200430 Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20201103 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20200430 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20200430 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20200409 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20190612 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230524 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20240229 Year of fee payment: 16 |