Terminal

Abstract

To provide a terminal that achieves improved flexibility in communication control when a large number of component carriers are set.SOLUTION: In a wireless communication system, a terminal 200 includes a communication device that performs data communication via one or more component carriers, and the communication device performs a predetermined transmission to transmit uplink control information to a network using the one or more component carriers based on settings of one or more physical uplink control channels.SELECTED DRAWING: Figure 11

Description

[Technical field]

[0001] The present disclosure relates to a terminal that performs wireless communication, and in particular to a terminal that performs wireless communication using multiple component carriers. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has developed specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] 3GPP Release 15 and Release 16 (NR) specify operation in multiple frequency ranges, specifically bands including FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz).

[0004] In addition, NR that supports frequencies above 52.6 GHz and up to 71 GHz is also being studied (Non-Patent Document 1). Furthermore, Beyond 5G, 5G Evolution, and 6G (Release-18 and later) aim to support frequency bands above 71 GHz. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] "New WID on Extending current NR operation to 71 GHz", RP-193229, 3GPP TSG RAN Meeting #86, 3GPP, December 2019 Summary of the Invention

[0006] As described above, it is expected that as the available frequency band is expanded, the possibility of configuring more component carriers (CCs) increases.

[0007] In carrier aggregation (CA), the number of CCs that can be configured is specified. For example, in 3GPP Release 15 and Release 16, the maximum number of CCs that can be configured for a terminal (User Equipment, UE) is 16 for both the downlink (DL) and the uplink (UL).

[0008] Against this background, the inventors conducted intensive research and discovered that it is possible to improve the flexibility of communication control using multiple CCs by focusing on the assumption that the channel quality for multiple CCs is similar.

[0009] Therefore, the following disclosure has been made in consideration of the above circumstances, and aims to provide a terminal that can achieve improved flexibility in communication control when a large number of component carriers (CCs) are configured.

[0010] One aspect of the present disclosure is a terminal including a communication unit that performs data communication via one or more component carriers, and the communication unit performs a predetermined transmission to transmit uplink control information to a network using one or more component carriers based on configuration of one or more physical uplink control channels. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram showing an overall schematic configuration of a wireless communication system 10. As shown in FIG. [Diagram 2] FIG. 2 is a diagram showing frequency ranges used in the wireless communication system 10. As shown in FIG. [Diagram 3] FIG. 3 is a diagram showing an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. As shown in FIG. [Figure 4]FIG. 4 is a functional block diagram of UE 200. [Diagram 5] FIG. 5 is a diagram for explaining resource configuration of PUCCH. [Figure 6] FIG. 6 is a diagram for explaining resource configuration of PUCCH. [Figure 7] FIG. 7 is a diagram for explaining resource configuration of PUCCH. [Figure 8] FIG. 8 is a diagram illustrating the first operation example. [Figure 9] FIG. 9 is a diagram illustrating the second operation example. [Figure 10] FIG. 10 is a diagram for explaining the first modification. [Figure 11] FIG. 11 is a diagram illustrating an example of a hardware configuration of the UE 200. As shown in FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and the description thereof will be omitted as appropriate.

[0013] [Embodiment] (1) Overall configuration of wireless communication system 1 is a schematic diagram of an overall configuration of a wireless communication system 10 according to the present embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (hereinafter, UE 200).

[0014] The wireless communication system 10 may be a wireless communication system conforming to a standard called Beyond 5G, 5G Evolution, or 6G.

[0015] The NG-RAN 20 includes a radio base station 100A (hereinafter, gNB 100A) and a radio base station 100B (hereinafter, gNB 100B). Note that the specific configuration of the wireless communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG.

[0016] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). The NG-RAN 20 and the 5GC may be simply referred to as a "network."

[0017] The gNB100 and gNB100B are radio base stations conforming to 5G, and perform radio communication conforming to 5G with the UE 200. The gNB100, gNB100B, and UE 200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beam BM by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which uses a bundle of multiple component carriers (CC), and Dual Connectivity (DC), which simultaneously communicates between the UE and each of two NG-RAN Nodes.

[0018] The wireless communication system 10 also supports a plurality of frequency ranges (FR).

[0019] 2, the wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR are as follows.

