JP7704589B2 - Terminal device, base station device, and communication method - Google Patents

Description

The present invention relates to a terminal device, a base station device, and a communication method.

A radio access method and a radio network for cellular mobile communication (hereinafter also referred to as "Long Term Evolution (LTE)" or "EUTRA: Evolved Universal Terrestrial Radio Access") are being studied in 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 areas covered by a base station device are arranged in a cell shape. A single base station device may manage multiple serving cells.

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

It is expected that the functional expansion of cellular mobile communications, such as NR, will be considered. For example, as shown in Non-Patent Document 2, a study on expanding the functionality of NR has begun.

"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

The present invention provides a terminal device that communicates efficiently, a communication method used in the terminal device, a base station device that communicates efficiently, and a communication method used in the base station device.

(1) A first aspect of the present invention is a terminal device comprising: an encoding unit configured to generate an encoded bit sequence d by encoding a bit sequence of a certain code block among one or more code blocks included in a transport block of a first size; and a rate matching unit configured to apply a bit selection procedure to the encoded bit sequence d based on comparing a length N of the encoded bit sequence d with _Nref , wherein the _Nref is determined based on a second size;
The terminal device is characterized in that the first size is determined by applying a scaling technique using a value of K greater than 1 to a process of determining a transport block size, and the second size is determined under the assumption that the scaling technique is not applied to the process of determining the transport block size.

(2) A second aspect of the present invention is a base station apparatus including: a decoding unit that decodes a coded bit sequence d generated by coding a bit sequence of a certain code block among one or more code blocks included in a transport block of a first size; and a rate matching unit that applies a bit selection procedure to the coded bit sequence d based on comparing a length N of the coded bit sequence d with _Nref , wherein _Nref is determined based on a second size, the first size is determined by applying a scaling technique using a value of K greater than 1 to a process of determining a transport block size, and the second size is determined under an assumption that the scaling technique is not applied to the process of determining the transport block size.

(3) A third aspect of the present invention is a communication method used in a terminal device, comprising: generating a coded bit sequence d by coding a bit sequence of a certain code block among one or more code blocks included in a transport block of a first size; and applying a bit selection procedure to the coded bit sequence d based on comparing a length N of the coded bit sequence d with _Nref , wherein _Nref is determined based on a second size, the first size is determined by applying a scaling technique using a value of K greater than 1 to a process of determining a transport block size, and the second size is determined under the assumption that the scaling technique is not applied to the process of determining the transport block size.

(4) Furthermore, a fourth aspect of the present invention is a communication method used in a base station device, comprising: a step of decoding a coded bit sequence d generated by coding a bit sequence of a certain code block among one or more code blocks included in a transport block of a first size; and a step of applying a bit selection procedure to the coded bit sequence d based on comparing a length N of the coded bit sequence d with _Nref , wherein _Nref is determined based on a second size, the first size is determined by applying a scaling technique using a value of K greater than 1 to a process of determining a transport block size, and the second size is determined under the assumption that the scaling technique is not applied to the process of determining the transport block size.

According to this invention, the terminal device can communicate efficiently. Also, the base station device can communicate efficiently.

1 is a conceptual diagram of a wireless communication system according to an embodiment of the present invention. 1 is an example showing a relationship between a subcarrier spacing setting μ, the number of OFDM symbols per slot N ^slot _symb , and a cyclic prefix (CP) setting according to an aspect of the present embodiment. FIG. 2 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. 1 is a schematic block diagram showing 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 showing a configuration example 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. A diagram showing an example of a monitoring opportunity for a search area set according to one aspect of this embodiment. A diagram showing an example of the configuration of a media access control layer processing unit 15 according to one aspect of this embodiment. FIG. 12 is a diagram illustrating an example of the configuration of an encoding processor unit 12000 according to an aspect of this embodiment. FIG. 13 illustrates an example of a bit selection procedure according to an aspect of the present embodiment. FIG. 2 illustrates a concept of a circular buffer according to one aspect of the present embodiment. A figure showing an example of multi-slot transmission of a PUSH in one embodiment of the present invention. A figure showing an example of multi-slot transmission of a PUSH in one embodiment of the present invention.

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 not exceeding 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 not 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. Here, e is Napier's constant. H^I indicates H to the power I. 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. "・" indicates multiplication.

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

In the wireless communication system, at least one communication method may be used. The one communication method may be OFDM (Orthogonal Frequency Division Multiplex). For example, in the downlink, which is communication from the base station device 3 to the terminal device 1, at least CP-OFDM (Cyclic Prefix - Orthogonal Frequency Division Multiplex) may be used. In the uplink, which is communication from the terminal device 1 to the base station device 3, at least either CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform - spread - Orthogonal Frequency Division Multiplex) may be used. DFT-s-OFDM is a communication method in which transformed precoding is applied prior to signal generation in CP-OFDM. Here, transformed precoding is also called DFT precoding.

The base station device 3 may be configured to include one or more transmitting devices (or transmission points, transmitting/receiving devices, transmitting/receiving points). When the base station device 3 is configured by multiple transmitting devices, the multiple transmitting devices may be located at different geographical locations or may be located at the same geographical location. When multiple transmitting devices are located at the same geographical location, the multiple transmitting devices may be configured as a single device.

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 called a cell.

The serving cell may be configured to include one downlink component carrier and one uplink component carrier, or both. The serving cell may be configured to include two or more downlink component carriers and two or more uplink component carriers, or both. The downlink component carriers and the uplink component carriers are also collectively referred to as component carriers.

For example, one resource grid may be provided for each component carrier. Also, one resource grid may be provided for each set of one component carrier and a certain subcarrier spacing configuration μ. Here, the subcarrier spacing configuration μ is also referred to as numerology. For example, one resource grid may be provided for a set of a certain antenna port p, a certain subcarrier spacing configuration μ, and a certain transmission direction x.

The resource grid includes N ^size,μ _grid,x N ^RB _sc subcarriers, where the resource grid starts from a common resource block N ^{start,μ grid} _{, x} , which is also referred to as the reference point of the resource grid.

The resource grid contains N ^subframe,μ _symb OFDM symbols.

The subscript x, which is added to the resource grid related parameters, indicates the transmission direction. For example, the subscript x may be used to indicate either the downlink or the uplink.

N ^{size, μ} _{grid, x} is an offset setting indicated by a parameter provided by the RRC layer (e.g., the parameter CarrierBandwidth). ^{N start, μ} _{grid, x} is a band setting indicated by a parameter provided by the RRC layer (e.g., the parameter OffsetToCarrier). The offset setting and band setting are settings used to configure an SCS-specific carrier.

The SubCarrier Spacing (SCS) Δf for a given subcarrier spacing setting μ may be Δf= ^2μ ·15 kHz, where 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 CP (cyclic prefix) setting according to one aspect of the present 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} .
_t = 40, N ^{subframe, μ} _slot = 4.

The time unit _Tc is used to express the length of 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 = ( _ΔfmaxNf /100)· _Ts = 10 ms. A radio frame is made up of 10 subframes. The length of a subframe _Tsf = ( _{ΔfmaxNf /} 1000 ₎ · _Ts = 1 ms. The number of OFDM symbols per subframe is Nsubframe ^, _{μsymb =} ^{NslotsymbNsubframe} _, ^μslot .

An OFDM symbol is a unit of time domain for one communication method. For example, an OFDM symbol may be a unit of time domain for CP-OFDM. Also, an OFDM symbol may be a unit of time domain for DFT-s-OFDM.

A slot may be configured to include a plurality of OFDM symbols. For example, one slot may be configured by N ^slot _symb consecutive OFDM symbols. For example, in the normal CP setting, N ^slot _symb =14 may be used. Also, in the extended CP setting, N ^slot _symb =12 may be used.

The slots may be indexed in the time domain, for example, the slot index n ^μ _s may be given in ascending order as integer values ranging from 0 to N ^subframe,μ _slot −1 in a subframe, and the 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.

Fig. 3 is a diagram showing an example of a method for configuring a resource grid according to one aspect of the present embodiment. The horizontal axis in Fig. 3 indicates the frequency domain. Fig. 3 shows a configuration example of a resource grid with a subcarrier spacing setting _μ1 in a component carrier 300 and a configuration example of a resource grid with a subcarrier spacing setting _μ2 in the certain component carrier. In this way, one or more subcarrier spacings may be set for a certain component carrier.

A point 3000 is an identifier for identifying a certain subcarrier. The point 3000 is also called point A. 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 including point 3000 (the block indicated by the upward slanting line in FIG. 3 ) is also called the reference point of the common resource block set 3100. The reference point of the common resource block set 3100 is the common resource block with index 0 for the subcarrier spacing setting μ ₁ .

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 an 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. The reference point of BWP 3003 of index i1 is the physical resource block of index 0 for that BWP.

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

Of the common resource block set 3200, the common resource block including point 3000 (the block indicated by the upward slanting line in FIG. 3 ) is also called the reference point of the common resource block set 3200. The reference point of the common resource block set 3200 is the common resource block with index 0 for the subcarrier spacing setting _μ2 .

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.

The offset 3014 is the offset from the reference point of the resource grid 3002 to the reference point (N ^{start ,μ} _BWP,i2 ) of the BWP 3004 with index i2, which is the physical resource block with index 0 for that BWP.

Fig. 4 is a diagram showing a configuration example of a resource grid 3001 according to one aspect of the present embodiment. In the resource grid of Fig. 4, the horizontal axis is the OFDM symbol index _lsym , and the vertical axis is the subcarrier index _ksc . The resource grid 3001 includes ^{Nsize,μgrid1} _,xNRBsc ^subcarriers _and includes at least Nsubframe ^,μsymb _OFDM symbols. In the resource grid, a resource specified by the subcarrier index _ksc and the OFDM symbol index _lsym is also called a resource element (RE).

The frequency domain of the resource grid corresponds to the SCS specific carrier. The configuration of the SCS specific carrier includes an offset configuration and a part or all of a band configuration. The offset indicates an offset from a reference point of the common resource block set to a reference point of the resource grid. For example, offset 3011 and offset 3012 are offset configurations included in the configuration of the SCS specific carrier. In addition, the band configuration indicates the bandwidth of the SCS specific carrier. Here, the bandwidth of the SCS specific carrier corresponds to the bandwidth of the resource grid. For example, N ^size,μ _grid1,x and N ^size,μ _grid2,x are band configurations included in the configuration of the SCS specific carrier.

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). For example, N ^RB _sc may be 12.

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

