JP7785068B2 - 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.
This application claims priority to Japanese Patent Application No. 2021-74580, filed on April 27, 2021, the contents of which are incorporated herein by reference.

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

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

It is expected that studies will be conducted on functional expansion of cellular mobile communications, such as NR. For example, as shown in Non-Patent Document 2, studies on expanding the functionality of NR have 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

One aspect of 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 that communicates with a base station device, the terminal device comprising: a physical layer processing unit and a medium access control layer processing unit; the physical layer processing unit delivers HARQ information included in a received PDCCH to the medium access control layer processing unit; the physical layer processing unit determines a number of PUSCH instances, N _instances , based on a number of PUSCH repetitions N and an external parameter provided from the base station device; the determined number is delivered to the medium access control layer processing unit; the medium access control layer processing unit obtains one uplink grant from the PDCCH; the medium access control layer processing unit further comprises a HARQ entity and a HARQ process; the HARQ entity generates N _instances of uplink grants based on the one uplink grant; and the HARQ process issues N _instances of transmission instructions to the physical layer processing unit based on the N _instances of uplink grants.

(2) A second aspect of the present invention is a base station device comprising a physical layer processing unit and a medium access control layer processing unit, wherein the physical layer processing unit transmits HARQ information on a PDCCH, and the physical layer processing unit determines a number N _instances of a PUSCH based on a number N of PUSCH repetitions and an external parameter, and attempts to receive the PUSCH based on the N _instances of uplink grants.

(3) A third aspect of the present invention is a communication method used in a terminal device communicating with a base station device, comprising: a step of delivering HARQ information included in a received PDCCH to the medium access control layer processing unit; a step of determining a number of PUSCH instances, N _instances , based on a number of PUSCH repetitions N and an external parameter provided from the base station device; a step of delivering the determined number to the medium access control layer processing unit; a step of acquiring one uplink grant from the PDCCH; a step of generating N _instances of uplink grants based on the one uplink grant; and a step of issuing N _instances of transmission instructions to the physical layer processing unit based on the N _instances of uplink grants.

(4) A fourth aspect of the present invention is a communication method used in a base station device, comprising the steps of: transmitting HARQ information on a PDCCH; determining a number N _instances of a PUSCH based on a number N of PUSCH repetitions and an external parameter; and attempting to receive the PUSCH based on the N _instances of uplink grants.

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

1 is a conceptual diagram of a wireless communication system according to an aspect of the present embodiment. 10 is an example showing the relationship between a subcarrier spacing setting μ, the number of OFDM symbols per slot N ^slot _symb , and a cyclic prefix (CP) setting according to one aspect of the present embodiment. FIG. 10 is a diagram illustrating an example of a method for configuring a resource grid according to an aspect of the present embodiment. FIG. 30 is a diagram illustrating an example of the configuration of a resource grid 3001 according to one aspect of the present embodiment. FIG. 2 is a schematic block diagram illustrating an example of the configuration of a base station device 3 according to one aspect of the present embodiment. 1 is a schematic block diagram illustrating an example of the configuration of a terminal device 1 according to an aspect of the present embodiment. A figure showing an example of the configuration of an SS/PBCH block related to one aspect of this embodiment. FIG. 10 is a diagram illustrating an example of a monitoring opportunity for a set of search areas according to one aspect of the present embodiment. FIG. 10 is a diagram illustrating an example of the configuration of a medium 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 one aspect of this embodiment. FIG. 10 is a diagram illustrating an example of a bit selection procedure according to one aspect of the present embodiment. FIG. 1 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 PUSCH according to one aspect of this embodiment. A figure showing an example of multi-slot transmission of a PUSCH according to one aspect of this embodiment.

The following describes an embodiment of the present invention.

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

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

At least one communication method may be used in the wireless communication system. The one communication method may be OFDM (Orthogonal Frequency Division Multiplex). For example, at least CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplex) may be used in the downlink, which is communication from the base station device 3 to the terminal device 1. Furthermore, at least one of CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplex) may be used in the uplink, which is communication from the terminal device 1 to the base station device 3. DFT-s-OFDM is a communication method in which modified precoding is applied prior to signal generation in CP-OFDM. Here, modified precoding is also referred to as 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 with multiple transmitting devices, the multiple transmitting devices may be located in different geographical locations, or may be located in the same geographical location. When multiple transmitting devices are located in 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 referred to as a cell.

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

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

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

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

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

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

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

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. An OFDM symbol may also be a unit of time domain for DFT-s-OFDM.