[0020] FR1: 410MHz~7.125GHz FR2: 24.25GHz~52.6GHz FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30 or 60 kHz and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 or 120 kHz (240 kHz may be included) and a bandwidth (BW) of 50 to 400 MHz.

[0021] The SCS may be interpreted as a numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier interval in the frequency domain.

[0022] Furthermore, the wireless communication system 10 also supports a frequency band higher than the FR2 frequency band. Specifically, the wireless communication system 10 supports a frequency band exceeding 52.6 GHz up to 114.25 GHz. For convenience, such a high frequency band may be referred to as "FR2x."

[0023] To solve this problem, when using a band above 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with a larger Sub-Carrier Spacing (SCS) may be applied.

[0024] FIG. 3 shows an example of the configuration of radio frames, subframes, and slots used in the radio communication system 10. In FIG.

[0025] As shown in Fig. 3, one slot is composed of 14 symbols, and the larger (wider) the SCS is, the shorter the symbol period (and slot period) is. The SCS is not limited to the interval (frequency) shown in Fig. 3. For example, 480 kHz, 960 kHz, etc. may be used.

[0026] Also, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 or 56 symbols). Furthermore, the number of slots per subframe may differ depending on the SCS.

[0027] 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a BWP (Bandwidth part), etc.

[0028] (2) Functional block configuration of wireless communication system Next, a description will be given of a functional block configuration of the wireless communication system 10. Specifically, a functional block configuration of the UE 200 will be described.

[0029] Fig. 4 is a functional block diagram of the UE 200. As shown in Fig. 4, the UE 200 includes a radio signal transmitting / receiving unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmitting / receiving unit 260, and a control unit 270.

[0030] The radio signal transmission / reception unit 210 transmits and receives radio signals conforming to NR. The radio signal transmission / reception unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and each of two NG-RAN nodes.

[0031] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier) ​​etc. The amplifier unit 220 amplifies the signal output from the modem unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the wireless signal transmitting / receiving unit 210.

[0032] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB100 or another gNB). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for uplink (UL) but also for downlink (DL).

[0033] The control signal / reference signal processor 240 executes processing related to various control signals transmitted and received by the UE 200, and processing related to various reference signals transmitted and received by the UE 200.

[0034] Specifically, the control signal / reference signal processor 240 receives various control signals, for example, radio resource control layer (RRC) control signals, transmitted from the gNB 100 via a predetermined control channel. In addition, the control signal / reference signal processor 240 transmits various control signals to the gNB 100 via a predetermined control channel.

[0035] The control signal / reference signal processor 240 executes processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0036] DMRS is a known reference signal (pilot signal) between a base station and a terminal for estimating a fading channel used for data demodulation. PTRS is a terminal-specific reference signal for estimating phase noise, which is an issue in high frequency bands.

[0037] In addition to the DMRS and PTRS, the reference signals may include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

[0038] The channels include a control channel and a data channel. The control channels include a PDCCH (Physical Downlink Control Channel), a PUCCH (Physical Uplink Control Channel), a RACH (Random Access Channel), Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), and a Physical Broadcast Channel (PBCH).

[0039] The data channel includes a physical downlink shared channel (PDSCH) and a physical uplink shared channel (PUSCH), etc. Data means data transmitted via the data channel. The data channel may be read as a shared channel.

[0040] In the embodiment, the control signal and reference signal processor 240 constitutes a communication unit that executes data communication via one or more CCs. The control signal and reference signal processor 240 executes a predetermined transmission that transmits uplink control information (UCI) to a network (e.g., NG-RAN 20) using one or more CCs. The UCI may include an acknowledgement (HARQ-ACK) for one or more TBs. The UCI may include a Scheduling Request (SR) that requests resource scheduling, and may include Channel State Information (CSI) that indicates a channel state. The UCI may be transmitted via a Physical Uplink Control Channel (PUCCH) or a Physical Uplink Shared Channel (PUSCH).

[0041] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding, etc. for each predetermined communication destination (gNB100 or another gNB).

[0042] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, and decodes the data output from the modem unit 230 and concatenates the decoded data.

[0043] The data transmission / reception unit 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmission / reception unit 260 performs assembly / disassembly of PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). In addition, the data transmission / reception unit 260 performs data error correction and retransmission control based on a hybrid automatic repeat request (Hybrid ARQ).

