[go: up one dir, main page]

WO2015023128A1 - Méthode et appareil de transmission/réception de données en utilisant de multiples porteuses dans un système de communication mobile - Google Patents

Méthode et appareil de transmission/réception de données en utilisant de multiples porteuses dans un système de communication mobile Download PDF

Info

Publication number
WO2015023128A1
WO2015023128A1 PCT/KR2014/007538 KR2014007538W WO2015023128A1 WO 2015023128 A1 WO2015023128 A1 WO 2015023128A1 KR 2014007538 W KR2014007538 W KR 2014007538W WO 2015023128 A1 WO2015023128 A1 WO 2015023128A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
terminal
serving cell
transmission
subframe
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.)
Ceased
Application number
PCT/KR2014/007538
Other languages
English (en)
Korean (ko)
Inventor
김성훈
정경인
김영범
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to EP14836612.3A priority Critical patent/EP3035561A4/fr
Priority to US14/912,386 priority patent/US9992773B2/en
Priority to EP19155351.0A priority patent/EP3506528A1/fr
Publication of WO2015023128A1 publication Critical patent/WO2015023128A1/fr
Anticipated expiration legal-status Critical
Priority to US15/996,240 priority patent/US10149295B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
    • H04B7/2643—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile using time-division multiple access [TDMA]
    • H04B7/2656—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile using time-division multiple access [TDMA] for structure of frame, burst
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
    • H04B7/2603—Arrangements for wireless physical layer control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
    • H04B7/26—Radio transmission systems, i.e. using radiation field for communication between two or more posts at least one of which is mobile
    • H04B7/2612—Arrangements for wireless medium access control, e.g. by allocating physical layer transmission capacity
    • 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) or DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/001—Synchronization between nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0453—Resources in frequency domain, e.g. a carrier in FDMA
    • 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/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • 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/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0096—Indication of changes in allocation
    • H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
    • 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/14—Two-way operation using the same type of signal, i.e. duplex
    • H04L5/143—Two-way operation using the same type of signal, i.e. duplex for modulated signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/18—TPC being performed according to specific parameters
    • H04W52/24—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters
    • H04W52/242—TPC being performed according to specific parameters using SIR [Signal to Interference Ratio] or other wireless path parameters taking into account path loss
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/30—Transmission power control [TPC] using constraints in the total amount of available transmission power
    • H04W52/32—TPC of broadcast or control channels
    • H04W52/327—Power control of multicast channels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/30—Transmission power control [TPC] using constraints in the total amount of available transmission power
    • H04W52/34—TPC management, i.e. sharing limited amount of power among users or channels or data types, e.g. cell loading
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/30—Transmission power control [TPC] using constraints in the total amount of available transmission power
    • H04W52/36—Transmission power control [TPC] using constraints in the total amount of available transmission power with a discrete range or set of values, e.g. step size, ramping or offsets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/30—Transmission power control [TPC] using constraints in the total amount of available transmission power
    • H04W52/36—Transmission power control [TPC] using constraints in the total amount of available transmission power with a discrete range or set of values, e.g. step size, ramping or offsets
    • H04W52/365—Power headroom reporting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/04—Transmission power control [TPC]
    • H04W52/30—Transmission power control [TPC] using constraints in the total amount of available transmission power
    • H04W52/36—Transmission power control [TPC] using constraints in the total amount of available transmission power with a discrete range or set of values, e.g. step size, ramping or offsets
    • H04W52/367—Power values between minimum and maximum limits, e.g. dynamic range
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/53—Allocation or scheduling criteria for wireless resources based on regulatory allocation policies
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to a mobile communication system, and more particularly, to a method and apparatus for transmitting and receiving data using a plurality of carriers in a mobile communication system.
  • a mobile communication system has been developed for the purpose of providing communication while securing user mobility.
  • Such a mobile communication system has reached a stage capable of providing high-speed data communication service as well as voice communication due to the rapid development of technology.
  • the LTE system is a technology for implementing a high-speed packet-based communication having a transmission rate of up to 100 Mbps higher than the currently provided data rate and is almost standardized.
  • Carrier aggregation is a representative example of the new technology to be introduced.
  • Carrier aggregation means that a terminal uses a plurality of forward carriers and a plurality of reverse carriers, unlike a conventional terminal that transmits and receives data using only one forward carrier and one reverse carrier.
  • An embodiment of the present disclosure has been made to solve at least some of the above problems, and an object thereof is to provide a method and apparatus for inter-ENB carrier aggregation between different base stations.
  • the data transmission and reception method of the terminal using a plurality of carriers additional control of the serving cell including uplink subframe pattern information for the master serving cell group or slave serving cell group
  • the uplink subframe pattern information may include information on a subframe in which uplink transmission is allowed for the master serving cell group, information on a subframe in which uplink transmission is allowed for the slave serving cell group, or It may include at least one of information on subframes for which uplink transmission is not allowed.
  • the length of the uplink subframe pattern may be determined based on a hybrid retransmission request (HARQ) round trip time (RTT).
  • HARQ hybrid retransmission request
  • RTT round trip time
  • the uplink subframe pattern information includes bit information indicating a subframe allowed for uplink transmission for the master serving cell group, and uplink transmission for the slave serving cell group is allowed. Bit information about the subframe or offset information indicating the start of the subframe pattern may be included.
  • the uplink subframe pattern information may be pattern index information indicating one pattern among a plurality of subframe patterns having a predetermined length.
  • a terminal for transmitting and receiving data using a plurality of carriers includes a transceiver for transmitting and receiving a signal to and from a base station, and uplink subframe pattern information for a master serving cell group or a slave serving cell group.
  • the transmission and reception speed of the terminal may be improved.
  • FIG. 1 is a diagram illustrating a structure of an LTE system to which some embodiments of the present specification are applied.
  • FIG. 2 is a diagram illustrating a radio protocol structure in an LTE system to which some embodiments of the present disclosure are applied.
  • FIG. 3 is a diagram illustrating carrier aggregation in a base station to which some embodiments of the present disclosure are applied.
  • FIG. 4 illustrates a carrier aggregation scheme according to an embodiment of the present disclosure.
  • 5 is a diagram illustrating an inefficient PUSCH transmission because a length of a pattern is set incorrectly.
  • FIG. 6 is a diagram illustrating a preferred pattern setting.
  • FIG. 7 is a flowchart illustrating operations of a terminal and a base station for configuring a SCell belonging to the MSCG.
  • FIG. 8 is a flowchart illustrating operations of a terminal and a base station for configuring a SCell belonging to an SSCG.
  • FIG. 9 is a configuration diagram of an RRC control message according to an embodiment of the present specification.
  • FIG. 10 is a configuration diagram of an RRC control message according to another embodiment of the present specification.
  • FIG. 11 is a diagram illustrating a CQI transmission subframe determined through a subframe pattern and CQI configuration information.
  • FIG. 12 is a diagram illustrating a UE operation for determining whether to transmit a PUCCH CQI in any subframe n.
  • FIG. 13 is a diagram illustrating an operation of a terminal for determining whether to transmit an SRS in an arbitrary subframe n.
  • FIG. 14 is a diagram illustrating an operation of a terminal transmitting an SR when a buffer status report is triggered.
  • 15 is a diagram illustrating an operation of a terminal performing random access.
  • 16 is a flowchart of operations of a terminal and a base station in which the terminal reports the performance and the base station sets the CA between the base stations.
  • 17 is a diagram illustrating a configuration of performance report information of a terminal.
  • 18 is a diagram illustrating a case where an MSCG subframe and an SSCG subframe overlap.
  • 19 is a diagram illustrating a structure of a terminal according to an embodiment of the present specification.
  • 20 is a diagram illustrating a structure of a base station according to an embodiment of the present specification.
  • 21 is a diagram illustrating a structure of a slave base station according to an embodiment of the present specification.
  • 22 is a diagram illustrating an operation of a terminal according to an embodiment of the present disclosure when a random access failure occurs.
  • 23 is a diagram illustrating an example of measurement setting.
  • 24 is a diagram illustrating a terminal operation of treating an SCell as a serving cell or a neighbor cell according to a measurement report setting.
  • 25 is a diagram illustrating a case where initial transmission and retransmission collide on the time axis.
  • FIG. 26 is a diagram illustrating a terminal operation when initial transmission and retransmission collide on the time axis.
  • 27 illustrates an operation of a terminal receiving an RRC control message.
  • 28A and 28B illustrate UE operation when a regular BSR is triggered.
  • 29 illustrates an operation of a terminal for determining a cell to trigger random access according to an indication of a base station.
  • FIG. 1 is a diagram illustrating a structure of an LTE system to which some embodiments of the present specification are applied.
  • a radio access network of an LTE system includes a next-generation base station (Evolved Node B, ENB, Node B or base station) 105, 110, 115, and 120, an MME 125, and a Mobility Management Entity (S-GW). (130, Serving-Gateway).
  • the user equipment (hereinafter referred to as UE or terminal) 135 connects to an external network through the ENBs 105, 110, 115, and 120 and the S-GW 130.
  • the ENBs 105, 110, 115, and 120 correspond to existing Node Bs of the UMTS system.
  • the ENB is connected to the UE 135 through a radio channel and performs a more complicated role than the existing Node B.
  • all user traffic including real-time services such as Voice over IP (VoIP) over the Internet protocol, is serviced through a shared channel, so information on the status of buffers, available transmit power, and channel status of UEs is available.
  • VoIP Voice over IP
  • a device is needed to collect and schedule the ENBs 105, 110, 115, and 120.
  • One ENB typically controls multiple cells.
  • the LTE system uses Orthogonal Frequency Division Multiplexing (OFDM) as a radio access technology in a 20 MHz bandwidth.
  • OFDM Orthogonal Frequency Division Multiplexing
  • AMC adaptive modulation & coding
  • the S-GW 130 is a device that provides a data bearer, and generates or removes a data bearer under the control of the MME 125.
  • the MME is a device that is in charge of various control functions as well as mobility management function for the terminal and is connected to a plurality of base stations.
  • FIG. 2 is a diagram illustrating a radio protocol structure in an LTE system to which some embodiments of the present disclosure are applied.
  • a wireless protocol of an LTE system includes packet data convergence protocols 205 and 240 (PDCP), radio link control 210 and 235 (RMC), and medium access control 215 and 230 (MAC) in a terminal and an ENB, respectively.
  • the PDCP Packet Data Convergence Protocol
  • RLC Radio Link control
  • PDCP PDU Packet Data Unit
  • the MACs 215 and 230 are connected to several RLC layer devices configured in one terminal, and multiplex RLC PDUs to MAC PDUs and demultiplex RLC PDUs from MAC PDUs.
  • the physical layers 220 and 225 channel-code and modulate higher layer data, make an OFDM symbol, and transmit it to a wireless channel, or demodulate, channel decode, and transmit the received OFDM symbol through a wireless channel to a higher layer. .
  • FIG. 3 is a diagram illustrating carrier aggregation in a base station to which some embodiments of the present disclosure are applied.
  • one base station can generally transmit and receive multiple carriers over several frequency bands. For example, when a carrier 315 having a forward center frequency of f1 and a carrier having a forward center frequency of f3 (310) is transmitted from the base station 305, one terminal conventionally uses one carrier of the two carriers. To transmit and receive data. However, a terminal having carrier aggregation capability may transmit and receive data through multiple carriers at the same time. The base station 305 may increase the transmission speed of the terminal 330 by allocating more carriers to the terminal 330 having carrier aggregation capability according to a situation. As described above, integrating forward and reverse carriers transmitted and received by one base station is called carrier aggregation in the base station. However, in some cases, unlike in FIG. 3, it may be necessary to integrate forward and reverse carriers transmitted and received from different base stations.
  • FIG. 4 is a diagram illustrating a carrier aggregation method according to an embodiment of the present specification.
  • the terminal 430 when the base station 1 405 transmits and receives a carrier having a center frequency of f1 and the base station 2 420 transmits and receives a carrier having a center frequency of f2, the terminal 430 has a carrier having a forward center frequency of f1.
  • the forward center frequency and (f2) carrier aggregates (combined), one terminal is a result of the aggregation of carriers transmitted and received from two or more base stations, in the present specification it is inter-ENB carrier aggregation (or inter-base station) CA).
  • carrier aggregation is understood as a terminal transmitting and receiving data through multiple cells at the same time. It could be. This increases the maximum transfer rate in proportion to the number of carriers integrated.
  • the terminal receiving data through any forward carrier or transmitting data through any reverse carrier means that the control channel and the data channel provided by the cell corresponding to the center frequency and the frequency band characterizing the carrier It has the same meaning as transmitting and receiving data using.
  • carrier aggregation will be expressed as 'a plurality of serving cells are set', and terms such as primary serving cell (hereinafter referred to as PCell) and secondary serving cell (hereinafter referred to as SCell) or activated serving cell will be used.
  • PCell primary serving cell
  • SCell secondary serving cell
  • activated serving cell activated serving cell
  • a set of serving cells controlled by the same base station is defined as a serving cell group (SCG).
  • the serving cell group is further divided into a master serving cell group (MSCG) and a slave serving cell group (SSCG).
  • the MSCG means a set of serving cells controlled by a base station (hereinafter referred to as a master base station, MeNB) that controls the PCell, and the SSCG is not a base station that controls the PCell, that is, a base station that controls only the SCells (hereinafter referred to as a slave base station, SeNB).
  • MeNB master base station
  • SeNB slave base station
  • Means a set of serving cells controlled by). Whether a predetermined serving cell belongs to the MSCG or SSCG is set by the base station in the process of setting the serving cell.
  • One MSCG and one or more SSCGs may be configured in one UE, and in the present invention, only one SSCG is set for convenience of description, but even if one or more SSCGs are set, the contents of the present invention may be applied as they are. Can be.
  • MSCG and SSCG may be used instead of MSCG and SSCG for understanding.
  • terms such as primary set and secondary set or primary carrier group and secondary carrier group or MCG (MeNB Cell Group) and SCG (SeNB Cell Group) may be used.
  • MCG Mobile Cell Group
  • SCG SeNB Cell Group
  • one or more SCGs may be configured in the terminal. However, in the present invention, it is assumed that at most one SCG may be configured in the terminal.
  • An SCG may consist of several SCells, one of which has special properties.
  • the UE may transmit HARQ feedback and CSI as well as HARQ feedback and CSI for the PCell through the PUCCH of the PCell. This is to apply a CA to a terminal that cannot simultaneously transmit uplink.
  • HARQ feedback should be delivered within HARQ Round Trip Time (typically 8 ms), since the transmission delay between MeNB and SeNB may be longer than HARQ RTT. Due to the above problem, a PUCCH transmission resource may be configured in one cell of a SCell belonging to an SCG, and HARQ feedback and CSI for SCG SCells may be transmitted through the PUCCH.
  • the special SCell is called PSCell (primary SCell) or PUCCH SCell.
  • the scheduler is provided in units of base stations, and it may not be easy to schedule transmission resources of a plurality of base stations without overlapping each other in real time. Accordingly, a terminal configured with one or more SCGs may be instructed to perform simultaneous backward transmission in serving cells controlled by one or more schedulers and belonging to different SCGs. Typically, since serving cells belonging to the same frequency band constitute one SCG, when performing simultaneous backward transmission on serving cells belonging to different SCGs, a so-called inter-modulation distortion (IMD) problem may occur. . Whether the IMD is generated has a close relationship with the structure of the terminal. For example, the structure of a terminal may be classified as follows, when operating in arbitrary f1 and f2.
  • f1 or f2 is a frequency specified by a predetermined bandwidth with respect to one center frequency
  • FDD frequency division duplex
  • a forward center frequency is determined.
  • a forward frequency specified in a predetermined bandwidth and a reverse frequency specified in a predetermined bandwidth are specified together with the center as the center.
  • 2Rx / 2Tx structure A Structure using separate Rx device, separate Tx device and separate power amplifier for f1 and f2. Forward simultaneous reception is possible. Reverse simultaneous transmission without IMD problems
  • 2Rx / 2Tx structure B structure using separate Rx devices, separate Tx devices and a common power amplifier for f1 and f2. Forward simultaneous reception is possible. IMD problem during reverse simultaneous transmission.
  • 2Rx / 1Tx structure A structure using separate Rx devices and common Tx devices for f1 and f2. Forward simultaneous reception is possible. Reverse simultaneous transmission impossible
  • 1Rx / 1Tx structure A structure using a common Rx device and a common Tx device for f1 and f2. Both forward and reverse simultaneous transmission is impossible
  • the terminal reports information indicating what structure is applied for each frequency band combination, and information indicating whether simultaneous transmission and reception are possible to the base station, and the base station schedules the terminal without precluding simultaneous transmission and reception or between SCGs based on the information.
  • the terminal is scheduled so that simultaneous backward transmission does not occur by using a time division multiplex (TDM) scheme.
  • TDM time division multiplex
  • the base station allocates a predetermined pattern to the terminal, and the terminal performs backward transmission between SCGs in a TDM form according to the pattern.
  • the TDM pattern is composed of the following three types of subframes.
  • MSCG subframe subframe allowed for backward transmission of master serving cells
  • SSCG subframe subframe allowed for backward transmission of slave serving cells
  • Switching subframe subframe in which reverse transmission is not allowed
  • the reason why the switching subframe is necessary is that the UE re-transmits the RF device to perform backward transmission in the serving cell of the MSCG and then perform backward transmission in the serving cell of the SSCG.
  • the time period required for readjustment of the RF device may vary depending on the structure or hardware performance of the terminal.
  • the terminal may report information indicating whether the switching subframe is necessary and the temporal length of switching for each frequency band combination to the base station.
  • a switching period of several hundred microseconds may be necessary because the Tx device needs to be reset during switching. If the 2Rx / 2Tx structure B is applied, a switching period smaller than one OFDM symbol length (about 66.7 microseconds) may be needed because the Tx device is used separately and only the path of the reverse signal is adjusted during switching.
  • the applied structure and the position or frequency of the switching subframe may have a close relationship, and the terminal provides related information so that the base station can properly arrange the switching subframe.
  • the MSCG subframe, the SSCG subframe, and the switching subframe are repeated in the same pattern with a constant period, and the length of the pattern is also an important factor influencing performance.
  • HARQ hybrid automatic request
  • PUSCH Physical Uplink Shared Channel
  • RTT HARQ round trip time
  • the length of the pattern is set differently from HARQ RTT, HARQ operation becomes inefficient. For example, if the length of the pattern is 10 subframes (_505), the PUSCH retransmission cannot be performed because the retransmission time point for the PUSCH transmission (_510) performed in any master serving cell is an SSCG subframe or a switching subframe ( _515, _520, and _525 may occur.
  • the length of the pattern is defined in consideration of HARQ RTT so that the above problem does not occur.
  • a pattern having a length of 8 subframes is used, and a combination between TDD bands.
  • the pattern with the following length is used according to the forward / reverse direction setting.
  • TDD there may be seven UL / DL configurations as shown in [Table 1].
  • the reverse HARQ RTT (temporal distance between HARQ initial transmission and HARQ retransmission) and bitmap length for each configuration are shown in [Table 2].
  • D denotes a forward subframe
  • U denotes a reverse subframe
  • S denotes a special subframe
  • the reverse HARQ RTT for 1, 2, 3, 4, and 5 is 10 ms, and the bitmap length is 10 bits.
  • the HARQ RTT of the reverse / forward settings 0 and 6 consists of two repeated values. For example, in configuration 0, the HARQ RTT is 11 ms for the nth transmission and the HARQ RTT is 13 ms for the (n + 1) th transmission.
  • the bitmap length is defined as the product of two RTTs multiplied by two to enable flexible pattern setting. That is, in setting 0, 48 bits, which are twice as large as (11 + 13) and 50 bits, which are twice as large as (11 + 14), are defined as the length of the bitmap.
  • FIG. 6 is a diagram illustrating a preferred pattern setting.
  • a pattern so that the MSs do not overlap each other.
  • a certain subframe is set to a switching subframe for one terminal, an MSCG subframe for another terminal, and an SSCG subframe for another terminal (_605) in view of transmission resource efficiency.
  • the starting point of the pattern is set differently for each terminal.
  • the following three pieces of information are transmitted to the terminal so that a specialized pattern for each terminal can be set as described above.
  • Bitmap 1 has a predetermined length, and each bit specifies whether or not the MSCG subframe. For example, 1 means MSCG subframe.
  • the length is 8 bits if the CA in the FDD band, 10 bits, 48 bits or 50 bits if the CA in the TDD band.
  • Bitmap 2 Has the same length as Bitmap 1, each bit specifies whether or not it is an SSCG subframe.
  • the subframe pattern is determined by bitmap 1 and bitmap 2.
  • a subframe indicated by a predetermined value in bitmap 1, for example 1 is an MSCG subframe
  • a subframe indicated by the predetermined value in bitmap 2 is an SSCG subframe
  • another predetermined in both bitmaps is determined by bitmap 1 and bitmap 2.
  • a subframe indicated by a value of, for example, 0 indicates a switching subframe.
  • Bitmap 2 may be defined as 00001110.
  • the first, second, and third subframes are MSCG subframes because they are indicated by bitmaps 1 through 1, and the fifth, sixth, and seventh subframes are indicated by bitmaps 2 through 1, and so are SSCG subframes. Since the first subframe is indicated by 0 in both bitmaps, it may indicate a switching subframe.
  • the subframe pattern may be defined as an index instead of being defined as two bitmaps as described above.
  • a pattern index may be defined and the index may be signaled.
  • Uppercase M means MSCG subframe
  • uppercase S means SSCG subframe
  • lowercase s means switching subframe.
  • the terminal calculates the reference subframe (or the starting subframe) of the subframe pattern using Equation 1 using the offset.
  • the subframes in which the pattern starts are as follows.
  • FIG. 7 is a flowchart illustrating an operation sequence of a terminal and a base station for configuring a SCell belonging to an MSCG according to an embodiment of the present specification.
  • serving cell_m the serving cell belonging to the MSCG
  • serving cell_s the serving cell belonging to SSCG
  • the mobile communication system may include a terminal 705, a base station 1 710, and a base station 2 715.
  • Cell a, cell b and cell c are controlled by base station 2 715 and cell d and cell e are controlled by base station 1 710. Assume that the PCell of the terminal is cell a.
  • Base station 1 715 is a MeNB in accordance with the term definition above.
  • Base station 1 715 which is a MeNB, wants to configure cell b as an additional SCell to the terminal.
  • the MeNB 715 stores and transmits information related to the SCell to be newly added to the UE 705 in an RRC connection reconfiguration control message (step 720).
  • the newly added SCell is a cell directly managed by a serving base station, and at least one of the information described in Table 4 is stored in the control message.
  • cellIdentification-r10 Information that physically identifies the serving cell. It consists of forward center frequency and PCI (Physical Cell Id).
  • radioResourceConfigCommonSCell-r10 Information related to radio resources of the serving cell. For example, it includes forward bandwidth, forward HARQ feedback channel configuration information, reverse center frequency information, reverse bandwidth information, and the like.
  • Timing Advance Group Information indicating which TAG a terminal belongs to. This may be configured, for example, with a TAG id and a Timing Advance (TA) timer. If the terminal belongs to a P-TAG (primary TAG), this information is not signaled.
  • TAG is a set of serving cells that share the same backward transmission timing.
  • Types of TAG include P-TAG (Primary TAG) and S-TAG (Secondary TAG).
  • P-TAG is a TAG belonging to the PCell
  • S-TAG is a TAG consisting of only the SCell.
  • the fact that any serving cell belongs to an arbitrary TAG means that the backward transmission timing of the serving cell is the same as backward transmission timing of other serving cells belonging to the TAG, and it is determined whether backward synchronization is performed by the TA timer of the TAG. It means.
  • the backward transmission timing of any TAG is established by performing a random access procedure in a predetermined serving cell belonging to the TAG, and is maintained by receiving a TA command.
  • the UE drives or restarts the TA timer of the corresponding TAG.
  • the UE determines that backward transmission synchronization of the corresponding TAG is lost and does not perform backward transmission until random access is performed again.
  • the aforementioned pattern related information is not used. This is because, since the serving cells configured in the terminal are controlled by the same scheduler, it is possible for the scheduler to schedule the reverse transmission so as not to overlap each other.
  • the terminal 705 transmits a response message (RRC Connection Reconfiguration Complete) to the control message (step 725).
  • the terminal 705 establishes forward / downlink synchronization for cell b, that is, serving cell 1 (730).
  • the forward / downlink means that the base station transmits and is received by the terminal
  • the reverse / uplink means that the terminal transmits and the base station receives.
  • 'forward' and 'downlink' are used interchangeably as words having the same meaning.
  • the terms "reverse direction” and "uplink” are used interchangeably.
  • Establishing forward synchronization for an arbitrary cell means acquiring a synchronization channel of the cell to recognize a forward frame boundary (boundary).
  • the MeNB 715 may activate / deactivate MAC control element, which is a MAC layer control command for activating the SCell 1, at any time when the terminal 705 determines that the terminal 705 has completed the configuration of the SCell 1.
  • a / D MAC CE is transmitted (735).
  • the control command may consist of a bitmap.
  • the first bit may correspond to SCell 1, the second bit to SCell 2, and the nth bit to SCell n.
  • Each bit indicates activation / deactivation of a corresponding SCell.
  • the bitmap may have a size of 1 byte. Since there are seven 1 to 7 indexes of the SCell, the first LSB (Least Significant Bit) of the byte is not used, the second LSB is SCell 1, the third LSB is SCell 2, the last LSB (or Most Significant Bit, MSB) may be mapped to SCell 7.
  • the terminal 705 starts monitoring the downlink physical control channel (PDCCH) of the SCell 1 after a predetermined period has elapsed based on the time point of receiving the activation command for the SCell 1.
  • the PDCCH is forward / reverse direction. It is a channel through which transmission resource allocation information and the like are provided.
  • the terminal 705 If the SCell 1 belongs to a TAG that has already been synchronized, the terminal 705 starts forward / reverse transmission and reception from the start point of monitoring. If the SCell 1 belongs to the TAG that is not synchronized, the terminal 705 starts receiving the forward signal only at the start of monitoring and does not perform the backward signal transmission. That is, the terminal 705 receives the forward data when receiving the forward transmission resource allocation information through the PDCCH, but ignores the backward transmission resource allocation information. If the SCell 1 belongs to a TAG that is not synchronized, the UE waits for receiving a 'random access command' from a predetermined SCell belonging to the TAG through the PDCCH.
  • the random access command is to set a predetermined field of a reverse grant (assignment of a reverse transmission resource to the terminal by scheduling information transmitted through the PDCCH) to a predetermined value, and the terminal receives a predetermined preamble in a predetermined serving cell. Instruct to send.
  • a carrier indicator field (CIF) of the random access command an identifier of a serving cell to perform preamble transmission may be indicated.
  • the terminal 705 receives a random access command instructing to transmit a random access preamble through the serving cell 1.
  • the terminal 705 transmits the indicated preamble through SCell 1 and monitors the PDCCH of the PCell to receive a random access response (RAR), which is a response message to the preamble.
  • RAR random access response
  • the RAR contains a TA (Timing Advance or Timing Adjustment) command and other control information. If the cell to which the preamble is transmitted is serving cell_m, if the PCell responds to the preamble, the RAR reception is performed only in the PCell, thereby reducing the PDCCH monitoring load of the terminal 705.
  • the terminal 705 monitors the PDCCH of the PCell to receive the RAR in step 750.
  • the terminal 705 Upon receiving the valid response message for the preamble transmitted in step 745, the terminal 705 determines that the reverse signal transmission is possible after a predetermined period has elapsed based on the time point. For example, if a valid RAR is received in subframe n, backward transmission is considered to be possible starting from subframe (n + m). In the newly configured serving cell, the terminal performs forward / reverse data transmission / reception until the serving cell is released or deactivated.
  • FIG. 8 is a flowchart illustrating a process of setting an SCell, that is, serving cell_s, belonging to an SSCG.
  • FIG. 7 illustrates a process of adding carriers in the same base station
  • FIG. 8 illustrates a process of adding carriers for different base stations.
  • the MeNB 815 determines to add the SCell to the terminal 805 (820). In particular, if the terminal 805 is located in the region of the cell controlled by the base station 1 810, the MeNB 815 determines to add the cell controlled by the base station 1 810 to the SCell in step 820. The MeNB 815 then sends a control message to the base station 2 810 to request the addition of the SCell (825).
  • the control message may contain at least some of the information mentioned in Table 5 below.
  • Table 5 name Explanation SCell id information Information related to the identifier of SCells to be set in the SeNB. It consists of one or more sCellIndex-r10.
  • the MeNB decides and informs the SeNB to prevent the identifier already in use in the MeNB from being reused.
  • the SCell id used by the MeNB and the SCell id used by the drifty base station may be separately defined.
  • SCell ids 1 to 3 define MeNB in advance for SCell ids 4 to 7 to be used by SeNB.
  • TAG id information Information related to the identifier of the TAG to be set in the SeNB.
  • the MeNB decides and informs the SeNB to prevent the identifier already in use in the MeNB from being reused.
  • Reverse Scheduling Information It consists of the priority information of the logical channels set in the terminal and the logical channel group information.
  • the SeNB interprets the buffer status report information of the UE and performs backward scheduling using this information.
  • Bearer Information to be Offloaded In SeNB, it is desirable to handle services that require large data transmission and reception, such as FTP download.
  • the MeNB determines which bearer to be offloaded to the SeNB among bearers configured in the terminal, and provides information related to the bearer to be offloaded, for example, DRB identifier, PDCP configuration information, RLC configuration information, required QoS information, and the like. Deliver to SeNB. Call Admission Control Related Information
  • the MeNB provides reference information so that the SeNB can determine whether to accept or reject the SCELL addition request. For example, the required data rate, the expected uplink data amount, the estimated downlink data amount, and the like correspond.
  • the SeNB 810 determines whether to accept the request in consideration of the current load situation. If the decision is made to accept the request, the SeNB 810 generates a control message containing at least some of the information in Table 6 below and sends it to the MeNB 815 (830).
  • Table 6 name Explanation SCellToAddMod Information related to the SCells configured in the SeNB, and consists of the following information.
  • sCellIndex-r10 cellIdentification-r10, radioResourceConfigCommonSCell-r10, radioResourceConfigDedicatedSCell-r10, TAG Related Information
  • PUCCH setting information for PUCCH SCell Physical Uplink Control Channel (PUCCH) is configured in at least one SCell among SCells belonging to the SSCG.
  • backward control information such as HARQ feedback, channel status information (CSI), sounding reference signal (SRS), or scheduling request (SR) is transmitted.
  • CSI channel status information
  • SRS sounding reference signal
  • SR scheduling request
  • Identifier information and PUCCH configuration information of the PUCCH SCell are sub-information of this information.
  • Data Forwarding Information Information of a logical channel (or logical tunnel) to be used for data exchange between the MeNB and SeNB and consists of information such as a GTP (GPRS Tunnel Protocol) tunnel identifier for forward data exchange and a GTP tunnel identifier for reverse data exchange.
  • Identifier of the terminal The UE is a C-RNTI to be used in the SCell of the SSCG. This is called C-RNTI_S.
  • Bearer setup information Configuration information of the bearer to be offloaded The list of bearers accepted offload and bearer-specific configuration information are included. If the bearer settings are the same, only the list information of the accepted bearers may be included.
  • Load information Information about a recent load status of the SCell to be added that is, the serving cell_s. For example, it may be a% indicating how much the cell has been loaded in a recent past period of a predetermined length, or information such as High / Medium / Low.
  • the MeNB 815 When the MeNB 815 receives the control message, the MeNB 815 sets the current frequency band combination of the UE (ie, the combination of the frequency band of the serving cell_m and the frequency band of the serving cell_s) and the performance reported by the UE for the frequency band combination. You can compare this to determine if you need to apply the pattern.
  • the MeNB 815 compares the load information of the serving cell_s provided by the SeNB with the load of the serving cell_m set for the UE and determines a pattern to be applied. For example, if the load of the serving cell_s is more favorable than the load of the serving cell_m, the SSCG subframe selects more patterns than the MSCG subframe.
  • the MeNB delivers the determined pattern information to the SeNB using a predetermined control message.
  • the pattern information may include a bitmap 1, a bitmap 2, and an offset or a pattern index and an offset.
  • the MeNB 815 generates and transmits an RRC control message indicating the addition of the serving cell to the terminal 805 (835).
  • the RRC control message includes at least some of the information in Table 7 below, including pattern information.
  • SCellAddMod The information delivered by the SeNB is stored as it is. That is, the same information as the SCellAddMod of Table 6.
  • One SCellAddMod is stored per SCell, and the information is sub-information of SCellAddModList.
  • PUCCH setting information for PUCCH SCell The information delivered by the SeNB is stored as it is. That is, the same information as the PUCCH information for PUCCH SCell of Table 6.
  • Identifier of the terminal C-RNTI ie, C-RNTI_S, to be used by a UE in a serving cell of SSCG.
  • Offroad Bearer Information Information related to the bearer to be processed in the SeNB.
  • the terminal is information related to a bearer to be transmitted and received through the serving cell_s, and bearer configuration information is included when the bearer list and the bearer configuration are different. Pattern information Bitmap 1, bitmap 2, offset, etc.
  • Configuration information of a plurality of SCells may be stored in the RRC control message.
  • the serving cell_m and the serving cell_s may be configured together. For example, if Cell a, Cell c, Cell d, and Cell e are set to SCell for a terminal in which Cell a is PCell, the information may be arranged in various orders in the RRC control message.
  • FIG. 9 is a diagram illustrating a configuration of an RRC control message according to an embodiment of the present specification.
  • the RRC control message includes SCellToAddModList 905 and pattern information 940, SCellToAddModList 905 includes SCellToAddMod 910 for Cell b, SCellToAddMod 915 for Cell c, SCellToAddMod 920 for Cell d, SCellToAddMod 925 for Cell e is stored.
  • SCellToAddMod (910, 915, 920, 925) may or may not include specific information depending on the nature of the SCell. If the SCell belongs to the P-TAG, that is, has the same backward transmission timing as that of the PCell, the SCellToAddMod does not store information related to the TAG. For example, information related to a TAG is not stored in the SCellToAddMod 910 for Cell b.
  • SCellToAddMod (915, 920, 925) for SCells belonging to a TAG other than the remaining P-TAG includes an identifier and a TA timer value of the TAG to which the corresponding SCell belongs.
  • At least one of the serving cells_s stores information 930 related to the SSCG, for example, an identifier of the SSCG and a C-RNTI of the terminal to be used in the SSCG.
  • the information is stored in the SCellToAddMod 915 for Cell d.
  • PUCCH configuration information 935 is stored in at least one of the serving cells_s.
  • the information is stored in the SCellToAddMod 915 for Cell d.
  • SSCG related information of a SCell having the same TAG id is applied to a SCell belonging to the SSCG but having no SSCG related information.
  • SSCG related information is not stored in Cell e, but since SSCG related information is stored in Cell d having the same TAG id, the terminal determines that Cell e is also SSCG, and the SSCG identifier and C-RNTI of Cell e are Cell. Use the same value as indicated for d.
  • FIG. 10 is a diagram illustrating a configuration of an RRC control message according to another embodiment of the present specification.
  • FIG. 10 illustrates another example of storing TAG related information and SSCG related information in a separate location instead of SCellToAddMod.
  • the RRC control message includes SCellToAddModList (_1005), and SCellToAddModList (_1005) contains SCellToAddMod (_1010) for Cell 2, SCellToAddMod for Cell 3, SCellToAddMod for Cell 4, and SCellToAddMod for Cell 5.
  • SCellToAddMod contains information such as sCellIndex-r10, cellIdentification-r10, and radioResourceConfigCommonSCell-r10.
  • the TAG related information (_1015), the SSCG related information (_1020), the PUCCH configuration information of the PUCCH SCell, the pattern information _1050, and the like are individually stored.
  • the TAG related information _1015 stores a TAG identifier, identifiers of SCells constituting the TAG, and a TA timer value for each TAG. For example, a TAG with a TAG identifier of 1 is composed of SCell 2 and the information t1 is used as the TA timer (_1030), and a TAG with a TAG identifier 2 is composed of SCell 3 and SCell 4, and the value t2 is used as the TA timer.
  • Information _1035 is stored.
  • the SSCG related information _1020 stores a cell group identifier for each SSCG, identifiers of serving cells constituting the cell group, and C-RNTI information to be used in the corresponding cell group.
  • the SSCG having the cell group identifier of 1 is composed of SCell 3 and SCell 4, and information _1040 that x is used as the C-RNTI is stored.
  • Information about the MSCG is not signaled separately and is determined according to the following rules.
  • SCell Serving cells belonging to MSCG: SCell and PCell that are not serving cell_s among SCells
  • C-RNTI for use with MSCG C-RNTI currently in use with PCell
  • the SSCG related information may include the identifier of the TAG rather than the identifier of the SCell. This is possible under the premise that one TAG is not configured across multiple cell groups.
  • the SSCG configuration information _1020 may store information indicating TAG id 2 instead of information indicating SCell 3 and SCell 4, and the terminal may determine that SCell 3 and SCell 4 belonging to TAG id 2 are SSCG.
  • the PUCCH configuration information of the PUCCH SCell is composed of an SSCG identifier, an identifier of the PUCCH SCell, and PUCCH configuration information.
  • One PUCCH SCell exists per SSCG, and CSI information and HARQ feedback information about serving cells belonging to the SSCG are transmitted through the PUCCH configured in the PUCCH SCell.
  • the PUCCH SCell may be determined according to a predetermined rule. For example, the SCell corresponding to the first SCellToAddMod of the SCellToAddModList may be determined as the PUCCH SCell. Alternatively, the SCell having the highest SCell identifier or the SCell having the lowest SCell identifier may be determined as the PUCCH SCell among the SCells in which the SCellToAddMod information is stored in the RRC control message. This implicit decision method assumes that only one SSCG exists.
  • Random access configuration information of multiple serving cells may be included.
  • the UE should be able to perform random access in at least one serving cell among the serving cells belonging to the TAG. In order to perform random access in any serving cell, random access configuration information of the serving cell is required.
  • a terminal having a plurality of serving cells configured therein has random access configuration information as follows.
  • Random access configuration information of the PCell Information obtained by the terminal through system information (SIB 2) of the PCell, and is applied when the terminal performs random access in the PCell.
  • SIB 2 system information
  • Random access setting information of a predetermined SCell Information applied when the terminal performs random access in the SCell, and is stored in radioResourceConfigCommonSCell-r10 and radioResourceConfigDedicatedSCell-r10 of the corresponding SCell. That is, it is delivered to the terminal through a dedicated RRC control message.
  • the random access configuration information includes prach-ConfigIndex-r10, which is information on a physical random access channel (PRACH) resource set in a corresponding serving cell.
  • the random access process includes an operation in which the terminal transmits a preamble and the base station transmits an RAR to the terminal.
  • prach-ConfigIndex-r10 is information for specifying a PRACH resource through which the UE transmits a preamble.
  • the information specifies a subframe in which the PRACH is set.
  • the PRACH is set to one of six frequency resources, the information specifies both the subframe and the frequency resource.
  • prach-ConfigIndex-r10 is an integer between 0 and 63, and the PRACH each index specifies is described in section 5.7 of Specification 36.211.
  • step 840 the terminal 805 transmits a response message (RRC connection reconfiguration complete message) to the serving base station 815 and establishes forward synchronization with newly established SCells in step 845.
  • a response message RRC connection reconfiguration complete message
  • the terminal 805 obtains an SFN (System Frame Number) of the PUCCH SCell among the newly set SCells (850).
  • SFN acquisition is achieved in the process of receiving system information called MIB (Master Information Block).
  • MIB Master Information Block
  • SFN is an integer between 0 and 1023, increasing by 1 every 10 ms.
  • the terminal 805 determines the PUCCH transmission time point of the PUCCH SCell using the SFN and the PUCCH configuration information.
  • the SeNB 810 receives the forward data from the serving base station 815 or, upon receiving a predetermined control message instructing to activate the SCell, begins the procedure of activating the SCells (855).
  • the SeNB 810 may transmit a control message (eg, A / D MAC CE) to the terminal 805 indicating to activate SCell 3, for example, in step 860.
  • a control message eg, A / D MAC CE
  • the terminal 805 activates the SCell in subframe n + m1 when the MAC CE is received in subframe n.
  • the terminal 805 monitors the PDCCH of the SCell, but ignores the reception of the forward / reverse resource allocation signal.
  • the SeNB 810 transmits a random access command to the terminal 805 so that the terminal 805 establishes reverse synchronization of the PUCCH SCell (865).
  • the terminal 805 initiates a random access procedure in the PUCCH SCell using the dedicated preamble indicated by the command. That is, the terminal 805 transmits a preamble in the SCell (870) and monitors the PDCCH to receive the RAR, which is a response message.
  • the terminal 805 transmits the preamble in the MSCG, the RAR is transmitted through the PCell.
  • the terminal 805 monitors the PDCCH of the SCell or the PUCCH SCell that transmitted the preamble in order to receive the RAR. This is because additional information exchange between the SeNB 810 and the serving base station 815 is required to process the RAR in the PCell.
  • the RAR may be received through, for example, C-RNTI_s of the terminal 805. This is because C-RNTI_s has already been allocated to the UE 805, and since there is no possibility of malfunction due to collision since the dedicated preamble is used (the base station recognizes that a UE has transmitted a preamble when receiving the dedicated preamble. It knows which UE should send the RAR.) Because it is more efficient to send and receive the response message using C-RNTI_s.
  • the terminal 805 adjusts the backward transmission timing of the PUCCH SCell and the TAG to which the PUCCH SCell belongs by applying a TA command of the response message and at a predetermined time.
  • the predetermined time point may be a subframe (n + m2) when a valid TA command or a valid random access response message is received in the subframe (n).
  • M2 is a predetermined integer.
  • the UE may perform backward transmission using a predetermined transmission resource or according to its own decision without relying on dynamic scheduling in the serving cell_s.
  • the CQI may be transmitted through a transmission resource allocated to the PUCCH in advance.
  • the terminal selects a part of transmission resources notified for preamble transmission to perform preamble transmission.
  • a SRS Sounding Reference Signal
  • the reverse transmission performed by the UE itself should also be adjusted to the pattern as described above.
  • the PUCCH transmission resource configured in the serving cell_s of the UE should be configured only in the SSCG subframe, and the PRACH preamble transmitted in the random access procedure of the serving cell_m should be transmitted only in the MSCG subframe.
  • PUCCH configuration information so that PUCCH transmission resources can be allocated to conform to a specific pattern
  • a method of defining PRACH configuration information to configure a PRACH to conform to a specific pattern can be considered.
  • this method has limitations in that PUCCH configuration information or PRACH configuration information previously defined cannot be reused, and PRACH configuration information applicable to all UEs of a cell cannot be used because patterns are different for each UE.
  • the terminal according to the embodiment of the present invention can define a pattern to be applied to the reverse transmission based on the subframe specified by the configuration information and the subframe specified by the pattern while using the existing configuration information as it is.
  • the terminal may define the intersection of the subframe specified by the configuration information and the subframe specified by the pattern as the pattern to be applied to the own uplink transmission.
  • a subframe pattern of any UE A is equal to _1105, and a subframe in which a CQI (Channel Quality Indicator) transmission resource is specified by cqi-PUCCH-ResourceIndex of the PCell is equal to _1110, the UE transmits a CQI in the PCell.
  • the subframes _1115 which are the MSCG subframe of the subframe pattern and the CQI transmission subframe of the PCell are determined as the subframes to which the CQI is transmitted.
  • the UE In determining the subframe in which the PUCCH SCell is to transmit the CQI, the UE masks the subframe in which the CQI transmission resource specified by the cqi-PUCCH-ResourceIndex of the PUCCH SCell is set to the SSCG subframe, and corresponds to both subframes. Only transmit the CQI in the PUCCH SCell.
  • the operation may correspond to other PUCCH transmission resources, for example, a Precoding Matrix Indicator (PMI), a Precoding Type Indicator (PTI), a Rank Indicator (RI), a Scheduling Request (SR) transmission resource, and an SRS transmission resource.
  • PMI Precoding Matrix Indicator
  • PTI Precoding Type Indicator
  • RI Rank Indicator
  • SR Scheduling Request
  • the transmission resources are specified by cqi-pmi-ConfigIndex, ri-ConfigIndex, sr-ConfigIndex, srs-ConfigIndex, etc., and the terminal determines the subframe to transmit the reverse signal in the PCell, cqi-pmi-ConfigIndex,
  • the subframes specified by ri-ConfigIndex, sr-ConfigIndex, and srs-ConfigIndex are respectively masked into MSCG subframes to determine the PCell subframes to which the reverse signal is to be transmitted.
  • the subframe specified by cqi-pmi-ConfigIndex, ri-ConfigIndex, sr-ConfigIndex, and srs-ConfigIndex of the PUCCH SCell is an SSCG subframe.
  • Masking may determine a PUCCH SCell subframe to transmit the reverse signal.
  • each subframe specified by the srs-ConfigIndex of the SCell if the SCell is a serving cell_m MSCG subframe, the SCell is serving In the case of cell_s, the subframe in which the SRS is to be transmitted may be determined by masking the SSCG subframe.
  • FIG. 12 is a flowchart illustrating an operation sequence of a terminal for transmitting a CQI according to an embodiment of the present invention.
  • step _1205 the UE receives cqi-PUCCH-ResourceIndex of the PCell, cqi-PUCCH-ResourceIndex of the PUCCH SCell, pattern information and the like from the base station.
  • the information may be simultaneously received through one control message or sequentially received through a separate control message.
  • step _1210 the UE determines a subframe for transmitting the PUCCH CQI of the PCell, the subframe for transmitting the PUCCH CQI of the PUCCH SCell, and the subframe pattern using the information.
  • Transmitting the PUCCH CQI means transmitting the CQI using the PUCCH transmission resource.
  • the determination operation may be performed at the same time or may be sequentially performed according to the order of receiving the related control information.
  • the UE performs a normal operation and proceeds to step _1220 when a subframe to transmit the PUCCH CQI, for example, the subframe n is imminent in step _1215.
  • step _1220 the UE determines the type of the subframe n. If the subframe n is the MSCG subframe, the process proceeds to step _1225, if the switching subframe is to step _1230, and if the SSCG subframe is to step _1235.
  • step _1225 the UE checks whether the scheduled PUCCH CQI transmission in subframe n is the PUCCH CQI transmission of the PCell. In other words, it is checked whether the subframe n is a subframe specified by cqi-PUCCH-ResourceIndex of the PCell. If the scheduled PUCCH CQI transmission in subframe n is the CQI transmission of the PCell, the process proceeds to step _1240 and, if not, to step _1230.
  • the UE proceeds to step _1230 and does not perform the scheduled PUCCH CQI transmission in subframe n, but waits until the next subframe is set in the PUCCH CQI transmission.
  • step _1235 the UE checks whether the scheduled PUCCH CQI transmission in subframe n is the PUCCH CQI transmission of the PUCCH SCell. In other words, it is checked whether the subframe n is a subframe specified by cqi-PUCCH-ResourceIndex of the PUCCH SCell.
  • step _1245 the terminal proceeds to step _1245, otherwise proceeds to step _1230.
  • step _1240 the terminal determines whether subframe n was an active time when determined in subframe [n-5]. Step _1240 is performed only when DRX is set, and the terminal without DRX is skipped to step _1240 and immediately proceeds to step _1250.
  • the DRX reduces the battery consumption of the terminal, and the terminal can monitor the PDCCH only during an active time specified by a predetermined condition.
  • CQI transmission in principle, it is desirable to transmit CQI only during Active Time. However, it may not always be possible to comply with the above principles because Active Time can be extended or terminated indefinitely.
  • the UE transmits a CQI if the subframe is an Active Time when it is determined before a predetermined period of time, and otherwise does not transmit the CQI. More specifically, when the UE determines whether to transmit CQI in subframe n, whether the subframe n is an active time in consideration of a forward assignment, a reverse grant, a DRX command, etc. received up to subframe [n-5]. It is determined whether the CQI transmission according to.
  • n is an active time
  • the terminal proceeds to step _1250, otherwise, proceeds to step _1230.
  • step _1250 the UE performs PUCCH CQI transmission in the PCell.
  • the UE waits for the next subframe after the PUCCH CQI transmission is set.
  • step _1245 when the UE considers the situation up to the subframe [n-5], if n is an active time, the terminal proceeds to step _1255, and otherwise, proceeds to step _1230.
  • step _1255 the UE performs PUCCH CQI transmission in the PUCCH SCell.
  • FIG. 13 is a flowchart illustrating an operation sequence of a terminal transmitting an SRS according to an embodiment of the present invention.
  • the terminal receives one or more srs-ConfigIndex and pattern information from the base station.
  • srs-ConfigIndex may be signaled for each serving cell.
  • the information may be simultaneously received through one control message or sequentially received through a separate control message.
  • step _1310 the UE determines a subframe for transmitting the SRS for each serving cell and determines a subframe pattern using the information.
  • the determination operation may be performed at the same time or may be sequentially performed according to the order of receiving the control information.
  • the UE performs a normal operation and proceeds to step _1320 if a subframe to transmit SRS, for example, subframe n is imminent in step _1315.
  • step _1320 the UE determines the type of subframe n. If the subframe n is the MSCG subframe, the process proceeds to step _1325, if the switching subframe is to step _1330, and if the SSCG subframe is to step _1335.
  • step _1325 the UE checks whether the scheduled SRS transmission in subframe n is configured in the serving cell_m. In other words, it is checked whether the subframe n is a subframe specified by srs-ConfigIndex of the serving cell_m. If the SRS transmission scheduled in the subframe n is the SRS transmission of the serving cell_m, the process proceeds to step _1340, and if the SRS transmission of the serving cell_s is performed, the flow proceeds to step _1330.
  • step _1330 the UE does not perform the scheduled SRS transmission in subframe n but waits until the next subframe is set in the SRS transmission.
  • step _1335 the UE checks whether the SRS transmission scheduled in subframe n is the SRS transmission of the serving cell_s. In other words, it is checked whether the subframe n is a subframe specified by srs-ConfigIndex of the serving cell_s. If the SRS transmission scheduled in the subframe n is the SRS transmission of the serving cell_s, the process proceeds to step _1345 and, if not, to step _1330.
  • step _1340 when the terminal considers the situation up to the subframe [n-5], if n is an active time, the terminal proceeds to step _1350, otherwise proceeds to step _1330.
  • step _1350 the UE performs SRS transmission in the serving cell_m. It waits for the next subframe after SRS transmission is set.
  • step _1345 the terminal proceeds to step _1355 if n is an active time, considering the situation up to subframe [n-5], otherwise proceeds to step _1330.
  • step _1355 the UE performs SRS transmission in the serving cell_s. It waits for the next subframe after SRS transmission is set.
  • FIG. 14 is a flowchart illustrating an operation sequence of a terminal that transmits a scheduling request (SR) according to an embodiment of the present invention.
  • a buffer status report (BSR) is triggered to the terminal.
  • the BSR is control information in which the UE reports the buffer status to the base station, and one of two formats, short BSR and long BSR, is selectively used.
  • the BSR reports the buffer status (BS) for at least one and up to four logical channel groups (LCGs).
  • LCGs logical channel groups
  • the short BSR is used when there is only one LCG in which data is to be transmitted, and consists of an LCG identifier and a BS.
  • the long BSR reports the buffer status of four Logical Channel Groups (LCGs) and the BSs of the LCGs are stored in the order of the LCG identifier.
  • LCGs Logical Channel Groups
  • An LCG is a collection of logical channels grouped by the control of a base station, which typically has similar logical channel priorities.
  • the buffer state of the LCG is the sum of the buffer states associated with the logical channels included in the LCG, and indicates the amount of data that can be transmitted among the data of the RLC transmit buffer, the RLC retransmission buffer, and the PDCP transmit buffer of the logical channels.
  • the BSR is triggered periodically or when a predetermined condition occurs, for example, data having a higher priority than data currently stored.
  • the former is called a periodic BSR and the latter is called a regular BSR.
  • step _1407 the UE checks whether the triggered BSR is a periodic BSR or a regular BSR. If it is a regular BSR, it proceeds to step _1410, and if it is a periodic BSR, it proceeds to step _1409.
  • the UE proceeds to step _1409 and waits until a transmission resource capable of transmitting the BSR is allocated.
  • the terminal proceeds to step _1410 and initiates a procedure for requesting transmission resource allocation for transmitting the BSR.
  • the regular BSR needs to be transmitted to the base station quickly.
  • step _1410 the UE checks whether the data triggering the regular BSR or the data having the highest priority among the data that can be transmitted at the corresponding time is data belonging to LCG_m or data belonging to LCG_s. Or, it is checked whether the data triggering the regular BSR is data belonging to LCH_m or data belonging to LCH_s.
  • LCH transmitted / received in the serving cell_s is referred to as LCH_s and LCH transmitted / received in the serving cell_m as LCH_m
  • LCG_m is a logical channel group composed of only LCH_m
  • LCG_s is a logical channel group composed of only LCH_s.
  • step _1415 If the data triggering the regular BSR is data belonging to LCH_m, the process proceeds to step _1415, and if it belongs to LCH_s, the process proceeds to step _1430. Alternatively, if the data triggering the regular BSR belongs to LCG_m, the process proceeds to step _1415, and if it belongs to LCG_s, the process proceeds to step _1430.
  • step _1415 the UE checks whether an SR is configured in the PUCCH transmission resource of the PCell. Or check that sr-ConfigIndex is signaled for the PCell and not yet released. If the SR is set, the process proceeds to step _1420. If the SR is not set, the process proceeds to step _1427.
  • step _1420 the UE masks subframes specified by the sr-ConfigIndex of the PCell to the MSCG subframe to determine subframes capable of SR transmission.
  • step _1425 the UE selects one of the identified subframes and transmits the SR.
  • the terminal may select the subframe closest to the corresponding time point, for example.
  • the UE which proceeds to step _1427, triggers random access in the PCell.
  • step _1430 the UE checks whether an SR is set in the PUCCH transmission resource of the PUCCH SCell. Or, the UE checks whether sr-ConfigIndex is signaled and not released yet for the PUCCH SCell. If the SR is set, the process proceeds to step _1435. If the SR is not set, the process proceeds to step _1445.
  • step _1435 the UE masks the subframes specified by sr-ConfigIndex of the PUCCH SCell to the SSCG subframe and determines subframes capable of SR transmission.
  • step 1440 the UE selects one of the identified subframes and transmits the SR.
  • the terminal may select the subframe closest to the corresponding time point, for example.
  • the UE that proceeds to step _1445 triggers random access in the PUCCH SCell.
  • 15 is a flowchart illustrating an operation sequence of a terminal performing a random access procedure according to an embodiment of the present invention.
  • a random access is triggered to the terminal. Random access can be triggered for a variety of reasons. For example, when triggered by the target cell during handover, when triggered by an indication of a base station, or when triggered to transmit a BSR.
  • step _1510 the UE checks whether the random access is triggered by the PCell or the SCell. If it is triggered in the PCell, it proceeds to step _1520, if it is triggered in the SCell to step _1515.
  • step _1515 the UE checks whether the SCell triggered by random access is serving cell_m or serving cell_s. In case of serving cell_m, the process proceeds to step _1520, and in case of serving cell_s, the process proceeds to step _1525.
  • the terminal proceeds to step _1520 if the random access is triggered, if triggered by the PCell or the SCell of the MSCG, and proceeds to step _1525 if triggered by the SCell of the SSCG.
  • the normalization is performed by the LCH_m data of the UE where the PUCCH SR is not configured.
  • the BSR is triggered, when the RRC connection reestablishment process is triggered, or when the PUCCH SR transmission of the PCell fails.
  • the base station when random access is triggered in the SCell of the MSCG, the base station instructs the random access in the SCell.
  • the random access when the random access is triggered in the SCell of the SSCG, when the base station instructs to perform random access in the SCell, a case where the regular BSR is triggered by the LCH_s data, and the like.
  • the UE proceeding to step _1520 masks the subframe specified by the prach-ConfigIndex of the serving cell, that is, the PCell or the SCell of the MSCG, into the MSCG subframe, that is, the subframe specified by the prach-ConfigIndex and is also an MSCG subframe.
  • One subframe is determined to be a subframe capable of preamble transmission.
  • the prach-ConfigIndex of the PCell is obtained through SIB2 of the PCell
  • the prach-ConfigIndex of the SCell of the MSCG is obtained through a predetermined dedicated RRC control message.
  • the UE proceeding to step _1525 masks the subframe specified by the prach-ConfigIndex of the SCell of the corresponding serving cell, that is, the SSCG subframe, that is, the subframe specified by the prach-ConfigIndex and is also a SSCG subframe.
  • the frames are determined to be subframes capable of preamble transmission.
  • the prach-ConfigIndex of the SCell of the SSCG is obtained through a predetermined dedicated RRC control message.
  • step _1530 the UE selects one of the subframes capable of preamble transmission and transmits the preamble.
  • the terminal may select, for example, the closest subframe among the subframes.
  • the terminal transmits the preamble until a valid random access response message is received according to a predetermined rule.
  • the UE receives a random access response message.
  • the random access response message stores uplink transmission resource allocation information (Uplink Grant, UL grant), transmission output control command information (Transmission Power Control (TPC)), uplink transmission time adjustment information (Timing Advance, TA), and the like.
  • TPC Transmission Power Control
  • Timing Advance TA
  • the transmit power is adjusted according to the transmit power control command and the reverse transmit timing is adjusted according to the TA.
  • step _1540 the UE determines whether the random access is a contention free random access (CFRA) or a contention random access.
  • CFRA contention free random access
  • the non-competitive random access means a random access in which a preamble (dedicated preamble) indicated by the base station is used, and when the base station receives the preamble, the base station can know who the terminal has transmitted the preamble.
  • the competitive random access refers to a random access using a preamble (random preamble, random preamble) selected by the terminal
  • the base station can not know who is the terminal that transmitted the preamble only by receiving the preamble, the process of competition cancellation Msg 3 needs to be transmitted and received.
  • the base station allocates the UL grant in the random access response message, the UL grant to match the sub-frame pattern. In other words, if the contention-free random access in the PCell or the contention-free random access in the SCell of the MSCG, the UL grant is allocated so that the PUSCH transmission triggered by the UL grant proceeds in the MSCG subframe.
  • the UL grant is allocated so that the PUSCH transmission triggered by the UL grant is performed in the SSCG subframe.
  • the UE performs PUSCH transmission for the UL grant according to the subframe pattern. In case of contention-based random access, the terminal proceeds to step _1550.
  • the terminal ignores the subframe pattern for a predetermined period of time until, for example, the PUSCH transmission triggered by the UL grant of the random access response message is completed, and resumes the application of the subframe pattern after the predetermined period has elapsed. . If the uplink transmissions of the SSCG and the MSCG collide during the period of ignoring the subframe pattern, the PUSCH transmission triggered by the UL grant of the RAR is performed, and the other uplink transmission is abandoned.
  • the UE performs contention random access in the PCell, the UE performs PUSCH transmission in the subframe even though the PUSCH transmission triggered by the UL grant of the random access response message should occur in the SSCG subframe or the switching subframe. . If the PSUCH transmission overlaps with the backward transmission of the SSCG, the PUSCH transmission is performed and other backward transmission of the SSCG is abandoned.
  • FIG. 16 is a flowchart illustrating an operation sequence of a terminal and a base station in which a terminal reports terminal performance to a base station and the base station sets a CA between base stations according to an embodiment of the present invention.
  • the terminal establishes an RRC connection with the MeNB (_1616).
  • the MeNB transmits a control message called UE CAPABILITY ENQUIRY to the UE in order to obtain performance information of the UE (_1617).
  • the message instructs the terminal to report the performance, and may request performance information on a specific radio access technology (RAT) of the terminal using a parameter called a RAT type.
  • RAT radio access technology
  • the RAT-Type is set to ETRA (Evolved Universal Terrestrial Radio Access).
  • the base station may also request UMTS-related performance information of the terminal by adding UTRA to the RAT-Type in preparation for future handover if there is another wireless network, for example, a UMTS network.
  • the terminal When the UE receives the UE CAPABILITY ENQUIRY control message, the terminal generates UE capability information (UE CAPABILITY INFORMATION) containing its own performance information on the radio technology indicated by the RAT Type and transmits it to the base station (_1619).
  • the control message may store one or more band combination information for each band combination supported by the terminal.
  • the band combination information is information indicating which CA combination the terminal supports, and the base station may set an appropriate CA to the terminal using the information.
  • the performance information of the terminal includes information on band combinations supported by the terminal (hereinafter, SBC _1705).
  • SBC consists of one or more band combination parameters (BCP, _1710, _1715, _1720, _1725), and BCP is information on each band combination supported by the terminal.
  • a BCP consists of one or more band parameters (BPs).
  • the BP is composed of information indicating a band (FreqBandIndicator), a forward band parameter (BPDL below bandParametersDL) and a reverse band parameter (BPUL below bandParametersUL).
  • BPDL and BPUL again consist of a bandwidth class (bandwidthClass) indicating the number of serving cells supported in a corresponding band and antenna performance information.
  • Bandwidth class A represents the configurable performance of one serving cell up to 20 MHz total bandwidth
  • bandwidth class B represents the configurable performance of two serving cells up to 20 MHz total bandwidth
  • bandwidth class C represents the serving cell 2 It is configurable and has a total performance of up to 40 MHz.
  • the terminal In order to support CA between base stations, the terminal should be able to perform at least the following functions.
  • the terminal in reporting the performance of CA between base stations, the terminal may first indicate whether the terminal supports CA between base stations and report detailed performance for each band combination only if the terminal supports CA. .
  • the terminal displays the following information using 1 bit or information (_1735) coded in another manner of ASN.1 in the terminal capability information message.
  • PUCCH can be transmitted in two or more serving cells in at least one band combination among the band combinations supported by the UE
  • 'supporting CA between base stations', 'supporting two or more serving cell groups', and 'capable of transmitting PUCCH in two or more serving cells' have similar meanings. It can be used interchangeably.
  • multipleSCGcapability (_1735) is 'Yes' or when the terminal supports CA between base stations, one bit information (_1740 to _1760, multipleSCGsupported) per band combination or per BCP is included.
  • the 1 bit information may indicate Yes or no or may indicate whether the corresponding multipleSCGsupport exists.
  • multipleSCGsupported is information indicating whether a CA between base stations is supported or two or more serving cell groups are supported in the corresponding band combination.
  • the band combination consists of one band parameter (that is, one band entry) and there are two or more serving cells in the reverse direction for the band combination (i.e. the reverse bandwidth class is not A) Case, or if the reverse bandwidth class is B or C or higher), if multipleSCGsupported is Yes, it means that the base station CA is supported for the serving cells of the corresponding band entry.
  • the serving cells may be configured as two or more serving cell groups in the band, which means that the PUCCH may be configured in the serving cells (or the serving cells may be PCells or PUCCH SCells). do).
  • _1710 is a non-CA in which only one serving cell is set in both the forward and reverse directions
  • _1715 is a forward CA in which two serving cells are configured only in the forward direction.
  • multipleSCGsupported (_1750) is yes or present, two serving cells may be configured in band x, the serving cells may be configured as a separate serving cell group, and PUCCH may be configured for all the serving cells. do.
  • the band combination consists of one band parameter (that is, one band entry), and there is only one serving cell in the reverse direction for the band combination (ie, the reverse bandwidth class is A). Regardless of the value indicated by multipleSCGsupported, the UE does not support CA between base stations for the band combination. For example, in the band combinations _1710 and _1715, CAs between base stations are not supported regardless of the values indicated by _1740 and _1745.
  • the band combination consists of two or more band parameters and two or more band entries contain BPUL (that is, the reverse is set for two or more band entries, or two or more servings). If the reverse direction can be configured in the cell), if multipleSCGsupported is Yes, the UE supports CA between base stations for the band combination and configures component carriers (or serving cells) belonging to the same band as one serving cell group.
  • PUCCH may be configured in one component carrier among component carriers belonging to the same band, and at least one serving cell per band entry may be configured as a PCell or a PUCCH SCell.
  • _1730 corresponds to this, and _1760 indicates whether one serving cell group may be configured in band x, another serving cell group may be configured in band y, and whether the serving cells may be configured as PCell or PUCCH SCell. Indicates.
  • the terminal does not support CA between base stations for the band combination.
  • the band combination _1725 does not support CA between base stations regardless of the value indicated by _1755.
  • Pattern performance information (_1765, _1770) is composed of the following three pieces of sub-information.
  • patternCapabilityinfo1 pattern capability information 1
  • uplink TDM When uplink TDM is required, both downlink TDM necessary indication information and switching subframe need indication information are required.
  • Uplink TDM is required when the UE applies two Tx devices (2Rx / 2Tx B) or only one Tx device for a corresponding band combination. If two Tx devices are applied, the switching time is reported to be unnecessary because the time required for RF reset is extremely short. If one Tx device is applied, the time required for RF reset is considerable, and thus reporting that a switching subframe is required. If only one Rx device is applied to the SBC, downlink TDM is also reported as necessary. Therefore, when reporting that uplink TDM is necessary, downlink TDM necessary indication information and switching subframe need indication information should also be reported.
  • the uplink TDM required indication information, the downlink TDM required indication information, and the switching subframe required indication information are all included in the pattern capability information 2 (patternCapabilityinfo2).
  • the terminal reports patternCapabilityinfo1 or patternCapabilityinfo2 for a band combination that meets the following conditions.
  • a combination of bands with one band entry and a reverse bandwidth class of B or higher i.e., a combination of bands where the reverse bandwidth class is not A
  • the band combination _1720 and the band combination _1730 correspond to this, and patternCapabilityinfo (_1765, _1770) is stored for each.
  • the terminal may not store patternCapabilityinfo for a band combination that does not satisfy the above condition, or may store patternCapabilityinfo1 (ie, patternCapabilityInfo indicating that uplink TDM is not required).
  • the terminal stores the information in a control message called UE CAPABILITY INFORMATION and transmits the information to the base station. If multipleSCGcapability (_1735) is stored in the message, multipleSCGsupported (_1740 to _1760) information is stored in the same order as the band combination for all band combinations, and patternCapabilityinfo (_1765, _1770) for band combinations that satisfy a predetermined condition. This is accommodated. If multipleSCGcapbility is not stored, multipleSCGsupported and patternCapabilityinfo are not stored.
  • the base station when the base station receives the UE CAPABILITY INFORAMTION information containing the information, the base station determines whether to establish a CA or a CA based on the performance information. You can decide whether to set up your CA, etc.
  • Steps _1620, _1625, _1630, _1633, _1635 and _1640 of FIG. 16 may correspond to steps 820, 825, 830, 833, 835 and 840 of FIG. 8, respectively.
  • step _1645 and step _1650 the UE performs backward transmission for the serving cells controlled by the MeNB in the MSCG subframe and performs backward transmission for the serving cells controlled by the SeNB in the SSCG subframe.
  • the MSCG subframe and the SSCG subframe may partially overlap.
  • base station 1 is MeNB and base station 2 is SeNB
  • MSCG subframe _1805 and SSCG subframe _1810 overlap each other.
  • the UE punctures the last portion of the preceding subframe _1805 by a predetermined time period, for example, one symbol length (_1815 one OFDM symbol duration), and performs backward transmission.
  • the reason for puncturing by one symbol length is because a format that punctures by one symbol length is already defined in the standard among PUSCH transmission formats.
  • the terminal When the terminal fails in random access, according to the prior art, the terminal terminates the random access procedure and does not perform additional operations.
  • the random access since the random access is intended to convey important information to the base station, it may be desirable to continue the random access process before the RRC layer explicitly commands the end of the random access process.
  • the preamble transmission output may already be quite high because of the power ramping applied to the preamble, and continuous random preamble transmission may cause significant uplink interference to neighboring cells.
  • random access failures are classified into primary failures and secondary failures.
  • the UE continues preamble transmission even if the random access fails first. At this time, by adjusting the preamble transmission frequency before and after the first failure of the random access, the uplink interference is maintained at an appropriate level even after the first failure of the random access.
  • the first failure of random access refers to a case in which the random access is not successful even though the UE transmits the random access preamble a predetermined number of times.
  • Secondary failure of random access refers to a case where random access does not succeed until the upper layer instructs to stop random access.
  • step _2205 random access is triggered for any reason. Random access is triggered for a variety of reasons, and can be triggered at the PCell or at the SCell.
  • the UE selects a random access resource.
  • the random access resource refers to an access preamble, a PRACH resource to which the preamble is transmitted, and a subframe in which the PRACH resource is set.
  • the base station may specify a random access resource to the terminal. If the base station has assigned a non-zero preamble index and a PRACH mask to the terminal, the terminal selects a preamble (dedicated preamble) specified by the preamble index using the PRACH resource of the subframe specified by the PRACH mask.
  • the terminal selects a preamble to transmit by applying a predetermined rule (random preamble).
  • a predetermined rule random preamble.
  • the preamble index, the PRACH mask index, a rule for selecting a random preamble, and the like are described in the standard 36.321.
  • the first delay is a delay related to the PRACH configuration of the serving cell in which random access is being performed and is a maximum value rather than a fixed value. More specifically, the first delay is defined as a distance in time between when a random access preamble is selected and the closest subframe that can transmit the random access preamble. Different first delays may be applied for the PCell and the SCell.
  • step _2213 the UE transmits a preamble.
  • step _2215 the UE checks whether a valid RAR is received. More specifically, the terminal determines whether a RAR satisfying a predetermined condition is received in a predetermined serving cell during a period called ra-Window. More specifically, if a RAR addressed to a predetermined RA-RNTI has been received during the ra-Window, and the RAR includes a preamble identifier specifying a preamble transmitted by the terminal, the terminal determines that a valid RAR has been received. Proceed to step _2220. If the condition is not satisfied, the terminal proceeds to step _2240.
  • the predetermined serving cell to which the UE attempts to receive the RAR may vary according to the type of the serving cell that transmitted the preamble. If the preamble was transmitted in the PCell, the predetermined serving cell is a PCell. If the preamble has been transmitted in the SCell and the SCell is the SCell of the master serving cell group, the predetermined predetermined serving cell is the PCell. If the preamble is transmitted from the SCell and the SCell is an SCell of the slave serving cell group, the serving cell is the SCell to which the preamble is transmitted.
  • step _2220 the UE checks whether a dedicated preamble or a random preamble is transmitted. If the dedicated preamble is transmitted, the process proceeds to step _2225 and determines that the random access process is completed and ends the process. UE proceeds to step _2230 transmits message 3 according to the UL grant included in the RAR.
  • the message 3 is uplink data transmitted from the terminal to the base station for contention resolution, and the message 3 includes information for identifying the terminal, for example, C-RNTI MAC CE.
  • the UE determines the serving cell to which the message 3 is to be transmitted in consideration of the serving cell in which the RAR has transmitted the preamble, not the serving cell. For example, even if the RAR is received by the PCell, if the preamble is transmitted by the SCell, message 3 is also transmitted by the SCell.
  • step _2235 the UE checks whether contention is resolved.
  • Resolving contention means that the UE receives a downlink signal satisfying a predetermined condition before a predetermined timer called mac-ContentionResolutionTimer expires.
  • the downlink signal may be, for example, a UL grant or DL assignment addressed with a predetermined RRC control message or a C-RNTI.
  • the competition resolution process is described in Specification 36.321.
  • the terminal proceeds to step _2225 and determines that the random access process has been completed successfully and ends the process.
  • step _2240 If the competition is not resolved, the terminal proceeds to step _2240.
  • step _2240 the UE checks whether PREAMBLE_TRANSMISSION_COUNTER is equal to the sum of 1 to preambleTransMax.
  • PREAMBLE_TRANSMISSION_COUNTER is a variable that is initialized to 0 when a random access process is triggered, and then increments by 1 each time the preamble is transmitted. The above process is for determining whether a random access problem is reported to a higher layer device.
  • preambleTransMax is a value that the base station signals to the terminal. If the random access process is triggered in the PCell, the preambleTransMax acquired through the system information of the PCell is applied.
  • the preambleTransMax notified by the base station through a dedicated RRC message is applied. If the condition is not satisfied, the terminal branches to step _2257 and if the condition is met, the terminal proceeds to step _2250 and checks whether the serving cell transmitting the preamble is a PCell or a SCell. If PCell, go to step _2255, if SCell, go to step _2257. In step _2255, the UE reports that a random access problem has occurred in the RRC layer device. The RRC layer device may reset the MAC layer device so that the terminal stops random access according to the situation.
  • step _2257 the UE checks whether PREAMBLE_TRANSMISSION_COUNTER is greater than the sum of 1 in preambleTransMax to determine whether the random access primary failure has occurred, and if so, proceeds to step _2260 and otherwise returns to step _2210.
  • step _2260 the UE waits for a second delay to adjust the preamble transmission period, and then proceeds to step _2210 to select a random access resource.
  • the second delay is a value larger than the first delay and may be set differently according to the type of serving cell. Since PCell has a high probability of transmitting more important information through random access, a relatively short value of, for example, about 100 ms can be applied as the second delay.
  • the second delay of the SCell may be set to infinity such that the preamble transmission may be stopped after the random access primary failure in the SCell.
  • the UE applies the first period to the preamble transmission / retransmission before the predetermined condition is satisfied, that is, when the PREAMBLE_TRANSMISSION_COUNTER is equal to or less than the sum of 1 to preambleTransMax, and the PREAMBLE_TRANSMISSION_COUNTER adds 1 to the preambleTransMax. If greater than the second period applies to preamble transmission / retransmission.
  • the first period is determined by the first delay
  • the second period is determined by the sum of the second delay and the first delay.
  • the first delay and the second delay may be set differently for the PCell and the SCell, the first delay may be defined as a maximum value rather than a fixed value, and the second delay may be defined as a fixed value.
  • the terminal continuously measures channel conditions of the serving cell and neighbor cells according to the instructions of the base station, compares the measurement results, and reports the measurement results to the base station when predetermined conditions are satisfied.
  • the base station sets the measurement to the terminal using a predetermined RRC control message as needed.
  • the measurement configuration includes a measurement object (measurement object, measObject), a report configuration (report configuration, reportConfig), and a measurement indicator (measurement ID, measId).
  • the measurement target is a frequency at which the terminal performs measurement, and the base station may set one or more measurement targets to the terminal.
  • Each measurement object is assigned an identifier.
  • Report settings are related to measurement reporting triggers, and are classified into event triggered reporting and periodic reporting. Event-triggered reporting is broken down into six reporting events, for example:
  • A1 The measurement result of the serving cell is more than a predetermined standard
  • A2 The measurement result of the serving cell is below a predetermined standard
  • A3 The measurement result of the neighboring cell is more than a predetermined offset better than the measurement result of the PCell.
  • A4 The measurement result of the surrounding cell is more than a predetermined standard
  • A5 The measurement result of the PCell is less than or equal to 1 and the measurement result of the neighboring cells is greater than or equal to 2.
  • A6 The measurement result of neighboring cell is more than offset better than that of SCell
  • a plurality of measurements can be set in the terminal, and one measurement is composed of MeasId, measObjectId, and reportConfigId.
  • two measurement targets specified by measObjectId 1 (_2305) and measObjectId 2 (_2310) are set in an arbitrary terminal, and indicate center frequency 1 and center frequency 2, respectively.
  • the base station sets specific measurements using the measurement target setting information and the report setting information. That is, when MeasId 1 (_2325) is associated with measObjectId 1 and reportConfigId 2, the MeaseId 1 refers to a measurement for reporting a measurement result when eventA3 is satisfied for the center frequency 2.
  • the terminal and the base station may establish various measurements by variously associating a measurement object with a report configuration.
  • the content of this measurement is described in more detail in Specification 36.331.
  • the terminal compares the measurement result of the serving cell with a predetermined reference (A1 and A2), compares the measurement result of the neighboring cell with a predetermined criterion (A4), or compares the measurement result of the serving cell with the measurement result of the neighboring cell (A3 and A5) It may be determined whether to trigger a measurement report message. If an SCell is configured in the terminal, whether the SCell is treated as a serving cell or a neighbor cell should be clearly defined.
  • the present invention provides a method and apparatus for treating a SCell as a serving cell and also as a neighboring cell in some cases without fixing the serving cell or the neighboring cell.
  • step _2405 an arbitrary measurement is set in the terminal, and one or more SCells are set in the terminal.
  • the measurement it means that the MeasId associated with measObjectId and reportConfigId has been set.
  • the terminal checks the reportConfig of the measurement to determine whether to treat the SCell as a serving cell or a neighbor cell in the measurement. If reportConfig is about periodic reporting, it proceeds to step _2413, A1 or A2 to _2410, A3, A4 or A5 to _2430, and A6 to _2445.
  • the terminal treats all configured SCells as serving cells (_2413).
  • the UE includes measurement results for all the SCells set in the measurement result report (measResult) that is periodically triggered.
  • step _2410 the UE checks whether an SCell having the same center frequency (or carrier frequency) as the measurement target associated with the measurement is set. For example, when the measurement target is f1, it is checked whether an SCell having a center frequency of f1 exists. If there is an SCell that satisfies the above condition, the process proceeds to step _2415 and considers the SCell as a serving cell.
  • the measurement result report including the measurement result of the SCell is triggered and reported to the base station.
  • step _2420 If there is no SCell that satisfies the above condition, the process proceeds to step _2420 and the SCell is not treated as a serving cell. That is, the measurement result report is not triggered based on the measurement result of the SCell. However, if a measurement result report is triggered for other reasons, the measurement results of SCells are included in the measurement result report.
  • step _2430 the UE checks whether an SCell having the same center frequency as the measurement target associated with the measurement is set. If the SCell that satisfies the condition is set, step _2435. If the SCell that satisfies the condition is not set, the process proceeds to step _2440. In step _2435, the UE treats the SCell as a neighbor cell.
  • the state in which the measurement result of the SCell is better than the measurement result of the PCell by a predetermined offset is maintained for a predetermined period or more (for A3), or the state in which the measurement result of the SCell is better than the predetermined reference value is more than the predetermined period
  • the measurement result of the SCell is included. Trigger measurement report and report to base station. If there is no SCell that satisfies the above condition, the process proceeds to step _2440 and the SCell is not treated as a neighbor cell. That is, the measurement result report is not triggered based on the measurement result of the SCell. However, if a measurement result report is triggered for other reasons, the measurement results of SCells are included in the measurement result report.
  • the terminal proceeds to step _2445 and does not consider all SCells as neighbor cells. That is, it does not trigger the measurement result report based on the SCell measurement result. However, if a measurement result report is triggered for other reasons, the measurement results of SCells are included in the measurement result report.
  • the reason why the handling or the handling of the SCell as the serving cell or the neighboring cell is not performed is to trigger or not trigger the measurement result report based on the SCell measurement result according to the purpose of setting the event.
  • the terminal located in the cell change may experience a problem of lack of reverse transmission output.
  • the UE may be configured with a TTI bundling function for repeatedly transmitting data (hereinafter, referred to as bundle transmission) over 4 transmission time intervals (TTIs).
  • TTI bundling function is not used for a terminal in which a plurality of serving cells are configured. This is due to the recognition that carrier aggregation itself is a technique that can be used when the reverse transmission power is sufficient.
  • the carrier aggregation itself is a technique that can be used when the reverse transmission power is sufficient.
  • the carrier aggregation between base stations while the terminal located in the cell change performs a normal operation with the small cell, it is possible to increase communication efficiency by applying TTI bundling in the macro cell.
  • the UE may initiate a random access procedure while performing a TTI bundling operation. In the random access process, the UE transmits message 3. If the retransmission of the message 3 and the new TTI bundling transmission overlap on the time axis, the UE processes the new transmission prior to the retransmission according to the general rule. In other words, abandon message 3 retransmission and start a new transmission.
  • the terminal may transmit a buffer status report to the base station through message 3 of the random access procedure. If the UE abandons the message 3 transmission, the buffer status report message may be lost, which may seriously affect scheduling.
  • 26 illustrates the operation of the terminal. 26 is a flowchart illustrating an operation sequence of a terminal performing a TTI bundling operation.
  • TTI bundling is configured for the UE.
  • the UE receives an RRCConnectionReconfiguration message in which TTIbundling is set to True
  • the UE receives through the PDCCH until TTI bundling is released, that is, until an RRCConnectionReconfiguration message in which TTIbunling is set to False is received.
  • the bundle transmission is applied to the reverse grant.
  • step _2605 the UE recognizes that initial transmission and retransmission will collide on the time axis in the near future. For example, this is the case where the initial transmission is indicated for a subframe that is already scheduled for retransmission.
  • step _2610 the UE checks whether the collision occurs in the same HARQ process.
  • this is the case where the initial transmission is indicated for the HARQ process currently undergoing retransmission.
  • Case 1 is an example for non-bundling transmission, but the same case may occur for bundle transmission. If the collision occurred in the same process, the terminal proceeds to step _2625. If the collision does not occur in the same process, the terminal proceeds to step _2615. In step _2615, the UE checks whether the collision is due to bundle initial transmission and bundle retransmission.
  • this is a case where a bundle initial transmission is indicated for a subframe partially overlapping with a subframe in which bundle retransmission is to be performed.
  • the base station performs scheduling so that such a situation does not occur.
  • the current retransmission is caused by noise (e.g., the base station does not instruct transmission, but the terminal misunderstands that transmission is indicated due to the residual error of the CRC)
  • the situation may occur.
  • step _2620 the UE checks whether the initial transmission is a bundle transmission and the retransmission is a message 3 transmission (or whether the MAC PDU to be retransmitted is obtained from the message 3 buffer). If yes, go to step _2630; otherwise, if the new transmission is a message 3 transmission and the retransmission is a bundle transmission, go to step _2625. In step _2625, the UE performs a new transmission.
  • the terminal discards data of the HARQ process without performing bundle transmission in the remaining subframes (that is, stops the current bundle transmission of the HARQ process) in order to reduce battery consumption.
  • transmission may be performed in the subframes _2510 and _2515 before and after the message 3 transmission, and may be performed in the remaining subframes _2505.
  • the UE preferentially performs message 3 retransmission.
  • the HARQ process data is discarded without performing bundle transmission in order to reduce battery consumption of the UE.
  • transmission may be performed in subframes _2520 and _2525 before and after message 3 transmission, and may be performed in the remaining subframes _2530.
  • step _2615 the transmission that is already in progress may be performed first rather than the initial transmission. That is, if a collision between the bundle transmission and the bundle transmission occurs in step _2615, it may branch to step _2630.
  • the base station performs scheduling so that collisions do not occur between bundle transmissions, so that probability of subsequent transmissions are caused by noise rather than probability that the transmission already in progress is caused by noise. Because it is high. For example, if the priority is already in progress, if the first grant is not caused by noise after TTI bundling is set, then all grants caused by noise can be filtered out. On the other hand, if a new transmission is prioritized, it is affected by all noise grants that occur after TTI bundling is established.
  • Another embodiment of the present invention provides a method for a UE to perform random access in a PCell, a PSCell, or a SCell.
  • the UE determines in which serving cell to perform random access.
  • Table 8 Occation Serving Cells with Random Access RRC connection settings PCell Regular BSR Trigger by MCG Bearer Data PCell Regular BSR Trigger on Data of SCG Bearer PSCell Receive PDCCH order Serving Cell Received PDCCH Order Handover PCell Add or change SeNB / SCG PSCell Reconfiguration related to SeNB / SCG PSCell
  • the UE When the regular BSR is triggered by the data of the SCG bearer, the UE triggers random access in the PSCell to transmit to the SeNB of the regular BSR.
  • SeNB / SCG add / change, reset associated with SeNB / SCG is triggered by the reception of the RRC control message.
  • a handover complete control message is generated on the uplink, and the control message triggers a regular BSR based on data in the MCG bearer, thereby triggering a random access in the PCell.
  • the response RRC control message does not trigger random access in the PSCell. Therefore, the control information to trigger the random access in the PSCell is included in the associated RRC control message itself. If the SeNB is added or changed, some of the bearers configured in the terminal are reset to the SCG bearer, and if uplink data that can be transmitted to the SCG bearer is stored, the regular BSR by the SCG bearer may be triggered. . Therefore, when the PSCell random access by the RRC control message is already in progress, PSCell random access by the regular BSR may be triggered.
  • the completion of the SeNB addition / change may be delayed. Therefore, if the PSCell random access by the RRC control message is already in progress, it is preferable to complete the random access currently in progress first.
  • FIGS. 27, 28A and 28B Terminal operations related to the above are illustrated in FIGS. 27, 28A and 28B.
  • 27 is a diagram illustrating an operation of a terminal receiving an RRC control message.
  • step _2705 the UE receives an RRC control message.
  • step _2710 the UE checks whether the RRC control message is a message indicating handover, and if the message indicates handover, proceeds to step _2715, and if not, the terminal proceeds to step _2725.
  • the control message including MobilityControlInfo (see standard 36.331) is a control message indicating handover.
  • step _2715 the terminal generates a response message to the control message.
  • the response message is an RRC control message. Since the RRC control message has the highest priority and is always transmitted and received only through the MCG, the regular BSR for the MCG is triggered by the response control message.
  • Normal BSR for MCG means normal BSR triggered by data to be transmitted through MCG or regular BSR triggered by MAC device configured for MCG or regular BSR triggered by MeGB or LCG_m triggered by LCG_m. .
  • step _2720 the UE performs a handover to transmit the regular BSR, and then triggers random access in the PCell. That is, a process of transmitting a random preamble in a predetermined time / frequency resource of the PCell and receiving a random access response message through the downlink of the PCell is initiated.
  • step _2725 the UE checks whether the following predetermined information is included in the RRC control message.
  • Control information for initially setting up the SeNB information related to the eNB, for example, MAC setting information to be used for the SeNB, and the like.
  • Control information for initially adding an SCG serving cell Control information for setting at least one SCG SCell to a terminal in which the SCG serving cell is not configured, information related to the configured SCell, and information indicating that the SCell belongs to the SCG. This is the case.
  • Control information indicating change of SeNB Information indicating release of all existing SCG serving cells and indication of setting of new SCG serving cells corresponds to this.
  • Information indicating random access initiation may be 1 bit information.
  • step _2730 If the predetermined information is included in the RRC control message, the process proceeds to step _2730 and, if not included, to step _2740.
  • step _2730 the UE triggers a random access in a predetermined cell of the SCG serving cells, that is, the PSCell. That is, a process of transmitting a random preamble in a predetermined time / frequency resource of the PSCell and receiving a random access response message through the downlink of the PSCell is initiated.
  • the new random access is not triggered due to the regular BSR for the SCG. That is, when the random access commanded by the RRC is in progress in the PSCell, the random access trigger due to the normal BSR for the SCG is ignored until the random access procedure is completed (_2735).
  • Normal BSR for SCG means regular BSR triggered by data to be transmitted over SCG or regular BSR triggered by MAC device configured for SCG or regular BSR triggered by SeG or LCG_s triggered by SeG. .
  • the UE proceeds to step _2740 triggers the regular BSR for the MCG. If the SR transmission resource is not allocated to the PUCCH of the PCell, the UE triggers random access in the PCell.
  • 28A and 28B illustrate UE operation when a regular BSR is triggered.
  • a regular BSR is triggered at step _2805.
  • step _2810 the UE checks whether the normal BSR is BSR for SCG or BSR for MCG. If it is a BSR for an SCG, it proceeds to step _2815, and if it is a BSR for an MCG, it proceeds to step _2860.
  • step _2815 the UE checks whether there is a random access process currently in progress, and if so, proceeds to step _2825 and, if not, to step _2820.
  • step _2820 the UE triggers a random access in the PSCell.
  • step _2825 the UE checks whether the random access is in progress in the SCG serving cell or in the MCG serving cell. If it is in progress in the SCG serving cell, it proceeds to step _2830 and if it is in progress in the MCG serving cell, it proceeds to step _2820 to trigger random access in the PSCell.
  • step _2830 the UE checks whether a random access currently in progress is indicated by an RRC control message. That is, it is checked whether it is started by predetermined control information (for example, 1 bit information indicating random access start) included in the received RRC control message. If it is indicated by the RRC control message, it proceeds to step _2840, and if it is not indicated by the RRC control message (for example, if it is initiated by the PDCCH order or triggered by another regular BSR), it proceeds to step _2835.
  • predetermined control information for example, 1 bit information indicating random access start
  • the UE proceeds to step _2840 and continues the random access process initiated by the RRC control message, and proceeds to step _2855 when the random access process is being performed.
  • step _2855 the UE checks whether the most recently reported BSR (BSR reported in the random access procedure) reflects the current buffer state.
  • BSR BSR reported in the random access procedure
  • the regular BSR it means that new data with high priority has been generated, and the random access procedure that was in progress when the regular BSR is triggered also includes BSR information. Therefore, if the BSR transmitted in the random access process also includes information on the data that triggered the regular BSR, the new random access does not need to be triggered. Therefore, the process proceeds to step _2857 to terminate the process without triggering any further random access. do.
  • the process proceeds to step _2859 to trigger a new random access in the PSCell.
  • a new regular BSR for the SCG can be triggered.
  • step _2835 the UE checks whether contention based random access (CBRA) or contention free random access (CFRA) is currently in progress. If CBRA, go to step _2845; if CFRA, go to step _2840.
  • CBRA contention based random access
  • CFRA contention free random access
  • the random access triggered by the regular BSR is always CBRA, and if the ongoing random access is CFRA, the process proceeds to step _2840 to preferentially perform random access by CFRA.
  • step _2845 the UE checks whether data is stored in the message 3 buffer, and if so, proceeds to step _2850, and if not, proceeds to step _2853.
  • the fact that data is stored in the message 3 buffer means that the MAC PDU to be transmitted using the uplink transmission resource allocated in the random access response message has already been configured, and thus the BSR reflecting the triggering of the regular BSR can be transmitted during the random access procedure. It means no.
  • no data is stored in the message 3 buffer, it means that the MAC PDU to be transmitted has not yet been configured in the random access process, and the contents of the BSR to be stored in the MAC PDU can be modified to reflect the most recent buffer state. it means.
  • step _2850 the UE stops the random access currently in progress and starts a new random access in the PSCell.
  • step _2853 the UE continues the random access process currently in progress.
  • the BSR reflecting the most recent buffer state is stored in the MAC PDU to be transmitted through the random access procedure.
  • step _2860 the UE checks whether there is a random access process currently in progress, and if so, proceeds to step _2865 and, if not, to step _2870.
  • step _2870 the UE triggers a random access in the PCell.
  • step _2865 the UE checks whether the random access is in progress in the SCG serving cell or in the MCG serving cell. If it is in progress in the SCG serving cell, it proceeds to step _2870, and if it is in progress in the MCG serving cell, proceeds to step _2873.
  • step _2873 the UE checks whether contention based random access (CBRA) or contention free random access (CFRA) is currently in progress. If it is CBRA, go to step _2880, and if it is CFRA, go to step _2875.
  • CBRA contention based random access
  • CFRA contention free random access
  • step _2880 the UE checks whether data is stored in the message 3 buffer, and if so, proceeds to step _2883, and if not, proceeds to step _2885.
  • step _2883 the UE stops the random access currently in progress and newly initiates random access in the PCell.
  • step _2885 the UE continues the random access process currently in progress.
  • the BSR reflecting the most recent buffer state is stored in the MAC PDU to be transmitted through the random access procedure.
  • the UE proceeds to step _2875 and continues the current CFRA process, and proceeds to step _2890 when the random access process is completed.
  • step _2890 the UE checks whether the most recently reported BSR (i.e., BSR reported in the random access process) reflects the current buffer state. If so, the UE proceeds to step _2893 to terminate the process without triggering any more random access. do. If the most recently reported BSR does not reflect the current buffer state, go to step _2895 to trigger a new random access in the PCell. Alternatively, the regular BSR for the MCG may be newly triggered.
  • the most recently reported BSR i.e., BSR reported in the random access process
  • Random access is triggered by the terminal itself or triggered by the base station instructions.
  • the base station uses a layer 1 control signal or a layer 3 control message to trigger random access in a given serving cell.
  • 29 illustrates an operation of a terminal for determining a cell for triggering random access according to an instruction of a base station.
  • step _2905 the random access is triggered by the downlink signal transmitted by the base station.
  • random access may be triggered by an indication of the base station.
  • step _2910 the UE checks whether the downlink signal that triggered the random access is a layer 1 signal such as a PDCCH order or a layer 3 signal such as an RRC control message. If it is a 1-layer signal, it proceeds to step _2915 and if it is a 3-layer signal, it proceeds to step _2930.
  • a layer 1 signal such as a PDCCH order
  • a layer 3 signal such as an RRC control message
  • step _2915 the UE checks whether the CIF (Carrier Indicator Field) field is included in the 1 st layer signal. If yes, go to step _2925; if not, go to step _2920.
  • step _2920 the UE triggers random access in the serving cell in which the first layer signal is received.
  • the terminal transmits a random access preamble through the uplink of the serving cell in which the first layer signal is received, and receives the random access response message through the PCell if the serving cell is a serving cell of MCG. If the serving cell is a serving cell of the SCG, a random access response message is received through the PSCell.
  • CIF Carrier Indicator Field
  • step _2925 the UE triggers random access in the serving cell indicated in the CIF of the first layer signal.
  • step _2930 the UE checks whether the L3 control message includes MobilityControlInfo or control information explicitly indicating to trigger random access, and branches to _2935 or _2940 as follows. .
  • the process proceeds to step _2935 and the PCell transmits the preamble and receives the random access response message from the PCell.
  • step _2940 to trigger random access in the PSCell.
  • Another embodiment of the present invention provides a terminal and a base station operation and apparatus for transmitting and receiving PHR in a multi-connection state.
  • the PHR is a MAC control message for reporting a terminal power output (PH) for controlling uplink transmission power.
  • the base station schedules the uplink transmission of the terminal so that the transmission output of the terminal does not exceed the maximum transmission power in consideration of the PH reported by the terminal.
  • the type 1 PH is a PH associated with a PUSCH (Physical Uplink Shared Channel, standard 36.213) transmission and may be defined as a difference value between a transmission output required for a predetermined PUSCH transmission and a maximum transmission output of the UE.
  • Type 2 PH is a PH associated with PUCCH (Physical Uplink Control Channel, see 36.213) transmission and may be defined as a difference value between the required transmission power and the maximum transmission power when simultaneously performing a predetermined PUSCH transmission and a PUCCH transmission.
  • the general format 3001 is for storing Type 1 PH for one serving cell
  • the extended format 3002 is for Type 1 PH for multiple serving cells and Type 2 PH of PCell.
  • the first octet of the extended format is used as a bitmap indicating the presence or absence of a serving cell, and the octet located next includes type 2 PH information of the PCell, and then type 1 PH information of the PCell.
  • the PH information for the SCell designated in the first octet is sequentially listed in the order of the SCell identifier (SCell index).
  • SCell index SCell index
  • the maximum output (PCmax) of the terminal in the cell is also included and reported.
  • the multiple connection format 3003 houses the type 1 PH of all serving cells and the type 2 PH of PCell and PSCell that are active at the time the PHR is triggered.
  • the first octet of the multi-connection format is used as a bitmap indicating the presence or absence of a serving cell.
  • the octet located next may include PCell type 2 PH information, and PCmax may be stored in the next octet.
  • Type 2 PH information of the PSCell is then stored in octet 3005, and then in order of the size of the serving cell identifier.
  • PHs of multiple SCells are stored in a multiple connection format.
  • the type 1 PH of the SCell is stored in the order of serving cell identifier size of the SCell, while the type 2 PH of the SCell is stored in a predetermined position (for example, the next octet of the PCell type 2 PH), not in the order of serving cell identifier size. Therefore, the type 1 PH and type 2 PH of the PSCell are stored in at least two octets, not adjacent ones.
  • type 1 PH and type 2 PH of one cell are compared with those stored in adjacent octets.
  • Type 1 PH and Type 2 PH may or may not involve octets containing PCmax. Therefore, when any two PHs are stored in adjacent octets, it means whether or not adjacent to the octets in which PCmax is stored. That is, the type 1 PH and the type 2 PH of the PSCell are stored in octets that are not adjacent to each other, even if PCmax octets are not included in each PH.
  • the type 2 PH of the PCell in the extended format is an optional field.
  • the extended format always includes the type 2 PH of the PCell.
  • the extended format does not include the type 2 PH of the PCell. This is because the possibility that the transmission output state of the UE is generated by only PUCCH transmission is low, and if the simultaneous transmission of PUSCH and PUCCH is unlikely, the utility of type 2 PH is reduced.
  • the type 2 PH and the PSCell type 2 PH of the PCell are always included regardless of whether PUCCH and PUSCH are simultaneously transmitted. This is because even though PUCCH and PUSCH are not transmitted simultaneously in the corresponding cell group, simultaneous transmission is possible between cell groups.
  • the UE associates with or without Type 2 PH reporting whether PUCCH and PUSCH are simultaneously transmitted until multiple connections are established, but if multiple connections are established, PCell is independent of whether PUCCH and PUSCH are simultaneously transmitted. Always report the Type 2 PH of PSCell and the Type 2 PH of PSCell.
  • the UE Before the multiple connection is established, the UE reports the PHR using one of a general format and an extended format.
  • the base station delivers a parameter called extendedPHR to the terminal using an RRC control message, and when the parameter is delivered, the terminal uses an extended format.
  • extendedPHR a parameter called extendedPHR
  • multiple concatenation formats are preferably used only when multiple concatenations are established. Therefore, there is no need to signal using separate parameters. Therefore, when the multi-connection is not established, the terminal uses one of a general format and an extended format according to the instructions of the base station, and when the multi-connection is established, the terminal uses the multi-connection format regardless of the indication of the base station.
  • the PHR is triggered.
  • the PHR is triggered or periodically triggered, for example, when path loss changes above a certain threshold.
  • step 3110 the terminal checks whether multiple connections are currently established.
  • Setting up multiple connections means the same as setting up at least one SCG, setting up two MAC devices, setting up two cell groups, or setting up a PSCell.
  • step 3135 If multiple connections are established, the process proceeds to step 3135. If multiple connections are not established, the process proceeds to step 3115. In step 3115, the UE checks whether the extended PHR format is set, and if so, proceeds to step 3123, otherwise proceeds to step 3120.
  • step 3120 the UE generates and transmits a PHR of a general format containing the type 1 PH of the PCell.
  • step 3123 the UE checks whether simultaneous transmission of the PUCCH and the PUSCH is configured. Or check whether simultaneousPUCCH-PUSCH is set.
  • the simultaneousPUCCH-PUSCH may be configured for each MAC entity or for each cell group. Since step 3123 is not multiple connections, only one cell group exists. If simultaneousPUCCH-PUSCH is set, the process proceeds to step 3130, and if not, the process proceeds to step 3125.
  • step 3125 the UE generates and transmits an extended format PHR that contains the type 1 PHs of the SCell and the type 1 PH of the PCell.
  • the UE In step 3130, the UE generates and transmits an extended format PHR in which the Type 1 PHs of the SCell and the Type 1 PH and Type 2 PH of the PCell are activated. At this time, the type 1 PH and the type 2 PH of the same cell are stored in adjacent octets. Above and below adjacent octets are octets spaced one octet apart (eg nth and n + 2th octets) if PCmax is reported, or physically completely octets if PCmax is not reported ( For example, n th octet and n + 1 th octet.
  • the UE In step 3135, the UE generates and transmits a PHR of a multiple connection format in which the type 1 PHs of the SCell, the type 1 PH and type 2 PH of the PCell, and the type 2 PH of the PSCell are accommodated.
  • the UE does not consider whether to set the simultaneousPUCCH-PUSCH of the MCG and the simultaneousPUCCH-PUSCH of the SCG in determining whether to report the type 2 PH of the PCell and the type 2 PH of the PSCell. That is, even if simultaneousPUCCH-PUSCH is not set in MCG or SCG, type 2 PH of PCell or PSCell is reported.
  • the UE if the simultaneous PUCCH-PUSCH is not configured for the PCell, the UE generates and reports a PHR that does not include the type 2 PH of the PCell when multiple connections are not established, and if the multiple connection is established, the type 2 PH of the PCell is included. Generate and report a PHR.
  • a terminal configured with simultaneousPUCCH-PUSCH for a PCell generates and reports a PHR including a type 2 PH of the PCell regardless of whether multiple connections are configured.
  • the UE In generating the multiple connectivity format PHR, the UE stores the type 1 PH and the type 2 PH of the first serving cell in adjacent octets, and the type 1 PH and the type 2 PH of the second serving cell are not adjacent to each other. To octet not.
  • the first serving cell is a PCell
  • the second serving cell is a PSCell.
  • FIG. 19 is a diagram illustrating a terminal structure according to one embodiment of the present specification.
  • a terminal includes a transceiver _1905, a controller _1910, a multiplexing and demultiplexing unit _1915, a control message processing unit _1930, and various upper layer processing units _1920. , _1925).
  • the transceiver unit _1905 receives data and a predetermined control signal through a downlink channel of a serving cell and transmits data and a predetermined control signal through an uplink channel. When a plurality of serving cells are set, the transceiver unit _1905 performs data transmission and reception and control signal transmission and reception through the plurality of serving cells.
  • the multiplexer and demultiplexer _1915 multiplexes data generated by the upper layer processor _1920 and _1925 or the control message processor _1930 or demultiplexes the data received by the transceiver _1905 so that the upper layer processor _1920, _1925 or the control message processor _1930.
  • Independent multiplexing and demultiplexing unit (or MAC device) is configured in MeNB and SeNB, but one multiplexing and demultiplexing unit (or MAC device) is configured in UE.
  • the control message processing unit _1930 is an RRC layer device and processes a control message received from the base station to perform a necessary operation. For example, the RRC control message is received to transmit random access related information, PUCCH configuration information, pattern information, PHR configuration information, and the like to the controller.
  • the higher layer processing units _1920 and _1925 may be configured for each service.
  • Data generated from user services such as FTP (File Transfer Protocol) or Voice over Internet Protocol (VoIP) can be processed and delivered to the multiplexing and demultiplexing unit (_1915) or the data transferred from the multiplexing and demultiplexing unit (_1915). Process it and pass it to the higher-level service application.
  • FTP File Transfer Protocol
  • VoIP Voice over Internet Protocol
  • the control unit _1910 checks the scheduling command received through the transceiver unit _1905, for example, the reverse grants, and the multiplexing and demultiplexing unit _1915 and the multiplexing and demultiplexing unit _1915 to perform reverse transmission on the appropriate transmission resource at an appropriate time. ).
  • the control unit also manages all procedures related to SCell configuration, all procedures related to random access, various procedures related to PUCCH transmission, various procedures related to SCG, and various procedures related to PHR transmission. More specifically, necessary control operations related to the terminal operation illustrated in FIGS. 5 to 31 are performed.
  • control unit _1910 When the control unit _1910 according to an embodiment of the present invention receives a serving cell addition control message including uplink subframe pattern information for a master serving cell group or a slave serving cell group from a base station, the control unit _1910 is included in the serving cell addition control message. A series of processes for establishing synchronization with the included serving cell can be controlled. In addition, the controller _1910 may control to transmit / receive data with the base station through the added serving cell when receiving an activation command for the synchronized serving cell.
  • the uplink subframe pattern information may include information on a subframe in which uplink transmission is allowed for the master serving cell group, information on a subframe in which uplink transmission is allowed for the slave serving cell group, or It may include at least one of information on subframes for which uplink transmission is not allowed.
  • the length of the uplink subframe pattern may be determined based on a hybrid retransmission request (HARQ) round trip time (RTT).
  • HARQ hybrid retransmission request
  • RTT round trip time
  • the uplink subframe pattern information includes bit information indicating a subframe allowed for uplink transmission for the master serving cell group, and uplink transmission for the slave serving cell group is allowed. Bit information about the subframe or offset information indicating the start of the subframe pattern may be included.
  • the uplink subframe pattern information may be pattern index information indicating one pattern among a plurality of subframe patterns having a predetermined length.
  • control unit _1910 receives transmission resource configuration information for uplink control information transmission from the base station, and transmits the resource for transmitting the uplink subframe pattern information and the uplink control information.
  • a resource for transmitting uplink control information may be determined based on the configuration information.
  • the controller _1910 may control to transmit the uplink control information through the determined resource.
  • the uplink control information includes a channel quality indicator (CQI), a scheduling request (SR), a sounding reference signal (SRS), or a buffer status report (Buffer Status Report, BSR). It may include at least one.
  • control unit _1910 generates a terminal capability information message including information on at least one or more band combinations supported by the terminal, and transmits the generated terminal capability information message to a base station. You can also control it.
  • the controller _1910 may determine which of two transmissions is to be preferentially performed, as shown in FIG. 26.
  • FIG. 20 is a diagram illustrating a MeNB structure according to an embodiment of the present specification.
  • the MeNB includes a transceiver (_2005), a controller (_2010), a multiplexing and demultiplexing unit (_2020), a control message processing unit (_2035), various upper layer processing units (_2025, _2030), and a scheduler ( _2015).
  • the transceiver _2005 transmits data and a predetermined control signal through a forward carrier and receives data and a predetermined control signal through a reverse carrier. When a plurality of carriers are set, the transceiver _2005 performs data transmission and control signal transmission and reception to the plurality of carriers.
  • the multiplexing and demultiplexing unit _2020 multiplexes data generated by the upper layer processing units _2025 and _2030 or the control message processing unit _2035 or demultiplexes the data received by the transmitting and receiving unit _2005 so that the appropriate upper layer processing unit _2025, _2030), the control message processor _2035, or the controller _2010.
  • the control message processor _2035 processes the control message transmitted by the terminal to take a necessary action, or generates a control message to be transmitted to the terminal and delivers the control message to the lower layer.
  • the upper layer processing units _2025 and _2030 may be configured for each bearer, and the data transmitted from the S-GW or another base station is transferred to the multiplexing and demultiplexing unit _2020 or the RLC delivered from the multiplexing and demultiplexing unit _2020 Deliver the PDU to the S-GW or other base station.
  • the scheduler allocates a transmission resource to the terminal at an appropriate time point in consideration of the buffer state and the channel state of the terminal, and processes the signal transmitted by the terminal to the transceiver or transmits the signal to the terminal.
  • the controller also manages overall procedures related to SCell configuration. More specifically, in FIG. 5 to FIG. 31, a control operation necessary for an operation to be performed by the MeNB is performed.
  • FIG. 21 is a diagram illustrating a SeNB structure according to an embodiment of the present specification.
  • SeNB according to an embodiment of the present disclosure, the transceiver unit (_2105), the control unit (_2110), the multiplexing and demultiplexing unit (_2120), the control message processing unit (_2135), various upper layer processing unit (_2130), the scheduler (_2115) ) May be included.
  • the transceiver _2105 transmits data and a predetermined control signal through a forward carrier and receives data and a predetermined control signal through a reverse carrier. When a plurality of carriers are set, the transceiver _2105 performs data transmission and control signal transmission and reception to the plurality of carriers.
  • the multiplexing and demultiplexing unit _2120 multiplexes data generated by the upper layer processing units _2125 and _2130 or the control message processing unit _2135, or demultiplexes the data received by the transmitting and receiving unit _2105 to appropriately apply the upper layer processing unit _2130. Or it serves to deliver to the control unit (_2110).
  • the control message processing unit _2135 processes the control message sent by the MeNB and takes necessary actions.
  • the scheduler allocates a transmission resource to the terminal at an appropriate time point in consideration of the buffer state and the channel state of the terminal, and processes the signal transmitted by the terminal to the transceiver or transmits the signal to the terminal.
  • the controller also manages overall procedures related to SCell configuration. More specifically, in FIG. 5 to FIG. 31, a control operation necessary for an operation to be performed by the SeNB is performed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne une méthode et un appareil de transmission/réception de données utilisant de multiples porteuses dans un système de communication mobile. Une méthode de transmission/réception de données par un terminal utilisant de multiples porteuses dans un système de communication mobile de la présente invention comprend les étapes suivantes : recevoir un message de commande d'ajout de cellule de service comprenant des informations de motif de sous-trame de liaison montante sur un groupe de cellules de service maître ou un groupe de cellules de service esclave en provenance d'une station de base ; établir une synchronisation avec une cellule de service comprise dans le message de commande d'ajout de cellule de service ; et, lorsqu'une commande d'activation de la cellule de service avec laquelle la synchronisation est établie est reçue, transmettre/recevoir des données vers/à partir de la station de base par la cellule de service ajoutée.
