User equipment, base station and method

Abstract

To provide a flexible and efficient method for indicating that a first information field is present in a DCI format.SOLUTION: A method includes inserting most significant bit of which a value is "0" to a second information field in a DCI format with CRC scrambled by C-RNTI with a first information field indicating a transform precoder as disabled until a second umber of bits becomes equal to a first number, the second number of bits being included in the second information field in the DCI format with CRC scrambled by CS-RNTI, the second information field including the first number of bits, to align bit field size of the DCI formats. UE acquires at least a first RRC parameter for indicating that a first information field is present in a DCI format, and monitors the DCI format with CRC scrambled by C-RNTI and the DCI format with CRC scrambled by CS-RNTI.SELECTED DRAWING: Figure 16

Description

[Technical field]

[0001] The present invention relates to a user equipment, a base station and a method. [Background technology]

[0002] In the Third Generation Partnership Project (3GPP), radio access methods and radio networks for cellular mobile communication (hereinafter referred to as Long Term Evolution or Evolved Universal Terrestrial Radio Access) are being studied. In LTE (Long Term Evolution), a base station device is also referred to as Evolved NodeB (eNodeB) and a terminal device is also referred to as User Equipment (UE). LTE is a cellular communication system in which multiple areas are deployed in a cellular structure, and each of the multiple areas is covered by a base station device. A single base station device can manage multiple cells. Evolved Universal Terrestrial Radio Access is also referred to as E-UTRA.

[0003] In 3GPP, the next generation standard (New Radio: NR) is being studied to make a proposal for International-Mobile-Telecommunication 2020 (IMT 2020), which is the standard for the next generation mobile communication system defined by the International Telecommunications Union (ITU). NR is expected to meet the requirements considering three scenarios, eMBB (enhanced Mobile BroadBand), mMTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication), in a single technology framework.

[0004] For example, a wireless communication device may communicate with one or more devices using a communication structure. However, only the flexibility and / or efficiency of the communication structure used may be limited. As described in this discussion, systems and methods that improve the flexibility and / or efficiency of communication may be considered beneficial. [Brief description of the drawings]

[0005] [Figure 1] 1 is a conceptual diagram of a wireless communication system according to an embodiment of the present invention. [Diagram 2] 13 is an example showing a relationship between a subcarrier spacing configuration u, the number of OFDM symbols per slot Nslot symb, and a CP configuration according to one aspect of the present embodiment. [Diagram 3] FIG. 2 illustrates an example method for configuring a resource grid according to one aspect of the present embodiment. [Figure 4] FIG. 3 is a diagram illustrating an example of the configuration of a resource grid 3001 according to an aspect of the present embodiment. [Diagram 5] 2 is a schematic block diagram illustrating a configuration example of a base station device 3 according to an aspect of the present embodiment. FIG. [Figure 6] 1 is a schematic block diagram showing an example of the configuration of a terminal device 1 according to an aspect of the present embodiment. [Figure 7] FIG. 2 is a diagram illustrating an example of the configuration of an SS / PBCH block according to one embodiment of the present invention. [Figure 8] FIG. 2 is a diagram illustrating an example of a monitoring opportunity for a search-space-set according to one aspect of the present embodiment. [Figure 9] FIG. 13 is a diagram illustrating an example of a PUSCH generation procedure on the UE side. [Figure 10] FIG. 1 illustrates an example of a DFT processing formula for transform precoding. [Figure 11] A figure showing an example of the payload size before bit padding for DCI format 0_1 ​​in which the CRC is scrambled by the C-RNTI. [Figure 12]A figure showing an example of payload size after bit field size alignment for DCI format 0_1 ​​in which CRC is scrambled by C-RNTI. [Figure 13] A figure showing an example of bit field size matching between DCI format 0_1 ​​in which the CRC is scrambled by the C-RNTI and DCI format 0_1 ​​in which the CRC is scrambled by the CS-RNTI and in which NDI=0. [Figure 14] A figure showing an example of bit field size matching between DCI format 0_1 ​​in which the CRC is scrambled by the C-RNTI and DCI format 0_1 ​​in which the CRC is scrambled by the CS-RNTI and NDI=1. [Figure 15] A figure showing an example of payload size after payload size alignment for DCI format 0_1 ​​in which the CRC is scrambled by the C-RNTI. [Figure 16] FIG. 1 illustrates an example of a UE method. [Figure 17] FIG. 13 illustrates an example of a base station method. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0006] A user equipment (UE) is described. The UE may include an upper layer processing circuit configured to obtain at least a first RRC parameter for indicating a presence of a first information field in a DCI format, the first information field indicating whether a transform precoder is enabled or disabled for a PUSCH. The UE may also include a receiving circuit configured to monitor a C-RNTI-CRC-scrambled DCI format and a CS-RNTI-CRC-scrambled DCI format. A first number of bits may be included in a second information field of the DCI format in which the C-RNTI-CRC-scrambled DCI format and the first information field indicates the transform precoder as disabled. If a second number of bits included in the second information field of the CS-RNTI-CRC-scrambled DCI format is not equal to the first number, most significant bits with a value of "0" may be inserted in the second information field of the CS-RNTI-CRC-scrambled DCI format until the second number is equal to the first number.

[0007] A third number of bits may be included in a second information field of a DCI format in which the CRC is scrambled by the C-RNTI and the transform precoder is indicated as valid in the first information field. If the third number is not equal to the first number, most significant bits having a value of "0" may be inserted in the second information field of a DCI format in which the CRC is scrambled by the C-RNTI and the transform precoder is indicated as valid in the first information field until the third number is equal to the first number.

[0008] A fourth number of bits may be included in the DCI format in which the CRC is scrambled by the C-RNTI and the transform precoder is indicated as disabled in the first information field. A fifth number of bits may be included in the DCI format in which the CRC is scrambled by the C-RNTI and the transform precoder is indicated as enabled in the first information field. If the fourth number is not equal to the fifth number, bits with a value of "0" may be inserted in the DCI format in which the CRC is scrambled by the C-RNTI and the transform precoder is indicated as enabled in the first information field until the fifth number is equal to the fourth number.

[0009] A base station is described. The base station may include an upper layer processing circuit configured to transmit at least a first RRC parameter for indicating a presence of a first information field in a DCI format, the first information field indicating whether a transform precoder is enabled or disabled for a PUSCH. The base station may also include a transmitting circuit configured to transmit a DCI format in which a CRC is scrambled by a C-RNTI and a DCI format in which a CRC is scrambled by a CS-RNTI. A first number of bits may be included in a second information field of the DCI format in which a CRC is scrambled by a C-RNTI and in which a transform precoder is indicated as disabled in the first information field. If a second number of bits included in the second information field of the DCI format in which a CRC is scrambled by a CS-RNTI is not equal to the first number, a most significant bit having a value of "0" may be inserted in the second information field of the DCI format in which a CRC is scrambled by a CS-RNTI until the second number is equal to the first number.

[0010] A third number of bits may be included in a second information field of a DCI format in which the CRC is scrambled by the C-RNTI and the transform precoder is indicated as valid in the first information field. If the third number is not equal to the first number, most significant bits having a value of "0" may be inserted in the second information field of a DCI format in which the CRC is scrambled by the C-RNTI and the transform precoder is indicated as valid in the first information field until the third number is equal to the first number.

[0011] A fourth number of bits may be included in the DCI format in which the CRC is scrambled by the C-RNTI and the transform precoder is indicated as disabled in the first information field. A fifth number of bits may be included in the DCI format in which the CRC is scrambled by the C-RNTI and the transform precoder is indicated as enabled in the first information field. If the fourth number is not equal to the fifth number, bits with a value of "0" may be inserted in the DCI format in which the CRC is scrambled by the C-RNTI and the transform precoder is indicated as enabled in the first information field until the fifth number is equal to the fourth number.

[0012] A method for a user equipment (UE) is described. The method may include obtaining at least a first RRC parameter for indicating a presence of a first information field in a DCI format, the first information field indicating whether a transform precoder is enabled or disabled for a PUSCH. The method may also include monitoring a C-RNTI-CRC-scrambled DCI format and a CS-RNTI-CRC-scrambled DCI format. A first number of bits may be included in a second information field of the DCI format in which the C-RNTI-CRC-scrambled DCI format and the first information field indicates the transform precoder as disabled. If a second number of bits included in the second information field of the CS-RNTI-CRC-scrambled DCI format is not equal to the first number, most significant bits with a value of "0" may be inserted in the second information field of the CS-RNTI-CRC-scrambled DCI format until the second number is equal to the first number.

[0013] A method of a base station is described. The method may include transmitting at least a first RRC parameter for indicating a presence of a first information field in a DCI format, the first information field indicating whether a transform precoder is enabled or disabled for a PUSCH. The method may also include transmitting a DCI format in which a CRC is scrambled by a C-RNTI and a DCI format in which a CRC is scrambled by a CS-RNTI. A first number of bits may be included in a second information field of the DCI format in which a CRC is scrambled by a C-RNTI and in which a transform precoder is indicated as disabled in the first information field. If a second number of bits included in the second information field of the DCI format in which a CRC is scrambled by a CS-RNTI is not equal to the first number, most significant bits having a value of "0" may be inserted in the second information field of the DCI format in which a CRC is scrambled by a CS-RNTI until the second number is equal to the first number.

[0014] floor(CX) may be a floor function for the real number CX. For example, floor(CX) may be a function that provides the largest integer in a range that does not exceed the real number CX. ceil(DX) may be a ceiling function for the real number DX. For example, ceil(DX) may be a function that provides the smallest integer in a range that is equal to or greater than the real number DX. mod(EX,FX) may be a function that provides the remainder obtained by dividing EX by FX. mod(EX,FX) may be a function that provides a value corresponding to the remainder obtained by dividing EX by FX, which is exp(GX)=e ^ GX, where e is Napier's constant. (HX) A (IX) denotes the IXth power of HX.

[0015] In the wireless communication system according to an aspect of the present embodiment, at least OFDM (Orthogonal Frequency Division Multiplex) is used. An OFDM symbol is a time domain unit of OFDM. An OFDM symbol includes at least one or more subcarriers. The OFDM symbol is converted into a time continuous signal in baseband signal generation. In the downlink, at least CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplex) is used. In the uplink, CP-OFDM or DFT-s-OFDM (Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplex) is used. DFT-s-OFDM can be provided by applying transform precoding to CP-OFDM. CP-OFDM is OFDM using CP (Cyclic Prefix).

[0016] Either DFT-s-OFDM or CP-OFDM may be provided based on whether the transform precoder (or transform precoding) is enabled. If the transform precoder (or transform precoding) is enabled, DFT-s-OFDM may be provided. CP-OFDM may be provided if the transform precoder (or transform precoding) is disabled. For example, either an enabled or disabled transform precoder for PUSCH may be indicated based on the RRC parameters transformPrecoder in PUSCH-Config or ConfiguredGrantConfig and / or msg3-transformPrecoder in RACH-ConfigCommon. The information element PUSCH-Config may be used to configure UE-specific PUSCH parameters applicable to a particular BWP. The information element ConfiguredGrantConfig may be used to configure uplink transmissions without dynamic grant according to two possible schemes. The actual uplink grant can either be configured via RRC (type 1 CS) or provided via PDCCH (type 2 CS) (addressed to CS-RNTI). Multiple configured grant configurations can be configured in one BWP of the serving cell. The information element RACH-ConfigCommon can be used to specify cell-specific random access parameters.

[0017] The RRC parameter transformPrecoder indicates the UE specific selection of a transform precoder for PUSCH. If transformPrecoder is not present / configured, the UE applies the value of msg3-transformPrecoder to the transform precoder for PUSCH.

[0018] msg3-transformPrecoder indicates that the UE enables transform precoder for Msg3 transmission. If msg3-transformPrecoder is provided / configured, the UE enables transform precoder for Msg3 transmission. If msg3-transformPrecoder is not present / configured / not provided, the UE disables transform precoder for Msg3 transmission.

[0019] The OFDM symbol may be a designation that includes a CP added to the OFDM symbol, i.e., the OFDM symbol may be configured to include an OFDM symbol and a CP added to the OFDM symbol.

[0020] The terminal device may also be referred to as a user equipment (UE), and the base station device may also be referred to as a next-generation Node B (gNB, gNodeB).