[0044] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 controls communication of one or more CCs using one or more DCIs received via a predetermined CC. The predetermined CC may be one or more CCs included in a plurality of CCs. The communication of one or more CCs may include transmission of UCI using one or more CCs.

[0045] (3) PUCCH resource configuration 5 to 7 are diagrams showing resource configuration of PUCCH in the case where UCI is transmitted via PUCCH or PUSCH. In FIG. 5 to FIG. 7, the case where UCI is transmitted via CC#0 and CC#1 is illustrated. A resource used for PUCCH (hereinafter, PUCCH resource) is configured by a higher layer. The PUCCH resource is configured by an information element included in an RRC message. Such an information element may be referred to as PUCCH-Config. In PUCCH-Config., one or more PUCCH resource sets and one or more PUCCH resources are configured, and the one or more PUCCH resource sets include an information element specifying one or more PUCCH resources. A higher layer parameter for configuring a PUCCH resource for SR and CSI transmission may be configured separately from the above PUCCH resource set. In the present disclosure, PUCCH-Config. or PUCCH resource may be replaced with PUCCH resource set.

[0046] First, as shown in FIG. 5, PUCCH-Config. may be an information element capable of specifying a PUCCH resource spanning multiple CCs. One or more PUCCH resource sets may be configured in PUCCH-Config., and one or more PUCCH resources may be configured. Each PUCCH resource may be configured for one or more of multiple CCs, and a PUCCH resource spanning multiple CCs may be specified. In the example shown in FIG. 5, PUCCH-Config. may be a configuration targeting the PUCCH resource of CC#0, or may be a configuration targeting the PUCCH resource of CC#1. PUCCH-Config. may be a configuration targeting the PUCCH resource spanning both CC#0 and CC#1. In such a case, UCI is transmitted via a PUCCH spanning CC#0 and CC#1. In the present disclosure, a PUCCH spanning multiple CCs may mean that a certain PUCCH is mapped to multiple CCs, and may be transmitted or received via multiple CCs.

[0047] Secondly, as shown in FIG. 6, PUCCH-Config. may be an information element that cannot specify a PUCCH resource that spans multiple CCs. One or more PUCCH resource sets may be configured in PUCCH-Config., and one or more PUCCH resources may be configured. Each PUCCH resource may be configured for any one of multiple CCs, and may not span multiple CCs. Any one of multiple CCs may be any CC, and may be limited to a specific CC. In the example shown in FIG. 6, PUCCH-Config. is a configuration targeting the PUCCH resource of CC#0. In the configuration of the PUCCH resource, the PUCCH resource is not allowed to span multiple CCs, but in the transmission of UCI, the PUCCH based on the PUCCH resource may span multiple CCs. For example, the UE 200 and the NG-RAN 20 may determine whether or not to span multiple CCs based on one or more parameters selected from the payload size of UCI, the coding rate of UCI, the modulation order of UCI, and an Indication indicating transmission spanning multiple CCs.

[0048] Thirdly, as shown in FIG. 7, PUCCH-Config. may be an information element that cannot specify a PUCCH resource that spans multiple CCs. One or more PUCCH resource sets may be configured in PUCCH-Config., and one or more PUCCH resources may be configured. Each PUCCH resource may be configured for any one of multiple CCs, and may not span multiple CCs. Any one of multiple CCs may be any CC, or may be limited to a specific CC. In the example shown in FIG. 7, PUCCH-Config. is a configuration that targets the PUCCH resource of CC#0. In the configuration of the PUCCH resource, it may not be permitted for the PUCCH resource to span multiple CCs. In such a case, transmission of UCI via a PUCCH that spans CC#0 and CC#1 may not be permitted. That is, UCI is transmitted via a PUCCH mapped to CC#0.

[0049] Here, whether or not to apply the PUCCH-Config. and / or the PUCCH resource related to multiple CCs may be applied to the UE 200 by an information element included in the RRC message, or may be applied to the UE 200 by an information element included in the DCI. Application may be referred to as enable or activate. Non-application may be referred to as disable or inactivate.