In the physical resource block set for a certain subcarrier spacing setting μ, the physical resource blocks are indexed in the frequency domain in ascending order starting from 0. The physical resource block index n ^μ _PRB for a certain 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 may be configured as a portion of a frequency band of a component carrier. For example, a BWP may be defined as a subset of common resource blocks included in a resource grid. For example, a BWP may be configured to include N size ^,μ _BWP,i common resource blocks starting from a reference point N start ^,μ _BWP,i of the BWP. A BWP configured for a downlink is also called a downlink BWP. A BWP configured for an uplink is also called an uplink BWP.

An antenna port is 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, the channel may correspond to a physical channel. Also, the symbol may correspond to a modulation symbol that is mapped to a resource element.

Two antenna ports are considered to be in a Quasi Co-Located (QCL) relationship if the large scale properties of the channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at the other antenna port. Here, the large scale properties may include at least the long-range properties of the channel. The large scale properties may include at least some or all of the delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. The first antenna port and the second antenna port being QCL with respect to beam parameters may mean that the receiving beam assumed by the receiving side for the first antenna port and the receiving beam assumed by the receiving side for the second antenna port are the same (or correspond to each other). The first antenna port and the second antenna port being QCL with respect to the 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 (or correspond to each other). The terminal device 1 may assume that the two antenna ports are QCL if the large-scale characteristics of the channel through which symbols are transmitted at one antenna port can be estimated from the channel through which symbols are transmitted at the other 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 a plurality of aggregated serving cells. Also, carrier aggregation may be performing communication using a plurality of aggregated component carriers. Also, carrier aggregation may be performing communication using a plurality of aggregated downlink component carriers. Also, carrier aggregation may be performing communication using a plurality of aggregated uplink component carriers.

Figure 5 is a schematic block diagram showing an example of the 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 wireless transceiver unit (physical layer processing unit) 30 and/or part or all of a higher layer processing unit 34. The wireless 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 higher layer processing unit 34 includes at least a medium access control layer (MAC layer) processing unit 35, and part or all of a radio resource control (RRC) layer processing unit 36.

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

For example, the wireless transmitter 30a may generate a baseband signal of a downlink physical channel. For example, the wireless transmitter 30a may generate a baseband signal of a downlink physical signal.

For example, the wireless receiver 30b may attempt to detect information transmitted by an uplink physical channel. For example, the wireless receiver 30b may attempt to detect information transmitted by an uplink physical signal.

The upper layer processing unit 34 outputs downlink data (e.g., a transport block) to the radio transceiver unit 30 (or the radio transmitter unit 30a). The upper layer processing unit 34 performs some or all of the processing of the Medium Access Control (MAC) 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 (e.g., RRC parameters) of the terminal device 1. The radio resource control layer processing unit 36 sets parameters based on the RRC message received from the terminal device 1.

The wireless transceiver unit 30 (or the wireless transmitter unit 30a) performs some or all of the modulation process, the encoding process, and the transmission process. The wireless transceiver unit 30 (or the wireless transmitter unit 30a) generates a physical signal by performing some or all of the modulation process, the encoding process, and the baseband signal generation process (conversion to a time-continuous signal) on the downlink data. The wireless transceiver unit 30 (or the wireless transmitter unit 30a) may place the physical signal on a certain component carrier. The wireless transceiver unit 30 (or the wireless transmitter unit 30a) transmits the generated physical signal.

The wireless transceiver 30 (or the wireless receiver 30b) performs some or all of the demodulation, decoding, and reception processes. The wireless transceiver 30 (or the wireless receiver 30b) outputs information detected based at least on the demodulation and decoding processes performed on the received physical signal to the upper layer processor 34.

When carrier sensing is required in the band of the serving cell, the radio transceiver unit 30 (or the radio receiver unit 30b) may perform carrier sensing prior to transmitting a physical signal.

The RF unit 32 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 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 signal from which the CP has been removed to extract a signal in the frequency domain.

The baseband unit 33 performs an inverse fast Fourier transform (IFFT) on the downlink data, generates an OFDM symbol, adds a CP to the generated OFDM symbol, generates a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 33 outputs the converted analog signal to the RF unit 32. Prior to the inverse fast Fourier transform, modified precoding may be applied to the downlink data.

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 for controlling 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 any of a PCell (Primary cell), a PSCell (Primary SCG cell), and a SCell (Secondary Cell).

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

The PSCell is a serving cell included in a secondary cell group (SCG). The PSCell is a serving cell to which random access is performed by the terminal device 1.

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

The serving cell group (cell group) is a general term for the MCG, SCG, and PUCCH cell group. The serving cell group may include one or more serving cells (or component carriers). The one or more serving cells (or component carriers) included in the 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 an 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 an 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 attempt to 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 attempt to transmit the PUCCH and PUSCH in an active uplink BWP. The active downlink BWP and the active uplink BWP are collectively referred to as the active BWP.

The PDSCH, PDCCH, and CSI-RS may not be received in a downlink BWP that is not an active downlink BWP (inactive downlink BWP). The terminal device 1 may not attempt to receive the PDSCH, PDCCH, and CSI-RS in a downlink BWP that is not an active downlink BWP. The PUCCH and PUSCH may not be transmitted in an uplink BWP that is not an active uplink BWP (inactive uplink BWP). The terminal device 1 may not attempt to transmit the PUCCH and PUSCH in an uplink BWP that is not an active uplink BWP. The inactive downlink BWP and the inactive uplink BWP are collectively referred to as the inactive BWP.

Downlink BWP switch is a procedure for deactivating one active downlink BWP of a serving cell and activating one of the inactive downlink BWPs of the serving cell. Downlink BWP switch may be controlled by a BWP field included in downlink control information. Downlink BWP switch may be controlled based on higher layer parameters.

The uplink BWP switching is used to deactivate one active uplink BWP of a serving cell and activate one of the inactive uplink BWPs of the serving cell. The uplink BWP switching may be controlled by a BWP field included in the downlink control information. The uplink BWP switching may 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.

For each component carrier, one downlink BWP may be set as an active BWP. In other words, two or more downlink BWPs may not be set as active downlink BWPs for a given component carrier. Also, two or more uplink BWPs may not be set as active downlink BWPs for a given component carrier.

Figure 6 is a schematic block diagram showing an example of the 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 transmission/reception unit (physical layer processing unit) 10 and part or all of an upper layer processing unit 14. The radio transmission/reception unit 10 includes at least an antenna unit 11, an RF unit 12, and part 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 part or all of a radio resource control layer processing unit 16.

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

For example, the wireless transmission unit 10a may generate a baseband signal of an uplink physical channel. For example, the wireless transmission unit 10a may generate a baseband signal of an uplink physical signal.

For example, the wireless receiver 10b may attempt to detect information transmitted by a downlink physical channel. For example, the wireless receiver 10b may attempt to detect information transmitted by an uplink physical signal.

The upper layer processing unit 14 outputs uplink data (e.g., a transport block) to the radio transceiver unit 10 (or the radio transmitter unit 10a). The upper layer processing unit 14 performs some or all of the processing of the MAC layer, the packet data integration protocol layer, the radio link control layer, and the 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 included in the upper layer processing unit 14 performs processing of the RRC layer.
The radio resource control layer processing unit 16 manages various setting information/parameters (e.g., RRC parameters) of the terminal device 1. The radio resource control layer processing unit 16 sets the RRC parameters based on an RRC message received from the base station device 3.

The wireless transceiver 10 (or the wireless transmitter 10a) performs some or all of the modulation, encoding, and transmission processes. The wireless transceiver 10 (or the wireless transmitter 10a) generates a physical signal by performing some or all of the modulation, encoding, and baseband signal generation (conversion to a time-continuous signal) processes on the uplink data. The wireless transceiver 10 (or the wireless transmitter 10a) may place the physical signal in a certain BWP (active uplink BWP). The wireless transceiver 10 (or the wireless transmitter 10a) transmits the generated physical signal.

The wireless transceiver 10 (or the wireless receiver 10b) performs part or all of the demodulation process, the decoding process, and the reception process. The wireless transceiver 10 (or the wireless receiver 30b) may receive a physical signal in a certain BWP (active downlink BWP) of a certain serving cell. The wireless transceiver 10 (or the wireless receiver 10b) outputs information detected based at least on the demodulation process and the decoding process of the received physical signal to the upper layer processing unit 14.

When carrier sensing is required in the band of the serving cell, the radio transceiver unit 10 (radio receiver unit 10b) may perform carrier sensing prior to transmitting a physical signal.

The RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by quadrature demodulation 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 signal from which the CP has been removed to extract a signal in the frequency domain.

The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the uplink data, generates an OFDM symbol, adds a CP to the generated OFDM symbol, generates a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12. Prior to the inverse fast Fourier transform, modified precoding may be applied to the uplink data.

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 for controlling transmission power. The RF unit 12 is also referred to as a transmission power control unit.

The following explains physical signals (signals).

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

The uplink physical channel may correspond to a set of resource elements that convey 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 the terminal device 1. The uplink physical channel may be received by the base station device 3. In the uplink of the 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 transmitted to deliver, transmit, and convey uplink control information (UCI). The uplink control information may be mapped to the PUCCH. The terminal device 1 may transmit the PUCCH in which the uplink control information is mapped. The base station device 3 may receive the 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: Channel State Information), scheduling request (SR: Scheduling Request), and HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement) information.

The channel state information is also called a channel state information bit or a channel state information sequence. The scheduling request is also called a scheduling request bit or a scheduling request sequence. The HARQ-ACK information is also called a HARQ-ACK information bit or a HARQ-ACK information sequence.

