JP7827634B2 - Terminal device and communication method - Google Patents

Description

The present invention relates to a terminal device and a base station device.
This application claims priority to Japanese Patent Application No. 2020-171852, filed on October 12, 2020, the contents of which are incorporated herein by reference.

A radio access method and a radio network for cellular mobile communications (hereinafter also referred to as "Long Term Evolution (LTE)" or "EUTRA: Evolved Universal Terrestrial Radio Access") are being studied by the ^3rd Generation Partnership Project (3GPP). In LTE, a base station device is also referred to as an evolved NodeB (eNodeB), and a terminal device is also referred to as a User Equipment (UE). LTE is a cellular communication system in which multiple areas covered by a base station device are arranged in the form of cells. A single base station device may manage multiple serving cells.

3GPP is currently studying the next-generation standard (NR: New Radio) to be proposed for IMT (International Mobile Telecommunication)-2020, the standard for next-generation mobile communications systems formulated by the International Telecommunication Union (ITU) (Non-Patent Document 1). NR is required to meet the requirements of three scenarios: eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication) within a single technology framework.

3GPP is currently studying the expansion of services supported by NR (Non-Patent Document 2).

"New SID proposal: Study on New Radio Access Technology", RP-160671, NTT docomo, 3GPP TSG RAN Meeting #71, Goteborg, Sweden, 7th - 10th March, 2016. “Release 17 package for RAN”, RP-193216, RAN chairman, RAN1 chairman, RAN2 chairman, RAN3 chairman, 3GPP TSG RAN Meeting #86, Sitges, Spain, 9th ― 12th December, 2019

One aspect of the present invention provides a terminal device that communicates efficiently and a base station device that communicates efficiently.

(1) An aspect of the present invention employs the following means. That is, a first aspect of the present invention provides a terminal device comprising: a coding unit that generates a first coded bit sequence d by coding a bit sequence, and generates a second coded bit sequence by applying a cyclic shift of a predetermined amount _Cs to the first coded bit sequence d for an s-th uplink channel entity among S uplink channel entities; and a transmitter that transmits the S uplink channels including the second coded bit sequence , where S is an integer equal to or greater than 2 and s is an integer equal to or greater than 0 and equal to or less than S−1, and the coding unit determines the predetermined amount _Cs based on a predetermined amount _Cs−1 for an s−1th uplink channel entity among the S uplink channel entities, a number Ns ₋₁ of OFDM symbols included in the s−1th uplink channel entity , and Nblockbit indicating the number of UCI bits per OFDM ^symbol _.

(2) A second aspect of the present invention is a communication method used in a terminal device, the method comprising: an encoding step of generating a first coded bit sequence d by encoding a bit sequence, and generating a second coded bit sequence by applying a cyclic shift of a predetermined amount _Cs to the first coded bit sequence d for an s-th uplink channel entity among S uplink channel entities; and a transmitting step of transmitting the S uplink channels including the second coded bit sequence , wherein S is an integer equal to or greater than 2 and s is an integer equal to or greater than 0 and equal to or less than S−1, and in the encoding step, the predetermined amount _Cs is determined based on a predetermined amount _Cs−1 for an s−1th uplink channel entity among the S uplink channel entities, a number Ns ₋₁ of OFDM symbols included in the s−1th uplink channel entity , _and ^Nblockbit indicating the number of UCI bits per OFDM symbol .

According to one aspect of this invention, terminal devices can communicate efficiently. Also, base station devices can communicate efficiently.

1 is a conceptual diagram of a wireless communication system according to an aspect of the present embodiment. 10 is an example showing the relationship between a subcarrier spacing setting μ, the number of OFDM symbols per slot N ^slot _symb , and a cyclic prefix (CP) setting according to one aspect of the present embodiment. FIG. 10 is a diagram illustrating an example of a method for configuring a resource grid according to an aspect of the present embodiment. FIG. 30 is a diagram illustrating an example of the configuration of a resource grid 3001 according to one aspect of the present embodiment. FIG. 2 is a schematic block diagram illustrating an example of the configuration of a base station device 3 according to one aspect of the present embodiment. 1 is a schematic block diagram illustrating an example of the configuration of a terminal device 1 according to an aspect of the present embodiment. A figure showing an example of the configuration of an SS/PBCH block related to one aspect of this embodiment. FIG. 10 is a diagram illustrating an example of a monitoring opportunity for a set of search areas according to one aspect of the present embodiment. FIG. 10 is a diagram illustrating an example of transmission based on PUCCH repetition according to one aspect of the present embodiment. FIG. 2 is a diagram illustrating an example of the configuration of a baseband unit 13 of a terminal device 1 according to an aspect of the present embodiment. FIG. 10 is a diagram illustrating an example of the operation of a dividing unit 1001 according to one aspect of the present embodiment. FIG. 10 is a diagram illustrating an example of a procedure for determining a variable n used in encoding a polar code according to an aspect of the present embodiment. FIG. 10 is a diagram illustrating an example of mapping of uplink control information for sequence-based PUCCH according to an aspect of the present embodiment.

The following describes an embodiment of the present invention.

floor(C) may be a floor function for real number C. For example, floor(C) may be a function that outputs the largest integer that does not exceed real number C. ceil(D) may be a ceiling function for real number D. For example, ceil(D) may be a function that outputs the smallest integer that does not fall below real number D. mod(E,F) may be a function that outputs the remainder when E is divided by F. mod(E,F) may be a function that outputs a value corresponding to the remainder when E is divided by F. exp(G) = e^G, where e is Napier's constant. H^I represents H to the Ith power. max(J,K) is a function that outputs the maximum value of J and K. Here, max(J,K) is a function that outputs J or K when J and K are equal. min(L,M) is a function that outputs the maximum value of L and M. Here, when L and M are equal, min(L, M) is a function that outputs L or M. round(N) is a function that outputs the integer value closest to N.

In a wireless communication system according to one aspect of this embodiment, at least OFDM (Orthogonal Frequency Division Multiplexing) is used. An OFDM symbol is a time domain unit of OFDM. An OFDM symbol includes at least one or more subcarriers. The OFDM symbol is converted into a time-continuous signal during baseband signal generation. In the downlink, at least CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplexing) is used. In the uplink, either CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing) is used. DFT-s-OFDM may be achieved by applying transform precoding to CP-OFDM.

The OFDM symbol may be a name that includes the CP added to the OFDM symbol. In other words, a certain OFDM symbol may be composed of that certain OFDM symbol and the CP added to that certain OFDM symbol.