[0050] Also, two higher layer parameter sets may be configured. For example, one higher layer parameter set may be a PUCCH-Config. related to multiple CCs and may include parameters specifying PUCCH resources in different CCs, or may include parameters specifying PUCCH resources across multiple CCs. The other higher layer parameter set may be a PUCCH-Config. related to a single CC and may include parameters specifying PUCCH resources in a single CC (i.e., similar to the conventional PUCCH-Config.).

[0051] In addition, the multiple CCs may be consecutive CCs in the intra-band. The multiple CCs may be CCs included in the scheduling cell, or may be CCs included in the search space of the PDCCH. The search space of the PDCCH may be defined by RNTIs such as SI (System Information)-RNTI (Radio Network Temporary Identifier), RA (Random Access)-RNTI, TC (Temporary Cell)-RNTI, C (Cell)-RNTI, P (Paging)-RNTI, INT (Interruption)-RNTI, SFI (Slot Format Indication)-RNTI, TPC (Transmit Power Control)-PUSCH-RNTI, TPC-PUCCH-RNTI, TPC-SRS-RNTI, and SP (Semi Persistent)-CSI (Channel State Information)-RNTI. The multiple CCs may be CCs to which the configuration of the serving cell is commonly applied. The configuration of the serving cell may include TDD DL / UL configuration and SCS specific carrier list.

[0052] Under such a background, the UE 200 may receive an RRC message including an information element instructing application of the PUCCH-Config. and / or PUCCH resource related to multiple CCs from the NG-RAN 20. The information element instructing application of the PUCCH-Config. and / or PUCCH resource related to multiple CCs may include identification information of a CC to which the PUCCH-Config. and / or PUCCH resource is applied and an indication of application of the PUCCH-Config. and / or PUCCH resource related to multiple CCs (e.g., enable). The UE 200 may receive an RRC message including an information element instructing non-application of the PUCCH-Config. and / or PUCCH resource related to multiple CCs from the NG-RAN 20. The information element instructing non-application of the PUCCH-Config. and / or PUCCH resource related to multiple CCs may include a CC to which the PUCCH-Config. and / or PUCCH resource is not applied and an indication of non-application of the PUCCH-Config. and / or PUCCH resource related to multiple CCs (e.g., disable). The elements in the above table indicating the application or non-application of PUCCH-Config. and / or PUCCH resource may be bitmap information that can identify a CC by a bit position, and each bit may be an information element indicating whether the CC corresponding to the bit position is applicable to PUCCH-Config. and / or PUCCH resource related to multiple CCs.

[0053] UE200 may specify a CC to which PUCCH-Config. and / or PUCCH resource related to multiple CCs is applied based on an information element included in DCI. For example, UE200 specifies a CC to which PUCCH-Config. and / or PUCCH resource is applied based on a CI stored in a CI (Channel Indicator) field included in DCI. For example, in the case shown in FIG. 5, when the CI is a value indicating CC#0 and CC#1, the CCs to which PUCCH-Config. and / or PUCCH resource is applied are CC#0 and CC#1.

[0054] Furthermore, when two CCs included in a plurality of CCs are adjacent in the frequency domain, PUCCH mapping may be performed for the Guard Subcarrier(s) between the two CCs. In other words, the Guard Subcarrier(s) between consecutive CCs may be used as a resource. Alternatively, the Guard Subcarrier(s) between the two CCs may be rate matched. That is, the PUCCH may not be mapped to the Guard Subcarrier(s) but may be mapped in order beyond the Guard Subcarrier(s).

[0055] (4)TDD settings In cases where a PUCCH-Config. related to multiple CCs and / or a PUCCH resource spanning multiple CCs may be applied, the TDD configuration may be defined as follows.

[0056] First, it may be expected that the same TDD (Time Division Duplex) configuration is applied to multiple CCs. That is, only when the same TDD (Time Division Duplex) configuration is applied to multiple CCs, a PUCCH-Config. related to multiple CCs and / or a PUCCH resource across multiple CCs may be applied. The TDD configuration is an example of an information element (higher layer parameter) of an RRC message, and may be referred to as a TDD UL / DL Common Configuration or a TDD UL / DL Dedicated Configuration. Alternatively, the TDD configuration may be indicated by a specific DCI (e.g., SFI).