The HARQ-ACK information may include at least a HARQ-ACK corresponding to a transport block (TB). The HARQ-ACK may indicate an acknowledgement (ACK) or a negative-acknowledgement (NACK) corresponding to the transport block. The ACK may indicate that the decoding of the transport block has been successfully completed. The NACK may indicate that the 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.

A transport block is a sequence of information bits delivered from a higher layer. Here, the sequence of information bits is also called a bit sequence. Here, the transport block may be delivered from the UL-SCH (UpLink-Shared CHannel) of the transport layer.

The HARQ-ACK for a transport block may be referred to as a HARQ-ACK for a PDSCH. In this case, "HARQ-ACK for a PDSCH" refers to a HARQ-ACK for a transport block included in the PDSCH.

HARQ-ACK may indicate ACK or NACK for each Code Block Group (CBG) of a transport block.

The scheduling request is sent to the UL-SCH for a new transmission.
The scheduling request bit may be used at least to request resources for the initial transmission. The scheduling request bit may be used to indicate either a positive SR or a negative SR. The scheduling request bit indicating a positive SR is also referred to as "a positive SR is transmitted". The positive SR may indicate that UL-SCH resources for the initial transmission are requested by the terminal device 1. The positive SR may indicate that a scheduling request is triggered by a higher layer. The positive SR may be transmitted when a scheduling request is indicated by a higher layer. The scheduling request bit indicating a negative SR is also referred to as "a negative SR is transmitted". The negative SR may indicate that UL-SCH resources for the initial transmission are not requested by the terminal device 1. The negative SR may indicate that a scheduling request is not triggered by a higher layer. The negative SR may be transmitted when a scheduling request is not indicated by a higher layer.

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 is an indicator regarding the reception state of at least a physical signal (e.g., CSI-RS) used for channel measurement. The value of the channel state information may be determined by the terminal device 1 based on the reception state assumed by at least a physical signal used for channel measurement. The channel measurement may include interference measurement.

The PUCCH may be transmitted with a certain PUCCH format. The PUCCH may be a set of resource elements used to convey the PUCCH format. The PUCCH may include the PUCCH format. The PUCCH format may be interpreted as a format of information. The PUCCH format may also be interpreted as a set of information set to a certain information format.

The PUSCH may be used to transmit one or both of a transport block and uplink control information. The PUSCH may be used to transmit one or both of a transport block delivered by the UL-SCH and uplink control information. The PUSCH may be used to transmit one or both of a transport block delivered by the UL-SCH and uplink control information. The transport block may be placed in the PUSCH. The transport block delivered by the UL-SCH may be placed in the PUSCH. The uplink control information may be placed in the PUSCH. The terminal device 1 may transmit a PUSCH in which one or both of a transport block and uplink control information are placed. The base station device 3 may receive a PUSCH in which one or both of a transport block and uplink control information are placed.

The PRACH may be transmitted to convey a random access preamble. The terminal device 1 may transmit the PRACH. The base station device 3 may receive the PRACH. The PRACH sequence x _u,v (n) is defined by x _u,v (n) = x _u (mod (n + C _v , L _RA )). Here, x _u is a ZC (Zadoff Chu) sequence. Also, x _u may be defined by x _u = exp (-jπui (i + 1) / L _RA ). Also, j is an imaginary unit. Also, π is the ratio of the circumference of a circle to its circumference. Also, C _v corresponds to a cyclic shift of the PRACH sequence. Also, L _RA corresponds to the length of the PRACH sequence. Also, L _RA is 839 or 139. Also, i is an integer ranging from 0 to L _RA -1. Also, u is the sequence index for the PRACH sequence.

For each PRACH opportunity, 64 random access preambles are defined. The random access preambles are identified based on a cyclic shift C _v of the PRACH sequence and a sequence index u for the PRACH sequence. Each of the 64 identified random access preambles may be indexed.

The uplink physical signal may correspond to a set of resource elements. The uplink physical signal may not be used to transmit information generated in a higher layer. In addition, the uplink physical signal may be used to transmit information generated in a physical 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 the uplink of the 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 the DMRS for the PUSCH (DMRS associated with the PUSCH, DMRS included in the PUSCH, DMRS corresponding to the PUSCH) may be given based on the set of antenna ports for the PUSCH. For example, the set of antenna ports for the DMRS for the PUSCH may be the same as the set of antenna ports for the PUSCH.

The transmission of the PUSCH and the transmission of the 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 the PUSCH. In other words, transmitting the PUSCH may be transmitting the PUSCH and the DMRS for the PUSCH.

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.

The transmission of the PUCCH and the transmission of the DMRS for the PUCCH may be indicated (or triggered) by one DCI format. The PUCCH format may indicate one or both of the mapping of the PUCCH to resource elements and the mapping of the DMRS for the PUCCH to resource elements. The PUCCH and the DMRS for the PUCCH may be collectively referred to as the PUCCH. That is, transmitting the PUCCH may be transmitting the PUCCH and the DMRS for the PUCCH.

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 that convey 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 the downlink of the 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 transmitted to convey one or both of the MIB (Master Information Block) and the physical layer control information. Here, the physical layer control information is information generated in the physical layer. The MIB is a set of parameters placed in the BCCH (Broadcast Control CHannel), which is a logical channel of the MAC layer. The BCCH is placed in the BCH, which is a channel of the transport layer. The BCH is placed in the PBCH. The terminal device 1 may receive the PBCH in which the MIB and one or both of the physical layer control information are placed. The base station device 3 may transmit the PBCH in which the MIB and one or both of the physical layer control information are placed.

For example, the physical layer control information may be configured with 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 from 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 the radio frame in which the PBCH is transmitted. Here, the half radio frame may be configured to include five subframes. Also, the half radio frame may be configured to include the first five subframes of the ten subframes included in the radio frame. Also, the half radio frame may be configured to include the last five subframes of the ten subframes included in the 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 composed of 3 bits of a 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 bits are 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 transmitted to transmit downlink control information (DCI). The downlink control information may be arranged in the PDCCH. The terminal device 1 may receive the PDCCH in which the downlink control information is arranged. The base station device 3 may transmit the PDCCH in which the downlink control information is arranged.

The downlink control information may be transmitted with a DCI format. The DCI format may be interpreted as a format of the downlink control information. The DCI format may be interpreted as a set of downlink control information set to a certain downlink control information format.

DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1 are DCI formats. 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 arranged in a certain cell. DCI format 0_0 includes at least some or all of fields 1A to 1E.
1A) Identifier field for DCI formats
1B) Frequency domain resource assignment field
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 including the DCI format specification field is an uplink DCI format or a downlink DCI format. That is, the DCI format specification field may be included in both the uplink DCI format and the downlink DCI format. Here, the DCI format specification field included in DCI format 0_0 may indicate 0. .

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

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

The frequency hopping flag field may be used to indicate whether frequency hopping is applied to the PUSCH.

The MCS field included in DCI format 0_0 may be used to indicate at least one or both of a modulation scheme and a target coding rate for the PUSCH. The target coding rate may be a target coding rate for a transport block arranged in the PUSCH. The size of the transport block (TBS: Transport Block Size) arranged in the PUSCH may be determined based on a part 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. .

DCI format 0_0 may not include a carrier indicator field. In other words, the serving cell to which the uplink component carrier on which the PUSCH scheduled by DCI format 0_0 is placed may be the same as the serving cell of the downlink component carrier on which the PDCCH including the DCI format 0_0 is placed. Based on detecting DCI format 0_0 in a downlink component carrier of a serving cell, the terminal device 1 may recognize that the PUSCH scheduled by DCI format 0_0 is placed on the uplink component carrier of the serving cell.

DCI format 0_0 may not include a BWP field. Here, DCI format 0_0 may be a DCI format that schedules a PUSCH without changing the active uplink BWP. Based on detecting DCI format 0_0 used for scheduling a PUSCH, the terminal device 1 may recognize that the PUSCH is to be transmitted without switching the active uplink BWP.

DCI format 0_1 is used at least for scheduling a PUSCH arranged in a certain cell. DCI format 0_1 includes at least a part 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.

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

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

The MCS field included in DCI format 0_1 may be used to indicate one or both of the modulation scheme and the target coding rate for the PUSCH.

The BWP field of the DCI format 0_1 may be used to indicate an uplink BWP in which a PUSCH scheduled by the DCI format 0_1 is arranged. That is, the DCI format 0_1 may involve a change in the active uplink BWP. The terminal device 1 may recognize the uplink BWP in which the PUSCH is arranged based on detecting the DCI format 0_1 used for scheduling the PUSCH.

DCI format 0_1 that does not include a BWP field may be a DCI format that schedules a PUSCH without changing the active uplink BWP. The terminal device 1 may recognize that the PUSCH is to be transmitted without switching the active uplink BWP based on detecting DCI format 0_1 that is used for scheduling a PUSCH and does not include a BWP field.

If the DCI format 0_1 includes a BWP field, but the terminal device 1 does not support the BWP switching function using the DCI format 0_1, the BWP field may be ignored by the terminal device 1. In other words, a terminal device 1 that does not support the BWP switching function may recognize that the PUSCH is transmitted without switching the active uplink BWP based on detecting the DCI format 0_1 that is used for PUSCH scheduling and includes the BWP field. Here, if the terminal device 1 supports the BWP switching function, it may report that "the terminal device 1 supports the BWP switching function" in the RRC layer function information reporting procedure.

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

When DCI format 0_1 includes a carrier indicator field, the carrier indicator field may be used to indicate the serving cell of the uplink component carrier in which the PUSCH is arranged. Based on detecting DCI format 0_1 in the downlink component carrier of a serving cell, the terminal device 1 may recognize that the PUSCH scheduled by the DCI format 0_1 is arranged in the uplink component carrier of the serving cell indicated by the carrier indicator field included in the DCI format 0_1.

When DCI format 0_1 does not include a carrier indicator field, the serving cell to which the uplink component carrier on which the PUSCH scheduled by DCI format 0_1 is placed may be the same as the serving cell of the downlink component carrier on which the PDCCH including the DCI format 0_1 is placed. Based on detecting DCI format 0_1 in a downlink component carrier of a serving cell, the terminal device 1 may recognize that the PUSCH scheduled by the DCI format 0_1 is placed on the uplink component carrier of the serving cell.