Figure 1 is a conceptual diagram of a wireless communication system according to one aspect of this embodiment. In Figure 1, the wireless communication system includes at least terminal devices 1A to 1C and base station device 3 (BS#3: Base station#3). Hereinafter, terminal devices 1A to 1C will also be referred to as terminal device 1 (UE#1: User Equipment#1).

The base station device 3 may be configured to include one or more transmitting devices (or transmission points, transmitting/receiving devices, transmitting/receiving points). If the base station device 3 is configured with multiple transmitting devices, each of the multiple transmitting devices may be located in a different location.

The base station device 3 may provide one or more serving cells. A serving cell may be defined as a set of resources used for wireless communication. A serving cell is also referred to as a cell.

A serving cell may be configured to include at least one downlink component carrier (downlink carrier) and/or one uplink component carrier (uplink carrier). A serving cell may be configured to include at least two or more downlink component carriers and/or two or more uplink component carriers. A downlink component carrier and an uplink component carrier are also referred to as a component carrier (carrier).

For example, one resource grid may be provided for one component carrier. Also, one resource grid may be provided for one component carrier and a certain subcarrier spacing configuration μ. Here, the subcarrier spacing configuration μ is also referred to as numerology. The resource grid includes N ^size,μ _grid,x N ^RB _sc subcarriers. The resource grid starts from a common resource block N ^start,μ _grid,x . The common resource block N ^start,μ _grid,x is also referred to as the reference point of the resource grid. The resource grid includes N ^subframe,μ _symb OFDM symbols. x is a subscript indicating the transmission direction, either downlink or uplink. One resource grid is provided for a set of an antenna port p, a certain subcarrier spacing configuration μ, and a certain transmission direction x.

N ^size,μ _grid,x and N ^start,μ _grid,x are determined based at least on a higher layer parameter (CarrierBandwidth). The higher layer parameter is also referred to as an SCS specific carrier. One resource grid corresponds to one SCS specific carrier. One component carrier may include one or more SCS specific carriers. The SCS specific carriers may be included in the system information. One subcarrier spacing setting μ may be determined for each SCS specific carrier.

The subcarrier spacing (SCS) Δf may be Δf= ^2μ ·15 kHz. For example, the subcarrier spacing setting μ may represent any of 0, 1, 2, 3, or 4.

2 is an example showing the relationship between the subcarrier spacing setting μ, the number of OFDM symbols per slot N ^slot _symb , and the CP (cyclic prefix) setting according to one aspect of this embodiment. In Fig. 2A, for example, when the subcarrier spacing setting μ is 2 and the CP setting is normal cyclic prefix (CP), N ^slot _symb =14, N ^frame,μ _slot =40, and N ^subframe,μ _slot =4. Also, in Fig. 2B, for example, when the subcarrier spacing setting μ is 2 and the CP setting is extended cyclic prefix (CP), N ^slot _symb =12, N ^frame,μ _slot =40, and N ^subframe,μ _slot =4.

In a wireless communication system according to an aspect of this embodiment, a time unit _Tc may be used to express a length in the time domain. The time unit _Tc is _Tc = 1/(Δf _max · N _f ). _{Δf max} = 480 kHz. N _f = 4096. The constant κ is κ = Δf _max · N _f / (Δf _ref N _f,ref ) = 64. _{Δf ref} is 15 kHz. _{N f,ref} is 2048.

The transmission of signals in the downlink and/or the transmission of signals in the uplink may be organized into radio frames (system frames, frames) of length _Tf , where _Tf = ( _{Δfmax Nf} /100)· _Ts = 10 ms. "·" indicates multiplication. A radio frame includes 10 subframes. The length of a subframe is _Tsf = ( _{Δfmax Nf} /1000)· _Ts = 1 ms. The number of OFDM symbols per subframe is Nsubframe ^,μsymb ₌ ^Nslotsymb _Nsubframe ^,μslot _.

For a certain subcarrier spacing setting μ, the number and index of slots included in a subframe may be given. For example, slot index n ^μ _s may be given in ascending order as integer values ranging from 0 to N ^subframe,μ _slot −1 in a subframe. For a certain subcarrier spacing setting μ, the number and index of slots included in a radio frame may be given. Also, slot index n ^μ _s,f may be given in ascending order as integer values ranging from 0 to N ^frame,μ _slot −1 in a radio frame. N ^slot _symb consecutive OFDM symbols may be included in one slot. N ^slot _symb =14.

Fig. 3 is a diagram showing an example of a resource grid configuration method according to one aspect of this embodiment. The horizontal axis in Fig. 3 represents the frequency domain. Fig. 3 shows an example of a resource grid configuration with subcarrier spacing μ ₁ in a component carrier 300, and an example of a resource grid configuration with subcarrier spacing μ ₂ in the component carrier. In this way, one or more subcarrier spacings may be set for a certain component carrier. In Fig. 3, it is assumed that μ ₁ = μ ₂ - 1, but various aspects of this embodiment are not limited to the condition μ ₁ = μ ₂ - 1.

Component carrier 300 is a band having a predetermined width in the frequency domain.

Point 3000 is an identifier for identifying a certain subcarrier. Point 3000 is also referred to as point A. Common resource block (CRB) set 3100 is a set of common resource blocks for the subcarrier spacing setting μ ₁ .

Of the common resource block set 3100, the common resource block that includes point 3000 (the block indicated by the diagonal line slanting upward to the right in Figure 3) is also referred to as the reference point of the common resource block set 3100. The reference point of the common resource block set 3100 may be the common resource block with index 0 in the common resource block set 3100.

The offset 3011 is the offset from the reference point of the common resource block set 3100 to the reference point of the resource grid 3001. The offset 3011 is indicated by the number of common resource blocks for the subcarrier spacing setting μ _1. The resource grid 3001 includes N ^size,μ _grid1,x common resource blocks starting from the reference point of the resource grid 3001.

Offset 3013 is the offset from the reference point of resource grid 3001 to the reference point (N ^{start, μ} _BWP,i1 ) of BWP (BandWidth Part) 3003 of index i1.

Common resource block set 3200 is a set of common resource blocks for subcarrier spacing setting μ ₂ .

Of the common resource block set 3200, the common resource block that includes point 3000 (the block indicated by the diagonal line slanting upward to the left in Figure 3) is also referred to as the reference point of the common resource block set 3200. The reference point of the common resource block set 3200 may be the common resource block with index 0 in the common resource block set 3200.

The offset 3012 is the offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002. The offset 3012 is indicated by the number of common resource blocks relative to the subcarrier spacing μ _2. The resource grid 3002 includes N ^size,μ _grid2,x common resource blocks starting from the reference point of the resource grid 3002.

Offset 3014 is the offset from the reference point of resource grid 3002 to the reference point (N ^start,μ _BWP,i2 ) of BWP 3004 with index i2.

Fig. 4 is a diagram showing an example of the configuration of a resource grid 3001 according to one aspect of this embodiment. In the resource grid of Fig. 4, the horizontal axis represents the OFDM symbol index l _sym and the vertical axis represents the subcarrier index k _sc . The resource grid 3001 includes N ^size,μ _grid1,× N ^RB _sc subcarriers and N ^subframe,μ _symb OFDM symbols. Within the resource grid, a resource identified by the subcarrier index k _sc and the OFDM symbol index l _sym is also referred to as a resource element (RE).

A resource block (RB) includes N ^RB _sc consecutive subcarriers. The resource block is a collective term for a common resource block, a physical resource block (PRB), and a virtual resource block (VRB), where N ^RB _sc =12.

A resource block unit is a set of resources corresponding to one OFDM symbol in one resource block. That is, one resource block unit contains 12 resource elements corresponding to one OFDM symbol in one resource block.

The common resource blocks for a given subcarrier spacing setting μ are indexed in a given common resource block set in the frequency domain in ascending order starting from 0. For a given subcarrier spacing setting μ, the common resource block with index 0 includes (or collides with, or coincides with) point 3000. The common resource block index n ^μ _CRB for a given subcarrier spacing setting μ satisfies the relationship n ^μ _CRB = ceil(k _sc /N ^RB _sc ), where the subcarrier with k _sc = 0 is the subcarrier with the same center frequency as the subcarrier corresponding to point 3000.

The physical resource blocks for a given subcarrier spacing setting μ are indexed in the frequency domain in ascending order starting from 0 in a given BWP. The physical resource block index n ^μ _PRB for a given subcarrier spacing setting μ satisfies the relationship n ^μ _CRB = n ^μ _PRB + N ^start,μ _BWP,i , where N ^start,μ _BWP,i denotes the reference point of the BWP with index i.

A BWP is defined as a subset of common resource blocks included in a resource grid. A BWP includes N ^size, μ _BWP,i common resource blocks starting from the reference point N ^start, μ _BWP,i of the BWP. A BWP configured for a downlink carrier is also called a downlink BWP. A BWP configured for an uplink component carrier is also called an uplink BWP.

An antenna port may be defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. For example, a channel may correspond to a physical channel. A symbol may correspond to an OFDM symbol. A symbol may correspond to a resource block unit. A symbol may correspond to a resource element.

When the large-scale properties of a channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at another antenna port, the two antenna ports are said to be Quasi Co-Located (QCL). The large-scale properties may include at least the long-range characteristics of the channel. The large-scale properties may include at least some or all of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. The first and second antenna ports being QCL with respect to beam parameters may mean that the receive beam assumed by the receiver for the first antenna port is the same as the receive beam assumed by the receiver for the second antenna port. The first antenna port and the second antenna port being QCL with respect to beam parameters may mean that the transmission beam assumed by the receiving side for the first antenna port and the transmission beam assumed by the receiving side for the second antenna port are the same. The terminal device 1 may assume that the two antenna ports are QCL if the large-scale characteristics of a channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at another antenna port. The two antenna ports being QCL may mean that the two antenna ports are assumed to be QCL.

Carrier aggregation may be performing communication using multiple aggregated serving cells. Also, carrier aggregation may be performing communication using multiple aggregated component carriers. Also, carrier aggregation may be performing communication using multiple aggregated downlink component carriers. Also, carrier aggregation may be performing communication using multiple aggregated uplink component carriers.

Figure 5 is a schematic block diagram showing an example configuration of a base station device 3 according to one aspect of this embodiment. As shown in Figure 5, the base station device 3 includes at least a radio transceiver unit (physical layer processing unit) 30 and/or part or all of an upper layer processing unit 34. The radio transceiver unit 30 includes at least an antenna unit 31, an RF (Radio Frequency) unit 32, and part or all of a baseband unit 33. The upper layer processing unit 34 includes at least a medium access control layer processing unit 35 and part or all of a radio resource control (RRC) layer processing unit 36.

The wireless transceiver unit 30 includes at least a wireless transmitter unit 30a and part or all of a wireless receiver unit 30b. Here, the baseband unit included in the wireless transmitter unit 30a and the baseband unit included in the wireless receiver unit 30b may have the same or different device configurations. Furthermore, the RF unit included in the wireless transmitter unit 30a and the RF unit included in the wireless receiver unit 30b may have the same or different device configurations. Furthermore, the antenna unit included in the wireless transmitter unit 30a and the antenna unit included in the wireless receiver unit 30b may have the same or different device configurations.

For example, the radio transmitting unit 30a may generate and transmit a baseband signal for the PDSCH. For example, the radio transmitting unit 30a may generate and transmit a baseband signal for the PDCCH. For example, the radio transmitting unit 30a may generate and transmit a baseband signal for the PBCH. For example, the radio transmitting unit 30a may generate and transmit a baseband signal for a synchronization signal. For example, the radio transmitting unit 30a may generate and transmit a baseband signal for the PDSCH DMRS. For example, the radio transmitting unit 30a may generate and transmit a baseband signal for the PDCCH DMRS. For example, the radio transmitting unit 30a may generate and transmit a baseband signal for the CSI-RS. For example, the radio transmitting unit 30a may generate and transmit a baseband signal for the DL PTRS.

For example, the radio receiving unit 30b may receive a PRACH. For example, the radio receiving unit 30b may receive and demodulate a PUCCH. The radio receiving unit 30b may receive and demodulate a PUSCH. For example, the radio receiving unit 30b may receive a PUCCH DMRS. For example, the radio receiving unit 30b may receive a PUSCH DMRS. For example, the radio receiving unit 30b may receive a UL PTRS. For example, the radio receiving unit 30b may receive an SRS.

The upper layer processing unit 34 outputs the downlink data (transport block) to the radio transceiver unit 30 (or the radio transmitter unit 30a). The upper layer processing unit 34 processes the MAC (Medium Access Control) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the RRC layer.

The media access control layer processing unit 35 provided in the upper layer processing unit 34 performs MAC layer processing.

The radio resource control layer processing unit 36 included in the upper layer processing unit 34 performs RRC layer processing. The radio resource control layer processing unit 36 manages various setting information/parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 36 sets the RRC parameters based on the RRC message received from the terminal device 1.

The radio transceiver unit 30 (or the radio transmitter unit 30a) performs processes such as modulation and encoding. The radio transceiver unit 30 (or the radio transmitter unit 30a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting it into a time-continuous signal) the downlink data, and transmits it to the terminal device 1. The radio transceiver unit 30 (or the radio transmitter unit 30a) may place the physical signal on a component carrier and transmit it to the terminal device 1.

The radio transceiver unit 30 (or the radio receiver unit 30b) performs processes such as demodulation and decoding. The radio transceiver unit 30 (or the radio receiver unit 30b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 34. The radio transceiver unit 30 (or the radio receiver unit 30b) may perform a channel access procedure prior to transmitting the physical signal.

The RF unit 32 converts (down-converts) the signal received via the antenna unit 31 into a baseband signal by quadrature demodulation and removes unnecessary frequency components. The RF unit 32 outputs the processed analog signal to the baseband unit.

The baseband unit 33 converts the analog signal input from the RF unit 32 into a digital signal. The baseband unit 33 removes the portion corresponding to the cyclic prefix (CP) from the converted digital signal, and performs a fast Fourier transform (FFT) on the CP-removed signal to extract the frequency domain signal.

The baseband unit 33 performs an Inverse Fast Fourier Transform (IFFT) on the data to generate OFDM symbols, adds a CP to the generated OFDM symbols, generates baseband digital signals, and converts the baseband digital signals to analog signals. The baseband unit 33 outputs the converted analog signals to the RF unit 32.

The RF unit 32 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 33, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 31. The RF unit 32 may also have a function to control transmission power. The RF unit 32 is also referred to as a transmission power control unit.

One or more serving cells (or component carriers, downlink component carriers, uplink component carriers) may be configured for the terminal device 1.

Each of the serving cells configured for the terminal device 1 may be either a PCell (Primary cell), a PSCell (Primary SCG cell), or an SCell (Secondary Cell).

PCell is a serving cell included in the MCG (Master Cell Group). PCell is the cell in which the terminal device 1 performs the initial connection establishment procedure or the connection re-establishment procedure (the cell in which the procedure was performed).

A PSCell is a serving cell included in an SCG (Secondary Cell Group). A PSCell is a serving cell to which random access is performed by terminal device 1 during a reconfiguration procedure with synchronization.

The SCell may be included in either the MCG or the SCG.

Serving cell group (cell group) is a term that includes at least MCG and SCG. A serving cell group may include one or more serving cells (or component carriers). One or more serving cells (or component carriers) included in a serving cell group may be operated by carrier aggregation.

One or more downlink BWPs may be configured for each serving cell (or downlink component carrier). One or more uplink BWPs may be configured for each serving cell (or uplink component carrier).

Of one or more downlink BWPs configured for a serving cell (or a downlink component carrier), one downlink BWP may be set as the active downlink BWP (or one downlink BWP may be activated). Of one or more uplink BWPs configured for a serving cell (or an uplink component carrier), one uplink BWP may be set as the active uplink BWP (or one uplink BWP may be activated).

The PDSCH, PDCCH, and CSI-RS may be received in an active downlink BWP. The terminal device 1 may receive the PDSCH, PDCCH, and CSI-RS in an active downlink BWP. The PUCCH and PUSCH may be transmitted in an active uplink BWP. The terminal device 1 may transmit the PUCCH and PUSCH in an active uplink BWP. The active downlink BWP and the active uplink BWP are also referred to as active BWPs.

The PDSCH, PDCCH, and CSI-RS do not have to be received in downlink BWPs (inactive downlink BWPs) other than the active downlink BWP. The terminal device 1 does not have to receive the PDSCH, PDCCH, and CSI-RS in downlink BWPs other than the active downlink BWP. The PUCCH and PUSCH do not have to be transmitted in uplink BWPs (inactive uplink BWPs) other than the active uplink BWP. The terminal device 1 does not have to transmit the PUCCH and PUSCH in uplink BWPs other than the active uplink BWP. The inactive downlink BWP and the inactive uplink BWP are also referred to as inactive BWPs.

Downlink BWP switch is used to deactivate one active downlink BWP and activate any inactive downlink BWP other than the one active downlink BWP. Downlink BWP switch may be controlled by the BWP field included in downlink control information. Downlink BWP switch may also be controlled based on higher layer parameters.

Uplink BWP switching is used to deactivate one active uplink BWP and activate any inactive uplink BWPs other than the one active uplink BWP. Uplink BWP switching may be controlled by the BWP field included in the downlink control information. Uplink BWP switching may also be controlled based on higher layer parameters.

Of one or more downlink BWPs configured for a serving cell, two or more downlink BWPs may not be configured as active downlink BWPs. For a serving cell, one downlink BWP may be active at any given time.

Of one or more uplink BWPs configured for a serving cell, two or more uplink BWPs may not be configured as active uplink BWPs. For a serving cell, one uplink BWP may be active at any given time.

Figure 6 is a schematic block diagram showing an example configuration of a terminal device 1 according to one aspect of this embodiment. As shown in Figure 6, the terminal device 1 includes at least a radio transceiver unit (physical layer processing unit) 10 and one or all of an upper layer processing unit 14. The radio transceiver unit 10 includes at least an antenna unit 11, an RF unit 12, and some or all of a baseband unit 13. The upper layer processing unit 14 includes at least a medium access control layer processing unit 15 and some or all of a radio resource control layer processing unit 16.

The wireless transceiver unit 10 includes at least a wireless transmitter unit 10a and part or all of a wireless receiver unit 10b. Here, the baseband unit 13 included in the wireless transmitter unit 10a and the baseband unit 13 included in the wireless receiver unit 10b may have the same or different device configurations. Furthermore, the RF unit 12 included in the wireless transmitter unit 10a and the RF unit 12 included in the wireless receiver unit 10b may have the same or different device configurations. Furthermore, the antenna unit 11 included in the wireless transmitter unit 10a and the antenna unit 11 included in the wireless receiver unit 10b may have the same or different device configurations.

For example, the radio transmitting unit 10a may generate and transmit a baseband signal for the PRACH. For example, the radio transmitting unit 10a may generate and transmit a baseband signal for the PUCCH. The radio transmitting unit 10a may generate and transmit a baseband signal for the PUSCH. For example, the radio transmitting unit 10a may generate and transmit a baseband signal for the PUCCH DMRS. For example, the radio transmitting unit 10a may generate and transmit a baseband signal for the PUSCH DMRS. For example, the radio transmitting unit 10a may generate and transmit a baseband signal for the UL PTRS. For example, the radio transmitting unit 10a may generate and transmit a baseband signal for the SRS.

For example, the radio receiving unit 10b may receive and demodulate the PDSCH. For example, the radio receiving unit 10b may receive and demodulate the PDCCH. For example, the radio receiving unit 10b may receive and demodulate the PBCH. For example, the radio receiving unit 10b may receive a synchronization signal. For example, the radio receiving unit 10b may receive a PDSCH DMRS. For example, the radio receiving unit 10b may receive a PDCCH DMRS. For example, the radio receiving unit 10b may receive a CSI-RS. For example, the radio receiving unit 10b may receive a DL PTRS.

The upper layer processing unit 14 outputs the uplink data (transport block) to the radio transceiver unit 10 (or the radio transmitter unit 10a). The upper layer processing unit 14 processes the MAC layer, packet data integration protocol layer, radio link control layer, and RRC layer.

The media access control layer processing unit 15 provided in the upper layer processing unit 14 performs MAC layer processing.

The radio resource control layer processing unit 16 provided in the upper layer processing unit 14 performs RRC layer processing. The radio resource control layer processing unit 16 manages various setting information/parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 16 sets the RRC parameters based on the RRC message received from the base station device 3.

The radio transceiver unit 10 (or the radio transmitter unit 10a) performs processes such as modulation and encoding. The radio transceiver unit 10 (or the radio transmitter unit 10a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting to a time-continuous signal) the uplink data, and transmits it to the base station device 3. The radio transceiver unit 10 (or the radio transmitter unit 10a) may place the physical signal in a certain BWP (active uplink BWP) and transmit it to the base station device 3.

The radio transceiver unit 10 (or the radio receiver unit 10b) performs processes such as demodulation and decoding. The radio transceiver unit 10 (or the radio receiver unit 30b) may receive a physical signal in a certain BWP (active downlink BWP) of a certain serving cell. The radio transceiver unit 10 (or the radio receiver unit 10b) separates, demodulates, and decodes the received physical signal and outputs the decoded information to the upper layer processing unit 14. The radio transceiver unit 10 (radio receiver unit 10b) may perform a channel access procedure prior to transmitting the physical signal.

The RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by quadrature demodulation (down-converting) and removes unnecessary frequency components. The RF unit 12 outputs the processed analog signal to the baseband unit 13.

The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 removes the portion corresponding to the cyclic prefix (CP) from the converted digital signal, and performs a fast Fourier transform (FFT) on the CP-removed signal to extract the frequency domain signal.

The baseband unit 13 performs an Inverse Fast Fourier Transform (IFFT) on the uplink data to generate OFDM symbols, adds a CP to the generated OFDM symbols, generates baseband digital signals, and converts the baseband digital signals to analog signals. The baseband unit 13 outputs the converted analog signals to the RF unit 12.

The RF unit 12 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 13, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 11. The RF unit 12 may also have a function to control transmission power. The RF unit 12 is also referred to as a transmission power control unit.

The following explains physical signals (signals).

Physical signal is a general term for downlink physical channel, downlink physical signal, uplink physical channel, and uplink physical channel. Physical channel is a general term for downlink physical channel and uplink physical channel. Physical signal is a general term for downlink physical signal and uplink physical signal.

The uplink physical channel may correspond to a set of resource elements carrying information generated in a higher layer. The uplink physical channel may be a physical channel used in an uplink component carrier. The uplink physical channel may be transmitted by a terminal device 1. The uplink physical channel may be received by a base station device 3. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following uplink physical channels may be used.
・PUCCH (Physical Uplink Control CHannel)
・PUSCH (Physical Uplink Shared CHannel)
・PRACH (Physical Random Access CHannel)

The PUCCH may be used to transmit uplink control information (UCI). The PUCCH may be transmitted to deliver, transmit, or convey the uplink control information. The uplink control information may be mapped to the PUCCH. The terminal device 1 may transmit a PUCCH in which the uplink control information is mapped. The base station device 3 may receive a PUCCH in which the uplink control information is mapped.

The uplink control information (uplink control information bits, uplink control information sequence, uplink control information type) includes at least some or all of the channel state information (CSI), scheduling request (SR), and HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement) information.

Channel state information is also referred to as channel state information bits or channel state information sequences. Scheduling requests are also referred to as scheduling request bits or scheduling request sequences. HARQ-ACK information is also referred to as HARQ-ACK information bits or HARQ-ACK information sequences.

The HARQ-ACK information may include at least a HARQ-ACK corresponding to a transport block (TB: Transport block, MAC PDU: Medium Access Control Protocol Data Unit, DL-SCH: Downlink-Shared Channel, UL-SCH: Uplink-Shared Channel, PDSCH: Physical Downlink Shared Channel, PUSCH: Physical Uplink Shared CHannel). The HARQ-ACK may indicate an acknowledgement (ACK) or a negative acknowledgement (NACK) corresponding to the transport block. An ACK may indicate that decoding of the transport block has been successfully completed. A NACK may indicate that decoding of the transport block has not been successfully completed. The HARQ-ACK information may include a HARQ-ACK codebook including one or more HARQ-ACK bits.

Correspondence between HARQ-ACK information and a transport block may mean that the HARQ-ACK information and the PDSCH used to transmit the transport block correspond to each other.

HARQ-ACK may indicate an ACK or NACK corresponding to one CBG (Code Block Group) included in the transport block.

The scheduling request may be used at least to request PUSCH (or UL-SCH) resources for an initial transmission. The scheduling request bit may be used to indicate either a positive SR or a negative SR. When the scheduling request bit indicates a positive SR, this is also referred to as "a positive SR being transmitted." A positive SR may indicate that PUSCH (or UL-SCH) resources are requested by the terminal device 1 for the initial transmission. A positive SR may indicate that a scheduling request is triggered by a higher layer. A positive SR may be transmitted when a scheduling request is instructed to be transmitted by a higher layer. When the scheduling request bit indicates a negative SR, this is also referred to as "a negative SR being transmitted." A negative SR may indicate that PUSCH (or UL-SCH) resources are not requested by the terminal device 1 for the initial transmission. A negative SR may indicate that no scheduling request is triggered by higher layers. A negative SR may be sent when no scheduling request is instructed to be sent by higher layers.

The channel state information may include at least some or all of a Channel Quality Indicator (CQI), a Precoder Matrix Indicator (PMI), and a Rank Indicator (RI). The CQI is an indicator related to the quality of the propagation path (e.g., propagation strength) or the quality of the physical channel, and the PMI is an indicator related to the precoder. The RI is an indicator related to the transmission rank (or the number of transmission layers).

The channel state information may be provided based at least on receiving a physical signal (e.g., CSI-RS) used at least for channel measurement. The channel state information may be selected by the terminal device 1 based at least on receiving a physical signal used at least for channel measurement. The channel measurement may include interference measurement.

A PUCCH may correspond to a PUCCH format. A PUCCH may be a set of resource elements used to convey the PUCCH format. A PUCCH may include the PUCCH format.

The PUSCH may be used to transmit transport blocks and/or uplink control information. The PUSCH may be used to transmit transport blocks corresponding to the UL-SCH and/or uplink control information. The PUSCH may be used to transmit transport blocks and/or uplink control information. The PUSCH may be used to transmit transport blocks corresponding to the UL-SCH and/or uplink control information. The transport blocks may be allocated to the PUSCH. The transport blocks corresponding to the UL-SCH may be allocated to the PUSCH. The uplink control information may be allocated to the PUSCH. The terminal device 1 may transmit a PUSCH in which transport blocks and/or uplink control information are allocated. The base station device 3 may receive a PUSCH in which transport blocks and/or uplink control information are allocated.

The PRACH may be used to transmit a random access preamble. The PRACH may be used to transmit a random access preamble. A PRACH sequence _xu,v (n) is defined by xu _,v (n) = _xu (mod(n+ _Cv , _LRA )). _xu may be a ZC (Zadoff-Chu) sequence. _xu is defined by _xu = exp(-jπui(i+1)/ _LRA ), where j is the imaginary unit and π is the ratio of the circumference of a circle to its circumference. _Cv corresponds to a cyclic shift of the PRACH sequence. _LRA corresponds to the length of the PRACH sequence. _LRA is 839 or 139. i is an integer ranging from 0 to _LRA -1. u is a sequence index for the PRACH sequence. The terminal device 1 may transmit the PRACH, and the base station device 3 may receive the PRACH.

For a given PRACH opportunity, 64 random access preambles are defined. The random access preambles are identified (determined or given) based on at least a cyclic shift _Cv of the PRACH sequence and a sequence index u for the PRACH sequence. Each of the 64 identified random access preambles may be assigned an index.

The uplink physical signal may correspond to a set of resource elements. The uplink physical signal may not carry information generated in a higher layer. The uplink physical signal may be a physical signal used in an uplink component carrier. The terminal device 1 may transmit the uplink physical signal. The base station device 3 may receive the uplink physical signal. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following uplink physical signals may be used.
・UL DMRS (UpLink Demodulation Reference Signal)
・SRS (Sounding Reference Signal)
・UL PTRS (UpLink Phase Tracking Reference Signal)

UL DMRS is a general term for DMRS for PUSCH and DMRS for PUCCH.

The set of antenna ports for DMRS for PUSCH (DMRS associated with PUSCH, DMRS included in PUSCH, DMRS corresponding to PUSCH) may be determined based on the set of antenna ports for the PUSCH. In other words, the set of antenna ports for DMRS for PUSCH may be the same as the set of antenna ports for the PUSCH.

The transmission of a PUSCH and the transmission of a DMRS for the PUSCH may be indicated (or scheduled) by one DCI format. The PUSCH and the DMRS for the PUSCH may be collectively referred to as a PUSCH. Transmitting a PUSCH may mean transmitting a PUSCH and a DMRS for the PUSCH.

The PUSCH may be estimated from the DMRS for the PUSCH. In other words, the propagation path of the PUSCH may be estimated from the DMRS for the PUSCH.

The set of antenna ports for DMRS for PUCCH (DMRS associated with PUCCH, DMRS included in PUCCH, DMRS corresponding to PUCCH) may be the same as the set of antenna ports for PUCCH.

Transmission of a PUCCH and transmission of a DMRS for the PUCCH may be indicated (or triggered) by one DCI format. The mapping of the PUCCH to resource elements and/or the mapping of the DMRS for the PUCCH to resource elements may be provided by one PUCCH format. The PUCCH and the DMRS for the PUCCH may be collectively referred to as the PUCCH. Transmitting a PUCCH may also mean transmitting the PUCCH and the DMRS for the PUCCH.

The PUCCH may be estimated from the DMRS for the PUCCH. In other words, the propagation path of the PUCCH may be estimated from the DMRS for the PUCCH.

The downlink physical channel may correspond to a set of resource elements carrying information generated in a higher layer. The downlink physical channel may be a physical channel used in a downlink component carrier. The base station device 3 may transmit the downlink physical channel. The terminal device 1 may receive the downlink physical channel. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following downlink physical channels may be used.
・PBCH (Physical Broadcast Channel)
・PDCCH (Physical Downlink Control Channel)
・PDSCH (Physical Downlink Shared Channel)

The PBCH may be used to transmit a Master Information Block (MIB) and/or physical layer control information. The PBCH may be transmitted to deliver, transmit, or convey the MIB and/or physical layer control information. The BCH may be mapped to the PBCH. The terminal device 1 may receive a PBCH in which the MIB and/or physical layer control information is mapped. The base station device 3 may transmit a PBCH in which the MIB and/or physical layer control information is mapped. The physical layer control information is also called a PBCH payload or a PBCH payload related to timing. The MIB may include one or more higher layer parameters.

The physical layer control information includes 8 bits. The physical layer control information may include at least some or all of the following 0A to 0D:
0A) Radio frame bit 0B) Half radio frame (half system frame, half frame) bit 0C) SS/PBCH block index bit 0D) Subcarrier offset bit