PCT/KR2014/007538 2013-08-14 2014-08-13 Méthode et appareil de transmission/réception de données en utilisant de multiples porteuses dans un système de communication mobile Ceased WO2015023128A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP14836612.3A EP3035561A4 (fr) 2013-08-14 2014-08-13 Méthode et appareil de transmission/réception de données en utilisant de multiples porteuses dans un système de communication mobile
US14/912,386 US9992773B2 (en) 2013-08-14 2014-08-13 Method and apparatus for transmitting/receiving data using multiple carriers in mobile communication system
EP19155351.0A EP3506528A1 (fr) 2013-08-14 2014-08-13 Procédé et appareil de transmission/réception de données au moyen de porteuses multiples dans un système de communication mobile
US15/996,240 US10149295B2 (en) 2013-08-14 2018-06-01 Method and apparatus for transmitting/receiving data using multiple carriers in mobile communication system

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
KR10-2013-0096293 2013-08-14
KR20130096293 2013-08-14
KR10-2013-0097941 2013-08-19
KR20130097941 2013-08-19
KR20130115454 2013-09-27
KR10-2013-0115454 2013-09-27
KR10-2014-0033679 2014-03-21
KR20140033679A KR20150020018A (ko) 2013-08-14 2014-03-21 이동 통신 시스템에서 복수의 캐리어를 이용하는 데이터 송수신 방법 및 장치
KR10-2014-0102548 2014-08-08
KR1020140102548A KR102077166B1 (ko) 2013-08-14 2014-08-08 이동 통신 시스템에서 복수의 캐리어를 이용하는 데이터 송수신 방법 및 장치

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US14/912,386 A-371-Of-International US9992773B2 (en) 2013-08-14 2014-08-13 Method and apparatus for transmitting/receiving data using multiple carriers in mobile communication system
US15/996,240 Continuation US10149295B2 (en) 2013-08-14 2018-06-01 Method and apparatus for transmitting/receiving data using multiple carriers in mobile communication system