A slot may include a plurality of OFDM symbols. For example, N ^slot _symb consecutive OFDM symbols may be included in one slot. For example, N ^slot _symb =14.

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. Also, 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 resource grid configuration method according to one aspect of this embodiment. The horizontal axis in Fig. 3 represents the frequency domain. Fig. 3 shows an example of a resource grid configuration with subcarrier spacing setting _μ1 in a component carrier 300, and an example of a resource grid configuration with subcarrier spacing setting _μ2 in the certain component carrier. In this way, one or more subcarrier spacings may be configured for a certain component carrier.

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

Of the common resource block set 3100, the common resource block including point 3000 (the block indicated by the diagonal line slanting upward to the right 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 the offset from the reference point of resource grid 3001 to the reference point (N ^{start, μ} _BWP,i1 ) of BWP (BandWidth Part) 3003 with index i1. The reference point of BWP 3003 with index i1 is the physical resource block with index 0 for that BWP.

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

Of the common resource block set 3200, the common resource block including point 3000 (the block indicated by the diagonal line slanting downwards to the left in FIG. 3 ) is also referred to as the reference point of the common resource block set 3200. The reference point of the common resource block set 3200 is the common resource block with index 0 for the subcarrier spacing setting μ ₂ .

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

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

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

The frequency domain of the resource grid corresponds to an SCS-specific carrier. The SCS-specific carrier configuration includes an offset and some or all of a band configuration. The offset indicates the offset from the reference point of the common resource block set to the reference point of the resource grid. For example, offset 3011 and offset 3012 are offsets included in the SCS-specific carrier configuration. 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 SCS-specific carrier configuration.

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 a common resource block set for a certain subcarrier spacing setting μ, the common resource blocks are indexed in ascending order starting from 0 in the frequency domain. For a certain subcarrier spacing setting μ, the common resource block with index 0 includes (or collides with, or coincides with) point 3000. The index of the common resource block n ^μ _CRB for a certain subcarrier spacing setting μ satisfies the relationship n ^μ _CRB = ceil(k _sc,c /N ^RB _sc ), where the subcarrier with 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 a 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 the 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 include N size,μ _BWP,i common resource blocks starting from a reference point N ^{start ,μ} _BWP,i of the BWP. A BWP configured for the downlink is also referred to as a downlink BWP. A BWP configured for the uplink is also referred to as an uplink BWP.

An antenna port may be defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. For example, the channel may correspond to a physical channel. Alternatively, the symbols may correspond to modulation symbols mapped to resource elements.

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

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

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

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

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

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

The upper layer processing unit 34 outputs downlink data (e.g., transport blocks) 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 MAC (Medium Access Control) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and 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 the RRC parameters based on the RRC message received from the terminal device 1.

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

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

The wireless transceiver unit 30 (or the wireless 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 CP-removed signal to extract the frequency domain signal.

The baseband unit 33 performs an Inverse Fast Fourier Transform (IFFT) on the downlink data to generate OFDM symbols, adds a CP to the generated OFDM symbols, generates a baseband digital signal, and converts the baseband digital signal to an analog signal. The baseband unit 33 outputs the converted analog signal to the RF unit 32. Modified precoding may be applied to the downlink data prior to the IFFT.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Figure 6 is a schematic block diagram showing an example configuration of a terminal device 1 according to one aspect of this embodiment. As shown in Figure 6, the terminal device 1 includes at least a radio transceiver unit (physical layer processing unit) 10 and part or all of an upper layer processing unit 14. The radio transceiver unit 10 includes at least an antenna unit 11, an RF unit 12, and 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 unit 10 includes at least a wireless transmitter unit 10a and part or all of a wireless receiver unit 10b. Here, the baseband unit 13 included in the wireless transmitter unit 10a and the baseband unit 13 included in the wireless receiver unit 10b may have the same or different device configurations. Furthermore, the RF unit 12 included in the wireless transmitter unit 10a and the RF unit 12 included in the wireless receiver unit 10b may have the same or different device configurations. Furthermore, the antenna unit 11 included in the wireless transmitter unit 10a and the antenna unit 11 included in the wireless receiver unit 10b may have the same or different device configurations.

For example, the radio transmitter 10a may generate a baseband signal of an uplink physical channel. For example, the radio transmitter 10a may generate a baseband signal of an uplink physical signal.

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

The upper layer processing unit 14 outputs uplink data (e.g., transport blocks) 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, packet data integration protocol layer, radio link control layer, and RRC layer.

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

The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs RRC layer processing. 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 the RRC message received from the base station device 3.

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

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

The wireless transceiver unit 10 (wireless 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 CP-removed signal to extract the frequency domain signal.

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

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

The following explains physical signals (signals).

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

The uplink physical channel may correspond to a set of resource elements carrying information generated in a higher layer. The uplink physical channel may be a physical channel used in an uplink component carrier. The uplink physical channel may be transmitted by 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 used to transmit uplink control information (UCI). The PUCCH may be transmitted to deliver, transmit, or convey the uplink control information. The uplink control information may be mapped to the PUCCH. The terminal device 1 may transmit a PUCCH in which the uplink control information is mapped. The base station device 3 may receive a PUCCH in which the uplink control information is mapped.

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

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

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

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

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

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

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

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

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

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

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

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

The uplink physical signal may correspond to a set of resource elements. The uplink physical signal may not carry information generated in a higher layer. The uplink physical signal may be a physical signal used in an uplink component carrier. The terminal device 1 may transmit the uplink physical signal. The base station device 3 may receive the uplink physical signal. In 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 DMRS for PUSCH (DMRS associated with PUSCH, DMRS included in PUSCH, DMRS corresponding to PUSCH) may be determined based on the set of antenna ports for the PUSCH. In other words, the set of antenna ports for DMRS for PUSCH may be the same as the set of antenna ports for the PUSCH.

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

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

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

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

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

The downlink physical channel may correspond to a set of resource elements carrying information generated in a higher layer. The downlink physical channel may be a physical channel used in a downlink component carrier. The base station device 3 may transmit the downlink physical channel. The terminal device 1 may receive the downlink physical channel. In 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 used to transmit a Master Information Block (MIB) and/or physical layer control information. The PBCH may be transmitted to deliver, transmit, or convey the MIB and/or physical layer control information. The BCH may be mapped to the PBCH. The terminal device 1 may receive a PBCH in which the MIB and/or physical layer control information is mapped. The base station device 3 may transmit a PBCH in which the MIB and/or physical layer control information is mapped. The physical layer control information is also called a PBCH payload or a PBCH payload related to timing. The MIB may include one or more higher layer parameters.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The downlink physical signal may correspond to a set of resource elements. The downlink physical signal may not carry information generated in a higher layer. The downlink physical signal may be a physical signal used in a downlink component carrier. The downlink physical signal may be transmitted by a base station device 3. The downlink physical signal may be transmitted by a terminal device 1. In 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 at least by the terminal device 1 to synchronize the frequency domain and/or time domain of the downlink. The synchronization signal is a general term for the PSS (Primary Synchronization Signal) and the SSS (Secondary Synchronization Signal).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The uplink grant is managed by the medium 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 a HARQ entity included in the medium access control layer processing unit 15.

Figure 9 is a diagram showing an example configuration of the medium access control layer processing unit 15 according to one aspect of this embodiment. In Figure 9, the medium 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 via 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 via 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 some or all of the HARQ process number corresponding to the uplink grant, the new data indicator (NDI) corresponding to the uplink grant, and the 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, based on the new data indicator corresponding to the uplink grant, whether a transmission instruction to the physical layer processing unit 10 based on the uplink grant corresponds to a retransmission. For example, if a transmission instruction to the physical layer processing unit 10 based on the uplink grant does not correspond to a retransmission, the transmission instruction may correspond to an initial transmission. For example, the HARQ entity 9000 may determine, based on the new data indicator corresponding to the uplink grant, whether to acquire a MAC PDU for 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 may not 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 assigned with 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 assigned with the HARQ process number corresponding to the uplink grant.

The HARQ process may issue a transmission instruction to the physical layer processing unit 10 based on the received uplink grant and HARQ information. Furthermore, when the HARQ process receives a MAC PDU from the HARQ entity 9000, it 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.

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

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

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

The encoding unit 12003 may apply error correction coding to the code block r. For example, the error correction coding method may be a Quasi-Cyclic Low Density Parity Check (QC-LDPC) code. Here, the code block index r may be any integer value between 0 and 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 perform a bit selection procedure, in which the coded bit sequence d ^r is input to a circular buffer of size N _cb .

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 each set to 0. Next, in step 1, it is determined whether the value of variable k is smaller than the rate matching output sequence length E _r . If the value of 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 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 at least on the modulation order Q _m of the PUSCH, the number of layers L _v of the PUSCH, the number C of code blocks, and the value G. For example, the rate matching output sequence length E _r may be determined by either E _r = N _v Q _m · floor(G/(N _v Q _m C)) or E _r = N _v Q _m · ceil(G/(N _v Q _m C)).

Here, the value G indicates the number of bits included in a PUSCH instance and available for UL-SCH transmission. A PUSCH instance is also referred to as a PUSCH transmission occasion. Furthermore, 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) indicates 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 circular buffer for reading, 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 indicates the termination point for step 2.

In step 6, the value of j is incremented.

Step 7 indicates the termination point for step 1.

12 is a diagram illustrating the concept of a circular buffer according to one aspect of this 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 to the circular buffer may be read out starting from the start position k _0. The read E _r bits are input to a rate matching output sequence e. Here, the start position k ₀ may be determined based on the RV value indicated by the DCI format used for PUSCH scheduling.

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 code block may be combined to generate a single sequence g. Furthermore, if multiple code blocks are not generated, a single rate matching output sequence may be considered as a single sequence g. A single sequence g may be input to the multiplexing unit 12005.

In the multiplexing unit 12005, one sequence g and control data (e.g., HARQ-ACK, CSI, etc.) may be multiplexed. For example, the multiplexing unit 12005 may generate an array Q. Each element of the array Q may be identified based on at least some or all of a subcarrier-related index k' _sc , an OFDM symbol-related index l', and an index m' based on a modulation order and the number of layers. Here, the subcarrier-related index k' _sc may be an index related to a subcarrier to which an instance of PUSCH is assigned. Furthermore, the OFDM symbol-related index l' may be an index m' related to an OFDM symbol to which an instance of PUSCH is assigned. Furthermore, the index based on the modulation order and the 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, the element of array Q with index _k'sc = _kx , index l' = _lx , and index m' = _mx is called Q( _kx , _lx , _mx ).

When the multiplexing unit 12005 arranges the coded bit sequence q of HARQ-ACK in the array Q, the multiplexing unit 12005 may specify a start position l _start . Once 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 has finished in the element of the array at l=l _start , the arrangement may proceed to the element of the array at 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 allocated to the PUSCH instance. For example, if the first DMRS in the PUSCH instance is allocated to the second OFDM symbol, l _start may be 2. Here, the index l′ starts 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 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 is generated for each slot and may be 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 by the RRC layer. Furthermore, R may be indicated by the PDCCH that provides the uplink grant that triggers the repeated transmission of the PUSCH.

In repeated transmissions of the PUSCH, the HARQ entity may deliver 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 PUSH, the HARQ process may issue N transmission instructions to the physical layer processing unit 10 based on N uplink grants.

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

It may also be determined whether at least some of the OFDM symbols in the set of OFDM symbols on 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 on which a PUSCH instance is transmitted belong to the downlink region, transmission of the instance may be omitted.

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

Figure 13 is a diagram showing an example of multi-slot transmission of a 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, slot indices are set in ascending order to the right, with the first slot in the diagram being slot #n.

In the multi-slot transmission shown in Figure 13, the number of PUSCH repetitions N is set to 8, and 8 slots of time resources are used in the multi-slot transmission. Meanwhile, each of PUSCH instances 13001, 13002, and 13003 is composed of time resources of multiple slots. That is, in the multi-slot transmission of the PUSCH, the format 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 _instances 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 ). Furthermore, 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 the PUSCH instance may be indicated by a _parameter provided by the RRC layer, or may be provided by the PDCCH.

The HARQ entity 9000 may issue uplink grants 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. Furthermore, 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 PUSH instance for each HARQ process transmission instruction.

Figure 14 is a diagram showing an example of multi-slot transmission of a PUSCH according to one aspect of this embodiment. In Figure 14, the horizontal axis is the time axis, and each grid on the time axis is a slot boundary. The slot indices are set in ascending order to the right, with the first slot in the figure being slot #n. Each of 14001 to 14008 indicates a time resource set for multi-slot transmission of a PUSCH. In Figure 14, the number of repetitions is set to N = 8, and time resources are set for slots #n to #n+7. In the example shown in Figure 14, the PUSCH instance for multi-slot transmission may be determined based on the number of repetitions N and the TDD pattern setting. Here, in Figure 14, the time resources corresponding to the black boxes indicate the downlink region, and the time resources corresponding to the white boxes indicate the uplink region. In the example shown in Figure 14, the PUSCH instance may be composed of consecutive 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 by a set of time resources corresponding to one temporally continuous uplink region 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 multi-slot transmission is applied. For example, if the external parameter indicates the application of multi-slot transmission, time resources corresponding to N repetitions may be aggregated to generate one PUSCH instance, and the number of PUSCH instances N _instance may be 1. Also, if the external parameter does not indicate the application of multi-slot transmission, N PUSCH instances may be generated, and the number N of PUSCH repetitions may be reported to the medium 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, if the external parameters indicate the application of multi-slot transmission, the configuration of the PUSCH instances may be determined based on the TDD pattern settings. Also, if the external parameters indicate the application of multi-slot transmission, the number of PUSCH instances may be determined based on the TDD pattern settings.

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, a parameter indicating whether multi-slot transmission is applied may be provided by a TDRA field included in a DCI format used for scheduling a PUSCH. For example, each column of the table corresponding to the TDRA field may indicate the time resource of the PUSCH and the parameter.

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 for collision with PUCCH may be performed for each PUSCH instance. For example, if a PUSCH instance collides with PUCCH, the UCI that was scheduled to be transmitted on PUCCH may be multiplexed onto that 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 may be multiplexed onto the certain PUSCH instance. Here, the multiplexing unit 12005 may multiplex the coded bit sequence q with one sequence g that was scheduled to be transmitted in the certain PUSCH instance. Here, the coded bit sequence q may specify a start position l _start based on the OFDM symbol next to the OFDM symbol containing the first DMRS of the instance.

For example, to specify the start position l _start , the first DMRS in the slot into which the PUCCH is multiplexed may be specified. For example, if instances of a certain PUSCH are 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 OFDM symbol next to the OFDM symbol including the first DMRS.

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

(1) In order to achieve the above object, the present invention provides the following measures. That is, a first aspect of the present invention is a terminal device that communicates with a base station device, the terminal device comprising: a physical layer processing unit and a medium access control layer processing unit; the physical layer processing unit delivers HARQ information included in a received PDCCH to the medium access control layer processing unit; the physical layer processing unit determines a number of PUSCH instances N _instances based on a number of PUSCH repetitions N and an external parameter provided from the base station device; the determined number is delivered to the medium access control layer processing unit; the medium access control layer processing unit obtains one uplink grant from the PDCCH; the medium access control layer processing unit further comprises a HARQ entity and a HARQ process; the HARQ entity generates N _instances of uplink grants based on the one uplink grant; and the HARQ process issues N _instances of transmission instructions to the physical layer processing unit based on the N _instances of uplink grants.

(2) Also, a second aspect of the present invention is a base station device comprising a physical layer processing unit and a medium access control layer processing unit, wherein the physical layer processing unit transmits HARQ information on a PDCCH, and the physical layer processing unit determines a number N _instances of a PUSCH based on a number N of PUSCH repetitions and an external parameter, and attempts to receive the PUSCH based on the N _instances of uplink grants.

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

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

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

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

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

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

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

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

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

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

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

Claims (3)

A terminal device that communicates with a base station device,
A physical layer processing unit and a medium access control layer processing unit are provided,
The physical layer processing unit delivers HARQ information included in the received PDCCH to the medium access control layer processing unit;
The physical layer processing unit determines the number N _instances of PUSCH based on the number N of repetitions of PUSCH provided from the base station device and external parameters;
the determined number is delivered to the medium access control layer processing unit;
The medium access control layer processing unit obtains one uplink grant from the PDCCH;
the medium access control layer processing unit further comprises a HARQ entity and a HARQ process;
The HARQ entity generates N _instances of uplink grants based on the one uplink grant;
The HARQ process issues N _instances of transmission instructions to the physical layer processing unit based on the N _instances of uplink grants. A physical layer processing unit and a medium access control layer processing unit are provided,
The physical layer processing unit transmits HARQ information on a PDCCH;
The physical layer processing unit determines the number N _instances of the PUSCH based on the number N of repetitions of the PUSCH and external parameters;
A base station device that attempts to receive the PUSCH based on the N _instances of uplink grants. A communication method used in a base station device,
transmitting HARQ information on a PDCCH;
Determining the number of instances of the PUSCH (N _instance) based on the number of repetitions of the PUSCH (N) and external parameters;
and attempting to receive the PUSCH based on the N _instances of uplink grants.