KR20140145524A - Methods and apparatus for dual connectivity configuration - Google Patents
Methods and apparatus for dual connectivity configuration Download PDFInfo
- Publication number
- KR20140145524A KR20140145524A KR1020130130408A KR20130130408A KR20140145524A KR 20140145524 A KR20140145524 A KR 20140145524A KR 1020130130408 A KR1020130130408 A KR 1020130130408A KR 20130130408 A KR20130130408 A KR 20130130408A KR 20140145524 A KR20140145524 A KR 20140145524A
- Authority
- KR
- South Korea
- Prior art keywords
- senb
- radio resource
- resource configuration
- message
- menb
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 58
- 230000009977 dual effect Effects 0.000 title description 7
- 238000004891 communication Methods 0.000 claims abstract description 20
- 238000012545 processing Methods 0.000 claims abstract description 9
- 230000008569 process Effects 0.000 claims description 18
- 230000005540 biological transmission Effects 0.000 description 34
- 238000010586 diagram Methods 0.000 description 16
- 238000012790 confirmation Methods 0.000 description 10
- 230000011664 signaling Effects 0.000 description 10
- 238000005516 engineering process Methods 0.000 description 8
- 238000002360 preparation method Methods 0.000 description 7
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 238000012937 correction Methods 0.000 description 4
- 238000005259 measurement Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 3
- 238000000926 separation method Methods 0.000 description 3
- 230000004913 activation Effects 0.000 description 2
- 239000000470 constituent Substances 0.000 description 2
- 208000000649 small cell carcinoma Diseases 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 101000744882 Homo sapiens Zinc finger protein 185 Proteins 0.000 description 1
- 108091005487 SCARB1 Proteins 0.000 description 1
- 102100037118 Scavenger receptor class B member 1 Human genes 0.000 description 1
- 102100040032 Zinc finger protein 185 Human genes 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000023402 cell communication Effects 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 230000001747 exhibiting effect Effects 0.000 description 1
- 238000004880 explosion Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
The present invention relates to a method and apparatus for handling when a terminal fails in an instruction to use radio resources provided by at least two different network points (Master eNB and Secondary eNBs).
A method for processing a wireless link in a wireless terminal, comprising the steps of: adding a secondary base station for additional radio resources; detecting a radio link failure in an additional process of a secondary base station; And restarting the communication.
1 is a diagram showing a network configuration scenario example 1 for the present invention.
2 is a diagram showing a network configuration scenario example 2 for the present invention.
3 is a diagram showing a network configuration scenario example 3 for the present invention.
4 is a diagram illustrating an example of additional radio resource configuration scenario according to the present invention.
Figure 5 is a diagram illustrating an example of a further radio configuration bearer-separated.
FIG. 6 is a diagram illustrating an example of a further radio configuration that is not bearer detached.
7 is a diagram illustrating a configuration of a base station according to another embodiment of the present invention.
FIG. 8 is a diagram illustrating a configuration of a user terminal according to another embodiment of the present invention.
Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference symbols as possible even if they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.
The wireless communication system in the present invention is widely deployed to provide various communication services such as voice, packet data and the like. A wireless communication system includes a user equipment (UE) and a base station (BS, or eNB). The user terminal in this specification is a comprehensive concept of a terminal in wireless communication. It is a comprehensive concept which means a mobile station (MS), a user terminal (UT), an SS (User Equipment) (Subscriber Station), a wireless device, and the like.
A base station or a cell generally refers to a station that communicates with a user terminal and includes a Node-B, an evolved Node-B (eNB), a sector, a Site, a BTS A base transceiver system, an access point, a relay node, a remote radio head (RRH), a radio unit (RU), and a small cell.
That is, the base station or the cell in this specification is interpreted as a comprehensive meaning indicating a partial region or function covered by BSC (Base Station Controller) in CDMA, NodeB in WCDMA, eNB in LTE or sector (site) And covers various coverage areas such as megacell, macrocell, microcell, picocell, femtocell and relay node, RRH, RU, and small cell communication range.
Since the various cells listed above exist in the base station controlling each cell, the base station can be interpreted into two meanings. i) a device itself providing a megacell, a macrocell, a microcell, a picocell, a femtocell, or a small cell in relation to a wireless region, or ii) the wireless region itself. i indicate to the base station all devices that are controlled by the same entity or that interact to configure the wireless region as a collaboration. An eNB, an RRH, an antenna, an RU, an LPN, a point, a transmission / reception point, a transmission point, a reception point, and the like are exemplary embodiments of a base station according to a configuration method of a radio area. ii) may indicate to the base station the wireless region itself that is to receive or transmit signals from the perspective of the user terminal or from a neighboring base station.
Therefore, a base station is collectively referred to as a megacell, a macrocell, a microcell, a picocell, a femtocell, a small cell, an RRH, an antenna, an RU, a low power node (LPN), a point, an eNB, Quot;
Herein, the user terminal and the base station are used in a broad sense as the two transmitting and receiving subjects used to implement the technical or technical idea described in this specification, and are not limited by a specific term or word. The user terminal and the base station are used in a broad sense as two (uplink or downlink) transmitting and receiving subjects used to implement the technology or technical idea described in the present invention, and are not limited by a specific term or word. Here, an uplink (UL, or uplink) means a method of transmitting / receiving data to / from a base station by a user terminal, and a downlink (DL or downlink) .
There are no restrictions on multiple access schemes applied to wireless communication systems. Various multiple access schemes such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), OFDM-FDMA, OFDM- Can be used. An embodiment of the present invention can be applied to asynchronous wireless communication that evolves into LTE and LTE-Advanced via GSM, WCDMA, and HSPA, and synchronous wireless communication that evolves into CDMA, CDMA-2000, and UMB. The present invention should not be construed as limited to or limited to a specific wireless communication field and should be construed as including all technical fields to which the idea of the present invention can be applied.
A TDD (Time Division Duplex) scheme in which uplink and downlink transmissions are transmitted using different time periods, or an FDD (Frequency Division Duplex) scheme in which they are transmitted using different frequencies can be used.
In systems such as LTE and LTE-Advanced, the uplink and downlink are configured on the basis of one carrier or carrier pair to form a standard. The uplink and the downlink are divided into a Physical Downlink Control Channel (PDCCH), a Physical Control Format Indicator CHannel (PCFICH), a Physical Hybrid ARQ Indicator CHannel, a Physical Uplink Control CHannel (PUCCH), an Enhanced Physical Downlink Control Channel (EPDCCH) Transmits control information through the same control channel, and is configured with data channels such as PDSCH (Physical Downlink Shared CHannel) and PUSCH (Physical Uplink Shared CHannel), and transmits data.
On the other hand, control information can also be transmitted using EPDCCH (enhanced PDCCH or extended PDCCH).
In this specification, a cell refers to a component carrier having a coverage of a signal transmitted from a transmission point or a transmission point or transmission / reception point of a signal transmitted from a transmission / reception point, and a transmission / reception point itself .
The wireless communication system to which the embodiments are applied may be a coordinated multi-point transmission / reception system (CoMP system) or a coordinated multi-point transmission / reception system in which two or more transmission / reception points cooperatively transmit signals. antenna transmission system, or a cooperative multi-cell communication system. A CoMP system may include at least two multipoint transmission / reception points and terminals.
The multi-point transmission / reception point includes a base station or a macro cell (hereinafter referred to as 'eNB'), and at least one mobile station having a high transmission power or a low transmission power in a macro cell area, Lt; / RTI >
Hereinafter, a downlink refers to a communication or communication path from a multiplex transmission / reception point to a terminal, and an uplink refers to a communication or communication path from a terminal to a multiplex transmission / reception point. In the downlink, a transmitter may be a part of a multipoint transmission / reception point, and a receiver may be a part of a terminal. In the uplink, the transmitter may be a part of the terminal, and the receiver may be a part of multiple transmission / reception points.
Hereinafter, a situation in which a signal is transmitted / received through a channel such as PUCCH, PUSCH, PDCCH, EPDCCH, and PDSCH is expressed as 'PUCCH, PUSCH, PDCCH, EPDCCH and PDSCH are transmitted and received'.
In the following description, an indication that a PDCCH is transmitted or received or a signal is transmitted or received via a PDCCH may be used to mean transmitting or receiving an EPDCCH or transmitting or receiving a signal through an EPDCCH.
That is, the physical downlink control channel described below may mean a PDCCH, an EPDCCH, or a PDCCH and an EPDCCH.
Also, for convenience of description, EPDCCH, which is an embodiment of the present invention, may be applied to the portion described with PDCCH, and EPDCCH may be applied to the portion described with EPDCCH according to an embodiment of the present invention.
Meanwhile, the High Layer Signaling described below includes RRC signaling for transmitting RRC information including RRC parameters.
The eNB performs downlink transmission to the UEs. The eNB includes a physical downlink shared channel (PDSCH) as a main physical channel for unicast transmission, downlink control information such as scheduling required for reception of a PDSCH, A physical downlink control channel (PDCCH) for transmitting scheduling grant information for transmission in a Physical Uplink Shared Channel (PUSCH). Hereinafter, the transmission / reception of a signal through each channel will be described in a form in which the corresponding channel is transmitted / received.
Small cells using low power nodes are being considered as a means to cope with mobile traffic explosion. A low power node represents a node using lower transmit (Tx) power than a typical macro node.
Prior to 3GPP Release 11, carrier aggregation (CA) technology was able to build a small cell using a low power RRH (Remote Radio Head), which is a geographically dispersed antenna within macro cell coverage.
However, in order to apply the CA technology, the macro cell and the RRH cell must be configured to be scheduled under the control of one eNB, and an ideal backhaul between the macro cell node and the RRH is required. An ideal backhaul is a backhaul that has very high throughput and very little delay, such as a dedicated point-to-point connection using optical fiber, LOS (line of sight) microware. In contrast, a backhaul exhibiting relatively low throughput and large delay, such as Digital Subscriber Line (xDSL) and Non-LOS microwave, is called a non-ideal backhaul.
Through the single eNB-based CA technology described above, a plurality of serving cells could be merged to service a UE (User Equipment). That is, a plurality of serving cells can be configured for a UE in the RRC (Radio Resource Control) CONNECTED state. When an ideal backhaul is established between the macro cell node and the RRH, the macro cell and the RRH cell together constitute serving cells, Could.
When the above-described single eNB-based CA technology is configured, the UE may have only one RRC connection with the network. One serving cell provides NAS mobility information (eg TAI: Tracking Area Identity) in RRC connection establishment / re-establishment / handover, and one serving cell in the RRC connection reset / It provides a security input. These cells are called PCell (Primary Cell). PCell can only be changed with the handover procedure.
Depending on the UE capabilities, SCells (Secondary Cells) can be configured with the serving cell as the PCells. In a single eNB-based CA technology, the SCell is only served as an additional radio resource on the physical layer. PCell can use the CQI and measurement result to detect the radio link problem in the SCell, and if there is a radio link problem in the SCell, , The RLM (Radio Link Monitoring) UE procedure was not applied to SCell. In the single eNB-based CA, a plurality of carrier attributes of the physical layer affect only the MAC layer, and the MAC layer performs one independent Hybrid Automatic Retransmission request (HARQ) for each serving cell in the uplink and downlink, It has an object. Each HARQ entity processes a data stream of a component carrier (CC).
The addition and removal of SCells in the single eNB-based CA are performed by an RRC Connection Reconfiguration message. When adding a new SCell, dedicated RRC signaling is used to send all the necessary system information of the SCell. That is, in the connected mode, the UE does not need to directly acquire the broadcasted system information. If the RRC Connection Reconfiguration message received from the PCell includes a SCell additional modification list (sCellToAddModList), the UE performs addition or modification of the SCell. That is, SCell corresponding to the cell identifier (cellIdentification) is added to each SCell index (sCellIndex) included in the SCell additional modification list (sCellToAddModList) which is not part of the current UE configuration. And configure the SCell to be deactivated in the lower layer. Modify the SCell configuration for each SCell index (sCellIndex) contained in the SCell additional modification list (sCellToAddModList) which is part of the current UE configuration.
To use SCell's carrier, the added SCell must be activated. That is, SCell's carrier can be used through the SCell addition step and the separate activation step. Therefore, while the terminal is configuring the SCell addition, the SCell addition failure does not occur due to the failure of the SCell radio link. That is, a radio resource configuration for using radio resources provided by at least two different network points in a conventional single eNB-based CA technology is performed through an RRC message including SCell addition information in the PCell and a separate activation SCell radio link failure in the process of SCell radio resource configuration was not required to be considered because it uses the radio resources configured in the step
Dual Connectivity
Dual connectivity represents an operation using radio resources provided by at least two different network points (Master eNB and Secondary eNBs) connected in a non-ideal backhaul at RRC_CONNECTED. In dual connectivity, the Master eNB represents an eNB that terminates the S1-MME and acts as a mobility anchor towards the Core Network (CN). The Master eNB may be referred to as MeNB or Macro eNB or Primary eNB or PCell eNB or Anchor eNB or Macrocell eNB. In dual connectivity, the secondary eNB is an eNB that provides additional radio resources for the UE and represents an eNB other than the master eNB. The Secondary eNB may be referred to as SeNB or Small Cell eNB or Small eNB or SCell eNB or Assisting eNB.
In order to use radio resources provided by at least two different network points connected by a non-ideal backhaul, a procedure for configuring them is needed. Currently, dual connectivity is conceptually focused on 3GPP's Release 12 work item, and the configuration procedure is not materialized.
In the prior art, different eNBs could not be configured to use the radio resources provided by different network points if they were connected in a non-ideal backhaul. In particular, the existing single eNB-based CA technology does not need to consider the SCELL radio link failure in the SCell configuration process and is provided by a non-ideal backhaul-connected Secondary eNB (or SeNB or Small cell eNB or Small eNB or SCell eNB or Assisting eNB) There is a problem that a failure or an exceptional situation can not be handled in a secondary eNB (or SeNB or Small cell eNB, Small eNB, SCell eNB, or Assisting eNB) wireless link in the process of constructing additional radio resources that can be used.
In order to solve the above problems, the present invention provides a specific configuration procedure for using radio resources provided by one or more different network points connected through a non-ideal backhaul. Which may be provided by a secondary eNB (or SeNB or Small cell eNB or Small eNB or SCell eNB or Assisting eNB) in order to use radio resources provided by one or more different eNBs connected in particular via non-ideal backhaul And to provide a method of processing a radio link failure or the like in the process of configuring resources when the radio link failure occurs.
Figures 1, 2 and 3 show network configuration scenarios for the present invention.
1 is a diagram showing a network configuration scenario example 1 for the present invention.
As shown in FIG. 1, macrocells and small cells have the same carrier frequency F1 and are connected through a non-ideal backhaul between a macro cell node (eNB) and a small cell node (eNB). Small cells are built into an overlaid macro network. An outdoor small cell environment and a small cell cluster can be considered.
2 is a diagram showing a network configuration scenario example 2 for the present invention.
As shown in FIG. 2, macrocells and small cells have different carrier frequencies F1 and F2, and non-ideal backhaul between a macro cell node (eNB) and a small cell node (eNB) Lt; / RTI > Small cells are built into an overlaid macro network. An outdoor small cell environment or an indoor small cell environment and a small cell cluster are considered.
3 is a diagram showing a network configuration scenario example 3 for the present invention.
Only small cells with only one or more carrier frequencies are present, as shown in FIG. 3, and are connected via non-ideal backhaul between small cell nodes (eNBs). Indoor small cell environments and small cell clusters are considered.
In one example of the present invention, in the scenarios of FIGS. 1 and 2, a UE may communicate with one or more small cell eNBs under the control of a macrocell eNB, or through collaboration between macrocell eNBs and one or more small cell eNBs, 3, it is possible to transmit user plane data through collaboration between small cell eNBs. That is, for control plane data transmission, the UE sets up one RRC connection with the macro cell eNB, and can configure one or more DRBs (Data Radio Bearers) with the macro cell eNB and the small cell eNB. For this, UEs that have set up macrocell eNB and RRC connection can configure additional radio resources in small-cell eNB connected with non-ideal backhaul.
As another example of the present invention, in the scenario of FIG. 1 and FIG. 2, under the control of the macrocell eNB, through collaboration between the macrocell eNB and one or more small cell eNBs, or cooperation between small cell eNBs in the scenario of FIG. The user plane data can be transmitted only by the macro cell eNB or the user plane data can be transmitted by only the small cell eNB. That is, for control plane data transmission, the UE establishes one RRC connection with the macrocell eNB, and can configure one or more DRBs only through the macrocell eNB. And / or one or more DRBs through only the small cell eNB.
4 is a diagram illustrating an example of additional radio resource configuration scenario according to the present invention.
Additional radio resource configuration procedures
FIG. 4 shows an example of a procedure for constructing a macro cell eNB and an RRC connection with a small-cell eNB connected with a non-ideal backhaul and an additional radio resource. 4 will be described in detail below.
1) The MeNB constitutes a UE measurement procedure.
2) The UE is triggered to send a MEASUREMENT REPORT by rule set.
3) MeNB determines offloading based on MEASUREMENT REPORT and Radio Resource Management (RRM) information. For example, it is determined to transmit user plane data (or a specific DRB (s)) via the macro cell eNB via the macro cell eNB and the small cell eNB (using the radio resources of the macro cell eNB and the small cell eNB) It is determined to transmit user plane data (or a specific DRB (s)) (using the radio resources of the macro cell eNB) via the macro cell eNB through the small cell eNB (using the radio resources of the small cell eNB).
4) MeNB sends a message (offload request message) to SeNB to prepare additional radio resource configuration. A message (an offload request message) for preparing the above-described additional radio resource configuration includes information (e.g., AS-configuration, E-RAB context) necessary for preparing an additional radio resource configuration in the SeNB.
When the MeNB sends a message (an offload request message) to prepare the additional radio resource configuration in SeNB, the MeNB starts an additional radio resource configuration ready timer. The additional radio resource configuration ready timer indicates a timer for specifying / limiting the maximum time for processing a message (an offload request message) procedure for preparation of additional radio resource configuration. If the MeNB does not receive a message (an offload request ACK message) for confirmation of the message to prepare the additional radio resource configuration before the above-described additional radio resource configuration ready timer expires, the MeNB sends an additional radio resource configuration preparation in progress to the SeNB (An offload cancellation message) for canceling the message.
5) Admission control can be performed by SeNB. Alternatively, the SeNB may not perform admission control for the E-RAB (s) that has determined off-loading based on the E-RAB QoS profile in MeNB.
6) SeNB prepares the L1 / L2 additional radio resource configuration [sets or prepares the L1 / L2 entity for the accepted E-RAB (s) or E-RAB (s) requested for offloading]. SeNB sends a message (an offload request ACK message) to the MeNB for confirmation of the additional radio resource configuration. A message (an offload request ACK message) for confirming the above-described additional radio resource configuration may include information necessary for the UE to generate an RRC message in the MeNB to configure additional radio resources of the SeNB. Alternatively, a message for confirming the above-described additional radio resource configuration (an offload request ACK message) may include an RRC message for configuring an additional radio resource of the SeNB by the RRC layer of the SeNB. A message (an offload request ACK message) for confirmation of the above-described additional radio resource configuration may include a dedicated RACH preamble and other necessary parameters (i.e., SIBs, etc.) if necessary.
SeNB may send a message (an offload request ACK message) for confirmation of the additional radio resource configuration to the MeNB, and then start an additional radio resource configuration timer of the SeNB. The additional radio resource configuration timer of the SeNB indicates a timer for specifying / limiting the maximum time for processing additional radio resource configuration procedures in the SeNB. The additional radio resource configuration timer of SeNB may be stopped when the additional radio resource configuration of SeNB is completed successfully. If the SeNB does not successfully complete additional radio resources in the SeNB before the additional radio resource configuration timer of the SeNB expires, the SeNB can cancel the ongoing additional radio resource configuration preparation. For this, when the MeNB receives a success message (eg RRC Connection Reconfiguration Complete) for the additional radio resource configuration of the SeNB from the UE, the MeNB sends a success message for the additional radio resource configuration to the SeNB, Upon receiving a success message (eg RRC Connection Reconfiguration Complete) for the additional radio resource configuration or receiving a failure message (eg RRC Connection reestablish request), the MeNB sends a failure message (or cancel message) . As another method, the SeNB does not separately configure an additional radio resource configuration timer of the SeNB, but uses the additional radio resource configuration timer of MeNB described below so that the MeNB adds additional radio resource configuration timers before expiration of the additional radio resource configuration timer of MeNB If a confirmation message (eg RRC Connection Reconfiguration Complete) for the resource configuration is not received, the MeNB may send a message (an offload cancel message) to cancel preparation for further radio resource configuration in progress to SeNB.
If the RRC layer of the SeNB generates and includes an RRC message for configuring the additional radio resources of the SeNB with the UE, the SeNB may generate an RRC entity for the UE (additional support). Alternatively, if an RRC message is generated by the RRC layer of the SeNB to configure additional radio resources of the SeNB by the UE, the SeNB may not generate an RRC entity for the UE, (Or RRC Connection Reconfiguration Complete) for the additional radio resource configuration of the SeNB from the UE after generating the RRC entity when generating the RRC message (or additional radio resource configuration information) If the MeNB receives a success message for the SeNB additional radio resource configuration from the MeNB, or the MeNB fails to receive a success message (e.g., RRC Connection Reconfiguration Complete) for SeNB's additional radio resource configuration from the UE, When you receive a message (or a cancellation message), you can remove it.
The MeNB, which has received a message (an offload request ACK message) for confirmation of the additional radio resource configuration from the SeNB, stops the above-described additional radio resource configuration ready timer. And MeNB starts the additional radio resource configuration timer of MeNB. Alternatively, the additional radio resource configuration timer of the MeNB may be started after the MeNB transmits an RRC Connection Reconfiguration message to the UE. The additional radio resource configuration timer of the MeNB indicates a timer that specifies / limits the maximum time for processing additional radio resource configuration procedures (e.g., RRC connection reconfiguration) in the MeNB.
If the MeNB does not successfully complete the additional radio resource configuration procedure before the expiration of the additional radio resource configuration timer of MeNB (eg, receiving a success message (eg, RRC Connection Reconfiguration Complete) from the terminal to the SeNB for additional radio resource configuration, (Eg RRC Connection Reconfiguration or forwarding a new signaling message between the MeNB and the SeNB), the MeNB transmits a success message (eg, RRC Connection Reconfiguration) to the SeNB by receiving a success message (eg, RRC Connection Reconfiguration Complete) It is possible to send a message (an offload cancel message) for canceling the preparation of the additional radio resource configuration, and resume the radio resource configuration through the old MeNB to service the UE.
If the SeNB does not accept at least one E-RAB, or if a failure occurs during the processing of the message (Offload Request message) to prepare the additional radio resource configuration, the SeNB sends an additional radio resource configuration readiness failure message Message) to MeNB. The message may include cause information (Cause IE) with an appropriate value.
If the MeNB does not receive a response (an offload request ACK message) for preparing an additional radio resource configuration (Offload Request message) until the above-described additional radio resource configuration ready timer expires in the MeNB, To send a message (an offload cancel message) with an appropriate value for the cause information (Cause IE) to cancel the preparation of the additional radio resource configuration in progress. If there is no response to the message (offload request message) for preparing the additional radio resource configuration until the above-described additional radio resource configuration ready timer expires, the MeNB transmits a message for preparing an additional radio resource configuration Message) procedure can be canceled.
If a radio bearer for additional radio resource configuration is configured not to be bearer split, i.e. a radio bearer configured to use MeNB (to use MeNB radio resources) via SeNB (to use SeNB radio resources) , The MeNB receives an RRC Connection Reconfiguration Complete message after receiving a message (Offload Request ACK message) for confirmation of the additional radio resource configuration from the SeNB or after the MeNB sends an RRC Connection Reconfiguration message to the UE Packets can be buffered until. Alternatively, if the radio bearer for additional radio resource configuration is configured not to be bearer split, that is, if a radio bearer configured to use MeNB (using MeNB radio resources) is transmitted through SeNB When the MeNB sends a RRC Connection Reconfiguration message to the UE after receiving a message for confirmation of the additional radio resource configuration from the SeNB (Offload Request ACK message), the MeNB performs RRC Connection Reconfiguration Complete The data transfer can continue through the MeNB until the message is received.
If a radio bearer for additional radio resource configuration is configured to be bearer split, that is, a radio bearer configured to use MeNB (using MeNB radio resources) is transmitted between MeNB and SeNB (MeNB radio resource and SeNB radio resource The MeNB sends an RRC Connection Reconfiguration message to the UE before receiving a message for confirmation of the additional radio resource configuration (Offload Request ACK message) from the SeNB, or after the MeNB sends the RRC Connection Reconfiguration message to the UE, You can continue to send data through MeNB until you receive a Connection Reconfiguration Complete message. Alternatively, if a radio bearer for additional radio resource configuration is configured to be bearer split, that is, a radio bearer configured to use MeNB (using MeNB radio resources), via MeNB and SeNB (MeNB radio resource And SeNB radio resources), before the SeNB receives a message (an offload request ACK message) for confirmation of the additional radio resource configuration, or when the MeNB sends an RRC Connection Reconfiguration message to the UE The MeNB can buffer the packet until it receives the RRC Connection Reconfiguration Complete message.
7) The MeNB sends an RRC Connection Reconfiguration message to the UE. The RRC Connection Reconfiguration message may include information for indicating to the SeNB that the message is for additional radio resource configuration.
Information for additional radio resource configuration in the SeNB will be separately described below.
8) When the UE receives an RRC Connection Reconfiguration message including information for additional radio resource configuration in the SeNB, the UE may start a timer for limiting the additional radio resource configuration time of the UE. The timer for limiting the additional radio resource configuration time of the UE may be a timer (e.g., T304 timer or ARRC timer) included in information for additional radio resource configuration in the SeNB included in the RRC Connection Reconfiguration message. Alternatively, the timer value may be a pre-configured value for the UE.
The UE may determine that the additional radio resource configuration has been successfully completed (e.g., the RRC Connection Reconfiguration Complete message has been sent, or that the MAC has successfully synchronized uplink synchronization, or has been successfully randomized) before the timer for limiting the UE ' The access process is completed (SeNB requests random access and receives a random access response via SeNB)), the timer for stopping the additional radio resource configuration time of the UE can be stopped. If the timer for limiting the additional radio resource configuration time of the UE expires before the additional radio resource configuration is successfully completed, the UE transmits the radio resource configuration (configuration before receiving the RRC Connection Reconfiguration message) originally used in the MeNB, . ≪ / RTI > Then, additional radio resource configuration failure information may be stored in a new information element for reporting a VarRLF-Report or SeNB additional radio resource configuration failure, or an indication of a SeNB additional radio resource configuration failure may be sent to MeNB. The additional radio resource configuration failure information or SeNB additional radio resource configuration failure indication included in the new information element for the VarRLF-Report or SeNB additional radio resource configuration failure report will be separately described below.
Figure 5 is a diagram illustrating an example of a further radio configuration bearer-separated.
The UE may synchronize with the SeNB if necessary and access the SeNB via the RACH.
The UE performs synchronization with the SeNB and performs synchronization with the SeNB before accessing the SeNB via the RACH, accessing the SeNB via the RACH, or performing synchronization with the SeNB with the SeNB And after accessing the SeNB over the RACH, the UE may configure additional radio resources via the SeNB. For example, when a radio bearer previously configured through MeNB is separated and transmitted through SeNB as shown in FIG. 5, each DRB identifier included in radio bearer addition correction information (drb-ToAddMod) rlc-config (eg rlc-config of the terminal RLC entity peered to the MeNB RLC entity, rlc-config of the terminal RLC entity peered to the SeNB RLC entity) is included in the received rlc-config RLC entities or entities (e.g., MeNB peered UE RLC entity, SeNB peered UE RLC entity) are reconfigured according to FIG. For example, the UE RLC entity to be peered to the MeNB RLC entity is reset, and the UE RLC entity to be peered is configured with the rlc-config of the UE RLC entity to be peered to the received SeNB RLC entity. If the logicalChannelConfig is included, the logical channel is reconfigured according to the received logicalChannelConfig. The above rlc-config and / or logicalChannelConfig may contain new information for additional bearer-separated radio configurations.
FIG. 6 is a diagram illustrating an example of a further radio configuration that is not bearer detached.
As another example, when a radio bearer previously configured through MeNB is to be transmitted through the SeNB without bearer separation as shown in FIG. 6, each DRB identifier included in the radio bearer addition correction information (drb-ToAddMod) (rlc-config of the UE RLC entity to be peered to the SeNB RLC entity) is included in the rlc-config, the RLC entity or entities are reconfigured according to the received rlc-config. For example, the terminal RLC entity that is MeNB peered is reset with the rlc-config of the terminal RLC entity that is peered to the received SeNB RLC entity. If the logicalChannelConfig is included, the logical channel is reconfigured according to the received logicalChannelConfig. The logicalChannelConfig may include new information for bearer-separated additional radio configurations.
Alternatively, the UE can modify the radio resources to the UE according to the radio bearer addition correction information (drb-ToAddMod) received through the RRC Connection Reconfiguration message only when the UE can successfully access the SeNB.
If the UE successfully accesses the SeNB, the UE sends an RRC Connection Reconfiguration Complete message to the MeNB (and / or SeNB). The manner in which the UE sends an RRC Connection Reconfiguration Complete message to the MeNB is described separately below.
Upon receiving the RRC Connection Reconfiguration Complete message, the MeNB sends a success message for additional radio resource configuration to the SeNB and starts to send data to the UE via SeNB.
About Displaying Additional Radio Resource Configurations
In step 7, information for indicating that the SeNB is a message for additional radio resource configuration may be configured in the following manner.
Method 1 : MobilityControlInfo Contains fields for displaying additional radio resource configurations
The RRC Connection Reconfiguration message (generated by MeNB or RRC message generated by SeNB and forwarded by MeNB) sent by the MeNB to the UE includes a new field in the MobilityControlInfo information element to indicate to SeNB that the message is for additional radio resource configuration can do. The configuration example of the
Method 2 : sCellToAddMod Contains fields for displaying additional radio resource configurations
The RRC Connection Reconfiguration message sent by the MeNB to the UE (generated by the MeNB or generated by the SeNB and forwarded by the MeNB) is sent to the SeNB with a Release 10 SCell information element (eg, sCellToAddMod -r10). < / RTI > The configuration example of the
The ARRCtimer can be started when the UE receives an RRC Connection Reconfiguration message including information for additional radio resource configuration via the SeNB, and when the additional radio resource configuration is successfully completed (e.g., the MAC successfully completes the uplink synchronization, Or successfully complete the random access process, or send an RRC Connection Reconfiguration Complete message). If the ARRC timer expires before the additional radio resource configuration is successfully completed, the UE may revert to the radio resource configuration originally used in the MeNB. Additional radio resource configuration failure information can be stored in the VarRLF-Report. The ARRCtimer may be a T304 timer or a new timer that is not a T304 timer.
Another method is to add additional DRB-ToAddMod to the SCell additional modification information (sCellToAddMod-r12) instead of the SeNBradioresourceconfig information on whether additional radio resource configuration through SeNB is made, It can indicate the resource configuration.
Method 3 : Contains new information elements to display additional radio resource configurations
An RRC Connection Reconfiguration message (generated by MeNB or RRC message generated by SeNB and forwarded by MeNB) sent by the MeNB to the UE includes a new information element (eg SeNBRadioResourceConfig) to indicate to the SeNB that the message is for additional radio resource configuration . An example of the new information element configuration is as follows.
Another example of the above-described new information element configuration is as follows.
Another example of the above-described new information element configuration is as follows.
The UE may acquire system information after performing the random access process to the SeNB and configuring additional radio resources. Alternatively, the UE may not acquire the broadcasted system information by receiving the system information (RadioResourceConfigCommonSCell-r10) in the common radio resource configuration (radioResourceConfigCommon) through the RRC message.
Method 4 : Wireless resource configuration only ( radioResourceConfigDedicated ) Contains new fields to display additional radio resource configurations in the information element
The RRC Connection Reconfiguration message (generated by MeNB or RRC message generated by SeNB and forwarded by MeNB) sent by the MeNB to the UE is transmitted to the SeNB by radioResourceConfigDedicated information You can include a new field in an element. The configuration example of the
Additional radio resource configuration failure information
When the UE receives an RRC Connection Reconfiguration message including additional radio resource configuration information in the SeNB, the UE may start a timer for limiting the additional radio resource configuration time of the UE. The timer for limiting the additional radio resource configuration time of the UE may be a timer (e.g., T304 timer or ARRCtimer) included in the information for additional radio resource configuration in the SeNB including the RRC Connection Reconfiguration message. Alternatively, the timer value may be a pre-configured value for the UE.
If the additional radio resource configuration via the SeNB is successfully completed (e.g., before the RRC Connection Reconfiguration Complete message is sent, or the MAC successfully completes the uplink synchronization, or successfully completes the random access process) When the timer for limiting the radio resource configuration time expires, the UE may revert to the last radio resource configuration before receiving the RRC Connection Reconfiguration message including the additional radio resource configuration information. If the bearer is intended to be transmitted over the SeNB without bearer separation or bearer separation, it may be reconfigured with a radio bearer configuration previously configured via the MeNB for each of the bearer bearers. SeNB new radio resource configuration report for failure Element, or send an indication of the SeNB addition radio resource configuration failure to the MeNB. If the additional radio resource configuration failure information included in the new information element for the above-described VarRLF-Report or SeNB additional radio resource configuration failure report Here is an example:
The new information element for the VarRLF-Report or SeNB addition radio resource configuration failure report provides SeNB or SeNB information that fails to configure additional radio resources via the field (failedSeNBId or failedSCellId) to identify the SeNB or SeNB that failed to configure additional radio resources can do. The fields (failedSeNBId or failedSCellId) for identifying the SeNB or SeNB described above are the global cell identifiers of the SeNB or SCell or SeNB cell or the representative cell of the SeNB that have failed to configure the SeNB additional radio resource if available, cell identity and carrier frequency. Alternatively, a field (failedSeNBId or failedSCellId) for identifying the SCell of the SeNB or SeNB may include a SeNB identifier or a Seell ID of the SeNB that failed the additional radio resource configuration.
The new information element for the VarRLF-Report or SeNB addition radio resource configuration failure report includes a field (previousPCellId or previousMeNBId) identifying the PCell or MeNB that transmitted the RRC Connection Reconfiguration message including the SeNB additional radio resource configuration information before configuring the additional radio resource, Can be provided together. The previous PCellID or previousMeNBId field identifying the PCell or MeNB sets the global cell identifier of the PCell or MeNB or MeNB cell or MeNB representative cell. Alternatively, the previous PCellId or previousMeNBId field identifying the PCell or MeNB as described above may include a MeNB identifier.
The new information element for the VarRLF-Report or SeNB additional radio resource configuration failure report can set the elapsed time after receiving the last RRC Connection Reconfiguration message including the additional radio resource configuration information through the timeConnFailure field.
A new information element for the VarRLF-Report or SeNB Add Radio Resource Configuration Failure Report can set additional radio resource configuration failure types or cause values via the connectionFailureType field.
If the additional radio resource configuration via the SeNB is successfully completed (e.g., before the RRC Connection Reconfiguration Complete message is sent, or the MAC successfully completes the uplink synchronization, or successfully completes the random access process) If the timer for limiting the radio resource configuration time has expired and a new information element has been set for the above-described VarRLF-Report or SeNB additional radio resource configuration failure report, or if the additional radio resource configuration via the SeNB is successfully completed if the timer for limiting the additional radio resource configuration time of the UE expires before the RRC Connection Reconfiguration Complete message is sent or the MAC successfully completes the uplink synchronization or successfully completes the random access process, The UE transmits an RRC Connection Reconfiguration Complete message with the above-described VarRLF-Report or SeNB Add / It is possible to allow the MeNB to return to the radio resource configuration formerly used in the MeNB by transmitting a new information element for reporting a failure in line resource configuration or information for indicating that the SeNB additional radio resource configuration has failed, (Eg, RRC Connection Reconfiguration Complete) if the additional radio resource configuration via the SeNB has been successfully completed (eg, RRC Connection Reconfiguration Complete). The timer for limiting the additional radio resource configuration time of the UE expires before the transmission of the message or the MAC is successfully completed, or the random access process is successfully completed, and the above VarRLF-Report or SeNB If a new information element for additional radio resource configuration failure report is set, Or if the additional radio resource configuration via SeNB has been successfully completed (e.g. If the timer for limiting the additional radio resource configuration time of the UE expires before the RRC Connection Reconfiguration Complete message is sent or the MAC successfully completes the uplink synchronization or successfully completes the random access process, May send an indication or failure indication that the SeNB additional radio resource configuration failure information is available in the RRC Connection Reconfiguration Complete message so that the MeNB may revert to the radio resource configuration previously used in the MeNB. An indication that the SeNB additional radio resource configuration failure information included in the RRC Connection Reconfiguration Complete message is available may be expressed as ENUMERATED {cause1, cause2} by using the existing rlf-InfoAvailable (ENUMERATED {true}) or by extending the existing rlf- InfoAvailable ), Or a new field where additional radio resource configuration failure information is available [eg arrcf-InfoAvailable: additional radio resource configuration failure-infoAvailable (true)].
Another indication is that a new information element or SeNB additional radio resource configuration failure information for the VarRLF-Report or SeNB additional radio resource configuration failure report is available or a failure indication for the SeNB addition radio resource configuration is not included in the RRC Connection Reconfiguration message (E.g. UEInformationResponse or ULInformationTransfer or RRC Connection Re-establishment or a new RRC message). The conventional RRC Connection Reconfiguration procedure considers a reconfiguration failure if the UE fails to comply with a part of the configuration included in the RRC Connection reconfiguration message received from the base station, and if the security is not activated, leaves the RRC Connected state (leaving RRC_CONNECTED), and if not (e.g., when security is activated), the RRC Connection re-establish procedure had to be initiated.
In the process of configuring the SeNB additional radio resource while the UE is performing normal data communication through the MeNB, a connection failure to the SeNB (e.g., a problem on SeNB random access, a synchronization on the downlink of the SeNB serving cell, When the SeNB additional radio resource configuration failure occurs due to N310 consecutive out-of-sync indications in the physical layer of the SeNB serving cell, etc., it may be inefficient to process the RRC connection reconfiguration failure as in the conventional method . That is, since the UE can perform normal data communication through the MeNB even if it fails to configure the additional radio resource through the SeNB, the UE sets the RRC connection again after the transition from the RRC connected state to the RRC IDLE state, or re-establishes the RRC connection ), It may be quite inefficient to stop all radio bearers except SRB0, release SCell, reselect the cell, resume SRB1, and reconfigure the DRB according to the RRC Connection reconfiguration.
Therefore, as described above, a failure indication for the SeNB additional radio resource configuration is included in the RRC Connection Reconfiguration message, a new failure message for reporting the failure of the SeNB additional radio resource configuration is defined, or an existing RRC Connection re- Can be modified. For example, if the RRC Connection Reconfiguration message includes a failure indication for the SeNB additional radio resource configuration, the UE can maintain the serving cell (s) of the existing MeNB.
As another example, when transmitting a new RRC failure message for the SeNB additional radio resource configuration, the UE can maintain the serving cell (s) of the existing MeNB.
As another example, if the RRC Connection Reset procedure is executed due to the SeNB additional radio resource configuration failure, the UE can maintain the serving cell (s) of the existing MeNB. And a ReestablishmentCause information of the RRC Connection re-establish request message may include a SeNB additional radio resource configuration failure indication. If the MeNB receives a new information element for the VarRLF-Report or SeNB additional radio resource configuration failure report Or SeNB additional radio resource configuration information is available or a failure indication for the SeNB addition radio resource configuration is received, the MeNB may de-provision the on-going SeNB additional radio resource configuration in the MeNB. The MeNB may then send a message (an offload cancel message) to the SeNB to cancel the ongoing additional radio resource configuration preparation.
How the UE sends an RRC Connection Reconfiguration Complete message to MeNB
In step 8, the UE may send an RRC Connection Reconfiguration Complete message to the MeNB using the following method.
Method 1 : MeNB in RRC Connection Reconfiguration Complete Send message
The UE may send an RRC Connection Reconfiguration Complete message to the MeNB. If the Signaling Radio Bearer (SRB) for transmitting an RRC message is configured in the MeNB and the SeNB through the bearer separated additional radio resource configuration as shown in FIG. 5, the UE does not distinguish between the MeNB uplink and SeNB uplink, Reconfiguration Complete can be transmitted. If the Signaling Radio Bearer (SRB) for transmitting the RRC message is configured to be transmitted only through MeNB in FIG. 5, the UE transmits RRC Connection Reconfiguration Complete to the MeNB uplink transmission channel. If the Signaling Radio Bearer (SRB) for transmitting the RRC message is configured to be transmitted only through the MeNB in FIG. 6, the UE can transmit the RRC Connection Reconfiguration Complete message to the MeNB uplink transport channel with the SRB set.
The MeNB receiving the RRC Connection Reconfiguration Complete message can forward it to the SeNB. Or the MeNB receiving the RRC Connection Reconfiguration Complete message can forward a success message to the SeNB for the additional radio resource configuration.
5, when the RRC Connection Reconfiguration Complete message is transmitted through the SeNB transmission channel of the UE, the SeNB transmits the MeNB and the SeNB to the MeNB and the SeNB through the additional radio resource configuration, The RRC Connection Reconfiguration Complete message is forwarded to the RRC.
Alternatively, SeNB can verify the success of additional radio resources, such as through Random Access procedures.
Method 2 : SeNB in RRC Connection Reconfiguration Complete Send message
The UE may send an RRC Connection Reconfiguration Complete message to the SeNB. If a Signaling Radio Bearer (SRB) for transmitting an RRC message is configured in the MeNB and the SeNB through a bearer-separated additional radio resource configuration as shown in FIG. 5, the UE can transmit RRC Connection Reconfiguration Complete via the SeNB uplink transmission channel. Even if the Signaling Radio Bearer (SRB) for transmitting the RRC message is configured to be transmitted only through MeNB in FIG. 5, the UE transmits RRC Connection Reconfiguration Complete to the SeNB uplink logical channel. Even if the Signaling Radio Bearer (SRB) for transmitting the RRC message is configured to be transmitted only through MeNB in FIG. 6, the UE can transmit the RRC Connection Reconfiguration Complete message to the SeNB uplink transmission channel.
The SeNB that received the RRC Connection Reconfiguration Complete message can forward it to the MeNB.
Method 3 : MeNB Wow SeNB Respectively RRC Connection Reconfiguration Complete Send message
The UE may send an RRC Connection Reconfiguration Complete message to MeNB and SeNB. To this end, the RRC Connection Reconfiguration message may include information for allowing the UE to transmit an RRC Connection Reconfiguration Complete message to each of the MeNB and the SeNB. If the UE includes information for transmitting an RRC Connection Reconfiguration Complete message to each of the MeNB and the SeNB in the RRC Connection Reconfiguration message or includes information indicating the additional radio resource configuration in the SeNB, the UE transmits the MeNB uplink transmission channel and the SeNB RRC Connection Reconfiguration Complete can be transmitted to the uplink transmission channel through each of them. MeNB or SeNB can forward the received RRC Connection Reconfiguration Complete message to SeNB or MeNB.
The present invention may be provided by a secondary eNB (or SeNB or Small cell eNB or Small eNB or SCell eNB or Assisting eNB) to use radio resources provided by one or more different network points connected through a non-ideal backhaul The UE and the MeNB can resume the existing radio resource configuration and continue the communication even if the additional radio resource configuration is not successful due to the radio link failure or the like in the process of configuring the additional radio resources.
7 is a diagram illustrating a configuration of a base station according to another embodiment of the present invention.
Referring to FIG. 7, a
The
The
FIG. 8 is a diagram illustrating a configuration of a user terminal according to another embodiment of the present invention.
Referring to FIG. 8, a
The receiving
In addition, the
The
The standard content or standard documents referred to in the above-mentioned embodiments constitute a part of this specification, for the sake of simplicity of description of the specification. Therefore, it is to be understood that the content of the above standard content and portions of the standard documents are added to or contained in the scope of the present invention.
The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.
Claims (1)
Adding a secondary base station for additional radio resources;
Detecting a radio link failure in an additional process of the secondary base station; And
And resuming communication with the master base station upon occurrence of the radio link failure.
Priority Applications (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR1020130161875A KR101602999B1 (en) | 2013-06-13 | 2013-12-23 | Methods for configuring a dual connection in mobile communication networks and apparatuses thereof |
| PCT/KR2014/010094 WO2015064972A1 (en) | 2013-06-13 | 2014-10-27 | Method and apparatus for configuring dual connection in mobile communication network |
| CN201480058780.3A CN105684491B (en) | 2013-10-30 | 2014-10-27 | Method for configuring dual connection in mobile communication network and apparatus therefor |
| US15/032,651 US10362615B2 (en) | 2013-10-30 | 2014-10-27 | Method and apparatus for configuring dual connection in mobile communication network |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR20130068044 | 2013-06-13 | ||
| KR1020130068044 | 2013-06-13 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| KR20140145524A true KR20140145524A (en) | 2014-12-23 |
Family
ID=52675287
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| KR1020130130408A KR20140145524A (en) | 2013-06-13 | 2013-10-30 | Methods and apparatus for dual connectivity configuration |
| KR1020130161875A KR101602999B1 (en) | 2013-06-13 | 2013-12-23 | Methods for configuring a dual connection in mobile communication networks and apparatuses thereof |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| KR1020130161875A KR101602999B1 (en) | 2013-06-13 | 2013-12-23 | Methods for configuring a dual connection in mobile communication networks and apparatuses thereof |
Country Status (2)
| Country | Link |
|---|---|
| KR (2) | KR20140145524A (en) |
| WO (1) | WO2015064972A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107113670A (en) * | 2014-12-30 | 2017-08-29 | Lg 电子株式会社 | The method and apparatus switched between the MENB changed without SENB are performed in wireless communication system |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106332114A (en) * | 2015-06-19 | 2017-01-11 | 北京信威通信技术股份有限公司 | Method of optimizing network mobility |
| KR101954495B1 (en) * | 2015-09-23 | 2019-03-07 | 주식회사 케이티 | Methods for controlling mobility of UE and Apparatuses thereof |
| WO2017052206A1 (en) * | 2015-09-23 | 2017-03-30 | 주식회사 케이티 | Method for controlling mobility of terminal, and device therefor |
| EP3445128B1 (en) * | 2016-05-10 | 2022-02-23 | Huawei Technologies Co., Ltd. | Method and device for data transmission |
| CN111935779A (en) * | 2016-05-11 | 2020-11-13 | 华为技术有限公司 | Radio Resource Control (RRC) configuration method and related equipment |
| CN107690200B (en) * | 2016-08-05 | 2019-12-10 | 电信科学技术研究院 | random access method and terminal |
| WO2018056623A1 (en) * | 2016-09-22 | 2018-03-29 | Lg Electronics Inc. | Handling of conflict configuration in dual connectivity |
| US11064401B2 (en) | 2017-04-01 | 2021-07-13 | Samsung Electronics Co., Ltd. | Random access method, network node and user equipment |
| CN109600841B (en) * | 2017-09-30 | 2024-03-15 | 北京三星通信技术研究有限公司 | Random access method, network node and user equipment |
| EP3666035B1 (en) | 2017-08-07 | 2023-04-05 | LG Electronics Inc. | Method and apparatus for keeping dc configuration |
| WO2020197469A1 (en) | 2019-03-25 | 2020-10-01 | Telefonaktiebolaget Lm Ericsson (Publ) | User equipment, radio network node and methods performed therein for handling communication |
| KR20210016945A (en) * | 2019-08-06 | 2021-02-17 | 삼성전자주식회사 | Method and apparatus for processing integrity verification failure in high reliability and low latency service supporting system |
| KR102393333B1 (en) * | 2020-09-23 | 2022-04-29 | 주식회사 엘지유플러스 | Method of Blocking a 5G NR Addition |
| CN113301510B (en) * | 2021-05-25 | 2022-06-28 | 浙江万消基业科技有限公司 | Smart city safety management method and system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101473005B1 (en) * | 2008-03-14 | 2014-12-15 | 엘지전자 주식회사 | Method of performing uplink synchronization in wireless communication system |
| KR101470648B1 (en) * | 2008-09-24 | 2014-12-09 | 엘지전자 주식회사 | Method of transmitting control signal in multi-cell cooperative wireless communication system |
| CN102045862B (en) * | 2009-10-22 | 2014-10-01 | ***通信集团公司 | Carrier aggregation realizing method, device and system |
| KR101419571B1 (en) * | 2010-09-10 | 2014-07-14 | 주식회사 팬택 | User Terminal and Method of Radio Resource Connection |
-
2013
- 2013-10-30 KR KR1020130130408A patent/KR20140145524A/en unknown
- 2013-12-23 KR KR1020130161875A patent/KR101602999B1/en active IP Right Grant
-
2014
- 2014-10-27 WO PCT/KR2014/010094 patent/WO2015064972A1/en active Application Filing
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107113670A (en) * | 2014-12-30 | 2017-08-29 | Lg 电子株式会社 | The method and apparatus switched between the MENB changed without SENB are performed in wireless communication system |
| US10588065B2 (en) | 2014-12-30 | 2020-03-10 | Lg Electronics Inc. | Method and apparatus for performing inter-MeNB handover without SeNB change in wireless communication system |
| CN107113670B (en) * | 2014-12-30 | 2020-10-30 | Lg 电子株式会社 | Method and apparatus for performing inter-MENB handover without SENB change in wireless communication system |
| US10856196B2 (en) | 2014-12-30 | 2020-12-01 | Lg Electronics Inc. | Method and apparatus for performing inter-MeNB handover without SeNB change in wireless communication system |
| US11044655B2 (en) | 2014-12-30 | 2021-06-22 | Lg Electronics Inc. | Method and apparatus for performing inter-MeNB handover without SeNB change in wireless communication system |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2015064972A1 (en) | 2015-05-07 |
| KR101602999B1 (en) | 2016-03-11 |
| KR20140145527A (en) | 2014-12-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11503634B2 (en) | Method and apparatus for supporting RACH-less mobility with pre-allocated beams in wireless communication system | |
| KR101954495B1 (en) | Methods for controlling mobility of UE and Apparatuses thereof | |
| KR102183826B1 (en) | Methods for configuring dual connectivity of UE and Apparatuses thereof | |
| KR102174932B1 (en) | Methods for transmitting and receiving a data in Dual connectivity and Apparatuses thereof | |
| US10362615B2 (en) | Method and apparatus for configuring dual connection in mobile communication network | |
| US10278126B2 (en) | Method for activating or deactivating small cell and apparatus therefor | |
| KR101632277B1 (en) | Handover Methods for a mobile station connected with multiple base stations and apparatuses thereof | |
| KR101602999B1 (en) | Methods for configuring a dual connection in mobile communication networks and apparatuses thereof | |
| US9832806B2 (en) | Method for processing radio link failure and device therefor | |
| US10856201B2 (en) | Handover control method and device therefor | |
| US10362590B2 (en) | Method for transmitting uplink data and apparatus for same | |
| KR102038500B1 (en) | Methods for processing uplink data And Apparatuses thereof | |
| KR102258443B1 (en) | Method for configuring transmission time interval bundling at a user equipment with multiple carriers and device therefor | |
| US20180020444A1 (en) | Method for applying a new pucch configuration in a carrier aggregation system and a device therefor | |
| KR20140107088A (en) | Methods and apparatuses for transmitting buffer status report of a user equipment in small cell deployments | |
| US10687369B2 (en) | Method for initiating a random access procedure in a carrier aggregation system and a device therefor | |
| US10034312B2 (en) | Method for initiating a random access procedure in a carrier aggregation system and a device therefor | |
| KR20170114258A (en) | Methods for performing handover and Apparatuses thereof | |
| KR102003273B1 (en) | Method and apparatus of configuring ue identifier in wireless communication system supporting dual connectivity | |
| KR20150109174A (en) | Method and apparatus for radio resource control connection reestablishment in dual connectivity | |
| KR20150018285A (en) | Method and apparatus for transmitting scheduling request of user equipment in wireless communication system | |
| US20170374688A1 (en) | Method for initiating a random access procedure in a carrier aggregation system and a device therefor | |
| KR20140137277A (en) | Methods and apparatuses for RRC Connection Re-establishment/Re-configuration | |
| KR101930114B1 (en) | Methods for transmitting uplink data and Apparatuses thereof |