DCI format 1_0 is used at least for scheduling a PDSCH arranged in a certain cell. DCI format 1_0 includes at least a part 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.

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 the 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 the PDSCH.

The MCS field included in DCI format 1_0 may be used to indicate at least one or both of a modulation scheme and a target coding rate for the PDSCH. The target coding rate may be a target coding rate for a transport block placed in the PDSCH. The size of the transport block (TBS: Transport Block Size) placed in the PDSCH may be determined based on one or both of the target coding rate and the modulation scheme for the PDSCH.

The PDSCH_HARQ feedback timing indication field may be used 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 an index of one or more PUCCH resources included in the PUCCH resource set. Each 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 arranged may be the same as the downlink component carrier on which the PDCCH including the DCI format 1_0 is arranged. Based on detecting DCI format 1_0 in a certain downlink component carrier, the terminal device 1 may recognize that the PDSCH scheduled by the DCI format 1_0 is to be arranged on the downlink component carrier.

DCI format 1_0 may not include a BWP field. Here, DCI format 1_0 may be a DCI format that schedules a PDSCH without changing the active downlink BWP. Based on detecting DCI format 1_0 used for scheduling a PDSCH, the terminal device 1 may recognize that the PDSCH will be received without switching the active downlink BWP.

DCI format 1_1 is used at least for scheduling a PDSCH arranged in a certain cell. DCI format 1_1 includes 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 contained in DCI format 1_1 may indicate 1.

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 the 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 the PDSCH.

The MCS field included in DCI format 1_1 may be used to indicate at least one or both of the modulation scheme and the 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 an 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 an index of one or more PUCCH resources included in the PUCCH resource set.

The BWP field of DCI format 1_1 may be used to indicate the uplink BWP in which the PDSCH scheduled by the DCI format 1_1 is placed. In other words, DCI format 1_1 may involve a change in the active downlink BWP. The terminal device 1 may recognize the downlink BWP in which the PDSCH is placed based on detecting DCI format 1_1 used for scheduling the PDSCH.

DCI format 1_1 that does not include a BWP field may be a DCI format that schedules a PDSCH without changing the active downlink BWP. The terminal device 1 may recognize that it will receive the PDSCH without switching the active downlink BWP based on detecting DCI format 1_1 that is used for scheduling a PDSCH and does not include a BWP field.

If DCI format 1_1 includes a BWP field, but the terminal device 1 does not support the BWP switching function using DCI format 1_1, the BWP field may be ignored by the terminal device 1. In other words, a terminal device 1 that does not support the BWP switching function may recognize that it receives the PDSCH without switching the active downlink BWP based on detecting DCI format 1_1 that is used for PDSCH scheduling and includes a BWP field. Here, if the terminal device 1 supports the BWP switching function, it may report that "the terminal device 1 supports the BWP switching function" in the RRC layer function information reporting procedure.

When DCI format 1_1 includes a carrier indicator field, the carrier indicator field may be used to indicate the serving cell of the downlink component carrier on which the PDSCH scheduled by DCI format 1_1 is arranged. Based on detecting DCI format 1_1 in the downlink component carrier of a serving cell, the terminal device 1 may recognize that the PDSCH scheduled by DCI format 1_1 is arranged on the downlink component carrier of the serving cell indicated by the carrier indicator field included in the DCI format 1_1.

When DCI format 1_1 does not include a carrier indicator field, the downlink component carrier on which the PDSCH scheduled by DCI format 1_1 is arranged may be the same as the downlink component carrier on which the PDCCH including the DCI format 1_1 is arranged. Based on detecting DCI format 1_1 in a certain downlink component carrier, the terminal device 1 may recognize that the PDSCH scheduled by the DCI format 1_1 is arranged in the downlink component carrier of the certain serving cell.

The PDSCH may be transmitted to transmit a transport block. The PDSCH may be used to transmit a transport block delivered by the DL-SCH. The PDSCH may be used to transmit a transport block. The transport block may be placed in the PDSCH. The transport block delivered by 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. In addition, the downlink physical signal may be used to transmit information generated in a physical 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 the downlink of the 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 by the terminal device 1 to synchronize one or both of the frequency domain and the time domain of the downlink. The synchronization signal is a general term for the PSS (Primary Synchronization Signal) and the SSS (Secondary Synchronization Signal).

Fig. 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 indicates the time axis (OFDM symbol index _lsym ), and the vertical axis indicates the frequency domain. The diagonal line block indicates a set of resource elements for the PSS. The grid line block indicates a set of resource elements for the SSS. The horizontal line block indicates a set of resource elements for the PBCH and the DMRS for the PBCH (DMRS related to the PBCH, DMRS included in the PBCH, and DMRS corresponding to the PBCH).

As shown in FIG. 7, the SS/PBCH block includes a PSS, an SSS, and a PBCH. The SS/PBCH block also includes four consecutive OFDM symbols. The SS/PBCH block includes 240 subcarriers. The PSS is placed in the 57th to 183rd subcarriers in the first OFDM symbol. The SSS is placed in 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 placed in the 1st to 240th subcarriers of the second OFDM symbol, and in subcarriers where the DMRS for the PBCH is not placed. The PBCH is placed in the 1st to 48th subcarriers of the third OFDM symbol, and in subcarriers where the DMRS for the PBCH is not placed. The PBCH is placed in the 193rd to 240th subcarriers of the third OFDM symbol, and in subcarriers where the DMRS for the PBCH is not placed. The PBCH is placed in the 1st to 240th subcarriers of the fourth OFDM symbol, and in subcarriers where the DMRS for the PBCH is not placed.

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

The PBCH to 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 that 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 the DMRS for the PDSCH (DMRS associated with the PDSCH, DMRS included in the PDSCH, DMRS corresponding to the PDSCH) may be given based on the set of antenna ports for the PDSCH. For example, the set of antenna ports for the DMRS for the 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. That is, transmitting the PDSCH may be transmitting the PDSCH and the DMRS for the PDSCH.

The propagation path of a 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 by 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 propagation path of a 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 a set of resource elements on which a symbol of a certain PDCCH is transmitted and a set of resource elements on which a symbol of a DMRS for the certain PDCCH is transmitted, the PDCCH on which the symbol of the PDCCH is transmitted at a certain antenna port 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. Transport channels define the relationship between physical layer channels and MAC layer channels (also called logical channels).

The BCH of the transport layer is mapped to the PBCH of the physical layer. That is, a transport block passing through the BCH of the transport layer is delivered to the PBCH of the physical layer. Also, the UL-SCH of the transport layer is mapped to the PUSCH of the physical layer. That is, a transport block passing through the UL-SCH of the transport layer is delivered to the PUSCH of the physical layer. Also, the DL-SCH of the transport layer is mapped to the PDSCH of the physical layer. That is, a transport block passing through the DL-SCH of the transport layer is delivered to the PDSCH of the physical layer.

For each serving cell, one UL-SCH and one DL-SCH may be provided. BCH may be provided to the PCell. BCH may not be provided to the PSCell or SCell.

In the MAC layer, HARQ (Hybrid Automatic Repeat reQuest) is controlled for each transport block.

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

The logical channel BCCH is mapped to the BCH or DL-SCH of the transport layer. For example, a transport block containing MIB information is delivered to the BCH of the transport layer. A transport block containing system information other than the MIB is delivered to the DL-SCH of the transport layer. CCCH is mapped to the DL-SCH or UL-SCH. In other words, a transport block mapped to CCCH is delivered to the DL-SCH or UL-SCH. DCCH is mapped to the DL-SCH or UL-SCH. In other words, a transport block mapped to DCCH is delivered to the DL-SCH or UL-SCH.

The RRC message includes one or more parameters managed in the RRC layer. Here, the parameters managed in the RRC layer are also referred to as RRC parameters. For example, the RRC message may include an MIB. The RRC message may also include system information. The RRC message may also include a message corresponding to a CCCH. The RRC message may also include a message corresponding to a DCCH. An RRC message including a message corresponding to a DCCH is also referred to as an individual RRC message.

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

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 the terminal device 1 to synchronize with a certain cell in the time domain and the frequency domain and detect a physical cell identity. In other words, the terminal device 1 may use cell search to synchronize with a certain cell in the time domain and the 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 permitted (possible, reserved, configured, defined, possible).

The set of SS/PBCH block candidates in a half radio frame is also called an SS burst set. The SS burst set is also called a transmission window, an SS transmission window, or a Discovery Reference Signal transmission window (DRS 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 of the SS/PBCH blocks of the one or more indexes and attempt to decode the PBCH contained in the 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 in which a PRACH is transmitted by a terminal device 1. The terminal device 1 transmits a PRACH in one PRACH opportunity selected from one or more PRACH opportunities based on at least an index of an SS/PBCH block candidate detected based on a cell search. Each of the PRACH opportunities is defined based on at least resources in the time domain and the 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 RA-RNTI (Random Access - Radio Network Temporary Identifier). The terminal device 1 attempts to detect a PDCCH including the DCI format in a control resource set provided based on an MIB included in a PBCH included in an SS/PBCH block detected based on a cell search, and in resources indicated based on the setting of a 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 a 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 a PDSCH scheduled by the DCI format 1_0.

The PUSCH scheduled based on the random access response grant is either message 3 PUSCH or PUSCH. 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 Cell-Radio Network Temporary Identifier (C-RNTI) 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).

The 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, the control resource set may be composed of continuous resources (non-interleaved mapping) or may be composed of distributed resources (interleaver mapping).

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

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

The 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, the Type 0a PDCCH common search space set, the Type 1 PDCCH common search space set, the Type 2 PDCCH common search space set, the 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 general term for the Type 0 PDCCH common search space set, the Type 0a PDCCH common search space set, the Type 1 PDCCH common search space set, the Type 2 PDCCH common search space set, and the Type 3 PDCCH common search space set. The USS 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 a resource of a 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 PDCCH monitoring interval, the PDCCH monitoring pattern in the slot, and the PDCCH monitoring offset.