The radio frame bits are used to indicate the radio frame in which the PBCH is transmitted (the radio frame including the slot in which the PBCH is transmitted). The radio frame bits include 4 bits. The radio frame bits may be composed of 4 bits of a 10-bit radio frame indicator. For example, the radio frame indicator may be used at least to identify radio frames with index 0 to index 1023.

The half radio frame bit is used to indicate whether the PBCH is transmitted in the first five subframes or the last five subframes of a radio frame in which the PBCH is transmitted. Here, a half radio frame may be composed of five subframes. Alternatively, a half radio frame may be composed of the first five subframes of the ten subframes included in a radio frame. Alternatively, a half radio frame may be composed of the last five subframes of the ten subframes included in a radio frame.

The SS/PBCH block index bits are used to indicate the SS/PBCH block index. The SS/PBCH block index bits include 3 bits. The SS/PBCH block index bits may be configured by 3 bits of the 6-bit SS/PBCH block index indicator. The SS/PBCH block index indicator may be used at least to identify SS/PBCH blocks from index 0 to index 63.

The subcarrier offset bit is used to indicate the subcarrier offset. The subcarrier offset may be used to indicate the difference between the first subcarrier to which the PBCH is mapped and the first subcarrier to which the control resource set with index 0 is mapped.

The PDCCH may be used to transmit downlink control information (DCI). The PDCCH may be transmitted to deliver, transmit, or convey the downlink control information. The downlink control information may be mapped to the PDCCH. The terminal device 1 may receive the PDCCH in which the downlink control information is mapped. The base station device 3 may transmit the PDCCH in which the downlink control information is mapped.

The downlink control information may correspond to a DCI format. The downlink control information may be included in the DCI format. The downlink control information may be placed in each field of the DCI format.

DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1 are DCI formats that each include a different set of fields. The uplink DCI format is a general term for DCI format 0_0 and DCI format 0_1. The downlink DCI format is a general term for DCI format 1_0 and DCI format 1_1.

DCI format 0_0 is used at least for scheduling a PUSCH of a certain cell (or configured in a certain cell), and is configured to include at least some or all of fields 1A to 1E.
1A) Identifier field for DCI formats
1B) Frequency Domain Resource Assignment Field
1C) Time Domain Resource Assignment Field
1D) Frequency hopping flag field
1E) MCS field (Modulation and Coding Scheme field)

The DCI format specification field may indicate whether the DCI format containing the DCI format specification field is an uplink DCI format or a downlink DCI format. The DCI format specification field included in DCI format 0_0 may indicate 0 (or may indicate that DCI format 0_0 is an uplink DCI format).

The frequency domain resource allocation field included in DCI format 0_0 may be used at least to indicate the allocation of frequency resources for PUSH.

The time domain resource allocation field included in DCI format 0_0 may be used at least to indicate the allocation of time resources for PUSH.

The frequency hopping flag field may be used at least to indicate whether frequency hopping is applied to the PUSH.

The MCS field included in DCI format 0_0 may be used to indicate at least some or all of the modulation scheme and/or target coding rate for the PUSCH. The target coding rate may be the target coding rate for the PUSCH transport block. The size of the PUSCH transport block (TBS) may be determined based on at least some or all of the target coding rate and the modulation scheme for the PUSCH.

DCI format 0_0 may not include fields used for CSI requests. In other words, CSI may not be requested by DCI format 0_0.

DCI format 0_0 may not include a carrier indicator field. In other words, the uplink component carrier on which the PUSCH scheduled by DCI format 0_0 is allocated may be the same as the uplink component carrier on which the PDCCH including DCI format 0_0 is allocated.

DCI format 0_0 may not include a BWP field. In other words, the uplink BWP in which the PUSH scheduled by DCI format 0_0 is placed may be the same as the uplink BWP in which the PDCCH including DCI format 0_0 is placed.

DCI format 0_1 is used at least for scheduling a PUSCH of a certain cell (located in a certain cell), and is configured to include at least some or all of fields 2A to 2H.
2A) DCI format specific field 2B) Frequency domain resource allocation field 2C) Uplink time domain resource allocation field 2D) Frequency hopping flag field 2E) MCS field 2F) CSI request field
2G) BWP field
2H) Carrier Indicator Field

The DCI format specific field included in DCI format 0_1 may indicate 0 (or may indicate that DCI format 0_1 is an uplink DCI format).

The frequency domain resource allocation field included in DCI format 0_1 may be used at least to indicate the allocation of frequency resources for PUSH.

The time domain resource allocation field included in DCI format 0_1 may be used at least to indicate the allocation of time resources for PUSH.

The MCS field included in DCI format 0_1 may be used to indicate at least some or all of the modulation scheme and/or target coding rate for the PUSH.

If DCI format 0_1 includes a BWP field, the BWP field may be used to indicate the uplink BWP in which the PUSCH is arranged. If DCI format 0_1 does not include a BWP field, the uplink BWP in which the PUSCH is arranged may be the same as the uplink BWP in which the PDCCH including DCI format 0_1 used for scheduling the PUSCH is arranged. If the number of uplink BWPs configured in the terminal device 1 for a certain uplink component carrier is two or more, the number of bits in the BWP field included in DCI format 0_1 used for scheduling the PUSCH to be arranged on the certain uplink component carrier may be one or more. When the number of uplink BWPs set in a terminal device 1 for a certain uplink component carrier is 1, the number of bits in the BWP field included in DCI format 0_1 used for scheduling the PUSH to be placed on the certain uplink component carrier may be 0 bits (or the BWP field may not be included in DCI format 0_1 used for scheduling the PUSH to be placed on the certain uplink component carrier).

The CSI request field is used at least to indicate the reporting of CSI.

If DCI format 0_1 includes a carrier indicator field, the carrier indicator field may be used to indicate the uplink component carrier on which the PUSCH is allocated. If DCI format 0_1 does not include a carrier indicator field, the uplink component carrier on which the PUSCH is allocated may be the same as the uplink component carrier on which the PDCCH including DCI format 0_1 used for scheduling the PUSCH is allocated. If the number of uplink component carriers configured in the terminal device 1 in a certain serving cell group is two or more (if uplink carrier aggregation is operated in a certain serving cell group), the number of bits of the carrier indicator field included in DCI format 0_1 used for scheduling the PUSCH allocated to the certain serving cell group may be one bit or more (e.g., three bits). When the number of uplink component carriers configured for a terminal device 1 in a certain serving cell group is 1 (when uplink carrier aggregation is not operated in a certain serving cell group), the number of bits in the carrier indicator field included in DCI format 0_1 used for scheduling the PUSH placed in the certain serving cell group may be 0 bits (or the carrier indicator field may not be included in DCI format 0_1 used for scheduling the PUSH placed in the certain serving cell group).

DCI format 1_0 is used at least for scheduling a PDSCH of a certain cell (located in a certain cell), and is configured to include at least some or all of 3A to 3F.
3A) DCI format specific field 3B) Frequency domain resource allocation field 3C) Time domain resource allocation field 3D) MCS field 3E) PDSCH to HARQ feedback timing indicator field
3F) PUCCH resource indicator field

The DCI format specific field included in DCI format 1_0 may indicate 1 (or may indicate that DCI format 1_0 is a downlink DCI format).

The frequency domain resource allocation field included in DCI format 1_0 may be used at least to indicate the allocation of frequency resources for PDSCH.

The time domain resource allocation field included in DCI format 1_0 may be used at least to indicate the allocation of time resources for PDSCH.

The MCS field included in DCI format 1_0 may be used to indicate at least some or all of the modulation scheme and/or target coding rate for the PDSCH. The target coding rate may be the target coding rate for the transport block of the PDSCH. The size of the transport block (TBS) of the PDSCH may be determined based on at least some or all of the target coding rate and the modulation scheme for the PDSCH.

The PDSCH_HARQ feedback timing indication field may be used at least to indicate the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH.

The PUCCH resource indication field may be a field indicating the index of one or more PUCCH resources included in a PUCCH resource set. A PUCCH resource set may include one or more PUCCH resources.

DCI format 1_0 may not include a carrier indicator field. In other words, the downlink component carrier on which the PDSCH scheduled by DCI format 1_0 is allocated may be the same as the downlink component carrier on which the PDCCH including DCI format 1_0 is allocated.

DCI format 1_0 may not include a BWP field. In other words, the downlink BWP in which the PDSCH scheduled by DCI format 1_0 is placed may be the same as the downlink BWP in which the PDCCH including DCI format 1_0 is placed.