Publications (1)

Publication Number Publication Date
WO2015023128A1 true WO2015023128A1 (fr) 2015-02-19

Family

ID=52579002

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2014/007538 Ceased WO2015023128A1 (fr) 2013-08-14 2014-08-13 Méthode et appareil de transmission/réception de données en utilisant de multiples porteuses dans un système de communication mobile

Country Status (4)

Country Link
US (2) US9992773B2 (fr)
EP (2) EP3035561A4 (fr)
KR (2) KR20150020018A (fr)
WO (1) WO2015023128A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016144078A1 (fr) * 2015-03-09 2016-09-15 주식회사 케이티 Procédé de transmission d'informations d'état de canal et dispositif associé
WO2019194652A1 (fr) * 2018-04-05 2019-10-10 엘지전자 주식회사 Procédé d'émission et de réception d'un signal dans un système de communication sans fil prenant en charge une bande sans licence et appareil le prenant en charge
CN110521260A (zh) * 2017-03-23 2019-11-29 高通股份有限公司 用于减轻队列间干扰的方法
US10708893B2 (en) 2015-03-09 2020-07-07 Kt Corporation Method for transmitting channel state information and device therefor
US20210250920A1 (en) * 2020-02-06 2021-08-12 Samsung Electronics Co., Ltd. Method and apparatus for configuring bandwidth in wireless communication system