[0057] Secondly, the pattern of symbols to which DL and UL are assigned in the time domain (hereinafter, D / U Type) may be the same among multiple CCs. The usable PUCCH may be limited to resources across one or more CCs with the same D / U Type. Note that, when multiple CCs include CCs with different D / U Types, existing control for mapping the PUCCH to one CC may be executed.

[0058] (5) Mapping The order of mapping PUCCH to multiple CCs may be an order in which PUCCH is mapped to the frequency domain across multiple CCs in the n-th unit included in the time domain, and then PUCCH is mapped to the frequency domain across multiple CCs in the n+1-th unit included in the time domain (see, for example, FIG. 9). Alternatively, the order of mapping PUCCH to multiple CCs may be an order in which PUCCH is mapped to the frequency domain in the n-th unit included in the time domain in the m-th CC, and then PUCCH is mapped to the frequency domain in the n+1-th unit included in the time domain, and then this is repeated in the m+1-th CC.

[0059] When the PUCCH is mapped to multiple CCs, different UCI types may be mapped to different CCs. The UCI type may include types such as HARQ-ACK, SR, and CSI. For example, in a PUCCH mapped to CC#0 and CC#1, the HARQ-ACK may be transmitted via CC#0, and the SR and CSI may be transmitted via CC#1.

[0060] (6) Frequency hopping In the case where PUCCH-Config. is related to multiple CCs and / or the PUCCH resource spans multiple CCs, frequency hopping (FH) may not be configured. Even if FH is configured, FH may not be applied. The information element for configuring FH is an example of an information element (higher layer parameter) included in an RRC message.

[0061] In the case where PUCCH-Config. is related to multiple CCs and / or where PUCCH resource spans multiple CCs, if FH is supported, the PRB index may be defined in a format spanning multiple CCs. For example, in the case shown in FIG. 8, the PRB indexes included in CC#0 and CC#1 may be defined in a continuous format between CCs, not independent for each CC. Alternatively, the PRB at which FH starts may be defined by the CC index of the CC and the PRB index within the CC.

[0062] (7) Example of operation (7.1) Example 1 As shown in Fig. 8, in step S10, the UE 100 receives an RRC message including a PUCCH-Config. associated with a plurality of CCs from the NG-RAN 20. The RRC message may include an information element indicating application of the PUCCH-Config. associated with a plurality of CCs (see Fig. 5).

[0063] In step S11, the UE 200 receives one or more DCIs from the NG-RAN 20 via a PDCCH that is mapped to a predetermined CC.

[0064] In step S12, the UE 200 receives data via a PDSCH that is mapped to one or more CCs based on the DCI received in step S11.

[0065] In step S13, the UE 200 transmits data via a PUCCH based on the DCI received in step S11. In an embodiment, the UE 200 transmits UCI via a PUCCH across multiple CCs. For example, the UCI may include a HARQ-ACK for data received via a PDSCH.

[0066] Fig. 8 illustrates a case where PUCCH-Config. can specify one PUCCH resource across multiple CCs (see Fig. 5). However, as shown in Fig. 6, PUCCH-Config. may be an information element that cannot specify one PUCCH resource across multiple CCs.

[0067] (7.2) Example 2 As shown in FIG. 9, in step S20, the UE 100 receives an RRC message including PUCCH-Config. associated with multiple CCs from the NG-RAN 20 (see FIG. 5).

[0068] In step S21, UE 200 receives one or more DCIs from NG-RAN 20 via a PDCCH mapped to a predetermined CC. UE 200 may identify a CC to which PUCCH-Config. related to multiple CCs is applied based on an information element included in the DCI. For example, UE 200 identifies a CC to which PUCCH-Config. is applied based on a CI stored in a CI field included in the DCI.

[0069] In step S22, the UE 200 receives data via a PDSCH that is mapped to one or more CCs based on the DCI received in step S21.

[0070] In step S23, the UE 200 transmits data via a PUCCH based on the DCI received in step S21. In an embodiment, the UE 200 transmits UCI via a PUCCH across multiple CCs. For example, the UCI may include a HARQ-ACK for data received via a PDSCH.

[0071] Fig. 9 illustrates a case where PUCCH-Config. can specify one PUCCH resource across multiple CCs (see Fig. 5). However, as shown in Fig. 6, PUCCH-Config. may be an information element that cannot specify one PUCCH resource across multiple CCs.

