WO2016163059A1 - Terminal radio et station radio, et procédés associés - Google Patents

Terminal radio et station radio, et procédés associés Download PDF

Info

Publication number
WO2016163059A1
WO2016163059A1 PCT/JP2016/000127 JP2016000127W WO2016163059A1 WO 2016163059 A1 WO2016163059 A1 WO 2016163059A1 JP 2016000127 W JP2016000127 W JP 2016000127W WO 2016163059 A1 WO2016163059 A1 WO 2016163059A1
Authority
WO
WIPO (PCT)
Prior art keywords
scell
scells
downlink signaling
signaling message
pcg
Prior art date
Application number
PCT/JP2016/000127
Other languages
English (en)
Japanese (ja)
Inventor
尚 二木
Original Assignee
日本電気株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電気株式会社 filed Critical 日本電気株式会社
Priority to EP16776239.2A priority Critical patent/EP3282792B1/fr
Priority to JP2017511453A priority patent/JP6617770B2/ja
Priority to US15/564,655 priority patent/US11076345B2/en
Publication of WO2016163059A1 publication Critical patent/WO2016163059A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • 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
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present disclosure relates to wireless communication, and more particularly, to a wireless communication system in which a wireless terminal performs data transmission or reception using a plurality of carriers simultaneously.
  • 3GPP 3rd Generation Partnership Project
  • LTE Long Term Evolution
  • 3GPP 3rd Generation Partnership Project
  • CA Carrier Aggregation
  • CC Component Carrier
  • CC Component Carrier
  • the UCI Uplink Control Information
  • the increase in the amount of UCI information means that one wireless terminal (User Equipment (UE)) has to transmit a large amount of information on the uplink control channel (Physical Uplink Control Channel (PUCCH)) or lacks PUCCH resources. , And so on.
  • the UCI includes control information related to the downlink, and includes, for example, Channel State Information (CSI).
  • the CSI includes at least one of Channel Quality Indicator (CQI), Pre-Coding Matrix Indicator (PMI), and Rank Indicator (RI).
  • CQI Channel Quality Indicator
  • PMI Pre-Coding Matrix Indicator
  • RI Rank Indicator
  • a plurality of UEs perform CA on the same cell group, particularly when CA performs a first cell with a low frequency (eg, 800 MHz) and a second cell with a high frequency (eg, 3.5 GHz), many UEs It is assumed that a low-frequency first cell is used as a primary cell (PCell) and a high-frequency second cell is used as a secondary cell (SCell). In this case, since a plurality of UEs transmit UCIs for the second cell (SCell) in the PUCCH of the first cell (PCell), there is a problem that the overhead of the first cell becomes enormous. .
  • a low-frequency eg, 800 MHz
  • SCell secondary cell
  • PUCCHCon SCell for example, called PUCCHCon SCell or SCell PUCCH
  • SCell PUCCH a function that enables transmission of PUCCH in CC (Secondary CC (SCC)) used as SCell.
  • SCC Secondary CC
  • the base station determines whether the UE transmits UCI on the PCell PUCCH or the PUCCH of the one SCell to the UE. It has been proposed to set each time. It is assumed that the UCI for PCell is always transmitted on PCell's PUCCH.
  • a cell group in which UCI is transmitted on the PUCCH of the same cell may be referred to as PUCCH Cell Group (PCG).
  • a PCG including a PCell is referred to as a Primary PCG (P-PCG)
  • a PCG including only one or a plurality of SCells including a SCell that transmits a PUCCH is referred to as a Secondary PCG (S-PCG).
  • CA supports SCell activation / deactivation mechanisms to moderate UE battery consumption when CA is configured.
  • SCell and its activation are described below.
  • the UE When the UE receives a Radio Resource Control (RRC) Connection Reconfiguration message and one or more SCells are added (newly configured) by the RRC Connection Reconfiguration message (SCell addition), the added one Alternatively, the plurality of SCells are initially in a deactivated state (deactivated state). That is, the RRC layer of the UE sets a lower layer (i.e., “Medium” Access “Control (MAC) layer) so that one or more of these added SCells are in a deactivated state.
  • RRC Radio Resource Control
  • MAC Medium” Access “Control
  • the UE when the RRC Connection Reconfiguration message indicates the modification of the SCell setting that has already been set (SCell modification (SCell modification)), the UE does not change the state of the SCell related to the activation and before receiving the RRC Connection Reconfiguration message. Maintain the state.
  • the network ie, eNB
  • CE Activation / Deactivation MAC control element
  • the UE activates the SCell specified by the MAC CE.
  • the UE When the SCell is in the activated state, the UE performs the following operations: -When uplink CA is set, sending Sounding reference signals (SRS) in the SCell; -Monitoring the physical downlink control channel (PDCCH) in the SCell; In the case of cross-carrier scheduling, monitor the PDCCH for the SCell, and perform CSI reporting for the SCell.
  • SRS Sounding reference signals
  • PDCCH physical downlink control channel
  • the UE when the SCell is in the deactivated state, the UE performs the following operations: ⁇ Do not transmit SRS in the SCell; -Do not transmit Uplink Shared Channel (UL-SCH) in the SCell; ⁇ Do not transmit Random Access Channel (RACH) in the SCell; ⁇ Do not monitor PDCCH in the SCell; • Do not monitor the PDCCH for the SCell; and • Do not perform CSI reporting for the SCell.
  • UL-SCH Uplink Shared Channel
  • RACH Random Access Channel
  • the UE performs CSI reporting for the activated SCell and does not perform CSI reporting for the deactivated SCell.
  • the delay required until the CSI of the activated SCell becomes available depends on the processing capability of the UE, and in the system It is not decided uniquely.
  • Non-Patent Document 2 when the UE receives activation / deactivation MAC CE for activating SCell in subframe #n, the UE will receive subframe # n + 24 or # n + 34 at the latest (no later than subframe # n + 24 or #n +34), it is supposed that transmission of a valid CSI report (valid CSI report) should be started (see Non-Patent Document 2).
  • the UE When the UE receives activation / deactivation MAC CE to activate the SCell from the eNB in the subframe #n, the UE activates the SCell, and the CSI report valid by the subframe # n + 24 or # n + 34 at the latest Start sending (valid CSI report).
  • Such an operation is the same as the operation of SCell addition and SCell activation in the conventional CA, and no particular problem occurs.
  • the S-PCG to be added includes an activated SCell, and a PUCCH is transmitted in the SCell.
  • SCell modification procedure SCell modification modification procedure
  • the eNB cannot recognize whether an effective CSI report to be transmitted on the PUCCH of the SCell has been prepared in the UE.
  • some delay may be required before the UE can transmit it on the newly configured PUCCH.
  • Non-Patent Document 3 describes that when some SCells included in the added S-PCG are currently included in the P-PCG and are in the activated state, they are first deactivated and added to the S-PCG. It is proposed that all SCells, including the PUCCH SCell within, should remain deactivated during the RRCPCConnection Reconfiguration procedure with S-PCG addition.
  • PUCCH SCell means SCell to which PUSCCH is transmitted.
  • Non-Patent Document 3 proposes two options for deactivating SCells that are in an activated state. In Option 1, before adding the SCell to the S-PCG, it is deactivated by Activation / Deactivation MAC CE. In option 2, the SCell is first released and then added again.
  • 3GPP TS 36.321 V12.5.0 2015-03
  • 3GPP TS 36.133 V12.6.0 (2014-12) 3rd Generation Partnership Project; Technical Technical Specification Group Radio Access Network, Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements Requirements for support, radio resource, management, (Release 2014) December 3GPP R2-150372, Huawei, HiSilicon, Introduce PUCCH on SCell for CA beyond 5 carriers, February 2015
  • Non-Patent Document 3 may have the following problems.
  • Option 1 requires an explicit Activation / Deactivation MAC CE transmission to deactivate the activated SCells. Therefore, there may be additional delay due to this redundant Activation / Deactivation-MAC-CE transmission.
  • One of the objects to be achieved by the embodiments disclosed herein is that one or more SCells including the first SCell with respect to the first SCell that has already been added or newly added.
  • the uplink control channel eg, PUCCH
  • the uplink control information eg, CSI
  • a wireless terminal includes a wireless transceiver for communicating with a wireless station, and at least one processor configured to perform carrier aggregation with the wireless station using the wireless transceiver.
  • the at least one processor is used for transmission of uplink control information (UCI) for at least one SCell including the first SCell in a first secondary cell (SCell) of the carrier aggregation.
  • UCI uplink control information
  • SCell secondary cell
  • a method performed in a wireless terminal communicating with a wireless station is: (A) receiving one or more first downlink signaling messages including secondary cell (SCell) settings for carrier aggregation from the radio station and adding one or more SCells of the carrier aggregation; The one or more SCells are initially deactivated; (B) receiving one or more second downlink signaling messages including an activation instruction from the wireless station and activating part or all of the one or more SCells according to the activation instruction; And (c) used to transmit uplink control information (UCI) for at least one SCell including the first SCell in the first SCell that has already been added or newly added according to the SCell configuration.
  • UCI uplink control information
  • One or more activated SCells that are in an activated state among the at least one SCell are not received when receiving a third downlink signaling message including an information element indicating that the first uplink control channel is set. Deactivate, including.
  • the wireless station includes a wireless transceiver for communicating with a wireless terminal, and at least one processor configured to perform carrier aggregation with the wireless terminal using the wireless transceiver.
  • the at least one processor is used for transmission of uplink control information (UCI) for at least one SCell including the first SCell in a first secondary cell (SCell) of the carrier aggregation.
  • UCI uplink control information
  • SCell secondary cell
  • a method performed in a radio station configured to perform carrier aggregation with a radio terminal includes at least one first SCell included in the first secondary cell (SCell) of the carrier aggregation.
  • SCell first secondary cell
  • a downlink signaling message including an information element instructing to set up a first uplink control channel used for transmission of uplink control information (UCI) for one SCell is completed to the wireless terminal , Including thinking that one or more activated SCells in the activated state among the at least one SCell are deactivated by the wireless terminal.
  • UCI uplink control information
  • the program includes a group of instructions (software code) for causing the computer to perform the method according to the second or fifth aspect described above when read by the computer.
  • uplink control information eg, CSI
  • CSI uplink control information
  • An apparatus, method, and program that do not involve the release and re-addition of one or more SCells and contribute to the reduction of the number of control signaling when setting the uplink control channel (eg, PUCCH) to be used. Can be provided.
  • FIG. 5 is a flowchart illustrating an example of an operation of the wireless terminal according to the first embodiment. It is a figure which shows the 1st example of the process which adds new S-PCG to a radio
  • EPS Evolved Packet System
  • SAE System Architecture Evolution
  • 3GPP UMTS 3GPP2 CDMA2000 systems (1xRTT, HRPD (High Rate Packet Data)
  • GSM Global System for Mobile communications
  • GPRS registered general packet radio service
  • WiMAX WiMAX
  • FIG. 1 shows a configuration example of a wireless communication system according to some embodiments including this embodiment.
  • the wireless communication system includes at least one wireless terminal (UE) 1 and a wireless base station (eNB) 2.
  • eNB2 provides a plurality of cells using a plurality of component carriers (CC) having different frequencies.
  • the eNB 2 provides a cell 21 (Cell 1, eg, 800 MHz), a cell 22 (Cell 2, eg, 2 GHz), and a cell 23 (Cell 3, eg, 3.5 GHz).
  • a remote radio unit 3 is called Remote Radio Head (RRH) or Remote Radio Equipment (RRE).
  • Each UE 1 is configured to support carrier aggregation (CA) and communicate with the eNB 2 using a plurality of CCs (or a plurality of cells).
  • CA carrier aggregation
  • UE1A performs CA which uses the cell 21 as PCell and uses the cell 22 as SCell.
  • UE1B performs CA which uses the cell 22 as PCell and uses the cell 21 and the cell 23 as SCells.
  • Each UE1 supports the above PUCCHCon SCell (or SCell PUCCH). That is, each UE 1 is configured to transmit uplink control information (UCI) not only on the PCell PUCCH but also on the SCell PUCCH when performing CA.
  • UCI includes control information related to the downlink, and includes, for example, Channel State Information (CSI).
  • the CSI includes at least one of Channel Quality Indicator (CQI), Pre-Coding Matrix Indicator (PMI), and Rank Indicator (RI).
  • the UCI may also include an HARQ confirmation response (i.e. ACK, NACK) regarding downlink data reception.
  • a radio resource scheduling request (SR) for uplink data transmission may be transmitted in the PUCCH of the SCell.
  • SR radio resource scheduling request
  • UE1 transmits UCI for PCell or PCell included in Primary ⁇ ⁇ ⁇ PCG (P-PCG) and UCI for at least one SCell on the PUCCH of the PCell, and Secondary PCG (S -UCI for one or a plurality of SCells including SCell (ie, PUCCH SCell) for transmitting PUCCH included in -PCG) may be transmitted on the PUCCH of the PUCCH SCell.
  • P-PCG Primary ⁇ ⁇ ⁇ PCG
  • S -UCI Secondary PCG
  • SCell SCell secondary PCG
  • SCell ie, PUCCH SCell
  • PUCCH SCell for which PUCCH is set may be a SCell that has already been added to UE1 and belongs to P-PCG or S-PCG, or is newly added to UE1.
  • SCell may be used.
  • Setting a PUCCH in a SCell that has already been added to UE1 or newly added may be performed, for example, along with a new addition of S-PCG (referred to as S-PCG-addition).
  • S-PCG-addition a new addition of S-PCG
  • setting PUCCH to SCell that has already been added to UE1 or newly added means that PUCCH SCell change (S-PCG change) within already added (set) S-PCG May also be performed.
  • ENB2 is configured to transmit a downlink (DL) signaling message related to S-PCG setting to UE1 for S-PCG addition or S-PCG change.
  • the DL signaling message includes an information element indicating S-PCG addition or S-PCG change accompanying setting PUCCH in the SCell of UE1.
  • UE1 is configured to set all SCells in the S-PCG to be added or changed to a deactivate state (or to be regarded as a deactivate state) Has been. Specifically, UE1 deactivates (or regards as a deactivated state) one or more activated SCells that were in the activated state in the S-PCG to be added or changed. On the other hand, UE1 maintains one or more deactivated SCells that were originally deactivated in the S-PCG to be added or changed in the deactivated state (or continue to be regarded as deactivated).
  • the concept of S-PCG may not be used. That is, eNB2 sets PUCCH used for transmission of UCI for at least one SCell including the first SCell in the first SCell that has already been added or newly added to UE1. A DL signaling message including the indicated information element is transmitted to UE1.
  • UE1 sets all of these at least one SCell to a deactivate state (or regards it as a deactivate state). Specifically, UE1 deactivates (or regards as a deactivated state) one or a plurality of activated SCells that have been activated among these at least one SCell.
  • UE1 maintains one or more deactivated SCells originally in the deactivated state among these at least one SCell in the deactivated state (or continues to be regarded as the deactivated state).
  • the addition, change and release of SCell in the existing CA are performed in the RRC layer, and the RRC Connection Reconfiguration message is used. Therefore, the DL signaling message transmitted from eNB2 to UE1 for S-PCGPCaddition or S-PCG change including setting PUCCH in SCell may typically be an RRC Connection Reconfiguration message.
  • UE1 in response to reception of the DL signaling message, UE1 considers that one or more activated SCells that have been activated or added in the S-PCG to be added or changed are deactivated (consider)
  • the lower layer may be configured by the RRC layer. Instead, UE1 may set the lower layer by the RRC layer so that the activated SCell is changed to the deactivated state (change or move).
  • the lower layer includes a MAC layer.
  • eNB2 may operate similarly to UE1. That is, eNB2 transmitted to UE1 a DL signaling message including an information element indicating that a PUCCH used for transmission of UCI for at least one SCell including the first SCell is set in the first SCell. In this case, it may be configured that one or more activated SCells in the activated state among the at least one SCell are considered to be deactivated by the UE1. More specifically, when the eNB 2 completes transmission of the DL signaling message, the eNB 2 configures its lower layer by the RRC layer so that the one or more activated SCells are deactivated by the UE 1 (configure). May be.
  • the UE 1 is a DL signaling message (eg, RRC Connection Reconfiguration message) for S-PCG addition or S-PCG change including setting PUCCH in the SCell.
  • a DL signaling message eg, RRC Connection Reconfiguration message
  • S-PCG addition or S-PCG change including setting PUCCH in the SCell.
  • the apparatus and method shown in this embodiment set the PUCCH used for transmitting UCI for one or a plurality of SCells for the first SCell that has already been added or newly added. In this case, it is possible to contribute to suppressing the number of control signaling (or the amount of control information) without releasing and re-adding one or more SCells.
  • FIG. 2 is a flowchart showing an example of operation of UE1 (processing 200).
  • Blocks 201 and 202 are similar to SCell configuration and activation in an existing CA. That is, in block 201, UE1 receives the RRC
  • UE1 receives Activation / Deactivation
  • UE1 is used to transmit UCI for at least one SCell (ie, S-PCG) that includes the first SCell in the first SCell that has already been added or is newly added.
  • RRC Connection Reconfiguration message indicating that PUCCH to be set is received.
  • UE1 deactivates activated SCell (s) among these at least one SCell.
  • UE1 maintains deactivated SCell (s) of these at least one SCell in the deactivated state (or continues to be regarded as the deactivated state).
  • UCI ie, CSI
  • UCI for activated SCell (s) to be deactivated within a predetermined period based on the reception of the RRC Connection Reconfiguration message. It may operate to stop transmission of reporting.
  • the starting point of the predetermined period is when the RRCRRConnection Reconfiguration message is received, when the content of the RRC Connection Reconfiguration message is recognized, or when the RRC layer sets the deactivation of activated SCell (s) to the lower layer ( It may be the point of time).
  • the predetermined period may be specified in units of subframes.
  • UE1 when UE1 receives the RRC ⁇ Connection Reconfiguration message indicating that PUCCH is set in the first SCell in subframe #n, subframe # n + 8 It may operate to stop CSI reporting by
  • UE1 prior to receiving the RRC Connection Reconfiguration message in block 203, UE1 has an explicit MAC CE for deactivating activated SCell (s) in the S-PCG. Does not need to be received. Therefore, the procedure of FIG. 2 can contribute to suppressing the number of control signaling (or the amount of control information) when setting PUCCH for SCell.
  • the PUCCHPCSCell of the added S-PCG may be a SCell belonging to the P-PCG or another S-PCG (that is, already set in the UE 1), or with the addition of the S-PCG SCell newly added to UE1 may be sufficient.
  • FIG. 3 shows a first example regarding the addition of S-PCG.
  • UE1 is set with PCG # 1 (i.e., P-PCG) composed of PCell 301 and SCell 302 (SCell1).
  • SCell 302 is activated, so UE1 transmits the UCI (here CSI) for PCell 301 and SCell 302 on PUCCH 321 of PCell 301.
  • UCI here CSI
  • UE1 receives RRC message 341 (e.g., “RRC” Connection “Reconfiguration message”) including SCell PUCCH configuration (SCell PUCCH Configuration).
  • the SCell PUCCH setting indicates that a new PCG # 2 (i.e., S-PCG) including the already added SCell 302 is added and that a PUCCH 322 is set in the SCell 302.
  • the SCell PUCCH setting included in the RRC message 341 indicates that the UCI (e.g., CSI) for the SCells 302 is transmitted on the PUCCH 322 set in the SCell 302.
  • the SCell PUCCH setting may include only setting information related to newly added PCG # 2, or may include setting information related to all PCGs, that is, PCG # 1 and PCG # 2.
  • the UE1 When the UE1 receives the RRC message 341, the UE1 recognizes that the PUCCH 322 is set in the SCell302 (SCell1), and puts the SCell302 (SCell1) into a deactivated state. More specifically, the RRC layer of UE1 configures a lower layer (MAC layer) so that SCell 302 (SCell1) is considered to be a deactivated state (consider). Then, the MAC layer of UE1 deactivates SCell 302, stops (associated with SCell1) sCellDeactivationTimer associated with SCell 302 (SCell1), and stops all Hybrid Automatic Repeat Requests associated with SCell 302 (SCell1). (HARQ) Flush buffers.
  • MAC layer MAC layer
  • the MAC layer of UE1 stops the transmission of UCI (e.g., CSI) for SCell 302 (SCell1) in PUCCH 321 of PCell 301.
  • UCI e.g., CSI
  • the UE 1 When the UE 1 receives the RRC message 341, the UE 1 must stop transmission of the UCI (eg, CSI) for the SCell 302 in the PCell 301 within a predetermined period based on the reception of the RRC message 341 ( requirement).
  • sCellDeactivationTimer may not be applied (not used) to SCell 302 (SCell1), that is, PUCCHCSCell.
  • UE1 receives Activation / Deactivation MAC CE342 which activates SCell302 (SCell1) from eNB2.
  • SCell1 activates SCell 302 (SCell1).
  • UE1 performs the following operations on the activated SCell 302 (SCell1): Sending SRS on SCell 302 when uplink CA is configured; Monitoring PDCCH in SCell 302; In the case of cross-carrier scheduling, monitor the PDCCH for SCell 302 (in PCell 301), and perform CSI reporting for SCell 302.
  • UE1 starts (or restarts) sCellDeactivationTimer associated with SCell302 (SCell1) and triggers Power Headroom Report (PHR). Furthermore, as in the case of the existing CA, when UE1 receives Activation / Deactivation MAC CE342 in subframe #n, UE1 at the latest by subframe # n + 24 or # n + 34 (no later than subframe # n + 24 or #n +34), a requirement may be imposed that transmission of a valid CSI report (valid CSI report) must be initiated.
  • FIG. 4 is a sequence diagram showing an example (process 400) of the S-PCG addition procedure related to the first example shown in FIG.
  • Blocks 401 to 403 correspond to reception by the UE1 of the RRC message 341 shown in FIG. That is, in block 401, eNB2 transmits RRC Connection Reconfiguration message including SCell PUCCH configuration (SCell PUCCH Configuration) to UE1.
  • SCell PUCCH Configuration SCell PUCCH Configuration
  • UE1 sets PUCCH 322 to SCell302 (SCell1), transmits an RRC Connection Reconfiguration Complete message to eNB2 (402), and deactivates SCell302 (SCell1) (deactivate). (403).
  • UE1 may transmit an RRC Connection Reconfiguration Complete message to eNB2 after the start or completion of deactivation of SCell302 (SCell1).
  • Blocks 404 to 406 correspond to reception by UE1 of Activation / Deactivation MAC CE342 shown in FIG. That is, in block 404, eNB2 transmits Activation / Deactivation
  • SCell1 SCell1
  • CQI effective CSI
  • FIG. 5 shows an example of the S-PCG addition procedure (process 500) regarding the comparative example.
  • the eNB 2 explicitly transmits Activation / Deactivation MAC CE that deactivates the SCell 302 (SCell1) to the UE 1.
  • the UE1 deactivates the SCell 302 (SCell1) (502).
  • the eNB 2 transmits an RRC Connection Reconfiguration message including the SCell PUCCH configuration (SCell PUCCH Configuration) to the UE1.
  • UE1 In response to receiving the RRCRRConnection Reconfiguration message, UE1 sets PUCCH 322 to SCell302 (SCell1), and transmits an RRC Connection Reconfiguration Complete message to eNB2 (504).
  • SCell1 SCell1
  • RRC Connection Reconfiguration Complete message 504.
  • the example of FIG. 4 is an explicit activation / deactivation transmission of MAC cell CE to deactivate SCell 302 (SCell1) in which PUCCH 322 is set (ie, FIG. 5). 5 blocks 501) are not required. Therefore, the procedure of FIG. 4 can suppress the number of control signaling (or the amount of control information) when setting the PUCCH 322 for the SCell 302 (SCell1) as compared to the procedure of FIG.
  • FIG. 6 shows a second example regarding the addition of S-PCG.
  • UE1 is set with PCG # 1 (i.e., P-PCG) composed of PCell 601, SCell 602 (SCell1), and SCell 603 (SCell2).
  • PCG # 1 i.e., P-PCG
  • SCells 602 and 603 are activated, so UE1 transmits UCI (e.g., CSI) for PCell 601 and SCells 602 and 603 on PUCCH 621 of PCell 601.
  • UCI e.g., CSI
  • UE1 receives an RRC message 641 (e.g., “RRC Connection Reconfiguration message) including SCell PUCCH configuration (SCell PUCCH Configuration).
  • the SCell PUCCH setting indicates that a new PCG # 2 (i.e., S-PCG) including already added SCells 602 and 603 is added and that a PUCCH 622 is set in the SCell 602 (SCell1).
  • the SCell PUCCH setting included in the RRC message 641 indicates that the UCI (e.g., CSI) for the SCells 602 and 603 is transmitted on the PUCCH 622 set in the SCell 602.
  • the SCell PUCCH setting may include only setting information related to newly added PCG # 2, or may include setting information related to all PCGs, that is, PCG # 1 and PCG # 2.
  • the UE1 When the UE1 receives the RRC message 641, the UE1 recognizes that the PUCCH 622 is set in the SCell602 (SCell1), sets the SCell602 (SCell1) to the deactivated state, and further sets the SCell603 (SCell2) to the deactivated state.
  • SCell1 SCell1
  • SCell2 SCell1
  • SCell2 SCell2
  • SCell3 SCell2
  • UE1 receives Activation / Deactivation MAC CE642 that activates SCells 602 and 603 from eNB2.
  • UE1 activates SCells 602 and 603.
  • a specific example of the requirements imposed on UE1 regarding the operation of UE1 regarding activated SCells 602 and 603 and the start (or resumption) of CSI reporting is as described with reference to FIG.
  • FIG. 7 is a sequence diagram showing an example (process 700) of the S-PCG addition procedure related to the second example shown in FIG.
  • the processing of blocks 701 to 706 shown in FIG. 7 is basically the same as the processing of blocks 401 to 406 shown in FIG.
  • the RRC Connection Reconfiguration message transmitted in block 701 indicates that the UCI (e.g., CSI) for SCells 602 and 603 is transmitted in PUCCH 622 of SCell 602.
  • the RRC Connection Reconfiguration message at block 701 indicates that PCG # 2 (i.e., S-PCG) including SCells 602 and 603 is added. Accordingly, UE1 deactivates SCells 602 and 603 at block 703.
  • PCG # 2 i.e., S-PCG
  • UE1 receives Activation / Deactivation MAC CE that activates SCells 602 and 603 in block 704 and activates SCells 602 and 603 (705). Then, when UE1 receives Activation / Deactivation MAC CE in subframe #n, by no later than subframe # n + 24 or # n + 34 (no later than subframe # n + 24 or # n + 34), SCell602 (SCell1) In the PUCCH 622, effective CSI (CQI) transmission related to the SCells 602 and 603 is started (706).
  • CQI effective CSI
  • FIG. 8 shows a third example regarding the addition of S-PCG.
  • UE1 is set with PCG # 1 (i.e., P-PCG) composed of PCell 801, SCell 802 (SCell1), and SCell 803 (SCell2).
  • PCell 802 is in an activated state, but SCell 803 is in a deactivated state. Therefore, UE1 transmits UCI (e.g., CSI) for PCell 801 and SCell 802 (SCell1) in PUCCH 821 of PCell 801, and does not perform CSI reporting for SCell 803 (SCell2).
  • UCI e.g., CSI
  • UE1 receives RRC message 841 (e.g., “RRC” Connection “Reconfiguration message”) including the SCell PUCCH configuration (SCell PUCCH Configuration).
  • the SCell PUCCH setting indicates that a new PCG # 2 (i.e., S-PCG) including already added SCells 802 and 803 is added, and that a PUCCH 822 is set in the SCell 803 (SCell2).
  • the SCell PUCCH setting included in the RRC message 841 indicates that the UCI (e.g., CSI) for the SCells 802 and 803 is transmitted on the PUCCH 822 set in the SCell 803.
  • the SCell PUCCH setting may include only setting information related to newly added PCG # 2, or may include setting information related to all PCGs, that is, PCG # 1 and PCG # 2.
  • the UE1 When the UE1 receives the RRC message 841, it recognizes that the PUCCH 822 is set in the deactivated SCell 803 (SCell2), and not only the SCell 803 (SCell2) but also the UCI (eg, CSI) of the SCell 802 (SCell1) Recognize that it will be sent. In response to this, UE1 maintains the deactivated SCell 803 (SCell2) in the deactivated state, and sets the activated SCell 802 (SCell1) to the deactivated state.
  • SCell2 deactivated SCell 803
  • a specific example of the requirements imposed on UE1 regarding UE1 RRC and MAC layer processing and CSI reporting stop is as described with reference to FIG.
  • UE1 receives Activation / Deactivation MAC CE842 that activates SCells 802 and 803 from eNB2.
  • UE1 activates SCells 802 and 803.
  • the specific example of the requirements imposed on UE1 regarding the operation of UE1 regarding activated SCells 802 and 803 and the start (or resumption) of CSI reporting is as described with reference to FIG.
  • FIG. 9 is a sequence diagram showing an example (process 900) of the S-PCG addition procedure related to the third example shown in FIG.
  • the processing of blocks 901 to 906 shown in FIG. 9 is basically the same as the processing of blocks 401 to 406 shown in FIG.
  • the RRC Connection Reconfiguration message transmitted in block 901 indicates that the UCI (e.g., CSI) for SCells 802 and 803 is transmitted in PUCCH 822 of SCell 803.
  • the RRC Connection Reconfiguration message at block 901 indicates that PCG # 2 (i.e., S-PCG) including SCells 802 and 803 is added. Therefore, in block 903, UE1 deactivates activated SCell802 in SCells802 and 803.
  • UE1 receives Activation / Deactivation MAC CE for activating SCells 802 and 803 in block 904, and activates SCells 802 and 803 (905). Then, when UE1 receives Activation / Deactivation MAC CE in subframe #n, at the latest by subframe # n + 24 or # n + 34 (no later than subframe # n + 24 or # n + 34), SCell 803 (SCell2) In the PUCCH 822, effective CSI (CQI) transmission for the SCells 802 and 803 is started (906).
  • CQI effective CSI
  • FIG. 10 shows a fourth example regarding the addition of S-PCG.
  • a new SCell is added to UE1 along with the addition of S-PCG, and the new SCell is a PUCCH ⁇ SCell.
  • UE1 is set with PCG # 1 (i.e., P-PCG) composed of PCell 1001 and SCell 1002 (SCell1). SCell 1002 is in an activated state.
  • Cell 1003 (Cell2) is a cell or CC not set in UE1.
  • UE1 receives RRC message 1041 (e.g., “RRC Connection Reconfiguration message) including SCell configuration (SCell Configuration) and SCell PUCCH configuration (SCell PUCCH Configuration).
  • RRC message 1041 e.g., “RRC Connection Reconfiguration message” including SCell configuration (SCell Configuration) and SCell PUCCH configuration (SCell PUCCH Configuration).
  • SCell Configuration SCell Configuration
  • SCell PUCCH Configuration SCell PUCCH Configuration
  • the said SCell setting shows that Cell1003 is added to UE1 as SCell.
  • SCell PUCCH setting adds a new PCG # 2 (ie, S-PCG) composed of the already added SCells 1002 (SCell1) and the newly added SCell 1003 (SCell2), and SCell1003 (SCell2) Indicates that PUCCH1022 is set.
  • PCG # 2 ie, S-PCG
  • the SCell PUCCH setting included in the RRC message 1041 indicates that the UCI (e.g., CSI) for the SCells 1002 and 1003 is transmitted on the PUCCH 1022 set in the SCell 1003.
  • the SCell PUCCH setting may include only setting information related to newly added PCG # 2, or may include setting information related to all PCGs, that is, PCG # 1 and PCG # 2.
  • SCell2 SCell2
  • the added SCell 1003 SCell2 is initially in a deactivated state (deactivated state).
  • UE1 further recognizes that PUCCH1022 is set in a new SCell1003 (SCell2), and recognizes that not only SCell1003 (SCell2) but also UCI (eg, CSI) of SCell1002 (SCell1) is transmitted on PUCCH1022.
  • the UE 1 keeps the newly added and deactivated SCell 1003 (SCell2) in the deactivated state, and puts the activated SCell 1002 (SCell1) into the deactivated state.
  • a specific example of the requirements imposed on UE1 regarding UE1 RRC and MAC layer processing and CSI reporting stop is as described with reference to FIG.
  • UE1 receives Activation / Deactivation MAC CE1042 for activating SCells 1002 and 1003 from eNB2.
  • UE1 activates SCells 1002 and 1003.
  • the operation of UE1 regarding activated SCells 1002 and 1003 and specific examples of requirements imposed on UE1 regarding the start (or resumption) of CSI reporting are as described with reference to FIG.
  • FIG. 11 is a sequence diagram showing an example of the S-PCG addition procedure (processing 1100) related to the fourth example shown in FIG.
  • the processing of blocks 1101 to 1106 shown in FIG. 11 is basically the same as the processing of blocks 901 to 906 shown in FIG.
  • the RRC Connection Reconfiguration message transmitted in block 1101 includes a SCell configuration (SCell Configuration) for newly adding SCell 1003 to UE1.
  • SCell Configuration SCell Configuration
  • S-PCG change in this specification means a procedure in which PUCCH SCell is changed in an already added S-PCG.
  • the PUCCH SCell after the S-PCG change may be the SCell that belonged to the S-PCG before the S-PCG change, or it belongs to the P-PCG or another S-PCG before the S-PCG change. It may be a SCell, or a SCell that is newly added to the UE 1 as the S-PCG changes.
  • FIG. 12 shows an example of a change in S-PCG.
  • UE1 is set with PCGPC # 1 (ie, ieP-PCG) composed of PCell1201, and PCG # 2 (ie, S-PCG) composed of SCell1202 (SCell1) and SCell1203 (SCell2). ing.
  • PUCCH SCell in PCG # 2 is SCell1202 (SCell1), and SCells1202 and 1203 are activated. Therefore, UE1 transmits UCI (e.g., CSI) for PCell 1201 on PUCCH 1221 of PCell 1201, and transmits UCI (e.g., CSI) for SCells 1202 and 1203 on PUCCH 1222 of SCell 1202.
  • UCI e.g., CSI
  • UE1 receives the RRC message 1241 (e.g., “RRC” Connection “Reconfiguration message”) including the SCell PUCCH configuration (SCell PUCCH Configuration).
  • the SCell PUCCH setting indicates that the SCell (i.e., PUCCH SCell) that transmits the PUCCH 1222 is changed from SCell1202 (SCell1) to SCell1203 (SCell2).
  • the SCell PUCCH setting may include only setting information related to PCG # 2 to be changed, or may include setting information related to all PCGs, that is, PCG # 1 and PCG # 2.
  • UE1 When UE1 receives RRC message 1241, UE1 recognizes that PUCCH SCell is changed from SCell1202 (SCell1) to SCell1203 (SCell2). In response to this, UE1 puts SCells 1202 and 1203 into a deactivated state.
  • SCell1 SCell1
  • SCell2 SCell2
  • SCell2 SCell2
  • SCell2 SCell2
  • SCell2 SCell2
  • SCell2 and 1203 A specific example of the requirements imposed on UE1 regarding UE1 RRC and MAC layer processing and CSI reporting stop is as described with reference to FIG.
  • UE1 receives Activation / Deactivation MAC CE1242 for activating SCells 1202 and 1203 from eNB2.
  • UE1 activates SCells 1202 and 1203.
  • a specific example of the requirements imposed on UE1 regarding the operation of UE1 regarding activated SCells 1202 and 1203 and the start (or resumption) of CSI reporting is as described with reference to FIG.
  • FIG. 12 shows an example in which PUCCH is set in the already added SCell 1203 when the S-PCG (PCG (# 2) is changed.
  • a new SCell may be added to UE1, and the new SCell may be a PCG # 2 PUCCH SCell.
  • SCell addition SCellitionaddition
  • PCG addition PCG addition
  • PCG change PCG change
  • UE1 is set with PCG # 1 (ie, P-PCG) composed of PCell1301 and PCG # 2 (ie, S-PCG) composed of SCell1302 (SCell1) and SCell1303 (SCell2). ing.
  • Cell 1304 (Cell3) is a cell or CC that is not set in UE1.
  • PUCCH SCell in PCG # 2 is SCell 1302 (SCell1), and SCells 1302 and 1303 are activated.
  • UE1 transmits UCI (e.g., CSI) for PCell 1301 on PUCCH 1321 of PCell 1301, and transmits UCI (e.g., CSI) for SCells 1302 and 1303 on PUCCH 1322 of SCell 1302 (SCell1).
  • UCI e.g., CSI
  • UE1 receives the RRC message 1341 (e.g., “RRC Connection Reconfiguration message) including SCell configuration (SCell Configuration) and SCell PUCCH configuration (SCell PUCCH Configuration).
  • the said SCell setting shows that Cell1304 is added to UE1 as SCell.
  • the SCell PUCCH setting indicates that UCI (e.g., CSI) for a new SCell 1304 (SCell3) is transmitted on the PUCCH 1322 of SCell1302 (SCell1).
  • the SCell PUCCH setting indicates that the existing PCG # 2 is reconfigured so that a new SCell 1304 (SCell3) is added.
  • UE1 upon receiving the RRC message 1341, adds SCell1304 (SCell3). Similar to the existing CA, the added SCell 1304 (SCell3) is initially in a deactivated state (deactivated state). In some implementations, as shown in FIG. 13, UE1 may deactivate existing SCells 1302 and 1303 in PCG # 2 to which SCell 1304 (SCell3) is added. Alternatively, in some implementations, UE1 may not change activation status of existing SCells 1302 and 1303 in PCG # 2 to which SCell 1304 (SCell3) is added, and SCells 1302 and 1303 are in an activated state. It may be maintained as it is.
  • UE1 receives Activation / Deactivation-MAC-CE1342 from eNB2.
  • indicates activation of SCell1304.
  • SCells 1302 and 1303 are deactivated, Activation / DeactivationDeMAC CE 1342 further instructs activation of SCells 1302 and 1303.
  • UE1 activates SCell 1304 (and SCells 1302 and 1303).
  • PCG reconfiguration Such replacement (replacement) of SCell (s) between PCGs without changing PUCCH SCell is referred to as “PCG reconfiguration” in this specification.
  • PCG reconfiguration Such replacement (replacement) of SCell (s) between PCGs without changing PUCCH SCell is referred to as “PCG reconfiguration” in this specification.
  • PCG reconfiguration is different from the example of PCG addition (PCG) addition) and PCG change (PCG ⁇ change) described with reference to FIGS. It should be noted that no changes are made.
  • FIG. 14 shows a first example regarding S-PCG reconfiguration.
  • UE1 has PCG1 # 1 (ie, P-PCG) composed of PCell1401, PCG # 2 (ie, S) composed of SCell1402 (SCell1), SCell1403 (SCell2), and SCell1404 (SCell3).
  • PCG PCG1 # 1
  • PCG # 2 ie, S
  • SCell1 SCell1402
  • SCell2 SCell1
  • SCell2 SCell1
  • SCell2 SCell1
  • SCell2 SCell1403
  • SCell3 SCell1404
  • UE1 transmits UCI (e.g., CSI) for PCell 1401 in PUCCH 1421 of PCell 1401, and transmits UCI (e.g., CSI) for SCells 1402, 1403, and 1404 in PUCCH 1422 of SCell 1403 (SCell2).
  • UCI e.g., CSI
  • UE1 receives RRC message 1441 (e.g., RRC Connection Reconfiguration message) including SCell PUCCH configuration (SCell PUCCH Configuration).
  • the SCell PUCCH setting indicates that the PUCCH Cell Group (PCG) to which the SCell 1402 (SCell1) belongs is changed from PCG # 2 to PCG # 1.
  • the SCell PUCCH setting indicates that UCI (e.g., CSI) for SCell 1402 (SCell1) is transmitted in PUCCH 1421 of PCell 1401.
  • UE1 When UE1 receives RRC message 1441, UE1 reconfigures PCGPC # 1 and PCG # 2 so that UCI (e.g., CSI) for SCell1402 (SCell1) is transmitted in PUCCH1421 of PCell1401.
  • UCI e.g., CSI
  • SCell1 deactivates SCell 1402 (SCell1) whose PCG is changed, and further deactivates SCells 1403 and 1404 in PCG # 2 from which SCell 1402 (SCell1) is removed. It may be activated.
  • UE1 deactivates only SCell 1402 (SCell1) where the PCG is changed, and changes the activation status of SCells 1403 and 1404 in PCG # 2 where SCell 1402 (SCell1) is removed. It does not have to be. That is, UE1 may maintain SCells 1403 and 1404 in the activated state. Instead, in some implementations, UE1 maintains SCell 1402 (SCell1) in which PCG is changed in an activated state, and deactivates SCells 1403 and 1404 in PCG # 2 from which SCell 1402 (SCell1) is removed. May be. Furthermore, instead of this, in some implementations, UE1 can change the PCG from PCG # 2 (ie S-PCG) including only SCell to PCG # 1 (ie P-PCG) including PCell. This may be maintained in the activated state.
  • PCG # 2 ie S-PCG
  • PCG # 1 ie P-PCG
  • UE1 receives Activation / Deactivation MAC CE1442 from eNB2.
  • Activation / Deactivation MAC CE 1442 instructs activation of SCell (s) deactivated in response to reception of the RRC message 1441.
  • CE1442 directs activation of SCell1402 (SCell1), SCell1403 (SCell2), and SCell1404 (SCell3).
  • SCell1 SCell1
  • SCell2 SCell1
  • UE1 has PCG1 # 1 (ie, P-PCG) composed of PCell1501, and PCG # 2 (ie, ⁇ ⁇ S) composed of SCell1502 (SCell1), SCell1503 (SCell2), and SCell1504 (SCell3).
  • PCG and PCG # 3 ie, S-PCG
  • SCell 1505 (SCell4) and SCell1506 (SCell5) are set.
  • the PUCCH SCell in PCG # 2 is SCell1502 (SCell1)
  • the PUCCH SCell in PCG3 # 3 is SCell1506 (SCell5).
  • UE1 transmits UCI (eg, CSI) for PCell 1501 in PUCCH 1521 of PCell 1501, transmits UCI (eg, CSI) for SCells 1502, 1503, and 1504 in PUCCH 1522 of SCell 1502 (SCell1), and SCells 1505 And UCI (eg, CSI) for 1506 are transmitted in PUCCH 1523 of SCell 1506 (SCell5).
  • UCI eg, CSI
  • UE1 receives the RRC message 1541 (e.g., “RRC” Connection “Reconfiguration message”) including the SCell PUCCH configuration (SCell PUCCH Configuration).
  • the SCell PUCCH setting indicates that the PCG to which the SCell 1504 (SCell3) belongs is changed from PCG # 2 to PCG # 3.
  • the SCell PUCCH configuration indicates that UCI (e.g., CSI) for SCell1504 (SCell3) is transmitted in PUCCH1523 of SCell1506 (SCell5).
  • UE1 When UE1 receives RRC message 1541, UE1 reconfigures PCGPC # 2 and PCG # 3 so that UCI (e.g., eCSI) for SCell1504 (SCell3) is transmitted in PUCCH 1523 of SCell1506 (SCell5).
  • UCI e.g., eCSI
  • SCell3 As shown in FIG. 15A, UE1 deactivates SCell 1504 (SCell3) in which PCG is changed, deactivates SCells 1502 and 1503 in PCG # 2 from which SCell 1504 (SCell3) is removed, SCells 1505 and 1506 in PCG # 3 to which SCell 1504 (SCell3) is added may be further deactivated.
  • UE1 may deactivate only SCell 1504 (SCell3) for which the PCG is changed, and may not change the activation status of other SCells 1502, 1503, 1505, and 1506. That is, UE1 may maintain SCells 1502, 1503, 1505, and 1506 in the activated state. Instead, in some implementations, UE1 may deactivate SCells 1505 and 1506 in PCGPC # 3 to which SCell 1504 (SCell3) and SCell 1504 (SCell3) to which the PCG is changed are added. That is, UE1 does not need to change the activation status of SCells 1502 and 1503 in PCG # 2 from which SCell 1504 (SCell3) is excluded.
  • UE1 receives Activation / Deactivation MAC CE1542 from eNB2.
  • Activation / Deactivation MAC CE 1542 instructs activation of the deactivated SCell (s) in response to reception of the RRC message 1541.
  • Activation / Deactivation MAC CE 1542 instructs activation of SCells 1502-1506.
  • UE1 activates SCells 1502-1506.
  • ⁇ Second Embodiment> a specific example of an information element transmitted from the eNB 2 to the UE 1 in order to set a PUCCH in a SCell that has already been added or is newly added will be described.
  • the information element corresponds to, for example, the information element included in the RRC CONNECTION RECONFIGURATION message transmitted in the block 203 of FIG. 2, and further, the SCell PUCCH setting (SCell PUCCH Configuration).
  • the information element may indicate a PUCCH Cell Group (PCG).
  • PCG PUCCH Cell Group
  • the information element may be defined to give PUCCH Cell Group index to each cell.
  • the information element may be defined to generate a list of cells included in each PUCCHCCell Group.
  • FIG. 16 shows an example of an information element that assigns a PUCCH Cell Group index to each cell. Specifically, FIG. 16 shows an improvement of the sCellToAddModList information element (Information Element (IE)) in the RRC Connection Reconfiguration message.
  • “PUCCH Cell Group configuration” (1601) shown in FIG. 16 is defined to give a PUCCH Cell Group index to each cell.
  • “SCellIndex” (1602) is an identifier used to specify the SCell to be added or modified.
  • “PUCCH Cell Group configuration” (1601) assigns “PUCCH Cell Group index (i.e., pucch-CellGroupIndex-r13)” to the SCell specified by “SCellIndex” (1602).
  • PUCCH Cell Group index is an identifier used to specify PUCCH Cell Group. Note that the maximum value 31 of “PUCCH Cell Group Index” is an example based on 32, which is considered as the maximum number of CCs that can be CAed, and may be another value.
  • the PCG Index of the P-PCG including PCell may be set to 0 by default.
  • “PUCCH Cell Group configuration” (1601) assigns PCG ⁇ ⁇ Index only to SCells belonging to S-PCG including only one or a plurality of SCells, and PCG Index to SCells belonging to P-PCG. May not be explicitly given.
  • “PUCCH Cell Group configuration” (1601) may explicitly assign PCG Index to all SCells.
  • UE1 In the case of assigning PUCCH Cell Group index to each cell (eg, Fig. 16), UE1 is concerned when PCG Index is set for a certain SCell, or when already set PCG Index is changed. SCells and other SCells affected thereby may be deactivated.
  • the UE1 receives the received PUCCH? Cell PUCCH Cell Group configuration may be added according to Group index (1601). Also, UE1 receives (a) when SCellIndex (1602) included in sCellToAddModList ⁇ ⁇ is included in the current UE configuration and PUCCH Cell (Group160index (1601) is included in sCellToAddModList.
  • Modify PUCCH Cell Group configuration according to PUCCH Cell Group index (modify)
  • the MAC layer of UE1 is configured (configured) to change the SCell to the deactivated state by the RRC layer, the SCell is deactivated and associated with the SCell (associated with SCell1 ) Stop sCellDeactivationTimer and flush all HARQ buffers associated with the SCell.
  • the MAC layer of UE1 stops the transmission of UCI (e.g. CSI) for the SCell.
  • UCI e.g. CSI
  • FIG. 17 shows an example of an information element for generating a list of cells included in each PUCCH Cell Group.
  • FIG. 17 shows “pucch-CellGroup” IE (1701) and “CellGroupList” IE (1704) newly defined in the RRCRRConnection Reconfiguration message.
  • “Pucch-CellGroup” IE (1701) includes “pucch-CellGroupIndex” (1702) and “cellGroupList” (1703).
  • “Pucch-CellGroupIndex” (1702) is an identifier used to specify PUCCH Cell Group (PCG).
  • CellGroupList As shown in “CellGroupList” IE (1704), “cellGroupList” (1703) includes one or a plurality of SCell identifiers (sCellIndex) included in the PCG specified by “pucch-CellGroupIndex” (1702). Including.
  • the PCG Index of the P-PCG including PCell may be set to 0 by default.
  • a PCG index may be assigned only to an S-PCG including only one or a plurality of SCells, and a list of SCell (s) included in the S-PCG may be created. And it is not necessary to explicitly give PCG
  • a list of SCell (s) included therein May be created explicitly.
  • the PCell may be excluded from the list.
  • the PCell may be explicitly listed in the list.
  • PUCCH CellGroupList IE (1704) of FIG. 17 as Alt. 1
  • PUCCH Cell is PCell
  • PUCCH Cell Index is not explicitly assigned
  • PUCCH Cell is SCell.
  • PUCCH CellPUIndex may be given only in some cases.
  • SCellIndex may be used as PUCCH Cell Index.
  • the PUCCH Cell Index is not assigned, it means that the UCI (e.g., CSI) of the SCell is transmitted on the PUCCH of the PCell.
  • PUCCH “Cell Index” may be explicitly assigned to all SCells.
  • ServCellIndex may be used as PUCCH Cell Index.
  • UE1 All SCells may be deactivated.
  • the PCG is an S-PCG including only a SCell
  • the UE1 deactivates all SCells in the S-PCG
  • the PCG is a P-PCG including a PCell
  • SCell may be maintained in an activated state.
  • UE1 may operate as follows.
  • the UE1 performs PUCCHCCell Group according to the received “pucch-CellGroup” IE (1701). May be added. Otherwise (that is, when “pucch-CellGroupIndex” (1702) included in the “pucch-CellGroup” IE (1701) is included in the current UE configuration), the UE1 receives the “pucch-CellGroup” IE ( 1701), PUCCH Cell Group may be modified.
  • the UE1 changes its SCell to a deactivated state (change or move) if the SCell is currently in an activated state by the RRC layer. If the SCell is currently in the deactivated state, the lower layer may be configured by the RRC layer so that the SCell is considered deactivated (consider).
  • ⁇ Third Embodiment> a specific example of an information element transmitted from the eNB 2 to the UE 1 in order to set a PUCCH in a SCell that has already been added or is newly added will be described.
  • the information element corresponds to, for example, the information element included in the RRC CONNECTION RECONFIGURATION message transmitted in the block 203 of FIG. 2, and further, the SCell PUCCH setting (SCell PUCCH Configuration).
  • the information element may indicate a cell in which a PUCCH carrying UCI for each cell is transmitted (referred to as PUCCH Cell).
  • PUCCH Cell a cell in which a PUCCH carrying UCI for each cell is transmitted
  • the information element may be defined to give PUCCH Cell index to each cell.
  • FIG. 18 shows an example of an information element that assigns a PUCCH cell index to each cell. Specifically, FIG. 18 shows an improvement of the sCellToAddModList information element in the RRC Connection Reconfiguration message.
  • “PUCCH Cell configuration” (1801) shown in FIG. 18 is defined to give “PUCCH Cell index (i.e., pucch-CellIndex-r13)” to each cell.
  • “PUCCH Cell index” is an identifier used to identify a PUCCH Cell that is responsible for UCI transmission for each cell.
  • the PUCCH Cell Index is not explicitly assigned, and only when the PUCCH Cell is a SCell, the PUCCH Cell Index is assigned. May be.
  • SCellIndex may be used as PUCCH Cell Index.
  • the PUCCH Cell Index is not assigned, it means that the UCI (e.g., CSI) of the SCell is transmitted on the PUCCH of the PCell.
  • PUCCH Cell Index may be explicitly assigned to all SCells.
  • ServCellIndex may be used as PUCCH Cell Index.
  • UE1 In the case of assigning PUCCH Cell Index to each cell (eg, FIG. 18), UE1 is configured when PUCCH Cell Index is changed for a certain SCell, or when PUCCH Cell Index already set is changed, The SCell and other SCells affected by the SCell may be deactivated.
  • UE1 receives the received PUCCH? Cell? Index.
  • the lower layer may be configured by the RRC layer to use the PUCCH on the SCell indicated by.
  • UE1 includes SCellIndex (1802) included in sCellToAddModList in the current UE configuration and PUCCH Cell Index (1801) is included in sCellToAddModList
  • UE1 (a) receives PUCCH
  • the lower layer is configured by the RRC layer to use the PUCCH on the SCell indicated by Cell Index.
  • FIG. 19 is a block diagram illustrating a configuration example of UE1.
  • the Radio Frequency (RF) transceiver 1901 performs analog RF signal processing in order to communicate with the eNB 2.
  • Analog RF signal processing performed by RF transceiver 1901 includes frequency up-conversion, frequency down-conversion, and amplification.
  • RF transceiver 1901 is coupled to antenna 1902 and baseband processor 1903. That is, the RF transceiver 1901 receives modulation symbol data (or OFDM symbol data) from the baseband processor 1903, generates a transmission RF signal, and supplies the transmission RF signal to the antenna 1902. Further, the RF transceiver 1901 generates a baseband received signal based on the received RF signal received by the antenna 1902 and supplies this to the baseband processor 1903.
  • modulation symbol data or OFDM symbol data
  • the baseband processor 1903 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication.
  • Digital baseband signal processing consists of (a) data compression / decompression, (b) data segmentation / concatenation, (c) ⁇ transmission format (transmission frame) generation / decomposition, and (d) transmission path encoding / decoding. , (E) modulation (symbol mapping) / demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT).
  • control plane processing includes layer 1 (eg, transmission power control), layer 2 (eg, radio resource management, hybrid automatic repeat request (HARQ) processing), and layer 3 (eg, attach, mobility, and call management). Communication management).
  • the digital baseband signal processing by the baseband processor 1903 includes signal processing of the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, MAC layer, and PHY layer. But you can. Further, the control plane processing by the baseband processor 1903 may include Non-AccessatumStratum (NAS) protocol, RRC protocol, and MAC CE processing.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • PHY Packet Data Convergence Protocol
  • the control plane processing by the baseband processor 1903 may include Non-AccessatumStratum (NAS) protocol, RRC protocol, and MAC CE processing.
  • NAS Non-AccessatumStratum
  • the baseband processor 1903 includes a modem processor (eg, Digital Signal Processor (DSP)) that performs digital baseband signal processing and a protocol stack processor (eg, Central Processing Unit (CPU), or Micro Processing Unit (CPU) that performs control plane processing. (MPU)).
  • DSP Digital Signal Processor
  • MPU Micro Processing Unit
  • a protocol stack processor that performs control plane processing may be shared with an application processor 1904 described later.
  • the application processor 1904 is also called a CPU, MPU, microprocessor, or processor core.
  • the application processor 1904 may include a plurality of processors (a plurality of processor cores).
  • the application processor 1904 is a system software program (Operating System (OS)) read from the memory 1906 or a memory (not shown) and various application programs (for example, a call application, a web browser, a mailer, a camera operation application, music playback)
  • OS Operating System
  • application programs for example, a call application, a web browser, a mailer, a camera operation application, music playback
  • Various functions of UE1 are realized by executing (application).
  • the baseband processor 1903 and the application processor 1904 may be integrated on a single chip, as indicated by the dashed line (1905) in FIG.
  • the baseband processor 1903 and the application processor 1904 may be implemented as a single System on Chip (SoC) device 1905.
  • SoC System on Chip
  • An SoC device is sometimes called a system Large Scale Integration (LSI) or chipset.
  • the memory 1906 is a volatile memory, a nonvolatile memory, or a combination thereof.
  • the memory 1906 may include a plurality of physically independent memory devices.
  • the volatile memory is, for example, Static Random Access Memory (SRAM), Dynamic RAM (DRAM), or a combination thereof.
  • the non-volatile memory is a mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, hard disk drive, or any combination thereof.
  • the memory 1906 may include an external memory device accessible from the baseband processor 1903, the application processor 1904, and the SoC 1905.
  • the memory 1906 may include an embedded memory device integrated within the baseband processor 1903, within the application processor 1904, or within the SoC 1905.
  • the memory 1906 may include a memory in a Universal Integrated Circuit Card (UICC).
  • UICC Universal Integrated Circuit Card
  • the memory 1906 may store a software module (computer program) including an instruction group and data for performing processing by the UE 1 described in the above-described embodiments.
  • the baseband processor 1903 or the application processor 1904 may be configured to read and execute the software module from the memory 1906 to perform the processing of the UE 1 described in the above embodiment.
  • FIG. 20 is a block diagram illustrating a configuration example of the eNB 2 according to the above-described embodiment.
  • the eNB 2 includes an RF transceiver 2001, a network interface 2003, a processor 2004, and a memory 2005.
  • the RF transceiver 2001 performs analog RF signal processing to communicate with UE1.
  • the RF transceiver 2001 may include multiple transceivers.
  • RF transceiver 2001 is coupled to antenna 2002 and processor 2004.
  • the RF transceiver 2001 receives modulation symbol data (or OFDM symbol data) from the processor 2004, generates a transmission RF signal, and supplies the transmission RF signal to the antenna 2002. Further, the RF transceiver 2001 generates a baseband received signal based on the received RF signal received by the antenna 2002, and supplies this to the processor 2004.
  • the network interface 2003 is used to communicate with network nodes (e.g., MME and S / P-GW).
  • the network interface 2003 may include, for example, a network interface card (NIC) compliant with IEEE 802.3 series.
  • NIC network interface card
  • the processor 2004 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication.
  • the digital baseband signal processing by the processor 2004 may include PDCP layer, RLC layer, MAC layer, and PHY layer signal processing.
  • the control plane processing by the processor 2004 may include S1 protocol, RRC protocol, and MAC-CE processing.
  • the processor 2004 may include a plurality of processors.
  • the processor 2004 may include a modem processor (e.g., DSP) that performs digital baseband signal processing and a protocol stack processor (e.g., CPU or MPU) that performs control plane processing.
  • DSP digital baseband signal processing
  • protocol stack processor e.g., CPU or MPU
  • the memory 2005 is configured by a combination of a volatile memory and a nonvolatile memory.
  • the volatile memory is, for example, SRAM or DRAM or a combination thereof.
  • the non-volatile memory is, for example, an MROM, PROM, flash memory, hard disk drive, or a combination thereof.
  • Memory 2005 may include storage located remotely from processor 2004. In this case, the processor 2004 may access the memory 2005 via the network interface 2003 or an I / O interface not shown.
  • the memory 2005 may store a software module (computer program) including an instruction group and data for performing processing by the eNB 2 described in the above-described plurality of embodiments.
  • the processor 2004 may be configured to perform the processing of the eNB 2 described in the above-described embodiment by reading and executing the software module from the memory 2005.
  • each of the processors included in the UE and the eNB 2 includes a group of instructions for causing a computer to execute the algorithm described with reference to the drawings. Run multiple programs.
  • the program can be stored and supplied to a computer using various types of non-transitory computer readable media.
  • Non-transitory computer readable media include various types of tangible storage media (tangible storage medium).
  • non-transitory computer-readable media are magnetic recording media (eg flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg magneto-optical discs), Compact Disc Read Only Memory (CD-ROM), CD-ROM R, CD-R / W, semiconductor memory (for example, mask ROM, Programmable ROM (PROM), Erasable PROM (EPROM), flash ROM, Random Access Memory (RAM)).
  • the program may also be supplied to the computer by various types of temporary computer-readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves.
  • the temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.
  • the above-described embodiment may be applied to a wireless communication system that supports Dual Connectivity (DC). That is, the apparatus, method, and program for setting PUCCH in the SCell described in the above-described embodiment may be applied to carrier aggregation in Master Cell Group (MCG) in Dual Connectivity,
  • MCG Master Cell Group
  • the present invention may be applied to carrier aggregation within a secondary cell group (SCG) in dual connectivity.
  • SCG secondary cell group
  • the PCell described in the above embodiment may be considered to correspond to the Primary SCell (PSCell).
  • PSCell is a special SCell in SCG provided by SecondarySecondeNB (SeNB).
  • SeNB SecondarySecondeNB
  • PSCell is set to PUCCH and is never deactivated, and RACH procedure is required for the initial setting of PSCell.
  • the one or more SCells used in the CA described in the above embodiment may include phantom cells.
  • Phantom Cell is a small cell that is considered for use in C / U-plane split scenarios.
  • the Phantom cell is, for example, an existing cell-specific signal / channel, such as a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a cell-specific reference signal (CRS), a master information block (MIB), and a system information block.
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • CRS cell-specific reference signal
  • MIB master information block
  • SIB system information block
  • the above-described embodiment has mainly described LTE / LTE-Advanced and its improvements.
  • the above-described embodiments may be applied to other wireless communication systems, for example, dual cell operation (DualTSCell HSPA.
  • dual cell operation DualTSCell HSPA.
  • ENB2 demonstrated by the above-mentioned embodiment can also be called a radio station.
  • the radio station in this specification is a control node having a radio resource management function (eg, Radio Network Controller (RNC) in UMTS, or Base Station Controller (BSC) in GSM system) and a radio transmission node (Node, Node B in UMTS, Alternatively, Base (transceiver station) (BTS) in the GSM system may be included.
  • RNC Radio Network Controller
  • BSC Base Station Controller
  • BTS Base (transceiver station)
  • the radio station in this specification may include RRH / RRE as shown in FIG.
  • Radio terminal 2 Radio base station 1901 Radio Frequency (RF) transceiver 1903 Baseband processor 2001 RF transceiver 2004 processor

Landscapes

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

Abstract

L'invention concerne un terminal radio (1) configuré de telle sorte que lorsque le terminal radio (1) reçoit un message de signalisation de liaison descendante comprenant un élément d'information (641) indiquant qu'un premier canal de commande de Liaison Montante (UL) (622) doit être défini dans une première cellule secondaire (SCell) (602) ayant déjà été ajoutée en tant que cellule SCell d'agrégation de porteuses dans laquelle ledit premier canal de commande de UL (622) doit être utilisé pour transmettre des informations de commande de liaison montante (UL) pour au moins une cellule SCell (602, 603), y compris la première cellule SCell (602), le terminal radio (1) désactive une ou plusieurs cellules SCell (602, 603) se trouvant dans un état activé, parmi lesdites cellules SCell (602, 603).
PCT/JP2016/000127 2015-04-08 2016-01-13 Terminal radio et station radio, et procédés associés WO2016163059A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP16776239.2A EP3282792B1 (fr) 2015-04-08 2016-01-13 Deactivation automatique de cellules secundaires lors des reconfigurations de pucch
JP2017511453A JP6617770B2 (ja) 2015-04-08 2016-01-13 無線端末及び無線局並びにこれらの方法
US15/564,655 US11076345B2 (en) 2015-04-08 2016-01-13 Radio terminal, radio station, and method therefor

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2015079068 2015-04-08
JP2015-079068 2015-04-08

Publications (1)

Publication Number Publication Date
WO2016163059A1 true WO2016163059A1 (fr) 2016-10-13

Family

ID=57073178

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2016/000127 WO2016163059A1 (fr) 2015-04-08 2016-01-13 Terminal radio et station radio, et procédés associés

Country Status (4)

Country Link
US (1) US11076345B2 (fr)
EP (1) EP3282792B1 (fr)
JP (1) JP6617770B2 (fr)
WO (1) WO2016163059A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019023574A1 (fr) * 2017-07-28 2019-01-31 Qualcomm Incorporated Champ de signalisation et d'activation de configuration de cellules secondaires
WO2019074429A1 (fr) 2017-10-09 2019-04-18 Telefonaktiebolaget Lm Ericsson (Publ) Nœud maître, nœud secondaire et procédés mis en œuvre par ces derniers
WO2019134619A1 (fr) * 2018-01-04 2019-07-11 维沃移动通信有限公司 Procédé de traitement d'état, terminal et station de base

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9924526B2 (en) * 2015-03-09 2018-03-20 Ofinno Technologies, Llc Radio resource control mechanism in a wireless device and wireless network
US10200164B2 (en) * 2015-09-22 2019-02-05 Comcast Cable Communications, Llc Carrier activation in a multi-carrier wireless network
PL3485597T3 (pl) * 2017-01-09 2020-08-24 Telefonaktiebolaget Lm Ericsson (Publ) Systemy i sposoby dla niezawodnego dynamicznego wskazywania dla półtrwałych CSI-RS
US10411795B2 (en) * 2017-03-14 2019-09-10 Qualcomm Incorporated Coverage enhancement mode switching for wireless communications using shared radio frequency spectrum
WO2018227590A1 (fr) * 2017-06-16 2018-12-20 Zte Corporation Configuration de trajet secondaire

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013511916A (ja) * 2009-11-19 2013-04-04 インターデイジタル パテント ホールディングス インコーポレイテッド マルチキャリアシステムにおけるコンポーネントキャリアのアクティブ化／非アクティブ化
WO2012128544A2 (fr) * 2011-03-21 2012-09-27 엘지전자 주식회사 Procédé d'émission et procédé de réception pour signal montant, équipement utilisateur et station de base
US9118452B2 (en) * 2011-03-28 2015-08-25 Lg Electronics Inc. Method for transmitting an uplink signal, method for receiving an uplink signal, user equipment, and base station
WO2013168850A1 (fr) * 2012-05-09 2013-11-14 삼성전자 주식회사 Procédé et appareil de commande de réception discontinue dans un système de communication mobile
US10075279B2 (en) * 2013-11-25 2018-09-11 Lg Electronics Inc. Method for deactivating secondary cells by a base station and device therefor
JP6081350B2 (ja) 2013-12-26 2017-02-15 株式会社Ｎｔｔドコモ ユーザ端末、無線基地局及び無線通信方法
US9924526B2 (en) * 2015-03-09 2018-03-20 Ofinno Technologies, Llc Radio resource control mechanism in a wireless device and wireless network

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
CATT: "Discussion on the functionality of PUCCH Scell", 3GPP TSG-RAN WG2#89, R2-150264, 31 January 2015 (2015-01-31), XP050935589 *
HUAWEI ET AL.: "Introduce PUCCH on SCell for CA beyond 5 carriers", 3GPP TSG-RAN WG2#89, R2- 150372, 31 January 2015 (2015-01-31), XP050935662 *
INTEL CORPORATION: "Considerations for PUCCH on SCell in carrier aggregation", 3GPP TSG-RAN WG2#89, R2-150169, 31 January 2015 (2015-01-31), XP050935517 *
NEC: "SCell state at PUCCH SCell configuration", 3GPP TSG-RAN WG2#89BIS, R2-151419, 10 April 2015 (2015-04-10), XP050936349 *
See also references of EP3282792A4 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019023574A1 (fr) * 2017-07-28 2019-01-31 Qualcomm Incorporated Champ de signalisation et d'activation de configuration de cellules secondaires
CN110945912A (zh) * 2017-07-28 2020-03-31 高通股份有限公司 副蜂窝小区配置信令和激活字段
US11025401B2 (en) 2017-07-28 2021-06-01 Qualcomm Incorporated Secondary cell configuration signaling and activation field
CN110945912B (zh) * 2017-07-28 2022-02-15 高通股份有限公司 副蜂窝小区配置信令和激活字段
TWI778106B (zh) * 2017-07-28 2022-09-21 美商高通公司 輔細胞配置訊號傳遞和啟動欄位
US11483119B2 (en) 2017-07-28 2022-10-25 Qualcomm Incorporated Secondary cell configuration signaling and activation field
WO2019074429A1 (fr) 2017-10-09 2019-04-18 Telefonaktiebolaget Lm Ericsson (Publ) Nœud maître, nœud secondaire et procédés mis en œuvre par ces derniers
US11265776B2 (en) 2017-10-09 2022-03-01 Telefonaktiebolaget Lm Ericsson (Publ) Master node, a secondary node and methods performed therein
WO2019134619A1 (fr) * 2018-01-04 2019-07-11 维沃移动通信有限公司 Procédé de traitement d'état, terminal et station de base

Also Published As

Publication number Publication date
US11076345B2 (en) 2021-07-27
EP3282792B1 (fr) 2020-05-20
EP3282792A4 (fr) 2018-11-07
JP6617770B2 (ja) 2019-12-11
US20180098266A1 (en) 2018-04-05
JPWO2016163059A1 (ja) 2018-02-08
EP3282792A1 (fr) 2018-02-14

Similar Documents

Publication Publication Date Title
US11777697B2 (en) Method and apparatus for processing activation/deactivation of inter-eNodeB carrier aggregation
JP6617770B2 (ja) 無線端末及び無線局並びにこれらの方法
CN107431592B (zh) 用于发送信道状态信息的方法及其设备
US11438898B2 (en) Beam indication method, apparatus and system
US9872245B2 (en) System and method for activating and deactivating multiple secondary cells
EP3116259B1 (fr) Dispositif de terminal, dispositif de station de base, système de communications, procédé de commande et circuit intégré
JP2021503230A (ja) 複数のコンポーネントキャリアを用いたネットワークアシスト伝送のための方法、デバイスおよびシステム
JP2021029057A (ja) 端末、基地局、無線通信方法及びシステム
JP6462588B2 (ja) 端末装置、基地局装置および通信方法
JP6174094B2 (ja) ユーザ端末、無線基地局及び無線通信方法
JP6892735B2 (ja) 端末装置、基地局装置、および通信制御方法
CN111404655A (zh) 用于改进解码时间线的搜索空间和探通参考信号放置的优化
JPWO2015141637A1 (ja) 端末装置、基地局装置、通信システム、通信方法および集積回路
JP2015164352A (ja) 無線通信システムにおいて集約された複数のセルにおけるシステム情報のための方法及び装置
JP6927966B2 (ja) 端末、無線通信方法及びシステム
TWI783252B (zh) 將啟動次級小區在休眠與活動行為之間轉換之方法與裝置
WO2013123894A1 (fr) Procédé et dispositif permettant de déterminer une cellule synchrone
CN110784895A (zh) 由用户设备执行的方法以及用户设备
CN117796099A (zh) 物理上行控制信道小区切换的方法及用户设备
WO2023185689A1 (fr) Procédé exécuté par un équipement utilisateur et équipement utilisateur
WO2023127273A1 (fr) Nœud de réseau d'accès sans fil, équipement utilisateur et procédés associés
CN116848881A (zh) 无线通信中的scell管理
JP2015088997A (ja) 移動局
JP2016226057A (ja) 移動局

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: 16776239

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2016776239

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2017511453

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 15564655

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE