WO2022230451A1

WO2022230451A1 - Terminal device, base station device, and communication method

Info

Publication number: WO2022230451A1
Application number: PCT/JP2022/012979
Authority: WO
Inventors: 友樹吉村; 智造野上; 崇久福井; 翔一鈴木; 大一郎中嶋; 渉大内; 会発林
Original assignee: シャープ株式会社
Priority date: 2021-04-27
Filing date: 2022-03-22
Publication date: 2022-11-03
Also published as: JPWO2022230451A1

Abstract

A terminal device comprising a physical layer processing unit and a media access control layer processing unit. The physical layer processing unit delivers HARQ information included in a received PDCCH to the media access control layer processing unit. The physical layer processing unit, on the basis of a PUSCH repetition number N provided from the base station device and an external parameter, determines the number of instances of PUSCH Ninstance. The determined number is delivered to the media access control layer processing unit. The media access control layer processing unit acquires one uplink grant from the PDCCH. The media access control layer processing unit further comprises a HARQ entity and a HARQ process. The HARQ entity generates Ninstance uplink grants based on the one uplink grant. The HARQ process, on the basis of the Ninstance uplink grants, sends Ninstance transmission instructions to the physical layer processing unit.

Description

TERMINAL DEVICE, BASE STATION DEVICE, AND COMMUNICATION METHOD

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 in Japan on April 27, 2021, the content of which is incorporated herein.

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

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

It is expected that functional expansion of cellular mobile communications such as NR will be considered. For example, as shown in Non-Patent Document 2, studies on extending the function of NR have been started.

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, comprising: a physical layer processing unit and a medium access control layer processing unit; The HARQ information received is delivered to the medium access control layer processing unit, and the physical layer processing unit determines the number of PUSCH instances N _instance based on the PUSCH repetition count N and external parameters provided from the base station device. and 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, and the medium access control layer processing unit further A HARQ entity and a HARQ process, wherein the HARQ entity generates N _instances of uplink grants based on the one uplink grant, and the HARQ processes generate N _instances of uplink grants based on the N _instances of the uplink grants. to the physical layer processing unit.

(2) A second aspect of the present invention is a base station apparatus comprising a physical layer processing unit and a medium access control layer processing unit, the physical layer processing unit transmitting HARQ information on a PDCCH, The layer processing unit determines the number of PUSCH instances N _instance based on the PUSCH repetition count N and external parameters, and attempts to receive the PUSCH based on the N _instance uplink grants.

(3) A third aspect of the present invention is a communication method used in a terminal device that communicates 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; determining the number of PUSCH instances N _instance based on the PUSCH repetition count N and external parameters provided from the base station apparatus; and delivering the determined number to the medium access control layer processing unit. and obtaining one uplink grant from the PDCCH; generating N _instance uplink grants based on the one uplink grant; and N _instance times based on the N _instance uplink grants. and a step of instructing the physical layer processing unit to transmit the

(4) A fourth aspect of the present invention is a communication method used in a base station apparatus, comprising: a step of transmitting HARQ information on a PDCCH; determining N _instance ; and attempting to receive the PUSCH based on the N _instance uplink grants.

According to one aspect of the present invention, the terminal device can communicate efficiently. Also, the base station apparatus can communicate efficiently.

1 is a conceptual diagram of a wireless communication system according to one aspect of the present embodiment; FIG. 7 is an example showing the relationship between subcarrier spacing setting μ, the number of OFDM symbols per slot N ^slot _symb , and CP (cyclic prefix) setting according to one aspect of the present embodiment. It is a figure which shows an example of the configuration method of the resource grid based on one aspect|mode of this embodiment. It is a figure which shows the structural example of the resource grid 3001 which concerns on one aspect|mode of this embodiment. 1 is a schematic block diagram showing a configuration example of a base station device 3 according to one aspect of the present embodiment; FIG. 1 is a schematic block diagram showing a configuration example of a terminal device 1 according to one aspect of the present embodiment; FIG. FIG. 4 is a diagram illustrating a configuration example of an SS/PBCH block according to one aspect of the present embodiment; FIG. 4 illustrates an example of a search area set monitoring opportunity according to an aspect of the present embodiments; It is a figure which shows the structural example of the medium access control layer process part 15 which concerns on one aspect|mode of this embodiment. FIG. 3 is a diagram showing a configuration example of an encoding processor unit 12000 according to one aspect of the present embodiment; FIG. 10 is a diagram illustrating an example bit selection procedure according to one aspect of the present embodiment; FIG. 3 is a diagram illustrating the concept of a circular buffer according to one aspect of the present embodiments; FIG. 4 is a diagram illustrating an example of PUSCH multi-slot transmission according to an aspect of the present embodiment; FIG. 4 is a diagram illustrating an example of PUSCH multi-slot transmission according to an aspect of the present embodiment;

Embodiments of the present invention will be described below.

　floor(C) may be a floor function for the real number C. For example, floor(C) may be a function that outputs the largest integer that does not exceed the real number C. ceil(D) may be the ceiling function for real D. For example, ceil(D) may be a function that outputs the smallest integer in the range not less than the real number D. mod(E,F) may be a function that outputs the remainder of dividing E by F. mod(E,F) may be a function that outputs a value corresponding to the remainder of E divided by F. exp(G)=e^G. where e is the Napier number. ĤI indicates H raised to the I power. max(J,K) is a function that outputs the maximum 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, min(L,M) is a function that outputs L or M when L and M are equal. round(N) is a function that outputs the integer value closest to N.

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

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

The base station device 3 may be configured including one or more transmission devices (or transmission points, transmission/reception devices, transmission/reception points). When the base station apparatus 3 is composed of a plurality of transmitters, the plurality of transmitters may be located at geographically different locations, or may be located at the same geographical location. Arranging a plurality of transmission devices at the same geographical location may mean that the plurality of transmission devices are configured as one device.

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

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 called component carriers.

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

N ^{size, μ} _{grid, x} and N ^{start, μ} _{grid, x} are given based on at least the upper layer parameter (CarrierBandwidth). The higher layer parameters are also called SCS specific carrier. One resource grid corresponds to one SCS-specific carrier. One component carrier may comprise one or more SCS-specific carriers. The SCS specific carrier may be included in system information. For each SCS unique carrier, one subcarrier spacing setting μ may be given.

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

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

In the wireless communication system according to one aspect of the present embodiment, a time unit (time unit) _Tc may be used to express the length of the time domain. The time unit T _c is T _c =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 . T _f =(Δf _max N _f /100)·T _s =10 ms. “·” indicates multiplication. A radio frame includes 10 subframes. The subframe length T _sf =(Δf _max N _f /1000)·T _s =1 ms. The number of OFDM symbols per subframe is N ^{subframe, μ} _symb =N ^slot _symb N ^{subframe, μ} _slot .

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

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

Slots may be indexed in the time domain. For example, the slot index n ^μ _s may be given in ascending order by integer values ranging from 0 to N ^{subframe, μ} _slot −1 in subframes. Also, the slot indices n ^μ _s,f may be given in ascending order by integer values ranging from 0 to N ^frame,μ _slot −1 in the radio frame.

FIG. 3 is a diagram illustrating an example of a resource grid configuration method according to one aspect of the present embodiment. The horizontal axis of FIG. 3 indicates the frequency domain. _FIG . 3 shows a configuration example of a resource grid with a subcarrier interval setting μ1 in a component carrier 300 and _a resource grid configuration example with a subcarrier interval setting μ2 in a certain component carrier. In this way, one or more subcarrier intervals may be set for a given component carrier.

Point 3000 is an identifier for specifying a certain subcarrier. Point 3000 is also called point A. A common resource block (CRB) set 3100 is a set of common resource blocks for _a subcarrier spacing setting μ1.

Of the common resource block set 3100 , the common resource block including the point 3000 (the block indicated by the upward slanting lines in FIG. 3 ) is also called the reference point of the common resource block set 3100 . The reference point for common resource block set 3100 is the common resource block with index ₀ for subcarrier spacing setting μ1.

Offset 3011 is the offset from the reference point of common resource block set 3100 to the reference point of 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 .

An offset 3013 is the offset from the reference point of the resource grid 3001 to the reference point (N ^{start, μ} _{BWP, i1} ) of the BWP (BandWidth Part) 3003 of 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 _μ2 .

Of the common resource block set 3200 , the common resource block including the point 3000 (the block indicated by the diagonal lines rising to the left in FIG. 3 ) is also called the reference point of the common resource block set 3200 . The reference point for common resource block set 3200 is the common resource block with index ₀ for subcarrier spacing setting μ2.

Offset 3012 is the offset from the reference point of common resource block set 3200 to the reference point of resource grid 3002 . The offset 3012 is indicated by the _number of common resource blocks for 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. The reference point of the BWP 3004 with index i2 is the physical resource block with index 0 for that BWP.

FIG. 4 is a diagram illustrating a configuration example of a resource grid 3001 according to one aspect of the present embodiment. In the resource grid of FIG. 4, the horizontal axis is the OFDM symbol index l _sym and the vertical axis is the subcarrier index k _sc . The resource grid 3001 includes N ^{size, μ} _{grid1, x} N ^RB _sc subcarriers and includes at least N ^{subframe, μ} _symb OFDM symbols. Within the resource grid, the resource identified by the subcarrier index k _sc and OFDM symbol index l _sym is also called a resource element (RE).

A frequency region of the resource grid corresponds to an SCS-specific carrier. The setting of the SCS-specific carrier is configured including part or all of the offset and band setting. 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 configuration of SCS specific carriers. Also, the band setting 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 the band configurations included in the SCS-specific carrier configuration.

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

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

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

A BWP may be configured as part of a component carrier frequency band. 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 the reference point N ^start,μ _BWP,i of the BWP. A BWP set for the downlink is also called a downlink BWP. A BWP configured for the uplink is also called an uplink BWP.

Antenna ports may be defined by the fact that the channel over which symbols at one antenna port are conveyed can be estimated from the channels over which other symbols at that antenna port are conveyed. a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed). For example, a channel may correspond to a physical channel. A symbol may also correspond to a modulation symbol that is placed on a resource element.

Two antenna ports are Quasi Co-Located (QCL) if the large scale property of the channel over which the symbols are conveyed at one antenna port can be estimated from the channel over which the symbols are conveyed at the other antenna port. ) are considered to be in a relationship. Large-scale characteristics may include at least long-term characteristics of the channel. Large-scale properties are delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. It may include at least part or all. A first antenna port and a second antenna port are QCL with respect to beam parameters if the receive beam expected by the receiver for the first antenna port and the receive beam expected by the receiver for the second antenna port and may be the same. A first antenna port and a second antenna port are QCL with respect to beam parameters if the transmit beam expected by the receiver for the first antenna port and the transmit beam expected by the receiver for the second antenna port and may be the same. The terminal device 1 assumes that the two antenna ports are QCL when the large-scale characteristics of the channel through which the symbols are transmitted at one antenna port can be estimated from the channel through which the symbols are transmitted at another antenna port. may be Two antenna ports being QCL may be assumed to be two antenna ports being QCL.

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

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

The wireless transmission/reception unit 30 includes at least part or all of the wireless transmission unit 30a and the wireless reception unit 30b. Here, the device configurations of the baseband unit included in the radio transmission unit 30a and the baseband unit included in the radio reception unit 30b may be the same or different. Further, the device configuration of the RF unit included in the wireless transmission unit 30a and the RF unit included in the wireless reception unit 30b may be the same or different. Further, the device configuration of the antenna unit included in the wireless transmission unit 30a and the antenna unit included in the wireless reception unit 30b may be the same or may be different.

For example, the radio transmission unit 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 receiving unit 30b may attempt to detect information transmitted by an uplink physical channel. For example, the radio receiver 30b may attempt to detect information conveyed by uplink physical signals.

The upper layer processing unit 34 outputs downlink data (for example, transport blocks) to the radio transmission/reception unit 30 (or the radio transmission unit 30a). The upper layer processing unit 34 performs part or all of the processing of the MAC (Medium Access Control) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the RRC layer. do

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

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

The radio transmission/reception unit 30 (or radio transmission unit 30a) performs part or all of modulation processing, encoding processing, and transmission processing. The radio transmitting/receiving unit 30 (or radio transmitting unit 30a) generates a physical signal by part or all of modulation processing, coding processing, and baseband signal generation (conversion to time-continuous signal) processing for downlink data. do. The radio transmitting/receiving unit 30 (or radio transmitting unit 30a) may allocate the physical signal to a certain component carrier. The radio transmission/reception unit 30 (or radio transmission unit 30a) transmits the generated physical signal.

The radio transmitting/receiving section 30 (or radio receiving section 30b) performs part or all of demodulation processing, decoding processing, and reception processing. The radio transmitting/receiving unit 30 (or the radio receiving unit 30b) outputs information detected based on at least demodulation processing and decoding processing on the received physical signal to the upper layer processing unit 34. FIG.

The radio transmitting/receiving section 30 (or the radio receiving section 30b) may perform carrier sense prior to transmission of the physical signal.

The RF unit 32 converts the signal received via the antenna unit 31 into a baseband signal by orthogonal demodulation, and removes unnecessary frequency components. The RF section 32 outputs analog signals to the baseband section.

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 CP (Cyclic Prefix) from the converted digital signal, performs Fast Fourier Transform (FFT) on the CP-removed signal, and converts the signal in the frequency domain. Extract.

The baseband unit 33 performs an inverse fast Fourier transform (IFFT) on the downlink data, generates an OFDM symbol, adds a CP to the generated OFDM symbol, generates a baseband digital signal, Converts baseband digital signals to analog signals. The baseband section 33 outputs the converted analog signal to the RF section 32 . Modified precoding may be applied to the downlink data prior to the inverse fast Fourier transform.

The RF unit 32 uses a low-pass filter to remove excess frequency components from the analog signal input from the baseband unit 33, up-converts the analog signal to a carrier frequency, and transmits the signal through the antenna unit 31. do. Also, the RF unit 32 may have a function of controlling transmission power. The RF section 32 is also called a transmission power control section.

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

Each of the serving cells configured for the terminal device 1 is either PCell (Primary cell, primary cell), PSCell (Primary SCG cell, primary SCG cell), and SCell (Secondary Cell, secondary cell) good too.

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

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

SCell may be included in either MCG or SCG.

A serving cell group (cell group) is a name 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 the one or more downlink BWPs configured for the serving cell (or downlink component carrier), one downlink BWP may be configured as an active downlink BWP (or one downlink BWP may may be activated). Of the one or more uplink BWPs set for the serving cell (or uplink component carrier), one uplink BWP may be set to the active uplink BWP (or one uplink BWP may be may be activated).

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

PDSCH, PDCCH, and CSI-RS may not be received in downlink BWPs other than active downlink BWPs (inactive downlink BWPs). The terminal device 1 may not receive the PDSCH, PDCCH, and CSI-RS in downlink BWPs other than the active downlink BWP. PUCCH and PUSCH may not be transmitted in uplink BWPs other than active uplink BWPs (inactive uplink BWPs). The terminal device 1 may not transmit PUCCH and PUSCH in uplink BWPs other than the active uplink BWP. Inactive downlink BWP and inactive uplink BWP are also called inactive BWP.

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

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

Of the one or more downlink BWPs configured for the 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 a time.

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

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

The wireless transmission/reception unit 10 includes at least part or all of the wireless transmission unit 10a and the wireless reception unit 10b. Here, the device configurations of the baseband unit 13 included in the radio transmission unit 10a and the baseband unit 13 included in the radio reception unit 10b may be the same or different. Further, the device configuration of the RF unit 12 included in the wireless transmission unit 10a and the RF unit 12 included in the wireless reception unit 10b may be the same or different. Further, the device configuration of the antenna section 11 included in the radio transmission section 10a and the device configuration of the antenna section 11 included in the radio reception section 10b may be the same or different.

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

For example, the radio receiving unit 10b may attempt to detect information transmitted by the downlink physical channel. For example, the radio receiver 10b may attempt to detect information transmitted by uplink physical signals.

The upper layer processing unit 14 outputs the uplink data (eg, transport block) to the radio transmission/reception unit 10 (or the radio transmission unit 10a). The upper layer processing unit 14 performs part or all of the processing of the MAC layer, packet data integration protocol layer, radio link control layer, and RRC layer.

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

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

The radio transmission/reception unit 10 (or radio transmission unit 10a) performs part or all of modulation processing, encoding processing, and transmission processing. The radio transmitting/receiving unit 10 (or radio transmitting unit 10a) generates a physical signal by part or all of modulation processing, coding processing, and baseband signal generation (conversion to time-continuous signal) processing for uplink data. do. The radio transmitting/receiving unit 10 (or the radio transmitting unit 10a) may arrange physical signals in a certain BWP (active uplink BWP). The radio transmission/reception unit 10 (or radio transmission unit 10a) transmits the generated physical signal.

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

The radio transmitting/receiving section 10 (radio receiving section 10b) may perform carrier sense prior to transmission of the physical signal.

The RF section 12 converts the signal received via the antenna section 11 into a baseband signal by orthogonal demodulation, and removes unnecessary frequency components. The RF section 12 outputs the processed analog signal to the baseband section 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 CP (Cyclic Prefix) from the converted digital signal, performs Fast Fourier Transform (FFT) on the CP-removed signal, and converts the signal in the frequency domain. Extract.

The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the uplink data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a baseband digital signal, Converts baseband digital signals to analog signals. The baseband section 13 outputs the converted analog signal to the RF section 12 . Modified precoding may be applied to the uplink data prior to the inverse fast Fourier transform.

The RF unit 12 uses a low-pass filter to remove excess frequency components from the analog signal input from the baseband unit 13, up-converts the analog signal to a carrier frequency, and transmits the signal through the antenna unit 11. do. Also, the RF unit 12 may have a function of controlling transmission power. The RF section 12 is also called a transmission power control section.

The physical signal (signal) will be explained below.

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

An uplink physical channel may correspond to a set of resource elements that carry information originating in higher layers. An uplink physical channel may be a physical channel used in an uplink component carrier. An uplink physical channel may be transmitted by the terminal device 1 . An uplink physical channel may be received by the base station device 3 . In the uplink of the radio 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)

PUCCH may be used to transmit uplink control information (UCI: Uplink Control Information). PUCCH may be transmitted to deliver, transmit, and convey uplink control information. The uplink control information may be mapped onto the PUCCH. The terminal device 1 may transmit PUCCH on which uplink control information is arranged. The base station apparatus 3 may receive PUCCH in which uplink control information is arranged.

Uplink control information (uplink control information bit, uplink control information sequence, uplink control information type) includes channel state information (CSI: Channel State Information), scheduling request (SR: Scheduling Request), HARQ-ACK (Hybrid including at least some or all of the Automatic Repeat request ACKnowledgement information.

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

HARQ-ACK information is transport block (or 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). HARQ-ACK may indicate ACK (acknowledgment) or NACK (negative-acknowledgement) corresponding to the transport block. The ACK may indicate that decoding of the transport block has been successfully completed (has been decoded). A NACK may indicate that decoding of the transport block has not been successfully completed (has not been decoded). The HARQ-ACK information may include a HARQ-ACK codebook containing one or more HARQ-ACK bits.

Correspondence between the HARQ-ACK information and the transport block may mean that the HARQ-ACK information corresponds to the PDSCH used to transmit the transport block.

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

A scheduling request may be used at least to request PUSCH (or UL-SCH) resources for a new transmission. The scheduling request bit may be used to indicate either positive SR or negative SR. The Scheduling Request bit indicating a positive SR is also referred to as "positive SR sent". A positive SR may indicate that PUSCH (or UL-SCH) resources for initial transmission are requested by the terminal device 1 . A positive SR may indicate that the scheduling request is triggered by higher layers. A positive SR may be sent when higher layers indicate to send a scheduling request. The Scheduling Request bit indicating negative SR is also referred to as "negative SR is sent". A negative SR may indicate that no PUSCH (or UL-SCH) resource is requested for the initial transmission by the terminal device 1 . 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 indicated to be sent by higher layers.

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

The channel state information may be provided at least based on receiving physical signals (eg, CSI-RS) that are used at least for channel measurements. The channel state information may be selected by the terminal device 1 based at least on receiving physical signals that are used at least for channel measurements. Channel measurements may include interference measurements.

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

PUSCH may be used to transmit transport blocks and/or uplink control information. PUSCH may be used to transmit transport blocks corresponding to UL-SCH and/or uplink control information. PUSCH may be used to convey transport blocks and/or uplink control information. PUSCH may be used to convey transport blocks corresponding to UL-SCH and/or uplink control information. A transport block may be placed on the PUSCH. A transport block corresponding to the UL-SCH may be placed on the PUSCH. Uplink control information may be placed on the PUSCH. The terminal device 1 may transmit PUSCH in which transport blocks and/or uplink control information are arranged. The base station apparatus 3 may receive PUSCH in which transport blocks and/or uplink control information are arranged.

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

64 random access preambles are defined for a given PRACH opportunity. A random access preamble is identified (determined, given) based at least on the cyclic shift C _v of the PRACH sequence and the sequence index u for the PRACH sequence. Each of the 64 identified random access preambles may be indexed.

An uplink physical signal may correspond to a set of resource elements. Uplink physical signals may not carry information originating in higher layers. The uplink physical signal may be a physical signal used in an uplink component carrier. The terminal device 1 may transmit an uplink physical signal. The base station device 3 may receive an uplink physical signal. In the uplink of the radio 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 generic term for DMRS for PUSCH and DMRS for PUCCH.

A set of antenna ports for DMRS for PUSCH (DMRS related to PUSCH, DMRS included in PUSCH, DMRS corresponding to PUSCH) may be given based on the set of antenna ports for the PUSCH. That is, the set of DMRS antenna ports for the PUSCH may be the same as the set of antenna ports for the PUSCH.

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

A PUSCH may be estimated from DMRS for the PUSCH. That is, the PUSCH propagation path may be estimated from the DMRS for the PUSCH.

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

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

A PUCCH may be estimated from DMRS for the PUCCH. That is, the PUCCH propagation path may be estimated from the DMRS for the PUCCH.

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

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

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

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

The SS/PBCH block index bit is used to indicate the SS/PBCH block index. The SS/PBCH block index bits contain 3 bits. The SS/PBCH block index bits may consist of 3 bits of the 6-bit SS/PBCH block index indicator. The SS/PBCH block index indicator may be used at least to identify the SS/PBCH blocks from index 0 to index 63.

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

The PDCCH may be used to transmit downlink control information (DCI: Downlink Control Information). The PDCCH may be transmitted to deliver, transmit, and convey downlink control information. Downlink control information may be mapped to the PDCCH. The terminal device 1 may receive the PDCCH in which the downlink control information is arranged. The base station apparatus 3 may transmit PDCCH in which downlink control information is arranged.

The downlink control information may correspond to the DCI format. Downlink control information may be included in the DCI format. 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 each including a different set of fields. The uplink DCI format is a general term for DCI format 0_0 and DCI format 0_1. A 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 PUSCH of a certain cell (or arranged in a certain cell). DCI format 0_0 includes at least some or all of the 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 (MCS field: Modulation and Coding Scheme field)

The DCI format specific field may indicate whether the DCI format including the DCI format specific field is an uplink DCI format or a downlink DCI format. A DCI format specific 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 frequency resource allocation for PUSCH.

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

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

The MCS field included in DCI format 0_0 may be used at least to indicate part or all of the modulation scheme for PUSCH and/or the target coding rate. The target code rate may be the target code rate for transport blocks of PUSCH. A Transport Block Size (TBS) for the PUSCH may be given based at least on the target coding rate and part or all of the modulation scheme for the PUSCH.

DCI format 0_0 may not include fields used for CSI requests (CSI requests). That is, CSI may not be required by DCI format 0_0.

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

　DCI format 0_0 may not include the BWP field. That is, the uplink BWP in which the PUSCH scheduled by the DCI format 0_0 is arranged may be the same as the downlink BWP in which the PDCCH including the DCI format 0_0 is arranged.

DCI format 0_1 is used at least for scheduling PUSCH of a certain cell (located in a certain cell). DCI format 0_1 includes at least some or all of the fields 2A to 2H.
2A) DCI format identification 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 at least be used to indicate frequency resource allocation for PUSCH.

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

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

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

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

When DCI format 0_1 includes a carrier indicator field, the carrier indicator field may be used to indicate the uplink component carrier on which PUSCH is arranged. When DCI format 0_1 does not include a carrier indicator field, the uplink component carrier on which PUSCH is mapped is the same as the uplink component carrier on which PDCCH including DCI format 0_1 used for scheduling the PUSCH is mapped. good too. When the number of uplink component carriers configured in the terminal device 1 in a certain serving cell group is 2 or more (when uplink carrier aggregation is operated in a certain serving cell group), PUSCH arranged in the certain serving cell group. The number of bits of the carrier indicator field included in DCI format 0_1 used for scheduling may be 1 bit or more (eg, 3 bits). When the number of uplink component carriers configured in the terminal device 1 in a certain serving cell group is 1 (when uplink carrier aggregation is not operated in a certain serving cell group), scheduling of PUSCH arranged in the certain serving cell group The number of bits of the carrier indicator field included in the used DCI format 0_1 may be 0 bits (or the carrier indicator field is included in the DCI format 0_1 used for scheduling of the PUSCH arranged in the serving cell group. may be omitted).

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

A 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 at least be used to indicate frequency resource allocation for the PDSCH.

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

The MCS field included in DCI format 1_0 may be used at least to indicate part or all of the modulation scheme for PDSCH and/or the target coding rate. The target code rate may be a target code rate for a PDSCH transport block. A Transport Block Size (TBS) for the PDSCH may be given based at least on the target coding rate and part or all of 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 PDSCH to the slot containing the first OFDM symbol of PUCCH.

The PUCCH resource indication field may be a field that indicates the index of one or more PUCCH resources included in the 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. That is, the downlink component carrier on which the PDSCH scheduled by the DCI format 1_0 is arranged may be the same as the downlink component carrier on which the PDCCH including the DCI format 1_0 is arranged.

　DCI format 1_0 may not include the BWP field. That is, the downlink BWP in which the PDSCH scheduled by the DCI format 1_0 is arranged may be the same as the downlink BWP in which the PDCCH including the DCI format 1_0 is arranged.

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

A 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 at least be used to indicate frequency resource allocation for the PDSCH.

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

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

When the PDSCH_HARQ feedback timing indication field is included in DCI format 1_1, the PDSCH_HARQ feedback timing indication field indicates the offset from the slot including the last OFDM symbol of PDSCH to the slot including the first OFDM symbol of PUCCH. may be used at least for If the PDSCH_HARQ feedback timing indication field is not included in DCI format 1_1, the offset from the slot that includes the last OFDM symbol of PDSCH to the slot that includes the first OFDM symbol of PUCCH may be specified by higher layer parameters. good.

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

When the 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 the DCI format 1_1 does not include the BWP field, the downlink BWP in which the PDSCH is arranged may be the same as the downlink BWP in which the PDCCH including the DCI format 1_1 used for scheduling the PDSCH is arranged. When the number of downlink BWPs configured in the terminal device 1 in a certain downlink component carrier is 2 or more, the BWP field included in the DCI format 1_1 used for scheduling the PDSCH arranged in the certain downlink component carrier. The number of bits may be 1 bit or more. When the number of downlink BWPs configured in the terminal device 1 in a certain downlink component carrier is 1, the bits of the BWP field included in the DCI format 1_1 used for scheduling the PDSCH arranged in the certain downlink component carrier. The number may be 0 bits (or the BWP field may not be included in the DCI format 1_1 used for scheduling PDSCH allocated to the certain downlink component carrier).

When the 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 arranged. When DCI format 1_1 does not include a carrier indicator field, the downlink component carrier on which PDSCH is arranged is the same as the downlink component carrier on which PDCCH including DCI format 1_1 used for scheduling of the PDSCH is arranged. good too. When the number of downlink component carriers configured in the terminal device 1 in a certain serving cell group is 2 or more (when downlink carrier aggregation is operated in a certain serving cell group), PDSCH arranged in the certain serving cell group. The number of bits of the carrier indicator field included in the DCI format 1_1 used for scheduling may be 1 bit or more (eg, 3 bits). When the number of downlink component carriers configured in the terminal device 1 in a certain serving cell group is 1 (when downlink carrier aggregation is not operated in a certain serving cell group), scheduling of the PDSCH arranged in the certain serving cell group The number of bits of the carrier indicator field included in the used DCI format 1_1 may be 0 bits (or the carrier indicator field is included in the DCI format 1_1 used for scheduling the PDSCH allocated to the serving cell group. may be omitted).

The PDSCH may be used to transmit transport blocks. PDSCH may be used to transmit transport blocks corresponding to DL-SCH. PDSCH may be used to convey transport blocks. PDSCH may be used to convey transport blocks corresponding to DL-SCH. Transport blocks may be placed on the PDSCH. A 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.

A downlink physical signal may correspond to a set of resource elements. Downlink physical signals may not carry information originating in higher layers. A downlink physical signal may be a physical signal used in a downlink component carrier. A downlink physical signal may be transmitted by the base station device 3 . A downlink physical signal may be transmitted by the terminal device 1 . In the downlink of the radio communication system according to one aspect of this 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 for the terminal device 1 to synchronize in the downlink frequency domain and/or time domain. A synchronization signal is a general term for PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal).

FIG. 7 is a diagram illustrating a configuration example of an SS/PBCH block according to one aspect of the present embodiment. In FIG. 7, the horizontal axis is the time axis (OFDM symbol index l _sym ), and the vertical axis is the frequency domain. Also, hatched blocks indicate a set of resource elements for the PSS. Also, the grid block indicates a set of resource elements for the SSS. Also, a block with horizontal lines indicates a set of resource elements for a PBCH and a DMRS for the PBCH (DMRS associated with the PBCH, DMRS included in the PBCH, and DMRS corresponding to the PBCH).

As shown in FIG. 7, the SS/PBCH block includes PSS, SSS, and PBCH. Also, the SS/PBCH block includes four consecutive OFDM symbols. The SS/PBCH block contains 240 subcarriers. The PSS is arranged on the 57th to 183rd subcarriers in the 1st OFDM symbol. The SSS is located on the 57th to 183rd subcarriers in the 3rd OFDM symbol. The 1st to 56th subcarriers of the 1st OFDM symbol may be set to zero. The 184th to 240th subcarriers of the 1st OFDM symbol may be set to zero. The 49th to 56th subcarriers of the 3rd OFDM symbol may be set to zero. The 184th to 192nd subcarriers of the 3rd OFDM symbol may be set to zero. The PBCH is arranged on subcarriers that are the 1st to 240th subcarriers of the second OFDM symbol and on which no DMRS for the PBCH is arranged. The PBCH is arranged on subcarriers that are the 1st to 48th subcarriers of the 3rd OFDM symbol and on which no DMRS for the PBCH is arranged. The PBCH is arranged in the 193rd to 240th subcarriers of the 3rd OFDM symbol and in subcarriers where no DMRS for the PBCH is arranged. The PBCH is arranged in subcarriers that are the 1st to 240th subcarriers of the 4th OFDM symbol and in which the DMRS for the PBCH is not arranged.

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

A PBCH to which symbols of a PBCH in a certain antenna port are transmitted is a DMRS for the PBCH that is mapped to the slot to which the PBCH is mapped, and is included in the SS/PBCH block that includes the PBCH. of DMRS.

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

A set of antenna ports for DMRS for PDSCH (DMRS associated with PDSCH, DMRS included in PDSCH, DMRS corresponding to PDSCH) may be provided based on the set of antenna ports for the PDSCH. That is, the set of DMRS antenna ports for the PDSCH may be the same as the set of antenna ports for the PDSCH.

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

A PDSCH may be estimated from the DMRS for the PDSCH. That is, the PDSCH propagation path may be estimated from the DMRS for the PDSCH. If a set of resource elements in which a certain PDSCH symbol is transmitted and a set of resource elements in which a DMRS symbol for the certain PDSCH is transmitted are included in the same Precoding Resource Group (PRG) In that case, the PDSCH on which the PDSCH symbols on a given antenna port are conveyed may be estimated by the DMRS for the PDSCH.

Antenna ports for DMRS for PDCCH (DMRS related to PDCCH, DMRS included in PDCCH, DMRS corresponding to PDCCH) may be the same as antenna ports for PDCCH.　

A PDCCH may be estimated from the DMRS for the PDCCH. That is, the PDCCH propagation path may be estimated from the DMRS for the PDCCH. If the same precoder is applied (assumed to be applied, applicable), the PDCCH on which the symbols for that PDCCH at a given antenna port are conveyed may be estimated by the DMRS for that 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 transport block (TB) or MAC PDU (Protocol Data Unit). HARQ (Hybrid Automatic Repeat reQuest) control is performed for each transport block in the MAC layer. A transport block is the unit of data that the MAC layer delivers to the physical layer. At the physical layer, transport blocks are mapped to codewords, and modulation processing is performed on each codeword.

One UL-SCH and one DL-SCH may be provided for each serving cell. A BCH may be provided to the PCell. BCH may not be given to PSCell, SCell.

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

An RRC message includes one or more RRC parameters (information elements). For example, the RRC message may contain the MIB. The RRC message may also contain system information. Also, the RRC message may include a message corresponding to CCCH. Also, the RRC message may include a message corresponding to the DCCH. RRC messages containing messages corresponding to DCCH are also referred to as dedicated RRC messages.

A BCCH in a logical channel may be mapped to a BCH or a DL-SCH in a transport channel. A CCCH in a Logical Channel may be mapped to a DL-SCH or UL-SCH in a Transport Channel. A DCCH in a Logical Channel may be mapped to a DL-SCH or UL-SCH in a Transport Channel.

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

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

The procedure performed by the terminal device 1 includes at least some or all of 5A to 5C below.
5A) Cell search
5B) random access
5C) data communication

A cell search is a procedure used by the terminal device 1 to synchronize with a certain cell in the time domain and frequency domain and to detect a physical cell identity. That is, the terminal device 1 may perform time domain and frequency domain synchronization with a certain cell by cell search and detect the physical cell ID.