DCI format 1_1 is used at least for scheduling a PDSCH of a certain cell (or configured in a certain cell), and is configured to include at least some or all of 4A to 4I.
4A) DCI format specific field 4B) Frequency domain resource allocation field 4C) Time domain resource allocation field 4E) MCS field 4F) PDSCH_HARQ feedback timing indication field 4G) PUCCH resource indication field 4H) BWP field 4I) Carrier indicator field

The DCI format specific field included in DCI format 1_1 may indicate 1 (or may indicate that DCI format 1_1 is a downlink DCI format).

The frequency domain resource allocation field included in DCI format 1_1 may be used at least to indicate the allocation of frequency resources for PDSCH.

The time domain resource allocation field included in DCI format 1_1 may be used at least to indicate the allocation of time resources for PDSCH.

The MCS field included in DCI format 1_1 may be used to indicate at least some or all of the modulation scheme and/or target coding rate for the PDSCH.

If DCI format 1_1 includes a PDSCH_HARQ feedback timing indication field, the PDSCH_HARQ feedback timing indication field may be used at least to indicate the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH. If DCI format 1_1 does not include a PDSCH_HARQ feedback timing indication field, the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH may be specified by a higher layer parameter.

The PUCCH resource indication field may be a field indicating the index of one or more PUCCH resources included in the PUCCH resource set.

If DCI format 1_1 includes a BWP field, the BWP field may be used to indicate the downlink BWP in which the PDSCH is arranged. If DCI format 1_1 does not include a BWP field, the downlink BWP in which the PDSCH is arranged may be the same as the downlink BWP in which the PDCCH including DCI format 1_1 used for scheduling the PDSCH is arranged. If the number of downlink BWPs configured in the terminal device 1 for a certain downlink component carrier is two or more, the number of bits in the BWP field included in DCI format 1_1 used for scheduling the PDSCH arranged for the certain downlink component carrier may be one or more. If the number of downlink BWPs configured in the terminal device 1 for a certain downlink component carrier is one, the number of bits in the BWP field included in DCI format 1_1 used for scheduling the PDSCH arranged for the certain downlink component carrier may be zero (or the BWP field may not be included in DCI format 1_1 used for scheduling the PDSCH arranged for the certain downlink component carrier).

If DCI format 1_1 includes a carrier indicator field, the carrier indicator field may be used to indicate the downlink component carrier on which the PDSCH is allocated. If DCI format 1_1 does not include a carrier indicator field, the downlink component carrier on which the PDSCH is allocated may be the same as the downlink component carrier on which the PDCCH including DCI format 1_1 used for scheduling the PDSCH is allocated. If the number of downlink component carriers configured in the terminal device 1 in a serving cell group is two or more (if downlink carrier aggregation is operated in a serving cell group), the number of bits of the carrier indicator field included in DCI format 1_1 used for scheduling the PDSCH allocated to the serving cell group may be one bit or more (e.g., three bits). When the number of downlink component carriers configured for a terminal device 1 in a certain serving cell group is 1 (when downlink carrier aggregation is not operated in a certain serving cell group), the number of bits in the carrier indicator field included in DCI format 1_1 used for scheduling the PDSCH placed in the certain serving cell group may be 0 bits (or the carrier indicator field may not be included in DCI format 1_1 used for scheduling the PDSCH placed in the certain serving cell group).

The PDSCH may be used to transmit a transport block. The PDSCH may be used to transmit a transport block corresponding to the DL-SCH. The PDSCH may be used to transmit a transport block. The PDSCH may be used to transmit a transport block corresponding to the DL-SCH. The transport block may be placed in the PDSCH. The transport block corresponding to the DL-SCH may be placed in the PDSCH. The base station device 3 may transmit the PDSCH. The terminal device 1 may receive the PDSCH.

The downlink physical signal may correspond to a set of resource elements. The downlink physical signal may not carry information generated in a higher layer. The downlink physical signal may be a physical signal used in a downlink component carrier. The downlink physical signal may be transmitted by a base station device 3. The downlink physical signal may be transmitted by a terminal device 1. In a wireless communication system according to one aspect of the present embodiment, at least some or all of the following downlink physical signals may be used.
・Synchronization signal (SS)
・DL DMRS (DownLink DeModulation Reference Signal)
・CSI-RS (Channel State Information-Reference Signal)
・DL PTRS (DownLink Phase Tracking Reference Signal)

The synchronization signal may be used at least by the terminal device 1 to synchronize the frequency domain and/or time domain of the downlink. The synchronization signal is a general term for the PSS (Primary Synchronization Signal) and the SSS (Secondary Synchronization Signal).

7 is a diagram showing an example of the configuration of an SS/PBCH block according to one aspect of this embodiment. In FIG. 7, the horizontal axis represents the time axis (OFDM symbol index l _sym ), and the vertical axis represents the frequency domain. The diagonally shaded blocks represent sets of resource elements for the PSS. The grid-lined blocks represent sets of resource elements for the SSS. The horizontally shaded blocks represent sets of resource elements for the PBCH and DMRS for the PBCH (DMRS associated with the PBCH, DMRS included in the PBCH, and DMRS corresponding to the PBCH).

As shown in Figure 7, the SS/PBCH block includes a PSS, SSS, and PBCH. The SS/PBCH block also includes four consecutive OFDM symbols. The SS/PBCH block includes 240 subcarriers. The PSS is located on the 57th to 183rd subcarriers in the first OFDM symbol. The SSS is located on the 57th to 183rd subcarriers in the third OFDM symbol. The 1st to 56th subcarriers in the first OFDM symbol may be set to zero. The 184th to 240th subcarriers in the first OFDM symbol may be set to zero. The 49th to 56th subcarriers in the third OFDM symbol may be set to zero. The 184th to 192nd subcarriers in the third OFDM symbol may be set to zero. The PBCH is allocated to the 1st to 240th subcarriers of the second OFDM symbol, and to subcarriers where a DMRS for the PBCH is not allocated. The PBCH is allocated to the 1st to 48th subcarriers of the third OFDM symbol, and to subcarriers where a DMRS for the PBCH is not allocated. The PBCH is allocated to the 193rd to 240th subcarriers of the third OFDM symbol, and to subcarriers where a DMRS for the PBCH is not allocated. The PBCH is allocated to the 1st to 240th subcarriers of the fourth OFDM symbol, and to subcarriers where a DMRS for the PBCH is not allocated.

The antenna ports for PSS, SSS, PBCH, and DMRS for PBCH may be the same.

The PBCH on which the PBCH symbol is transmitted at a certain antenna port may be estimated by the DMRS for the PBCH that is placed in the slot to which the PBCH is mapped and is included in the SS/PBCH block to which the PBCH is included.

DL DMRS is a general term for DMRS for PBCH, DMRS for PDSCH, and DMRS for PDCCH.

The set of antenna ports for DMRS for a PDSCH (DMRS associated with a PDSCH, DMRS included in a PDSCH, DMRS corresponding to a PDSCH) may be determined based on the set of antenna ports for the PDSCH. In other words, the set of antenna ports for DMRS for a PDSCH may be the same as the set of antenna ports for the PDSCH.

The transmission of the PDSCH and the transmission of the DMRS for the PDSCH may be indicated (or scheduled) by one DCI format. The PDSCH and the DMRS for the PDSCH may be collectively referred to as the PDSCH. Transmitting the PDSCH may mean transmitting the PDSCH and the DMRS for the PDSCH.

The PDSCH may be estimated from the DMRS for the PDSCH. That is, the propagation path of the PDSCH may be estimated from the DMRS for the PDSCH. If a set of resource elements on which a certain PDSCH symbol is transmitted and a set of resource elements on which a DMRS symbol for the certain PDSCH is transmitted are included in the same precoding resource group (PRG), the PDSCH on which the PDSCH symbol is transmitted at a certain antenna port may be estimated from the DMRS for the PDSCH.

The antenna port for DMRS for PDCCH (DMRS associated with PDCCH, DMRS included in PDCCH, DMRS corresponding to PDCCH) may be the same as the antenna port for PDCCH.

The PDCCH may be estimated from the DMRS for the PDCCH. That is, the propagation path of the PDCCH may be estimated from the DMRS for the PDCCH. If the same precoder is applied (assumed to be applied, assumed to be applied) to the set of resource elements on which a certain PDCCH symbol is transmitted and the set of resource elements on which a DMRS symbol for the certain PDCCH is transmitted, the PDCCH on which the PDCCH symbol for a certain antenna port is transmitted may be estimated by the DMRS for the PDCCH.

BCH (Broadcast CHannel), UL-SCH (Uplink-Shared CHannel), and DL-SCH (Downlink-Shared CHannel) are transport channels. Channels used in the MAC layer are called transport channels. The unit of transport channel used in the MAC layer is also called a transport block (TB) or MAC PDU (Protocol Data Unit). In the MAC layer, HARQ (Hybrid Automatic Repeat reQuest) control is performed for each transport block. A transport block is a unit of data that the MAC layer delivers to the physical layer. In the physical layer, transport blocks are mapped to codewords, and modulation processing is performed for each codeword.

One UL-SCH and one DL-SCH may be provided for each serving cell. BCH may be provided for the PCell. BCH does not have to be provided for the PSCell or SCell.

The BCCH (Broadcast Control CHannel), CCCH (Common Control CHannel), and DCCH (Dedicated Control CHannel) are logical channels. For example, the BCCH is an RRC layer channel used to transmit MIB or system information. The CCCH (Common Control CHannel) may also be used to transmit RRC messages common to multiple terminal devices 1. Here, the CCCH may be used, for example, for terminal devices 1 that are not RRC-connected. The DCCH (Dedicated Control CHannel) may also be used at least to transmit RRC messages dedicated to terminal devices 1. Here, the DCCH may be used, for example, for terminal devices 1 that are RRC-connected.

An RRC message includes one or more RRC parameters (information elements). For example, an RRC message may include an MIB. An RRC message may also include system information. An RRC message may also include a message corresponding to a CCCH. An RRC message including a message corresponding to a DCCH is also referred to as an individual RRC message.

The BCCH in the logical channel may be mapped to the BCH or DL-SCH in the transport channel. The CCCH in the logical channel may be mapped to the DL-SCH or UL-SCH in the transport channel. The DCCH in the logical channel may be mapped to the DL-SCH or UL-SCH in the transport channel.

The UL-SCH in the transport channel may be mapped to the PUSCH in the physical channel. The DL-SCH in the transport channel may be mapped to the PDSCH in the physical channel. The BCH in the transport channel may be mapped to the PBCH in the physical channel.

Upper layer parameters are parameters contained in RRC messages or MAC CE (Medium Access Control Control Element). In other words, upper layer parameters are a collective term for the parameters contained in the MIB, system information, messages corresponding to CCCH, messages corresponding to DCCH, and MAC CE. Parameters contained in MAC CE are transmitted by MAC CE (Control Element) commands.

The procedure performed by the terminal device 1 includes at least some or all of the following steps 5A to 5C.
5A) Cell Search
5B) Random Access
5C) Data communication

Cell search is a procedure used by terminal device 1 to synchronize with a cell in the time domain and frequency domain and detect a physical cell identity. In other words, terminal device 1 may use cell search to synchronize with a cell in the time domain and frequency domain and detect a physical cell identity.

The PSS sequence is assigned based at least on the physical cell ID. The SSS sequence is assigned based at least on the physical cell ID.

SS/PBCH block candidates indicate resources on which transmission of SS/PBCH blocks is allowed (possible, reserved, configured, specified, possible).

The set of SS/PBCH block candidates in a given half radio frame is also called the SS burst set. The SS burst set is also called the transmission window, SS transmission window, or DRS (Discovery Reference Signal transmission window). The SS burst set is a general term that includes at least the first SS burst set and the second SS burst set.

The base station device 3 transmits SS/PBCH blocks of one or more indexes at a predetermined period. The terminal device 1 may detect at least one SS/PBCH block of the SS/PBCH blocks of the one or more indexes and attempt to decode the PBCH contained in that SS/PBCH block.

Random access is a procedure that includes at least some or all of message 1, message 2, message 3, and message 4.

Message 1 is a procedure for transmitting a PRACH by terminal device 1. Terminal device 1 transmits a PRACH in one PRACH opportunity selected from one or more PRACH opportunities based at least on the index of an SS/PBCH block candidate detected based on cell search. Each PRACH opportunity is defined based at least on resources in the time domain and frequency domain.

The terminal device 1 transmits one random access preamble selected from the PRACH opportunity corresponding to the index of the SS/PBCH block candidate in which the SS/PBCH block is detected.

Message 2 is a procedure in which the terminal device 1 attempts to detect DCI format 1_0 with a CRC (Cyclic Redundancy Check) scrambled with the RA-RNTI (Random Access - Radio Network Temporary Identifier). The terminal device 1 attempts to detect a PDCCH including this DCI format in the control resource set provided based on the MIB included in the PBCH included in the SS/PBCH block detected based on cell search, and in the resources indicated based on the setting of the search space set. Message 2 is also referred to as a random access response.

Message 3 is a procedure for transmitting a PUSCH scheduled by the random access response grant included in DCI format 1_0 detected by the message 2 procedure. Here, the random access response grant is indicated by a MAC CE included in the PDSCH scheduled by DCI format 1_0.

The PUSCH scheduled based on the random access response grant is either a message 3 PUSCH or a PUSCH. The message 3 PUSCH includes a contention resolution identifier (MAC CE). The contention resolution identifier (MAC CE) includes a contention resolution ID.

Message 3 PUSCH retransmission is scheduled using DCI format 0_0 with CRC scrambled based on TC-RNTI (Temporary Cell - Radio Network Temporary Identifier).

Message 4 is a procedure for attempting to detect DCI format 1_0 with a CRC scrambled based on either the C-RNTI (Cell-Radio Network Temporary Identifier) or the TC-RNTI. The terminal device 1 receives a PDSCH scheduled based on the DCI format 1_0. The PDSCH may include a collision resolution ID.

Data communication is a general term for downlink communication and uplink communication.

In data communication, the terminal device 1 attempts to detect the PDCCH in resources identified based on the control resource set and the search space set (monitors the PDCCH, monitors the PDCCH).

A control resource set is a set of resources consisting of a predetermined number of resource blocks and a predetermined number of OFDM symbols. In the frequency domain, a control resource set may be composed of contiguous resources (non-interleaved mapping) or distributed resources (interleaver mapping).

The set of resource blocks that constitute the control resource set may be indicated by higher layer parameters. The number of OFDM symbols that constitute the control resource set may be indicated by higher layer parameters.

The terminal device 1 attempts to detect a PDCCH in a search space set. Here, attempting to detect a PDCCH in a search space set may mean attempting to detect a PDCCH candidate in the search space set, or attempting to detect a DCI format in the search space set, or attempting to detect a PDCCH in a control resource set, or attempting to detect a PDCCH candidate in the control resource set, or attempting to detect a DCI format in the control resource set.

A search space set is defined as a set of PDCCH candidates. The search space set may be a Common Search Space (CSS) set or a UE-specific Search Space (USS) set. The terminal device 1 attempts to detect PDCCH candidates in some or all of the Type 0 PDCCH common search space set, Type 0a PDCCH common search space set, Type 1 PDCCH common search space set, Type 2 PDCCH common search space set, Type 3 PDCCH common search space set, and/or the UE-specific search space set.