[0021] Fig. 1 is a conceptual diagram of a wireless communication system according to an aspect of the present embodiment. In Fig. 1, the wireless communication system includes at least terminal devices 1A-1C and a base station device 3 (BS#3: base station #3). Hereinafter, the terminal devices 1A-1C are also referred to as terminal device 1 (UE#1: user equipment #1).

[0022] The base station device 3 may be configured to include one or more transmitting devices (or transmitting points, transmitting devices, receiving devices, transmitting points, receiving points). When the base station device 3 is configured by multiple transmitting devices, each of the multiple transmitting devices may be located at a different position.

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

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

[0025] For example, one resource grid may be provided for one component carrier. For example, one resource grid may be provided for one component carrier and subcarrier spacing configuration u. The subcarrier spacing configuration u is also referred to as numerology. The resource grid may be N size,u grid,x N RB sc The resource grid contains subcarriers with index N start,u grid Start with a common resource block with index N start,u grid The common resource block having N subframe,u symb OFDM symbols. The subscript x denotes the transmission direction, either downlink or uplink. One resource grid is provided for antenna port p, subcarrier spacing configuration u, and transmission direction x.

[0026] The resource grid is also referred to as a carrier.

[0027] N size,u grid,x and N start,u gridis given based on at least an RRC parameter (e.g., referred to as the RRC parameter CarrierBandwidth). The RRC parameter is used to define one or more SCS (subcarrier spacing) specific carriers. One resource grid corresponds to one SCS specific carrier. One component carrier may include one or more SCS specific carriers. The SCS specific carriers may be included in a system information block (SIB). For each SCS specific carrier, a subcarrier spacing configuration u may be provided.

[0028] FIG. 2 illustrates a subcarrier spacing configuration u and the number of OFDM symbols per slot N according to one embodiment of the present invention. slot symb 2A is an example showing the relationship between the subcarrier spacing configuration u and the CP configuration. In FIG. 2A, for example, when the subcarrier spacing configuration u is set to 2 and the CP configuration is set to normal CP (normal cyclic prefix), N slot symb =14, N fame,u slot =40, N subframe , u slot 2B, for example, when the subcarrier spacing configuration u is set to 2 and the CP configuration is set to extended cyclic prefix (Extended CP), N slot symb =12, N fame,u slot =40, N subframe,u slot =4.

[0029] In the wireless communication system according to one aspect of the present embodiment, the length of the time domain may be expressed using a time unit Tc. The time unit Tc is expressed as Tc=1 / (df max * Nf). It is df max = 480kHz. That is, Nf = 4096. The constant k is k = df max * N f / (df ref N f,ref )=64, and dfref is 15 kHz. Nf,ref is 2048.

[0030] The transmission of the signal in the downlink and / or the transmission of the signal in the uplink has a length T f The system frame can be organized into a number of radio frames (system frames, frames). f =(df max N f / 100) * T s = 10 ms. One radio frame is configured to include 10 subframes. The subframe length is T sf =(df max N f / 1000)T s = 1 ms. The number of OFDM symbols per subframe is N subframe ’ u symb =N slot symb N subframe ’ u slot It is.

[0031] For a subcarrier spacing configuration u, the number and index of slots contained in a subframe may be given. For example, slot index n u s is 0 to N in the subframe. subframe,u slot For a subcarrier spacing configuration u, the number of slots included in a radio frame and the index of the slot included in the radio frame may be given. Also, the slot index n u s,f is 0 to N in the radio frame. frame,u slot The integers can be given in ascending order from -1 to N. slot symb OFDM symbols can be included in one slot. That is, N slot symb =14.

[0032] 3 is a diagram showing an example of a method for configuring a resource grid according to an aspect of the present embodiment. The horizontal axis of FIG. 3 indicates the frequency domain. FIG. 3 shows a subcarrier spacing configuration u=u 1 Example of resource grid configuration and subcarrier spacing configuration u=u 2 3 shows an example of a resource grid configuration for u. One or more subcarrier spacing configurations can be configured for a component carrier. 1 =u 2 -1, but various aspects of this embodiment may 1 =u 2 Not limited to the condition -1.

[0033] The component carrier 300 is a band having a predetermined width in the frequency domain.

[0034] The point 3000 is an identifier for identifying a subcarrier. The point 3000 is also referred to as point A. The common resource block (CRB) set 3100 is a subcarrier spacing configuration u 1 A set of common resource blocks for

[0035] Within the common resource block set 3100, the common resource block that includes the point 3000 (the block indicated by the diagonal upper right line in FIG. 3) is also referred to as the reference point of the common resource block set 3100. The reference point of the common resource block set 3100 may be the common resource block with index 0 in the common resource block set 3100.

[0036] The offset 3011 is the offset from the reference point of the common resource block set 3100 to the reference point of the resource grid 3001. The offset 3011 is determined by the subcarrier spacing configuration u 1 The resource grid 3001 is represented by the number of common resource blocks for N size,u grid1,xIt contains common resource blocks.

[0037] The offset 3013 is the distance from the reference point of the resource grid 3001 to the reference point of the BWP (bandwidth portion) 3003 of index i1 (N start,u BWP,i1 ).

[0038] The common resource block set 3200 has a subcarrier spacing configuration u 2 is a set of common resource blocks for

[0039] The common resource block that includes the point 3000 in the common resource block set 3200 (the block indicated by the upper left diagonal line in FIG. 3 ) is also referred to as the reference point of the common resource block set 3200. The reference point of the common resource block set 3200 may be the common resource block with index 0 in the common resource block set 3200.

[0040] The offset 3012 is an offset from the reference point of the common resource block set 3200 to the reference point of the resource grid 3002. The offset 3012 is determined by the subcarrier spacing configuration u=u 2 The resource grid 3002 is denoted by the number of common resource blocks for the N size,u grid2,x It contains common resource blocks.

[0041] The offset 3014 is the distance from the reference point of the resource grid 3002 to the reference point of the BWP 3004 with index i2 (N start,u BWP,i2 ).

[0042] 4 is a diagram showing an example of the configuration of a resource grid 3001 according to one aspect of this embodiment. In the resource grid of FIG. 4, the horizontal axis represents the OFDM symbol index l sym The vertical axis is the subcarrier index k scThe resource grid 3001 is size,u grid1 ,xN RB sc It contains N subcarriers and subframes,u symb Contains OFDM symbols. Subcarrier index k sc and OFDM symbol index l in the resource grid sym A resource specified by is also called a resource element (RE).

[0043] A resource block (RB) is N RB sc A resource block is a collective term for a common resource block, a physical resource block (PRB), and a virtual resource block (VRB). It consists of N RB sc =12.

[0044] A resource block unit is a set of resources corresponding to one OFDM symbol in one resource block, i.e., one resource block unit includes 12 resource elements corresponding to one OFDM symbol in one resource block.

[0045] The common resource blocks of subcarrier spacing configuration u are indexed in ascending order in the frequency domain from 0 within the common resource block set. The common resource block with index 0 of subcarrier spacing configuration u contains (or collides with, coincides with) point 3000. The index n of the common resource block for subcarrier spacing configuration u u CRB is n u CRB =ceil(k sc / N RB sc ) relationship is satisfied. k scA subcarrier with .DELTA..times ...

[0046] The physical resource blocks for subcarrier spacing configuration u are indexed in ascending order in the frequency domain within the BWP starting from 0. The index n of the physical resource block for subcarrier spacing configuration u u PRB is n u CRB =n u PRB +N start,u BWP,i The relationship of N start,u BWP,i denotes the reference point of the BWP with index i.

[0047] A BWP is defined as a subset of common resource blocks contained in the resource grid. start,u BWP,i Starting with N size,u bwp,i The BWP of a downlink component carrier is also referred to as a downlink BWP, and the BWP of an uplink component carrier is also referred to as an uplink BWP.

[0048] The antenna ports are defined such that a channel on which a symbol on an antenna port is conveyed can be inferred from a channel on which another symbol on the same antenna port is conveyed. For example, the channel may correspond to a physical channel. For example, the symbol may correspond to an OFDM symbol. For example, the symbol may correspond to a resource block unit. For example, the symbol may correspond to a resource element.

[0049] Two antenna ports are said to be Quasi Co-Located (QCL) if the large-scale characteristics of the channel through which symbols on one antenna port are conveyed can be inferred from the channel through which symbols on the other antenna port are conveyed. The large-scale characteristics include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters.

[0050] Carrier aggregation may be communication using multiple aggregated serving cells. Carrier aggregation may be communication using multiple aggregated component carriers. Carrier aggregation may be communication using multiple aggregated downlink component carriers. Carrier aggregation may be communication using multiple aggregated uplink component carriers.

[0051] Fig. 5 is a schematic block diagram showing a configuration example of a 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 a part or all of a radio transmission / reception unit (physical layer processing unit) 30 and an upper layer processing unit 34. The radio transmission / reception unit 30 includes at least a part or all of an antenna unit 31, an RF unit 32 (radio frequency unit 32), and a baseband unit 33. The upper layer processing unit 34 includes at least a part or all of a media access control layer processing unit 35 and a radio resource control (RRC) layer processing unit 36.

[0052] The wireless transceiver 30 includes at least a part or all of a wireless transmitter 30a and a wireless receiver 30b. The configuration of a baseband unit 33 included in the wireless transmitter 30a and the configuration of the baseband unit 33 included in the wireless receiver 30b may be the same as or different from each other. The configuration of an RF unit 32 included in the wireless transmitter 30a and the configuration of an RF unit 32 included in the wireless receiver 30b may be the same as or different from each other. The configuration of an antenna unit 31 included in the wireless transmitter 30a and the configuration of an antenna unit 31 included in the wireless receiver 30b may be the same as or different from each other.

[0053] The higher layer processing unit 34 provides downlink data (transport blocks) to the radio transceiver unit 30 (or the radio transmitter unit 30a). The higher layer processing unit 34 executes processing of a media access control (MAC) layer, a packet data convergence protocol layer (PDCP layer), a radio link control layer (RLC layer), and / or an RRC layer.

[0054] The media access control layer processing unit 35 included in the upper layer processing unit 34 performs processing of the MAC layer.

[0055] A radio resource control layer processing unit 36 ​​included in the upper layer processing unit 34 performs processing of the RRC layer. The radio resource control layer processing unit 36 ​​manages various configuration information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 36 ​​configures the RRC parameters based on an RRC message received from the terminal device 1.

[0056] The wireless transceiver unit 30 (or the wireless transmitter unit 30a) performs processing such as encoding and modulation. The wireless transceiver unit 30 (or the wireless transmitter unit 30a) generates a physical signal by encoding and modulating downlink data. The wireless transceiver unit 30 (or the wireless transmitter unit 30a) converts the OFDM symbols of the physical signal into a baseband signal by converting it into a time-continuous signal. The wireless transceiver unit 30 (or the wireless transmitter unit 30a) transmits the baseband signal (or physical signal) to the terminal device 1 via a radio frequency. The wireless transceiver unit 30 (or the wireless transmitter unit 30a) can place the baseband signal (or physical signal) on a component carrier and transmit the baseband signal (or physical signal) to the terminal device 1.

[0057] The wireless transceiver unit 30 (or the wireless receiver unit 30b) performs processes such as demodulation and decoding. The wireless transceiver unit 30 (or the wireless receiver unit 30b) separates, demodulates, and decodes the received physical signal, and provides the decoded information to the upper layer processing unit 34. The wireless transceiver unit 30 (or the wireless receiver unit 30b) can execute a channel access procedure before transmitting the physical signal.

[0058] The RF unit 32 demodulates (down-converts) the physical signal received via the antenna unit 31 to a baseband signal and / or removes unnecessary frequency components. The RF unit 32 provides a processed analog signal to the baseband unit 33.

[0059] The baseband unit 33 converts the analog signal (radio frequency signal) input from the RF unit 32 into a digital signal (baseband signal). The baseband unit 33 separates a portion corresponding to a CP (cyclic prefix) from the digital signal. The baseband unit 33 performs a fast Fourier transform (FFT) on the digital signal from which the CP has been removed. The baseband unit 33 provides a physical signal in the frequency domain.

[0060] The baseband unit 33 performs an inverse fast Fourier transform (IFFT) on the downlink data to generate OFDM symbols, adds a CP to the generated OFDM symbols, generates a digital signal (baseband signal), and converts the digital signal into an analog signal. The baseband unit 33 provides the analog signal to the RF unit 32.

[0061] The RF unit 32 removes unnecessary frequency components from the analog signal (radio frequency signal) input from the baseband unit 33, up-converts the analog signal to a radio frequency, and transmits it via the antenna unit 31. The RF unit 32 may have a function of controlling transmission power. The RF unit 32 is also called a transmission power control unit.

[0062] At least one or more serving cells (or one or more component carriers, one or more downlink component carriers, one or more uplink component carriers) can be configured for the terminal device 1.

[0063] Each of the serving cells configured for the terminal device 1 may be any of a PCell (primary cell), a PSCell (primary SCG cell), and a SCell (secondary cell).

[0064] The 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 executes an initial connection establishment procedure or a connection re-establishment procedure.

[0065] The PSCell is a serving cell included in an SCG (Secondary Cell Group). The PSCell is a serving cell to which random access is performed by the terminal device 1 in a synchronous reconfiguration procedure (synchronous reconfiguration).

[0066] An SCell may be included in either an MCG or an SCG.

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

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

[0069] Among one or more downlink BWPs configured for a serving cell (or a downlink component carrier), one downlink BWP may be configured as an active downlink BWP (or one downlink BWP may be activated). Among one or more uplink BWPs configured for a serving cell (or an uplink component carrier), one uplink BWP may be configured as an active uplink BWP (or one uplink BWP may be activated).

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

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

[0072] The switching of the downlink BWP deactivates the active downlink BWP and activates one of the inactive downlink BWPs other than the active downlink BWP. The switching of the downlink BWP may be controlled by a BWP field included in the downlink control information. The switching of the downlink BWP may be controlled based on higher layer parameters.

[0073] The switching of the uplink BWP is used to deactivate the active uplink BWP and to deactivate any active uplink BWPs other than the active uplink BWP. The switching of the uplink BWP may be controlled by the BWP field included in the downlink control information. The switching of the uplink BWP may be controlled based on higher layer parameters.

[0074] Among one or more downlink BWPs configured for a serving cell, two or more downlink BWPs may not be configured as active downlink BWPs. For a serving cell, one downlink BWP may be active at a particular time.

[0075] Among one or more uplink BWPs configured for a serving cell, two or more uplink BWPs may not be configured as active uplink BWPs. For a serving cell, one uplink BWP may be active at a particular time.

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

[0077] The wireless transceiver 10 includes at least a part or all of a wireless transmitter 10a and a wireless receiver 10b. The configuration of a baseband unit 13 included in the wireless transmitter 10a and the configuration of the baseband unit 13 included in the wireless receiver 10b may be the same as or different from each other. The configuration of an RF unit 12 included in the wireless transmitter 10a and the configuration of an RF unit 12 included in the wireless receiver 10b may be the same as or different from each other. The configuration of an antenna unit 11 included in the wireless transmitter 10a and the configuration of an antenna unit 11 included in the wireless receiver 10b may be the same as or different from each other.

[0078] The upper layer processing unit 14 provides uplink data (transport blocks) to the radio transceiver unit 10 (or the radio transmitter unit 10a). The upper layer processing unit 14 performs processing of the MAC layer, the packet data integration protocol layer, the radio link control layer, and / or the RRC layer.

[0079] The media access control layer processing unit 15 included in the upper layer processing unit 14 performs processing of the MAC layer.

[0080] A radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs processing of the RRC layer. The radio resource control layer processing unit 16 manages various configuration information / parameters (RRC parameters) of the terminal device 1. The radio resource control layer processing unit 16 configures the RRC parameters based on an RRC message received from the base station device 3.

[0081] The wireless transceiver 10 (or the wireless transmitter 10a) performs processing such as encoding and modulation. The wireless transceiver 10 (or the wireless transmitter 10a) generates a physical signal by encoding and modulating uplink data. The wireless transceiver 10 (or the wireless transmitter 10a) converts OFDM symbols in the physical signal into a baseband signal by converting it into a time-continuous signal. The wireless transceiver 10 (or the wireless transmitter 10a) transmits the baseband signal (or physical signal) to the base station device 3 via a radio frequency. The wireless transceiver 10 (or the wireless transmitter 10a) can place the baseband signal (or physical signal) on a BWP (active uplink BWP) and transmit the baseband signal (or physical signal) to the base station device 3.

[0082] The wireless transceiver unit 10 (or the wireless receiver unit 10b) performs processes such as demodulation and decoding. The wireless transceiver unit 10 (or the wireless receiver unit 10b) can receive physical signals in the BWP (active downlink BWP) of the serving cell. The wireless transceiver unit 10 (or the wireless receiver unit 10b) separates, demodulates, and decodes the received physical signals, and provides the decoded information to the upper layer processing unit 14. The wireless transceiver unit 10 (or the wireless receiver unit 10b) can perform a channel access procedure before transmitting the physical signals.

[0083] The RF unit 12 demodulates (down-converts) the physical signal received via the antenna unit 11 to a baseband signal and / or removes unnecessary frequency components. The RF unit 12 provides the processed analog signal to the baseband unit 13.

[0084] The baseband unit 13 converts the analog signal (radio frequency signal) input from the RF unit 12 into a digital signal (baseband signal). The baseband unit 13 separates a portion corresponding to the CP from the digital signal, performs a fast Fourier transform on the digital signal from which the CP has been removed, and provides a physical signal in the frequency domain.

[0085] The baseband unit 13 performs an inverse fast Fourier transform on the uplink data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a digital signal (baseband signal), and converts the digital signal into an analog signal. The baseband unit 13 provides the analog signal to the RF unit 12.

[0086] The RF unit 12 removes unnecessary frequency components from the analog signal (radio frequency signal) input from the baseband unit 13, up-converts the analog signal to a radio frequency, and transmits it via the antenna unit 11. The RF unit 12 may have a function of controlling transmission power. The RF unit 12 is also called a transmission power control unit.

[0087] The physical signals (signals) will be explained below.

[0088] The physical signal is a general term for a downlink physical channel, a downlink physical signal, an uplink physical channel, and an uplink physical channel. The physical channel is a general term for a downlink physical channel and an uplink physical channel.

[0089] The uplink physical channel may correspond to a set of resource elements carrying information originating from a higher layer and / or uplink control information. The uplink physical channel may be a physical channel used in an uplink component carrier. The uplink physical channel may be transmitted by a terminal device 1. The uplink physical channel may be received by a base station device 3. In a wireless communication system according to an aspect of the present embodiment, at least some or all of a PUCCH (Physical Uplink Control Channel), a PUSCH (Physical Uplink Shared Channel), and a PRACH (Physical Random Access Channel) may be used.

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

[0091] The uplink control information (uplink control information bits, uplink control information sequence, uplink control information type) includes at least a part or all of channel state information (CSI), a scheduling request (SR), and a hybrid automatic repeat request ACKnowledgement (HARQ-ACK).

[0092] The channel state information is conveyed by using channel state information bits or channel state information sequences, the scheduling request is also referred to as a scheduling request bit or a scheduling request sequence, and the HARQ-ACK information is also referred to as a HARQ-ACK information bit or a HARQ-ACK information sequence.

[0093] The HARQ-ACK information may include a HARQ-ACK status corresponding to a transport block (TB: Transport Block, MAC PDU: Media Access Control Protocol Data Unit, DL-SCH: Downlink Shared Channel, UL-SCH: Uplink Shared Channel, PDSCH: Physical Downlink Shared Channel, PUSCH: Physical Uplink Shared Channel). The HARQ-ACK status may indicate an ACK (positive acknowledgement) or a NACK (negative acknowledgement) corresponding to the transport block. An ACK may indicate that the transport block has been successfully decoded. A NACK may indicate that the transport block has not been successfully decoded. The HARQ-ACK information may include a HARQ-ACK codebook that includes one or more HARQ-ACK statuses (or HARQ-ACK bits).

[0094] For example, the correspondence between HARQ-ACK information and a transport block may mean that the HARQ-ACK information and the PDSCH used for transmitting a transport block correspond.

[0095] The HARQ-ACK status may indicate an ACK or NACK corresponding to one CBG (Code Block Group) included in a transport block.

[0096] The scheduling request may be used at least to request PUSCH (or UL-SCH) resources for a new transmission. The scheduling request may be used to indicate either a positive SR or a negative SR. The fact that the scheduling request indicates a positive SR is also referred to as "a positive SR is transmitted". A positive SR may indicate that PUSCH (or UL-SCH) resources for an initial transmission are requested by the terminal device 1. A positive SR may indicate that an upper layer triggers a scheduling request. A positive SR may be transmitted when an upper layer instructs to transmit a scheduling request. The fact that the scheduling request bit indicates a negative SR is also referred to as "a negative SR is transmitted". A negative SR may indicate that PUSCH (or UL-SCH) resources for an initial transmission are not requested by the terminal device 1. A negative SR may indicate that an upper layer does not trigger a scheduling request. A negative SR may be transmitted when an upper layer is not instructed to transmit a scheduling request.

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

[0098] The channel state information may be provided based at least on reception of one or more physical signals (e.g., one or more CSI-RS) used for at least channel measurement. The channel state information may be selected by the terminal device 1 based at least on reception of one or more physical signals used for channel measurement. The channel measurement may include an interference measurement.

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

[0100] The PUSCH may be used to transmit uplink data (transport block) and / or uplink control information. The PUSCH may be used to transmit uplink data (transport block) corresponding to the UL-SCH and / or uplink control information. The PUSCH may be used to transmit uplink data (transport block) and / or uplink control information. The PUSCH may be used to transmit uplink data (transport block) corresponding to the UL-SCH and / or uplink control information. The uplink data (transport block) may be arranged in the PUSCH. The uplink data (transport block) corresponding to the UL-SCH may be arranged in the PUSCH. The uplink control information may be arranged in the PUSCH. The terminal device 1 can transmit the PUSCH in which the uplink data (transport block) and / or the uplink control information is arranged. The base station device 3 can receive the PUSCH in which the uplink data (transport block) and / or the uplink control information is arranged.

[0101] The PRACH may be used to transmit a random access preamble. The PRACH may be used to convey a random access preamble. u,v (n) is X u,v (n)=X u (mod(n+C v ,L ra )). X u X may be a ZC sequence (Zadoff-Chu sequence). u X u =exp(-jpui(i+1) / L ra), where j is the imaginary unit. p is the ratio of circumference to circumference. C v L corresponds to the cyclic shift of the PRACH. RA L corresponds to the length of the PRACH. RA may be 839 or 139 or another value. i ranges from 0 to L RA where u is an integer in the range of -1. u is a sequence index of the PRACH. The terminal device 1 can transmit the PRACH. The base station device 3 can receive the PRACH.

[0102] For a given PRACH opportunity, 64 random access preambles are defined. The random access preambles are at least the cyclic shift C v and is specified (determined, given) based on the sequence index u of the PRACH.

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

[0104] UL DMRS is a general term for PUSCH DMRS and PUCCH DMRS.

[0105] The set of antenna ports for DMRS for PUSCH (DMRS associated with PUSCH, DMRS included in PUSCH, DMRS corresponding to PUSCH) may be given based on the set of antenna ports for PUSCH, i.e., the set of DMRS antenna ports for PUSCH may be the same as the set of antenna ports for PUSCH.

[0106] A transmission of the PUSCH and a transmission of the DMRS for the PUSCH may be indicated (or scheduled) by one DCI format. The PUSCH and the DMRS for the PUSCH may be collectively referred to as the PUSCH. A transmission of the PUSCH may be a transmission of the PUSCH and the DMRS for the PUSCH.

[0107] The PUSCH may be estimated from the DMRS for the PUSCH, i.e., the propagation path of the PUSCH may be estimated from the DMRS for the PUSCH.

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

[0109] The transmission of the PUCCH and the transmission of the DMRS for the PUCCH may be indicated (or scheduled) by one DCI format. The arrangement of the PUCCH in resource elements (resource element mapping) and / or the arrangement of the DMRS within the resource elements for the PUCCH may be provided by at least one PUCCH format. The PUCCH and the DMRS for the PUCCH may be collectively referred to as the PUCCH. The transmission of the PUCCH may be the transmission of the PUCCH and the DMRS for the PUCCH.

[0110] The PUCCH may be estimated from the DMRS for the PUCCH, i.e., the propagation path of the PUCCH may be estimated from the DMRS for the PUCCH.

[0111] The downlink physical channel may correspond to a set of resource elements carrying information originating from a higher layer and / or downlink control information. The downlink physical channel may be a physical channel used for a downlink component carrier. The base station device 3 can transmit the downlink physical channel. The terminal device 1 can receive the downlink physical channel. In the wireless communication system according to one aspect of the present embodiment, at least some or all of a PBCH (Physical Broadcast Channel), a PDCCH (Physical Downlink Control Channel), and a PDSCH (Physical Downlink Shared Channel) may be used.

[0112] The PBCH may be used to transmit a MIB (Master Information Block) and / or physical layer control information. The physical layer control information is a type of downlink control information. The PBCH may be transmitted to deliver the MIB and / or physical layer control information. The BCH may be mapped to (or correspond to) the PBCH. The terminal device 1 may receive the PBCH. The base station device 3 may transmit the PBCH. The physical layer control information is also referred to as the PBCH payload, which is related to the PBCH payload and timing. The MIB may include one or more higher layer parameters.

[0113] The physical layer control information includes 8 bits. The physical layer control information may include at least a part or all of 0A to 0D. 0A is radio frame information. 0B is half radio frame information (half system frame information). 0C is SS / PBCH block index information. 0D is subcarrier offset information.

[0114] The radio frame information is used to indicate the radio frame in which the PBCH is transmitted (the radio frame including the slot in which the PBCH is transmitted). The radio frame information is represented by 4 bits. The radio frame information can be represented by 4 bits of the radio frame indicator. The radio frame indicator may include 10 bits. For example, the radio frame indicator may be used at least to identify radio frames from index 0 to index 1023.

[0115] The half radio frame information is used to indicate whether the PBCH is transmitted in the first 5 subframes or the second 5 subframes of a radio frame in which the PBCH is transmitted, where the half radio frame may be configured to include 5 subframes. The half radio frame may be configured by the first half 5 subframes of the 10 subframes included in the radio frame. The half radio frame may be configured by the second half 5 subframes of the 10 subframes included in the radio frame.

[0116] The SS / PBCH block index information is used to indicate an SS / PBCH block index. The SS / PBCH block index information may be represented by 3 bits. The SS / PBCH block index information may consist of 3 bits of the SS / PBCH block index indicator. The SS / PBCH block index indicator may include 6 bits. The SS / PBCH block index indicator may be used at least to identify SS / PBCH blocks from index 0 to index 63 (or index 0 to index 3, index 0 to index 7, index 0 to index 9, index 0 to index 19, etc.).

[0117] The subcarrier offset information is used to indicate a subcarrier offset. The subcarrier offset information may be used to indicate a difference between the first subcarrier in which the PBCH is located and the first subcarrier in which the control resource set having index 0 is located.

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

[0119] The downlink control information may correspond to a DCI format. The downlink control information may be included in the DCI format. The downlink control information may be arranged in each field of the DCI format.

[0120] The DCI format is a general term for DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1. The uplink DCI format is a general term for DCI format 0_0 and DCI format 0_1. The downlink DCI format is a general term for DCI format 1_0 and DCI format 1_1.

[0121] DCI format 0_0 is at least used to schedule a PUSCH of a cell (or a PUSCH arranged on a cell). DCI format 0_0 includes at least some or all of fields 1A to 1E. 1A is a DCI format identification field (an identifier field for a DCI format). 1B is a frequency domain resource allocation field (FDRA field, FDRA information field). 1C is a time domain resource allocation field (TDRA field, TDRA information field). 1D is a frequency hopping flag field. 1E is an MCS field (Modulation-and-Coding-Scheme field).

[0122] The frequency domain resource allocation field may be referred to as a FDRA field or an FDRA information field.

[0123] The time domain resource allocation field may be referred to as a TDRA field or a TDRA information field.

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

[0125] The frequency domain resource allocation field included in DCI format 0_0 may be used at least to indicate an allocation of frequency resources for the PUSCH. The frequency domain resource allocation field included in DCI format 0_0 may be used at least to indicate an allocation of frequency resources for the PUSCH scheduled by DCI format 0_0.

[0126] The time domain resource allocation field included in DCI format 0_0 may be used at least to indicate an allocation of time resources for the PUSCH. The time domain resource allocation field included in DCI format 0_0 may be used at least to indicate an allocation of time resources for the PUSCH scheduled by DCI format 0_0.

[0127] The frequency hopping flag field may be used at least to indicate whether frequency hopping is applied to the PUSCH. The frequency hopping flag field may be used at least to indicate whether frequency hopping is applied to the PUSCH scheduled by DCI format 0_0.

[0128] The MCS field included in DCI format 0_0 may be used at least to indicate a modulation scheme for PUSCH and / or a part or all of a target coding rate for PUSCH. The MCS field included in DCI format 0_0 may be used at least to indicate a modulation scheme for PUSCH scheduled by DCI format 0_0 and / or a part or all of a target coding rate for PUSCH. A transport block size (TBS) of the PUSCH may be given based on at least a target coding rate and a part or all of a modulation scheme for PUSCH. The modulation scheme may include at least one of a modulation order, a target coding rate, and a spectral efficiency.

[0129] DCI format 0_0 may not include fields used for CSI requests, i.e., no CSI may be requested by DCI format 0_0.

[0130] DCI format 0_0 may not include a carrier indicator field. The uplink component carrier on which the PUSCH scheduled by DCI format 0_0 is arranged may be the same as the uplink component carrier on which the PDCCH including DCI format 0_0 is arranged.

[0131] DCI format 0_0 may not include a BWP field. The uplink BWP in which a PUSCH scheduled by DCI format 0_0 is arranged may be the same as the uplink BWP in which a PDCCH including DCI format 0_0 is arranged.

[0132] DCI format 0_1 ​​is used for scheduling at least PUSCH for (or located on) a cell. DCI format 0_1 ​​includes at least some or all of fields 2A to 2H. 2A is a DCI format identification field. 2B is a frequency domain resource allocation field. 2C is a time domain resource allocation field. 2D is a frequency hopping flag field. 2E is an MCS field. 2F is a CSI request field. 2G is a BWP field. 2H is a carrier indicator field.

[0133] The DCI format identification field included in DCI format 0_1 ​​may indicate 0 (or may indicate that DCI format 0_1 ​​is an uplink DCI format).

[0134] The frequency domain resource allocation field included in DCI format 0_1 ​​may be used at least to indicate the allocation of frequency resources for the PUSCH. The frequency domain resource allocation field included in DCI format 0_1 ​​may be used at least to indicate the allocation of frequency resources for the PUSCH scheduled by the DCI format.

[0135] The time domain resource allocation field included in DCI format 0_1 ​​may be used at least to indicate the allocation of time resources for the PUSCH. The time domain resource allocation field included in DCI format 0_1 ​​may be used at least to indicate the allocation of time resources for the PUSCH scheduled by DCI format 0_1.

[0136] The frequency hopping flag field may be used at least to indicate whether frequency hopping is applied to the PUSCH scheduled by DCI format 0_1.

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

[0138] If DCI format 0_1 ​​includes a BWP field, the BWP field may be used to indicate an uplink BWP in which a PUSCH scheduled by DCI format 0_1 ​​is arranged. If DCI format 0_1 ​​does not include a BWP field, the uplink BWP in which a PUSCH is arranged may be an active uplink BWP. If the number of uplink BWPs configured in the terminal device 1 in the uplink component carrier is two or more, the number of bits for the BWP field included in DCI format 0_1 ​​used to schedule a PUSCH arranged on the uplink component carrier may be one or more. If the number of uplink BWPs configured in the terminal device 1 in the uplink component carrier is one, the number of bits for the BWP field included in DCI format 0_1 ​​used to schedule a PUSCH arranged on the uplink component carrier may be zero.

[0139] The CSI request field is at least used to indicate a CSI report.

[0140] When DCI format 0_1 ​​includes a carrier indicator field, the carrier indicator field may be used to indicate an uplink component carrier (or a serving cell) in which a PUSCH is arranged. When DCI format 0_1 ​​does not include a carrier indicator field, the serving cell in which a PUSCH is arranged may be the same as the serving cell in which a PDCCH including a DCI format 0_1 ​​used for scheduling a PUSCH is arranged. When the number of uplink component carriers (or the number of serving cells) configured in a terminal device 1 in a serving cell group is two or more (when uplink carrier aggregation operates in a serving cell group) or when cross-carrier scheduling is configured for a serving cell group, the number of bits of the carrier indicator field included in DCI format 0_1 ​​used for scheduling a PUSCH arranged in a serving cell group may be one or more (for example, three). If the number of uplink component carriers (or the number of serving cells) configured in a terminal device 1 in a serving cell group is 1 (or if uplink carrier aggregation is not operating in the serving cell group), or if cross-carrier scheduling is not configured for the serving cell group, the number of bits of the carrier indicator field included in DCI format 0_1 ​​used for scheduling the PUSCH placed in the serving cell group may be zero.

[0141] DCI format 1_0 is used at least for scheduling the PDSCH of a cell (located on the cell). DCI format 1_0 includes at least some or all of fields 3A to 3F. 3A is a DCI format identification field. 3B is a frequency domain resource allocation field. 3C is a time domain resource allocation field. 3D is an MCS field. 3E is a PDSCH-to-HARQ-feedback indicator field. 3F is a PUCCH resource indicator field.

[0142] The DCI format identification field included in DCI format 1_0 may indicate 1 (or may indicate that DCI format 1_0 is a downlink DCI format).

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

[0144] The time domain resource allocation field included in DCI format 1_0 may be used at least to indicate an allocation of time resources for a PDSCH. The time domain resource allocation field included in DCI format 1_0 may be used at least to indicate an allocation of time resources for a PDSCH scheduled by DCI format 1_0.

[0145] The MCS field included in DCI format 1_0 may be used at least to indicate a modulation scheme of the PDSCH and / or a part or all of a target coding rate for the PDSCH. The MCS field included in DCI format 1_0 may be used at least to indicate a modulation scheme of the PDSCH scheduled by DCI format 1_0 and / or a part or all of a target coding rate for the PDSCH. The size of the transport block (TBS: transport block size) of the PDSCH may be given based on at least a part or all of the target coding rate and the modulation scheme for the PDSCH.

[0146] The PDSCH-to-HARQ feedback timing indicator field may be used at least to indicate an offset (K1) from a slot in which the last OFDM symbol of the PDSCH scheduled by DCI format 1_0 is included in another slot in which the first OFDM symbol of the PUCCH triggered by DCI format 1_0 is included.

[0147] The PUCCH resource indicator field may be a field that indicates an index of any one or more PUCCH resources included in a PUCCH resource set for PUCCH transmission. The PUCCH resource set may include one or more PUCCH resources. The PUCCH resource indicator field may trigger a PUCCH transmission on the PUCCH resource indicated based at least on the PUCCH resource indicator field.

[0148] DCI format 1_0 may not include a carrier indicator field. The downlink component carrier on which the PDSCH scheduled by DCI format 1_0 is arranged may be the same as the downlink component carrier on which the PDCCH including DCI format 1_0 is arranged.

[0149] DCI format 1_0 may not include a BWP field. A downlink BWP in which a PDSCH scheduled by DCI format 1_0 is arranged may be the same as a downlink BWP in which a PDCCH including DCI format 1_0 is arranged.

[0150] DCI format 1_1 is used for scheduling at least PDSCH for (or located on) a cell. DCI format 1_1 includes at least some or all of fields 4A to 4H. 4A is a DCI format identification field. 4B is a frequency domain resource allocation field. 4C is a time domain resource allocation field. 4D is an MCS field. 4E is a PDSCH-to-HARQ-feedback indicator field. 4F is a PUCCH resource indicator field. 4G is a BWP field. 4H is a carrier indicator field.

[0151] The DCI format identification field included in DCI format 1_1 may indicate 1 (or may indicate that DCI format 1_1 is a downlink DCI format).

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

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

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

[0155] If DCI format 1_1 includes a PDSCH-to-HARQ feedback timing indicator field, the PDSCH-to-HARQ feedback timing indicator field indicates an offset (K1) from a slot including the last OFDM symbol of the PDSCH scheduled by DCI format 1_1 to another slot including the first OFDM symbol of the PUCCH triggered by DCI format 1_1. If DCI format 1_1 does not include a PDSCH-to-HARQ feedback timing indicator field, the offset from a slot including the last OFDM symbol of the PDSCH scheduled by DCI format 1_1 to another slot where the first OFDM symbol of the PUCCH triggered by DCI format 1_1 is identified by higher layer parameters.

[0156] If DCI format 1_1 includes a BWP field, the BWP field may be used to indicate a downlink BWP in which a PDSCH scheduled by DCI format 1_1 is arranged. If DCI format 1_1 does not include a BWP field, the downlink BWP in which a PDSCH is arranged may be an active downlink BWP. If the number of downlink BWPs configured in the terminal device 1 in the downlink component carrier is two or more, the number of bits of the BWP field included in DCI format 1_1 used to schedule a PDSCH arranged on the downlink component carrier may be one or more. If the number of downlink BWPs configured in the terminal device 1 in the downlink component carrier is one, the number of bits of the BWP field included in DCI format 1_1 used to schedule a PDSCH arranged on the downlink component carrier may be zero.

[0157] When DCI format 1_1 includes a carrier indicator field, the carrier indicator field may be used to indicate a downlink component carrier (or serving cell) on which the PDSCH is arranged. When DCI format 1_1 does not include a carrier indicator field, the downlink component carrier (or serving cell) on which the PDSCH is arranged may be the same as the downlink component carrier (or serving cell) on which the PDCCH including the DCI format 1_1 used for scheduling the PDSCH is arranged. When the number of downlink component carriers (or the number of serving cells) configured in the terminal device 1 in the serving cell group is two or more (when downlink carrier aggregation operates in the serving cell group) or when cross-carrier scheduling is configured for the serving cell group, the number of bits of the carrier indicator field included in DCI format 1_1 used to schedule the PDSCH arranged in the serving cell group may be one or more (for example, three). If the number of downlink component carriers (or the number of serving cells) configured in a terminal device 1 in a serving cell group is 1 (or if downlink carrier aggregation does not operate in the serving cell group), or if cross-carrier scheduling is not configured for the serving cell group, the number of bits of the carrier indicator field included in DCI format 1_1 used for scheduling the PDSCH placed in the serving cell group may be zero.

[0158] The PDSCH may be used to transmit one or more transport blocks. The PDSCH may be used to transmit one or more transport blocks corresponding to the DL-SCH. The PDSCH may be used to convey one or more transport blocks. The PDSCH may be used to convey one or more transport blocks corresponding to the DL-SCH. One or more transport blocks may be arranged in the PDSCH. One or more transport blocks corresponding to the DL-SCH may be arranged in the PDSCH. The base station device 3 may transmit the PDSCH. The terminal device 1 may receive the PDSCH.

[0159] A downlink physical signal may correspond to a set of resource elements. A downlink physical signal cannot carry information generated at higher layers. The downlink physical signal may be a physical signal used in a downlink component carrier. The downlink physical signal may be transmitted by a base station device 3. The downlink physical signal may be transmitted by a terminal device 1. In a wireless communication system according to an aspect of the present embodiment, at least a part or all of an SS (synchronization signal), DL DMRS (DownLink DeModulation Reference Signal), CSI-RS (Channel State Information Reference Signal), and DL PTRS (DownLink Phase Tracking Reference Signal) may be used.

[0160] The synchronization signal may be used for synchronization in the frequency domain and / or the time domain of the downlink by at least the terminal device 1. The synchronization signal is a general term for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS).

[0161] FIG. 7 is a diagram showing an example of the configuration of an SS / PBCH block according to one embodiment of the present invention. In FIG. 7, the horizontal axis represents the time domain (OFDM symbol index l sym), with the vertical axis representing the frequency domain. The shaded blocks represent a set of resource elements for the PSS. The gridded blocks represent a set of resource elements for the SSS. Additionally, the horizontally lined blocks represent a set of resource elements for the PBCH and a set of resource elements for the DMRS for the PBCH (DMRS associated with the PBCH, DMRS included in the PBCH, and DMRS corresponding to the PBCH).

[0162] As shown in FIG. 7, the SS / PBCH block includes a PSS, an SSS, and a PBCH. The SS / PBCH block includes four consecutive OFDM symbols. The SS / PBCH block includes 240 subcarriers. The PSS is assigned to the 57th to 183rd subcarriers in the first OFDM symbol. The SSS is assigned to the 57th to 183rd subcarriers in the third OFDM symbol. The 1st to 56th subcarriers of the first OFDM symbol may be set to zero. The 184th to 240th subcarriers of the first OFDM symbol may be set to zero. The 49th to 56th subcarriers of the third OFDM symbol may be set to zero. The 184th to 192nd subcarriers of the third OFDM symbol may be set to zero. In the 1st to 240th subcarriers of the second OFDM symbol, the PBCH is assigned to subcarriers to which the DMRS of the PBCH is not assigned. In the 1st to 48th subcarriers of the third OFDM symbol, the PBCH is assigned to subcarriers to which the DMRS of the PBCH is not assigned. In the 193rd to 240th subcarriers of the third OFDM symbol, the PBCH is assigned to subcarriers to which the DMRS of the PBCH is not assigned. In the 1st to 240th subcarriers of the fourth OFDM symbol, the PBCH is assigned to subcarriers to which the DMRS of the PBCH is not assigned.

[0163] The antenna ports for the PSS, SSS, PBCH, and PBCH DMRS within an SS / PBCH block may be the same.

[0164] The PBCH may be estimated from the DMRS for the PBCH, where the channel on which a symbol of the PBCH on an antenna port is carried may be inferred from the channel on which another symbol of the DM-RS on an antenna port is carried with the same SS / PBCH block index only if the two symbols are within an SS / PBCH block transmitted in the same slot.

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

[0166] The set of antenna ports for the DMRS for the PDSCH (DMRS associated with the PDSCH, DMRS included in the PDSCH, DMRS corresponding to the PDSCH) may be given based on the set of antenna ports for the PDSCH. The set of antenna ports for the DMRS for the PDSCH may be the same as the set of antenna ports for the PDSCH.

[0167] A transmission of the PDSCH and a transmission of the DMRS for the PDSCH may be indicated (or scheduled) by one DCI format. The PDSCH and the DMRS for the PDSCH may be collectively referred to as the PDSCH. A transmission of the PDSCH may be a transmission of the PDSCH and a DMRS for the PDSCH.

[0168] The PDSCH may be estimated from the DMRS for the PDSCH. For a DM-RS associated with a PDSCH, the channel on which a symbol of the PDSCH on one antenna port is carried may be inferred from the channel on which another symbol of the DM-RS on the antenna port is carried only if the two symbols are in the same resource as the scheduled PDSCH, in the same slot, and in the same precoding resource group (PRG).

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

[0170] The PDCCH may be estimated from the DMRS for the PDCCH. For a DM-RS associated with the PDCCH, the channel on which a symbol of the PDCCH on one antenna port is carried may be inferred from the channel on which another symbol of the DM-RS on the same antenna port is carried only if the two symbols are within resources where the UE can assume that it is using the same precoding (i.e., within resources within a REG bundle).

[0171] BCH (Broadcast CHannel), UL-SCH (Uplink-Shared CHannel) and DL-SCH (Downlink-Shared CHannel) are transport channels. A channel used in the MAC layer is called a transport channel. The unit of the transport channel used in the MAC layer is also called a transport block (TB) or a MAC PDU (Protocol Data Unit). In the MAC layer, HARQ (Hybrid Automatic Repeat Request) control is performed for each transport block. A transport block is a unit of data delivered to the physical layer by the MAC layer. In the physical layer, a transport block is mapped to a codeword, and a modulation process is performed for each codeword.

[0172] One UL-SCH and one DL-SCH may be provided per serving cell. The BCH may be provided for the PCell. The BCH may not be provided for the PSCell and SCell.

[0173] BCCH (Broadcast Control CHannel), CCCH (Common Control CHannel), and DCCH (Dedicated Control CHannel) are logical channels. BCCH is an RRC layer channel used to distribute MIB or system information. CCCH may be used to transmit common RRC messages in multiple terminal devices 1. CCCH may be used for terminal devices 1 that are not connected by RRC. DCCH may be used at least to transmit dedicated RRC messages to terminal devices 1. DCCH may be used for terminal devices 1 that are in RRC connected mode.

[0174] An RRC message includes one or more RRC parameters (information elements, higher layer parameters). For example, an RRC message may include a MIB. For example, an RRC message may include system information (SIB: System Information Block, MIB). SIB is a general term for various types of SIBs (e.g., SIB1, SIB2). For example, an RRC message may include a message corresponding to a CCCH. For example, an RRC message may include a message corresponding to a DCCH. An RRC message is a general term for a common RRC message and a dedicated RRC message.

[0175] The BCCH in the logical channel can be mapped to the BCH or DL-SCH in the transport channel, the CCCH in the logical channel can be mapped to the DL-SCH or UL-SCH in the transport channel, and the DCCH in the logical channel can be mapped to the DL-SCH or UL-SCH in the transport channel.

[0176] The UL-SCH in the transport channel may be mapped to the PUSCH in the physical channel, the DL-SCH in the transport channel may be mapped to the PDSCH in the physical channel, and the BCH in the transport channel may be mapped to the PBCH in the physical channel.

[0177] The upper layer parameters are parameters included in an RRC message or a MAC CE (Medium Access Control Element). The upper layer parameters are a collective term for information included in an MIB, system information, a message corresponding to a CCCH, a message corresponding to a DCCH, and a MAC CE. When the upper layer parameters are parameters included in an RRC message, the upper layer parameters may be referred to as RRC parameters or RRC configurations.

[0178] The higher layer parameters may be cell-specific parameters or UE-specific parameters. Cell-specific parameters are parameters that include common configurations within a cell. UE-specific parameters are parameters that include configurations that may be configured differently for each UE.

[0179] The base station device may indicate changes in cell-specific parameters due to reconfiguration by random access. The UE may change cell-specific parameters before triggering random access. The base station device may indicate changes in UE-specific parameters due to reconfiguration with or without random access. The UE may change UE-specific parameters before or after random access.

[0180] The procedure executed by the terminal device 1 includes at least a part or all of the following steps 5A to 5C: 5A is cell search, 5B is random access, and 5C is data communication.

[0181] Cell search is a procedure used by the terminal device 1 to synchronize with a cell in the time domain and / or frequency domain and to detect a physical cell identifier. Through cell search, the terminal device 1 can detect a physical cell ID by performing time domain and / or frequency domain synchronization with a cell.

[0182] The sequence of PSSs is given based on at least a physical cell ID. The sequence of SSSs is given based on at least a physical cell ID.

[0183] The SS / PBCH block candidate indicates a resource on which the transmission of the SS / PBCH block may occur. The SS / PBCH block may be transmitted on a resource indicated as the SS / PBCH block candidate. The base station device 3 may transmit the SS / PBCH block on the SS / PBCH block candidate. The terminal device 1 may receive (detect) the SS / PBCH block on the SS / PBCH block candidate.

[0184] The set of SS / PBCH block candidates in a half radio frame is also referred to as an SS burst set. The SS burst set is also referred to as a transmission window, an SS transmission window, or a discovery reference signal transmission window (DRS transmission window). The SS burst set is a general term including at least a first SS burst set and a second SS burst set.

[0185] The base station device 3 transmits SS / PBCH blocks of one or more indexes at a predetermined period. The terminal device 1 can detect at least one SS / PBCH block among the SS / PBCH blocks of one or more indexes. The terminal device 1 can attempt to decode the PBCH included in the SS / PBCH block.

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

[0187] Message 1 is a procedure for transmitting a PRACH by the terminal device 1. The terminal device 1 transmits a PRACH on one PRACH opportunity selected from one or more PRACH opportunities based on at least an index of an SS / PBCH block candidate detected based on a cell search.

[0188] Message 2 is a procedure in which the terminal device 1 attempts to detect DCI format 1_0 by a CRC (Cyclic Redundancy Check) scrambled by a RA-RNTI (Random Access-Radio Network Temporary Identifier). The terminal device 1 can attempt to detect DCI format 1_0 in a search space set.

[0189] Message 3 (Msg3) is a procedure for transmitting a PUSCH scheduled by a random access response grant included in DCI format 1_0 detected in the procedure of message 2. The random access response grant is indicated by a MAC CE included in a PDSCH scheduled by DCI format 1_0.

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

[0191] Message 3 PUSCH retransmissions are scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI (Temporary Cell-Radio Network Temporary Identifier).

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

[0193] Data communication is a general term for downlink communication and uplink communication.

[0194] In data communication, the terminal device 1 attempts to detect a PDCCH (attempts to monitor a PDCCH, monitors a PDCCH) in resources identified based at least on one or all of a control resource set and a search space set. Also referred to as "the terminal device 1 attempts to detect a PDCCH in a control resource set", "the terminal device 1 attempts to detect a PDCCH in a search space set", "the terminal device 1 attempts to detect a PDCCH candidate in a search space set", "the terminal device 1 attempts to detect a PDCCH candidate in a search space set", "the terminal device 1 attempts to detect a DCI format in a control resource set", or "the terminal device 1 attempts to detect a DCI format in a search space set". Monitoring the PDCCH may be equivalent to monitoring a DCI format in a PDCCH.

[0195] A control resource set is a set of resources constituted by a number of resource blocks and a given number of OFDM symbols in a slot.

[0196] The set of resources for the control resource set may be indicated by a higher layer parameter. The number of OFDM symbols included in the control resource set may be indicated by a higher layer parameter.

[0197] The PDCCH may also be referred to as a PDCCH candidate.

[0198] A search space set is defined as a set of PDCCH candidates, which may be a common search space (CSS) set or a UE-specific search space (USS) set.

[0199] The CSS set is a collective term for a PDCCH common search space set of type 0, a PDCCH common search space set of type O, a PDCCH common search space set of type 1, a PDCCH common search space set of type 2, and a PDCCH common search space set of type 3. The USS set may also be referred to as a UE-specific PDCCH search space set.

[0200] A PDCCH common search space set of type 0 may be used as a common search space set with index 0. A PDCCH common search space set of type 0 may be a common search space set with index 0.

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

[0202] For a search space set, some or all of 6A to 6C may be indicated by at least higher layer parameters. 6A is a PDCCH monitoring period. 6B is a PDCCH monitoring pattern in a slot. 6C is a PDCCH monitoring offset.

[0203] The monitoring opportunity for the search space set may correspond to one or more OFDM symbols to which a first OFDM symbol of a control resource set associated with the search space set is assigned. The monitoring opportunity for the search space set may correspond to a resource identified by the first OFDM symbol of a control resource set associated with the search space set. The monitoring opportunity for the search space set is provided based on at least some or all of the following: a PDCCH monitoring periodicity, a PDCCH monitoring pattern within a slot, and a PDCCH monitoring offset.

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

[0205] In Figure 8, blocks indicated by grid lines indicate search space set 91, blocks indicated by diagonal lines slanting upward to the right indicate search space set 92, blocks indicated by diagonal lines slanting upward to the left indicate search space set 93, and blocks indicated by horizontal lines indicate search space set 94.

[0206] 8, the PDCCH monitoring period of search space set 91 is set to 1 slot, the PDCCH monitoring offset of search space set 91 is set to 0 slot, and the PDCCH monitoring pattern of search space set 91 is [1,0,0,0,0,0,0,1,0,0,0,0,0,0,0]. That is, the monitoring opportunities of search space set 91 correspond to the first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDM symbol #7) in each slot.