The PSS sequence is given based at least on the physical cell ID. A sequence of SSSs is provided based at least on the physical cell ID.

An SS/PBCH block candidate indicates a resource on which transmission of an SS/PBCH block is permitted (possible, reserved, configured, specified, possible).

A set of SS/PBCH block candidates in a half radio frame is also called an SS burst set. An SS burst set is also called a transmission window, an SS transmission window, or a DRS transmission window (Discovery Reference Signal transmission window). The SS burst set is a generic term including 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 indices at a predetermined cycle. The terminal device 1 may detect at least one of the SS/PBCH blocks of the one or more indices and attempt to decode the PBCH included in the SS/PBCH blocks.

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

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

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

Message 2 is a procedure for trying to detect DCI format 1_0 with CRC (Cyclic Redundancy Check) scrambled by RA-RNTI (Random Access-Radio Network Temporary Identifier) by terminal device 1. The terminal device 1 includes the 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 the cell search and the resource indicated based on the configuration of the search area set. Try to detect PDCCH. Message 2 is also called a random access response.

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

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

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

Message 4 is a procedure that attempts to detect DCI format 1_0 with a scrambled CRC based on either C-RNTI (Cell-Radio Network Temporary Identifier) or TC-RNTI. The terminal device 1 receives the PDSCH scheduled based on the DCI format 1_0. The PDSCH may contain 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 PDCCH in resources identified based on the control resource set and the search area set (monitor PDCCH, monitor PDCCH).

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

The set of resource blocks that make up the control resource set may be indicated by higher layer parameters. The number of OFDM symbols that make up the control resource set may be indicated by a higher layer parameter.

The terminal device 1 attempts to detect the PDCCH in the search area set. Here, trying to detect a PDCCH in the search area set may be trying to detect a PDCCH candidate in the search area set, or may be trying to detect a DCI format in the search area set. Then, it may be trying to detect PDCCH in the control resource set, may be trying to detect PDCCH candidates in the control resource set, or may be trying to detect the DCI format in the control resource set. There may be.

A search area set is defined as a set of PDCCH candidates. The search area set may be a CSS (Common Search Space) set or a USS (UE-specific Search Space) set. The terminal device 1 uses a type 0 PDCCH common search space set, a type 0a PDCCH common search space set, a type 1 PDCCH common search space set, One of Type2 PDCCH common search space set, Type3 PDCCH common search space set and/or UE-specific PDCCH search space set Attempt to detect PDCCH candidates in part or all.

A type 0 PDCCH common search region set may be used as the index 0 common search region set. The type 0 PDCCH common search region set may be the index 0 common search region set.

A CSS set is a generic term for a type 0 PDCCH common search area set, a type 0a PDCCH common search area set, a type 1 PDCCH common search area set, a type 2 PDCCH common search area set, and a type 3 PDCCH common search area set. A USS set is also referred to as a UE-specific PDCCH search area set.

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

For a given search area set, some or all of 6A through 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 occurrence of a certain search area set may correspond to the OFDM symbol in which the leading OFDM symbol of the control resource set associated with the certain search area set is located. A monitoring opportunity for a given search area set may correspond to resources of the control resource set starting from the first OFDM symbol of the control resource set associated with the given search area set. The search area set monitoring opportunities are provided based on at least some or all of a PDCCH monitoring interval, a PDCCH monitoring pattern within a slot, and a PDCCH monitoring offset.

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

In FIG. 8, the blocks indicated by grid lines indicate the search area set 91, the blocks indicated by diagonal lines rising to the right indicate the search area set 92, the blocks indicated by diagonal lines rising to the left indicate the search area set 93, and the blocks indicated by horizontal lines indicate the search area set 93. The block shown represents the search area set 94 .