The Type 0 PDCCH common search space set may be used as the common search space set with index 0. The Type 0 PDCCH common search space set may be the common search space set with index 0.

The CSS set is a collective term for the Type 0 PDCCH common search space set, Type 0a PDCCH common search space set, Type 1 PDCCH common search space set, Type 2 PDCCH common search space set, and Type 3 PDCCH common search space set. The CSS set is also called the UE-specific PDCCH search space set.

A search space set is associated with (contained in, corresponds to) a control resource set. The index of the control resource set associated with the search space set may be indicated by a higher layer parameter.

For a given search area set, some or all of 6A to 6C may be indicated by at least higher layer parameters.
6A) PDCCH monitoring periodicity
6B) PDCCH monitoring pattern within a slot
6C) PDCCH monitoring offset

A monitoring occasion for a search space set may correspond to an OFDM symbol in which the first OFDM symbol of a control resource set associated with the search space set is located. A monitoring occasion for a search space set may correspond to resources of the control resource set starting from the first OFDM symbol of the control resource set associated with the search space set. The monitoring occasion for the search space set is given based on at least some or all of the PDCCCH monitoring interval, the PDCCCH monitoring pattern within the slot, and the PDCCCH monitoring offset.

Figure 8 is a diagram showing an example of a monitoring opportunity for a search area set according to one aspect of this embodiment. In Figure 8, search area set 91 and search area set 92 are set in primary cell 301, search area set 93 is set in secondary cell 302, and search area set 94 is set in secondary cell 303.

In Figure 8, blocks indicated by grid lines represent search area set 91, blocks indicated by diagonal lines going up to the right represent search area set 92, blocks indicated by diagonal lines going up to the left represent search area set 93, and blocks indicated by horizontal lines represent search area set 94.

The monitoring interval of search area set 91 is set to 1 slot, the monitoring offset of search area set 91 is set to 0 slots, and the monitoring pattern of search area set 91 is set to [1,0,0,0,0,0,0,1,0,0,0,0,0,0]. That is, the monitoring opportunities for search area set 91 correspond to the first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDM symbol #7) in each slot.