[0207] 8, the PDCCH monitoring period of search space set 92 is set to 2 slots, the PDCCH monitoring offset of search space set 92 is set to 0 slots, and the PDCCH monitoring pattern of search space set 92 is [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring opportunity of search space set 92 corresponds to the first OFDM symbol (OFDM symbol #0) in each of the even-numbered slots.

[0208] 8, the PDCCH monitoring period of search space set 93 is set to 2 slots, the PDCCH monitoring offset of search space set 93 is set to 0 slots, and the PDCCH monitoring pattern of search space set 93 is set to [0,0,0,0,0,0,0,1,0,0,0,0,0,0,0]. That is, the monitoring opportunity of search space set 93 corresponds to the seventh OFDM symbol (OFDM symbol #8) in each of the even-numbered slots.

[0209] 8, the PDCCH monitoring period of search space set 94 is set to 2 slots, the PDCCH monitoring offset of search space set 94 is set to 1 slot, and the PDCCH monitoring pattern of search space set 94 is [1,0,0,0,0,0,0,0,0,0,0,0,0,0,0]. That is, the monitoring opportunity of search space set 94 corresponds to the first OFDM symbol (OFDM symbol #0) in each of the odd-numbered slots.

[0210] A Type 0 PDCCH common search space set may be used at least for DCI formats having a cyclic redundancy check (CRC) sequence scrambled by a System Information-Radio Network Temporary Identifier (SI-RNTI).

[0211] A Type 0a PDCCH common search space set may be used at least for DCI formats having a cyclic redundancy check sequence scrambled by the SI-RNTI.

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

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

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

[0215] The UE-specific search space set may be used at least for DCI formats having a CRC sequence scrambled by a C-RNTI, a Configured Scheduling-Radio Network Temporary Identifier (CS-RNTI), a Modulation and Coding Scheme-Radio Network Temporary Identifier (MCS-C-RNTI), or a Semi Persistent-Channel State Information-Radio Network Temporary Identifier (SP-CSI-RNTI).

[0216] A DCI format with a CRC sequence scrambled by a C-RNTI may be used to schedule a PUSCH (dynamically scheduled PUSCH (DG-PUSCH)). A DCI format with a CRC sequence scrambled by a CS-RNTI may be used to enable and / or disable Type 2 Configured Scheduling (CS). A PUSCH based on a CS may be referred to as a CS-PUSCH. A DCI format with a CRC sequence scrambled by a CS-RNTI may be used to schedule retransmissions of a CS-PUSCH (e.g., a Type 1 CS-PUSCH and / or a Type 2 CS-PUSCH).

[0217] In downlink communication, the terminal device 1 can detect a downlink DCI format. The detected downlink DCI format is used for at least PDSCH resource allocation. The detected downlink DCI format is also referred to as downlink allocation. The terminal device 1 attempts to receive a PDSCH. Based on the PUCCH resource indicated based on the detected downlink DCI format, a HARQ-ACK corresponding to the PDSCH (a HARQ-ACK corresponding to a transport block included in the PDSCH) can be reported to the base station device 3.

[0218] In uplink communication, the terminal device 1 can detect an uplink DCI format. The detected uplink DCI format is at least used for resource allocation of a PUSCH. The detected uplink DCI format is also referred to as an uplink grant. The terminal device 1 transmits a PUSCH.

[0219] The PUSCH transmission(s) can be dynamically scheduled by an UL grant in the DCI or the transmission can correspond to configured grant type 1 or type 2. Configured grant type 1 PUSCH transmissions are semi-statically configured to operate upon reception of higher layer parameters of configuredGrantConfig including rrc-ConfiguredUplinkGrant without detection of an UL grant in the DCI. Configured grant type 2 PUSCH transmissions are semi-persistently scheduled by an UL grant in a valid activation DCI according to their procedure(s) after reception of higher layer parameters configuredGrantConfig including no rrc-ConfiguredUplinkGrant. If configuredGrantConfigToAddModList is configured, two or more configured grant configurations of configured grant type 1 and / or configured grant type 2 can be active simultaneously on the active BWP of the serving cell.

[0220] Further details of resource allocation in the time domain of PUSCH scheduled by DCI format will be described. If UE (terminal device 1) is scheduled to transmit a transport block and not transmit a CSI report, or if UE is scheduled by DCI to transmit a transport block and CSI report(s) on PUSCH, the "Time domain resource allocation" field value m of DCI can provide row index m+1 in the allocated table. The determination of the resource allocation table to be used can be predefined and / or defined in RRC configuration. The indexed row of the resource allocation table can define the slot offset K2, the start and length indicator SLIV (start and length indicator) or directly the start symbol S and allocation length L to apply to PUSCH transmission, the PUSCH mapping type, and the number of repetitions (if the RRC parameter numberOfRepetitions is present in the resource allocation table). It should be noted that the RRC parameters are a kind of higher layer parameters.

[0221] For a PUSCH scheduled by DCI format 0_1, if the RRC parameter pusch-RepTypeIndicatorDCI-0-1 is set to "pusch-RepTypeB", the UE may apply the PUSCH repetition type B procedure when determining the time domain resource allocation. For a PUSCH scheduled by DCI format 0_2, if the RRC parameter pusch-RepTypeIndicatorDCI-0-2 is set to "pUSCH-RepTypeB", the UE may apply the PUSCH repetition type B procedure when determining the time domain resource allocation. Otherwise, the UE may apply the PUSCH repetition type A procedure when determining the time domain resource allocation for a PUSCH scheduled by PDCCH.

[0222] For PUSCH repetition type A, the starting symbol S relative to the start of the slot and the number of consecutive symbols L counted from the symbol S allocated for the PUSCH may be determined from the start and length indicator SLIV of the indexed row, where if (L-1)<7 then SLIV=14(L-1)+S, else SLIV=14(14-L+1+(14-1-S), where 0 <L<14-Sである。

[0223] For PUSCH repetition type A, when transmitting a scheduled PUSCH with DCI format 0_1 ​​or 0_2 in a PDCCH with C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1 scrambled CRC, the number of repetitions K may be determined as follows: If the RRC parameter numberOfRepetitions is present in the resource allocation table, the number of repetitions K may be equal to numberOfRepetitions, if the UE is configured with the RRC parameter pusch-AggregationFactor, the number of repetitions K may be equal to pusch-AggregationFactor, otherwise K=1.

[0224] If the UE is not capable of a particular coverage extension feature(s) (e.g., available slot-based PUSCH repetition count) or if the UE does not have a particular coverage extension configuration(s) (e.g., available slot-based PUSCH repetition count), the following may apply: For PUSCH repetition type A, if K>1, the same symbol allocation may be applied over K consecutive slots and the PUSCH may be limited to a single transmission tier. The UE may repeat a TB over K consecutive slots applying the same symbol allocation in each slot. The redundancy version applied to the nth transmission opportunity of a TB may be determined as described below, where (n=0, 1, ...K-1). For PUSCH repetition type A, a PUSCH transmission in a slot of a multi-slot PUSCH transmission may be omitted according to at least and / or at most conditions of a PUSCH priority-based procedure, a slot configuration-based procedure, a slot format-based procedure, and a cancellation indication-based procedure. For example, a slot may be determined to be available if it is available according to all conditions defined in these procedures, and / or a slot may be determined to be unavailable if it is unavailable according to at least one of the conditions defined in the procedures. K may be an integer.

[0225] The configuredGrantConfig may refer to the ConfiguredGrantConfig.

[0226] The configuredGrantConfig may be referred to as ConfiguredGrantConfig.

[0227] If the PUSCH resource allocation is semi-statically configured by the higher layer parameter configuredGrantConfig in the BWP-UplinkDedicated information element and the PUSCH transmission corresponds to a configured grant, the following higher layer parameters apply in the transmission:

[0228] For type 1 PUSCH transmission with configured grant, the following parameters are given in configuredGrantConfig unless otherwise mentioned, and for PUSCH repetition type determination, if the higher layer parameter pusch-RepTypeIndicator in rrc-ConfiguredUplinkGrant is configured and set to "pusch-RepTypeB", PUSCH repetition type B applies, otherwise PUSCH repetition type A applies.

[0229] The higher layer parameter pusch-RepTypeIndicator indicates whether the UE shall follow the PUSCH repetition type A or PUSCH repetition type B behavior for each Type 1 configured grant configuration. The value pusch-RepTypeA enables "PUSCH repetition type A" and the value pusch-RepTypeB enables "PUSCH repetition type B". The value pusch-RepTypeB is not configured at the same time as cg-nrofPUSCH-InSlot-r16 and cg-nrofSlots-r16.

[0230] For PUSCH repetition type A, the selection of the time domain resource allocation table follows the rules of DCI format 0_0 for UE-specific search spaces.

[0231] For PUSCH repetition type A, the selection of the time domain resource allocation table is as follows: If pusch-RepTypeIndicatorDCI-0-1 in pusch-Config is configured and set to "pusch-RepTypeA", then pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config is used. Otherwise, pusch-TimeDomainResourceAllocationListDCI-0-2 in pusch-Config is used. If neither pusch-RepTypeIndicatorDCI-0-1 nor pusch-RepTypeIndicatorDCI-0-2 in pusch-Config is set to "pusch-RepTypeA", then the pusch-RepTypeIndicator in the rrc-ConfiguredUplinkGrant is expected to be configured with "pusch-RepTypeA".

[0232] For PUSCH repetition type B, the selection of the time domain resource allocation table is as follows: If pusch-RepTypeIndicatorDCI-0-1 in pusch-Config is configured and set to "pusch-RepTypeB", then pusch-TimeDomainResourceAllocationListDCI-0-1 in pusch-Config is used. Otherwise, pusch-TimeDomainResourceAllocationListDCI-0-2 in pusch-Config is used. If neither pusch-RepTypeIndicatorDCI-0-1 nor pusch-RepTypeIndicatorDCI-0-2 in pusch-Config is set to "pusch-RepTypeB", then the pusch-RepTypeIndicator in the rrc-ConfiguredUplinkGrant is expected to be configured with "pusch-RepTypeB".

[0233] Further details of resource allocation in the time domain for PUSCH with configured grant are given. For PUSCH transmission with configured grant of type 1 or type 2, the (nominal) number of repetitions K applied to the transmitted transport block may be provided by an indexed row in the time domain resource allocation table if numberOfRepetitions is present in the table. Otherwise, K may be provided by higher layer configured parameter repK. The UE may not be allowed to transmit on what are the resources configured by the RRC parameter configuredGrantConfig if higher layers have not delivered a transport block to transmit on the resources allocated for uplink transmission without a grant.

[0234] The set of allowed periodicities P is defined in the RRC configuration. The RRC parameter cg-nrofSlots may provide the number of consecutive slots allocated within the configured grant period. The RRC parameter cg-nrofPUSCH-InSlot may provide the number of consecutive PUSCH allocations in a slot, where the first PUSCH allocation may follow the RRC parameter timeDomainAllocation for type 1 PUSCH transmission or higher layer configuration according to the MAC procedure, as well as the UL grant received in the DCI for type 2 PUSCH transmission, and the remaining PUSCH allocations may have the same length and PUSCH mapping type, and may be added following the previous allocation without gaps. The same combination of starting symbol, length and PUSCH mapping type may be repeated over consecutively allocated slots.

[0235] The UE may not be expected to be configured with a period of K repetitions of transmission that is greater than the period derived by the periodicity P. If the UE determines for a transmission opportunity that the number of symbols available for PUSCH transmission in a slot is less than the transmission duration L, then the UE may not transmit PUSCH at the transmission opportunity.

[0236] The procedure applies for PUSCH transmissions of PUSCH repetition type A with configured grant of type 1 or type 2. The RRC parameter repK-RV defines the redundancy version pattern to be applied for the repetitions. If cg-RetransmissionTimer is provided, the redundancy version for uplink transmissions with configured grant is determined by the UE. If the parameter repK-RV is not provided in configuredGrantConfig and cg-RetransmissionTimer is not provided, the redundancy version for uplink transmissions with configured grant may have to be set to 0. If the parameter repK-RV is not provided in configuredGrantConfig and is not provided in cg-RetransmissionTimer, it is associated with the (mod(n-1,4)+1)th value in the configured RV sequence for the nth transmission opportunity (n=1,2,.,K) during K repetitions. If the configured grant configuration is configured with startingFromRV0 set to "off", the initial transmission of a transport block may only start at the first transmission opportunity of the K repetitions. Otherwise, the initial transmission of the transport block may initiate the first transmission opportunity of K repetitions if the configured RV sequence is {0,2,3,1}, any of the K transmission opportunities associated with RV=0 if the configured RV sequence is {0,3,0,3}, and / or any of the K transmission opportunities if the configured RV sequence is {0,0,0,0}, excluding the last transmission opportunity if K>8.

[0237] If the configured grant configuration does not consist of startingFromRV0 set to "off", the initial transmission of the transport block may start at the first transmission opportunity of the K repetitions if an available slot-based count is configured.

[0238] If the configured grant configuration is not configured with startingFromRV0 set to "off", then if an available slot-based count is configured, the initial transmission of a transport block may start with the first transmission opportunity of the K repetitions if the configured RV sequence is {0,2,3,1}, any of the K repetitions associated with RV=0 if the configured RV sequence is {0,3,0,3}, and / or any of the K repetitions associated with RV=0 if the configured RV sequence is {0,0,0,0}, except for the last transmission opportunity if K>8.

[0239] If the configured grant configuration is not configured with startingFromRV0 set to "off", then if an available slot-based count is configured, the initial transmission of a transport block may start with the first transmission opportunity of the K repetitions if the configured RV sequence is {0,2,3,1}, any of the K repetitions associated with RV=0 if the configured RV sequence is {0,3,0,3}, and / or any of the K repetitions associated with RV=0 if the configured RV sequence is {0,0,0,0}, except for the last transmission opportunity if K>8.

[0240] If the configured grant configuration is not configured with startingFromRV0 set to "off", and if the available slot-based count is not configured, the initial transmission of the transport block assumes that the transmission opportunities among the K repetitions are determined based on consecutive physical slots if the configured RV sequence is {0,2,3,1}, or among the K repetitions if the configured RV sequence is {0,3,0,3}, and may start any of the first transmission opportunities among the K repetitions associated with RV=0 and / or any of the transmission opportunities among the K repetitions if the configured RV sequence is {0,0,0,0}, excluding the last transmission opportunity if K>8.

[0241] For any RV sequence, the repetition may need to end after transmitting K repetitions, or at the last transmission opportunity of the K repetitions within period P, or from the start symbol of the repetition that overlaps with a PUSCH with the same HARQ process scheduled by DCI format 0_0, 0_1 or 0_2, whichever comes first. Furthermore, if a UE is provided with and receives DCI format 0_1 ​​with DFI flag set to '1', the UE may need to end the repetition of a transport block in a PUSCH transmission if, within this DCI, the UE detects an ACK of a HARQ process corresponding to that transport block.

[0242] The UE is not expected to be configured with a period of K repetitions of transmission that is greater than the period derived by the period P. If the UE determines for a transmission opportunity that the number of symbols available for PUSCH transmission in a slot is less than the transmission duration L, then the UE does not transmit PUSCH at the transmission opportunity.

[0243] The MAC entity may be included in the medium access control layer processing unit 15 .

[0244] The pusch-Config may refer to the PUSCH-Config.

[0245] The pusch-Config may be referred to as a PUSCH-Config.

[0246] The RRC parameter frequency hopping indicates that the value intraSlot enables "intra-slot frequency hopping" and the value interSlot enables "inter-slot frequency hopping". If the field is not present, frequency hopping is not configured for "pusch-RepTypeA". The field frequencyHopping applies to DCI formats 0_0 and 0_1 for "pusch-RepTypeA".

[0247] The RRC parameter frequencyHoppingDCI-0-1-r16 indicates the frequency hopping scheme for DCI format 0_1 ​​if pusch-RepTypeIndicatorDCI-0-1 is set to "pusch-RepTypeB", the value interRepetition enables "inter-repetition frequency hopping" and the value interSlot enables "inter-slot frequency hopping". If the field is not present, frequency hopping is not configured for DCI format 0_1.

[0248] The RRC parameter frequencyHoppingDCI-0-1-r17 indicates the frequency hopping scheme for DCI format 0_1 ​​if pusch-RepTypeIndicatorDCI-0-1 is set to "pusch-RepTypeA" or "pusch-RepTypeB" with "inter-repetition frequency hopping". The value interRepetition enables "inter-repetition frequency hopping", the value interSlot enables "inter-slot frequency hopping" and the value intraSlot enables "intra-slot frequency hopping". If the field is not present, inter-repetition frequency hopping is not configured for DCI format 0_1 ​​with "pusch-RepTypeA" and frequency hopping is not configured for DCI format 0_1 ​​with "pusch-RepTypeB". Or, the RRC parameter frequencyHoppingDCI-0-1-r17 may indicate the frequency hopping scheme of DCI format 0_1 ​​if pusch-RepTypeIndicatorDCI-0-1 is set to "pusch-RepTypeA" which enables "frequency hopping between repetitions".

[0249] For resource allocation type 2, the UE transmits the PUSCH without frequency hopping.

[0250] For resource allocation type 1, regardless of whether transform precoding is enabled for PUSCH transmission or not, the UE may perform PUSCH frequency hopping if the frequency hopping field in the corresponding detected DCI format or random access response UL grant is set to 1, or for type 1 PUSCH transmission with configured grant, if the RRC parameter frequencyHoppingOffset is provided, otherwise no PUSCH frequency hopping is performed. If frequency hopping is enabled for PUSCH, the RE mapping is defined in these procedures.

[0251] For RAR UL grants, fallbackRAR UL grants or PUSCHs scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI, the frequency offset is obtained as described in these procedures. For PUSCHs scheduled by DCI format 0_0 / 0_1 or based on configured UL grants of type 2 activated by DCI format 0_0 / 0_1 and for resource allocation type 1, the frequency offset is configured by the RRC parameter frequencyHoppingOffsetLists in pusch-Config. For PUSCHs scheduled by DCI format 0_2 or based on configured UL grants of type 2 activated by DCI format 0_2 and for resource allocation type 1, the frequency offset is configured by the RRC parameter frequencyHoppingOffsetListsDCI-0-2 in pusch-Config. If the size of the active BWP is less than 50 PRB, one of the two higher layer configured offsets is indicated in the UL grant. If the size of the active BWP is 50 PRB or more, one of four higher layer configured offsets is indicated in the UL grant.

[0252] For PUSCH based on Type 1 configured UL grant, the frequency offset is provided by the RRC parameter frequencyHoppingOffset in rrc-ConfiguredUplinkGrant.

[0253] For PUSCH repetition type B (as determined according to the procedures specified in these procedures for scheduled PUSCH or procedures for configured PUSCH), the UE is configured for frequency hopping by the RRC parameter frequencyHoppingDCI-0-2 in pusch-Config for PUSCH transmissions scheduled with DCI format 0_2, by frequencyHoppingDCI-0-1 provided in pusch-Config for PUSCH transmissions scheduled with DCI format 0_1, and by frequencyHoppingPUSCH-RepTypeB provided in rrc-ConfiguredUplinkGrant for configured PUSCH transmissions of type 1. The frequency hopping mode for configured PUSCH transmissions of type 2 follows the configuration of the activation DCI format. One of two frequency hopping modes can be configured: inter-repetition frequency hopping and inter-slot frequency hopping.

[0254] For resource allocation type 1, whether transform precoding is enabled for a PUSCH transmission or not, the UE may perform PUSCH frequency hopping if the frequency hopping field in the corresponding detected DCI format is set to 1 or, for a type 1 PUSCH transmission with configured grant, the RRC parameter frequencyHoppingPUSCH-RepTypeB is provided, otherwise, no PUSCH frequency hopping is performed. If frequency hopping is enabled for PUSCH, the RE mapping is defined in these procedures.

[0255] For PUSCH scheduled by DCI format 0_1 ​​or for PUSCH for resource allocation type 1 based on configured UL grant of type 2 activated by DCI format 0_1, the frequency offset is configured by the RRC parameter frequencyHoppingOffsetLists in pusch-Config. For PUSCH scheduled by DCI format 0_2 or for PUSCH based on configured UL grant of type 2 activated by DCI format 0_2 and for resource allocation type 1, the frequency offset is configured by the RRC parameter frequencyHoppingOffsetListsDCI-0-2 in pusch-Config. If the size of the active BWP is less than 50 PRB, one of two higher layer configured offsets is indicated in the UL grant. If the size of the active BWP is equal to or greater than 50 PRB, one of four higher layer configured offsets is indicated in the UL grant.

[0256] For PUSCH based on Type 1 configured UL grant, the frequency offset is provided by the RRC parameter frequencyHoppingOffset in rrc-ConfiguredUplinkGrant.

[0257] For inter-slot frequency hopping, A The starting RB during u_s follows inter-slot frequency hopping of PUSCH repetition type A according to at least one of the conditions defined in those procedures.

[0258] A pattern of inter-slot frequency hopping through the available slots may be determined based on the omission of PUSCH transmissions.

[0259] The pattern of RVs with available slots may be determined based on the omission of PUSCH transmissions.

[0260] The pattern of slot counting according to the available slots may be determined based on the omission of PUSCH transmissions.

[0261] A PUSCH priority-based procedure will now be described. If a PUSCH is scheduled by a DCI or a PUSCH with a configured grant, the PUSCH is transmitted unless otherwise specified.

[0262] A PUSCH or PUCCH transmission with repetitions, if any, may have a priority index of 0 or a priority index of 1. For configured grant PUSCH transmission, the UE may determine the priority index from the RRC parameter phy-Prioritylndex, if provided. For PUCCH transmission with HARQ-ACK information corresponding to SPS PDSCH reception or SPS PDSCH release, the UE may determine the priority index from the RRC parameter harq-CodebookID, if provided. For PUCCH transmission with SR, the UE may determine the corresponding priority by the RRC parameter phy-Prioritylndex in the RRC parameter SchedulingRequestResourceConfig, if provided. For PUSCH transmission with semi-persistent CSI reporting, the UE may determine the priority index from the priority indicator field, if provided, in the DCI format that activates semi-persistent CSI reporting. If a priority index is not provided to the UE for a PUSCH or PUCCH transmission, the priority index may be 0.

[0263] If in an active DL BWP the UE can monitor the PDCCH for either DCI format 0_1 ​​and DCI format 1_1 detection or DCI format 0_2 and DCI format 1_2 detection, the priority index may be provided by the priority indicator field. If the UE indicates capability to monitor the PDCCH for DCI format 0_1 ​​and DCI format 1_1 detection and DCI format 0_2 and DCI format 1_2 detection in an active DL BWP, DCI format 0_1 ​​and DCI format 0_2 can schedule PUSCH transmission of any priority, and DCI format 1_1 or DCI format 1_2 can schedule PDSCH reception and trigger PUCCH transmission with corresponding HARQ-ACK information of any priority.

[0264] When the UE determines overlaps of PUCCH and / or PUSCH transmissions of different priority indexes, including repetitions, if any, the UE may first resolve overlaps of PUCCH and / or PUSCH transmissions of lower priority indexes. Then, if a first PUCCH transmission of a higher priority index scheduled by a DCI format in a PDCCH reception overlaps in time with a second PUSCH or a repetition of a second PUCCH transmission of a lower priority index, the UE may cancel the second PUSCH or the repetition of a second PUCCH transmission before the first symbol that would overlap with the first PUCCH transmission, and if a first PUSCH transmission of a higher priority index scheduled by a DCI format in a PDCCH reception overlaps in time with a repetition of a second PUCCH transmission of a lower priority index, the UE may cancel the second PUCCH transmission repetition before the first symbol that would overlap with the first PUSCH transmission. The overlap may be applicable before or after resolving overlap, if any, between channels of higher priority index. The UE may assume that the first PUCCH or first PUSCH transmission, respectively, will not start before T_(proc,2)+d_1 after the last symbol of the corresponding PDCCH reception, where T_(proc,2) is the PUSCH preparation time for the corresponding UE processing capability assuming d_2,1=0 based on u and N_2, and d_1 is determined by the reported UE capability.

[0265] If the UE is scheduled by a DCI format in the first PDCCH reception to transmit a first PUCCH or first PUSCH of a higher priority index that overlaps with a second PUCCH or second PUSCH transmission of a lower priority index scheduled by a DCI format in the second PDCCH, if any, then T_(proc,2) may be based on a value of u corresponding to the smallest SCS configuration among the first PDCCH, the second PDCCH, the first PUCCH or first PUSCH, and the second PUCCH or second PUSCH. If the overlapping group includes the first PUCCH, then N_2 is 5 for u=0, 5.5 for u=1, and 11 for u=2 if the RRC parameter processingType2Enabled of the RRC parameter PDSCH-ServingCellConfig is set to enable the serving cell on which the UE receives the first PDCCH and all serving cells on which the UE receives the PDSCH corresponding to the second PUCCH, and N_2 is 10 for u=0, 12 for u=1, 23 for u=2, and 36 for u=3 if the RRC parameter processingType2Enabled of the RRC parameter PDSCH-ServingCellConfig is set to enable the saving cell using the second PUSCH. If the overlapping group includes the first PUSCH, then N_2 is 5 for u=0, 5.5 for u=1, and 11 for u=2 when processingType2Enabled in PUSCH-ServingCellConfig is set to enable the serving cell with the first PUSCH and the second PUSCH, and N_2 is 10 for u=0, 12 for u=1, 23 for u=2, and 36 for u=3 when processingType2Enabled in PDSCH-ServingCellConfig is set to enable for all serving cells from which the UE receives a PDSCH corresponding to the second PUCCH.

[0266] The UE has, if any, a first PUCCH with a higher priority index and a second PUCCH or PUSCH with a lower priority index, or a configured grant PUSCH with a higher priority index and a PUCCH with a lower priority index, or a first PUCCH with a higher priority index and a second PUCCH with a lower priority index and a lower priority index in response to only receiving a PDSCH without a corresponding PDCCH, or a configured grant PUSCH with a lower priority index, or a PUSCH with a lower priority index and a SP-CSI report(s) without a corresponding PDCCH, or a SP-CSI report(s) without a corresponding PDCCH. When transmitting the following channels, including a PUSCH of a higher priority index and a PUCCH of a lower priority index with SR or CSI, or HARQ-ACK information only in response to PDSCH reception without a corresponding PDCCH, or a repetition that would overlap in time with a configured grant PUSCH of a higher priority index and a configured PUSCH of a lower priority index on the same serving cell, the UE may be expected to cancel a repetition of a PUCCH / PUSCH transmission before the first symbol that overlaps with a PUCCH / PUSCH transmission of a higher priority index if the repetition of the PUCCH / PUSCH transmission of a lower priority index overlaps in time with a PUCCH / PUSCH transmission of a higher priority index.

[0267] A UE may not be expected to transmit a PUCCH or a lower priority PUSCH that would overlap in time with a higher priority PUCCH that has HARQ-ACK information only in response to a PDSCH reception without a corresponding PDCCH. A UE may not be expected to be scheduled to transmit a lower priority PUCCH that overlaps in time with a higher priority PUSCH that has an SP-CSI report(s) that does not have a corresponding PDCCH.

[0268] When a UE multiplexes aperiodic CSI on a PUSCH, and the UE multiplexes UCI including HARQ-ACK information in a PUCCH that overlaps with the PUSCH, and the timing condition for overlapping with the PUCCH and PUSCH is met, the UE may multiplex only HARQ-ACK information on the PUSCH and does not transmit the PUCCH.

[0269] A UE transmits multiple PUSCHs in slots on each serving cell, including a first PUSCH and a second PUSCH scheduled by a DCI format configured by a respective RRC parameter ConfiguredGrantConfig or semiPersistentOnPUSCH, and the UE multiplexes UCI on one of the multiple PUSCHs, and if the multiple PUSCHs satisfy a condition for UCI multiplexing, the UE can multiplex UCI on the PUSCHs from the first PUSCH.

[0270] If the UE transmits multiple PUSCHs in a slot on each serving cell, the UE multiplexes UCI on one of the multiple PUSCHs, and the UE does not multiplex aperiodic CSI on any of the multiple PUSCHs, the UE may multiplex UCI in the PUSCH of the serving cell with the smallest RRC parameter ServCellIndex due to which the condition for UCI multiplexing is satisfied. If the UE transmits more than one PUSCH in a slot on the serving cell with the smallest ServCellIndex that satisfies the condition for UCI multiplexing, the UE may multiplex UCI in the earliest PUSCH that the UE transmits in the slot.

[0271] When a UE transmits a PUSCH over multiple slots, the UE transmits a PUCCH with HARQ-ACK and / or CSI information over a single slot that overlaps with a PUSCH transmission in one or more of the multiple slots, and the UE may multiplex the HARQ-ACK and / or CSI information onto the PUSCH transmission in one or more slots if the PUSCH transmission in the one or more slots meets a condition for multiplexing the HARQ-ACK and / or CSI information. In the absence of a PUSCH transmission, if the UE does not transmit a single-slot PUCCH with HARQ-ACK and / or CSI information in the slot, the UE may not multiplex the HARQ-ACK and / or CSI information onto the PUSCH transmission in a slot from multiple slots.

[0272] If a PUSCH transmission spanning multiple slots is scheduled by a DCI format that includes a DAI field, the value of the DAI field may be applicable to multiplexing of HARQ-ACK information within a PUSCH transmission in any slot from the multiple slots in which the UE multiplexes HARQ-ACK information.

[0273] If the UE is to multiplex HARQ-ACK information in a PUSCH transmission including CG-UCI as configured by the RRC parameter ConfiguredGrantConfig, the UE may multiplex the HARQ-ACK information in the PUSCH transmission if the UE is provided with the RRC parameter cg-UCI-Multiplexing, otherwise the UE will not transmit a PUSCH and will multiplex the HARQ-ACK information in a PUCCH transmission or another PUSCH transmission.

[0274] If it is determined that the PUSCH (or a repetition of the PUSCH) in the slot is transmitted or multiplexed with UCI(s), the slot may be considered available for PUSCH transmission. If it is determined that the PUSCH (or a repetition of the PUSCH) in the slot is cancelled, the slot may be considered unavailable for PUSCH transmission.

[0275] The slot configuration based procedure will be described below. If a PUSCH is scheduled by a DCI or a PUSCH with a configured grant, the PUSCH is transmitted unless otherwise specified.

[0276] If the UE is provided with the RRC parameter tdd-UL-DL-ConfigurationCommon, the UE can set the slot format (the format indicating what type of symbols there are among downlink, uplink, and flexible symbols per symbol in a slot) per slot for the number of slots indicated by tdd-UL-DL-ConfigurationCommon. If the UE is additionally provided with the RRC parameter tdd-UL-DL-ConfigurationDedicated, the parameter tdd-UL-DL-ConfigurationDedicated can override only the flexible symbols per slot for the number of slots provided by tdd-UL-DL-ConfigurationCommon.

[0277] In the case of operation with a single carrier in an unpaired spectrum, if the UE is configured by higher layers to receive PDCCH, or PDSCH, or CSI-RS, or DL ​​PRS in the set of symbols of a slot, if the UE does not detect a DCI format that indicates the UE to transmit PUSCH, PUCCH, PRACH, or SRS in at least one symbol of the set of symbols of the slot, then the UE will receive the PDCCH, PDSCH, CSI-RS, or DL ​​PRS; otherwise, the UE may not receive the PDCCH, or PDSCH, or CSI-RS, or DL ​​PRS in the set of symbols of the slot.

[0278] For a set of symbols of a slot that is indicated to the UE as downlink by the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, the UE may not transmit a PUSCH, PUCCH, PRACH, or SRS when the PUSCH, PUCCH, PRACH, or SRS overlaps, even partially, with the set of symbols of the slot.

[0279] For a set of slot symbols that is indicated to the UE as flexible by tdd-UL-DL-ConfigurationCommon and, if provided, tdd-UL-DL-ConfigurationDedicated, the UE may not expect to receive any dedicated RRC parameters configuring transmission from the UE in the set of slot symbols and any dedicated RRC parameters configuring reception by the UE in the set of slot symbols.

[0280] In case of operation with a single carrier in unpaired spectrum, for a set of symbols of a slot indicated to the UE by the RRC parameters ssb-PositionsInBurst in SIB1 or ssb-PositionslnBurst in ServingCellConfigCommon, for reception of SS / PBCH blocks, the UE may not transmit PUSCH, PUCCH, PRACH in the slot if the transmission overlaps with any symbol from the set of symbols, and the UE may not transmit SRS in the set of symbols of the slot. The UE may not assume that the set of symbols of a slot is indicated as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, if provided to the UE.

[0281] If the UE is scheduled by the DCI format to transmit PUSCH over multiple slots, if the tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated indicates that for a slot from the multiple slots, at least one symbol from the set of symbols for which the UE is scheduled for PUSCH transmission in the slot is a downlink symbol, the UE may not transmit PUSCH in the slot.

[0282] If it is determined that the PUSCH (or a repetition of the PUSCH) in the slot is transmitted, the slot may be considered available for PUSCH transmission. If it is determined that the PUSCH (or a repetition of the PUSCH) in the slot is canceled or not transmitted, the slot may be considered unavailable for PUSCH transmission.

[0283] A PUSCH instance may be a unit of baseband signal generation, where the baseband signal generation may be performed by the baseband unit 13.

[0284] The details of the UE procedure(s) for applying transform precoding to the PUSCH are now described.

[0285] FIG. 9 shows an example of a PUSCH generation procedure at the UE side. The PUSCH generation procedure may include multiple processes, such as scrambling, modulation, layer mapping, transform precoding, mapping to resource blocks, and OFDM baseband signal generation. A bit block for a codeword may be scrambled to generate scrambled bits. The scrambled bits may be modulated to generate modulation symbols (i.e., complex-valued modulation symbols). The modulation symbols may be layer mapped to generate a set of modulation symbols per layer. The set of modulation symbols per layer xi may be input to a transform precoding process, and the processed modulation symbols per layer yi may be an output corresponding to x(i). The processed modulation symbols per layer yi may be mapped to resource blocks (e.g., virtual resource blocks and / or physical resource blocks). An inverse fast Fourier transform (IFFT) may be applied to the modulation symbols on the resource blocks to generate an OFDM baseband signal.

[0286] On the gNB side, processes corresponding to the processes shown in Fig. 9 may be executed. For example, the descrambling process on the gNB side may correspond to the scrambling process on the UE side, the demodulation process on the gNB side may correspond to the modulation process on the UE side, the IDFT (inverse DFT) on the gNB side may correspond to the DFT on the UE side, and the FFT on the gNB side may correspond to the IFFT on the UE side.

[0287] In the transform precoding process, if transform precoding is disabled (or not enabled), the input may be passed through unchanged. Thus, in this case, yi=xi. If transform precoding is enabled, at least a digital Fourier transform (DFT) may be applied to the input to generate an output. Figure 10 shows an example equation for the DFT process for transform precoding, where M pusch rb may represent the bandwidth of the PUSCH in terms of the number of resource blocks, and M layer symb may denote the number of modulation symbols per layer, and N RB sc may indicate the number of subcarriers in a resource block (e.g., N RB sc =12). If no phase tracking reference signal (PT-RS) is used,

[0288]

number

[0289]

number

[0290] For a PUSCH scheduled by a RAR UL grant, or for a PUSCH scheduled by a fallbackRAR UL grant, or for a PUSCH scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI, the UE may consider transform precoding either "enabled" or "disabled" according to the configured parameter msg3-transformPrecoder.

[0291] For MsgA PUSCH, the UE may consider transform precoding either "enabled" or "disabled" according to the higher layer configured parameter msgA-TransformPrecoder. If the RRC parameter msgA-TransformPrecoder is not configured, the UE may consider transform precoding either "enabled" or "disabled" according to the RRC parameter msg3-transformPrecoder.

[0292] The RRC parameter msgA-TransformPrecoder indicates whether the UE enables or disables the transform precoder for MsgA transmission.

[0293] For a PUSCH transmission scheduled on a CS-RNTI, C-RNTI with NDI=1, or a PDCCH with CRC scrambled on MCS-C-RNTI or SP-CSI-RNTI, if a DCI with a scheduling grant is received in DCI format 0_0, the UE may consider transform precoding as either enabled or disabled for this PUSCH transmission according to the RRC parameter msg3-transformPrecoder.

[0294] For a PUSCH transmission scheduled on a CS-RNTI, C-RNTI with NDI=1, or a PDCCH with CRC scrambled on MCS-C-RNTI or SP-CSI-RNTI, if no DCI with a scheduling grant was received in DCI format 0_0, if the UE is configured with the RRC parameter transformPrecoder in pusch-Config, the UE may consider transform precoding either enabled or disabled for this PUSCH transmission according to this parameter (i.e. the configured transformPrecoder).

[0295] For a PUSCH transmission scheduled on a CS-RNTI, C-RNTI with NDI=1, or a PDCCH with CRC scrambled on MCS-C-RNTI or SP-CSI-RNTI, if no DCI with a scheduling grant was received in DCI format 0_0, if the UE is configured with the RRC parameter transformPrecoder, dynamicSwitchingTransformPrecoder set to "disabled" in pusch-Config, the UE may consider transform precoding either enabled or disabled for this PUSCH transmission according to the RRC parameter transformPrecoder.

[0296] "DCI having a scheduling grant was not received in DCI format 0_0" may mean "DCI having a scheduling grant was received in a DCI format other than DCI format 0_0". Or, "DCI having a scheduling grant was not received in DCI format 0_0" may mean "the scheduling grant was received in a configured grant".

[0297] The RRC parameter dynamicSwitchingTransformPrecoder indicates whether a "transform precoding indicator" field (also referred to as a transform precoding field or a transform precoder field) is included in DCI format 0_1 / 0_2. Alternatively, two different RRC parameters dynamicSwitchingTransformPrecoderDCI 0_1 and dynamicSwitchingTransformPrecoderDCI 0_2 indicate whether a "transform precoding indicator" field (also referred to as a transform precoding field) is included in DCI format 0_1 ​​and DCI 0_2, respectively. In this case, the RRC parameter dynamicSwitchingTransformPrecoder described below may be interpreted as the RRC parameters dynamicSwitchingTransformPrecoderDCI0_1 and dynamicSwitchingTransformPrecoderDCI0_2 for DCI format 0_1 ​​and DCI format 0_2, respectively.

[0298] The 'Transform Precoding Indicator' field is used to indicate whether the transform precoder is enabled or not.

[0299] The RRC parameter dynamicSwitchingTransformPrecoder may be configured as a common parameter for different DCI formats.

[0300] The RRC parameter dynamicSwitchingTransformPrecoder may be configured for DCI format 0_1 ​​and DCI format 0_2, respectively. In other words, the RRC parameter dynamicSwitchingTransformPrecoder corresponding to each of the DCI formats may be configured. If the UE is configured with the RRC parameter dynamicSwitchingTransformPrecoder corresponding to each of the DCI formats, the UE may assume that a "transform precoding indicator" field may be included in the corresponding DCI format(s), respectively.

[0301] If the RRC parameter dynamicSwitchingTransformPrecoder indicates "enabled", the "Transform Precoding Indicator" field may be included in DCI format 0_1 / 0_2. If the RRC parameter dynamicSwitchingTransformPrecoder indicates "disabled", the "Transform Precoding Indicator" field may not be included in DCI format 0_1 / 0_2.

[0302] If the RRC parameter dynamicSwitchingTransformPrecoder is configured, the UE may assume that the "Transform Precoding Indicator" field may be included in DCI format 0_1 / 0_2. The RRC parameter dynamicSwitchingTransformPrecoder, if provided, may indicate that the "Transform Precoding Indicator" field is included in DCI format 0_1 / 0_2.

[0303] If the RRC parameter dynamicSwitchingTransformPrecoder is not configured / absent, the UE may assume that the "Transform Precoding Indicator" field may not be included in DCI format 0_1 / 0_2.

[0304] For a PUSCH transmission scheduled on a CS-RNTI, C-RNTI with NDI=1, or a PDCCH with CRC scrambled on MCS-C-RNTI or SP-CSI-RNTI, if no DCI with a scheduling grant was received with DCI format 0_0, if the UE is configured with the RRC parameters transformPrecoder, dynamicSwitchingTransformPrecoder set to "enabled" in pusch-Config, the UE may consider transform precoding either enabled or disabled for this PUSCH transmission according to the DCI "Transform Precoding Indicator" field.

[0305] Alternatively, for a PUSCH transmission scheduled on a CS-RNTI, C-RNTI with NDI=1, or a PDCCH with CRC scrambled on MCS-C-RNTI or SP-CSI-RNTI, if no DCI with a scheduling grant was received in DCI format 0_0, if the UE is configured with the RRC parameters transformPrecoder, dynamicSwitchingTransformPrecoder set to "enabled" in pusch-Config, the UE may consider transform precoding either enabled or disabled for this PUSCH transmission according to the DCI "Transform Precoding Indicator" field, regardless of the value of transformPrecoder.

[0306] Alternatively, for a PUSCH transmission scheduled on a CS-RNTI, C-RNTI with NDI=1, or a PDCCH with CRC scrambled on MCS-C-RNTI or SP-CSI-RNTI, if no DCI with a scheduling grant was received in DCI format 0_0, if the UE is configured with the RRC parameters transformPrecoder set to "enabled" and dynamicSwitchingTransformPrecoder set to "enabled" in pusch-Config, the UE may consider transform precoding either enabled or disabled for this PUSCH transmission according to the DCI "Transform Precoding Indicator" field.

[0307] The UE may assume that the DCI "Transform Precoding Indicator" field is not included in DCI format 0_0.

[0308] For a PUSCH transmission scheduled on a CS-RNTI, C-RNTI with NDI=1, or a PDCCH with CRC scrambled on MCS-C-RNTI or SP-CSI-RNTI, if no DCI with a scheduling grant was received in DCI format 0_0, if the UE is not configured with the RRC parameter transformPrecoder in pusch-Config, the UE may consider transform precoding either enabled or disabled for this PUSCH transmission according to the RRC parameter msg3-transformPrecoder.

[0309] For a PUSCH transmission scheduled on a CS-RNTI, C-RNTI with NDI=1, or a PDCCH with CRC scrambled on MCS-C-RNTI or SP-CSI-RNTI, if no DCI with a scheduling grant was received with DCI format 0_0, if the UE is not configured with the RRC parameter transformPrecoder, dynamicSwitchingTransformPrecoder set to "enabled" in pusch-Config, the UE may consider transform precoding either enabled or disabled for this PUSCH transmission according to the higher layer configured parameter msg3-transformPrecoder.

[0310] For a PUSCH transmission scheduled on a CS-RNTI, C-RNTI with NDI=1, or a PDCCH with CRC scrambled on MCS-C-RNTI or SP-CSI-RNTI, if no DCI with a scheduling grant was received in DCI format 0_0, if the UE is not configured with the RRC parameters transformPrecoder in pusch-Config and dynamicSwitchingTransformPrecoder in pusch-Config, the UE may consider transform precoding either enabled or disabled for this PUSCH transmission according to the higher layer configured parameter msg3-transformPrecoder.

[0311] For a PUSCH transmission scheduled on a CS-RNTI, C-RNTI with NDI=1, or a PDCCH with CRC scrambled on MCS-C-RNTI or SP-CSI-RNTI, if no DCI with a scheduling grant was received with DCI format 0_0, if the UE is not configured with the RRC parameter transformPrecoder, and if the UE is configured with dynamicSwitchingTransformPrecoder set to "disabled" in pusch-Config, the UE may consider transform precoding either enabled or disabled for this PUSCH transmission according to the RRC parameter msg3-transformPrecoder.

[0312] For a PUSCH transmission scheduled on a CS-RNTI, C-RNTI with NDI=1, or a PDCCH with CRC scrambled on MCS-C-RNTI or SP-CSI-RNTI, if no DCI with a scheduling grant was received with DCI format 0_0, if the UE is not configured with the RRC parameter transformPrecoder in pusch-Config, and if the UE is configured with the RRC parameter dynamicSwitchingTransformPrecoder set to "enabled" in pusch-Config, the UE may consider transform precoding as either enabled or disabled for this PUSCH transmission according to the DCI "Transform Precoding Indicator" field.

[0313] The DCI "Transform Precoding Indicator" field feature may be realized by using a DCI field other than the "Transform Precoding Indicator" field. In other words, if the UE is configured with the RRC parameter dynamicSwitchingTransformPrecoder set to "enabled" in pusch-Config, a first value of the first DCI field may indicate that the transform precoder is enabled and a second value of the first DCI field may indicate that the transform precoder is disabled. The UE may assume that the value(s) of the first DCI field included in the DCI format is associated with whether the transform precoder is enabled or not.

[0314] If the base station provides the RRC parameter dynamicSwitchingTransformPrecode set to “enabled” in pusch-Config, a first value of the first DCI field may be set to indicate that the transform precoder is enabled and a second value of the first DCI field may be set to indicate that the transform precoder is disabled.

[0315] For a PUSCH transmission with a configured grant, if the UE is configured with the RRC parameter transformPrecoder in configuredGrantConfig, the UE may consider transform precoding enabled or disabled according to this parameter for this PUSCH transmission.

[0316] For a PUSCH transmission with configured grant, if the UE is configured with the RRC parameter transformPrecoder in configuredGrantConfig, the UE may consider transform precoding enabled or disabled for this PUSCH transmission according to the higher layer configured parameter msg3-transformPrecoder.

[0317] Here, "dynamicSwitchingTransformPrecoder is configured" may have the same meaning as "dynamicSwitchingTransformPrecoder set to "enabled" is configured. Also, "dynamicSwitchingTransformPrecoder is not configured" may have the same meaning as "dynamicSwitchingTransformPrecoder set to "disabled" is configured.

[0318] Alternatively or additionally, dynamic switching from DFT-S-OFDM (i.e., OFDM with a transform precoder) to OFDM (i.e., OFDM without a transform precoder) may not be allowed, but dynamic switching from OFDM to DFT-S-OFDM may be allowed. OFDM may also be referred to as CP-OFDM (Cyclic Prefix-OFDM), which means OFDM with CP.

[0319] DCI formats 0_1 and / or 0_2 with CRC scrambled by C-RNTI may include a "Transform Precoding Indicator" field if the RRC parameter dynamicSwitchingTransformPrecoder in pusch-Config is provided. DCI formats 0_1 and / or 0_2 may not include a "Transform Precoding Indicator" field if the RRC parameter dynamicSwitchingTransformPrecoder in pusch-Config is not provided. If the RRC parameter transformPrecoder set to "enabled" is provided in pusch-Config, the RRC parameter dynamicSwitchingTransformPrecoder may be configured. If the RRC parameter transformPrecoder set to "enabled" is not provided in pusch-Config, the RRC parameter dynamicSwitchingTransformPrecoder may not be allowed / expected to be configured. If the RRC parameter transformPrecoder set to "enabled" is provided in pusch-Config, DCI formats 0_1 and / or 0_2 with CRC scrambled by C-RNTI may include a "Transform Precoding Indicator" field. If the RRC parameter transformPrecoder set to "enabled" is not provided in pusch-Config, the DCI formats 0_1 and / or 0_2 CRC scrambled by the C-RNTI may not be allowed / expected to include the "Transform Precoding Indicator" field. Note that the DCI formats 0_1 and / or 0_2 CRC scrambled by the C-RNTI may be UL grants for dynamically scheduling PUSCH transmissions.

[0320] DCI formats 0_0, 0_1 and / or 0_2 with CRC scrambled by CS-RNTI may include a "Transform Precoding Indicator" field if the RRC parameter dynamicSwitchingTransformPrecoder in pusch-Config is provided. DCI formats 0_1 and / or 0_2 may not include a "Transform Precoding Indicator" field if the RRC parameter dynamicSwitchingTransformPrecoder in pusch-Config is not provided. The RRC parameter dynamicSwitchingTransformPrecoder may be configured if the RRC parameter transformPrecoder set to "enabled" is provided in ConfiguredGrantConfig. The RRC parameter dynamicSwitchingTransformPrecoder may not be allowed / expected to be configured if the RRC parameter transformPrecoder set to "enabled" is not provided in ConfiguredGrantConfig. DCI formats 0_1 and / or 0_2 with CRC scrambled by CS-RNTI may include a "Transform Precoding Indicator" field if the RRC parameter transformPrecoder set to "enabled" is provided in ConfiguredGrantConfig. If the RRC parameter transformPrecoder set to "enabled" is not provided in the ConfiguredGrantConfig, then DCI formats 0_1 and / or 0_2 CRC scrambled by CS-RNTI may not be allowed / expected to include the "Transform Precoding Indicator" field. Note that DCI formats 0_1 and / or 0_2 CRC scrambled by CS-RNTI may be configured UL grant type 2 and activate the configured scheduled PUSCH transmission.

[0321] In this case, the value of the "Transform Precoding Indicator" field may indicate whether or not a transform precoder is applied even if the transform precoder is not enabled by the RRC parameter transformPrecoder. The "Transform Precoding Indicator" field may be a 1-bit field. A "Transform Precoding Indicator" field value equal to "0" may indicate that a transform precoder is not applied (the transform precoder is actually disabled) for a PUSCH scheduled by a DCI format or a PUSCH with a configured UL grant type 2 (i.e., following the RRC configuration regarding the transform precoder), and a "Transform Precoding Indicator" field value equal to "1" may indicate that a transform precoder is applied (the transform precoder is actually enabled) (i.e., not following the RRC configuration regarding the transform precoder) for a PUSCH scheduled by a DCI format or a PUSCH with a configured UL grant type 2. Alternatively, a 'Transform Precoding Indicator' field value equal to '1' may indicate that a transform precoder is not applied (the transform precoder is actually disabled) for a PUSCH scheduled by a DCI format or a PUSCH with a configured UL grant type 2 (i.e., the RRC configuration for the transform precoder is not followed), and a 'Transform Precoding Indicator' field value equal to '0' may indicate that a transform precoder is applied (the transform precoder is actually enabled) for a PUSCH scheduled by a DCI format or a PUSCH with a configured UL grant type 2 (i.e., the RRC configuration for the transform precoder is not followed).

[0322] DCI format 0_0 may not include the "transform precoding indicator" field, regardless of whether the RRC parameter transformPrecoder set to "enabled" is provided or whether the RRC parameter dynamicSwitchingTransformPrecoder is provided or not. For a PUSCH scheduled by DCI format 0_0 or a configured scheduled PUSCH activated by DCI format 0_0, whether the transform precoder is actually enabled or not depends on whether the RRC parameter transformPrecoder is set to "enabled". In other words, if the RRC parameter transformPrecoder set to "enabled" is provided, transform precoding is applied to the PUSCH. If the RRC parameter transformPrecoder set to "enabled" is not provided, transform precoding is not applied to the PUSCH.

[0323] It should be noted that transform precoding is precoding applied to the output of layer mapping and / or the input of precoding based on a precoding matrix W, whose index may correspond to a precoding matrix indicator. For a single codeword q=0, the complex modulation symbols of that codeword that are transmitted may be mapped onto up to four layers.

[0324]

number

[0325]

number

[0326]

number

[0327] If transform precoding is not enabled (i.e., not applied), then each layer

[0328]

number

[0329]

number

[0330]

number

[0331]

number

[0332]

number

[0333]

number

[0334]

number

[0335]

number

[0336]

number

[0337]

number

[0338]

number

[0339]

number

[0340]

number

[0341]

number

[0342] As also shown in FIG. 10, transform precoding is

[0343]

number

[0344]

number

[0345]

number

[0346]

number

[0347]

number

[0348]

number

[0349]

number

[0350] Blocks of Vectors

[0351]

number

[0352]

number

[0353]

number

[0354] Table 1 shows the sizes of information fields in DCI format 0_1 ​​and the RRC parameters that affect each field size. Table 2 shows the sizes of information fields in DCI format 0_2 and the RRC parameters that affect each field size.

[0355] [Table 1-1]

[0356] [Table 1-2]

[0357] [Table 1-3]

[0358] [Table 2-1]

[0359] [Table 2-2]

[0360] According to Table 1, it can be seen that the sizes of the following information fields in DCI format 0_1, i.e., precoding information and number of layers, second precoding information, antenna port, PTRS-DMRS association, second PTRS-DMRS association, and DMRS sequence initialization, can be changed according to the waveform of the scheduled PUSCH. According to Table 2, it can be seen that the sizes of the following information fields in DCI format 0_2, i.e., precoding information and number of layers, second precoding information, antenna port, PTRS-DMRS association, second PTRS-DMRS association, and DMRS sequence initialization, can be changed according to the waveform of the scheduled PUSCH.

[0361] Figure 11 shows an example of a payload size before bit padding of DCI format 0_1 ​​with CRC scrambled by C-RNTI. This may be an example where the RRC parameter dynamicSwitchingTransformPrecoder is provided, and the bit width of some information fields (e.g., precoding information and number of layers, second precoding information, and / or antenna port) of the DCI format before bit padding may depend on the value set in the transform precoder field. A value #0 (e.g., 0) may indicate that transform precoding is disabled (or that transform precoding is not enabled), and a value #1 (e.g., 1) may indicate that transform precoding is enabled.

[0362] If the Transform Precoder field is set to value #0, the size and number of layers of the precoding information, the second precoding information, and / or the number of antenna ports may be L0, M0, and / or N0 bits, respectively. If the Transform Precoder field is set to value #1, the size and number of layers of the precoding information, the second precoding information, and / or the number of antenna ports may be L1, M1, and / or N1 bits, respectively.

[0363] L0 may be greater than or equal to L1, M0 may be greater than or equal to M1, and N0 may be greater than or equal to N1. Alternatively, or in addition, L0+M0+N0 may be greater than or equal to L1+M1+N1.

[0364] 12 shows an example of payload size after bit field size alignment for DCI format 0_1 ​​with CRC scrambled by C-RNTI. For a UE with a transform precoder field configured in DCI format 0_1 ​​(i.e., the RRC parameter dynamicSwitchingTransformPrecoder is provided), if the bit width of a field in DCI format 0_1 ​​with CRC scrambled by C-RNTI and the value of the transform precoder field set to 0 (value #0) is not equal to the bit width of the corresponding field in DCI format 0_1 ​​for the same serving cell with CRC scrambled by C-RNTI and the value of the transform precoder field set to 1 (value #1), the C-RNTI may be scrambled by the UE. In the field in DCI format 0_1 ​​where the CRC is scrambled by the NTI and the value of the transform precoder field is set to 1 (value #1), a certain number of most significant bits with a value set to "0" are inserted until the bit width of the field in DCI format 0_1 ​​where the CRC is scrambled by the C-RNTI and the value of the transform precoder field is set to 0 (value #0) is equal to the bit width of the corresponding field in DCI format 0_1 ​​for the same serving cell where the CRC is scrambled by the C-RNTI and the value of the transform precoder field is set to 1 (value #1). If L0 is greater than L1, L0-L1 bits may be inserted (bit padding) into the precoding information and layer number fields. If M0 is greater than M1, M0-M1 bits may be inserted (bit padding) into the second precoding information field. If N0 is greater than N1, N0-N1 bits may be inserted (bit padding) into the antenna port field. With this bit field size alignment, the payload size of DCI format 0_1 ​​with CRC scrambled by C-RNTI is the same whether the transform precoder field is set to 0 or 1.

[0365] In another example of field size matching, each field size may be matched to a larger field size. For a UE in which a transform precoder field is configured in DCI format 0_1, if the bit width of a field in DCI format 0_1 ​​in which the CRC has been scrambled by the C-RNTI and the value of the transform precoder field has been set to 0 (value #0) is not equal to the bit width of the corresponding field in DCI format 0_1 ​​for the same serving cell in which the CRC has been scrambled by the C-RNTI and the value of the transform precoder field has been set to 1 (value #1), a certain number of most significant bits with a value set to "0" are inserted into the field in DCI format 0_1 ​​in which the CRC has been scrambled by the C-RNTI and the value of the transform precoder field has been set to 1 (value #1) for the same serving cell in which the CRC has been scrambled by the C-RNTI and the value of the transform precoder field has been set to 1 (value #1) with the smaller size until the bit width of the field in DCI format 0_1 ​​in which the CRC has been scrambled by the C-RNTI and the value of the transform precoder field has been set to 1 (value #1) with the corresponding field.

[0366] In either example, the UE may attempt to decode the PDCCH while assuming the size-aligned DCI payload size. The UE may remove the padded bits from those fields before determining what values ​​those fields were set to. In other words, the UE may assume that the range of values ​​for the field is determined by the field bit width, not including the padded bits.

[0367] 13 shows an example of bit field size matching between DCI format 0_1 ​​with CRC scrambled by C-RNTI and DCI format 0_1 ​​with CRC scrambled by CS-RNTI and NDI=0. After field size matching between DCI format 0_1 ​​with transform precoder value set to 0 and CRC scrambled by C-RNTI and DCI format 0_1 ​​with transform precoder value set to 1 and CRC scrambled by C-RNTI, the size and layer of the precoding information, the second precoding information, and / or the number of antenna ports may be L0, M0, and / or N0 bits, respectively, as shown in the left part of the figure.

[0368] The size of some information fields of DCI format 0_1 ​​whose CRC is scrambled by the C-RNTI (e.g., precoding information and number of layers, second precoding information, antenna port, PTRS-DMRS association, second PTRS-DMRS association, DMRS sequence initialization) may vary depending on the value and / or waveform of the NDI field of that same DCI format.

[0369] The sizes of these fields in DCI format 0_1 ​​with NDI=0 and CRC scrambled by C-RNTI before bit padding may be determined based on the RRC parameter transformPrecoder included in the RRC information element configuredGrantConf, if the RRC parameter transformPrecoder included in the RRC information element configuredGrantConf is provided from the gNB to the UE, regardless of whether the RRC parameter dynamicSwitchingTransformPrecoder is provided and / or the value of the RRC parameter dynamicSwitchingTransformPrecoder. The sizes of these fields before bit padding may be determined based on the RRC parameter msg3-transformPrecoder in RACH-ConfigCommon, if the RRC parameter transformPrecoder included in the RRC information element configuredGrantConf is not provided from the gNB to the UE, regardless of whether the RRC parameter dynamicSwitchingTransformPrecoder is provided and / or the value of the RRC parameter dynamicSwitchingTransformPrecoder. In this case, if dynamicSwitchingTransformPrecoder set to "enabled" is not provided, the transform precoder field may not be included in DCI format 0_1 ​​whose CRC is scrambled by the C-RNTI, whereas if dynamicSwitchingTransformPrecoder set to "enabled" is provided for at least DCI format 0_1 ​​whose CRC is scrambled by the C-RNTI, the transform precoder field may be included in DCI format 0_1 ​​whose CRC is scrambled by the C-RNTI, and the transform precoder field may be reserved.

[0370] Alternatively, the sizes of these fields in DCI format 0_1 ​​with NDI=0 and CRC scrambled by C-RNTI before bit padding may be determined based on the RRC parameter transformPrecoder included in the RRC information element configuredGrantConf if the RRC parameter transformPrecoder included in the RRC information element configuredGrantConf is provided from the gNB to the UE and the RRC parameter dynamicSwitchingTransformPrecoder set to "enabled" for the CG-PUSCH is not configured. The sizes of these fields before bit padding may be determined based on the RRC parameter msg3-transformPrecoder in RACH-ConfigCommon if the RRC parameter transformPrecoder included in the RRC information element configuredGrantConf is not provided from the gNB to the UE and the RRC parameter dynamicSwitchingTransformPrecoder set to "enabled" for the CG-PUSCH is not configured. In these cases, if dynamicSwitchingTransformPrecoder set to "enabled" is not provided, then the transform precoder field may not be included in DCI format 0_1 ​​whose CRC is scrambled by the CS-RNTI, whereas if dynamicSwitchingTransformPrecoder set to "enabled" is provided for at least DCI format 0_1 ​​whose CRC is scrambled by the CS-RNTI, then the transform precoder field may be included in DCI format 0_1 ​​whose CRC is scrambled by the CS-RNTI and the transform precoder field may be reserved.If the RRC parameter dynamicSwitchingTransformPrecoder set to "enabled" is configured for the CG-PUSCH, the size before bit padding of these fields in DCI format 0_1 ​​with NDI=0 and C-RNTI CRC scrambled may be determined based on the value of the Transform Precoding field of that same DCI format. In this case, the value of the Transform Precoding field may indicate whether transform precoding is enabled or disabled for the CG-PUSCH activated by this DCI format.

[0371] Before bit padding, the size and number of layers of the precoding information in DCI format 0_1 ​​with NDI=0, CRC scrambled by CS-RNTI, the second precoding information, and / or the antenna port may be L2, M2, and / or N2 bits, respectively. As shown in the right part of the figure, if L0 is greater than L2, L0-L2 bits may be inserted (bit padded) into the precoding information and number of layers field in DCI format 0_1 ​​with NDI=0, CRC scrambled by C-RNTI. Similarly, if M0 is greater than M2, M0-M2 bits may be inserted (bit padded) into the second precoding information field. Similarly, if N0 is greater than N2, N0-N2 bits may be inserted (bit padded) into the antenna port field. With this bit field size alignment, the payload size of DCI format 0_1 ​​with NDI=0 and CRC scrambled by CS-RNTI is the same after alignment for DCI format 0_1 ​​with CRC scrambled by C-RNTI when the transform precoder field is set to 0 and when the transform precoder field is set to 1.

[0372] 14 shows an example of bit field size matching between DCI format 0_1 ​​with CRC scrambled by C-RNTI and DCI format 0_1 ​​with CRC scrambled by C-RNTI and NDI=1. After field size matching between DCI format 0_1 ​​with CRC scrambled by C-RNTI and transform precoder value set to 0 and DCI format 0_1 ​​with CRC scrambled by C-RNTI and transform precoder value set to 1, the size and layer of the precoding information, the second precoding information, and / or the number of antenna ports may be L0, M0, and / or N0 bits, respectively, as shown in the left part of the figure.

[0373] The size of some information fields of DCI format 0_1 ​​whose CRC is scrambled by the C-RNTI (e.g., precoding information and number of layers, second precoding information, antenna port, PTRS-DMRS association, second PTRS-DMRS association, DMRS sequence initialization) may vary depending on the value and / or waveform of the NDI field of that same DCI format.

[0374] The sizes of these fields in DCI format 0_1 ​​with NDI=1 and CRC scrambled by C-RNTI before bit padding may be determined based on the RRC parameter transformPrecoder included in the RRC information element PUSCH-Config, if the RRC parameter transformPrecoder included in the RRC information element PUSCH-Config is provided from the gNB to the UE, regardless of whether the RRC parameter dynamicSwitchingTransformPrecoder is provided and / or the value of the RRC parameter dynamicSwitchingTransformPrecoder. The sizes of these fields before bit padding may be determined based on the RRC parameter msg3-transformPrecoder in RACH-ConfigCommon, if the RRC parameter transformPrecoder included in the RRC information element PUSCH-Config is not provided from the gNB to the UE, regardless of whether the RRC parameter dynamicSwitchingTransformPrecoder is provided and / or the value of the RRC parameter dynamicSwitchingTransformPrecoder. In this case, if dynamicSwitchingTransformPrecoder set to "enabled" is not provided, the transform precoder field may not be included in DCI format 0_1 ​​whose CRC is scrambled by the CS-RNTI, whereas if dynamicSwitchingTransformPrecoder set to "enabled" is provided for at least DCI format 0_1 ​​whose CRC is scrambled by the C-RNTI, the transform precoder field may be included in DCI format 0_1 ​​whose CRC is scrambled by the CS-RNTI, and the transform precoder field may be reserved.

[0375] Alternatively, the size before bit padding of these fields in DCI format 0_1 ​​with NDI=1 and C-RNTI CRC scrambled may be determined based on the RRC parameter transformPrecoder included in the RRC information element PUSCH-Config if the RRC parameter transformPrecoder included in the RRC information element PUSCH-Config is provided from the gNB to the UE and dynamicSwitchingTransformPrecoder set to "enabled" is not configured for DG-PUSCH. The size before bit padding of these fields may be determined based on the RRC parameter msg3-transformPrecoder in RACHConfigCommon if the RRC parameter transformPrecoder included in the RRC information element PUSCH-Config is not provided from the gNB to the UE and dynamicSwitchingTransformPrecoder set to "enabled" is not configured for DG-PUSCH. In these cases, if dynamicSwitchingTransformPrecoder set to "enabled" is not provided, the transform precoder field may not be included in DCI format 0_1 ​​CRC-scrambled by CS-RNTI, whereas if dynamicSwitchingTransformPrecoder set to "enabled" is provided for at least DCI format 0_1 ​​CRC-scrambled by C-RNTI, the transform precoder field may be included in DCI format 0_1 ​​CRC-scrambled by CS-RNTI and the transform precoder field may be reserved. If the RRC parameter dynamicSwitchingTransformPrecoder set to "enabled" is configured for DG-PUSCH, the size before bit padding of these fields in DCI format 0_1 ​​CRC-scrambled by CS-RNTI and NDI=0 may be determined based on the value of the transform precoding field of that same DCI format.In this case, the value of the transform precoding field may indicate whether transform precoding is enabled or disabled for the CG-PUSCH activated by this DCI format.

[0376] Further alternatively, the sizes of these fields in DCI format 0_1 ​​with NDI=1 and CRC scrambled by CS-RNTI before bit padding may be determined based on the RRC parameter transformPrecoder included in the RRC information element PUSCH-Config if the RRC parameter transformPrecoder included in the RRC information element PUSCH-Config is provided from the gNB to the UE and the RRC parameter dynamicSwitchingTransformPrecoder set to "enabled" for the CG-PUSCH is not configured. The sizes of these fields before bit padding may be determined based on the RRC parameter msg3-transformPrecoder in RACH-ConfigCommon if the RRC parameter transformPrecoder included in the RRC information element PUSCH-Config is not provided from the gNB to the UE and the RRC parameter dynamicSwitchingTransformPrecoder set to "enabled" for the CG-PUSCH is not configured. In these cases, if dynamicSwitchingTransformPrecoder set to "enabled" is not provided, the DCI format 0_1 ​​with CRC scrambled by the CS-RNTI may not include a transform precoder field, whereas if dynamicSwitchingTransformPrecoder set to "enabled" is provided for at least DCI format 0_1 ​​with CRC scrambled by the C-RNTI, the transform precoder field may be included in DCI format 0_1 ​​with CRC scrambled by the CS-RNTI and the transform precoder field may be reserved. If the RRC parameter dynamicSwitchingTransformPrecoder set to "enabled" is configured for CG-PUSCH, the size before bit padding of these fields of DCI format 0_1 ​​with NDI=0 with CRC scrambled by the C-RNTI may be determined based on the value of the transform precoding field of that same DCI format.In this case, the value of the transform precoding field may indicate whether transform precoding is enabled or disabled for the CG-PUSCH activated by this DCI format. The UE may not expect dynamicSwitchingTransformPrecoder set to "enabled" for the DG-PUSCH to be configured without simultaneously configuring dynamicSwitchingTransformPrecoder set to "enabled" for the CG-PUSCH.

[0377] Before bit padding, the size and number of layers of the precoding information in DCI format 0_1 ​​with NDI=1, CRC scrambled by CS-RNTI, the second precoding information, and / or the antenna port may be L3, M3, and / or N3 bits, respectively. As shown in the right part of the figure, if L0 is greater than L3, L0-L3 bits may be inserted (bit padded) into the precoding information and number of layers field in DCI format 0_1 ​​with NDI=0, CRC scrambled by C-RNTI. Similarly, if M0 is greater than M3, M0-M3 bits may be inserted (bit padded) into the second precoding information field. Similarly, if N0 is greater than N3, N0-N3 bits may be inserted (bit padded) into the antenna port field. With this bit field size alignment, the payload size of DCI format 0_1 ​​with NDI=1 and CRC scrambled by CS-RNTI is the same after alignment for DCI format 0_1 ​​with CRC scrambled by C-RNTI when the transform precoder field is set to 0 and when the transform precoder field is set to 1.

[0378] The above procedure can also be written as follows: The UE may not expect the bit-width of a field in DCI format 0_1 ​​with CRC scrambled by the C-RNTI to be larger than the corresponding bit-width of the same field in DCI format 0_1 ​​with CRC scrambled by the CS-RNTI for the same serving cell after insertion of significant bits with value set to '0' is applied. If the bit width of a field in DCI format 0_1 ​​whose CRC is scrambled by the CS-RNTI is not equal to the corresponding bit width of the same field in DCI format 0_1 ​​whose CRC is scrambled by the C-RNTI for the same serving cell after insertion of high-order bits set to value "0" has been applied, then a certain number of most significant bits set to value "0" are inserted into that field in DCI format 0_1 ​​whose CRC is scrambled by the CS-RNTI until its bit width is equal to the bit width of the corresponding field in DCI format 0_1 ​​whose CRC is scrambled by the C-RNTI after insertion of high-order bits set to value "0" has been applied.

[0379] The UE may not expect the bit-width of a field in DCI format 0_1 ​​whose CRC is scrambled by the CS-RNTI to be larger than the corresponding bit-width of the same field in DCI format 0_1 ​​whose CRC is scrambled by the C-RNTI for the same serving cell before the insertion of the most significant bit set to the value "0" is applied. Alternatively, or in addition, the UE may assume the same transformation precoder field value and not expect the bit-width of a field in DCI format 0_1 ​​whose CRC is scrambled by the CS-RNTI to be larger than the corresponding bit-width of the same field in DCI format 0_1 ​​whose CRC is scrambled by the C-RNTI for the same serving cell before the insertion of the most significant bit set to the value "0" is applied.

[0380] 15 shows an example of payload size after payload size matching for DCI format 0_1 ​​with CRC scrambled by C-RNTI. For a UE with a transform precoder field configured in DCI format 0_1, if the number of information bits before padding in DCI format 0_1 ​​with CRC scrambled by C-RNTI and transform precoder field set to a value of 0 (value #0) is not equal to the number of information bits in DCI format 0_1 ​​with CRC scrambled by C-RNTI and transform precoder field set to a value of 1 (value #1) for the same serving cell, zeros are added to DCI format 0_1 ​​with transform precoder field set to a value of 1 (value #1) until the payload size is the same as DCI format 0_1 ​​with transform precoder field set to a value of 0 (value #0). If P0 (the total payload size before padding in DCI format 0_1 ​​in which the CRC is scrambled by the C-RNTI and the value of the transform precoder field is set to 0 (value #0)) is greater than P1 (the total payload size before padding in DCI format 0_1 ​​in which the CRC is scrambled by the C-RNTI and the value of the transform precoder field is set to 1 (value #1)), P0-P1 bits may be inserted (bit padding) into DCI format 0_1 ​​in which the CRC is scrambled by the C-RNTI and the value of the transform precoder field is set to 1 (value #1).

[0381] In another example of payload size alignment, the payload size may be aligned to a larger payload size. For a UE configured with a transform precoder field in DCI format 0_1, if the number of information bits before padding in DCI format 0_1 ​​CRC-scrambled by C-RNTI and with the transform precoder field set to a value of 0 (value #0) is not equal to the number of information bits in DCI format 0_1 ​​CRC-scrambled by C-RNTI and with the transform precoder field set to a value of 1 (value #1) for the same serving cell, zeros may be added to the smaller size DCI format 0_1 ​​until the payload sizes are the same.

[0382] With regard to field size matching between the C-RNTI and the CS-RNTI, the larger size between the two waveforms may be assumed for the C-RNTI. More specifically, if the bit width of a field in DCI format 0_1 ​​with CRC scrambled by the C-RNTI is not equal to the bit width of the corresponding field in DCI format 0_1 ​​with CRC scrambled by the C-RNTI assuming a transformed precoding field value requiring a larger size for the same serving cell, a certain number of most significant bits having a value set to "0" are inserted into that field in DCI format 0_1 ​​with CRC scrambled by the CS-RNTI until its bit width is equal to the bit width of the corresponding field in DCI format 0_1 ​​with CRC scrambled by the C-RNTI assuming a transformed precoding field value requiring a larger size for the same serving cell. Assuming that the size of any field of DCI format 0_1 ​​in which the transform precoder field value is set to 0 is greater than or equal to the field size of DCI format 0_1 ​​in which the transform precoder field value is set to 1, the result of field size matching between the C-RNTI and the CS-RNTI may be the same as that shown in Figures 13 and 14.

[0383] All procedures described above for DCI format 0_1 ​​may also be applicable to DCI format 0_2.

[0384] It should be noted that if there is no difference in terms of field size or DCI payload size, then bit padding may not be performed for each field or DCI format.

[0385] FIG. 16 illustrates an example of a method for a UE. The method may include obtaining at least a first RRC parameter for indicating the presence of a first information field in a DCI format (step 1601), where the first information field indicates whether a transform precoder is enabled or disabled for a PUSCH. The method may also include monitoring a C-RNTI-CRC-scrambled DCI format and a CS-RNTI-CRC-scrambled DCI format (step 1602). A first number of bits may be included in a second information field of the C-RNTI-CRC-scrambled DCI format in which the first information field indicates the transform precoder as disabled. If a second number of bits included in the second information field of the CS-RNTI-CRC-scrambled DCI format is not equal to the first number, most significant bits with a value of "0" may be inserted in the second information field of the CS-RNTI-CRC-scrambled DCI format until the second number is equal to the first number.

[0386] FIG. 17 illustrates an example of a method of a base station. The method may include sending at least a first RRC parameter for indicating the presence of a first information field in a DCI format (step 1701), where the first information field indicates whether a transform precoder is enabled or disabled for the PUSCH. The method may also include transmitting a DCI format with a CRC scrambled by the C-RNTI and a DCI format with a CRC scrambled by the CS-RNTI (step 1702). A first number of bits may be included in a second information field of the DCI format with a CRC scrambled by the C-RNTI and where the transform precoder is indicated as disabled in the first information field. If the second number of bits included in the second information field of the DCI format with a CRC scrambled by the CS-RNTI is not equal to the first number, most significant bits with a value of "0" may be inserted in the second information field of the DCI format with a CRC scrambled by the CS-RNTI until the second number is equal to the first number.

[0387] Each of the programs executed in the base station device and the terminal device according to one aspect of the present invention may be a program that controls a CPU (Central Processing Unit) or the like so that the program operates a computer to realize the functions of the above-mentioned embodiment of the present invention. Information processed in these devices is temporarily stored in a random access memory (RAM) while being processed. The information is then stored in various types of read-only memory (ROM), such as a flash ROM and a hard disk drive (HDD), and is read by the CPU for modification or rewriting, as necessary. Note that the terminal device 1 and the base station device 3 according to the above-mentioned embodiment may be partially achieved by a computer. In this case, this configuration may be realized by recording a program for realizing such a control function on a computer-readable recording medium and having a computer system read the program recorded on the recording medium for execution.

[0388] It should be noted that the "computer system" referred to here refers to a computer system incorporated in the terminal device 1 or the base station device 3, and is assumed to include hardware components such as an OS and peripheral devices. Furthermore, the "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage devices incorporated in a computer system such as hard disks.

[0389] Furthermore, the "computer-readable recording medium" may include a medium that dynamically holds a program for a short period of time, such as a communication line used to transmit a program via a network such as the Internet or via a communication line such as a telephone line, and may also include a medium that holds a program for a certain period of time, such as a volatile memory in a computer system that functions as a server or a client in such cases. Furthermore, the program may be configured to realize part of the above functions, or may be configured to be able to realize the above functions in combination with a program already recorded in a computer system.

[0390] Furthermore, the base station device 3 according to the above embodiment may be realized as an aggregation (device group) including multiple devices. Each of the devices constituting such a device group may include some or all of the functions or functional blocks of the base station device 3 according to the above embodiment. The device group may include general functions or respective functional blocks of each of the base station devices 3. Furthermore, the terminal device 1 according to the above embodiment may also communicate with the base station device as an aggregation.

[0391] Furthermore, the base station device 3 according to the above embodiment may function as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and / or an NG-RAN (Next Gen RAN, NR-RAN). Furthermore, the base station device 3 according to the above embodiment may have some or all of the functions of a node higher than an eNodeB or a gNB.

[0392] Furthermore, a part or all of each of the terminal device 1 and the base station device 3 according to the above-mentioned embodiment may be realized as an LSI, which is typically an integrated circuit, or may be realized as a chip set. Each functional block of the terminal device 1 and the base station device 3 may be realized individually as a chip, or a part or all of the functional block may be integrated into a chip.

[0393] Furthermore, the circuit integration technique is not limited to LSI, but can be realized by a dedicated circuit or a general-purpose processor. Furthermore, when a circuit integration technology that replaces LSI appears due to the progress of semiconductor technology, it is also possible to use an integrated circuit based on that technology.

[0394] Furthermore, in the above embodiment, the terminal device is described as an example of a communication device, but the present invention is not limited to such terminal devices and is applicable to terminal devices or communication devices of fixed or stationary electronic devices installed indoors or outdoors, such as audio-video (AV) devices, kitchen devices, cleaning machines or washing machines, air conditioning devices, office equipment, vending machines, and other household devices.

[0395] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to the embodiments, and includes, for example, modifications to the design within the scope of the present invention. Furthermore, various modifications are possible within the scope of one aspect of the present invention defined by the claims, and embodiments created by appropriately combining technical means disclosed according to different embodiments are also included in the technical scope of the present invention. Furthermore, configurations in which components described in each embodiment and having the same effect are replaced with each other are also included in the technical scope of the present invention.

Claims

1. A user equipment (UE), an upper layer processing circuit configured to obtain at least a first RRC parameter for indicating the presence of a first information field in a DCI format, the first information field indicating whether a transform precoder is enabled or disabled for a PUSCH; and a receiving circuit configured to monitor the DCI format whose CRC is scrambled by a C-RNTI and the DCI format whose CRC is scrambled by a CS-RNTI; The first information field is included in the DCI format in which a CRC is scrambled by a CS-RNTI; If the first RRC parameter is set to valid, the first information field is reserved; the first information field is a 1-bit field, a second information field of the DCI format in which a CRC is scrambled by a C-RNTI and the transform precoder is indicated as disabled in the first information field includes a first number of bits; if a second number of bits included in the second information field of the DCI format in which a CRC is scrambled by a CS-RNTI is not equal to the first number, most significant bits having a value of "0" are inserted into the second information field of the DCI format in which a CRC is scrambled by a CS-RNTI until the second number becomes equal to the first number; User Equipment (UE).

2. a CRC is scrambled by a C-RNTI, and the second information field of the DCI format in which the transform precoder is indicated as valid in the first information field includes a third number of bits; If the third number is not equal to the first number, a CRC is scrambled by a C-RNTI, and a most significant bit having a value of "0" is inserted into the second information field of the DCI format in which the transform precoder is indicated as valid in the first information field, until the third number becomes equal to the first number. The UE of claim 1.

3. a fourth number of bits is included in the DCI format in which a CRC is scrambled by a C-RNTI and the transform precoder is indicated as disabled in the first information field; the DCI format, in which the CRC is scrambled by the C-RNTI and the transform precoder is indicated as valid in the first information field, includes a fifth number of bits; If the fourth number is not equal to the fifth number, a CRC is scrambled by a C-RNTI, and bits having a value of "0" are inserted into the DCI format in which the transform precoder is indicated as valid in the first information field until the fifth number becomes equal to the fourth number. The UE of claim 1.

4. A base station, an upper layer processing circuit configured to obtain at least a first RRC parameter for indicating the presence of a first information field in a DCI format, the first information field indicating whether a transform precoder is enabled or disabled for a PUSCH; and a receiving circuit configured to monitor the DCI format whose CRC is scrambled by a C-RNTI and the DCI format whose CRC is scrambled by a CS-RNTI; The first information field is included in the DCI format in which a CRC is scrambled by a CS-RNTI; If the first RRC parameter is set to valid, the first information field is reserved; the first information field is a 1-bit field, a second information field of the DCI format in which a CRC is scrambled by a C-RNTI and the transform precoder is indicated as disabled in the first information field includes a first number of bits; if a second number of bits included in the second information field of the DCI format in which a CRC is scrambled by a CS-RNTI is not equal to the first number, most significant bits having a value of "0" are inserted into the second information field of the DCI format in which a CRC is scrambled by a CS-RNTI until the second number becomes equal to the first number; User Equipment (UE).

5. a CRC is scrambled by a C-RNTI, and the second information field of the DCI format in which the transform precoder is indicated as valid in the first information field includes a third number of bits; If the third number is not equal to the first number, a CRC is scrambled by a C-RNTI, and a most significant bit having a value of "0" is inserted into the second information field of the DCI format in which the transform precoder is indicated as valid in the first information field, until the third number becomes equal to the first number. The base station of claim 4.

6. a fourth number of bits is included in the DCI format in which a CRC is scrambled by a C-RNTI and the transform precoder is indicated as disabled in the first information field; the DCI format, in which the CRC is scrambled by the C-RNTI and the transform precoder is indicated as valid in the first information field, includes a fifth number of bits; If the fourth number is not equal to the fifth number, a CRC is scrambled by a C-RNTI, and bits having a value of "0" are inserted into the DCI format in which the transform precoder is indicated as valid in the first information field until the fifth number becomes equal to the fourth number. The base station of claim 4.

7. 1. A method for a user equipment (UE), the method comprising: obtaining at least a first RRC parameter to indicate the presence of a first information field in a DCI format, the first information field indicating whether a transform precoder is enabled or disabled for a PUSCH; monitoring the DCI format whose CRC is scrambled by a C-RNTI and the DCI format whose CRC is scrambled by a C-RNTI; The first information field is included in the DCI format in which a CRC is scrambled by a CS-RNTI; If the first RRC parameter is set to valid, the first information field is reserved; the first information field is a 1-bit field, a second information field of the DCI format in which a CRC is scrambled by a C-RNTI and the transform precoder is indicated as disabled in the first information field includes a first number of bits; if a second number of bits included in the second information field of the DCI format in which a CRC is scrambled by a CS-RNTI is not equal to the first number, most significant bits having a value of "0" are inserted into the second information field of the DCI format in which a CRC is scrambled by a CS-RNTI until the second number becomes equal to the first number; A method for a user equipment (UE).

Images