The monitoring interval of the search area set 91 is set to 1 slot, the monitoring offset of the search area set 91 is set to 0 slots, and the monitoring pattern of the search area set 91 is [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 of the slots.

The monitor interval for search area set 92 is set to 2 slots, the monitor offset for search area set 92 is set to 0 slots, and the monitor pattern for search area set 92 is [1,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 of the even slots.

The monitoring interval of the search area set 93 is set to 2 slots, the monitoring offset of the search area set 93 is set to 0 slots, and the monitoring pattern of the search area set 93 is [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 eighth OFDM symbol (OFDM symbol #7) in each of the even slots.

The monitoring interval of the search area set 94 is set to 2 slots, the monitoring offset of the search area set 94 is set to 1 slot, and the monitoring pattern of the search area set 94 is [1,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 of the odd slots.

A type 0 PDCCH common search area set may be used at least for DCI formats with CRC (Cyclic Redundancy Check) sequences scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier).

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

Type 1 PDCCH common search area set includes CRC sequences scrambled by RA-RNTI (Random Access-Radio Network Temporary Identifier) and/or CRC sequences scrambled by TC-RNTI (Temporary Cell-Radio Network Temporary Identifier). It may at least be used for the DCI format that accompanies it.

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

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

A UE-specific PDCCH search area set may be used at least for DCI formats with CRC sequences scrambled by 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. HARQ-ACK corresponding to the PDSCH (HARQ-ACK corresponding to the transport block included in the PDSCH) is reported to the base station apparatus 3 based on the PUCCH resource indicated based on the detected downlink DCI format.

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 the configured scheduling (configured grant), the uplink grant for scheduling the PUSCH is configured for each PUSCH transmission cycle. Part or all of the information indicated by the uplink DCI format when the PUSCH is scheduled by the uplink DCI format may be indicated by the uplink grant that is configured in the case of scheduling that is configured.

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

FIG. 9 is a diagram showing a configuration example of the medium access control layer processing unit 15 according to one aspect of the present embodiment. In FIG. 9, the medium access control layer processing unit 15 is configured including a HARQ entity 9000 . Also, the HARQ entity 9000 comprises N HARQ processes. For example, N may be 8 or 16.

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

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

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

The HARQ entity 9000 may deliver the uplink grant and HARQ information corresponding to the uplink grant to the HARQ process assigned the HARQ process number corresponding to the uplink grant. Furthermore, if the uplink grant does not correspond to retransmission, the HARQ entity 9000 may deliver the obtained MAC PDU to the HARQ process with the HARQ process number corresponding to the uplink grant.

The HARQ process may instruct the physical layer processing unit 10 to transmit based on the received uplink grant and HARQ information. Furthermore, when a 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 the transport block encoding procedure based on the transmission instruction from the HARQ process. Here, the transport block is the MAC PDU delivered from the HARQ process. The transport block encoding procedure may be performed by the encoding unit 12000 included in the physical layer processing unit 10 .

FIG. 10 is a diagram showing a configuration example of an encoding processor unit 12000 according to one aspect of the present embodiment. In FIG. 10, an encoding processing unit 12000 includes a CRC addition unit 12001, a code lock segmentation unit 12002, an encoding unit 12003, a rate-matching unit ) 12004 and a part or all of a multiplexing unit 12005.

The transport block is input to the CRC adding section 12001. CRC adding section 12001 may add a CRC sequence to the transport block. A bit sequence including CRC and transport blocks may be input to code block division section 12002 . If no CRC sequence is attached to the transport block, a bit sequence including the transport block may be input to code block division section 12002 .

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

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

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

FIG. 11 is a diagram illustrating an example bit selection procedure according to one aspect of the present embodiment. In FIG. 11, the bit selection procedure comprises eight steps. In step 1 of the bit selection procedure, the values of two variables k and j are each set to zero. Next, in step 1, it is determined whether the value of variable k is smaller than the rate matching output sequence length _Er . If the value of variable k is less than the rate matching output sequence length _Er , the bit selection procedure proceeds to step 2; If the value of variable k is not less than the rate matching output sequence length _Er , the bit selection procedure is completed.

The rate matching output sequence length E _r indicates the number of bits available for transmission of code block r. For example, the rate matching output sequence length E _r may be determined based on at least the PUSCH modulation order Q _m , the number of PUSCH layers L _v , the number C of code blocks, and the value G. For example, the rate matching output sequence length E _r can be 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 the PUSCH instance and available for UL-SCH transmission. Here, the PUSCH instance is also called a PUSCH transmission occasion. Also, the bits available for UL-SCH transmission indicates the number of bits available for transport block transmission.

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; Also, 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, e(k) is input with the value of d ^r (mod(k ₀ +j, N _cb )). 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 _Er .

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

In step 4, the value of k is incremented.

Step 5 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.

FIG. 12 is a diagram illustrating the concept of a circular buffer according to one aspect of the present embodiment. In the circular buffer, the coded bit sequence d ^r is written clockwise starting at the position denoted by RV0. Since the coded bit d ^r is a sequence in which a systematic bit sequence and a parity bit sequence are combined, systematic bits are written clockwise from RV0 (area indicated by a black frame in the figure), and systematic bits are written. The configuration is such that the parity bit sequence is written from the end of the sequence (the area indicated by the white frame in the figure).

In the bit selection procedure, the bits written into the circular buffer may be read from starting position k ₀ for E _r bits. The read E _r bits are input to the rate matching output sequence e. Here, the start position _k0 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. Also, when multiple code blocks are generated, the rate matching output sequences for each of the code blocks may be combined to generate one sequence g. Also, when multiple code blocks are not generated, one rate matching output sequence may be regarded as one sequence g. One sequence g may be input to multiplexing section 12005 .

Multiplexing section 12005 may multiplex one sequence g and control data (eg, HARQ-ACK, CSI, etc.). For example, the multiplexing unit 12005 may generate array Q. Each of the elements of array Q is identified based at least on some or all of an index k′ _sc associated with a subcarrier, an index l′ associated with an OFDM symbol, and an index m′ based on modulation order and number of layers. good too. Here, the index k′ _sc associated with the subcarrier may be an index associated with the subcarrier to which the PUSCH instance is allocated. Also, the index l' associated with the OFDM symbol may be the index m' associated with the OFDM symbol to which the PUSCH instance is assigned. Also, the index based on the modulation order and number of layers may take values 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 the array Q with index k′ _sc =k _x , index l′=l _x and index m′=m _x is called Q(k _x , l _x , m _x ).

When multiplexing section 12005 allocates HARQ-ACK coded bit sequence q to array Q, multiplexing section 12005 may specify the start position l _start . Once the starting position l _start is specified, the encoded bit sequence q may be placed at Q(k′ _sc , l _start , m′). Here, the coded bit sequence q may be arranged in ascending order with respect to index m′ and then arranged in the direction of index k′ _sc . When the arrangement of the coded bit sequence q is completed in the element of the array of l=l _start , the element of the array of l=l _start +1 may be moved to.

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

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

The multiplexing unit 12005 reads the sequence from array Q and generates sequence b. The series b is subjected to various baseband processing and used to generate a time domain signal. Here, 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 PUSCH instance is generated per slot and may be transmitted in multiple slots.

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

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

In repeated transmission of PUSCH, the HARQ process may instruct the physical layer processing unit 10 to transmit N times 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 whether or not a collision with another uplink channel occurs for each instance of PUSCH. If a PUSCH instance collides with a higher priority uplink channel, transmission of the PUSCH instance may be omitted. Here, omitting the transmission of the PUSCH instance may mean that the transmission is dropped or that the transmission is not performed.

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

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

FIG. 13 is a diagram illustrating an example of PUSCH multi-slot transmission according to one aspect of the present embodiment. In FIG. 13, the horizontal axis is the time axis, and each grid on the time axis is the slot boundary. In addition, the slot indices are set in ascending order in the right direction, and the first slot in the figure is slot #n.

In the multi-slot transmission shown in FIG. 13, the PUSCH repetition count N is set to 8, and 8-slot time resources are used in the multi-slot transmission. On the other hand, each of the

PUSCH instances

13001, 13002, and 13003 is configured with time resources of multiple slots. That is, in PUSCH multi-slot transmission, the PUSCH instance format and the number of PUSCH instances N _instance may be determined based on at least the number of repetitions N and external parameters. Here, the extrinsic parameter may be provided by the RRC layer, or may be provided by the PDCCH that provides an uplink grant to instruct multi-slot transmission.

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

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

Here, the number of repetitions N _unit that configures the PUSCH instance may be indicated by a parameter provided by the RRC layer. Also, the repetition number N _unit that constitutes an instance of PUSCH may be provided by the PDCCH.

The HARQ entity 9000 may issue uplink grants based on the number N _instance determined by the physical layer processing unit 10 . For example, the HARQ entity 9000 may issue N _instance uplink grants. Also, the HARQ process may instruct the physical layer processing unit 10 to transmit based on the N _instance uplink grants.

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

FIG. 14 is a diagram illustrating an example of PUSCH multi-slot transmission according to one aspect of the present embodiment. In FIG. 14, the horizontal axis is the time axis, and each grid on the time axis is the slot boundary. In addition, the slot indices are set in ascending order in the right direction, and the first slot in the figure is slot #n. Each of 14001 to 14008 indicates time resources configured for PUSCH multi-slot transmission. In FIG. 14, the number of repetitions N is set to 8, and time resources are set for each of slot #n to slot #n+7. In one example shown in FIG. 14, PUSCH instances for multi-slot transmission may be determined based on the repetition number N and the TDD pattern settings. Here, in FIG. 14, time resources corresponding to black frames indicate downlink regions, and time resources corresponding to white frames indicate uplink regions. In the example shown in FIG. 14, PUSCH instances may be configured by continuous time resources corresponding to the uplink region among resources corresponding to N repetitions. In the example of FIG. 14, 14011 and 14012 respectively indicate instances of PUSCH.

For example, the external parameter may be the setting of the TDD pattern. One PUSCH instance may be composed of a set of time resources corresponding to one temporally continuous uplink region among time resources corresponding to N repetitions. That is, one PUSCH instance may be configured not to include time resources corresponding to the downlink region. Here, the uplink area may or may not include the flexible area. Also, the uplink area may or may not include the flexible area.

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

For example, if the extrinsic parameter indicates the application of multi-slot transmission, the number of PUSCH instances may be determined based on the repetition number N _unit that constitutes the PUSCH instances. Also, if the extrinsic parameter indicates the application of multi-slot transmission, the configuration of the PUSCH instance may be determined based on N _unit .

For example, if the extrinsic parameter indicates the application of multi-slot transmission, the configuration of the PUSCH instance may be determined based on the setting of the TDD pattern. Also, if the extrinsic parameter indicates the application of multi-slot transmission, the number of PUSCH instances may be determined based on the configuration of the TDD pattern.

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

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

By using the external parameters, the medium access control layer processing unit 15 can suitably instruct the physical layer processing unit 10 to transmit.

In PUSCH multi-slot transmission, the procedure for collision with PUCCH may be implemented for each instance of PUSCH. For example, when a certain PUSCH instance and PUCCH collide, UCI scheduled to be transmitted on PUCCH may be multiplexed onto the certain PUSCH instance.

For example, when a certain PUSCH instance collides with a PUCCH on which HARQ-ACK is scheduled to be transmitted, the coded bit sequence q of the HARQ-ACK may be multiplexed on the certain PUSCH instance. Here, the multiplexing section 12005 may multiplex the encoded bit sequence q with one sequence g scheduled to be transmitted in the certain PUSCH instance. Here, the coded bit sequence q may specify the starting position l _start based on the OFDM symbol next to the OFDM symbol containing the leading DMRS of the instance.

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

Aspects of various devices according to one aspect of the present embodiment will be described below.

(1) In order to achieve the above objects, the aspects of the present invention take the following measures. That is, a first aspect of the present invention is a terminal device that communicates with a base station device, comprising a physical layer processing unit and a medium access control layer processing unit, wherein the physical layer processing unit is included in a received PDCCH. HARQ information is delivered to the medium access control layer processing unit, and the physical layer processing unit determines the number of PUSCH instances N _instance based on the PUSCH repetition count N and external parameters 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 performs HARQ and a HARQ process, wherein the HARQ entity generates N _instances of uplink grants based on the one uplink grant, and the HARQ processes generate N _instances of uplink grants based on the N _instances of uplink grants. A transmission instruction is issued to the physical layer processing unit.

(2) A second aspect of the present invention is a base station apparatus comprising a physical layer processing unit and a medium access control layer processing unit, the physical layer processing unit transmitting HARQ information on a PDCCH, The physical layer processing unit determines the number of PUSCH instances N _instance based on the PUSCH repetition count N and external parameters, and attempts to receive the PUSCH based on the N _instance uplink grants.

A program that operates on the base station device 3 and the terminal device 1 according to one aspect of the present invention controls a CPU (Central Processing Unit) and the like so as to realize the functions of the above-described embodiments related to one aspect of the present invention. It may be a program (a program that causes a computer to function). The 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) and HDD (Hard Disk Drive), It is read, modified, and written by the CPU as necessary.

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

The "computer system" here is a computer system built into the terminal device 1 or the base station device 3, and includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible discs, magneto-optical discs, ROMs and CD-ROMs, and storage devices such as hard discs incorporated in computer systems.

Furthermore, "computer-readable recording medium" means a medium that dynamically stores a program for a short period of time, such as a communication line for transmitting a program via a network such as the Internet or a communication line such as a telephone line. In that case, it may also include a memory that holds the program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or client. Further, the program may be for realizing part of the functions described above, or may be capable of realizing the functions described above in combination with a program already recorded in the computer system.

Also, the base station device 3 in the above-described embodiment can be realized as an aggregate (device group) composed of a plurality of devices. Each of the devices constituting the device group may include a part or all of each function or each functional block of the base station device 3 related to the above-described embodiments. A device group may have a series of functions or functional blocks of the base station device 3 . Also, the terminal device 1 according to the above-described embodiments can communicate with a base station device as a group.

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

Also, part or all of the terminal device 1 and the base station device 3 in the above-described embodiments may be typically implemented as an LSI, which is an integrated circuit, or may be implemented as a chipset. Each functional block of the terminal device 1 and the base station device 3 may be individually chipped, or part or all of them may be integrated and chipped. Also, the method of circuit integration is not limited to LSI, but may be realized by a dedicated circuit or a general-purpose processor. In addition, when a technology for integrating circuits to replace LSIs emerges due to advances in semiconductor technology, it is possible to use an integrated circuit based on this technology.

In addition, in the above-described embodiments, a terminal device was described as an example of a communication device, but the present invention is not limited to this. For example, it can be applied to terminal devices or communication devices such as AV equipment, kitchen equipment, cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household equipment.

Although the embodiment of this invention has been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes etc. within the scope of the gist of this invention are also included. Further, one aspect of the present invention can be modified in various ways within the scope of the claims, and an embodiment obtained by appropriately combining technical means disclosed in different embodiments can also be Included in the scope. Moreover, it is an element described in each said embodiment, and the structure which replaced the element with which the same effect is produced is also included.

One aspect of the present invention is, for example, a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), or a program, etc. be able to.

1 (1A, 1B, 1C) terminal device 3

base station devices

10, 30 radio transmitting/receiving units 10a, 30a radio transmitting units 10b, 30b

radio receiving units

11, 31

antenna units

12, 32

RF units

13, 33

baseband unit

14, 34 upper

layer processing units

15, 35 medium access control

layer processing units

16, 36 radio resource control layer processing units 91, 92, 93, 94 search area set 300 component carrier 301

primary cells

302, 303 secondary cells 3000

points

3001, 3002

resources grid

3003, 3004 BWP
3011, 3012, 3013, 3014 offset 3100, 3200 common resource block set 9000 HARQ entity 12000

encoding processing unit

13001, 13002, 13003, 14011, 14012

instance

14001, 14002, 14003, 14004, 14005, 14006, time resource 140087

Claims

A terminal device that communicates with a base station 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 the received PDCCH to the medium access control layer processing unit,
The physical layer processing unit determines the number of PUSCH instances N instance based on the PUSCH repetition count N and external parameters provided from the base station apparatus,
The determined number is delivered to the medium access control layer processing unit,
The medium access control layer processing unit acquires 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 instance uplink grants based on the one uplink grant;
The HARQ process instructs the physical layer processing unit to transmit N instances based on the N instances of uplink grants.
comprising a physical layer processing unit and a medium access control layer processing unit,
The physical layer processing unit transmits HARQ information on PDCCH,
The physical layer processing unit determines the number of PUSCH instances N instance based on the PUSCH repetition count N and an external parameter,
A base station apparatus that tries to receive the PUSCH based on the N instance uplink grants.
A communication method used in a base station device,
transmitting HARQ information on the PDCCH;
determining the number of instances of PUSCH, N instance , based on the number of PUSCH iterations, N, and an extrinsic parameter;
Attempting to receive the PUSCH based on the N instance uplink grants.