The monitoring interval of search area set 92 is set to 2 slots, the monitoring offset of search area set 92 is set to 0 slots, and the monitoring pattern of search area set 92 is set to [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring opportunity for search area set 92 corresponds to the first OFDM symbol (OFDM symbol #0) in each even slot.

The monitoring interval of search area set 93 is set to 2 slots, the monitoring offset of search area set 93 is set to 0 slots, and the monitoring pattern of search area set 93 is set to [0,0,0,0,0,0,0,1,0,0,0,0,0,0]. That is, the monitoring opportunity for search area set 93 corresponds to the 8th OFDM symbol (OFDM symbol #7) in each of the even slots.

The monitoring interval of search area set 94 is set to 2 slots, the monitoring offset of search area set 94 is set to 1 slot, and the monitoring pattern of search area set 94 is set to [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring opportunity for search area set 94 corresponds to the first OFDM symbol (OFDM symbol #0) in each odd slot.

The Type 0 PDCCH common search space set may be used at least for DCI formats with a CRC (Cyclic Redundancy Check) sequence scrambled by the SI-RNTI (System Information-Radio Network Temporary Identifier).

The Type 0a PDCCH common search space set may be used at least for DCI formats with a CRC (Cyclic Redundancy Check) sequence scrambled by the SI-RNTI (System Information-Radio Network Temporary Identifier).

A Type 1 PDCCH common search space set may be used at least for DCI formats with a CRC sequence scrambled by an RA-RNTI (Random Access-Radio Network Temporary Identifier) and/or a CRC sequence scrambled by a TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).

A Type 2 PDCCH common search space set may be used for DCI formats with a CRC sequence scrambled by a P-RNTI (Paging-Radio Network Temporary Identifier).

A Type 3 PDCCH common search space set may be used for DCI formats with a CRC sequence scrambled by a C-RNTI (Cell-Radio Network Temporary Identifier).

The UE-specific PDCCH search area set may be used at least for DCI formats with CRC sequences scrambled by the C-RNTI.

In downlink communication, the terminal device 1 detects the downlink DCI format. The detected downlink DCI format is used at least for PDSCH resource allocation. The detected downlink DCI format is also called downlink assignment. The terminal device 1 attempts to receive the PDSCH. Based on the PUCCH resource indicated based on the detected downlink DCI format, the terminal device 1 reports a HARQ-ACK corresponding to the PDSCH (a HARQ-ACK corresponding to the transport block included in the PDSCH) to the base station device 3.

In uplink communication, the terminal device 1 detects the uplink DCI format. The detected DCI format is used at least for PUSCH resource allocation. The detected uplink DCI format is also called an uplink grant. The terminal device 1 transmits the PUSCH.

In configured scheduling (configured grant), the uplink grant for scheduling the PUSCH is configured for each transmission period of the PUSCH. When the PUSCH is scheduled using an uplink DCI format, some or all of the information indicated by the uplink DCI format may be indicated by the uplink grant configured in the case of configured scheduling.

Figure 9 is a diagram showing an example of transmission based on PUCCH repetition according to one aspect of this embodiment. PUCCH repetition is also referred to as UCI repetition. In Figure 9, the horizontal axis represents the time domain. The grid on the line representing the time domain indicates the slot boundaries. Here, in the upper diagram of Figure 9, the first slot is slot #0. The diagonally shaded blocks below the line representing the time domain indicate that the time domain corresponding to the diagonally shaded blocks is the downlink domain. The vertically shaded blocks below the line representing the time domain indicate that the time domain corresponding to the vertically shaded blocks is the uplink domain. The lower diagram of Figure 9 is an expanded diagram of a portion of slot #3 and slot #4.

In Figure 9, PUCCH is allocated to slot #3 and slot #4. Here, 9001 is the PUCCH instance allocated to OFDM symbol #12 and OFDM symbol #13 of slot #3. Also, 9002 is the PUCCH instance allocated to OFDM symbol #0 to OFDM symbol #13 of slot #4. In this way, it is preferable in some scenarios to divide and allocate PUCCH so that no PUCCH instance occurs across slot boundaries. Here, for example, the PUCCH instance may be a single PUCCH. Also, for example, the PUCCH instance may be one repetition of PUCCH.

Figure 10 is a diagram showing an example configuration of the baseband unit 13 of the terminal device 1 according to one aspect of this embodiment. The baseband unit 13 includes at least some or all of a segmentation unit (Segmentation) 1001, an encoding unit (Encoder) 1002, a rate matching unit (Rate Matcher) 1003, a concatenation unit (Concatenation) 1004, and a multiplexer (Multiplexer) 1005. If any of the units is not included in the baseband unit, that unit may be considered to be short-circuited. For example, if the baseband unit 13 includes the encoding unit 1002, the rate matching unit 1003, and the multiplexer 1004, the segmentation unit 1001 may be considered to be short-circuited. Here, by short-circuiting the segmentation unit 1001, a may be input to c. Also, by short-circuiting the concatenation unit 1004, h may be input to f.

In Fig. 10, a indicates a bit sequence of uplink control information. Bit sequence a includes _a0 , _a1 ,..., _aA-1 . Here, _ak (k is an integer from 0 to A-1) indicates the k-th bit of the bit sequence of uplink control information. Bit sequence a is input to division section 1001. A indicates the number of bits of the uplink control information.

Figure 11 is a diagram showing an example of the operation of the division unit 1001 according to one aspect of this embodiment. Condition 1101 is that A is 12 or greater. If A is 12 or greater, the process proceeds to evaluating condition 1102. Condition 1102 is that at least either condition 1102a or condition 1102b is satisfied. Condition 1102a is that A is 360 or greater and E is 1088 or less. Condition 1102b is that A is 1013 or greater. Here, E indicates the length of the rate matching output sequence. The rate matching output sequence will be described later.

If condition 1102 is satisfied, division section 1001 divides bit sequence a to generate C _UCI code blocks. Furthermore, a CRC sequence is generated for each of the generated C _UCI code blocks. Here, if an index assigned to each of the C _UCI code blocks is r, bit sequence c for code block r output from division section 1001 is a sequence in which a CRC sequence is added to the code block of index r.

If condition 1102 is not satisfied, the division unit 1001 does not divide the bit sequence a, but generates a CRC sequence for the bit sequence a. Here, the bit sequence c output from the division unit 1001 is a sequence in which the CRC sequence is added to the bit sequence a.

If condition 1101 is not satisfied, the division unit 1001 does not divide the bit sequence a, and no CRC sequence is generated. Here, the bit sequence c output from the division unit 1001 is equal to the bit sequence a.

Bit sequence c for code block r includes c ₀ , c ₁ , ..., c _K-1 , where c _k (k is an integer from 0 to K-1) denotes the kth coded bit of bit sequence c. Bit sequence c for code block r is input to coding unit 1002. K denotes the number of bits in the bit sequence for code block r.

The encoding unit 1002 generates an encoded bit sequence d by encoding the bit sequence c. The encoding method used in the encoding unit 1002 may be determined based at least on the number of bits A of the uplink control information. For example, if condition 1101 is satisfied, the encoding method used in the encoding unit 1002 may be a polar code. Also, if condition 1101 is not satisfied, the encoding method used in the encoding unit 1002 may be either a Reed-Muller code or a repetition code.

Figure 12 is a diagram showing an example of a procedure for determining the variable n used in encoding a polar code according to one aspect of this embodiment. In step P1, if E is less than or equal to (9/8) * 2^(ceil(log2(E)) - 1) and K/E is less than 9/16, step P2 is executed. If E is not less than or equal to (9/8) * 2^(ceil(log2(E)) - 1) and/or K/E is not less than 9/16, step P4 is executed. In other words, in step P1, the variable n may be determined based on at least one or both of K and E. Also, in step P1, an array used for polar encoding may be determined based on at least one or both of K and E.

In step P2, ceil(log2(E)-1) is input to variable _n1 .

In step P4, ceil(log2(E)) is input to variable _n1 .

In step P6, 1/8 is input to R _min .

In step P7, ceil(log2(K/R _min )) is input to variable _n2 .

In step P8, max(min(n ₁ , n ₂ , n _max ), n _min ) is input to the variable n.

Here, n _min is 5 and n _max is 10.

Based at least on the value of the variable n determined in step P8, the number of coding bits N after polar coding is determined by N = 2^n. The number of coding bits N corresponds to the size of the array used for polar coding. The array used for polar coding may be determined based at least on the number of coding bits N. Here, the array used for polar coding is also referred to as a matrix, polarization matrix, etc. Furthermore, the array used for polar coding may be an array calculated based on the Kronecker product of the matrix G = [1,0;1,1].

If K is 1, N is set to _Qm , where _Qm represents the order of the modulation scheme of the PUCCH, and if K is 2, N is set to 3* _Qm .

If K is greater than or equal to 3 and less than or equal to 11, N is set to 32. If K is greater than or equal to 3 and less than or equal to 11, a Reed-Muller code may be used to encode the bit sequence c.

The coded bit sequence d for the bit sequence c includes d ₀ , d ₁ , ..., d _N-1 , where d _k (k is an integer from 0 to N-1) indicates the k-th coded bit of the coded bit sequence d. The coded bit sequence d is input to the rate matching unit 1003.

The rate matching unit 1003 generates a rate matching sequence f by applying an interleaver and some or all of bit selection to the input coded bit sequence d. The rate matching sequence f includes f ₀ , f ₁ , ..., f _E-1 , where f _k (k is an integer from 0 to E-1) indicates the k-th coded bit of the rate matching sequence f. The rate matching sequence f is input to the combining unit 1004.

The length E of the rate matching output sequence may be determined based at least on the number of resource elements of the PUCCH entity. The rate matching output sequence E may be determined by E = E _UCI /C _UCI .

The _EUCI may be determined based at least on a combination of uplink control information transmitted on the PUCCH. For example, if the uplink control information transmitted on the PUCCH is HARQ-ACK, the _EUCI may be E _tot . For example, if the uplink control information transmitted on the PUCCH is HARQ-ACK and SR, _{the EUCI} may be E _tot . For example, if the uplink control information transmitted on the PUCCH is CSI, the _EUCI may be E _tot . For example, if the uplink control information transmitted on the PUCCH is HARQ-ACK and CSI, the _EUCI may be E _tot . For example, if the uplink control information transmitted on the PUCCH is HARQ-ACK, SR, and CSI, _{the EUCI} may be E _tot . Here, it is assumed that the CSI is not divided into two parts (two-part CSI). The method of determining E _tot will be described later.

For example, when the uplink control information transmitted on the PUCCH includes at least CSI and the CSI is divided into two parts, E _UCI for the first CSI part may be min(E _tot , ceil((O ^ACK + O ^SR + O ^CSI-part1 + L)/R ^max _UCI /Q _m )·Q _m ). Also, for the second CSI part, E _UCI may be E _tot -min(E _tot , ceil((O ^CSI-part1 + L)/R ^max _UCI /Q _m )·Q _m ). Here, when A is 360 or more, L is 11. Also, when A is not 360 or more, L indicates the number of bits of the CRC sequence. Also, when a CRC sequence is not generated, L is 0. Furthermore, O ^ACK indicates the number of HARQ-ACK bits. Furthermore, if the uplink control information transmitted on the PUCCH does not include HARQ-ACK, O ^ACK is 0. Furthermore, O ^SR indicates the number of SR bits. Furthermore, if the uplink control information transmitted on the PUCCH does not include SR, O ^SR is 0. Furthermore, O ^CSI-part1 indicates the number of bits of the first CSI part. Furthermore, R ^max _UCI indicates the maximum coding rate set in the PUCCH format.

For PUCCH format 2, E _tot is 16*N ^{PUCCH, 2} _{symb, UCI} ·N ^{PUCCH, 2} _PRBs . For PUCCH format 3, E _tot is 12*Q _m *N ^{PUCCH, 3} _{symb, UCI} ·N ^{PUCCH, 3} _PRBs . For PUCCH format 4, E _tot is 12*Q _m *N ^{PUCCH, 4} _{symb, UCI} /N ^{PUCCH, 4} _SFs . Here, N ^{PUCCH, 2} _{symb, UCI} indicates the number of OFDM symbols included in PUCCH format 2 that carry uplink control information. Also, N ^{PUCCH, 3} _{symb, UCI} indicates the number of OFDM symbols included in PUCCH format 3 that carry uplink control information. Furthermore, N ^PUCCH,4 _symb,UCI indicates the number of OFDM symbols included in PUCCH format 4 and carrying uplink control information. Furthermore, N ^PUCCH,2 _PRB indicates the number of resource blocks determined for transmission of PUCCH format 2. Furthermore, N ^PUCCH,3 _PRB indicates the number of resource blocks determined for transmission of PUCCH format 3. Furthermore, N ^PUCCH,4 _SF indicates the spreading factor set for PUCCH format 4.

In this way, the length E of the rate matching output sequence is determined based on at least some or all of the PUCCH modulation scheme, the number of resource blocks determined for transmitting the PUCCH, the number of OFDM symbols conveying uplink control information, the maximum coding rate set for the PUCCH format, and the spreading factor set for the PUCCH format. In other words, in the case of repeated PUCCH transmission as shown in Figure 9, a different number of code blocks and/or a different length of the rate matching output sequence may be determined for each PUCCH entity. A different number of code blocks and/or a different length of the rate matching output sequence for each PUCCH entity may result in cases where the coding procedure by the encoder 1002 differs for each PUCCH entity.

For example, the rate matching unit 1003 may determine the length E of the rate matching output sequence for each of the multiple PUCCH entities. On the other hand, the dividing unit 1001 may assume one value as the length of the rate matching output sequence for each of the multiple PUCCH entities. Also, the coding unit 1002 may assume one value as the length of the rate matching output sequence for each of the multiple PUCCH entities.

For example, the base station device 3 may use one DCI format to trigger the terminal device 1 to transmit S PUCCH entities for transmitting uplink control information. Here, S may be an integer greater than or equal to 2. In some cases, S may be 1. Here, the rate matching unit 1003 may determine a length E _s of a rate-matching output sequence to be determined for the s-th PUCCH entity among the S PUCCH entities. Here, a bit selection operation for the s-th PUCCH entity may be performed based on the determined E _s . Here, s is an integer from 0 to S−1. Note that some of the S PUCCH entities may be scheduled using one DCI format, and other parts of the S PUCCH entities may be scheduled using another DCI format.

For example, the dividing unit 1001 may select the maximum value of E _s and assume the selected maximum value as the length E of the rate matching output sequence. Alternatively, the dividing unit 1001 may determine the average value of E _s and assume the determined average value as the length E of the rate matching output sequence. Alternatively, the dividing unit 1001 may select the minimum value of E _s and assume the selected minimum value as the length E of the rate matching output sequence. Alternatively, the dividing unit 1001 may determine the sum of E _s and assume the determined sum as the length E of the rate matching output sequence. That is, for example, the dividing unit 1001 may determine the expected length E of the rate matching output sequence based at least on each of the lengths E _s of the rate matching output sequence. Alternatively, for example, the dividing unit 1001 may determine the expected length E of the rate matching output sequence using at least two or more of the lengths E _s of the S rate matching output sequences. For example, the dividing unit 1001 may perform encoding based on the expected length E of the rate matching output sequence.

For example, the dividing unit 1001 may select the maximum value of E _s for each of a plurality of PUCCH instances and assume the selected maximum value as the length E of the rate matching output sequence. The dividing unit 1001 may select the maximum value of E _s for each of a plurality of PUCCH repetitions for one PUCCH and assume the selected maximum value as the length E of the rate matching output sequence.

Alternatively, dividing section 1001 may determine an average value of E _s for each of a plurality of PUCCH instances, and assume the determined average value as the length E of the rate-matching output sequence. Dividing section 1001 may determine an average value of E _s for each of a plurality of PUCCH repetitions for one PUCCH, and assume the determined average value as the length E of the rate-matching output sequence.

Alternatively, dividing section 1001 may select the minimum value of E _s for each of a plurality of PUCCH entities, and assume the selected minimum value as the length E of the rate matching output sequence. Dividing section 1001 may select the minimum value of E _s for each of a plurality of PUCCH repetitions for one PUCCH, and assume the selected minimum value as the length E of the rate matching output sequence.

Alternatively, dividing section 1001 may determine the sum of _Es for each of a plurality of PUCCH instances and assume the determined sum as the length E of the rate matching output sequence. Dividing section 1001 may determine the sum of _Es for each of a plurality of PUCCH repetitions for one PUCCH and assume the determined sum as the length E of the rate matching output sequence.

That is, for example, dividing section 1001 may determine the length E of an expected rate matching output sequence based at least on each of the lengths E _s of the rate matching output sequence for each of a plurality of PUCCH entities. Dividing section 1001 may determine the length E of an expected rate matching output sequence for one PUCCH based at least on each of the lengths E _s of the rate matching output sequence for each of a plurality of PUCCH repetitions for one PUCCH.

Furthermore, for example, dividing section 1001 may use at least two or more of S rate matching output sequence lengths E _s for each of a plurality of PUCCH entities to determine expected rate matching output sequence length E. Dividing section 1001 may use at least two or more of S rate matching output sequence lengths E _s for each of a plurality of PUCCH repetitions for one PUCCH to determine expected rate matching output sequence length E for one PUCCH.

For example, the division unit 1001 may perform encoding based on the length E of the rate matching output sequence expected for one PUCCH.

Furthermore, for example, dividing unit 1001 may select length E0 of the rate matching output sequence for the first PUCCH instance # ₀ from among S rate matching output sequences of length E _s for each of a plurality of PUCCH instances, and assume _E0 as the rate matching output sequence length E. For example, dividing unit 1001 may select length E1 of the rate matching output sequence for the second first PUCCH instance #1 from among S rate matching output sequences of length E _s for each of a plurality of PUCCH instances, and assume _E1 as the rate matching output sequence length E. For example, dividing unit 1001 may select length E _{S-1 of} the rate matching output sequence for the last PUCCH instance #S-1 from among S rate matching output sequences of length E s for each of a plurality of PUCCH instances, and assume E S _{- 1} as the rate matching output sequence length E.

For example, the length E of the rate matching output sequence assumed by the dividing unit 1001 may be determined based on RRC signaling. Furthermore, the length E of the rate matching output sequence assumed by the dividing unit 1001 may be indicated by RRC signaling. For example, the length E of the rate matching output sequence assumed by the dividing unit 1001 may be determined based on the DCI format used for scheduling the S PUCCH entities. For example, the length E of the rate matching output sequence assumed by the dividing unit 1001 may be indicated by the DCI format used for scheduling the S PUCCH entities.

For example, the dividing unit 1001 may select one value as a parameter used to determine the length E of the rate matching output sequence for each of the S PUCCH instances. For example, the dividing unit 1001 may select any one of the numbers of OFDM symbols included in each of the S PUCCH instances. The dividing unit 1001 may use the selected number to determine the length E of the rate matching output sequence. For example, the dividing unit 1001 may select the largest number of the numbers of OFDM symbols included in each of the S PUCCH instances and determine the length E of the rate matching output sequence. For example, the dividing unit 1001 may select the smallest number of the numbers of OFDM symbols included in each of the S PUCCH instances and determine the length E of the rate matching output sequence. For example, the dividing unit 1001 may determine the average value of the numbers of OFDM symbols included in each of the S PUCCH instances and determine the length E of the rate matching output sequence. For example, dividing section 1001 may determine the sum of the number of OFDM symbols included in each of the S PUCCH entities, and determine the length E of the rate matching output sequence. For example, dividing section 1001 may select the number N0 of OFDM symbols included in the first PUCCH entity # ₀ from the number _Ns of OFDM symbols included in each of the S PUCCH entities, and determine the length E of the rate matching output sequence using the selected _N0 . For example, dividing section 1001 may select the number _N1 of OFDM symbols included in the second first PUCCH entity #1 from the number of OFDM symbols included in each of the S PUCCH entities, and determine the length E of the rate matching output sequence using the selected _N1 . For example, dividing section 1001 may select the number N _S-1 of OFDM symbols included in the last PUCCH entity #S-1 from the number of OFDM symbols included in each of the S PUCCH entities, and may determine the length E of the rate matching output sequence using the selected N _S-1 . Here, N _S indicates the number of OFDM symbols included in PUCCH entity #s. Note that N _S may also indicate the number obtained by subtracting the number of OFDM symbols for DMRS included in PUCCH entity #s from the OFDM symbols included in PUCCH entity #s. Furthermore, N _S may also indicate the number of OFDM symbols included in PUCCH entity #s that convey UCI.

For example, the dividing unit 1001 may select one of the numbers of resource blocks included in each of the S PUCCH instances. The dividing unit 1001 may use the selected number to determine the length E of the rate matching output sequence. For example, the dividing unit 1001 may select the largest number of resource blocks included in each of the S PUCCH instances and use this largest number to determine the length E of the rate matching output sequence. For example, the dividing unit 1001 may select the smallest number of resource blocks included in each of the S PUCCH instances and use this smallest number to determine the length E of the rate matching output sequence. For example, the dividing unit 1001 may determine the average value of the number of resource blocks included in each of the S PUCCH instances and use this determined average value to determine the length E of the rate matching output sequence. For example, the dividing unit 1001 may determine the sum of the number of resource blocks included in each of the S PUCCH instances and use this determined sum to determine the length E of the rate matching output sequence. For example, the division unit 1001 may determine the rate matching output sequence E using the number _R0 of resource blocks included in the first PUCCH entity #0 out of the number Rs of resource blocks included in each of the S PUCCH entities. For example, the division unit 1001 may determine the length E of the rate matching output sequence using the number _R1 of resource blocks included in the second PUCCH entity #1 from the beginning out of the number _Rs of resource blocks included in each of the S PUCCH entities. For example, the division unit 1001 may determine the length E of the rate matching output sequence using the number _Rs - ₁ of resource blocks included in the last PUCCH entity #S- ₁ out of the number Rs of resource blocks included in each of the S PUCCH entities. Here, _Rs indicates the number of resource blocks included in PUCCH entity #s. Note that _Rs may also indicate the number of resource blocks transmitted in PUCCH entity #s.

For example, the dividing unit 1001 may select one PUCCH format from among the PUCCH formats included in each of the S PUCCH entities. The dividing unit 1001 may determine the length E of the rate matching output sequence using the setting of the selected one PUCCH format. For example, the dividing unit 1001 may determine the length E of the rate matching output sequence using the index _F0 of the PUCCH format included in the first PUCCH entity #0 from among the PUCCH formats _Fs included in each of the S PUCCH entities. For example, the dividing unit 1001 may determine the length E of the rate matching output sequence using the second PUCCH entity #1 from among the PUCCH formats _Fs included in each of the S PUCCH entities. For example, dividing section 1001 may determine the length E of the rate matching output sequence using the index F _{S -1} of the PUCCH format included in the last PUCCH entity #S-1 among the PUCCH formats F S included in each of the S PUCCH entities, where F _S indicates the index of the PUCCH format included in the s-th PUCCH entity.

The dividing unit 1001 may determine the number of code blocks for polar coding for the S PUCCH entities using the length E of the assumed rate matching output sequence. The dividing unit 1001 may determine the number of code blocks for polar coding for the S PUCCH entities using the length E of the selected rate matching output sequence. The dividing unit 1001 may determine the number of code blocks for polar coding for the S PUCCH entities using the determined length E of the rate matching output sequence. Here, a bit sequence c of uplink control information to be transmitted in the S PUCCH entities may be generated based on the determined number of code blocks.

For example, the dividing unit 1001 and the rate matching unit 1003 may determine the length E of the rate matching output sequence using different methods. For example, the dividing unit 1001 may determine the length E ¹⁰⁰¹ of a first rate matching output sequence. Here, the length E ¹⁰⁰¹ of the first rate matching output sequence may be commonly used for each of the S PUCCH instances. On the other hand, the rate matching unit 1003 may determine the length E ¹⁰⁰³ of a second rate matching output sequence. Here, the length E ¹⁰⁰³ of the second rate matching output sequence may be determined for each of the S PUCCH instances.

The dividing unit 1001 may determine the number of code blocks C _UCI for the S PUCCH instances using the assumed rate matching output sequence length E. The dividing unit 1001 may determine the number of code blocks C _UCI for the S PUCCH instances using the selected rate matching output sequence length E. The dividing unit 1001 may determine the number of code blocks C _UCI for the S PUCCH instances using the determined rate matching output sequence length E.

For example, the encoder 1002 may select the maximum value of E _s and assume the selected maximum value as the length E of the rate matching output sequence. Alternatively, the encoder 1002 may determine the average value of E _s and assume the determined average value as the length E of the rate matching output sequence. Alternatively, the encoder 1002 may select the minimum value of E _s and assume the selected minimum value as the length E of the rate matching output sequence. Alternatively, the encoder 1002 may determine the sum of E _s and assume the determined sum as the length E of the rate matching output sequence. That is, for example, the encoder 1002 may determine the expected length E of the rate matching output sequence based at least on each of the lengths E _s of the rate matching output sequence. Alternatively, for example, the encoder 1002 may determine the expected length E of the rate matching output sequence using at least two or more of the lengths E _s of the S rate matching output sequences. For example, the encoder 1002 may perform encoding based on the expected length E of the rate matching output sequence.

For example, the encoder 1002 may select the maximum value of E _s for each of a plurality of PUCCH instances and assume the selected maximum value as the rate matching output sequence length E. The encoder 1002 may select the maximum value of E _s for each of a plurality of PUCCH repetitions for one PUCCH and assume the selected maximum value as the rate matching output sequence length E.

Alternatively, the encoder 1002 may determine an average value of E _s for each of a plurality of PUCCH instances and assume the determined average value as the length E of the rate-matching output sequence. The encoder 1002 may determine an average value of E _s for each of a plurality of PUCCH repetitions for one PUCCH and assume the determined average value as the length E of the rate-matching output sequence.

Alternatively, the encoder 1002 may select the minimum value of E _s for each of a plurality of PUCCH instances and assume the selected minimum value as the length E of the rate matching output sequence. The encoder 1002 may select the minimum value of E _s for each of a plurality of PUCCH repetitions for one PUCCH and assume the selected minimum value as the length E of the rate matching output sequence.

Alternatively, the encoder 1002 may determine the sum of _Es for each of a plurality of PUCCH instances and assume the determined sum as the length E of the rate-matching output sequence. The encoder 1002 may determine the sum of _Es for each of a plurality of PUCCH repetitions for one PUCCH and assume the determined sum as the length E of the rate-matching output sequence.

That is, for example, the encoder 1002 may determine the expected rate matching output sequence length E based on at least each of the rate matching output sequence lengths E _s for each of the multiple PUCCH instances. The encoder 1002 may determine the expected rate matching output sequence length E for one PUCCH based on at least each of the rate matching output sequence lengths E _s for each of the multiple PUCCH repetitions for one PUCCH.

Furthermore, for example, the encoding unit 1002 may use at least two or more of the S rate matching output sequence lengths E _s for each of a plurality of PUCCH entities to determine the expected rate matching output sequence length E. The encoding unit 1002 may use at least two or more of the S rate matching output sequence lengths E _s for each of a plurality of PUCCH repetitions for one PUCCH to determine the expected rate matching output sequence length E for one PUCCH.

For example, the encoding unit 1002 may perform encoding based on the length E of the rate matching output sequence expected for one PUCCH.

Furthermore, for example, the encoder 1002 may select a rate matching output sequence length E0 for the first PUCCH instance #0 from among _S rate matching output sequences of length Es for each of the multiple PUCCH instances, and assume that _{E0 is} the rate matching output sequence length E. For example, the encoder 1002 may select a rate matching output sequence length E1 for the second first PUCCH instance #1 from among _S rate matching output sequences of length Es for each of the multiple PUCCH instances, and assume that _{E1 is} the rate matching output sequence length E. For example, the encoder 1002 may select a rate matching output sequence length E _S -1 for the last PUCCH instance #S-1 from among S rate matching output sequences of length Es for each of the multiple PUCCH instances, and assume that E _{S -1} is the rate matching output sequence length E.

For example, the length E of the rate matching output sequence assumed by the encoding unit 1002 may be determined based on RRC signaling. Furthermore, the length E of the rate matching output sequence assumed by the encoding unit 1002 may be indicated by RRC signaling. For example, the length E of the rate matching output sequence assumed by the encoding unit 1002 may be determined based on the DCI format used for scheduling the S PUCCH entities. For example, the length E of the rate matching output sequence assumed by the encoding unit 1002 may be indicated by the DCI format used for scheduling the S PUCCH entities.

For example, the encoder 1002 may select one value as a parameter used to determine the length E of the rate matching output sequence for each of the S PUCCH instances. For example, the encoder 1002 may select any one of the numbers of OFDM symbols included in each of the S PUCCH instances. The encoder 1002 may use the selected number to determine the length E of the rate matching output sequence. For example, the encoder 1002 may select the largest number of the numbers of OFDM symbols included in each of the S PUCCH instances and determine the length E of the rate matching output sequence. For example, the encoder 1002 may select the smallest number of the numbers of OFDM symbols included in each of the S PUCCH instances and determine the length E of the rate matching output sequence. For example, the encoder 1002 may determine the average value of the numbers of OFDM symbols included in each of the S PUCCH instances and determine the length E of the rate matching output sequence. For example, the encoder 1002 may determine the sum of the number of OFDM symbols included in each of the S PUCCH entities, and determine the length E of the rate matching output sequence. For example, the encoder 1002 may select the number _N0 of OFDM symbols included in the first PUCCH entity #0 from the number _Ns of OFDM symbols included in each of the S PUCCH entities, and determine the length E of the rate matching output sequence using the selected _N0 . For example, the encoder 1002 may select the number _N1 of OFDM symbols included in the second first PUCCH entity #1 from the number of OFDM symbols included in each of the S PUCCH entities, and determine the length E of the rate matching output sequence using the selected _N1 . For example, the encoding unit 1002 may select the number N _S-1 of OFDM symbols included in the last PUCCH entity #S-1 from the number of OFDM symbols included in each of the S PUCCH entities, and determine the length E of the rate matching output sequence using the selected N _S-1 .

For example, the encoder 1002 may select one of the numbers of resource blocks included in each of the S PUCCH instances. The encoder 1002 may use the selected number to determine the length E of the rate matching output sequence. For example, the encoder 1002 may select the largest number of resource blocks included in each of the S PUCCH instances and use this largest number to determine the length E of the rate matching output sequence. For example, the encoder 1002 may select the smallest number of resource blocks included in each of the S PUCCH instances and use this smallest number to determine the length E of the rate matching output sequence. For example, the encoder 1002 may determine the average value of the number of resource blocks included in each of the S PUCCH instances and use this determined average value to determine the length E of the rate matching output sequence. For example, the encoder 1002 may determine the sum of the number of resource blocks included in each of the S PUCCH instances and use this determined sum to determine the length E of the rate matching output sequence. For example, the encoder 1002 may determine the rate matching output sequence E using the number _R0 of resource blocks included in the first PUCCH entity #0 out of the number Rs of resource blocks included in each of the S PUCCH entities. For example, the encoder 1002 may determine the length E of the rate matching output sequence using the number _R1 of resource _blocks included in the second first PUCCH entity # ₁ out of the number Rs of resource blocks included in each of the S PUCCH entities. For example, the encoder 1002 may determine the length E of the rate matching output sequence using the number Rs- ₁ of resource blocks included in the last PUCCH entity #S _- 1 out of the number Rs of resource blocks included in each of the S PUCCH entities.

For example, the encoder 1002 may select one PUCCH format from among the PUCCH formats included in each of the S PUCCH entities. The encoder 1002 may determine the length E of the rate-matching output sequence using the setting of the selected one PUCCH format. For example, the encoder 1002 may determine the length E of the rate-matching output sequence using the index _F0 of the PUCCH format included in the first PUCCH entity #0 from among the PUCCH formats _Fs included in each of the S PUCCH entities. For example, the encoder 1002 may determine the length E of the rate-matching output sequence using the second PUCCH entity #1 from among the PUCCH formats _Fs included in each of the S PUCCH entities. For example, the encoding unit 1002 may determine the length E of the rate matching output sequence using the index F _{S -1} of the PUCCH format included in the last PUCCH entity #S-1 among the PUCCH formats F S included in each of the S PUCCH entities, where F _S indicates the index of the PUCCH format included in the s-th PUCCH entity.

The encoder 1002 may determine a sequence to be used for polar coding for the S PUCCH entities using the length E of the assumed rate matching output sequence. The encoder 1002 may determine a sequence to be used for polar coding for the S PUCCH entities using the length E of the selected rate matching output sequence. The encoder 1002 may determine a sequence to be used for polar coding for the S PUCCH entities using the determined length E of the rate matching output sequence. Here, the bit sequence c of the uplink control information to be transmitted in the S PUCCH entities may be coded using the determined sequence.

For example, the encoder 1002 and the rate matching unit 1003 may determine the length E of the rate matching output sequence using different methods. For example, the encoder 1002 may determine the length E ¹⁰⁰² of a third rate matching output sequence. Here, the length E ¹⁰⁰² of the third rate matching output sequence may be used in common for each of the S PUCCH instances. On the other hand, the rate matching unit 1003 may determine the length E ¹⁰⁰³ of a second rate matching output sequence. Here, the length E ¹⁰⁰³ of the second rate matching output sequence may be determined for each of the S PUCCH instances.

In a polar code, a coded bit sequence y may be generated by applying a first interleaver to a coded bit sequence d. The coded bit sequence y includes y ₀ , y ₁ , ..., y _N-1 , where y _k (k is an integer from 0 to N-1) indicates the k-th coded bit of the coded bit sequence y. When the first interleaver is not applied to the coded bit sequence d, the coded bit sequence d may be input to the coded bit sequence y.

The first interleaver may be implemented by inputting coded bits d _J(k) to coded bits y _k , where J(k) is a function for the first interleaver. J(k)=k may mean that the first interleaver is not applied.

In a polar code, bit selection may be applied to a coded bit sequence y to generate a coded bit sequence e. The coded bit sequence e includes e ₀ , e ₁ , ..., e _E-1 , where e _k (k is an integer from 0 to E-1) denotes the k-th coded bit of the coded bit sequence e.

In polar codes, when E is greater than or equal to N, a first method of bit selection may be applied. In the first method of bit selection, y _mod(k,N) is input to coded bit e _k . In the first method of bit selection, the domain of k is an integer from 0 to E-1. The first method of bit selection is also called repetition.

In polar codes, if E is not greater than or equal to N and K/E is less than or equal to 7/16, a second method of bit selection may be applied. In the second method of bit selection, y _k+N-E is input to coded bit e _k . In the second method of bit selection, the domain of k is an integer from 0 to E-1. The second method of bit selection is also called puncture.

In polar codes, if E is not greater than or equal to N and K/E is not less than or equal to 7/16, a third method of bit selection may be applied. In the third method of bit selection, coded bit y _k is input to coded bit e _k . In the third method of bit selection, the domain of k is an integer from 0 to E-1. The third method of bit selection is also called shortening.

That is, for example, in a polar code, the method of bit selection may be determined based at least on some or all of K, E, and N.

In a polar code, an interleaver may be applied to the coded bit sequence e to generate the coded bit sequence f. If an interleaver is not applied to the coded bit sequence e, the coded bit sequence e may be input to the coded bit sequence f.

In the Reed-Muller code, an interleaver may not be applied to the coded bit sequence d, i.e., coded bits d _k may be input to coded bits y _k .

In the Reed-Muller code, a first method of bit selection may be applied, that is, y _mod(k,N) is input to the coding bit f _k by the first method of bit selection.

The combination unit 1004 may combine the coded bits f _k for each of the C _UCI code blocks to generate coded bits g _k . If the division unit 1001 does not divide the bit sequence into multiple code blocks, the coded bits f _k may be input to the coded bits g _k .

In multiplexing section 1005, multiplexing of a plurality of UCIs is performed, and a coded bit sequence h is generated. The coded bit sequence h includes h ₀ , h ₁ , ..., h _Etot-1 . Here, h _k (k is an integer from 0 to E _tot -1) indicates the k-th coded bit of the coded bit sequence h. For example, when a first CSI part and a second CSI part are transmitted on the PUCCH, the coded bit sequence g for the first CSI part and the coded bit sequence g for the second CSI part are multiplexed, and coded bit sequence h is generated. When multiplexing of a plurality of UCIs is not performed in multiplexing section 1005, the coded bit sequence h is the coded bit sequence g.

The coded bit sequence h may be transmitted on the PUCCH. The coded bit sequence h may be mapped to the PUCCH. The coded bit sequence h may be included in the PUCCH. The coded bit sequence h may be transmitted on the PUSCH. The coded bit sequence h may be mapped to the PUSCH. The coded bit sequence h may be included in the PUSCH.

The coded bit sequence h mapped to the PUCCH may be scrambled. The scrambled sequence may be modulated. The coded bit sequence h mapped to the PUSCH may be scrambled. The scrambled sequence may be modulated.

In the PUCCH repetition shown in FIG. 9, a sequence-based PUCCH may be used. The sequence-based PUCCH may be a sequence-based PUCCH format. The sequence-based PUCCH may be a PUCCH that does not include DMRS.

A sequence-based PUCCH is a PUCCH equipped with a means for transmitting information by linking information to each sequence included in a predetermined set of sequences. For example, if the predetermined set of sequences includes a first sequence linked to '00', a second sequence linked to '01', a third sequence linked to '10', and a fourth sequence linked to '11', and terminal device 1 wishes to notify base station device 3 of '01', it may select the second sequence and transmit it on the PUCCH.

For example, in the sequence-based PUCCH, polar coding may not be applied even when condition 1101 is satisfied. Also, in the sequence-based PUCCH, polar coding may be applied even when condition 1101 is satisfied. For example, in the sequence-based PUCCH, Reed-Muller coding may not be applied even when condition 1101 is not satisfied and A is 3 or greater. Also, in the sequence-based PUCCH, Reed-Muller coding may be applied even when condition 1101 is not satisfied and A is 3 or greater. For example, in the sequence-based PUCCH, repetition coding may not be applied even when condition 1101 is not satisfied and A is 2 or less. Also, in the sequence-based PUCCH, repetition coding may be applied even when condition 1101 is not satisfied and A is 2 or less.

13 is a diagram illustrating an example of mapping of uplink control information for sequence-based PUCCH according to one aspect of this embodiment. As shown in FIG. 13, one UCI block may be mapped to each of the OFDM symbols included in each of PUCCH entity 9001 and PUCCH entity 9002. A UCI block is a set of uplink control information bits or a set of coded bits _hk mapped to one OFDM symbol.

For example, a modulation symbol generated from a set of bits included in a UCI block may be mapped to one OFDM symbol. Also, a sequence selected by a set of bits included in a UCI block may be mapped to one OFDM symbol.

For example, UCI blocks may be obtained by dividing a coded bit sequence h. For example, a coded bit sequence h of E _tot bits may be divided into N _block = ceil(E _tot /N ^block _bit ) UCI blocks, where N ^block _bit may indicate the maximum number of bits included in one UCI block.

Fig. 13 shows an example of mapping of uplink control information when N _block is 3. As shown in Fig. 13, each of the N _blocks of UCI blocks is cyclically mapped to achieve suitable communication.

In Figure 13, mapping of UCI blocks for PUCCH entity 9001 starts from UCI block #0, and mapping of UCI blocks for PUCCH entity 9002 starts from UCI block #2. In this way, it is preferable that the UCI mapping method be adjusted for each PUCCH entity.

For example, mapping of UCI blocks to PUCCH entity 9001 may start from UCI block #0. Alternatively, mapping of UCI blocks to PUCCH entity 9001 may be the UCI block next to the UCI block mapped to the last OFDM symbol of PUCCH entity 9001. That is, if the number of OFDM symbols carrying UCI in PUCCH entity 9001 is N ₉₀₀₁ and UCI block #x is mapped to the first OFDM symbol of the OFDM symbols carrying UCI in PUCCH entity 9001, UCI block #(x+N ₉₀₀₁ ) may be mapped to the first OFDM symbol of the OFDM symbols carrying UCI in PUCCH entity 9002.

That is, the terminal device 1 may determine, based at least on N ₉₀₀₁ , mapping of UCI blocks to the PUCCH entity 9002. Furthermore, the base station device 3 may receive the PUCCH entity 9002 for which mapping of UCI blocks has been determined based on N ₉₀₀₁ .

For example, the mapping of UCI blocks to PUCCH entities 9002 may be related to the index of an OFDM symbol in a radio frame. For example, if the index in a radio frame of an OFDM symbol carrying UCI in PUCCH 9002 is l ^rf _symb , then UCI block # (mod(l ^rf _symb , N _block )) may be mapped to that OFDM symbol.

In other words, the terminal device 1 may map the UCI block based at least on the index within the radio frame of the OFDM symbol that conveys the UCI. Here, the index of the OFDM symbol used for mapping the UCI block may be set in a time domain other than the radio frame. For example, an index within a subframe may be used for mapping the UCI block. Alternatively, an index within a half radio frame may be used for mapping the UCI block. Alternatively, indices within two consecutive radio frames may be used for mapping the UCI block.

For example, the first OFDM symbol among the OFDM symbols that convey UCI in PUCCH entity 9001 may be set by RRC signaling, and the first OFDM symbol among the OFDM symbols that convey UCI in PUCCH entity 9002 may be set by RRC signaling.

For example, the terminal device 1 may apply a cyclic shift of a predetermined amount C to the coded bit sequence h. Here, by applying the cyclic shift of the predetermined amount C, a coded bit sequence j may be generated. The coded bit sequence j includes j ₀ , j ₁ , ..., j _Etot-1 . Here, j _k (k is an integer from 0 to E _tot -1) indicates the k-th coded bit of the coded bit sequence j. By applying the cyclic shift of the predetermined amount C, h _{mod(k+C, Etot)} may be input to coded bit j _k . For example, the coded bit sequence j after applying the cyclic shift of the predetermined amount C may be mapped to the PUCCH.

For example, the predetermined amount C may be determined for each PUCCH entity. Here, the predetermined amount C determined for PUCCH entity #s among the S PUCCH entities is referred to as predetermined amount _Cs . For example, the predetermined amount _Cs for PUCCH entity #s may be determined based on at _least some or all of the predetermined amount Cs-1 for PUCCH entity #s _-1 , ^Nblockbit , and the number Ns _-1 of OFDM symbols included in PUCCH entity #s-1.

That is, a different predetermined quantity _Cs may be determined for each of the S PUCCH instances.

For example, the predetermined quantity C _s for PUCCH entity #s may be determined based at least on C _s-1 +N _s-1 *N ^block _bits . For example, the predetermined quantity C _s for PUCCH entity #s may be set to C _s-1 +N _s-1 *N ^block _bits +O _s , where O _s indicates an offset value for PUCCH entity #s. For example, O _s may be 0. For example, O _s may be an offset value set for each PUCCH entity.

For example, the predetermined quantity C _s for PUCCH entity #s may be determined based at least on an OFDM symbol index l ^frame _sym within a radio frame. For example, the predetermined quantity C _s for PUCCH entity #s may be determined based at least on l ^frame _sym * N ^block _bit . For example, the predetermined quantity C _s for PUCCH entity #s may be set to l ^frame _sym * N ^block _bit + O _s . Alternatively, an OFDM symbol index l _sym within a slot may be used instead of an OFDM symbol index within a radio frame. Alternatively, an OFDM symbol index l ^subframe _sym within a subframe may be used instead of an OFDM symbol index within a radio frame. Alternatively, instead of the index of the OFDM symbol in the radio frame, an OFDM symbol index l ^hlf _sym in a half radio frame may be used, or instead of the index of the OFDM symbol in the radio frame, an index set in the S PUCCH entities may be used.

The index set within the S PUCCH entities may be the OFDM symbol index of the OFDM symbols included in the S PUCCH entities. For example, if the first OFDM symbol of 9001 has index 0, the index of the last OFDM symbol of 9001 may be 1. The index of the first OFDM symbol of 9002 may be 2. The index of the last OFDM symbol of 9002 may be 15. That is, for example, the index of the first OFDM symbol of PUCCH entity #s may be determined based at least on the sum of the number of OFDM symbols of PUCCH entities #0 to #s-1. The index of the first OFDM symbol of PUCCH entity #s may be equal to the sum of the number of OFDM symbols of PUCCH entities #0 to #s-1.

For example, a predetermined quantity C _s for PUCCH entity #s may be set to O _s . For example, O _s may be determined based at least on a higher layer parameter. Alternatively, O _s may be indicated by a higher layer parameter. Alternatively, O _s may be determined for each of S PUCCH entities based at least on a higher layer parameter. Alternatively, O _s may be indicated for each of S PUCCH entities by a higher layer parameter.

For example, the predetermined amount C _s may be applied to bit sequence a. Also, the predetermined amount C _s may be applied to bit sequence c. Also, the predetermined amount C _s may be applied to coded bit sequence d. Also, the predetermined amount C _s may be applied to coded bit sequence y. Also, the predetermined amount C _s may be applied to coded bit sequence e. Also, the predetermined amount C _s may be applied to coded bit sequence f. Also, the predetermined amount C _s may be applied to coded bit sequence g. Also, the predetermined amount C _s may be applied to a modulated symbol sequence after modulating the coded bit sequence.

The following describes various aspects of the device relating to one aspect of this embodiment.

(1) In order to achieve the above object, the present invention provides the following measures. That is, a first aspect of the present invention is a terminal device comprising: a segmentation unit that segments a bit sequence of uplink control information into one or more code blocks; a coding unit that applies an error correction code to each of the one or more code blocks to generate one or more coded bit sequences; a rate matching unit that applies bit selection for an s-th PUCCH entity based at least on a length E _s of a rate matching output sequence for the s-th PUCCH entity among S PUCCH entities to generate a coded bit sequence for the s-th PUCCH entity; and a transmission unit that transmits the coded bit sequence for the s-th PUCCH entity by the s-th PUCCH entity _, 2) the length E _S-1 of the rate matching output sequence for the S-1th PUCCH instance among the S PUCCH instances, 3) the maximum value of the length of the rate matching output sequence for each of the S PUCCH instances, 4) the minimum value of the length of the rate matching output sequence for each of the S PUCCH instances, and 5) the sum of the lengths of the rate matching output sequences for each of the S PUCCH instances.