8 is a diagram showing an example of a monitoring opportunity of a search area set according to an aspect of the present embodiment. In FIG. 8, a search area set 91 and a search area set 92 are included in a primary cell 301.
2 is set in the secondary cell 302, a search area set 93 is set in the secondary cell 303, and a search area set 94 is set in the secondary cell 303.

In FIG. 8, the blocks indicated by grid lines represent search area set 91, the blocks indicated by diagonal lines going up to the right represent search area set 92, the blocks indicated by diagonal lines going up to the left represent search area set 93, and the 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, 1, 0, 0, 0, 0, 0, 0]. That is, the monitoring opportunities of 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]. That is, the monitoring opportunity of search area set 92 corresponds to the first OFDM symbol (OFDM symbol #0) in each of the even slots.

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,0,1,0,0,0,0,0,0,0]. That is, the monitoring opportunity of 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]. That is, the monitoring opportunity of 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).

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

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

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

The UE-specific PDCCH search space 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 a downlink DCI format. The detected downlink DCI format is used at least for resource allocation of the PDSCH. The detected downlink DCI format is also called a 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 a transport block included in the PDSCH) to the base station device 3.

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

In configured scheduling, an uplink grant for scheduling a PUSCH is configured for each transmission period of the PUSCH. When a PUSCH is scheduled by 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.

The uplink grant is managed by the media access control layer processing unit 15. For example, the uplink grant may be delivered to any of the N HARQ processes. For example, the entity that delivers the uplink grant to any of the N HARQ processes may be an HARQ entity included in the media access control layer processing unit 15.

Figure 9 is a diagram showing an example of the configuration of the media access control layer processing unit 15 according to one aspect of this embodiment. In Figure 9, the media access control layer processing unit 15 includes an HARQ entity 9000. The HARQ entity 9000 includes N HARQ processes. For example, N may be 8 or 16.

The media access control layer processing unit 15 may receive the uplink grant through the PDCCH. For example, the PDCCH may be processed in the physical layer processing unit 10.

When the media access control layer processing unit 15 receives an uplink grant through the PDCCH, the physical layer processing unit 10 may deliver HARQ information corresponding to the uplink grant to the media access control layer processing unit 15. Here, the HARQ information may include at least a HARQ process number corresponding to the uplink grant, a new data indicator (NDI) corresponding to the uplink grant, and a part or all of a redundancy version (RV) corresponding to the uplink grant. Here, the HARQ process number corresponding to the uplink grant may be provided by a field included in a DCI format included in the PDCCH. Also, the new data indicator corresponding to the uplink grant may be provided by a field included in a DCI format included in the PDCCH. Also, the RV corresponding to the uplink grant may be provided by a field included in a DCI format included in the PDCCH.

The HARQ entity 9000 may determine whether a transmission instruction to the physical layer processing unit 10 based on the uplink grant corresponds to a retransmission based on the uplink grant based on the new data indicator corresponding to the uplink grant. For example, the transmission instruction to the physical layer processing unit 10 based on the uplink grant does not correspond to a retransmission, which may mean that the transmission instruction corresponds to an initial transmission. For example, the HARQ entity 9000 may determine whether to acquire a MAC PDU for the uplink grant based on the new data indicator corresponding to the uplink grant. For example, if the value of the new data indicator corresponding to the uplink grant has switched to the value of the NDI for the transport block stored in the HARQ process corresponding to the uplink grant, the HARQ entity 9000 may acquire a MAC PDU. Also, if the value of the new data indicator corresponding to the uplink grant has not been switched to the value of the NDI for the transport block stored in the HARQ process corresponding to the uplink grant, the HARQ entity 9000 does not need to obtain the MAC PDU.

The HARQ entity 9000 may deliver the uplink grant and the HARQ information corresponding to the uplink grant to the HARQ process having the HARQ process number corresponding to the uplink grant. Furthermore, if the uplink grant does not support retransmission, the HARQ entity 9000 may deliver the acquired MAC PDU to the HARQ process having the HARQ process number corresponding to the uplink grant.

The HARQ process may instruct the physical layer processing unit 10 to transmit based on the received uplink grant and HARQ information. Furthermore, when the HARQ process receives a MAC PDU from the HARQ entity 9000, the HARQ process may store the MAC PDU in the HARQ buffer.

The physical layer processing unit 10 may perform a transport block encoding procedure based on a transmission instruction from the HARQ process. Here, the transport block is a MAC PDU delivered from the HARQ process. The transport block encoding procedure may be performed by the encoding unit 12000 included in the physical layer processing unit 10.

Fig. 10 is a diagram showing an example of the configuration of an encoding processor unit 12000 according to one aspect of this embodiment. In Fig. 10, the encoding processor unit 12000 includes at least a CRC addition unit 12001, a code lock segmentation unit 12002, an encoding unit 12003, a rate matching unit 12004, and some or all of a multiplexing unit 12005.

The transport block is input to the CRC addition unit 12001. In the CRC addition unit 12001, a CRC sequence may be added to the transport block. A bit sequence including the CRC and the transport block may be input to the code block division unit 12002. If a CRC sequence is not added to the transport block, the bit sequence including the transport block may be input to the code block division unit 12002.

The code block division unit 12002 may determine whether to divide the input bit sequence into a plurality of code blocks. For example, the code block division unit 12002 may determine whether to divide the input bit sequence into a plurality of code blocks by comparing the size of the input bit sequence with the maximum code block size. When the input bit sequence is divided into a plurality of code blocks, one CRC sequence may be added to each of the plurality of code blocks. Hereinafter, the code block to which one CRC sequence is added is also referred to as a code block. When the input bit sequence is not divided into a plurality of code blocks, the input bit sequence is regarded as one code block. One or more code blocks are input to the encoding unit 12003.

The coding unit 12003 may apply error correction coding to the code block r. For example, the method of error correction coding may be a Quasi-Cyclic Low Density Parity Check (QC-LDPC) code. Here, the index r of the code block may be any integer value from 0 to C-1. Furthermore, C indicates the number of one or more code blocks. By applying error correction coding to the code block r, a coded bit sequence d ^r for the code block r is generated. The generated coded bit sequence d ^r is input to the rate matching unit 12004.

The rate matching unit 12004 may implement a bit selection procedure, in which the coded bit sequence d ^r is input to a circular buffer of size N _cb .

Fig. 11 is a diagram showing an example of a bit selection procedure according to one aspect of this embodiment. In Fig. 11, the bit selection procedure includes eight steps. In step 1 of the bit selection procedure, the values of two variables k and j are set to 0, respectively. Then, in step 1, it is determined whether the value of the variable k is smaller than the rate matching output sequence length E _r . If the value of the variable k is smaller than the rate matching output sequence length E _r , the bit selection procedure proceeds to step 2. If the value of the variable k is not smaller than the rate matching output sequence length E _r , the bit selection procedure is completed.

The rate matching output sequence length E _r indicates the number of bits available for transmitting code block r. For example, the rate matching output sequence length E _r may be determined based on at least the modulation order Q _m of the PUSCH, the number of layers v of the PUSCH, the number C of code blocks, and a value G. For example, the rate matching output sequence length E _r may be determined by either E _r = vQ _m · floor(G/(vQ _m C)) or E _r = vQ _m · ceil(G/(vQ _m C)).

Here, the value G indicates the number of bits included in a PUSCH instance and available for UL-SCH transmission. Here, a PUSCH instance is also called a PUSCH transmission occasion. Also, the bits available for UL-SCH transmission indicate the number of bits available for transmission of a transport block.

In step 2, it is determined whether the value of d ^r (mod(k ₀ +j, N _cb )) is set to <NULL>. If the value of ^{d r} (mod(k ₀ +j, N _cb )) is not set to <NULL>, the bit selection procedure proceeds to step 3. If the value of d ^r (mod(k ₀ +j, N _cb )) is set to <NULL>, the bit selection procedure proceeds to step 6, where d ^r (k) denotes the k-th element of d ^r .

In step 3, the value of d ^r (mod(k ₀ +j, N _cb )) is input to e(k), where e is the rate matching output sequence. Also, e(k) denotes the k-th element of the rate matching output sequence e. Also, the sequence length of the rate matching output sequence e is E _r .

k ₀ indicates the starting position of the reading from the circular buffer, that is, in step 3, the value of d ^r (mod(k ₀ +j, N _cb )) is read from the circular buffer.

In step 4, the value of k is incremented.

Step 5 shows the termination point for step 2.

In step 6, the value of j is incremented.

Step 7 shows the termination point for step 1.

12 is a diagram showing the concept of a circular buffer according to one aspect of the present embodiment. In the circular buffer, the coded bit sequence d ^r is written clockwise from the position indicated by RV0. Since the coded bit sequence d ^r is a sequence in which a systematic bit sequence and a parity bit sequence are combined, the systematic bits are written clockwise from RV0 (the region indicated by the black frame in the figure), and the parity bit sequence is written from the end of the systematic bit sequence (the region indicated by the white frame in the figure).

In the bit selection procedure, E _r bits written in the circular buffer may be read out from the starting position k _0. The read E _r bits are input to a rate matching output sequence e. Here, the starting position k ₀ may be determined based on the RV value indicated by the DCI format used for scheduling the PUSCH.

An interleaver may be applied to the rate matching output sequence generated in the bit selection procedure. Furthermore, if multiple code blocks are generated, the rate matching output sequences for each of the code blocks may be combined to generate one sequence g. Furthermore, if multiple code blocks are not generated, one rate matching output sequence may be regarded as one sequence g. One sequence g may be input to the multiplexing unit 12005.