[0072] (8) Actions and Effects In the embodiment, the UE 200 executes a predetermined transmission to transmit UCI to the network using one or more CCs. With such a configuration, when a large number of CCs are set, it is possible to improve the flexibility of communication control. In addition, it is possible to reduce the coding rate applied to UCI, and to transmit UCI with an increased number of bits in a short time.

[0073] [Change Example 1] Modification 1 of the embodiment will be described below, with differences from the embodiment being described below.

[0074] Specifically, the UE 200 transmits an information element indicating whether or not the UE 200 has the capability to perform the predetermined transmission to the network (NG-RAN 20). Specifically, as shown in Fig. 10, in step S30, the UE 200 transmits (reports) to the NG-RAN 20 a UE capability including an information element indicating whether or not the UE 200 has the capability to perform the predetermined transmission.

[0075] Although not particularly limited, the UE 200 may execute step S30 when an RRC connection is established with the NG-RAN 20. In other words, step S30 may be executed before the process shown in FIG. 8 or FIG.

[0076] [Change Example 2] Modification 2 of the embodiment will be described below. Differences from the embodiment will be described below. In modification 2, the predetermined condition to which the predetermined transmission is applied will be described.

[0077] The predetermined condition may be that the multiple CCs are controlled based on one or more DCIs received via a predetermined CC included in the multiple CCs.

[0078] The predetermined condition may be that one or more DCIs received via a predetermined CC indicate that the predetermined transmission is applied (first predetermined condition). The predetermined transmission may be applied to multiple CCs used to receive the DCI indicating that the predetermined transmission is applied. The DCI may include an information element (enable) indicating that the predetermined transmission is applied. The DCI may include an information element (disable) indicating that the predetermined transmission is not applied. The multiple CCs to which the predetermined transmission may be applied may be set by an RRC message or may be determined in advance.

[0079] The predetermined condition may be that the RRC message indicates that the predetermined transmission is applied (second predetermined condition). The RRC message may include an information element (enable) indicating that the predetermined transmission is applied. The RRC message may include an information element (disable) indicating that the predetermined transmission is not applied. The RRC message is bitmap information capable of identifying a CC by a bit position, and each bit may include an information element indicating whether the predetermined transmission is applied to the CC corresponding to the bit position. The RRC message may include identification information of the CC to which the predetermined transmission is applied. A plurality of CCs to which the predetermined transmission may be applied may be set by the RRC message or may be determined in advance.

[0080] As described above, the UE 200 (control unit 270) may determine whether or not a predetermined condition (for example, the above-mentioned first predetermined condition) is satisfied based on an RRC message including an information element indicating whether or not the predetermined transmission is applied. The UE 200 (control unit 270) may determine whether or not a predetermined condition (for example, the above-mentioned second predetermined condition) is satisfied based on an RRC message including an information element indicating whether or not the predetermined transmission is applied.

[0081] Furthermore, UE 200 (control unit 270) may determine whether a predetermined condition is satisfied based on the RRC message and the DCI. For example, UE 200 may set a plurality of CCs to which the predetermined transmission may be applied by the RRC message, and identify a CC to which the predetermined transmission is applied from among the set CCs based on the DCI.

[0082] [Change Example 3] The third modification of the embodiment will be described below, focusing on the differences from the embodiment.

[0083] In the embodiment, a case where UCI is transmitted via PUCCH is exemplified. In contrast, in Modification Example 3, a case where UCI is transmitted via PUSCH spanning multiple CCs is described. The case where UCI is transmitted via PUSCH spanning multiple CCs may be a case where PUCCH to be used for transmitting UCI collides with PUSCH in the time domain and UCI is multiplexed into PUSCH, or a case where UCI is instructed to be transmitted via PUSCH.

[0084] As a first option, the UCI may be mapped to a specific CC of the PUSCH and transmitted. The specific CC may be one CC.

[0085] As a second option, the UCI may be mapped across multiple CCs of the PUSCH and transmitted.