(2) Also, a second aspect of the present invention is a terminal device comprising: a dividing unit that divides a bit sequence of uplink control information into one or more code blocks; a coding unit that applies an error correction code to each of the one or more code blocks to generate one or more coded bit sequences; a rate matching unit that applies bit selection for an s-th PUCCH entity based at least on a length E _s of a rate matching output sequence for the s-th PUCCH entity among S PUCCH entities to generate a coded bit sequence for the s-th PUCCH entity; and a transmitting unit that transmits the coded bit sequence for the s-th PUCCH entity by the s-th PUCCH entity, wherein the coding unit determines a sequence used in applying the error correction code based at least on a reference value related to a length of the rate matching output sequence, and the reference value _is 2) the length E _S-1 of the rate matching output sequence for the S-1th PUCCH instance among the S PUCCH instances, 3) the maximum value of the length of the rate matching output sequence for each of the S PUCCH instances, 4) the minimum value of the length of the rate matching output sequence for each of the S PUCCH instances, and 5) the sum of the lengths of the rate matching output sequences for each of the S PUCCH instances.

(3) A third aspect of the present invention is a base station apparatus including an antenna unit and a baseband unit, wherein a bit sequence of uplink control information is divided into one or more code blocks, an error correction code is applied to each of the one or more code blocks to generate one or more coded bit sequences, bit selection for the s-th PUCCH entity is applied based at least on a length E _s of a rate matching output sequence for the s-th PUCCH entity among S PUCCH entities to generate a coded bit sequence for the s-th PUCCH entity, the coded bit sequence for the s-th PUCCH entity is transmitted in the s-th PUCCH entity, and whether to divide the bit sequence of the uplink control information into the plurality of code blocks is determined based at least on a reference value related to a length of a rate matching output sequence, and the reference value _is 2) the length E _S-1 of the rate matching output sequence for the S-1th PUCCH instance among the S PUCCH instances, 3) the maximum value of the length of the rate matching output sequence for each of the S PUCCH instances, 4) the minimum value of the length of the rate matching output sequence for each of the S PUCCH instances, and 5) the sum of the lengths of the rate matching output sequences for each of the S PUCCH instances, and the sth PUCCH instance is received.