In the multiplexing unit 12005, one sequence g and control data (for example, HARQ-ACK, CSI, etc.) may be multiplexed. For example, the multiplexing unit 12005 may generate an array Q. Each of the elements of the array Q may be identified based on at least some or all of an index k' _sc related to a subcarrier, an index l' related to an OFDM symbol, and an index m' based on a modulation order and a number of layers. Here, the index k' _sc related to a subcarrier may be an index related to a subcarrier to which an instance of a PUSCH is assigned. Also, the index l' related to an OFDM symbol may be an index m' related to an OFDM symbol to which an instance of a PUSCH is assigned. Also, the index based on a modulation order and a number of layers may take a value from 0 to Q _m N _v -1. Here, each element of the array is identified by Q(k' _sc , l', m'). That is, an element of array Q with index _k'sc = _kx , index l' = _lx , and index m' = _mx is referred to as Q( _kx , _lx , _mx ).

In the multiplexing unit 12005, when the coded bit sequence q of HARQ-ACK is arranged in the array Q, the multiplexing unit 12005 may specify a start position l _start . When the start position l _start is specified, the coded bit sequence q may be arranged in Q(k' _sc , l _start , m'). Here, the coded bit sequence q may be arranged in ascending order with respect to the index m', and then arranged in the direction of the index k' _sc . When the arrangement of the coded bit sequence q is completed in the element of the array of l=l _start , the arrangement may move to the element of the array of l=l _start +1.

For a coded bit sequence q of HARQ-ACK bits, l _start may indicate the OFDM symbol next to the OFDM symbol containing the DMRS assigned to the PUSCH instance. For example, in the PUSCH instance, if the first DMRS is assigned to the second OFDM symbol, l _start may be 2. Here, the index l′ is assumed to start from 0.

For one sequence g, the starting position l _start may be 0 regardless of DMRS allocation.

The multiplexing unit 12005 reads a sequence from the array Q and generates sequence b. Sequence b is subjected to various baseband processing and used to generate a time domain signal. Here, the various baseband processing includes at least some or all of scrambling, modulation, layer mapping, resource element mapping, and time domain signal generation.

When transmitting PUSCH in multiple slots, repeated transmission of PUSCH can be used. In repeated transmission of PUSCH, one instance of PUSCH may be generated for each slot and transmitted in multiple slots.

The repeated transmission of the PUSCH may be triggered, for example, by the PDCCH. For example, the medium access control layer processing unit 15 may obtain one uplink grant from the PDCCH. Here, in the repeated transmission of the PUSCH, the HARQ entity may generate N uplink grants from the one uplink grant. Here, N is the number of repetitions for the repeated transmission of the PUSCH. For example, the number of repetitions N may be provided from the RRC layer. Furthermore, N may be indicated by the PDCCH that provides the uplink grant that triggers the repeated transmission of the PUSCH.

In the repeated transmission of the PUSCH, the HARQ entity may deliver the N uplink grants to one HARQ process, where the one HARQ process may be determined by HARQ information associated with the N uplink grants.

In repeated transmission of the PUSCH, the HARQ process may issue N transmission instructions to the physical layer processing unit 10 based on N uplink grants.

In repeated transmission of the PUSCH, the physical layer processing unit 10 may generate and transmit N instances of the PUSCH based on N transmission instructions. Here, it may be determined for each PUSCH instance whether or not a collision with another uplink channel occurs. If a certain PUSCH instance collides with an uplink channel with a higher priority, the transmission of the certain PUSCH instance may be omitted. Here, omitting the transmission of the PUSCH instance may mean that the transmission is dropped or that the transmission is not performed.

It may also be determined whether at least some of the OFDM symbols in the set of OFDM symbols in which a PUSCH instance is transmitted belong to the downlink region. If at least some of the OFDM symbols in the set of OFDM symbols in which a PUSCH instance is transmitted belong to the downlink region, the transmission of the instance may be omitted.

Multi-slot transmission of the PUSCH may be a transmission method that generates an instance of the PUSCH consisting of multiple slots. Multi-slot transmission of the PUSCH is performed by the physical layer processing unit 10.

Figure 13 is a diagram showing an example of multi-slot transmission of PUSCH according to one aspect of this embodiment. In Figure 13, the horizontal axis is the time axis, and each grid on the time axis is a slot boundary. In addition, the slot index is set in ascending order to the right, and the first slot in the figure is slot #n.

In the multi-slot transmission shown in Fig. 13, the number of repetitions N of the PUSCH is set to 8, and 8 slots of time resources are used in the multi-slot transmission. Meanwhile, each of the PUSCH instances 13001, 13002, and 13003 is composed of a time resource of a plurality of slots. That is, in the multi-slot transmission of the PUSCH, the type of the PUSCH instance and the number of PUSCH instances N _instance may be determined based at least on the number of repetitions N and an external parameter. Here, the external parameter may be provided by the RRC layer or may be provided by the PDCCH that provides an uplink grant instructing the multi-slot transmission.

The physical layer processing unit 10 may report the number N _instance to the media access control layer processing unit 15 .

For example, the external parameter may be the number of repetitions N _unit constituting a PUSCH instance. For example, the number of PUSCH instances N _instance may be determined by ceil(N/N _unit ). In addition, each of the N _instance -1 PUSCH instances may be configured to include N _unit repetitions, and one PUSCH instance may be configured to include mod(N, N _unit ) repetitions.

Here, the number of repetitions N _units constituting an instance of the PUSCH may be indicated by a parameter provided by the RRC layer. Also, the number of repetitions N _units constituting an instance of the PUSCH may be provided by the PDCCH.

The HARQ entity 9000 may issue an uplink grant based on a number N _instances determined by the physical layer processing unit 10. For example, the HARQ entity 9000 may issue N _instances of uplink grants. Also, the HARQ process may issue a transmission instruction to the physical layer processing unit 10 based on the N _instances of uplink grants.

The physical layer processing unit 10 may generate one PUSCH instance for each transmission instruction of the HARQ process.

Figure 14 is a diagram showing an example of multi-slot transmission of PUSCH according to one aspect of the present embodiment. In Figure 14, the horizontal axis is the time axis, and each grid on the time axis is a slot boundary. In addition, the slot index is set in ascending order to the right, and the first slot in the figure is slot #n. In addition, each of 14001 to 14008 indicates a time resource set for multi-slot transmission of PUSCH. In Figure 14, the number of repetitions is set to N = 8, and time resources are set for each of slots #n to #n + 7. In the example shown in Figure 14, the instance of PUSCH for multi-slot transmission may be determined based on the number of repetitions N and the setting of the TDD pattern. Here, in Figure 14, the time resource corresponding to the black frame indicates the downlink region, and the time resource corresponding to the white frame indicates the uplink region. In the example shown in Figure 14, the instance of PUSCH may be configured by continuous time resources corresponding to the uplink region among the resources corresponding to N repetitions. In the example of Figure 14, 14011 and 14012 each indicate an instance of PUSCH.

For example, the external parameter may be a TDD pattern setting. One PUSCH instance may be configured with a set of time resources corresponding to one uplink region that is continuous in time among the time resources corresponding to N repetitions. In other words, one PUSCH instance may be configured not to include time resources corresponding to the downlink region. Here, the uplink region may or may not include a flexible region. Also, the uplink region may or may not include a flexible region.

For example, the external parameter may be a parameter indicating whether or not multi-slot transmission is applied. For example, when the external parameter indicates the application of multi-slot transmission, time resources corresponding to N repetitions are collected to generate one PUSCH instance, and the number of PUSCH instances N _instance may be 1. Also, when the external parameter does not indicate the application of multi-slot transmission, N PUSCH instances may be generated, and the number of PUSCH repetitions N may be reported to the media access control layer processing unit 15.

For example, when the external parameters indicate the application of multi-slot transmission, the number of PUSCH instances may be determined based on the number of repetitions N _units constituting the PUSCH instances. Also, when the external parameters indicate the application of multi-slot transmission, the configuration of the PUSCH instances may be determined based on N _units .

For example, when the external parameters indicate the application of multi-slot transmission, the configuration of the PUSCH instances may be determined based on the setting of the TDD pattern. Also, when the external parameters indicate the application of multi-slot transmission, the number of PUSCH instances may be determined based on the setting of the TDD pattern.

For example, a parameter indicating whether multi-slot transmission is applied may be provided by a parameter of the RRC layer. Also, a parameter indicating whether multi-slot transmission is applied may be provided by a DCI format used for scheduling the PUSCH.

For example, the parameter indicating whether multi-slot transmission is applied may be provided by a TDRA field included in the DCI format used for scheduling the PUSCH. For example, each column of the table corresponding to the TDRA field may indicate the time resource of the PUSCH and the parameter. Here, the time resource of the PUSCH may indicate the starting OFDM symbol S of the PUSCH in the slot and the number of OFDM symbols L of the PUSCH in the slot.

By using external parameters, the media access control layer processing unit 15 can appropriately issue transmission instructions to the physical layer processing unit 10.

In multi-slot transmission of PUSCH, the procedure regarding collision with PUCCH may be performed for each PUSCH instance. For example, if a certain PUSCH instance collides with PUCCH, the UCI that was scheduled to be transmitted on PUCCH may be multiplexed into the certain PUSCH instance.

For example, when a certain PUSCH instance collides with a PUCCH on which a HARQ-ACK is scheduled to be transmitted, the coded bit sequence q of the HARQ-ACK is
The multiplexing unit 12005 may multiplex one sequence g that was to be transmitted in the PUSCH instance with the coded bit sequence q. Here, the coded bit sequence q may specify a start position l _start based on the OFDM symbol next to the OFDM symbol including the first DMRS in the instance.

For example, in order to specify the start position l _start , the first DMRS in the slot in which the PUCCH is multiplexed may be specified. For example, when an instance of the PUSCH is arranged in slots #n, #n+1, and #n+2, and the PUCCH is arranged in slot #n+2, the OFDM symbol including the first DMRS in slot #n+2 may be specified to specify the start position l _start . Here, the start position l _start may be specified based on the next OFDM symbol of the OFDM symbol including the first DMRS.

A method for determining the circular buffer size N _cb will now be described.

If the size N _cb of the circular buffer is equal to the size of the coded bit sequence d ^r , all bits included in the coded bit sequence d ^r can be written into the circular buffer. On the other hand, the capacity of the storage device (or buffer, memory, storage, etc.) included in the terminal device 1 is finite. In addition, the base station device 3 needs to have a soft buffer corresponding to the size of the circular buffer. The soft buffer needs to store a soft value (e.g., a quantized value of a log-likelihood ratio) for each coded bit for a predetermined period of time, and a storage device with a large capacity needs to be allocated for the soft buffer. For this reason, LBRM (Limited Buffer Rate Matching) is specified for uplink communication in NR.

In addition, in NR, LBRM is also specified for downlink communication, and various aspects of the present invention are applicable to both downlink and uplink communication.

The application of the uplink LBRM may be controlled by a parameter of the RRC layer. For example, when the value of the RRC parameter provided by the RRC layer is set to 0, the value of _Ncb may be set to N, where N is the size of the coded bit sequence d ^r . Also, when the value of the RRC parameter is set to a value other than 0 (e.g., 1), _Ncb may be determined based on comparing N with the value of _Nref . For example, when the value of the RRC parameter is set to a value other than 0, _Ncb may be set to a value calculated by min(N, _Nref ).

N _ref may be determined based on some or all of TBS _LBRM , C, and R _LBRM . For example, N _ref may be calculated as floor(TBS _LBRM /(C·R _LBRM )), where TBS _LBRM is a transport block size calculated under a certain assumption. C may be the number of code blocks determined based on the transport block size calculated under the certain assumption. C may be the number of code blocks for the transport block included in the transmission of PUSCH. R _LBRM is a predetermined value, for example, 2/3.

In calculating the TBS _LBRM , certain assumptions may be made for each of some or all of the values of the number of layers v, the modulation order Q _m , the coding rate R, the number of PRBs n _PRB , and the number of resource elements per PRB N _RE .

The assumption for the number of layers v may be determined based on one or both of the maximum number of layers reported by the functional information reporting procedure of the terminal device 1 and the maximum number of layers (or maximum rank) provided by the RRC layer.

The assumption for the modulation order _Qm may be determined based on the MCS table set in the terminal device 1. For example, when the first MCS table is set to be used for at least one of one or more BWPs set in the serving cell, _Qm may be assumed to be 8. Here, the first MCS table may be an MCS table including a column indicating a modulation method of 256QAM. Also, when the first MCS table is not set to be used for any of one or more BWPs set in the serving cell, _Qm may be assumed to be 6.

The coding rate R may be assumed to be a predetermined value. For example, the predetermined value may be 948/1024.

The assumption for the number of PRBs n _PRBs may be determined based on the number of PRBs in the BWP. For example, the assumption for the number of PRBs n _PRBs may be determined based on the maximum number of the respective numbers of PRBs in one or more BWPs configured in the serving cell.

An assumption for the number of resource elements per PRB, N _RE , may be determined based on the number of PRBs, n _PRB , for example, N _RE = 156·N _PRB .

On the other hand, a scaling method is applied in determining the transport block size. Here, the scaling method may be used to realize an appropriate coding rate for PUSCH transmission in multiple slots. Here, the application of the scaling method to PUSCH transmission may be dynamically switched. For example, scaling may be applied in determining the transport block size of the transport block for PUSCH transmission scheduled by the first DCI format, and scaling may not be applied in determining the transport block size of the transport block for PUSCH transmission scheduled by the second DCI format.

In addition, a parameter indicating whether or not the scheduling method is applied to the determination of the transport block size may be provided by the RRC layer. Also, a parameter K that is acted upon in the process of determining the transport block size may be provided by the RRC layer. Here, by providing the parameter K that is acted upon in the process of determining the transport block size by the RRC layer, the terminal device 1 may recognize that the scheduling method is applied to the determination of the transport block size. Also, by not providing the parameter K that is acted upon in the process of determining the transport block size by the RRC layer, the terminal device 1 may recognize that the scheduling method is not applied to the determination of the transport block size.

In addition, whether or not a scaling technique is applied to determine the transport block size for a certain transport block may be indicated by the DCI format that schedules the PUSCH used to transmit the certain transport block. For example, if the parameter K is indicated by the DCI format that is used to schedule the PUSCH, the terminal device 1 may recognize that a scheduling technique is applied to determine the transport block size for the transport block included in the PUSCH. In addition, if the parameter K is not indicated by the DCI format that is used to schedule the PUSCH, the terminal device 1 may recognize that a scheduling technique is not applied to determine the transport block size for the transport block included in the PUSCH.

For example, the parameter K may be included for each of the columns of the table corresponding to the TDRA field. Here, the TDRA field included in the DCI format used for scheduling the PUSCH may indicate the parameter K by indicating one of the columns of the table.

For example, the scaling technique may be implemented by applying a parameter K to the process of determining the transport block size.

Here, the process of determining the transport block size may include at least some or all of steps 1 to 3 below.
Step 1) Determine _NRE. Step 2) Determine the intermediate number of information bits _Ninfo = _NRE ·R· _Qm ·v. Step 3) Determine the size of the transport block.