Families Citing this family (61)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104581854B (zh) * 2013-10-16 2019-07-12 中兴通讯股份有限公司 一种无线连接方法和装置
US10575315B2 (en) * 2013-12-16 2020-02-25 Apple Inc. System and method for providing priority data of band combinations for carrier aggregation
US9480029B2 (en) 2014-01-06 2016-10-25 Intel IP Corporation Power headroom reporting with dual connectivity
US10064142B2 (en) * 2014-04-18 2018-08-28 Ntt Docomo, Inc. User apparatus and uplink transmission power information transmission method
US10141983B2 (en) 2014-05-08 2018-11-27 Samsung Electronics Co., Ltd. Method for activating pSCell and SCell in mobile communication system supporting dual connectivity
WO2015172114A1 (fr) * 2014-05-09 2015-11-12 Huawei Technologies Co., Ltd. Dispositif, réseau et procédé de communication avec adaptation dynamique
EP3172923B1 (fr) 2014-07-23 2019-10-23 Samsung Electronics Co., Ltd. Procédé et appareil pour générer et transmettre un rapport de marge de sécurité de puissance dans un système de communication mobile
EP3216300B1 (fr) 2014-11-04 2018-08-29 Telefonaktiebolaget LM Ericsson (publ) Dispositif de communication sans fil, noeud de réseau et procédés associés pour des transmissions d'accès aléatoire améliorées
US10687369B2 (en) * 2015-01-22 2020-06-16 Lg Electronics Inc. Method for initiating a random access procedure in a carrier aggregation system and a device therefor
CN106134272B (zh) 2015-01-30 2020-01-31 华为技术有限公司 通信方法、网络设备、用户设备和通信系统
US9820264B2 (en) 2015-03-09 2017-11-14 Ofinno Technologies, Llc Data and multicast signals in a wireless device and wireless network
US10700845B2 (en) 2015-03-09 2020-06-30 Comcast Cable Communications, Llc Secondary cell deactivation in a wireless device and a base station
US10182406B2 (en) 2015-03-09 2019-01-15 Comcast Cable Communications, Llc Power headroom report for a wireless device and a base station
US10327236B2 (en) 2015-03-09 2019-06-18 Comcast Cable Communications, Llc Secondary cell in a wireless device and wireless network
US9820298B2 (en) 2015-03-09 2017-11-14 Ofinno Technologies, Llc Scheduling request in a wireless device and wireless network
WO2016154884A1 (fr) * 2015-03-31 2016-10-06 华为技术有限公司 Procédé de communication, équipement utilisateur et station de base
US11641255B2 (en) 2015-04-05 2023-05-02 Comcast Cable Communications, Llc Uplink control information transmission in a wireless network
US9877334B2 (en) 2015-04-05 2018-01-23 Ofinno Technologies, Llc Cell configuration in a wireless device and wireless network
US10200177B2 (en) 2015-06-12 2019-02-05 Comcast Cable Communications, Llc Scheduling request on a secondary cell of a wireless device
US9894681B2 (en) 2015-06-12 2018-02-13 Ofinno Technologies, Llc Uplink scheduling in a wireless device and wireless network
US9948487B2 (en) 2015-06-15 2018-04-17 Ofinno Technologies, Llc Uplink resource allocation in a wireless network
CN106413117B (zh) * 2015-07-29 2021-08-17 索尼公司 无线通信系统、基站侧和用户设备侧的装置及方法
US10200164B2 (en) 2015-09-22 2019-02-05 Comcast Cable Communications, Llc Carrier activation in a multi-carrier wireless network
US10172124B2 (en) 2015-09-22 2019-01-01 Comcast Cable Communications, Llc Carrier selection in a multi-carrier wireless network
JP2018532314A (ja) 2015-10-17 2018-11-01 コムキャスト ケーブル コミュニケーションズ， エルエルシー 部分および完全サブフレームにおける制御チャネル構成
EP3384723B1 (fr) * 2015-11-30 2023-06-14 Telefonaktiebolaget LM Ericsson (publ) Procédés et appareils de configuration d'une grappe
CN106922022A (zh) * 2015-12-25 2017-07-04 华为技术有限公司 上行业务资源调度方法、设备和系统
US10548121B2 (en) 2016-02-03 2020-01-28 Comcast Cable Communications, Llc Downlink and uplink channel transmission and monitoring in a wireless network
US10880921B2 (en) 2016-02-04 2020-12-29 Comcast Cable Communications, Llc Detection threshold for a wireless network
US10200992B2 (en) 2016-05-06 2019-02-05 Comcast Cable Communications, Llc Uplink signal starting position in a wireless device and wireless network
US10785789B2 (en) * 2016-06-08 2020-09-22 Telefonaktiebolaget Lm Ericsson (Publ) Systems and methods for signaling and using transmit patterns
KR102581594B1 (ko) 2016-07-19 2023-09-25 삼성전자 주식회사 무선 통신 시스템에서 반송파 집적 방법 및 장치
CN112188625B (zh) * 2016-08-11 2024-09-06 华为技术有限公司 信息传输方法、基站和用户设备
CN107801243B (zh) 2016-08-29 2021-01-29 华为技术有限公司 一种下行传输方法及装置
US11147062B2 (en) 2016-10-14 2021-10-12 Comcast Cable Communications, Llc Dual connectivity power control for wireless network and wireless device
US10848977B2 (en) 2016-11-02 2020-11-24 Comcast Cable Communications, Llc Dual connectivity with licensed assisted access
US20180124831A1 (en) 2016-10-29 2018-05-03 Ofinno Technologies, Llc Dual connectivity scheduling request for wireless network and wireless device
CN116669112A (zh) * 2017-01-26 2023-08-29 中兴通讯股份有限公司 通信方法、网络设备、计算机存储介质
KR102292044B1 (ko) * 2017-06-08 2021-08-20 엘지전자 주식회사 Nr에서 이중 연결을 지원하는 방법 및 장치
WO2018232724A1 (fr) * 2017-06-23 2018-12-27 Nokia Technologies Oy Commande de connectivité multiple
US11102731B2 (en) * 2017-07-13 2021-08-24 Lg Electronics Inc. Method for transmitting a power headroom reporting in wireless communication system and a device therefor
US11483119B2 (en) * 2017-07-28 2022-10-25 Qualcomm Incorporated Secondary cell configuration signaling and activation field
CN114679751B (zh) * 2017-09-20 2025-01-24 三星电子株式会社 无线通信系统中发送和接收数据的方法及装置
BR112020005862A2 (pt) * 2017-09-28 2020-09-29 Sony Corporation equipamento de usuário, e, estação-base.
CN108055698A (zh) * 2017-11-13 2018-05-18 深圳市万普拉斯科技有限公司 载波聚合中射频能力上报的控制方法和装置
US11323144B2 (en) * 2017-11-24 2022-05-03 Beijing Xiaomi Mobile Software Co., Ltd. Method and device for indicating inter-modulation distortion, base station, and user equipment
CN109982430B (zh) * 2017-12-28 2021-07-13 大唐移动通信设备有限公司 一种进行调度请求的方法和设备
US11690068B2 (en) * 2018-06-21 2023-06-27 Nokia Technologies Oy Optimal BSR for limited traffic mix
CN110831141A (zh) 2018-08-10 2020-02-21 华为技术有限公司 一种通信方法及装置
WO2020030147A1 (fr) * 2018-08-10 2020-02-13 华为技术有限公司 Procédé et appareil de communication
CN118368040A (zh) * 2018-09-10 2024-07-19 联想（新加坡）私人有限公司 消息3缓冲区中的媒体访问控制协议数据单元
CN112655245A (zh) * 2018-09-19 2021-04-13 Oppo广东移动通信有限公司 一种数据传输方法、设备及存储介质
WO2020060339A1 (fr) * 2018-09-21 2020-03-26 엘지전자 주식회사 Procédé d'émission et de réception de liaison montante prenant en compte de multiples faisceaux et/ou de multiples panneaux dans un système de communication sans fil et dispositif pour celui-ci
WO2020069174A1 (fr) * 2018-09-27 2020-04-02 Intel Corporation Indication de capacité d'équipement utilisateur destinée à un transfert intercellulaire à connectivité multiple
KR102665409B1 (ko) 2018-10-16 2024-05-10 삼성전자주식회사 다중 접속에서 데이터 분할을 위한 방법 및 장치
US10904935B2 (en) * 2019-01-28 2021-01-26 T-Mobile Usa, Inc. Smart scheduling for intermodulation distortion avoidance on multiple uplink transmissions
WO2020199221A1 (fr) * 2019-04-04 2020-10-08 Oppo广东移动通信有限公司 Procédé de configuration de ressources, dispositif réseau, et dispositif terminal
CN111817736B (zh) * 2019-07-04 2021-12-28 维沃移动通信有限公司 干扰处理方法、终端及网络侧设备
CN112449426B (zh) * 2019-09-04 2022-12-06 维沃移动通信有限公司 上行传输的方法和终端
CN113784339B (zh) * 2020-06-10 2023-06-02 华为技术有限公司 一种通信方法及装置
CN120660414A (zh) * 2023-02-15 2025-09-16 高通股份有限公司 用于多发送和接收点的随机接入增强

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012108718A2 (fr) * 2011-02-10 2012-08-16 엘지전자 주식회사 Procédé et dispositif de planification dans un système à agrégation de porteuses
KR20120092014A (ko) * 2011-02-09 2012-08-20 주식회사 팬택 다중 요소 반송파 시스템에서 상향링크 신호의 송신 장치 및 방법
KR20120094496A (ko) * 2009-11-19 2012-08-24 인터디지탈 패튼 홀딩스, 인크 다중-반송파 시스템에서의 요소 반송파 활성화/비활성화
KR20120120024A (ko) * 2011-04-22 2012-11-01 삼성전자주식회사 동기 복합 자동 재전송 요구 송신을 지원하는 방법 및 장치
WO2013025237A1 (fr) * 2011-08-12 2013-02-21 Intel Corporation Formation de groupes d'avance temporelle avec agrégation de porteuses dans un réseau hétérogène