(4) A fourth aspect of the present invention is a base station apparatus including an antenna unit and a baseband unit, wherein a bit sequence of uplink control information is divided into one or more code blocks, an error correction code is applied to each of the one or more code blocks to generate one or more coded bit sequences, bit selection for the s-th PUCCH entity is applied based at least on a length E _s of a rate matching output sequence for the s-th PUCCH entity among S PUCCH entities to generate the coded bit sequence for the s-th PUCCH entity, the coded bit sequence for the s-th PUCCH entity is transmitted in the s-th PUCCH entity, and a sequence used for applying the error correction code is determined based at least on a reference value related to a length of the rate matching output sequence, the reference value _being 2) the length E _S-1 of the rate matching output sequence for the S-1th PUCCH instance among the S PUCCH instances, 3) the maximum value of the length of the rate matching output sequence for each of the S PUCCH instances, 4) the minimum value of the length of the rate matching output sequence for each of the S PUCCH instances, and 5) the sum of the lengths of the rate matching output sequences for each of the S PUCCH instances, and the sth PUCCH instance is received.

(5) Also, a fifth aspect of the present invention is a terminal device comprising: a coding unit that generates a first coded bit sequence by error correction coding of a bit sequence of uplink control information; a rate matching unit that generates a second coded bit sequence by applying a cyclic shift of a predetermined amount C _s to the first coded bit sequence for an s-th PUCCH entity among S PUCCH entities; and a transmitting unit that transmits the second coded bit sequence by the s-th PUCCH entity, wherein the predetermined amount C _s is determined based on at least a part or all of a predetermined amount C _s-1 for the s-1-th PUCCH entity, the number of OFDM symbols included in the s-1-th PUCCH entity, and a number N ^block _bit of coded bits mapped per OFDM symbol.

(6) Furthermore, a sixth aspect of the present invention is a terminal device comprising: a coding unit that generates a first coded bit sequence by error correction coding of a bit sequence of uplink control information; a rate matching unit that generates a second coded bit sequence for an s-th PUCCH entity among S PUCCH entities by applying a cyclic shift of a predetermined amount _Cs to the first coded bit sequence; and a transmitting unit that transmits the second coded bit sequence by the s-th PUCCH entity, wherein the predetermined amount _Cs is determined based on at least one of an index of an OFDM symbol in a radio frame or an index of an OFDM symbol included in the S PUCCH entities.

(7) Furthermore, a seventh aspect of the present invention is a terminal device, comprising: a coding unit that generates a first coded bit sequence by error correction coding of a bit sequence of uplink control information; a rate matching unit that generates a second coded bit sequence by applying a cyclic shift of a predetermined amount _Cs to the first coded bit sequence for an s-th PUCCH entity of S PUCCH entities; and a transmitting unit that transmits the second coded bit sequence with the s-th PUCCH entity, wherein the predetermined amount _Cs is indicated by a parameter of a higher layer.

(8) Also, an eighth aspect of the present invention is a base station apparatus including an antenna unit and a baseband unit, wherein a first coded bit sequence is generated by error correction coding of a bit sequence of uplink control information, and a second coded bit sequence is generated for an s-th PUCCH entity among S PUCCH entities by applying a cyclic shift of a predetermined amount _Cs to the first coded bit sequence, and the second coded bit sequence is transmitted by the s-th PUCCH entity, wherein the predetermined amount _Cs is determined based on at least a part or all of a predetermined amount Cs _-1 for the s-1-th PUCCH entity, the number of OFDM symbols included in the s-1-th PUCCH entity, and a number N ^block _bit of coded bits mapped per OFDM symbol, and the base station apparatus receives the s-th PUCCH entity.

(9) Also, a ninth aspect of the present invention is a base station apparatus including an antenna unit and a baseband unit, wherein a first coded bit sequence is generated by error correction coding of a bit sequence of uplink control information, a cyclic shift of a predetermined amount _Cs is applied to the first coded bit sequence for an s-th PUCCH entity among S PUCCH entities to generate a second coded bit sequence, the second coded bit sequence is transmitted by the s-th PUCCH entity, the predetermined amount _Cs is determined based on at least one of an index of an OFDM symbol in a radio frame or an index of an OFDM symbol included in the S PUCCH entities, and the base station apparatus receives the s-th PUCCH entity.

(10) Also, a tenth aspect of the present invention is a base station apparatus including an antenna unit and a baseband unit, wherein a first coded bit sequence is generated by error correction coding of a bit sequence of uplink control information, a cyclic shift of a predetermined amount _Cs is applied to the first coded bit sequence for an s-th PUCCH entity among S PUCCH entities to generate a second coded bit sequence, the second coded bit sequence is transmitted in the s-th PUCCH entity, the predetermined amount _Cs is indicated by a parameter of a higher layer, and the s-th PUCCH entity is received.

The programs running on the base station device 3 and terminal device 1 relating to one aspect of the present invention may be programs (programs that cause a computer to function) that control a CPU (Central Processing Unit) or the like so as to realize the functions of the above-described embodiment relating to one aspect of the present invention. Information handled by these devices is temporarily stored in RAM (Random Access Memory) during processing, and then stored in various ROMs such as Flash ROM (Read Only Memory) or HDD (Hard Disk Drive), and is read, modified, and written by the CPU as needed.

In addition, a portion of the terminal device 1 and base station device 3 in the above-described embodiment may be implemented by a computer. In this case, the program for implementing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be read into a computer system and executed to implement the function.

Note that the term "computer system" here refers to a computer system built into the terminal device 1 or base station device 3, and includes hardware such as the OS and peripheral devices. Furthermore, "computer-readable recording media" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices such as hard disks built into the computer system.

Furthermore, "computer-readable recording medium" may include a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line, or a medium that stores a program for a fixed period of time, such as volatile memory within a computer system that serves as a server or client in such cases. Furthermore, the above program may be one that realizes part of the functions described above, or may be one that can realize the functions described above in combination with a program already stored in the computer system.

Furthermore, the base station device 3 in the above-described embodiment can also be realized as a collection (device group) consisting of multiple devices. Each of the devices constituting the device group may have some or all of the functions or functional blocks of the base station device 3 related to the above-described embodiment. It is sufficient for the device group to have all of the functions or functional blocks of the base station device 3. Furthermore, the terminal device 1 related to the above-described embodiment can also communicate with the base station device as a collection.

Furthermore, the base station device 3 in the above-described embodiments may be an EUTRAN (Evolved Universal Terrestrial Radio Access Network) and/or an NG-RAN (NextGen RAN, NR RAN).Furthermore, the base station device 3 in the above-described embodiments may have some or all of the functions of an upper node for an eNodeB and/or a gNB.

Furthermore, some or all of the terminal device 1 and base station device 3 in the above-described embodiments may be realized as an LSI, which is typically an integrated circuit, or as a chipset. Each functional block of the terminal device 1 and base station device 3 may be individually formed into a chip, or some or all may be integrated into a chip. Furthermore, the integrated circuit method is not limited to LSI, and may be realized using a dedicated circuit or a general-purpose processor. Furthermore, if an integrated circuit technology that can replace LSI emerges due to advances in semiconductor technology, it may also be possible to use an integrated circuit based on that technology.

In addition, in the above-mentioned embodiment, a terminal device is described as an example of a communication device, but the present invention is not limited to this and can also be applied to terminal devices or communication devices such as stationary or non-mobile electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment and includes design modifications within the scope of the invention. Furthermore, various modifications of one aspect of the present invention are possible within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included within the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are substituted for elements that achieve the same effect are also included.

One aspect of the present invention can be used, for example, in communication systems, communication equipment (e.g., mobile phone devices, base station devices, wireless LAN devices, or sensor devices), integrated circuits (e.g., communication chips), or programs.

1 (1A, 1B, 1C) Terminal device 3 Base station device 10, 30 Radio transceiver unit 10a, 30a Radio transmitter unit 10aa Channel coding/scrambling/modulation unit 10ab Layer mapping unit 10ac Precoding unit 10ad Time signal generation unit 10ae Spatial filter unit 10af Antenna unit 10b, 30b Radio receiver unit 10ba Channel decoding/descrambling/demodulation unit 10bb Layer demapping unit 10bc Channel demodulation unit 10bd Frequency signal generation unit 10be Spatial filter unit 10bf Antenna unit 11, 31 Antenna unit 12, 32 RF unit 13, 33 Baseband unit 14, 34 Upper layer processing unit 15, 35 Medium access control layer processing unit 16, 36 Radio resource control layer processing unit 91, 92, 93, 94 Search area set 300 Component carrier 301 Primary cells 302, 303 Secondary cell 1600 Spatial filter set 1700 Codebook set 3000 Points 3001, 3002 Resource grid 3003, 3004 BWP
3011, 3012, 3013, 3014 Offsets 3100, 3200 Common resource block sets 9001, 9002 PUSCH entity 1001 Dividing unit 1002 Encoding unit 1003 Rate matching unit 1004 Combining unit 1005 Multiplexing units 1101, 1102 Conditions

Claims (2)

an encoding unit that generates a first coded bit sequence d by encoding a bit sequence, and generates a second coded bit sequence by applying a cyclic shift of a predetermined amount _Cs to the first coded bit sequence d for an s-th uplink channel entity among the S uplink channel entities;
a transmitter configured to transmit the S uplink channels each including the second coded bit sequence ;
Equipped with
The S is an integer of 2 or more,
The s is an integer of 0 or more and S-1 or less,
the encoding unit determines the predetermined amount C _s based on a predetermined amount C s _- 1 for an s-1th uplink channel entity among the S uplink channel entities, a number N _s-1 of OFDM symbols included in the s-1th uplink channel entity , and N ^block _bit indicating the number of UCI bits per OFDM symbol ;
Terminal device. A communication method used in a terminal device, comprising:
an encoding step of generating a first coded bit sequence d by encoding a bit sequence, and generating a second coded bit sequence by applying a cyclic shift of a predetermined amount _Cs to the first coded bit sequence d for an s-th uplink channel entity among the S uplink channel entities;
a transmitting step of transmitting the S uplink channels including the second coded bit sequence ;
and
The S is an integer of 2 or more,
The s is an integer of 0 or more and S-1 or less,
In the encoding step, the predetermined amount Cs is determined based on a predetermined amount _Cs-1 for an s-1th uplink channel entity among the S uplink channel entities, a number Ns _-1 of OFDM symbols included in the s-1th uplink channel entity , and Nblockbit indicating the number of UCI bits per OFDM ^symbol _.
Communication method.