[0086] In the second option, the order of mapping UCI (RE of PUSCH used for transmitting UCI) to multiple CCs may be considered to be the same as the order of mapping PUCCH (UCI) to multiple CCs. That is, the order of mapping UCI to multiple CCs may be the order of mapping UCI to the frequency domain across multiple CCs in the n-th unit included in the time domain, and then mapping UCI to the frequency domain across multiple CCs in the n+1-th unit included in the time domain. Alternatively, the order of mapping UCI to multiple CCs may be the order of mapping UCI to the frequency domain in the n-th unit included in the time domain in the m-th CC, and then mapping UCI to the frequency domain in the n+1-th unit included in the time domain, and then repeating this in the m+1-th CC.

[0087] In the second option, the number of REs in each CC of the PUSCH used for transmitting the UCI may be limited to a predetermined number or less. The REs of the PUSCH used for transmitting the UCI may be discretely mapped or locally mapped in a frequency domain included in multiple CCs.

[0088] The first option and the second option may be switched by a higher layer parameter, for example, by an RRC message including an information element specifying either the first option or the second option.

[0089] The first option and the second option may be switched based on whether or not the PUCCH spans multiple CCs in a case where the PUCCH to be used for transmitting the UCI collides with the PUSCH in the time domain and the UCI is multiplexed into the PUSCH. For example, when the mapping of the PUCCH across multiple CCs is not applied, the first option may be adopted for the PUSCH, and when the mapping of the PUCCH across multiple CCs is applied, the second option may be adopted for the PUSCH.

[0090] The first option and the second option may be switched based on the UCI type. The UCI type may include a type such as HARQ-ACK, SR, CSI, etc. For example, the first option may be applied for HARQ-ACK, and the second option may be applied for SR and CSI.

[0091] For the first option and the second option, different values ​​may be set as the beta-offset applied to the UCI transmitted via the PUSCH. The beta-offset may be a value used to determine the coding rate of the UCI.

[0092] [Other embodiments] The present invention has been described above in accordance with the embodiments, but the present invention is not limited to these descriptions, and it will be obvious to those skilled in the art that various modifications and improvements are possible.

[0093] In the above-described embodiment, the RRC message and DCI are mainly described, but the embodiment is not limited thereto. For example, the UE 200 may apply a predetermined transmission of UCI across multiple CCs based on an information element used in a MAC CE (Control Element).

[0094] Although briefly mentioned in the embodiments, the information elements (higher layer parameters) included in the RRC message used in the case where UCI is transmitted using multiple CCs may be defined separately from the information elements (higher layer parameters) included in the RRC message used in the case where UCI is transmitted using one CC.

[0095] Although not specifically mentioned in the embodiment, when multiple CCs are included in one BWP, UCI may be transmitted using multiple CCs. In other words, the above-mentioned predetermined condition may include that multiple CCs are included in one BWP.

[0096] In the embodiment, UCI has been mainly described, but the embodiment is not limited thereto. UCI may be replaced with HARQ-ACK, SR, or CSI. UCI that can be transmitted using multiple CCs may be any parameter selected from HARQ-ACK, SR, and CSI.

[0097] The block diagram (FIG. 4) used in the description of the above-mentioned embodiment shows functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically combined, or may be realized by using two or more devices that are physically or logically separated and directly or indirectly connected (for example, by wire, wirelessly, etc.). The functional block may be realized by combining the one device or the multiple devices with software.

[0098] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the function of transmission is called a transmitting unit or a transmitter. As described above, there is no particular limitation on the method of realization of each of these.

[0099] Furthermore, the above-mentioned UE 200 (the device) may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 11 is a diagram showing an example of a hardware configuration of the device. As shown in Fig. 11, the device may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0100] In the following description, the term "apparatus" may be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0101] Each functional block of the device (see FIG. 4) is realized by any hardware element of the computer device, or a combination of the hardware elements.

[0102] In addition, each function in the device is realized by loading a specific software (program) onto hardware such as the processor 1001, memory 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing of data in the memory 1002 and storage 1003.

[0103] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, and the like.

[0104] Furthermore, the processor 1001 reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. Furthermore, the above-mentioned various processes may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0105] The memory 1002 is a computer-readable recording medium, and may be configured by at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a Random Access Memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.