Family Cites Families (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106851808B (zh) * 2010-04-01 2020-08-18 太阳专利信托公司 终端装置和功率调节方法
KR101831281B1 (ko) * 2010-04-06 2018-02-23 삼성전자주식회사 이동통신 시스템에서 스케줄링 정보를 처리하는 방법 및 장치
US8537767B2 (en) * 2010-04-06 2013-09-17 Sunplus Technology Co., Ltd Method for performing power headroom reporting procedure and PHR MAC control element
KR101852814B1 (ko) * 2010-06-18 2018-04-27 엘지전자 주식회사 무선 통신 시스템에서 단말이 잔여전력 정보를 송신하는 방법 및 이를 위한 장치
CN103053206A (zh) * 2010-06-21 2013-04-17 诺基亚西门子网络公司 具有功率余量报告的载波聚合
US8954106B2 (en) * 2010-08-10 2015-02-10 Samsung Electronics Co., Ltd. Method and apparatus for configuring power headroom information in mobile communication system supporting carrier aggregation
US9144038B2 (en) * 2010-11-05 2015-09-22 Samsung Electronics Co., Ltd. Method and apparatus for calculating power headroom in carrier aggregation mobile communication system
KR101910899B1 (ko) * 2010-11-05 2019-01-07 삼성전자 주식회사 이동통신 시스템에서 단말이 Ｐｏｗｅｒ Ｈｅａｄｒｏｏｍ을 계산하는 방법 및 장치
KR101762610B1 (ko) * 2010-11-05 2017-08-04 삼성전자주식회사 이동 통신 시스템에서 역방향 스케줄링 및 그를 위한 정보 전송 방법 및 장치
CN102469058B (zh) * 2010-11-12 2016-02-10 中兴通讯股份有限公司 一种用于载波聚合场景的载波最大功率的上报方法和装置
EP2509373A1 (fr) * 2011-04-01 2012-10-10 Panasonic Corporation Rapport de marge d'alimentation étendue efficace pour programmation semi-persistante
US9319203B2 (en) 2011-06-15 2016-04-19 Lg Electronics Inc. Method of transmitting control information and device for same
WO2013048081A2 (fr) * 2011-09-26 2013-04-04 엘지전자 주식회사 Procédé et appareil d'émission/réception d'un rapport de marge de puissance dans un système de communication mobile
KR20130045169A (ko) 2011-10-24 2013-05-03 주식회사 팬택 다중 요소 반송파 시스템에서 상향링크 동기의 수행장치 및 방법
US9215678B2 (en) 2012-04-01 2015-12-15 Ofinno Technologies, Llc Timing advance timer configuration in a wireless device and a base station
EP2849501B1 (fr) * 2012-05-09 2020-09-30 Samsung Electronics Co., Ltd. Procédé et appareil de commande de réception discontinue dans un système de communication mobile
KR20140022711A (ko) * 2012-08-14 2014-02-25 삼성전자주식회사 이동통신 시스템에서 핸드 오버를 수행하는 방법 및 장치
WO2014114261A1 (fr) * 2013-01-25 2014-07-31 Mediatek Singapore Pte. Ltd. Mécanisme amélioré de maintenance d'alignement temporel en liaison montante pour agrégation de porteuses inter-enb
KR102037388B1 (ko) * 2013-04-05 2019-10-28 주식회사 팬택 무선 통신 시스템에서 단말의 잉여전력보고 전송방법 및 장치
WO2014208560A1 (fr) * 2013-06-26 2014-12-31 シャープ株式会社 Dispositif de terminal, dispositif de station de base et procédé de communication
US10278139B2 (en) * 2013-12-20 2019-04-30 Lg Electronics Inc. Method for power headroom reporting and device therefor
US10172102B2 (en) * 2013-12-22 2019-01-01 Lg Electronics Inc. Method for power headroom reporting and device therefor
US9480029B2 (en) * 2014-01-06 2016-10-25 Intel IP Corporation Power headroom reporting with dual connectivity
EP3099118B1 (fr) * 2014-01-22 2019-06-12 LG Electronics Inc. Procédé d'exécution de commande de puissance, et équipement d'utilisateur
US9883467B2 (en) * 2014-03-06 2018-01-30 Sharp Kabushiki Kaisha Terminal device, base station device, communication system, control method, and integrated circuit
TWI628968B (zh) * 2014-03-14 2018-07-01 Ｌｇ電子股份有限公司 在雙連結系統中觸發功率餘裕回報的方法及其裝置
EP3172923B1 (fr) * 2014-07-23 2019-10-23 Samsung Electronics Co., Ltd. Procédé et appareil pour générer et transmettre un rapport de marge de sécurité de puissance dans un système de communication mobile

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20120094496A (ko) * 2009-11-19 2012-08-24 인터디지탈 패튼 홀딩스, 인크 다중-반송파 시스템에서의 요소 반송파 활성화/비활성화
KR20120092014A (ko) * 2011-02-09 2012-08-20 주식회사 팬택 다중 요소 반송파 시스템에서 상향링크 신호의 송신 장치 및 방법
WO2012108718A2 (fr) * 2011-02-10 2012-08-16 엘지전자 주식회사 Procédé et dispositif de planification dans un système à agrégation de porteuses
KR20120120024A (ko) * 2011-04-22 2012-11-01 삼성전자주식회사 동기 복합 자동 재전송 요구 송신을 지원하는 방법 및 장치
WO2013025237A1 (fr) * 2011-08-12 2013-02-21 Intel Corporation Formation de groupes d'avance temporelle avec agrégation de porteuses dans un réseau hétérogène

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3035561A4 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10708893B2 (en) 2015-03-09 2020-07-07 Kt Corporation Method for transmitting channel state information and device therefor
WO2016144078A1 (fr) * 2015-03-09 2016-09-15 주식회사 케이티 Procédé de transmission d'informations d'état de canal et dispositif associé
CN110521260B (zh) * 2017-03-23 2023-04-04 高通股份有限公司 用于减轻队列间干扰的方法
CN110521260A (zh) * 2017-03-23 2019-11-29 高通股份有限公司 用于减轻队列间干扰的方法
KR20200105952A (ko) * 2018-04-05 2020-09-09 엘지전자 주식회사 비면허 대역을 지원하는 무선 통신 시스템에서 신호를 송수신하는 방법 및 이를 지원하는 장치
CN111955044A (zh) * 2018-04-05 2020-11-17 Lg电子株式会社 在支持免许可频带的无线通信系统中发送和接收信号的方法及支持该方法的设备
KR102194934B1 (ko) 2018-04-05 2020-12-24 엘지전자 주식회사 비면허 대역을 지원하는 무선 통신 시스템에서 신호를 송수신하는 방법 및 이를 지원하는 장치
US11503650B2 (en) 2018-04-05 2022-11-15 Lg Electronics Inc. Method for transmitting and receiving signal in wireless communication system supporting unlicensed band, and apparatus supporting same
WO2019194652A1 (fr) * 2018-04-05 2019-10-10 엘지전자 주식회사 Procédé d'émission et de réception d'un signal dans un système de communication sans fil prenant en charge une bande sans licence et appareil le prenant en charge
US11751256B2 (en) 2018-04-05 2023-09-05 Lg Electronics Inc. Method for transmitting and receiving signal in wireless communication system supporting unlicensed band, and apparatus supporting same
CN111955044B (zh) * 2018-04-05 2023-12-19 Lg电子株式会社 在支持免许可频带的无线通信系统中发送和接收信号的方法及支持该方法的设备
US20210250920A1 (en) * 2020-02-06 2021-08-12 Samsung Electronics Co., Ltd. Method and apparatus for configuring bandwidth in wireless communication system
US11849460B2 (en) * 2020-02-06 2023-12-19 Samsung Electronics Co., Ltd. Methods and apparatus for managing a bandwidth part

Also Published As

Publication number Publication date
KR20150020018A (ko) 2015-02-25
US10149295B2 (en) 2018-12-04
KR102077166B1 (ko) 2020-04-07
US9992773B2 (en) 2018-06-05
EP3506528A1 (fr) 2019-07-03
EP3035561A1 (fr) 2016-06-22
KR20150020084A (ko) 2015-02-25
US20160205681A1 (en) 2016-07-14
US20180279308A1 (en) 2018-09-27
EP3035561A4 (fr) 2017-04-05

Similar Documents

Publication Publication Date Title
WO2015023128A1 (fr) Méthode et appareil de transmission/réception de données en utilisant de multiples porteuses dans un système de communication mobile
WO2018186677A1 (fr) Appareil et procédé de réalisation d'une procédure d'accès aléatoire
WO2019139382A1 (fr) Procédé de demande d'informations système efficace et appareil de terminal dans un système de communication mobile de prochaine génération
WO2013169048A2 (fr) Procédé et appareil d'envoi/réception de données à l'aide d'une pluralité de porteuses dans un système de communication mobile
WO2016144055A1 (fr) Procédé et appareil pour réaliser et relever des mesures à l'aide d'équipement utilisateur configuré par des porteuses multiples dans des systèmes de communication mobile
WO2020184954A1 (fr) Procédé permettant de contrôler un accès d'un terminal dans un système de communication
WO2014084638A1 (fr) Procédé et dispositif pour exécuter une communication dans un système de communication sans fil
WO2019031934A1 (fr) Procédé de réglage de temporisation de liaison montante dans un système de communication sans fil et dispositif associé
WO2016186401A1 (fr) Procédé et dispositif de transmission ou de réception de demande de programmation dans un système de communications mobiles
WO2014098534A1 (fr) Appareil et procédé d'émission et de réception dans un système de communication mobile
WO2013176473A1 (fr) Procédé et dispositif d'émission et de réception de données dans un système de communication mobile
WO2014027852A1 (fr) Procédé et dispositif d'exécution de transfert dans un système de communication mobile
WO2013168917A1 (fr) Procédé et appareil pour transmettre et recevoir des données à l'aide d'une pluralité de porteuses dans un système de communication mobile
WO2015115772A1 (fr) Procédé et appareil de transmission et de réception de données à l'aide d'une pluralité de porteuses dans un système de communication mobile
WO2021261879A1 (fr) Procédé et appareil d'émission et de réception de liaison montante dans un système de communication sans fil
WO2020027491A1 (fr) Procédé de traitement de données dans un nœud relais, et dispositif associé
WO2021194247A1 (fr) Procédé de transmission de paquet de données instantané et appareil associé
WO2017159886A1 (fr) Procédé de transmission de données de liaison montante dans un système de communication sans fil et appareil associé
WO2024071901A1 (fr) Procédé et appareil pour effectuer une reprise de connexion dans un système de communication sans fil
WO2019190265A1 (fr) Procédé et appareil de commande de la puissance de transmission de canal de données de liaison montante
WO2023055185A1 (fr) Procédé et dispositif pour la transmission/réception d'un pdsch commun de groupe dans un système de communication sans fil
WO2024237529A1 (fr) Procédé et appareil permettant d'effectuer une transmission et une réception en liaison descendante dans un système de communication sans fil
WO2020085831A1 (fr) Appareil et procédé de réalisation d'une communication de véhicule
WO2023140626A1 (fr) Procédé et dispositif de fourniture d'informations de capacité de terminal sur des intervalles simultanés dans un système de communication mobile sans fil
WO2024010315A1 (fr) Procédé et appareil pour la prise en charge de la mobilité de la couche 2

Legal Events

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

Ref document number: 14836612

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 14912386

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2014836612

Country of ref document: EP