Step 1 may further include at least part or all of steps 1a and 1b.
Step 1a) Determine N ^a _RE = N ^RB _sc · N ^sh _symb - ^{N PRB} _DMRS - N ^PRB _oh. Step 1b) Determine N _RE = min (X1, N ^a _RE ) · n _PRB.

Now, if a scaling approach is applied, procedure 1a may be modified to N ^a _RE = K·N ^RB _sc ·N ^sh _symb −N ^PRB _DMRS −N ^PRB _oh .

Here, N ^sh _symb may be determined based at least on the number L of OFDM symbols of PUSCH in a slot. For example, N ^sh _symb may be the number L of OFDM symbols of PUSCH in a slot. ^{N PRB} _DMRS is an overhead value taking into account resource elements in which DMRS for the PUSCH is arranged. N ^PRB _DMRS may be the number per PRB of resource elements in which DMRS is arranged in the OFDM symbol allocated for the PUSCH. N ^PRB _oh is a value that can take into account overhead caused by elements other than DMRS for PUSCH. Here, the overhead caused by elements other than DMRS may include at least overhead caused by arrangement of a control resource set or overhead caused by arrangement of CSI-RS. For example, N ^PRB _oh may be provided by an RRC parameter. Even if the terminal device 1 holds N ^PRB _oh , in transmitting the message 3 PUSCH, N ^PRB _oh may be assumed to be 0. Also, if the terminal device 1 does not hold N ^PRB _oh , in transmitting the PUSCH, N ^PRB _oh may be assumed to be 0.

For example, in procedure 1b, n _PRB may be the number of resource blocks allocated for the PUSCH.

Now, if a scaling approach is applied, procedure 1b may be modified to N _RE =min(X1,N ^a _RE )·n _PRB ·K.

In step 2, the coding rate R is a target coding rate corresponding to the value of the MCS. In step 2, the modulation order _Qm is the modulation order of the modulation method of the PUSCH. In step 2, v is the number of layers of the PUSCH. The number of layers is also called the spatial multiplexing number. That is, the layer may be the number of spatial streams.

Now, if a scaling approach is applied, step 2 may be modified to N _info =K·N _RE ·R·Q _m ·v.

Procedure 3 is a procedure for determining TBS based on N _info . For example, in procedure 3, switching between procedure 3a and procedure 3c may be performed based on the value of N _info . For example, procedure 3a may be performed when the value of N _info is equal to or smaller than a predetermined value. Also, procedure 3c may be performed when the value of N _info exceeds the predetermined value. Here, the predetermined value may be 3824, for example.

In step 3a, ^Na _info is given by Na info =max(24,floor(N _info /2 _^ n)· ² ^n). In step 3a, n=max(3,floor(N _info )-6).

For example, step 3a may be performed, followed by step 3b.

In step 3b, one value is selected from the candidate values of the transport block size contained in a predetermined table. Here, the predetermined table contains the following candidate values of the transport block size: 24, 32, 40, 48, 56, 64, 72, 80, 88, 96, 104, 112, 120, 128, 136, 144, 152, 160, 168, 176, 184, 192, 208, 224, 240, 256, 272, 288, 304, 320, 336, 352, 368, 384, 408, 432, 456, 480, 504, 528, 552, 576, 608, 640, 672, 704, 736, 768, 808, 848, 888 , 928, 984, 1032, 1064, 1128, 1160, 1192, 1224, 1256, 1288, 1320, 1352, 1416, 1480, 1544, 1608, 1672, 1736, 1800, 1864, 1928, 2024, 2088, 2152, 2216, 2280, 2408, 2472, 2536, 2600, 2664, 2728, 2792, 2856, 2976, 3104, 3240, 3368, 3496, 3624, 3753, 3824. That is, the predetermined table may include a set of integer values in a range not exceeding the predetermined value.

For example, in step 3b, a candidate value of TBS that is closest to ^Na _info within a range not below ^Na _info may be determined from the predetermined table.

In step 3c, ^Na _info is given by Na info =max(3840,2^n·round((N _{info -} 24)/2^n)). In step 3c, ⁿ is given _by n=floor(log2(N _info - 24)) - 5.

For example, step 3c may be performed, followed by step 3d.

In step 3d, N _TBS is determined. N _TBS is the TBS. For example, if R is less than or equal to 1/4, then N _TBS = 8·C·ceil((N ^a _info + 24)/(8·C)) - 24, where C = ceil((N ^a _info + 24)/3816).

In step 3d, for example, when R exceeds 1/4 and N ^a _info exceeds 8424, N _TBS is given by 8·C·ceil((N ^a _info +24)/(8·C))−24, where C is given by C=ceil((N ^a _info +24)/8424).

In step 3d, for example, when R exceeds 1/4 and N ^a _info is equal to or smaller than 8424, N _TBS is given by 8·ceil((N ^a _info +24)/8)−24.

For example, the value of K used in the scaling method may be dynamically switched. For example, in the process of determining the transport block size of a transport block for a PUSCH scheduled by a first DCI format, K may be set to a first value, and in the process of determining the transport block size of a transport block for a PUSCH scheduled by a second DCI format, K may be set to a second value. Here, the first value may be different from the second value.

That is, the parameter TBS _LBRM in LBRM is preferably calculated under some assumptions regarding the value of K used in the scaling procedure.