[0106] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like. Storage 1003 may be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0107] The communication device 1004 is hardware (transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0108] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, and the like to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0109] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0110] In addition, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0111] Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc., and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0112] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination of these. Furthermore, the RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0113] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other suitable systems, and next-generation systems extended based on these. In addition, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G, etc.) may be applied.

[0114] The order of the steps, sequences, flow charts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0115] In the present disclosure, a specific operation performed by a base station may be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and other network nodes other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case in which there is one other network node other than the base station, it may also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0116] Information and signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), and may be input and output via multiple network nodes.

[0117] The input / output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input / output information may be overwritten, updated, or appended. The output information may be deleted. The input information may be transmitted to another device.

[0118] The determination may be based on a value represented by a single bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0119] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched according to execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).

[0120] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0121] Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave, etc.), then these wired and / or wireless technologies are included within the definition of transmission media.

[0122] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0123] In addition, the terms described in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Also, a signal may be a message. Also, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0124] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0125] In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values ​​from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by an index.

[0126] The names used for the above-mentioned parameters are not limiting in any way. Furthermore, the formulas using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any way.

[0127] In this disclosure, terms such as "base station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", "component carrier", etc. may be used interchangeably. A base station may also be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, etc.

[0128] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0129] The term "cell" or "sector" refers to part or all of the coverage area of ​​a base station and / or a base station subsystem that provides communication services within that coverage.

[0130] In this disclosure, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably.

[0131] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0132] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, etc. The moving object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may include a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0133] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies below). For example, each aspect / embodiment of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, an uplink channel, a downlink channel, etc. may be read as a side channel.

[0134] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.

[0135] A radio frame may be composed of one or more frames in the time domain, each of which may be called a subframe.

[0136] A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0137] Numerology may be a communication parameter that applies to the transmission and / or reception of a signal or channel, and may indicate, for example, at least one of a SubCarrier Spacing (SCS), a bandwidth, a symbol length, a Cyclic Prefix length, a Transmission Time Interval (TTI), a number of symbols per TTI, a radio frame structure, a particular filtering operation that a transceiver performs in the frequency domain, a particular windowing operation that a transceiver performs in the time domain, etc.

[0138] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) A slot may be a time unit based on numerology.

[0139] A slot may include multiple minislots. Each minislot may be composed of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may be composed of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0140] A radio frame, a subframe, a slot, a minislot, and a symbol each represent a time unit for transmitting a signal. The radio frame, the subframe, the slot, the minislot, and the symbol may each be referred to by a different name.

[0141] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in the existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit expressing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0142] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0143] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) in which a transport block, a code block, a code word, etc. are actually mapped may be shorter than the TTI.

[0144] In addition, when one slot or one minislot is called TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. Also, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.

[0145] A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a minislot, a subslot, a slot, etc.

[0146] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0147] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

[0148] In addition, the time domain of the RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. Each of one TTI, one subframe, etc. may be composed of one or more resource blocks.

[0149] One or more RBs may be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0150] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0151] A Bandwidth Part (BWP), which may also be referred to as a fractional bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a numerology on a carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0152] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0153] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be replaced with "BWP".

[0154] The above-mentioned structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0155] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples. The reference signal may also be abbreviated as Reference Signal (RS), and may be called a pilot depending on the applicable standard.

[0156] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0157] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0158] Any reference to an element using a designation such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

[0159] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Further, when used in this disclosure, the term "or" is not intended to be an exclusive or.

[0160] In this disclosure, where articles have been added due to translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0161] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in a memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." In addition, "judgment" can be interpreted as "assuming," "expecting," "considering," etc.

[0162] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0163] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure. [Explanation of symbols]

[0164] 10. Wireless communication systems 20 NG-RAN 100 gNB 200UE 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and demodulation section 240 Control signal / reference signal processing unit 250 Encoding / Decoding Unit 260 Data transmission and reception unit 270 Control Unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output device 1007 Bus

Claims

1. A communication unit that performs data communication via a plurality of component carriers, The communication unit performs a predetermined transmission to transmit uplink control information across the multiple component carriers to a network, using a physical uplink control channel resource across the multiple component carriers, based on configuration of one or more physical uplink control channels.

2. The terminal according to claim 1 , further comprising a transmitting unit configured to transmit to the network an information element indicating whether or not the terminal is capable of performing the predetermined transmission.

Images