For example, the transport block size of a PUSCH transport block may be determined based on the application of a scaling technique, where K may be a value greater than 1. Also, the TBS _LBRM may be determined for one or more code blocks generated from the transport block, assuming that no scaling technique is applied.

For example, the transport block size of a PUSCH transport block may be determined based on the application of a scaling technique, where K may be a value greater than 1, and a TBS _LBRM may be determined for one or more code blocks generated from the transport block, assuming that a scaling technique is applied based on K=1.

For example, the transport block size of the transport block of the PUSCH may be determined based on the application of a scaling technique, where K may be a value greater than 1. Also, the TBS _LBRM may be determined for one or more code blocks generated from the transport block, on the assumption that a scaling technique is applied based on K being a predetermined value. Here, the predetermined value may be the smallest value among candidate values of K set for the serving cell. Also, the predetermined value may be the largest value among candidate values of K set for the serving cell.

For example, the encoding unit 12003 may generate a coded bit sequence d ^r by encoding a bit sequence of an r-th code block among one or more code blocks included in a transport block of a first size. The rate matching unit 12004 may apply a bit selection procedure to the coded bit sequence d based on comparing a size N of the coded bit sequence d ^r with N _ref . Here, N _ref may be determined based on a second size. Here, the first size may be determined by applying a scaling technique using a value of K greater than 1 to the process of determining the transport block size. Also, the second size may be determined under the assumption that a scaling technique is not applied to the process of determining the transport block size.

For example, the encoding unit 12003 may generate a coded bit sequence d ^r by encoding a bit sequence of an r-th code block among one or more code blocks included in a transport block of a first size. The rate matching unit 12004 may apply a bit selection procedure to the coded bit sequence d based on comparing a size N of the coded bit sequence d ^r with N _ref . Here, N _ref may be determined based on a second size. Here, the first size may be determined by applying a scaling technique using a value of K greater than 1 to the process of determining the transport block size. Also, the second size may be determined under the assumption that a scaling technique using K with a value of 1 is applied to the process of determining the transport block size.

For example, the encoding unit 12003 may generate an encoded bit sequence d ^r by encoding a bit sequence of an r-th code block among one or more code blocks included in a transport block of a first size. Furthermore, the rate matching unit 12004 may apply a bit selection procedure to the encoded bit sequence d based on comparing the size N of the encoded bit sequence d ^r with N _ref . Here, N _ref may be determined based on a second size. Here, the first size may be determined by applying a scaling method using a value of K greater than 1 to the process of determining the transport block size. Furthermore, the second size may be determined under the assumption that a scaling method using K whose value is X is applied to the process of determining the transport block size. Here, X may be a value that is known before the terminal device 1 is scheduled to transmit the transport block. For example, X may be a value provided by the RRC layer. Furthermore, X may be the smallest value among the candidate values of K set in the serving cell. Furthermore, X may be the largest value among the candidate values of K set in the serving cell.

Various aspects of the device according to one aspect of this embodiment are described below.

(1) In order to achieve the above object, the aspects of the present invention take the following measures. That is, a first aspect of the present invention is a terminal device, comprising: an encoding unit that generates a coded bit sequence d by encoding a bit sequence of a certain code block among one or more code blocks included in a transport block of a first size; and a rate matching unit that applies a bit selection procedure to the coded bit sequence d based on comparing a length N of the coded bit sequence d with _Nref , wherein the _Nref is determined based on a second size;
The first size is determined by applying a scaling technique using a value of K greater than 1 to the process of determining the transport block size, and the second size is determined under the assumption that the scaling technique is not applied to the process of determining the transport block size.

(2) A second aspect of the present invention is a base station apparatus comprising: a decoding unit that decodes a coded bit sequence d generated by coding a bit sequence of a certain code block among one or more code blocks included in a transport block of a first size; and a rate matching unit that applies a bit selection procedure to the coded bit sequence d based on comparing a length N of the coded bit sequence d with _Nref , wherein _Nref is determined based on a second size, the first size is determined by applying a scaling technique using a value of K greater than 1 to a process of determining a transport block size, and the second size is determined under the assumption that the scaling technique is not applied to the process of determining the transport block size.

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

In addition, a part of the terminal device 1 and the base station device 3 in the above-mentioned embodiment may be realized by a computer. In that case, the program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to realize the control function.

Note that the "computer system" referred to here is a computer system built into the terminal device 1 or base station device 3, and includes hardware such as the OS and peripheral devices. Additionally, the "computer-readable recording medium" refers to portable media such as floppy 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 also include something that dynamically holds 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 something that holds a program for a certain period of time, such as volatile memory inside a computer system that serves as a server or client in such a case. The above program may also be one that realizes part of the functions described above, or one that can realize the functions described above in combination with a program already recorded in the computer system.

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. The terminal device 1 related to the above-described embodiment can also communicate with the base station device as a collection.

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

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

In addition, in the above-described 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-movable 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 above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within the scope of the gist of the present invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which elements described in the above embodiments are replaced with elements that have the same effect are also included.

1 (1A, 1B, 1C) Terminal device 3 Base station device 10, 30 Radio transmission/reception unit 10a, 30a Radio transmission unit 10b, 30b Radio reception unit 11, 31 Antenna unit 12, 32 RF unit 13, 33 Baseband unit 14, 34 Upper layer processing unit 15, 35 Media access control layer processing unit 16, 36 Radio resource control layer processing unit 91, 92, 93, 94 Search space set 300 Component carrier 301 Primary cell 302, 303 Secondary cell 3000 Points 3001, 3002 Resource grid 3003, 3004 BWP
3011, 3012, 3013, 3014 Offset 3100, 3200 Common resource block set 9000 HARQ entity 12000 Encoding processing unit 13001, 13002, 13003, 14011, 14012 Instance 14001, 14002, 14003, 14004, 14005, 14006, 14007, 14008 Time resource

Claims (4)

a coding unit that generates a coded bit sequence d by coding a bit sequence of a certain code block among one or more code blocks included in a transport block of a first size;
a rate matching unit configured to apply a bit selection procedure to the coded bit sequence d based on comparing a length N of the coded bit sequence d with _Nref ;
The _Nref is determined based on a second size;
The first size is determined by N _RE =min(156, N ^a _RE )·n _PRB ·K , with K being a value greater than 1;
Here, the N ^a _RE is determined by N ^a _RE = N ^RB _sc · N ^sh _symb - ^{N PRB} _DMRS - N ^PRB _oh ;
N ^RB _sc is the number of subcarriers per resource block;
The N ^sh _symb is the number of OFDM symbols of the PUSCH to which the coded bit sequence d is mapped,
The N ^PRB _DMRS is an overhead value taking into account resource elements in which the DMRS for the PUSCH is arranged;
The N ^PRB _oh is a value taking into account overhead caused by factors other than the DMRS for the PUSCH,
The second size is determined by N _RE =min(156, N ^a _RE )·n _PRB ;
Terminal device. a decoding unit configured to decode a coded bit sequence d generated by coding a bit sequence of a certain code block among one or more code blocks included in a transport block of a first size;
a rate matching unit configured to apply a bit selection procedure to the coded bit sequence d based on comparing a length N of the coded bit sequence d with _Nref ;
The _Nref is determined based on a second size;
the first size is determined by N _RE =min(156, N ^a _RE )·n _PRB ·K with a value of K greater than 1;
Here, the N ^a _RE is determined by N ^a _RE = N ^RB _sc · N ^sh _symb - ^{N PRB} _DMRS - N ^PRB _oh ;
N ^RB _sc is the number of subcarriers per resource block;
The N ^sh _symb is the number of OFDM symbols of the PUSCH to which the coded bit sequence d is mapped,
The N ^PRB _DMRS is an overhead value taking into account resource elements in which the DMRS for the PUSCH is arranged;
The N ^PRB _oh is a value taking into account overhead caused by factors other than the DMRS for the PUSCH,
The second size is determined by N _RE =min(156, N ^a _RE )·n _PRB ;
Base station equipment. A communication method for use in a terminal device, comprising:
generating a coded bit sequence d by coding a bit sequence of a code block among one or more code blocks included in a transport block of a first size;
applying a bit selection procedure to the coded bit sequence d based on comparing a length N of the coded bit sequence d with _Nref ;
The _Nref is determined based on a second size;
the first size is determined by N _RE =min(156, N ^a _RE )·n _PRB ·K with a value of K greater than 1;
Here, the N ^a _RE is determined by N ^a _RE = N ^RB _sc · N ^sh _symb - ^{N PRB} _DMRS - N ^PRB _oh ;
N ^RB _sc is the number of subcarriers per resource block;
The N ^sh _symb is the number of OFDM symbols of the PUSCH to which the coded bit sequence d is mapped,
The N ^PRB _DMRS is an overhead value taking into account resource elements in which the DMRS for the PUSCH is arranged;
The N ^PRB _oh is a value taking into account overhead caused by factors other than the DMRS for the PUSCH,
The second size is determined by N _RE =min(156, N ^a _RE )·n _PRB ;
Communication methods. A communication method used in a base station device, comprising:
decoding a coded bit sequence d generated by coding a bit sequence of a certain code block among one or more code blocks included in a transport block of a first size;
applying a bit selection procedure to the coded bit sequence d based on comparing a length N of the coded bit sequence d with _Nref ;
The _Nref is determined based on a second size;
the first size is determined by N _RE =min(156, N ^a _RE )·n _PRB ·K with a value of K greater than 1;
Here, the N ^a _RE is determined by N ^a _RE = N ^RB _sc · N ^sh _symb - ^{N PRB} _DMRS - N ^PRB _oh ;
N ^RB _sc is the number of subcarriers per resource block;
The N ^sh _symb is the number of OFDM symbols of the PUSCH to which the coded bit sequence d is mapped,
The N ^PRB _DMRS is an overhead value taking into account resource elements in which the DMRS for the PUSCH is arranged;
The N ^PRB _oh is a value taking into account overhead caused by factors other than the DMRS for the PUSCH,
The second size is determined by N _RE =min(156, N ^a _RE )·n _PRB ;
Communication methods.

Images