WO2024034443A1 - Dispositif terminal, dispositif de station de base et procédé de communication - Google Patents

Dispositif terminal, dispositif de station de base et procédé de communication Download PDF

Info

Publication number
WO2024034443A1
WO2024034443A1 PCT/JP2023/027914 JP2023027914W WO2024034443A1 WO 2024034443 A1 WO2024034443 A1 WO 2024034443A1 JP 2023027914 W JP2023027914 W JP 2023027914W WO 2024034443 A1 WO2024034443 A1 WO 2024034443A1
Authority
WO
WIPO (PCT)
Prior art keywords
pusch
terminal device
codebook
srs
resource
Prior art date
Application number
PCT/JP2023/027914
Other languages
English (en)
Japanese (ja)
Inventor
涼太 森本
一成 横枕
崇久 福井
樺 万
Original Assignee
シャープ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by シャープ株式会社 filed Critical シャープ株式会社
Publication of WO2024034443A1 publication Critical patent/WO2024034443A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/0413—MIMO systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/0413—MIMO systems
    • H04B7/0456—Selection of precoding matrices or codebooks, e.g. using matrices antenna weighting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/24—Cell structures
    • H04W16/28—Cell structures using beam steering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource

Definitions

  • the present invention relates to a terminal device, a base station device, and a communication method.
  • This application claims priority to Japanese Patent Application No. 2022-125992 filed in Japan on August 8, 2022, and the contents thereof are incorporated herein.
  • LTE Long Term Evolution
  • EUTRA Evolved Universal Terrestrial Radio Access
  • 3GPP Third Generation Partnership Project
  • a base station device is also called an eNodeB (evolved NodeB)
  • a terminal device is also called a UE (User Equipment).
  • LTE is a cellular communication system in which multiple areas covered by base station devices are arranged in the form of cells. A single base station device may manage multiple serving cells.
  • NR New Radio
  • IMT International Mobile Telecommunication
  • ITU International Telecommunication Union
  • Non-patent Document 1 NR is required to meet the requirements of three scenarios within the framework of a single technology: eMBB (enhanced Mobile BroadBand), mmTC (massive Machine Type Communication), and URLLC (Ultra Reliable and Low Latency Communication). .
  • Non-Patent Document 2 In 3GPP, consideration is being given to expanding the services supported by NR (Non-Patent Document 2).
  • One aspect of the present invention provides a terminal device that communicates efficiently, a communication method used in the terminal device, a base station device that communicates efficiently, and a communication method used in the base station device.
  • a first aspect of the present invention is a terminal device, comprising: a receiving unit that receives a PDCCH in which a DCI that schedules a PUSCH is arranged; and a transmitting unit that transmits the PUSCH;
  • An RRC parameter and a second RRC parameter are set, the first RRC parameter is information for determining the number of SRS ports of the SRS resource instructed by the DCI, and the second RRC parameter is Information for defining a codebook subset for the PUSCH, and if the number of SRS ports is greater than 4 and the second RRC parameter is the first coherent type, the first codebook type is selected and the number of SRS ports is greater than 4, and the second RRC parameter is a second coherent type, a second codebook type is selected and the number of SRS ports is greater than 4.
  • a third codebook type is selected, and if the number of SRS ports is 4 or less, the second codebook type is selected. and determining a precoding matrix for the PUSCH based at least on the DCI and the selected codebook type.
  • the first coherent type is one or both of fullyAndPartialAndNonCoherent and fullyCoherent.
  • the second coherent type is part or all of partialAndNonCoherent, partialCoherent, 4portsPartialCoherent, and 2portsPartialCoherent.
  • the third coherent type is nonCoherent.
  • the first codebook type is Type I Single-Panel Codebook, TypeI Multi-Panel Codebook, TypeII Codebook, Type II Port Selection Codebook, Enhanced Type II Codebook, Enhanced Type II Port Selection Codebook, Further enhancedType II port selection codebook, which is determined based on at least i 1 , i 2 .
  • the second codebook type is a table-based codebook determined based on at least some or all of the number of layers, the number of antenna ports, and the settings of transform precoding.
  • the third codebook type is a codebook determined based on at least a vector for selecting ports.
  • a second aspect of the present invention is a base station device, comprising a transmitter that transmits a PDCCH in which a DCI that schedules a PUSCH is arranged, and a receiver that receives the PUSCH, A first RRC parameter and a second RRC parameter are set, the first RRC parameter is information for determining the number of SRS ports of the SRS resource instructed by the DCI, and the second RRC The parameter is information for defining a codebook subset for the PUSCH, and if the number of SRS ports is greater than 4 and the second RRC parameter is the first coherent type, the first If the number of SRS ports is greater than 4, and the second RRC parameter is a second coherent type, a second codebook type is selected.
  • a third codebook type is selected; Knowing that if the number of SRS ports is 4 or less, the second codebook type is selected, and the precoding matrix for the PUSCH is determined based at least on the DCI and the selected codebook type. Understand what will be decided.
  • the first coherent type is one or both of fullyAndPartialAndNonCoherent and fullyCoherent.
  • the second coherent type is part or all of partialAndNonCoherent, partialCoherent, 4portsPartialCoherent, and 2portsPartialCoherent.
  • the third coherent type is nonCoherent.
  • the first codebook type is Type I Single-Panel Codebook, Type I Multi-Panel Codebook, Type II Codebook, Type II Port Selection Codebook, Enhanced Type II Codebook, Enhanced Type II Port Selection Codebook, Further An expression-based codebook determined based on at least i 1 , i 2 , including part or all of the enhanced Type II port selection codebook.
  • the second codebook type is a table-based codebook determined based on at least some or all of the number of layers, the number of antenna ports, and the settings of transform precoding.
  • the third codebook type is a codebook determined based on at least a vector for selecting ports.
  • a third aspect of the present invention is a communication method used in a terminal device, which includes the steps of receiving a PDCCH in which a DCI that schedules a PUSCH is arranged, and transmitting the PUSCH.
  • a first RRC parameter and a second RRC parameter are set, the first RRC parameter is information for determining the number of SRS ports of the SRS resource instructed by the DCI, and the second The RRC parameter is information for defining a codebook subset for the PUSCH, and if the number of SRS ports is greater than 4, and the second RRC parameter is the first coherent type, If a first codebook type is selected and the number of SRS ports is greater than 4, and if the second RRC parameter is a second coherent type, a second codebook type is selected and the SRS If the number of ports is greater than 4, and the second RRC parameter is a third coherent type, a third codebook type is selected; if the number of SRS ports is less than or equal to 4, the second A codebook type is selected, and a
  • the terminal device can communicate efficiently. Furthermore, the base station device can communicate efficiently.
  • FIG. 1 is a conceptual diagram of a wireless communication system according to one aspect of the present embodiment.
  • 3 is an example showing the relationship among the subcarrier interval setting ⁇ , the number of OFDM symbols per slot N slot symb , and the CP (cyclic prefix) setting according to one aspect of the present embodiment.
  • FIG. 2 is a diagram illustrating an example of a method for configuring a resource grid according to an aspect of the present embodiment.
  • FIG. 3 is a diagram illustrating a configuration example of a resource grid 3001 according to one aspect of the present embodiment.
  • 1 is a schematic block diagram showing a configuration example of a base station device 3 according to an aspect of the present embodiment.
  • FIG. 1 is a schematic block diagram showing a configuration example of a terminal device 1 according to an aspect of the present embodiment.
  • FIG. FIG. 2 is a diagram illustrating a configuration example of an SS/PBCH block according to an aspect of the present embodiment.
  • FIG. 7 is a diagram illustrating an example of a monitoring opportunity for a search area set according to an aspect of the present embodiment.
  • FIG. 3 is a diagram illustrating an example of a method of applying a precoding matrix according to an aspect of the present embodiment.
  • Floor (C) may be a floor function for real number C.
  • floor(C) may be a function that outputs the largest integer within a range that does not exceed the real number C.
  • ceil(D) may be a ceiling function for the real number D.
  • ceil(D) may be a function that outputs the smallest integer not less than the real number D.
  • mod (E, F) may be a function that outputs the remainder when E is divided by F.
  • mod (E, F) may be a function that outputs a value corresponding to the remainder when E is divided by F.
  • exp(G) e ⁇ G.
  • e is Napier's number.
  • H ⁇ I indicates H to the I power.
  • max(J, K) is a function that outputs the maximum value of J and K.
  • max(J, K) is a function that outputs J or K when J and K are equal.
  • min(L, M) is a function that outputs the maximum value of L and M.
  • min(L, M) is a function that outputs L or M when L and M are equal.
  • round(N) is a function that outputs the integer value closest to N. “ ⁇ ” indicates multiplication.
  • At least OFDM Orthogonal Frequency Division Multiplex
  • An OFDM symbol is a time domain unit of OFDM.
  • An OFDM symbol includes at least one or more subcarriers. OFDM symbols are converted into time-continuous signals in baseband signal generation.
  • CP-OFDM Cyclic Prefix - Orthogonal Frequency Division Multiplex
  • DFT-s-OFDM Discrete Fourier Transform - spread - Orthogonal Frequency Division Multiplex
  • the OFDM symbol may have a name that includes a CP added to the OFDM symbol. That is, a certain OFDM symbol may be configured to include the certain OFDM symbol and the CP added to the certain OFDM symbol.
  • FIG. 1 is a conceptual diagram of a wireless communication system according to one aspect of this embodiment.
  • the wireless communication system is configured to include at least terminal devices 1A to 1C and a base station device 3 (BS#3: Base station#3).
  • BS#3 Base station#3
  • the terminal devices 1A to 1C will also be referred to as terminal device 1 (UE#1: User Equipment#1).
  • the base station device 3 may be configured to include one or more transmitting devices (or transmitting points, transmitting/receiving devices, transmitting/receiving points). When the base station device 3 is configured with a plurality of transmitting devices, each of the plurality of transmitting devices may be arranged at a different position.
  • the base station device 3 may provide one or more serving cells.
  • a serving cell may be defined as a set of resources used for wireless communication. Further, the serving cell is also called a cell.
  • a serving cell may be configured to include one or both of one downlink component carrier (downlink carrier) and one uplink component carrier (uplink carrier).
  • a serving cell may be configured to include one or both of two or more downlink component carriers and two or more uplink component carriers.
  • Downlink component carriers and uplink component carriers are also collectively referred to as component carriers (carriers).
  • one resource grid may be provided for each component carrier. Also, one resource grid may be provided for each set of one component carrier and a certain subcarrier spacing configuration ⁇ .
  • the subcarrier interval setting ⁇ is also called numerology.
  • one resource grid may be provided for a certain antenna port p, a certain subcarrier spacing setting ⁇ , and a certain set of transmission directions x.
  • the resource grid includes N size, ⁇ grid, x N RB sc subcarriers.
  • the resource grid starts from a common resource block N start, ⁇ grid, x .
  • the common resource block N start, ⁇ grid, x is also called the reference point of the resource grid.
  • the resource grid includes N subframes and ⁇ symb OFDM symbols.
  • subscript x added to the parameters related to the resource grid indicates the transmission direction.
  • subscript x may be used to indicate either a downlink or an uplink.
  • N size, ⁇ grid, and x are offset settings indicated by parameters provided by the RRC layer (for example, the parameter CarrierBandwidth).
  • N start, ⁇ grid, x are band settings indicated by parameters provided by the RRC layer (for example, parameters, OffsetToCarrier).
  • the offset setting and band setting are settings used for configuring an SCS-specific carrier.
  • the subcarrier interval setting ⁇ may be 0, 1, 2, 3, or 4.
  • FIG. 2 is an example showing the relationship among the subcarrier interval setting ⁇ , the number of OFDM symbols per slot N slot symb , and the CP (cyclic prefix) setting according to one aspect of the present embodiment.
  • N slot symb 14
  • N frame 20
  • ⁇ slot 40
  • N slot symb 12
  • the time unit (time unit) T c may be used to express the length of the time domain.
  • ⁇ f max 480kHz.
  • N f 4096.
  • ⁇ f ref is 15kHz.
  • N f,ref is 2048.
  • the transmission of signals on the downlink and/or the transmission of signals on the uplink may be organized into radio frames (system frames, frames) of length T f .
  • a radio frame includes 10 subframes.
  • An OFDM symbol is a time domain unit of one communication method.
  • an OFDM symbol may be a time domain unit of CP-OFDM.
  • the OFDM symbol may be a time domain unit of DFT-s-OFDM.
  • a slot may be configured to include multiple OFDM symbols.
  • one slot may be composed of N slot symb consecutive OFDM symbols.
  • the number and index of slots included in the subframe may be given.
  • the slot index n ⁇ s may be given in ascending order as an integer value ranging from 0 to N subframe, ⁇ slot ⁇ 1 in the subframe.
  • the number and index of slots included in the radio frame may be given.
  • the slot index n ⁇ s,f may be given in ascending order as an integer value ranging from 0 to N frame, ⁇ slot ⁇ 1 in the radio frame.
  • FIG. 3 is a diagram illustrating an example of a method for configuring a resource grid according to an aspect of the present embodiment.
  • the horizontal axis in FIG. 3 indicates the frequency domain.
  • FIG. 3 shows a configuration example of a resource grid with a subcarrier spacing ⁇ 1 in a component carrier 300 and a configuration example of a resource grid with a subcarrier spacing ⁇ 2 in a certain component carrier. In this way, one or more subcarrier intervals may be set for a certain component carrier.
  • the component carrier 300 is a band with a predetermined width in the frequency domain.
  • Point 3000 is an identifier for specifying a certain subcarrier. Point 3000 is also referred to as point A.
  • a common resource block (CRB) set 3100 is a set of common resource blocks for the subcarrier interval setting ⁇ 1 .
  • the common resource block including the point 3000 (the solid black block in the common resource block set 3100 in FIG. 3) is also called the reference point of the common resource block set 3100.
  • the reference point of the common resource block set 3100 may be the common resource block with index 0 in the common resource block set 3100.
  • Offset 3011 is an offset from the reference point of common resource block set 3100 to the reference point of resource grid 3001.
  • the offset 3011 is indicated by the number of common resource blocks for the subcarrier spacing setting ⁇ 1 .
  • the resource grid 3001 includes N size, ⁇ grid1,x common resource blocks starting from the reference point of the resource grid 3001.
  • the offset 3013 is an offset from the reference point of the resource grid 3001 to the reference point (N start, ⁇ BWP, i1 ) of the BWP (BandWidth Part) 3003 of index i1.
  • the common resource block set 3200 is a set of common resource blocks for the subcarrier spacing setting ⁇ 2 .
  • the common resource block including the point 3000 (the solid black block in the common resource block set 3200 in FIG. 3) is also called the reference point of the common resource block set 3200.
  • the reference point of the common resource block set 3200 may be the common resource block with index 0 in the common resource block set 3200.
  • Offset 3012 is an offset from the reference point of common resource block set 3200 to the reference point of resource grid 3002.
  • the offset 3012 is indicated by the number of common resource blocks for subcarrier spacing ⁇ 2 .
  • the resource grid 3002 includes N size, ⁇ grid2,x common resource blocks starting from the reference point of the resource grid 3002.
  • the offset 3014 is an offset from the reference point of the resource grid 3002 to the reference point (N start, ⁇ BWP, i2 ) of the BWP 3004 with index i2.
  • FIG. 4 is a diagram illustrating a configuration example of a resource grid 3001 according to one aspect of this embodiment.
  • the horizontal axis is the OFDM symbol index l sym
  • the vertical axis is the subcarrier index k sc .
  • the resource grid 3001 includes N size, ⁇ grid1, x N RB sc subcarriers, and N subframe, ⁇ symb OFDM symbols.
  • the resource specified by the subcarrier index k sc and the OFDM symbol index l sym is also called a resource element (RE).
  • RE resource element
  • a resource block (RB) includes N RB sc consecutive subcarriers.
  • a resource block is a general term for a common resource block, a physical resource block (PRB), and a virtual resource block (VRB).
  • PRB physical resource block
  • VRB virtual resource block
  • N RB sc 12.
  • a resource block unit is a set of resources corresponding to one OFDM symbol in one resource block. That is, one resource block unit includes 12 resource elements corresponding to one OFDM symbol in one resource block.
  • Common resource blocks for a certain subcarrier spacing setting ⁇ are indexed in ascending order from 0 in the frequency domain in a certain common resource block set.
  • the common resource block with index 0 includes (or collides with, matches) point 3000.
  • Physical resource blocks for a certain subcarrier spacing setting ⁇ are indexed in ascending order from 0 in the frequency domain in a certain BWP.
  • N start, ⁇ BWP, i indicates the reference point of the BWP of index i.
  • a BWP is defined as a subset of common resource blocks included in a resource grid.
  • a BWP includes N size , ⁇ BWP,i common resource blocks starting from a reference point N start , ⁇ BWP,i of the BWP.
  • the BWP configured for a downlink carrier is also called a downlink BWP.
  • BWP configured for uplink component carriers is also referred to as uplink BWP.
  • An antenna port may be defined such that the channel over which symbols at an antenna port are conveyed can be deduced from the channel over which other symbols at that antenna port are conveyed. a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed).
  • a channel may correspond to a physical channel.
  • the symbols may correspond to OFDM symbols.
  • a symbol may correspond to a resource block unit. Additionally, the symbols may correspond to resource elements.
  • the large scale properties of the channel over which symbols are conveyed at one antenna port can be estimated from the channel over which symbols are conveyed at another antenna port means that the two antenna ports are called QCL (Quasi Co-Located ) is called.
  • the large-scale characteristics may include at least long-term characteristics of the channel. Large-scale characteristics include delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. It may contain at least a part or all of it.
  • QCL with respect to beam parameters for the first antenna port and the second antenna port means that the receive beam expected by the receiving side for the first antenna port and the received beam expected by the receiving side for the second antenna port. may be the same (or correspond).
  • Terminal device 1 assumes that two antenna ports are QCL if the large-scale characteristics of the channel in which symbols are transmitted in one antenna port can be estimated from the channel in which symbols are transmitted in another antenna port. may be done.
  • the two antenna ports being QCL may mean that the two antenna ports are assumed to be QCL.
  • Carrier aggregation may mean performing communication using a plurality of aggregated serving cells. Moreover, carrier aggregation may mean performing communication using a plurality of aggregated component carriers. Moreover, carrier aggregation may mean performing communication using a plurality of aggregated downlink component carriers. Moreover, carrier aggregation may be performing communication using a plurality of aggregated uplink component carriers.
  • FIG. 5 is a schematic block diagram showing a configuration example of the base station device 3 according to one aspect of the present embodiment.
  • the base station device 3 includes at least part or all of a radio transmitting/receiving unit (physical layer processing unit) 30 and/or a higher layer processing unit 34.
  • the radio transmitting/receiving section 30 includes at least part or all of an antenna section 31, an RF (Radio Frequency) section 32, and a baseband section 33.
  • the upper layer processing section 34 includes at least part or all of a medium access control layer processing section 35 and a radio resource control (RRC) layer processing section 36 .
  • RRC radio resource control
  • the wireless transmitter/receiver 30 includes at least part or all of a wireless transmitter 30a and a wireless receiver 30b.
  • the device configurations of the baseband section included in the wireless transmitting section 30a and the baseband section included in the wireless receiving section 30b may be the same or different.
  • the device configurations of the RF unit included in the wireless transmitter 30a and the RF unit included in the wireless receiver 30b may be the same or different.
  • the device configurations of the antenna section included in the wireless transmitting section 30a and the antenna section included in the wireless receiving section 30b may be the same or different.
  • the wireless transmitter 30a may generate and transmit a PDSCH baseband signal.
  • the wireless transmitter 30a may generate and transmit a PDCCH baseband signal.
  • the wireless transmitter 30a may generate and transmit a PBCH baseband signal.
  • the wireless transmitter 30a may generate and transmit a baseband signal of a synchronization signal.
  • the wireless transmitter 30a may generate and transmit a PDSCH DMRS baseband signal.
  • the wireless transmitter 30a may generate and transmit a PDCCH DMRS baseband signal.
  • the wireless transmitter 30a may generate and transmit a CSI-RS baseband signal.
  • the wireless transmitter 30a may generate and transmit a DL PTRS baseband signal.
  • the wireless receiving unit 30b may receive PRACH.
  • the radio receiving unit 30b may receive and demodulate PUCCH.
  • the radio receiving unit 30b may receive and demodulate the PUSCH.
  • the radio receiving unit 30b may receive PUCCH DMRS.
  • the radio receiving unit 30b may receive PUSCH DMRS.
  • the wireless receiving unit 30b may receive UL PTRS.
  • the wireless receiving section 30b may receive SRS.
  • the upper layer processing unit 34 outputs downlink data (transport block) to the wireless transmitting/receiving unit 30 (or wireless transmitting unit 30a).
  • the upper layer processing unit 34 processes the MAC (Medium Access Control) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the RRC layer.
  • MAC Medium Access Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • RRC Radio Link Control
  • the medium access control layer processing unit 35 included in the upper layer processing unit 34 performs MAC layer processing.
  • the radio resource control layer processing unit 36 included in the upper layer processing unit 34 performs RRC layer processing.
  • the radio resource control layer processing unit 36 manages various setting information/parameters (RRC parameters) of the terminal device 1.
  • RRC parameters setting information/parameters
  • the radio resource control layer processing unit 36 sets parameters based on the RRC message received from the terminal device 1.
  • the wireless transmitter/receiver 30 performs processing such as modulation and encoding.
  • the wireless transmitter/receiver 30 (or wireless transmitter 30a) modulates, encodes, and generates a baseband signal (converts to a time continuous signal) on downlink data to generate a physical signal and transmits it to the terminal device 1.
  • the wireless transmitter/receiver 30 (or the wireless transmitter 30a) may place a physical signal on a certain component carrier and transmit it to the terminal device 1.
  • the wireless transmitter/receiver 30 (or the wireless receiver 30b) performs processes such as demodulation and decoding.
  • the wireless transmitting/receiving section 30 (or the wireless receiving section 30b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing section 34.
  • the wireless transmitter/receiver 30 (or the wireless receiver 30b) may perform a channel access procedure prior to transmitting the physical signal.
  • the RF unit 32 converts the signal received via the antenna unit 31 into a baseband signal by orthogonal demodulation (down convert), and removes unnecessary frequency components.
  • the RF section 32 outputs the processed analog signal to the baseband section.
  • the baseband section 33 converts the analog signal input from the RF section 32 into a digital signal.
  • the baseband unit 33 removes a portion corresponding to a CP (Cyclic Prefix) from the converted digital signal, performs Fast Fourier Transform (FFT) on the signal from which the CP has been removed, and transforms the frequency domain signal. Extract.
  • CP Cyclic Prefix
  • FFT Fast Fourier Transform
  • the baseband unit 33 performs an inverse fast Fourier transform (IFFT) on the data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a baseband digital signal, and generates a baseband digital signal. Convert band digital signals to analog signals.
  • the baseband section 33 outputs the converted analog signal to the RF section 32.
  • IFFT inverse fast Fourier transform
  • the RF section 32 removes extra frequency components from the analog signal input from the baseband section 33 using a low-pass filter, upconverts the analog signal to a carrier frequency, and transmits it via the antenna section 31. . Furthermore, the RF section 32 may have a function of controlling transmission power.
  • the RF section 32 is also referred to as a transmission power control section.
  • One or more serving cells may be configured for the terminal device 1.
  • Each of the serving cells configured for the terminal device 1 is one of PCell (Primary cell), PSCell (Primary SCG cell), and SCell (Secondary Cell). Good too.
  • PCell is a serving cell included in MCG (Master Cell Group).
  • the PCell is a cell (an executed cell) in which the terminal device 1 performs an initial connection establishment procedure or a connection re-establishment procedure.
  • a PSCell is a serving cell included in an SCG (Secondary Cell Group). PSCell is a serving cell to which random access is performed by the terminal device 1.
  • SCell may be included in either MCG or SCG.
  • the serving cell group is a name that includes at least MCG and SCG.
  • a serving cell group may include one or more serving cells (or component carriers).
  • One or more serving cells (or component carriers) included in a serving cell group may be operated by carrier aggregation.
  • One or more downlink BWPs may be configured for each serving cell (or downlink component carrier).
  • One or more uplink BWPs may be configured for each serving cell (or uplink component carrier).
  • one downlink BWP may be configured as an active downlink BWP (or one downlink BWP may be configured as an active downlink BWP). may be activated).
  • one uplink BWP may be configured as an active uplink BWP (or one uplink BWP may be configured as an active uplink BWP). may be activated).
  • the PDSCH, PDCCH, and CSI-RS may be received in the active downlink BWP.
  • the terminal device 1 may attempt to receive the PDSCH, PDCCH, and CSI-RS in the active downlink BWP.
  • PUCCH and PUSCH may be transmitted in active uplink BWP.
  • the terminal device 1 may transmit PUCCH and PUSCH in the active uplink BWP.
  • the active downlink BWP and the active uplink BWP are also collectively referred to as active BWP.
  • PDSCH, PDCCH, and CSI-RS may not be received in downlink BWPs other than active downlink BWPs (inactive downlink BWPs).
  • the terminal device 1 does not have to attempt to receive the PDSCH, PDCCH, and CSI-RS in a downlink BWP that is not an active downlink BWP.
  • PUCCH and PUSCH may not be transmitted in an uplink BWP that is not an active uplink BWP (inactive uplink BWP).
  • the terminal device 1 does not have to transmit PUCCH and PUSCH in an uplink BWP that is not an active uplink BWP.
  • the inactive downlink BWP and the inactive uplink BWP are collectively referred to as inactive BWP.
  • Downlink BWP switching is a procedure for deactivating one active downlink BWP of a certain serving cell and activating any of the inactive downlink BWPs of the certain serving cell.
  • Downlink BWP switching may be controlled by a BWP field included in downlink control information. Downlink BWP switching may be controlled based on upper layer parameters.
  • Uplink BWP switching is used to deactivate one active uplink BWP and activate any of the inactive uplink BWPs that are not the one active uplink BWP.
  • Uplink BWP switching may be controlled by a BWP field included in downlink control information. Uplink BWP switching may be controlled based on upper layer parameters.
  • two or more downlink BWPs may not be configured as active downlink BWPs.
  • One downlink BWP may be active for a serving cell at a certain time.
  • two or more uplink BWPs may not be configured as active uplink BWPs.
  • One uplink BWP may be active for a serving cell at a certain time.
  • FIG. 6 is a schematic block diagram showing a configuration example of the terminal device 1 according to one aspect of the present embodiment.
  • the terminal device 1 includes at least one or all of a wireless transmitting/receiving section (physical layer processing section) 10 and an upper layer processing section 14.
  • the radio transmitter/receiver 10 includes at least part or all of an antenna section 11, an RF section 12, and a baseband section 13.
  • the upper layer processing section 14 includes at least part or all of the medium access control layer processing section 15 and the radio resource control layer processing section 16.
  • the wireless transmitter/receiver 10 includes at least part or all of a wireless transmitter 10a and a wireless receiver 10b.
  • the device configurations of the baseband section 13 included in the wireless transmitting section 10a and the baseband section 13 included in the wireless receiving section 10b may be the same or different.
  • the device configurations of the RF section 12 included in the wireless transmitter 10a and the RF section 12 included in the wireless receiver 10b may be the same or different.
  • the device configurations of the antenna section 11 included in the wireless transmitting section 10a and the antenna section 11 included in the wireless receiving section 10b may be the same or different.
  • the wireless transmitter 10a may generate and transmit a PRACH baseband signal.
  • the wireless transmitter 10a may generate and transmit a PUCCH baseband signal.
  • the wireless transmitter 10a may generate and transmit a PUSCH baseband signal.
  • the wireless transmitter 10a may generate and transmit a PUCCH DMRS baseband signal.
  • the wireless transmitter 10a may generate and transmit a PUSCH DMRS baseband signal.
  • the wireless transmitter 10a may generate and transmit a UL PTRS baseband signal.
  • the wireless transmitter 10a may generate and transmit an SRS baseband signal. Generating the SRS baseband signal may be generating an SRS sequence.
  • the radio receiving unit 10b may receive the PDSCH and demodulate it.
  • the radio receiving unit 10b may receive the PDCCH and demodulate it.
  • the radio receiving unit 10b may receive and demodulate the PBCH.
  • the wireless receiving section 10b may receive a synchronization signal.
  • the radio receiving unit 10b may receive PDSCH DMRS.
  • the radio receiving unit 10b may receive PDCCH DMRS.
  • the wireless receiving unit 10b may receive CSI-RS.
  • the wireless receiving unit 10b may receive DL PTRS.
  • the upper layer processing unit 14 outputs uplink data (transport block) to the wireless transmitting/receiving unit 10 (or wireless transmitting unit 10a).
  • the upper layer processing unit 14 processes the MAC layer, packet data integration protocol layer, radio link control layer, and RRC layer.
  • the medium access control layer processing unit 15 included in the upper layer processing unit 14 performs MAC layer processing.
  • the radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs RRC layer processing.
  • the radio resource control layer processing unit 16 manages various setting information/parameters (RRC parameters) of the terminal device 1.
  • RRC parameters setting information/parameters
  • the radio resource control layer processing unit 16 sets RRC parameters based on the RRC message received from the base station device 3.
  • the wireless transmitter/receiver 10 performs processing such as modulation and encoding.
  • the wireless transmitter/receiver 10 (or the wireless transmitter 10a) generates a physical signal by modulating, encoding, and generating a baseband signal (converting to a time continuous signal) uplink data, and transmits the physical signal to the base station device 3. do.
  • the wireless transmitter/receiver 10 (or the wireless transmitter 10a) may place a physical signal in a certain BWP (active uplink BWP) and transmit it to the base station device 3.
  • BWP active uplink BWP
  • the wireless transmitter/receiver 10 (or the wireless receiver 10b) performs processes such as demodulation and decoding.
  • the radio transmitter/receiver 10 (or the radio receiver 30b) may receive a physical signal in a certain BWP (active downlink BWP) of a certain serving cell.
  • the wireless transmitting/receiving unit 10 (or the wireless receiving unit 10b) separates, demodulates, and decodes the received physical signal, and outputs the decoded information to the upper layer processing unit 14.
  • the wireless transmitter/receiver 10 (wireless receiver 10b) may perform a channel access procedure prior to transmitting the physical signal.
  • the RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by orthogonal demodulation (down convert), and removes unnecessary frequency components.
  • the RF section 12 outputs the processed analog signal to the baseband section 13.
  • the baseband section 13 converts the analog signal input from the RF section 12 into a digital signal.
  • the baseband unit 13 removes a portion corresponding to CP (Cyclic Prefix) from the converted digital signal, performs Fast Fourier Transform (FFT) on the signal from which CP has been removed, and converts the signal in the frequency domain. Extract.
  • CP Cyclic Prefix
  • FFT Fast Fourier Transform
  • the baseband unit 13 performs an inverse fast Fourier transform (IFFT) on uplink data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, and generates a baseband digital signal. , converts baseband digital signals to analog signals.
  • the baseband section 13 outputs the converted analog signal to the RF section 12.
  • IFFT inverse fast Fourier transform
  • the RF section 12 removes extra frequency components from the analog signal input from the baseband section 13 using a low-pass filter, upconverts the analog signal to a carrier frequency, and transmits it via the antenna section 11. . Further, the RF section 12 may have a function of controlling transmission power.
  • the RF section 12 is also referred to as a transmission power control section.
  • Physical signal is a general term for downlink physical channel, downlink physical signal, uplink physical channel, and uplink physical channel.
  • a physical channel is a general term for a downlink physical channel and an uplink physical channel.
  • a physical signal is a general term for a downlink physical signal and an uplink physical signal.
  • An uplink physical channel may correspond to a set of resource elements that convey information that occurs in a higher layer.
  • the uplink physical channel may be a physical channel used in an uplink component carrier.
  • the uplink physical channel may be transmitted by the terminal device 1.
  • the uplink physical channel may be received by the base station device 3.
  • at least some or all of the following uplink physical channels may be used.
  • ⁇ PUCCH Physical Uplink Control CHannel
  • PUSCH Physical Uplink Shared CHannel
  • PRACH Physical Random Access CHannel
  • PUCCH may be used to transmit uplink control information (UCI).
  • UCI uplink control information
  • PUCCH may be transmitted to deliver, transmit, convey uplink control information.
  • Uplink control information may be mapped to PUCCH.
  • the terminal device 1 may transmit a PUCCH in which uplink control information is arranged.
  • the base station device 3 may receive the PUCCH in which uplink control information is arranged.
  • Uplink control information (uplink control information bits, uplink control information sequences, uplink control information types) includes channel state information (CSI), scheduling request (SR), HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement) containing at least some or all of the information.
  • CSI channel state information
  • SR scheduling request
  • HARQ-ACK Hybrid Automatic Repeat request ACKnowledgement
  • Channel state information is also called channel state information bits or channel state information series.
  • a scheduling request is also called a scheduling request bit or a scheduling request series.
  • HARQ-ACK information is also called HARQ-ACK information bit or HARQ-ACK information sequence.
  • the HARQ-ACK information may include at least a HARQ-ACK corresponding to a transport block (TB).
  • HARQ-ACK may indicate ACK (acknowledgement) or NACK (negative-acknowledgement) corresponding to the transport block.
  • the ACK may indicate that the transport block has been decoded successfully.
  • a NACK may indicate that the transport block has not been decoded successfully.
  • HARQ-ACK information may include a HARQ-ACK codebook that includes one or more HARQ-ACK bits.
  • a transport block is a sequence of information bits delivered from an upper layer.
  • the information bit series is also called a bit series.
  • the transport block may be delivered from UL-SCH (UpLink - Shared CHannel) of the transport layer.
  • HARQ-ACK for transport blocks is sometimes referred to as HARQ-ACK for PDSCH.
  • HARQ-ACK for PDSCH indicates HARQ-ACK for the transport block included in the PDSCH.
  • HARQ-ACK may indicate ACK or NACK corresponding to one CBG (Code Block Group) included in the transport block.
  • CBG Code Block Group
  • the scheduling request may be used at least to request UL-SCH resources for new transmission.
  • the scheduling request bit may be used to indicate either positive SR or negative SR.
  • the fact that the scheduling request bit indicates a positive SR is also referred to as "a positive SR is transmitted.”
  • a positive SR may indicate that the terminal device 1 requests UL-SCH resources for initial transmission.
  • a positive SR may indicate that a scheduling request is triggered by an upper layer.
  • a positive SR may be communicated when a scheduling request is indicated by an upper layer.
  • 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 the terminal device 1 does not request UL-SCH resources for initial transmission.
  • a negative SR may indicate that no scheduling request is triggered by the upper layer.
  • a negative SR may be communicated if no scheduling request is directed by an upper layer.
  • the channel state information may include at least some or all of a channel quality indicator (CQI), a precoder matrix indicator (PMI), and a rank indicator (RI).
  • CQI is an index related to the quality of a propagation path (eg, propagation intensity) or physical channel quality
  • PMI is an index related to a precoder
  • RI is an index related to transmission rank (or number of transmission layers).
  • Channel state information is an indicator regarding the reception state of at least a physical signal (for example, CSI-RS) used for channel measurement.
  • the value of the channel state information may be determined by the terminal device 1 based on the reception state assumed by at least the physical signal used for channel measurement.
  • Channel measurements may include interference measurements.
  • PUCCH may correspond to PUCCH format.
  • PUCCH may be a set of resource elements used to convey the PUCCH format.
  • PUCCH may include a PUCCH format.
  • PUCCH may be transmitted with a certain PUCCH format. Note that the PUCCH format may be interpreted as an information format. Further, the PUCCH format may be interpreted as a set of information set in a certain information format.
  • PUSCH may be used to convey one or both of a transport block and uplink control information.
  • the transport block may be placed on PUSCH.
  • Transport blocks delivered by UL-SCH may be placed on PUSCH.
  • Uplink control information may be placed on PUSCH.
  • the terminal device 1 may transmit a PUSCH in which one or both of a transport block and uplink control information are arranged.
  • the base station device 3 may receive a PUSCH in which one or both of a transport block and uplink control information are arranged.
  • PRACH may be sent to convey a random access preamble.
  • the terminal device 1 may transmit PRACH.
  • the base station device 3 may receive PRACH.
  • x u is a ZC (Zadoff Chu) series.
  • j is an imaginary unit.
  • ⁇ is pi.
  • C v corresponds to a cyclic shift of the PRACH series.
  • LRA corresponds to the length of the PRACH sequence.
  • L RA is 839 or 139.
  • i is an integer in the range from 0 to L RA ⁇ 1.
  • u is a sequence index for the PRACH sequence.
  • the random access preamble is identified based on the cyclic shift C v of the PRACH sequence and the sequence index u for the PRACH sequence. An index may be attached to each of the 64 identified random access preambles.
  • the uplink physical signal may correspond to a set of resource elements. Uplink physical signals may not be used to convey information that occurs in upper layers. Note that the uplink physical signal may be used to transmit information generated in the physical layer.
  • the uplink physical signal may be a physical signal used in an uplink component carrier.
  • the terminal device 1 may transmit an uplink physical signal.
  • the base station device 3 may receive an uplink physical signal. In the wireless communication system according to one aspect of the present embodiment, at least some or all of the following uplink physical signals may be used. ⁇ UL DMRS (UpLink Demodulation Reference Signal) ⁇ SRS (Sounding Reference Signal) ⁇ UL PTRS (UpLink Phase Tracking Reference Signal)
  • UL DMRS is a generic term for DMRS for PUSCH and DMRS for PUCCH.
  • a set of antenna ports for DMRS for PUSCH may be provided based on the set of antenna ports for the PUSCH.
  • the set of DMRS antenna ports for a PUSCH may be the same as the set of antenna ports for the PUSCH.
  • Transmission of PUSCH and transmission of DMRS for the PUSCH may be indicated (or scheduled) by one DCI format.
  • PUSCH and DMRS for PUSCH may be collectively referred to as PUSCH.
  • Transmitting PUSCH may be transmitting PUSCH and DMRS for the PUSCH.
  • the propagation path of the PUSCH may be estimated from the DMRS for the PUSCH.
  • the set of antenna ports of DMRS for PUCCH may be the same as the set of antenna ports of PUCCH.
  • the transmission of PUCCH and the transmission of DMRS for the PUCCH may be indicated (or triggered) by one DCI format.
  • One or both of the PUCCH to resource element mapping and the DMRS to resource element mapping for the PUCCH may be provided by one PUCCH format.
  • PUCCH and DMRS for PUCCH may be collectively referred to as PUCCH. Transmitting the PUCCH may be transmitting the PUCCH and DMRS for the PUCCH.
  • the propagation path of the PUCCH may be estimated from the DMRS for the PUCCH.
  • a downlink physical channel may correspond to a set of resource elements conveying information originating in upper layers.
  • the downlink physical channel may be a physical channel used in a downlink component carrier.
  • the base station device 3 may transmit a downlink physical channel.
  • the terminal device 1 may receive the downlink physical channel.
  • at least some or all of the following downlink physical channels may be used.
  • PBCH Physical Broadcast Channel
  • PDCCH Physical Downlink Control Channel
  • PDSCH Physical Downlink Shared Channel
  • the PBCH may be transmitted to convey one or both of an MIB (Master Information Block) and physical layer control information.
  • the physical layer control information is information generated in the physical layer.
  • MIB is a set of parameters arranged in BCCH (Broadcast Control CHannel), which is a logical channel of the MAC layer.
  • BCCH Broadcast Control CHannel
  • the BCCH is placed in a BCH which is a transport layer channel.
  • BCH may be mapped to PBCH.
  • the terminal device 1 may receive a PBCH in which one or both of the MIB and the physical layer control information are arranged.
  • the base station device 3 may transmit a PBCH in which one or both of the MIB and physical layer control information are arranged.
  • the physical layer control information may consist of 8 bits.
  • the physical layer control information may include at least some or all of 0A to 0D below.
  • the radio frame bit 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).
  • Radio frame bits include 4 bits.
  • the radio frame bits may consist of 4 bits of a 10-bit radio frame indicator.
  • a radio frame indicator may be used to at least identify radio frames from index 0 to index 1023.
  • the half radio frame bit is used to indicate whether the PBCH is transmitted in the first five subframes or the latter five subframes of the radio frame in which the PBCH is transmitted.
  • the half radio frame may include five subframes.
  • a half radio frame may be configured by the first five subframes out of ten subframes included in the radio frame.
  • the half radio frame may be configured by the latter five subframes among the ten subframes included in the radio frame.
  • the SS/PBCH block index bit is used to indicate the SS/PBCH block index.
  • the SS/PBCH block index bits include 3 bits.
  • the SS/PBCH block index bits may be comprised of 3 bits of the 6-bit SS/PBCH block index indicator.
  • the SS/PBCH block index indicator may be used at least to identify SS/PBCH blocks from index 0 to index 63.
  • the subcarrier offset bit is used to indicate the subcarrier offset.
  • the subcarrier offset may be used to indicate the difference between the first subcarrier to which the PBCH is mapped and the first subcarrier to which the control resource set with index 0 is mapped.
  • the PDCCH may be transmitted to convey downlink control information (DCI). Downlink control information may be mapped to the PDCCH.
  • the terminal device 1 may receive a PDCCH in which downlink control information is arranged.
  • the base station device 3 may transmit a PDCCH in which downlink control information is arranged.
  • Downlink control information may be transmitted with DCI format.
  • the DCI format may be interpreted as a format of downlink control information. Further, the DCI format may be interpreted as a set of downlink control information set in a certain format of downlink control information.
  • DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1 are DCI formats.
  • the uplink DCI format is a generic term for DCI format 0_0 and DCI format 0_1.
  • the downlink DCI format is a generic term for DCI format 1_0 and DCI format 1_1.
  • DCI format 0_0 is used at least for scheduling PUSCH located in a certain cell.
  • DCI format 0_0 is configured to include at least some or all of the fields 1A to 1E.
  • the DCI format specific field may indicate whether the DCI format including the DCI format specific field is an uplink DCI format or a downlink DCI format. That is, the DCI format specific field may be included in each of the uplink DCI format and the downlink DCI format.
  • the DCI format specific field included in DCI format 0_0 may indicate 0.
  • the frequency domain resource allocation field included in DCI format 0_0 may be used to indicate frequency resource allocation for PUSCH.
  • the time domain resource allocation field included in DCI format 0_0 may be used to indicate time resource allocation for PUSCH.
  • the frequency hopping flag field may be used to indicate whether frequency hopping is applied to PUSCH.
  • the MCS field included in DCI format 0_0 may be used at least to indicate one or both of the modulation scheme and target coding rate for PUSCH.
  • the target coding rate may be a target coding rate for a transport block placed in PUSCH.
  • the size of the transport block (TBS: Transport Block Size) placed on the PUSCH may be determined based on one or both of the target coding rate and the modulation method for the PUSCH.
  • DCI format 0_0 does not need to include fields used for CSI requests.
  • DCI format 0_0 may not include a carrier indicator field. That is, the serving cell to which the uplink component carrier to which the PUSCH scheduled according to DCI format 0_0 is arranged may belong may be the same as the serving cell of the uplink component carrier to which the PDCCH including the DCI format 0_0 is arranged. Based on detecting DCI format 0_0 on a certain downlink component carrier of a certain serving cell, the terminal device 1 recognizes that the PUSCH scheduled according to the DCI format 0_0 is to be allocated to the uplink component carrier of the certain serving cell. Good too.
  • DCI format 0_0 does not need to include the BWP field.
  • DCI format 0_0 may be a DCI format that schedules PUSCH without changing the active uplink BWP.
  • the terminal device 1 may recognize that the PUSCH is to be transmitted without switching the active uplink BWP based on the detection of the DCI format 0_0 used for PUSCH scheduling.
  • DCI format 0_1 is used at least for scheduling PUSCH placed in a certain cell.
  • DCI format 0_1 is configured to include at least some or all of fields 2A to 2H.
  • the DCI format specific field included in DCI format 0_1 may indicate 0.
  • the frequency domain resource allocation field included in DCI format 0_1 may be used to indicate frequency resource allocation for PUSCH.
  • the time domain resource allocation field included in DCI format 0_1 may be used to indicate time resource allocation for PUSCH.
  • the MCS field included in DCI format 0_1 may be used at least to indicate part or all of the modulation scheme and/or target coding rate for PUSCH.
  • the BWP field of DCI format 0_1 may be used to indicate the uplink BWP where the PUSCH scheduled according to the DCI format 0_1 is arranged. That is, DCI format 0_1 may be accompanied by a change in the active uplink BWP.
  • the terminal device 1 may recognize the uplink BWP where the PUSCH is arranged based on detecting the DCI format 0_1 used for scheduling the PUSCH.
  • the DCI format 0_1 that does not include the BWP field may be a DCI format that schedules PUSCH without changing the active uplink BWP.
  • the terminal device 1 transmits the PUSCH without switching the active uplink BWP based on detecting DCI format D0_1, which is the DCI format 0_1 used for PUSCH scheduling and does not include the BWP field. You may recognize that.
  • the BWP field is included in DCI format 0_1, if the terminal device 1 does not support the BWP switching function using DCI format 0_1, the BWP field may be ignored by the terminal device 1. In other words, the terminal device 1 that does not support the BWP switching function switches the active uplink BWP based on detecting DCI format 0_1 used for PUSCH scheduling and including the BWP field. It may be recognized that the PUSCH is to be transmitted without performing. Here, if the terminal device 1 supports the BWP switching function, it may be reported that "the terminal device 1 supports the BWP switching function" in the RRC layer function information reporting procedure.
  • the CSI request field is used to instruct CSI reporting.
  • the carrier indicator field may be used to indicate the uplink component carrier on which the PUSCH is allocated. If DCI format 0_1 does not include a carrier indicator field, the uplink component carrier on which the PUSCH is allocated is the same as the uplink component carrier on which the PDCCH including DCI format 0_1 used for scheduling of the PUSCH is allocated. Good too.
  • the PUSCH configured in the certain serving cell group may be 1 bit or more (for example, 3 bits).
  • the scheduling of PUSCH allocated to the certain serving cell group may be 0 bits (or the carrier indicator field is included in the DCI format 0_1 used for scheduling the PUSCH allocated to the certain serving cell group). (optional).
  • DCI format 1_0 is used at least for scheduling PDSCH allocated to a certain cell.
  • DCI format 1_0 is configured to include at least some or all of 3A to 3F.
  • the DCI format specific field included in DCI format 1_0 may indicate 1.
  • the frequency domain resource allocation field included in DCI format 1_0 may be used at least to indicate frequency resource allocation for PDSCH.
  • the time domain resource allocation field included in DCI format 1_0 may be used at least to indicate the allocation of time resources for the PDSCH.
  • the MCS field included in DCI format 1_0 may be used at least to indicate one or both of the modulation scheme and target coding rate for the PDSCH.
  • the target coding rate may be a target coding rate for a transport block placed in a PDSCH.
  • the size of a transport block (TBS: Transport Block Size) allocated to a PDSCH may be determined based on one or both of a target coding rate and a modulation scheme for the PDSCH.
  • the PDSCH_HARQ feedback timing indication field may be used to indicate the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH.
  • the PUCCH resource indication field may be a field indicating an index of one or more PUCCH resources included in the PUCCH resource set.
  • a PUCCH resource set may include one or more PUCCH resources.
  • DCI format 1_0 may not include a carrier indicator field. That is, the downlink component carrier on which the PDSCH scheduled according to DCI format 1_0 is arranged may be the same as the downlink component carrier on which the PDCCH including the DCI format 1_0 is arranged. Based on detecting DCI format 1_0 on a certain downlink component carrier, the terminal device 1 may recognize that the PDSCH scheduled according to the DCI format 1_0 is to be allocated to the downlink component carrier.
  • DCI format 1_0 does not need to include the BWP field.
  • DCI format 1_0 may be a DCI format that schedules PDSCH without changing the active downlink BWP.
  • the terminal device 1 may recognize that the PDSCH is to be received without switching the active downlink BWP based on the detection of the DCI format 1_0 used for PDSCH scheduling.
  • DCI format 1_1 is used at least for scheduling PDSCHs arranged in a certain cell.
  • DCI format 1_1 is configured to include at least some or all of 4A to 4I.
  • the DCI format specific field included in DCI format 1_1 may indicate 1.
  • the frequency domain resource allocation field included in DCI format 1_1 may be used at least to indicate frequency resource allocation for PDSCH.
  • the time domain resource allocation field included in DCI format 1_1 may be used at least to indicate the allocation of time resources for the PDSCH.
  • the MCS field included in DCI format 1_1 may be used at least to indicate one or both of the modulation scheme and target coding rate for the PDSCH.
  • the PDSCH_HARQ feedback timing indication field indicates the offset from the slot containing the last OFDM symbol of the PDSCH to the slot containing the first OFDM symbol of the PUCCH. may be used at least. If the DCI format 1_1 does not include the PDSCH_HARQ feedback timing indication field, the offset from the slot containing the last OFDM symbol of PDSCH to the slot containing the first OFDM symbol of PUCCH may be specified by upper layer parameters. good.
  • the PUCCH resource indication field may be a field indicating an index of one or more PUCCH resources included in the PUCCH resource set.
  • the BWP field of DCI format 1_1 may be used to indicate the downlink BWP where the PDSCH scheduled according to DCI format 1_1 is arranged. That is, DCI format 1_1 may be accompanied by a change in the active downlink BWP.
  • the terminal device 1 may recognize the downlink BWP where the PUSCH is arranged based on detecting the DCI format 1_1 used for PDSCH scheduling.
  • the DCI format 1_1 that does not include the BWP field may be a DCI format that schedules PDSCH without changing the active downlink BWP.
  • the terminal device 1 receives the PDSCH without switching the active downlink BWP based on detecting the DCI format 1_1 used for PDSCH scheduling and which does not include the BWP field. You may recognize that.
  • the BWP field is included in the DCI format 1_1, if the terminal device 1 does not support the BWP switching function according to the DCI format 1_1, the BWP field may be ignored by the terminal device 1. In other words, the terminal device 1 that does not support the BWP switching function switches the active downlink BWP based on detecting the DCI format 1_1 used for PDSCH scheduling and including the BWP field. It may also be possible to recognize that the PDSCH is received without performing. Here, if the terminal device 1 supports the BWP switching function, it may be reported that "the terminal device 1 supports the BWP switching function" in the RRC layer function information reporting procedure.
  • the carrier indicator field may be used to indicate the downlink component carrier on which the PDSCH is allocated. If the DCI format 1_1 does not include a carrier indicator field, the downlink component carrier on which the PDSCH is allocated is the same as the downlink component carrier on which the PDCCH including the DCI format 1_1 used for scheduling the PDSCH is allocated. Good too.
  • the number of PDSCHs allocated to the certain serving cell group is 2 or more (when downlink carrier aggregation is operated in a certain serving cell group), the number of PDSCHs allocated to the certain serving cell group is
  • the number of bits of the carrier indicator field included in the DCI format 1_1 used for scheduling may be 1 bit or more (for example, 3 bits).
  • the scheduling of the PDSCH allocated to the certain serving cell group may be 0 bits (or the carrier indicator field may be included in the DCI format 1_1 used for scheduling the PDSCH allocated to the certain serving cell group). (optional).
  • PDSCH may be transmitted to convey transport blocks.
  • PDSCH may be used to transmit transport blocks delivered by DL-SCH.
  • PDSCH may be used to convey transport blocks.
  • a transport block may be placed on a PDSCH.
  • a transport block corresponding to DL-SCH may be placed on PDSCH.
  • the base station device 3 may transmit the PDSCH.
  • the terminal device 1 may receive the PDSCH.
  • a downlink physical signal may correspond to a set of resource elements.
  • the downlink physical signals may not carry information generated in 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 the base station device 3.
  • the downlink physical signal may be transmitted by the terminal device 1.
  • at least some or all of the following downlink physical signals may be used.
  • SS Synchronization signal
  • DL DMRS DownLink DeModulation Reference Signal
  • CSI-RS Channel State Information-Reference Signal
  • DL PTRS DownLink Phase Tracking Reference Signal
  • the synchronization signal may be used by the terminal device 1 to synchronize one or both of the downlink frequency domain and time domain.
  • the synchronization signal is a general term for PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal).
  • FIG. 7 is a diagram illustrating a configuration example of an SS/PBCH block according to one aspect of the present embodiment.
  • the horizontal axis is the time axis (OFDM symbol index l sym ), and the vertical axis shows the frequency domain.
  • Block 700 also shows a set of resource elements for the PSS.
  • Block 720 also shows a set of resource elements for SSS.
  • four blocks (blocks 710, 711, 712, and 713) are for the PBCH and the DMRS for the PBCH (DMRS related to the PBCH, DMRS included in the PBCH, and DMRS corresponding to the PBCH). indicates a set of resource elements.
  • the SS/PBCH block includes PSS, SSS, and PBCH. Further, the SS/PBCH block includes four consecutive OFDM symbols.
  • An SS/PBCH block includes 240 subcarriers. PSS is placed on the 57th to 183rd subcarriers in the first OFDM symbol. SSS is placed on 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.
  • the PBCH is allocated to the 1st to 240th subcarriers of the second OFDM symbol, and on which the DMRS for the PBCH is not allocated.
  • the PBCH is allocated to the 1st to 48th subcarriers of the third OFDM symbol, and on which the DMRS for the PBCH is not allocated.
  • the PBCH is allocated to the 193rd to 240th subcarriers of the third OFDM symbol, and on which the DMRS for the PBCH is not allocated.
  • the PBCH is allocated to the 1st to 240th subcarriers of the 4th OFDM symbol, and on which the DMRS for the PBCH is not allocated.
  • the antenna ports of PSS, SSS, PBCH, and DMRS for PBCH may be the same.
  • a PBCH on which a PBCH symbol at a certain antenna port is transmitted is a DMRS for a PBCH allocated to the slot to which the PBCH is mapped, and a DMRS for the PBCH included in the SS/PBCH block in which the PBCH is included. may be estimated by DMRS.
  • DL DMRS is a collective term for DMRS for PBCH, DMRS for PDSCH, and DMRS for PDCCH.
  • the set of antenna ports for the DMRS for the PDSCH may be provided based on the set of antenna ports for the PDSCH. That is, the set of DMRS antenna ports for a PDSCH may be the same as the set of antenna ports for the PDSCH.
  • the transmission of a PDSCH and the transmission of a DMRS for the PDSCH may be indicated (or scheduled) by one DCI format.
  • a PDSCH and a DMRS for the PDSCH may be collectively referred to as a PDSCH.
  • Transmitting a PDSCH may include transmitting a PDSCH and a DMRS for the PDSCH.
  • the propagation path of the PDSCH may be estimated from the DMRS for the PDSCH. If a set of resource elements on which a certain PDSCH symbol is transmitted and a set of resource elements on which DMRS symbols for the certain PDSCH are transmitted are included in the same precoding resource group (PRG). In this case, the PDSCH on which the symbols of the PDSCH at an antenna port are conveyed may be estimated by the DMRS for the PDSCH.
  • PRG precoding resource group
  • the antenna port of DMRS for PDCCH (DMRS related to PDCCH, DMRS included in PDCCH, DMRS corresponding to PDCCH) may be the same as the antenna port for PDCCH.
  • the PDCCH may be estimated from the DMRS for the PDCCH. That is, the propagation path of the PDCCH may be estimated from the DMRS for the PDCCH. If the same precoder is applied (and is assumed to be (assumed to be applicable), the PDCCH on which the symbols of the PDCCH at an antenna port are conveyed may be estimated by the DMRS for the PDCCH.
  • BCH Broadcast CHannel
  • UL-SCH Uplink-Shared CHannel
  • DL-SCH Downlink-Shared CHannel
  • a transport channel defines the relationship between a physical layer channel and a MAC layer channel (also called a logical channel).
  • the transport layer BCH is mapped to the physical layer PBCH. In other words, transport blocks passing through the transport layer BCH are delivered to the physical layer PBCH. Furthermore, the transport layer UL-SCH is mapped to the physical layer PUSCH. In other words, a transport block passing through the UL-SCH of the transport layer is delivered to the PUSCH of the physical layer. Furthermore, the DL-SCH of the transport layer is mapped to the PDSCH of the physical layer. In other words, transport blocks passing through the DL-SCH in the transport layer are delivered to the PDSCH in the physical layer.
  • One UL-SCH and one DL-SCH may be provided for each serving cell.
  • BCH may be given to PCell.
  • BCH does not have to be given to PSCell and SCell.
  • HARQ Hybrid Automatic Repeat reQuest
  • BCCH Broadcast Control CHannel
  • CCCH Common Control CHannel
  • DCCH Dedicated Control CHannel
  • BCCH is an RRC layer channel used to transmit MIB or system information.
  • CCCH Common Control CHannel
  • CCCH Common Control CHannel
  • DCCH Dedicated Control CHannel
  • BCCH is an RRC layer channel used to transmit MIB or system information.
  • CCCH Common Control CHannel
  • DCCH Dedicated Control CHannel
  • DCCH Dedicated Control CHannel
  • the DCCH may be used at least to transmit a dedicated RRC message to the terminal device 1.
  • the DCCH may be used, for example, for the RRC-connected terminal device 1.
  • Upper layer parameters common to multiple terminal devices 1 are also referred to as common upper layer parameters.
  • the common upper layer parameter may be defined as a parameter specific to a serving cell.
  • the parameters unique to the serving cell may be common parameters to the terminal devices (for example, terminal devices 1-A, B, and C) in which the serving cell is configured.
  • common upper layer parameters may be included in the RRC message delivered to the BCCH.
  • common upper layer parameters may be included in RRC messages delivered on the DCCH.
  • upper layer parameters that are different from common upper layer parameters are also called dedicated upper layer parameters.
  • the dedicated upper layer parameters can provide dedicated RRC parameters to the terminal device 1-A in which the serving cell is configured.
  • the dedicated RRC parameters are upper layer parameters that can provide unique settings to each of the terminal devices 1-A, B, and C.
  • the logical channel BCCH is mapped to the transport layer BCH or DL-SCH.
  • a transport block containing MIB information is delivered to the BCH of the transport layer.
  • transport blocks containing system information other than MIB are delivered to the DL-SCH of the transport layer.
  • CCCH is mapped to DL-SCH or UL-SCH. That is, a transport block mapped to CCCH is delivered to DL-SCH or UL-SCH.
  • DCCH is mapped to DL-SCH or UL-SCH. That is, a transport block mapped to DCCH is delivered to DL-SCH or UL-SCH.
  • the RRC message includes one or more parameters managed at the RRC layer.
  • the parameters managed in the RRC layer are also called RRC parameters.
  • an RRC message may include a MIB.
  • the RRC message may also include system information.
  • the RRC message may include a message corresponding to CCCH.
  • the RRC message may include a message corresponding to DCCH.
  • RRC messages including messages corresponding to DCCH are also called individual RRC messages.
  • Upper layer parameters are RRC parameters or parameters included in MAC CE (Medium Access Control Element).
  • the upper layer parameter is a general term for the MIB, system information, messages corresponding to CCCH, messages corresponding to DCCH, and parameters included in MAC CE.
  • the parameters included in the MAC CE are sent by the MAC CE (Control Element) command.
  • the procedure performed by the terminal device 1 includes at least some or all of the following 5A to 5C.
  • Cell search is a procedure used by the terminal device 1 to synchronize with a certain cell in the time domain and frequency domain and to detect a physical cell ID (physical cell identity). That is, the terminal device 1 may perform time domain and frequency domain synchronization with a certain cell by cell search and detect the physical cell ID.
  • the PSS sequence is given based on at least the physical cell ID.
  • the SSS sequence is given based on at least the physical cell ID.
  • An SS/PBCH block candidate indicates a resource on which transmission of an SS/PBCH block is permitted (possible, reserved, configured, defined, possible).
  • a set of SS/PBCH block candidates in a certain half radio frame is also called an SS burst set.
  • the SS burst set is also referred to as a transmission window, an SS transmission window, or a DRS transmission window.
  • the SS burst set is a general term that includes at least the first SS burst set and the second SS burst set.
  • the base station device 3 transmits SS/PBCH blocks of one or more indexes at a predetermined period.
  • the terminal device 1 may detect at least one of the SS/PBCH blocks of the one or more indexes and attempt to decode the PBCH included in the SS/PBCH block.
  • Random access is a procedure that includes at least some or all of Message 1, Message 2, Message 3, and Message 4.
  • Message 1 is a procedure in which PRACH is transmitted by terminal device 1.
  • the terminal device 1 transmits a PRACH in one PRACH opportunity selected from one or more PRACH opportunities based at least on the index of the SS/PBCH block candidate detected based on the cell search.
  • Each PRACH opportunity is defined based on at least time domain and frequency domain resources.
  • the terminal device 1 transmits one random access preamble selected from the PRACH opportunities corresponding to the index of the SS/PBCH block candidate in which the SS/PBCH block is detected.
  • Message 2 is a procedure in which the terminal device 1 attempts to detect DCI format 1_0 with a CRC (Cyclic Redundancy Check) scrambled with RA-RNTI (Random Access - Radio Network Temporary Identifier).
  • the terminal device 1 includes the DCI format in the control resource set given based on the MIB included in the PBCH included in the SS/PBCH block detected based on the cell search, and in the resource indicated based on the setting of the search area set. Attempt to detect PDCCH.
  • Message 2 is also called a random access response.
  • Message 3 is a procedure for transmitting a PUSCH scheduled by a random access response grant included in DCI format 1_0 detected by message 2 procedure.
  • the random access response grant is indicated by the MAC CE included in the PDSCH scheduled by the DCI format 1_0.
  • the PUSCH scheduled based on the random access response grant is either message 3 PUSCH or PUSCH.
  • Message 3 PUSCH includes contention resolution identifier MAC CE.
  • Conflict resolution ID MAC CE contains the conflict resolution ID.
  • Message 3 Retransmission of PUSCH is scheduled by DCI format 0_0 with scrambled CRC based on TC-RNTI (Temporary Cell - Radio Network Temporary Identifier).
  • TC-RNTI Temporary Cell - Radio Network Temporary Identifier
  • Message 4 is a procedure that attempts to detect DCI format 1_0 with scrambled CRC based on either C-RNTI (Cell-Radio Network Temporary Identifier) or TC-RNTI.
  • the terminal device 1 receives the PDSCH scheduled based on the DCI format 1_0.
  • the PDSCH may include a conflict resolution ID.
  • Data communication is a general term for downlink communication and uplink communication.
  • the terminal device 1 attempts to detect a PDCCH (monitors a PDCCH) in a resource specified based on a control resource set and a search area set.
  • a PDCCH monitoring a PDCCH
  • a control resource set is a resource set made up of a predetermined number of resource blocks and a predetermined number of OFDM symbols.
  • the control resource set may be composed of continuous resources (non-interleaved mapping) or distributed resources (interleaver mapping).
  • the set of resource blocks that constitute the control resource set may be indicated by upper layer parameters.
  • the number of OFDM symbols constituting the control resource set may be indicated by an upper layer parameter.
  • the terminal device 1 attempts to detect PDCCH in the search area set.
  • attempting to detect a PDCCH in the search area set may be attempting to detect a PDCCH candidate in the search area set, or may be attempting to detect a DCI format in the search area set.
  • the method may be to try to detect a PDCCH in the control resource set, to try to detect a PDCCH candidate in the control resource set, or to try to detect a DCI format in the control resource set. There may be.
  • the search area set is defined as a set of PDCCH candidates.
  • the search area set may be a CSS (Common Search Space) set or a USS (UE-specific Search Space) set.
  • the terminal device 1 has a type 0 PDCCH common search space set (Type0 PDCCH common search space set), a type 0a PDCCH common search space set (Type0a PDCCH common search space set), a type 1 PDCCH common search space set (Type1 PDCCH common search space set), One of the Type 2 PDCCH common search space set, Type 3 PDCCH common search space set, and/or UE-specific PDCCH search space set. Attempts are made to detect PDCCH candidates in some or all parts.
  • the type 0 PDCCH common search area set may be used as the index 0 common search area set.
  • the type 0 PDCCH common search area set may be an index 0 common search area set.
  • CSS set is a general term for type 0 PDCCH common search area set, type 0a PDCCH common search area set, type 1 PDCCH common search area set, type 2 PDCCH common search area set, and type 3 PDCCH common search area set.
  • the USS set is also referred to as a UE individual PDCCH search area set.
  • a certain search area set is related to (includes in, corresponds to) a certain control resource set.
  • the index of the control resource set associated with the search area set may be indicated by the upper layer parameter.
  • 6A to 6C may be indicated by at least upper layer parameters.
  • a monitoring occasion for a certain search area set may correspond to an OFDM symbol in which a first OFDM symbol of a control resource set related to the certain search area set is placed.
  • a monitoring opportunity for a search area set may correspond to resources of the control resource set associated with the search area set starting from the first OFDM symbol of the control resource set. The opportunity to monitor the search area set is given based on at least some or all of the PDCCH monitoring interval, the PDCCH monitoring pattern within the slot, and the PDCCH monitoring offset.
  • FIG. 8 is a diagram illustrating an example of a search area set monitoring opportunity according to an aspect of the present embodiment.
  • a search area set 91 and a search area set 92 are set in the primary cell 301
  • a search area set 93 is set in the secondary cell 302
  • a search area set 94 is set in the secondary cell 303.
  • the monochrome blocks in the primary cell 301 indicate the search area set 91
  • the monochrome blocks in the primary cell 301 indicate the search area set 92
  • the blocks in the secondary cell 302 indicate the search area set 93
  • the blocks in the secondary cell 301 indicate the search area set 93.
  • the blocks in cell 303 indicate search area set 94.
  • the monitoring interval of the search area set 91 is set to 1 slot
  • the monitoring offset of the search area set 91 is set to 0 slot
  • the monitoring pattern of the search area set 91 is [1, 0, 0, 0, 0, 0, 0,1,0,0,0,0,0,0]. That is, the monitoring opportunities of the search area set 91 correspond to the first OFDM symbol (OFDM symbol #0) and the eighth OFDM symbol (OFDM symbol #7) in each slot.
  • the monitoring interval of the search area set 92 is set to 2 slots, the monitoring offset of the search area set 92 is set to 0 slots, and the monitoring pattern of the search area set 92 is [1, 0, 0, 0, 0, 0, 0,0,0,0,0,0,0,0].
  • the monitoring opportunity of the search area set 92 corresponds to the first OFDM symbol (OFDM symbol #0) in each even slot.
  • the monitoring interval of the search area set 93 is set to 2 slots
  • the monitoring offset of the search area set 93 is set to 0 slots
  • the monitoring pattern of the search area set 93 is [0,0,0,0,0,0, 0,1,0,0,0,0,0,0]. That is, the monitoring opportunity of the search area set 93 corresponds to the 8th OFDM symbol (OFDM symbol #7) in each of the even slots.
  • the monitoring interval of the search area set 94 is set to 2 slots, the monitoring offset of the search area set 94 is set to 1 slot, and the monitoring pattern of the search area set 94 is [1, 0, 0, 0, 0, 0, 0,0,0,0,0,0,0,0]. That is, the monitoring opportunity of the search area set 94 corresponds to the first OFDM symbol (OFDM symbol #0) in each odd slot.
  • the type 0 PDCCH common search area set may be used at least for the DCI format with a CRC (Cyclic Redundancy Check) sequence scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier).
  • CRC Cyclic Redundancy Check
  • the type 0a PDCCH common search area set may be used at least for the DCI format with a CRC (Cyclic Redundancy Check) sequence scrambled by SI-RNTI (System Information-Radio Network Temporary Identifier).
  • CRC Cyclic Redundancy Check
  • the type 1 PDCCH common search area set includes a CRC sequence scrambled by RA-RNTI (Random Access-Radio Network Temporary Identifier) and/or a CRC sequence scrambled by TC-RNTI (Temporary Cell-Radio Network Temporary Identifier). It may be used at least for the accompanying DCI format.
  • RA-RNTI Random Access-Radio Network Temporary Identifier
  • TC-RNTI Temporary Cell-Radio Network Temporary Identifier
  • Type 2 PDCCH common search area set may be used for DCI format with CRC sequence scrambled by P-RNTI (Paging- Radio Network Temporary Identifier).
  • P-RNTI Paging- Radio Network Temporary Identifier
  • Type 3 PDCCH common search area set may be used for DCI format with CRC sequence scrambled by C-RNTI (Cell-Radio Network Temporary Identifier).
  • C-RNTI Cell-Radio Network Temporary Identifier
  • the UE specific PDCCH search region set may be used at least for the DCI format with a CRC sequence scrambled by C-RNTI.
  • the terminal device 1 detects the downlink DCI format.
  • the detected downlink DCI format is used at least for PDSCH resource allocation.
  • the detected downlink DCI format is also referred to as downlink assignment.
  • the terminal device 1 attempts to receive the PDSCH. Based on the PUCCH resource indicated based on the detected downlink DCI format, the HARQ-ACK corresponding to the PDSCH (HARQ-ACK corresponding to the transport block included in the PDSCH) is reported to the base station device 3.
  • the terminal device 1 In uplink communication, the terminal device 1 detects the uplink DCI format.
  • the detected DCI format is used at least for PUSCH resource allocation.
  • the detected uplink DCI format is also called an uplink grant.
  • the terminal device 1 transmits the PUSCH.
  • an uplink grant for scheduling a PUSCH is configured for each transmission cycle of the PUSCH.
  • a PUSCH is scheduled using an uplink DCI format
  • part or all of the information indicated by the uplink DCI format may be indicated by an uplink grant that is set when the scheduling is set.
  • the UL slot may be a slot composed of UL symbols.
  • the special slot may be a slot composed of UL symbols, flexible symbols, and DL symbols.
  • the DL slot may be a slot composed of DL symbols.
  • the UL symbol may be an OFDM symbol configured or instructed for uplink in time division duplexing.
  • the UL symbol may be an OFDM symbol configured or directed for PUSCH, PUCCH, PRACH, or SRS.
  • the UL symbol may be provided by the upper layer parameter tdd-UL-DL-ConfigurationCommon.
  • the UL symbol may be provided by the upper layer parameter tdd-UL-DL-ConfigurationDedicated.
  • the UL slot may be provided by the upper layer parameter tdd-UL-DL-ConfigurationCommon.
  • the UL slot may be provided by the upper layer parameter tdd-UL-DL-ConfigurationDedicated.
  • the DL symbol may be an OFDM symbol set or instructed for downlink in time division duplexing.
  • the DL symbol may be an OFDM symbol configured or directed for PDSCH or PDCCH.
  • the DL symbol may be provided by the upper layer parameter tdd-UL-DL-ConfigurationCommon.
  • the DL symbol may be provided by the upper layer parameter tdd-UL-DL-ConfigurationDedicated.
  • the DL slot may be provided by the upper layer parameter tdd-UL-DL-ConfigurationCommon.
  • the DL slot may be provided by the upper layer parameter tdd-UL-DL-ConfigurationDedicated.
  • the flexible symbol may be an OFDM symbol that is not set or designated as a UL symbol or DL symbol among OFDM symbols within a certain period.
  • the certain period may be a period given by the upper layer parameter dl-UL-TransmissionPeriodicity.
  • the flexible symbol may be an OFDM symbol configured or directed for PDSCH, PDCCH, PUSCH, PUCCH, or PRACH.
  • the upper layer parameter tdd-UL-DL-ConfigurationCommon may be a parameter that sets either a UL slot, DL slot, or special slot for each of one or more slots.
  • the upper layer parameter tdd-UL-DL-ConfigurationDedicated may be a parameter that sets either the UL symbol, DL symbol, or flexible symbol for the flexible symbol in each of the one or more slots.
  • tdd-UL-DL-ConfigurationCommon may be a common upper layer parameter.
  • tdd-UL-DL-ConfigurationDedicated may be a dedicated upper layer parameter.
  • PUSCH-Config may be a dedicated upper layer parameter.
  • PUSCH-ConfigCommon may be a common upper layer parameter.
  • PUSCH-Config may be configured for each BWP for PUSCH transmission.
  • PUSCH-Config may include multiple upper layer parameters related to PUSCH transmission.
  • PUSCH-Config may be a UE-specific setting. For example, the PUSCH-Config for the terminal device 1A, the terminal device 1B, and the terminal device 1C in one cell, or a plurality of upper layer parameters included in the PUSCH-Config may be different.
  • PUSCH-ConfigCommon may be configured for each BWP for PUSCH transmission.
  • PUSCH-ConfigCommon may include multiple upper layer parameters related to PUSCH transmission.
  • PUSCH-ConfigCommon may be a cell-specific setting.
  • the PUSCH-ConfigCommon for the terminal device 1A, terminal device 1B, and terminal device 1C in one cell may be common.
  • PUSCH-ConfigCommon may be provided by system information.
  • Repeated transmission may be applied to PUSCH.
  • repeated transmission may be applied to PUSCH scheduled by DCI.
  • repeated transmission may be applied to the PUSCH scheduled according to the configured uplink grant.
  • the PUSCH repetition type may be either PUSCH repetition type A or PUSCH repetition type B.
  • the PUSCH repetition type may be set by upper layer parameters.
  • the PUSCH repetition type may be based on the DCI format. For example, a first PUSCH repetition type for a PUSCH scheduled by DCI format 0_1 may be different from a second PUSCH repetition type for a PUSCH scheduled by DCI format 0_2.
  • the number of repetitions for PUSCH repetition transmission may be set by upper layer parameters.
  • the upper layer parameter numberOfRepetitionins may be a parameter including the number of repetitions for PUSCH repeat transmission.
  • the number of repetitions for the PUSCH repetition transmission may be determined by the value of the upper layer parameter numberOfRepetitions.
  • PUSCH repetition type A PUSCH whose transmission is directed by DCI format with CRC scrambled by C-RNTI and either MCS-C-RNTI or CS-RNTI, if there are numberOfRepetitions in the resource allocation table , the number of repetitions may be equal to numberOfRepetitions.
  • PUSCH-TimeDomainResourceAllocation includes one or more PUSCH-Allocations
  • the upper layer parameter numberOfRepetitions may be set for each PUSCH-Allocation.
  • PUSCH-TimeDomainResourceAllocation may be called a resource allocation table.
  • the upper layer parameter push-AggregationFactor may be a parameter indicating the number of repetitions for PUSCH repeat transmission.
  • the number of repetitions for the PUSCH repetition transmission may be determined by the value of the upper layer parameter pusch-AggregationFactor.
  • pushch-AggregationFactor is set for PUSCH whose transmission is instructed by DCI format with CRC scrambled by C-RNTI, MCS-C-RNTI, or CS-RNTI. In this case, the number of iterations may be equal to pushch-AggregationFactor.
  • pusch-AggregationFactor may be set for PUSCH-Config.
  • the number of repetitions corresponding to PUSCH repetition type A may be the number of slots for PUSCH repetition transmission. Also, one TB may be repeated in one or more slots. The same OFDM symbol allocation may be applied to PUSCH repetitions transmitted in different slots.
  • PUSCH repetition transmission corresponding to PUSCH repetition type B may be based on nominal repetition (NominalRepetition) and actual repetition (Actual Repetition).
  • the frequency hopping method may be set by upper layer parameters.
  • the upper layer parameters frequencyHopping, frequencyHoppingDCI-0-1, and frequencyHoppingDCI-0-2 may be parameters that provide a frequency hopping method for PUSCH.
  • a frequency hopping method corresponding to frequency hopping for PUSCH may be set by frequencyHoppingDCI-0-2 in PUSCH-Config.
  • a frequency hopping method corresponding to frequency hopping for PUSCH may be set by frequencyHopping in PUSCH-Config.
  • a frequency hopping method corresponding to frequency hopping for PUSCH transmission set by frequencyHopping in configuredGrantConfig may be set.
  • the frequency hopping method may be intra-slot frequency hopping, inter-slot frequency hopping, or inter-repetition frequency hopping. Furthermore, the frequency hopping interval corresponding to intra-slot frequency hopping may be within one slot. The frequency hopping interval corresponding to inter-slot frequency hopping may be one slot or multiple slots. The frequency hopping interval corresponding to inter-iteration frequency hopping may be based on a nominal repetition.
  • the hopping interval may be provided by an upper layer parameter.
  • the upper layer parameter may be a dedicated upper layer parameter.
  • Whether or not to perform frequency hopping may be determined based at least on the DCI. Based at least on the value of the frequency hopping flag field included in the DCI format, it may be determined whether frequency hopping is applied for the PUSCH whose transmission is instructed by the DCI format. Based at least on the value of the frequency hopping flag field included in the random access response grant, it may be determined whether frequency hopping is applied for the PUSCH whose transmission is instructed by the random access response grant. For example, frequency hopping for PUSCH may be performed based at least on the value of the frequency hopping flag field being 1.
  • Intra-slot frequency hopping may be applied to PUSCH transmissions in one or multiple slots.
  • intra-slot frequency hopping may be applied to PUSCH repeated transmissions.
  • the arrangement may be switched for each one or more OFDM symbols.
  • the resource block arrangement may be switched between the first hop and the second hop for each one or more OFDM symbols. good.
  • the first hop and the second hop may be switched every one or more OFDM symbols.
  • the difference between the position of the first resource block of the first hop and the position of the first resource block of the second hop may be an RB offset .
  • RB offset may be set by upper layer parameters.
  • the one or more OFDM symbols may be within one slot.
  • the one or more OFDM symbols may be half the number of OFDM symbols for PUSCH within one slot.
  • Intra-slot frequency hopping may be applied to PUSCH corresponding to PUSCH repetition type A.
  • Inter-slot frequency hopping may be applied to PUSCH transmission in multiple slots.
  • the arrangement of resource blocks may be switched every slot.
  • inter-slot frequency hopping may be applied to PUSCH repeat transmissions.
  • the arrangement of resource blocks may be switched between the first hop and the second hop for each slot. For example, if the slot index n ⁇ s,f is an even number in a certain slot, the PUSCH transmission in the certain slot may correspond to the first hop. For example, if the slot index n ⁇ s,f in a certain slot is an odd number, the PUSCH transmission in the certain slot may correspond to the second hop.
  • Inter-slot frequency hopping may be applied to PUSCH corresponding to either PUSCH repetition type A or PUSCH repetition type B.
  • Inter-repetition frequency hopping may be applied to PUSCH corresponding to PUSCH repetition type B.
  • the first hop and the second hop may be switched based on the nominal repetition.
  • pusch-TransCoherence may define support for uplink codebook subsets for PUSCH transmission.
  • a UE that has indicated support for partial coherent codebook subsets may also support non-coherent codebook subsets.
  • a UE that indicates support for a fully coherent codebook subset may also support partial coherent and non-coherent codebook subsets.
  • pusch-TransCoherence-r18 may define support for uplink codebook subsets for PUSCH transmission.
  • a UE that has indicated support for a 2ports partial coherent codebook subset may also support a non-coherent codebook subset.
  • a UE that indicates support for the 4ports partial coherent codebook subset may also support the 2ports partial coherent and non-coherent codebook subsets.
  • a UE that has demonstrated support for the fully coherent codebook subset may also support 4ports partial coherent, 2ports partial coherent and non-coherent codebook subsets.
  • pusch-TransCoherence-r18 may be used as a UE capability that supports 8Tx transmission.
  • pusch-TransCoherence-r18 may define support for uplink codebook subsets for PUSCH transmission.
  • a UE that indicates support for non-coherent codebook subsets may only support non-coherent codebook subsets.
  • a UE that has indicated support for the 2ports partialcoherent codebook subset may only support the 2ports partialcoherent codebook subset.
  • a UE that indicates support for the 4ports partial coherent codebook subset may only support the 4ports partial coherent codebook subset.
  • a UE that has indicated support for the fully coherent codebook subset may only support the fully coherent codebook subset.
  • At least two transmission techniques may be supported for PUSCH.
  • codebook-based transmission may be one of the transmission methods for PUSCH.
  • non-codebook-based transmission may be one of the transmission techniques for PUSCH.
  • Upper layer parameters may provide for either codebook or non-codebook transmission. For example, if 'codebook' is set for the upper layer parameter, the terminal device 1 may be configured to send a codebook. For example, if 'nonCodebook' is set for the upper layer parameter, the terminal device 1 may be configured to transmit a non-codebook.
  • the upper layer parameter may be txConfig. The upper layer parameter may be usage.
  • the terminal device 1 does not need to expect to be scheduled according to either DCI format 0_1 or DCI format 0_2. If a PUSCH is scheduled by DCI format 0_0, the transmission of the PUSCH may be based on at least one antenna port.
  • PUSCH may be scheduled according to DCI format.
  • the DCI format may be any one of DCI format 0_0, DCI format 0_1, and DCI format 0_2.
  • PUSCH may be configured to be transmitted semi-statically.
  • Terminal device 1 may determine one or more precoders for PUSCH transmission.
  • the precoder may be determined based on at least some or all of SRI (SRS Resource indicator), TPMI (Transmitted Precoding Matrix Indicator), and transmission rank (Transmission rank).
  • SRI may be provided by the DCI field of one or two SRS resource indicators.
  • TPMI may be provided by one or two DCI fields of precoding information.
  • the transmission rank may be provided by the DCI field of the number of layers (number of transmission layers).
  • SRI may be provided by a first upper layer parameter.
  • TPMI and transmission rank may be provided by second upper layer parameters.
  • the first upper layer parameter may be srs-ResourceIndicator or srs-ResourceIndicator2.
  • the second upper layer parameter may be precodingAndNumberOfLayers or precodingAndNumberOfLayers2.
  • the SRS resource set applied to PUSCH may be determined based on upper layer parameters.
  • the PUSCH may be scheduled according to DCI format 0_1 or DCI format 0_2.
  • the upper layer parameter may be srs-ResourceSetToAddModList or srs-ResourceSetToAddModeListDCI-0-2.
  • the upper layer parameter may be an upper layer parameter set in SRS-Config.
  • one or two SRS resource sets may be set in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2.
  • the upper layer parameter usage may be set in the upper layer parameter SRS-ResourceSet.
  • SRI and TPMI may be given by the DCI field. TPMI may be used to direct the precoder.
  • the precoder may be applied across v layers. If multiple SRS resources are configured, one SRS resource may be selected by SRI.
  • the transmission precoder (precoder) may be selected from a codebook (uplink codebook). For example, a codebook may have a number of antenna ports. The number of antenna ports may be the same as the upper layer parameter nrofSRS-Ports.
  • 'codebook' is set in the upper layer parameter txConfig, at least one SRS resource may be configured in the terminal device 1.
  • the indicated SRI may be related to the transmission of SRS resources identified by the SRI.
  • the DCI field may be one or both of a DCI field for SRS resource indication, and a DCI field for precoding information and the number of layers.
  • the terminal device 1 may apply the instructed SRI and TPMI to one or more PUSCH repetitions.
  • TPMI may be used to direct the precoder based on the code points of the SRS resource set indication.
  • the precoder may be applied to the 0th to v-1th layers.
  • the precoder may correspond to SRS resources selected by SRI. Multiple SRS resources may be configured for an applicable SRS resource set.
  • the transmit precoder may be selected from a codebook (uplink codebook).
  • codebook uplink codebook
  • the terminal device 1 may expect that the number of antenna ports for the two indicated SRS resources is the same.
  • the number of antenna ports may be provided by higher layer parameters.
  • the terminal device 1 may determine a codebook subset.
  • the codebook subset may be determined based at least on TPMI.
  • the codebook subset may be determined in response to receiving certain upper layer parameters.
  • One upper layer parameter may be codebookSubset, codebookSubset-r18, or codebookSubsetDCI-0-2.
  • Certain upper layer parameters may be determined based at least on the number of SRS ports. For example, if the number of SRS ports is 4 or less, a certain upper layer parameter may be codebookSubset or codebookSubsetDCI-0-2. For example, if the number of SRS ports is greater than 4, one upper layer parameter may be codebookSubset-r18.
  • Certain upper layer parameters may be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', 'nonCoherent', 'fullyCoherent', 'partialCoherent', '4portsPartialCoherent', and '2portsPartialCoherent'.
  • the codebook subset associated with a 2-port SRS resource may be 'nonCoherent' if at least one upper layer parameter is set to 'partialAndNonCoherent'.
  • a codebook may include at least one SRS resource with 4 ports and at least one SRS resource with 2 ports.
  • the codebook subset associated with a 4-port SRS resource (an SRS resource with 4 ports) may be 'fullyAndPartialAndNonCoherent'.
  • the codebook subset associated with a 2-port SRS resource (SRS resource with 2 ports) may be 'partialAndNonCoherent'.
  • a codebook may include at least one SRS resource with 8 ports and at least one SRS resource with 4 ports.
  • the terminal device 1 may not expect the codebook subset with 'fullyAndPartialAndNonCoherent' to be configured.
  • the terminal device 1 may not expect the codebook subset with 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent' to be configured.
  • the terminal device 1 If the terminal device 1 reports the UE capability of 'fullyCoherent' transmission, the terminal device 1 does not need to expect that a codebook subset with 'partialCoherent' or 'nonCoherent' is configured.
  • the terminal device 1 If the terminal device 1 reports the UE capability of 'partialCoherent' transmission, the terminal device 1 does not need to expect that a codebook subset with 'fullyCoherent' or 'nonCoherent' is configured.
  • the terminal device 1 If the terminal device 1 reports the UE capability of 'nonCoherent' transmission, the terminal device 1 does not need to expect that a codebook subset with 'fullyCoherent' or 'partialCoherent' is configured.
  • terminal device 1 If terminal device 1 reports a UE capability of 'fullyCoherent' transmission, terminal device 1 does not expect the codebook subset with '2portsPartialCoherent', '4portsPartialCoherent' or 'nonCoherent' to be configured. good.
  • terminal device 1 If terminal device 1 reports a UE capability of '4portsPartialCoherent' transmission, terminal device 1 does not expect the codebook subset with 'fullyCoherent', '2portsPartialCoherent' or 'nonCoherent' to be configured. good.
  • terminal device 1 If terminal device 1 reports a UE capability of '2portsPartialCoherent' transmission, terminal device 1 does not expect the codebook subset with 'fullyCoherent', '4portsPartialCoherent' or 'nonCoherent' to be configured. good.
  • terminal device 1 If terminal device 1 reports a UE capability of 'nonCoherent' transmission, terminal device 1 does not expect the codebook subset with 'fullyCoherent', '4portsPartialCoherent' or '2portsPartialCoherent' to be configured. good.
  • terminal device 1 may not expect the upper layer parameter 'partialAndNonCoherent' to be configured. good.
  • the upper layer parameter may be codebookSubset or codebookSubsetForDCI-Format0-2.
  • the number of antenna ports may be determined by the upper layer parameter nrofSRS-Ports.
  • the upper layer parameter may be codebookSubset-r18 or codebookSubsetForDCI-Format0-2-r18.
  • the number of antenna ports may be determined by the upper layer parameter nrofSRS-Ports.
  • terminal device 1 specifies that the upper layer parameter is configured to 'fullyCoherent' or '4portsPartialCoherent'. You don't have to expect it.
  • the upper layer parameter may be codebookSubset-r18 or codebookSubsetForDCI-Format0-2-r18.
  • the number of antenna ports may be determined by the upper layer parameter nrofSRS-Ports.
  • terminal device 1 shall configure the upper layer parameter to be set to 'fullyCoherent' or '2portsPartialCoherent'. You don't have to expect it.
  • the upper layer parameter may be codebookSubset-r18 or codebookSubsetForDCI-Format0-2-r18.
  • the number of antenna ports may be determined by the upper layer parameter nrofSRS-Ports.
  • one SRS resource may be determined based on the SRI from the SRS resource set.
  • the maximum number of SRS resources configured for codebook transmission may be 2, except when 'fullpowerMode2' is set in the first upper layer parameter.
  • the first upper layer parameter may be ul-FullPowerTransmission.
  • the DCI may direct the transmission of SRS resources. For example, if aperiodic SRS is configured, the SRS request field in the DCI may indicate the transmission of aperiodic SRS resources.
  • the terminal device 1 does not need to expect that the first upper layer parameter to which 'fullpowerMode1' is set and the second upper layer parameter to which 'fullAndPartialAndNonCoherent' are set.
  • the terminal device 1 may transmit the PUSCH using the same one or more antenna ports as one or more SRS ports in the SRS resources indicated by the DCI format or upper layer parameters.
  • the SRS port may be the same as the antenna port for PUSCH transmission.
  • the DMRS antenna port may be determined according to DMRS port ordering.
  • the terminal device 1 may expect the upper layer parameter nrofSRS-Ports to be configured with the same value for these SRS resources.
  • the SRS resource set may be an upper layer parameter SRS-ResourceSet with an upper layer parameter usage in which 'codebook' is set.
  • 'fullpowerMode2' When 'fullpowerMode2' is set for the upper layer parameter, one or more SRS resources with the same or different numbers of SRS ports may be configured in one SRS resource set. If 'fullpowerMode2' is set for upper layer parameters, at most two different spatial relations may be configured for all SRS resources in one SRS resource set. When 'fullpowerMode2' is set for the upper layer parameter, a maximum of 2 or 4 SRS resources may be configured in one SRS resource set. Furthermore, up to eight SRS resources may be configured in one SRS resource set. The SRS resource set may be an SRS resource set with an upper layer parameter usage in which 'codebook' is set.
  • PUSCH may be scheduled according to DCI format 0_0, DCI format 0_1, or DCI format 0_2.
  • the terminal device 1 may determine the PUSCH precoder and transmission rank based on the SRI. For example, when multiple SRS resources are configured, SRI may be provided by one or two SRS resource indications in the DCI. For example, SRI may be given by upper layer parameters.
  • the SRS resource set applied to PUSCH may be defined by an entry of upper layer parameters.
  • the upper layer parameter may be srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2.
  • the terminal device 1 may use one or more SRS resources for SRS transmission.
  • the maximum number of SRS resources in one SRS resource set may be transmitted to the base station device 3 as UE capability.
  • SRS resources may be configured for simultaneous transmission in the same OFDM symbol. Multiple SRS resources transmitted simultaneously may occupy the same resource block.
  • One SRS port may be configured in each SRS resource.
  • One or two SRS resource sets may be configured in the upper layer parameter srs-ResourceSetToAddModList where the upper layer parameter usage in the upper layer parameter SRS-ResourceSet is set to 'nonCodebook'. If two SRS resource sets are configured, one or two SRIs may be given by the DCI field.
  • the DCI field may be the DCI field of two SRS resource indications.
  • the terminal device 1 may apply the instructed SRI to one or more PUSCH repetitions. For example, according to the SRS resource set of PUSCH repetition, the terminal device 1 may apply the instructed SRI to one or more PUSCH repetitions.
  • the maximum number of SRS resources per SRS resource set configured for non-codebook transmission may be four.
  • the maximum number of SRS resources per SRS resource set configured for non-codebook transmission may be eight.
  • Each of the one or two SRIs indicated may be associated with the most recent transmission of an SRS resource of the SRS resource set identified by the SRI. SRS transmission may precede the PDCCH carrying SRI. The terminal device 1 does not have to expect that different numbers of SRS resources are configured in the two SRS resource sets.
  • PDCCH candidate(s) If multiple PDCCH candidates (PDCCH candidate(s)) are associated with the search area set set by the upper layer parameters, one PDCCH candidate is used.
  • the one PDCCH candidate may be one of the two PDCCH candidates that starts earlier.
  • the upper layer parameter may be searchSpaceLinking.
  • the UE may calculate a precoder.
  • a precoder used for SRS transmission may be calculated based on measurements of NZP CSI-RS resources.
  • One NZP CSI-RS resource may be configured for one SRS resource set.
  • one SRS resource set may be an SRS resource set that has an upper layer parameter set to 'nonCodebook'.
  • the NZP-CSI RS may be indicated via the SRS request field.
  • the SRS request field may be one of the DCI fields in any of DCI format 0_1, DCI format 0_2, DCI format 1_1, and DCI format 1_2.
  • the first upper layer parameter may indicate an association between an aperiodic SRS (SRStriggering state) and an SRS resource set.
  • the first upper layer parameter, triggered SRS resource, srs-ResourceSetId, and csi-RS may be configured in the upper layer parameter SRS-ResourceSet.
  • the upper layer parameter csi-RS may indicate NZP-CSI-RS-ResourceId.
  • the upper layer parameters associated with the SRS request, SRS-ResourceSet may be defined by entries in a list of upper layer parameters.
  • the list that is the upper layer parameter may be the upper layer parameter srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2.
  • Terminal device 1 does not need to expect to update precoding information (SRS precoding information). For example, if the gap from the last OFDM symbol of reception of aperiodic NZP-CSI-RS resource to the first OFDM symbol of aperiodic SRS transmission is less than or equal to 42 OFDM symbols, terminal device 1 updates the precoding information. You don't have to expect that.
  • Aperiodic NZP When an aperiodic SRS associated with a CSI-RS resource is configured, the presence of the CSI-RS may be indicated by the SRS request field. If the value of the SRS request field is not '00' and the scheduling DCI is not used for cross carrier scheduling or cross BWP scheduling, the presence of CSI-RS may be indicated by the SRS request field.
  • the terminal device 1 may perform one-to-one mapping.
  • the one-to-one mapping may be a mapping from SRI to DMRS port and corresponding PUSCH layer.
  • PUSCH layers from 0 to v-1 may be provided.
  • v may be the number of layers.
  • the number of layers may be set by upper layer parameters.
  • the terminal device 1 may transmit PUSCH using the same antenna port as the SRS port.
  • the SRS port in the (i+1)th SRS resource may be pi.
  • the SRS port in the (i+1)th SRS resource may be indexed as pi.
  • both the spatial relation information (info) for the SRS resource and the upper layer parameter associatedCSI-RS in the upper layer parameter SRS-ResourceSet for the SRS resource set are set.
  • the terminal device 1 does not have to expect that this will happen.
  • Spatial relationship information may be determined by upper layer parameters.
  • the spatial relationship information may be an upper layer parameter spatialRelationInfo.
  • terminal device 1 schedules using DCI format 0_1 or DCI format 0_2. may be done.
  • the CQI index and its interpretation for reporting CQI may be indicated based on the modulation scheme.
  • the terminal device 1 derives the highest CQI index that satisfies the following conditions for each CQI value reported in uplink slot n, based on an observation interval that is unlimited in time and an observation interval that is unlimited in frequency. It's okay.
  • a single PDSCH transport block that occupies a group of downlink physical resource blocks called CSI reference resources exceeds the transport block error probability. It may be possible to receive it without any conditions.
  • terminal device 1 performs channel measurements for calculating the CSI value reported in UL slot n from the CSI reference resource associated with the CSI resource configuration. May be derived based only on NZP CSI-RS without slowing down.
  • terminal device 1 reports CSI in UL slot n based only on the latest opportunity of the NZP CSI-RS related to the CSI resource configuration and not later than the CSI reference resource. Channel measurements may be derived for calculation.
  • terminal device 1 uses the The interference measurement may be derived to be no later than the CSI reference resource associated with the CSI resource configuration.
  • terminal device 1 uses the latest CSI-IM and/or NZP CSI-RS for interference measurement related to the CSI resource configuration that is not slower than the CSI reference resource. Interference measurements may be derived to calculate a CSI value to report in UL slot n based on the opportunity.
  • a 2-bit subband difference CQI may be defined for each subband index s as follows.
  • Subband offset level (s) subband CQI index (s) - wideband CQI index
  • the combination of modulation scheme and transport block size may correspond to the CQI index in the following cases.
  • the CSI reference resource may be signaled for transmission on the PDSCH, and the modulation scheme is indicated by the CQI index, and the combination of transport block size and modulation scheme When applied to the reference resource, an effective channel coding rate closest to the coding rate indicated by the CQI index may be obtained. If there are multiple combinations of transport block sizes and modulation methods that result in effective channel coding rates that are equally close to the coding rate indicated by the CQI index, only the combination with the smallest transport block size is relevant. It's okay.
  • each PMI value may correspond to a codebook index as follows.
  • the terminal device 1 may be configured with an upper layer parameter twoTX-CodebookSubsetRestriction.
  • the bitmap parameter twoTX-CodebookSubsetRestriction may form a bit string a 5 ,...,a 1 ,a 0 where a 0 is the LSB and a 5 is the MSB.
  • a bit value of 0 may indicate that PMI reports are not allowed to correspond to the precoder associated with that bit.
  • Bits 0 to 3 may be associated with codebook indices 0 to 3, respectively, with a number of layers of 1
  • bits 4 and 5 may be associated with codebook indices 0 and 1, respectively, with a number of layers of 2.
  • the composite codebook index i 1 may be composed of part or all of i 1,1 , i 1,2 , i 1,3 .
  • k 1 and k 2 may be determined as 0 or a multiple of O 1 , O 2 based on i 1,3 , the number of layers v, and the antenna configuration N 1 , N 2 of the terminal device 1.
  • N 1 and N 2 may be the number of horizontal and vertical antennas arranged on the antenna panel of the terminal device 1.
  • O 1 and O 2 may be oversampling numbers that determine horizontal and vertical beam sweeping steps of the terminal device 1.
  • the supported combinations of (N 1 , N 2 ) and (O 1 , O 2 ) may be determined based on the number of CSI-RS ports P CSI-RS of the terminal device 1.
  • N 1 and N 2 may be set by upper layer parameters n1-n2.
  • the bitmap parameters n1-n2 may form a bit string a Ac-1 , ...,a 1 ,a 0 where a 0 is the LSB and a Ac-1 is the MSB.
  • a bit value of 0 may indicate that the PMI report is not allowed to correspond to any precoder associated with that bit.
  • bitmap parameter typeI-SinglePanel-codebookSubsetRestriction-i2 is b 15 ,..., where b 0 is the LSB and b 15 is the MSB.
  • a bit string of b 1 and b 0 may be formed.
  • the precoding matrix W may be determined based on part or all of the number of CSI-RS ports P CSI-RS and the quantities ⁇ n , ⁇ p , um , v l,m , v ⁇ l,m . Also, each of the quantities may be determined based on some or all of l,m,n,p, and the l,m,n,p is based on some or all of i 1 and i 2 . may be determined.
  • N g the values of N g , N 1 and N 2 are the upper layer parameters ng-n1-n2. May be set.
  • the number of CSI-RS ports P CSI-RS may be given as 2N g N 1 N 2 .
  • the supported combinations of (N g , N 1 , N 2 ) and (O 1 , O 2 ) may be determined based on the number of CSI-RS ports P CSI-RS of the terminal device 1.
  • N g 2, codebookMode may be set to 1 or 2.
  • N g 4, codebookMode may be set to 1.
  • N g may be the number of panels forming the antenna panel of the terminal device 1.
  • the bitmap parameters ng-n1-n2 may form a bit string a Ac - 1 ,...,a 1 ,a 0 where a 0 is the LSB and a Ac-1 is the MSB.
  • a bit value of 0 may indicate that the PMI report cannot correspond to any precoder associated with that bit.
  • the number of bits Ac may be given by N 1 O 1 N 2 O 2 .
  • Each PMI value may correspond to a codebook index i 1 and i 2 .
  • i 1 may be composed of part or all of i 1,1 , i 1,2 , and i 1,4 .
  • i 1 may be composed of part or all of i 1,1 , i 1,2 , i 1,3 , i 1,4 .
  • v may be related to the RI value.
  • k 1 and k 2 may be determined as 0 or a multiple of O 1 , O 2 based on i 1,3 , the number of layers v, and the antenna configuration N g , N 1 , N 2 of the terminal device 1.
  • N 2 1
  • the precoding matrix W (v) l,m,p,n is W 1,2,1 l,m,p,n , W 2,2,1 l,m,p,n , W 1,4,1 l ,m,p,n ,W 2,4,1 l,m,p,n ,W 1,2,2 l,m,p,n ,W 2,2,2 l,m,p,n It may consist of part or all.
  • W 1,2,1 l,m,p,n , W 2,2,1 l,m,p,n , W 1,4,1 l,m,p,n , W 2,4, 1 l,m,p,n , W 1,2,2 l,m,p,n , W 2,2,2 l,m,p,n is the number of CSI-RS ports P CSI-RS and the amount ⁇ n , a p , b n , um , and v l,m may be determined based on some or all of them.
  • each of the quantities may be determined based on some or all of l,m,n,p, and the l,m,n,p is based on some or all of i 1 and i 2 . may be determined.
  • the p may be composed of some or all of p 1 , p 2 , and p 3
  • the n may be composed of some or all of n 0 , n 1 , and n 2 .
  • FIG. 9 is a diagram illustrating an example of a method for applying a precoding matrix according to an aspect of the present embodiment.
  • W indicates a precoding matrix
  • precoding for PUSCH is performed based on the precoding matrix W.
  • vectors d 1 , d 2 , . . . , d K are subjected to precoding based on a precoding matrix W, and converted into vectors x 1 , x 2 , . . . , x M.
  • the vectors d 1 , d 2 , . . . , d K may be PUSCH data with K layers.
  • the conversion from d 1 , d 2 ,...,d K to x 1 , x 2 ,..., x M can be obtained by multiplying by the precoding matrix W.
  • the size of the precoding matrix W may be determined based on the number K of layers and the number M of transmitting side antenna ports.
  • Vectors x 1 , x 2 ,...,x M are received via propagation channel H as vectors y 1 , y 2 ,..., y N.
  • the size of the propagation channel H may be determined based on the number M of antenna ports on the transmitting side and the number N of antenna ports on the receiving side.
  • the precoding matrix W may be equal to the identity matrix.
  • the antenna configuration of the terminal device 1 may be given based on n1-n2-codebookSubsetRestriction, n1-n2-codebookSubsetRestriction-r16, and n1-n2-codebookSubsetRestriction-r18.
  • the terminal device 1 may edit the capability information of the terminal.
  • the terminal device 1 may transmit (transfer) terminal capability information.
  • the terminal device 1 may edit and transfer the terminal's capability information (UE capability information). Further, the notification of the terminal capability information may be performed according to the procedure shown below.
  • a procedure for the terminal may be initiated with RRC_CONNECTED.
  • UE capabilities may be obtained only after activation of AS security. The UE capabilities acquired before AS security activation may not be transferred to the CN.
  • the terminal device 1 may set the content of the UECapabilityInformation message as follows.
  • the ue-CapabilityRAT-ContainerList may include a UE-CapabilityRAT-Container whose type is UE-NR-Capability and whose rat-Type is set to nr.
  • SupportedBandCombinationList, featureSets and featureSetCombinations may be included.
  • the terminal device 1 sends UECapabilityInformation
  • the content of the message may be set as follows.
  • the ue-CapabilityRAT-ContainerList may include a UE-CapabilityRAT-Container whose type is UE-MRDC-Capability and whose rat-Type is set to eutra-nr. SupportedBandCombinationList and featureSetCombinations may be included.
  • the terminal device 1 sets the contents of the UECapabilityInformation message as follows. It may be set to
  • the ue-CapabilityRAT-ContainerList may include a ue-CapabilityRAT-Container with type UE-EUTRA-Capability and rat-Type set to eutra when received.
  • the terminal device 1 sends the contents of the UECapabilityInformation message as follows: You can also set it like this.
  • the UE radio access capability for UTRA-FDD whose rat-Type is set to utra-fdd may be included in the ue-CapabilityRAT-Container.
  • the terminal device 1 updates the contents of the UECapabilityInformation message as follows: May be set. A UL message segment transfer procedure may be initiated.
  • the terminal device 1 may set the contents of the UECapabilityInformation message as follows.
  • a UECapabilityInformation message may be sent to the lower layer, at which point the procedure may be terminated.
  • the terminal device 1 may call the procedure when the NR or E-UTRA network requests UE capabilities regarding nr, eutra-nr, or eutra. This procedure may be called once for each requested rat-Type.
  • the terminal device 1 may ensure that the feature set ID is consistent across feature sets, feature set combinations, and band combinations in all three UE capability containers in which the network queries the same field with the same value.
  • the UE capability container may be fields of the UE-CapabilityRequestFilterNR, UE-CapabilityRequestFilterCommon and UECapabilityEnquiry messages.
  • the gNB may require RAT type nr and eutra-nr capabilities.
  • the featureSets in UE-NR-Capability may also be used along with featureSetCombinations in UE-MRDC-Capability to determine the NR UE capabilities for supported MRDC band combinations.
  • the eNB may require capabilities of RAT types eutra and eutra-nr.
  • featureSetsEUTRA in UE-EUTRA-Capability may be used together with featuresSetCombinations in UE-MRDC-Capability to determine E-UTRA UE capabilities for supported MRDC band combinations.
  • the IDs used in featureSets may match the IDs referenced in featureSetCombinations in all three containers. The consistency requirement may mean that there are no undefined feature sets and feature set combinations.
  • the UE may be up to the UE implementation to prioritize which feature sets and feature set combinations. .
  • the terminal device 1 may create a list of "band combination candidates" consisting only of the bands included in frequencyBandListFilter, according to the filter criteria of capabilityRequestFilterCommon (if included). You may also prioritize frequencyBandListFilter.
  • the priority setting may be done in such a way as to first include the combination of bands that includes the first listed band, then include the remaining combinations of bands that include the second listed band, etc. good.
  • the band parameter may not exceed the received one of maxBandwidthRequestedDL, maxBandwidthRequestedUL, maxCarriersRequestedDL, maxCarriersRequestedUL, ca-BandwidthClassDL-EUTRA, or ca-BandwidthClassUL-EUTRA.
  • the terminal device 1 determines whether the network (E-UTRA) includes the eutra-nr-only field or if the requested rat-Type is eutra. If so, the NR-only band combination may be deleted from the list of “band combination candidates.”
  • the eutra-nr-only flag may indicate that the UE-NR-Capability does not include the NR band combination.
  • the above procedure may remove all NR-only band combinations from the candidate list, thereby avoiding the corresponding feature set combinations and also the inclusion of the following feature sets.
  • the terminal device 1 is considered to be a spare band combination that has the same capability as other band combinations included in the list of "band combination candidates", or if this spare band combination is A band combination may be removed from the list of "candidate band combinations" if it is generated by releasing an uplink configuration.
  • the E-UTRA band number may be included in the frequencyBandListFilter so that the UE includes all the feature sets required for the subsequently requested eutra-nr functionality.
  • the list of "band combination candidates" matches the filter provided by the NW (frequencyBandListFilter) AND (if RAT-Type nr was requested by E-UTRA) the eutra-nr only flag may include all NR- and/or E-UTRA-NR band combinations that match.
  • this candidate list may be used to derive the band combinations, feature set combinations, and feature sets reported in the requested capability container.
  • the terminal device 1 may include as many NR-only band combinations as possible from the list of "band combination candidates" in the supportedBandCombinationList from the first entry. Furthermore, when an srs-SwitchingTimeRequest is received and SRS carrier switching is supported, srs-SwitchingTimesListNR may be included for each band combination. At this time, srs-SwitchingTimeRequested may be set to true.
  • the terminal device 1 may include feature set combinations referenced from the corresponding band combinations included in supportedBandCombinationList in featureSetCombinations. Furthermore, the list of "candidate function set combinations" referenced from the list of “candidate band combinations” may be compiled by excluding entries (rows of function set combinations) having the same or lower capabilities.
  • terminal device 1 receives an uplinkTxSwitchRequest, it selects a possible NR-only band combination that supports UL TX switching from the list of "candidate band combinations" from the first entry. May be included in supportedBandCombinationList-UplinkTxSwitch as long as supportedBandCombinationList-UplinkTxSwitch.
  • srs-SwitchingTimeRequest may be included for each band combination. At this time, srs-SwitchingTimeRequested may be set to true.
  • the terminal device 1 may include the feature set combination referenced from the support band combinations included in supportedBandCombinationList-UplinkTxSwitch in featureSetCombinations.
  • feature set combination candidates may include not only combinations of E-UTRA-NR bands but also combinations of feature sets used exclusively for NR.
  • the list may be used to derive a list of NR feature sets referenced from the combination of feature sets in the UE-NR-Capability and the combination of feature sets in the UE-MRDC-Capability container.
  • the terminal device 1 may include the feature set referenced from the "candidate feature set combination" in featureSets. Further, a function set having a parameter exceeding any one of maxBandwidthRequestedDL, maxBandwidthRequestedUL, maxCarriersRequestedDL, and maxCarriersRequestedUL may be excluded even if it is received.
  • terminal device 1 sets as many E-UTRA-NR band combinations as possible from the list of "band combination candidates" in supportedBandCombinationList and/or supportedBandCombinationListNEDC-Only. , may be entered in order starting from the first entry. Furthermore, when srs-SwitchingTimeRequest is received and SRS carrier switching is supported, srs-SwitchingTimesListNR and srs-SwitchingTimesListEUTRA may be included for each band combination. At this time, srs-SwitchingTimeRequested may be set to true.
  • the terminal device 1 may include feature set combinations referenced from the corresponding band combinations included in supportedBandCombinationList in featureSetCombinations according to the previous section. Furthermore, the list of "candidate feature set combinations" referenced from the list of "candidate band combinations” may be compiled by excluding entries (rows of feature set combinations) with the same or lower capabilities.
  • the terminal device 1 receives an uplinkTxSwitchRequest, it sets the NR-dedicated band combination that supports UL TX switching from the list of "band combination candidates" in supportedBandCombinationList-UplinkTxSwitch. may be included as far as possible from the first entry. Furthermore, when an srs-SwitchingTimeRequest is received and SRS carrier switching is supported, srs-SwitchingTimesListNR may be included for each band combination. At this time, srs-SwitchingTimeRequested may be set to true.
  • the terminal device 1 may include the feature set combination referenced from the support band combinations included in supportedBandCombinationList-UplinkTxSwitch in featureSetCombinations.
  • the terminal device 1 replaces the list of "feature set combination candidates" referenced from the list of "band combination candidates" with entries with the same or lower capabilities ( It may be compiled without the feature set combination line).
  • This list of "feature set combination candidates” may include feature set combinations used to combine E-UTRA-NR bands.
  • the list may be used to derive a list of E-UTRA capability sets referenced from the combination of capability sets in the UE-MRDC-Capability container.
  • the terminal device 1 may include the feature set referenced from the "combination of candidate feature sets" (within UE-EUTRA-Capability) in featureSetsEUTRA. Additionally, feature sets with parameters exceeding ca-BandwidthClassDL-EUTRA or ca-BandwidthClassUL-EUTRA may be received or excluded.
  • the terminal device 1 may include the received frequencyBandListFilter in the requested UE capability field appliedFreqBandListFilter, unless the requested rat-Type is nr and the eutra-nr-only field is included in the network.
  • the terminal device 1 may include the received ue-CapabilityEnquiryExt in the receivedFilters field.
  • Terminal device 1 transmits first information, receives second information for determining a precoding matrix for the PUSCH, and determines a DCI to schedule the PUSCH and a precoding matrix for the PUSCH.
  • the precoding matrix is determined based on the second information for the PUSCH, and precoding for the PUSCH is performed based on the precoding matrix.
  • the terminal device 1 may transmit the first information.
  • the terminal device 1 may receive the second information.
  • the second information may be used to determine a precoding matrix for PUSCH.
  • the precoding matrix may be used in precoding for PUSCH.
  • the precoding matrix may be determined based on at least the DCI and the second information. DCI may schedule PUSCH.
  • the terminal device 1 may perform precoding for PUSCH. Precoding may be performed based at least on a precoding matrix.
  • the second information may be information for calculating a precoding matrix.
  • the first information may be capability information of the terminal device 1.
  • the first information may be the number of antenna ports.
  • the first information may be information indicating the number of one or more antenna ports.
  • the first information may be information indicating the number of antenna ports, which is two, and the number of panels, which is one.
  • the first information may be information indicating the number of first antenna ports in the first dimension and the second dimension.
  • the first information may be determined based on the antenna configuration of the terminal device 1.
  • the first information may be UE capability determined based on the antenna configuration of the terminal device 1.
  • the first information may be transmitted (reported) to the base station device 3 as UE capability.
  • the first information may be assistance information determined based on the antenna configuration of the terminal device 1.
  • the first information may be an RRC parameter determined based on the antenna configuration of the terminal device 1.
  • the first information may be determined based on channel state information.
  • the first information may be UE capability determined based on channel state information.
  • the first information may be assistance information determined based on channel state information.
  • the first information may be an RRC parameter determined based on channel state information.
  • the first information may be the number of antennas (physical antennas) of the terminal device 1.
  • the first information may be information related to one or both of the number of antennas and the arrangement of the antennas.
  • the first information is nrOfAntennaPorts, twoTX-CodebookSubsetRestriction, n1-n2, typeI-SinglePanel-codebookSubsetRestriction-i2, typeI-SinglePanel-ri-Restriction, ng-n1-n2, ri-Restriction, codebookMode, n1-n2-codebookSubsetRestriction , typeII-RI-Restriction, portSelectionSamplingSize, typeII-PortSelectionRI-Restriction, phaseAlphabetSize, subbandAmplitude, numberOfBeams, n1-n2-codebookSubsetRestriction-r16, typeII-RI-Restriction-r16, portSelectionSamplingSize-r16, typeII-PortSelectionRI-Restriction-r16, numberOfPMI -SubbandsPerCQI-Subband-r
  • the first information may be part or all of N g , N 1 , N 2 , O 1 , O 2 , i 1 , i 2 , k 1 , k 2 , l, m, n, p. good.
  • the second information may be RRC parameters.
  • the second information may be an RRC parameter for determining a codebook used in precoding for the PUSCH.
  • the second information may be the number of antenna ports.
  • the second information may be information indicating the number of one or more antenna ports.
  • the second information may be information indicating the number of antenna ports, which is two, and the number of panels, which is one.
  • the second information may be information indicating the second number of antenna ports in the first dimension and the second dimension.
  • the number of first antenna ports indicated by the first information may be different from the number of second antenna ports indicated by the second information.
  • the number of second antenna ports may be the same as the number of first antenna ports, or may be less than the number of first antenna ports.
  • the first number of panels indicated by the first information may be different from the second number of panels indicated by the second information.
  • the second information may be determined based on the antenna configuration of the terminal device 1.
  • the second information may be UE capability determined based on the antenna configuration of the terminal device 1.
  • the second information may be transmitted (reported) to the base station device 3 as UE capability.
  • the second information may be assistance information determined based on the antenna configuration of the terminal device 1.
  • the second information may be an RRC parameter determined based on the antenna configuration of the terminal device 1.
  • the second information may be determined based on channel state information.
  • the second information may be UE capability determined based on channel state information.
  • the second information may be assistance information determined based on channel state information.
  • the second information may be an RRC parameter determined based on channel state information.
  • the second information may be information for codebook subset restriction.
  • the second information may be information for limiting the codebook subset.
  • the codebook subset may be determined based at least on the second information.
  • the second information is nrOfAntennaPorts, twoTX-CodebookSubsetRestriction, n1-n2, typeI-SinglePanel-codebookSubsetRestriction-i2, typeI-SinglePanel-ri-Restriction, ng-n1-n2, ri-Restriction, codebookMode, n1-n2-codebookSubsetRestriction , typeII-RI-Restriction, portSelectionSamplingSize, typeII-PortSelectionRI-Restriction, phaseAlphabetSize, subbandAmplitude, numberOfBeams, n1-n2-codebookSubsetRestriction-r16, typeII-RI-Restriction-r16, portSelectionSamplingSize-r16, typeII-PortSelectionRI-Restriction-r16, numberOfPMI -SubbandsPerCQI-Subband-r
  • the second information may be part or all of N g , N 1 , N 2 , O 1 , O 2 , i 1 , i 2 , k 1 , k 2 , l, m, n, p. good.
  • Information for determining a codebook matrix from the restricted codebook subset based on the first information may be indicated in the DCI.
  • Information for determining a codebook matrix from the restricted codebook subset based on the second information may be indicated in the DCI.
  • the information for determining the codebook matrix may be i1 and i2.
  • i 1 and i 2 may be indicated by DCI.
  • Each value of the TPMI field in the DCI may be associated with i1, i2.
  • the information indicating the number of antenna ports in the first dimension and the second dimension may be N 1 and N 2 .
  • the information indicating the number of antenna ports in the first dimension and the second dimension may be part or all of N g , N 1 , and N 2 .
  • the information indicating the first number of antenna ports in the first dimension and the second dimension and the information indicating the second number of antenna ports in the first dimension and the second dimension may be the same or different information. It's okay.
  • the information indicating the first number of antenna ports in the first dimension and the second dimension and the information indicating the second number of antenna ports in the first dimension and the second dimension are determined by comparing. Good too.
  • the terminal device 1 receives a PDCCH in which a DCI that schedules a PUSCH is arranged, transmits the PUSCH, and sets a first RRC parameter and a second RRC parameter, and the first RRC parameter is
  • the second RRC parameter is information for defining a first codebook subset for the PUSCH
  • the third RRC parameter is information for defining a second codebook subset for the PUSCH
  • the third RRC parameter is information for defining a second codebook subset for the PUSCH.
  • the third RRC parameter is information for determining the number of SRS ports of the SRS resource instructed by the DCI, and if the number of SRS ports is 4 or less, the third RRC parameter is information for determining the number of SRS ports of the SRS resource instructed by the DCI.
  • a precoding matrix for the PUSCH is determined based at least on one codebook subset, and if the number of SRS ports is greater than four, the DCI and the second codebook subset; A precoding matrix for PUSCH is determined.
  • the terminal device 1 may receive the PDCCH in which the DCI that schedules the PUSCH is arranged.
  • the terminal device 1 may transmit the PUSCH.
  • a first RRC parameter and a second RRC parameter may be set.
  • the first RRC parameter may be information for defining a first codebook subset for the PUSCH.
  • the second RRC parameter may be information for defining a second codebook subset for the PUSCH.
  • a third RRC parameter may be configured.
  • the third RRC parameter may be information for determining the number of SRS ports of the SRS resource instructed by the DCI. If the number of SRS ports is 4 or less, a precoding matrix for the PUSCH may be determined based at least on the DCI and the first codebook subset. If the number of SRS ports is greater than 4, a precoding matrix for the PUSCH may be determined based at least on the DCI and the second codebook subset.
  • the first RRC parameter may be codebookSubset.
  • the first RRC parameter may correspond to some or all of full coherent capability, partial coherent capability, and non-coherent capability.
  • the first RRC parameter may be set to fullyAndPartialAndNonCoherent, partialAndNonCoherent, or nonCoherent.
  • the second RRC parameter may be codebookSubset-r18.
  • the second RRC parameter may correspond to some or all of full coherent capability, partial coherent capability, and non-coherent capability.
  • the second RRC parameter may be set to fullyCoherent, partialCoherent, or nonCoherent.
  • the second RRC parameter may be set to fullyCoherent, 4portsPartialCoherent, 2portsPartialCoherent, or nonCoherent.
  • the third RRC parameter may be nrofSRS-Ports.
  • the third RRC parameter may be nrOfAntennaPorts.
  • Terminal device 1 receives a PDCCH in which a DCI that schedules a PUSCH is arranged, transmits the PUSCH, and transmits terminal capability information, and the terminal device capability information is transmitted by the terminal device into an uplink codebook subset.
  • This is capability information for defining support, and the capability information of the terminal may include information on at least 2 transmit antenna ports partial-coherent and 4 transmit antenna ports partial-coherent.
  • the terminal device 1 may receive the PDCCH in which the DCI that schedules the PUSCH is arranged.
  • the terminal device 1 may transmit the PUSCH.
  • the terminal device 1 may transmit capability information of the first terminal.
  • the capability information of the first terminal may be capability information for defining support of an uplink codebook subset by the terminal device.
  • the capability information of the first terminal may include information on at least two transmit antenna ports partial-coherent and four transmit antenna ports partial-coherent.
  • the terminal device 1 may transmit capability information of the second terminal.
  • the capability information of the second terminal may be capability information for defining support of an uplink codebook subset by the terminal device.
  • the capability information of the second terminal may include information on at least 2 transmit antenna ports partial-coherent and 4 transmit antenna ports partial-coherent.
  • the terminal device 1 may transmit one or both of the first terminal capability information and the second terminal capability information.
  • the capability information of the first terminal may be push-TransCoherence.
  • the capability information of the first terminal may indicate fully coherent support.
  • the capability information of the first terminal may indicate support for partial coherent.
  • the capability information of the first terminal may indicate non-coherent support.
  • the capability information of the first terminal may indicate support for 4ports partial coherent.
  • the capability information of the first terminal may indicate support for 2ports partial coherent.
  • the capability information of the second terminal may be push-TransCoherence-r18.
  • the capability information of the second terminal may indicate fully coherent support.
  • the capability information of the second terminal may indicate support for partial coherent.
  • the capability information of the second terminal may indicate non-coherent support.
  • the capability information of the second terminal may indicate support for 4ports partial coherent.
  • the capability information of the second terminal may indicate support for 2ports partial coherent.
  • the terminal device 1 receives a PDCCH in which a DCI that schedules a PUSCH is arranged, transmits the PUSCH, and sets a first RRC parameter and a second RRC parameter, and the first RRC parameter is
  • the second RRC parameter is information for determining the number of SRS ports of the SRS resource instructed by the DCI, and the second RRC parameter is information for defining a codebook subset for the PUSCH, and the number of SRS ports is If the number of SRS ports is greater than 4, and the second RRC parameter is the first coherent type, then a first codebook type is selected, and if the number of SRS ports is greater than 4, and the second RRC If the parameter is a second coherent type, a second codebook type is selected, and if the number of SRS ports is greater than 4, and the second RRC parameter is a third coherent type, a second codebook type is selected; If three codebook types are selected and the number of SRS ports is four or less, then the second codebook type is selected for the
  • the terminal device 1 may receive the PDCCH in which the DCI that schedules the PUSCH is arranged.
  • the terminal device 1 may transmit the PUSCH.
  • a first RRC parameter and a second RRC parameter may be set.
  • the first RRC parameter may be information for determining the number of SRS ports of the SRS resource instructed by the DCI.
  • the second RRC parameter may be information for defining a codebook subset for the PUSCH. If the number of SRS ports is greater than 4 and the second RRC parameter is a first coherent type, a first codebook type may be selected. If the number of SRS ports is greater than 4 and the second RRC parameter is a second coherent type, a second codebook type may be selected.
  • a third codebook type may be selected. If the number of SRS ports is 4 or less, the second codebook type may be selected.
  • a precoding matrix for the PUSCH may be determined based at least on the DCI and the selected codebook type.
  • the first RRC parameter may be nrofSRS-Ports.
  • the first RRC parameter may be nrOfAntennaPorts.
  • the second RRC parameter may be codebookSubset.
  • the second RRC parameter may correspond to some or all of full coherent capability, partial coherent capability, and non-coherent capability.
  • the second RRC parameter may be set to fullyAndPartialAndNonCoherent, partialAndNonCoherent, or nonCoherent.
  • the second RRC parameter may be codebookSubset-r18.
  • the second RRC parameter may correspond to some or all of full coherent capability, partial coherent capability, and non-coherent capability.
  • the second RRC parameter may be set to fullyCoherent, partialCoherent, or nonCoherent.
  • the second RRC parameter may be set to fullyCoherent, 4portsPartialCoherent, 2portsPartialCoherent, or nonCoherent.
  • the first coherent type may be one or both of fullyAndPartialAndNonCoherent and fullyCoherent.
  • the second coherent type may be part or all of partialAndNonCoherent, partialCoherent, 4TxPartialCoherent, and 2TxPartialCoherent.
  • the third coherent type may be nonCoherent.
  • the first codebook type is Type I Single-Panel Codebook, Type I Multi-Panel Codebook, TypeII Codebook, Type II Port Selection Codebook, Enhanced Type II Codebook, Enhanced Type II Port Selection Codebook, Further enhanced Type II port selection It may include part or all of the codebook.
  • the first codebook type may be an expression-based codebook determined based on at least i 1 and i 2 .
  • the first codebook type may be a codebook in which i 1 and i 2 are determined according to values of a TPMI field.
  • the first codebook type may be a codebook based on a downlink codebook.
  • the second codebook type may be a table-based codebook determined based on at least some or all of the number of layers, the number of antenna ports, and the settings of transform precoding.
  • the second codebook type may be a codebook determined based on a plurality of TPMIs.
  • the second codebook type may be a codebook based on a combination of multiple codebooks.
  • the second codebook type may be a codebook based on a combination of uplink codebooks used when the number of SRS ports is 4 or less.
  • the third codebook type may be a codebook determined based at least on a vector for selecting ports.
  • the third codebook type may be a codebook consisting only of values of 0 and 1.
  • the third codebook type may be a codebook represented by an identity matrix.
  • a first aspect of the present invention is a terminal device, comprising: a receiving unit that receives a PDCCH in which a DCI that schedules a PUSCH is arranged; and a transmitting unit that transmits the PUSCH;
  • An RRC parameter and a second RRC parameter are set, the first RRC parameter is information for determining the number of SRS ports of the SRS resource instructed by the DCI, and the second RRC parameter is Information for defining a codebook subset for the PUSCH, and if the number of SRS ports is greater than 4 and the second RRC parameter is the first coherent type, the first codebook type is selected and the number of SRS ports is greater than 4, and the second RRC parameter is a second coherent type, a second codebook type is selected and the number of SRS ports is greater than 4.
  • a third codebook type is selected, and if the number of SRS ports is 4 or less, the second codebook type is selected. and determining a precoding matrix for the PUSCH based at least on the DCI and the selected codebook type.
  • the first coherent type is one or both of fullyAndPartialAndNonCoherent and fullyCoherent.
  • the second coherent type is part or all of partialAndNonCoherent, partialCoherent, 4portsPartialCoherent, and 2portsPartialCoherent.
  • the third coherent type is nonCoherent.
  • the first codebook type is Type I Single-Panel Codebook, TypeI Multi-Panel Codebook, TypeII Codebook, Type II Port Selection Codebook, Enhanced Type II Codebook, Enhanced Type II Port Selection Codebook, Further enhancedType II port selection codebook, which is determined based on at least i 1 , i 2 .
  • the second codebook type is a table-based codebook determined based on at least some or all of the number of layers, the number of antenna ports, and the settings of transform precoding.
  • the third codebook type is a codebook determined based on at least a vector for selecting ports.
  • a second aspect of the present invention is a base station device, comprising a transmitter that transmits a PDCCH in which a DCI that schedules a PUSCH is arranged, and a receiver that receives the PUSCH, A first RRC parameter and a second RRC parameter are set, the first RRC parameter is information for determining the number of SRS ports of the SRS resource instructed by the DCI, and the second RRC The parameter is information for defining a codebook subset for the PUSCH, and if the number of SRS ports is greater than 4 and the second RRC parameter is the first coherent type, the first If the number of SRS ports is greater than 4, and the second RRC parameter is a second coherent type, a second codebook type is selected.
  • a third codebook type is selected; Knowing that if the number of SRS ports is 4 or less, the second codebook type is selected, and the precoding matrix for the PUSCH is determined based at least on the DCI and the selected codebook type. Understand what will be decided.
  • the first coherent type is one or both of fullyAndPartialAndNonCoherent and fullyCoherent.
  • the second coherent type is part or all of partialAndNonCoherent, partialCoherent, 4portsPartialCoherent, and 2portsPartialCoherent.
  • the third coherent type is nonCoherent.
  • the first codebook type is Type I Single-Panel Codebook, Type I Multi-Panel Codebook, Type II Codebook, Type II Port Selection Codebook, Enhanced Type II Codebook, Enhanced Type II Port Selection Codebook, Further An expression-based codebook determined based on at least i 1 , i 2 , including part or all of the enhanced Type II port selection codebook.
  • the second codebook type is a table-based codebook determined based on at least some or all of the number of layers, the number of antenna ports, and the settings of transform precoding.
  • the third codebook type is a codebook determined based on at least a vector for selecting ports.
  • a third aspect of the present invention is a communication method used in a terminal device, which includes the steps of receiving a PDCCH in which a DCI that schedules a PUSCH is arranged, and transmitting the PUSCH.
  • a first RRC parameter and a second RRC parameter are set, the first RRC parameter is information for determining the number of SRS ports of the SRS resource instructed by the DCI, and the second The RRC parameter is information for defining a codebook subset for the PUSCH, and if the number of SRS ports is greater than 4, and the second RRC parameter is the first coherent type, If a first codebook type is selected and the number of SRS ports is greater than 4, and if the second RRC parameter is a second coherent type, a second codebook type is selected and the SRS If the number of ports is greater than 4, and the second RRC parameter is a third coherent type, a third codebook type is selected; if the number of SRS ports is less than or equal to 4, the second A codebook type is selected, and a
  • a program running on the base station device 3 and the terminal device 1 related to one aspect of the present invention controls a CPU (Central Processing Unit) etc. so as to realize the functions of the above embodiment related to one aspect of the present invention. It may also be a program (a program that makes a computer function).
  • the information handled by these devices is temporarily stored in RAM (Random Access Memory) during processing, and then stored in various ROMs such as Flash ROM (Read Only Memory) and HDD (Hard Disk Drive). It is read, modified, and written by the CPU as necessary.
  • part of the terminal device 1 and the base station device 3 in the embodiment described above may be realized by a computer.
  • a program for realizing this control function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed.
  • the "computer system” here refers to a computer system built into the terminal device 1 or the base station device 3, and includes hardware such as an OS and peripheral devices.
  • the term “computer-readable recording medium” refers to portable media such as flexible disks, magneto-optical disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into computer systems.
  • a "computer-readable recording medium” refers to a medium that dynamically stores a program for a short period of time, such as a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In that case, it may also include something that retains a program for a certain period of time, such as a volatile memory inside a computer system that is a server or a client. Further, the above-mentioned program may be one for realizing a part of the above-mentioned functions, or may be one that can realize the above-mentioned functions in combination with a program already recorded in the computer system.
  • the base station device 3 in the embodiment described above can also be realized as an aggregate (device group) composed of a plurality of devices.
  • Each of the devices constituting the device group may include a part or all of each function or each functional block of the base station device 3 related to the embodiment described above.
  • As a device group it is sufficient to have each function or each functional block of the base station device 3.
  • the terminal device 1 according to the embodiment described above can also communicate with a base station device as an aggregate.
  • the base station device 3 in the embodiment described above may be EUTRAN (Evolved Universal Terrestrial Radio Access Network) and/or NG-RAN (NextGen RAN, NR RAN). Furthermore, the base station device 3 in the embodiment described above may have some or all of the functions of an upper node for eNodeB and/or gNB.
  • EUTRAN Evolved Universal Terrestrial Radio Access Network
  • NG-RAN NextGen RAN, NR RAN
  • the base station device 3 in the embodiment described above may have some or all of the functions of an upper node for eNodeB and/or gNB.
  • part or all of the terminal device 1 and base station device 3 in the embodiments described above may be realized as an LSI, which is typically an integrated circuit, or may be realized as a chipset. Each functional block of the terminal device 1 and the base station device 3 may be individually chipped, or a part or all of them may be integrated into a chip.
  • the method of circuit integration is not limited to LSI, but may be realized using a dedicated circuit or a general-purpose processor. Further, if an integrated circuit technology that replaces LSI emerges due to advances in semiconductor technology, it is also possible to use an integrated circuit based on this technology.
  • a terminal device was described as an example of a communication device, but the present invention is not limited to this, and the present invention is applicable to stationary or non-movable electronic devices installed indoors or outdoors, For example, it can be applied to terminal devices or communication devices such as AV equipment, kitchen equipment, cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household equipment.
  • One embodiment of the present invention is used in, for example, a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), a program, or the like. be able to.
  • a communication device e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device
  • an integrated circuit e.g., a communication chip
  • a program e.g., a program, or the like.
  • Terminal device 3
  • Base station device 10 30
  • Radio transmitting/receiving section 10a 30a Radio transmitting section 10b, 30b
  • Radio receiving section 11 31 Antenna section 12, 32 RF section 13, 33 Baseband section 14, 34
  • Upper layer processing units 15, 35 Medium access control layer processing units 16, 36
  • Search area set 300 Component carrier 301

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Ce dispositif terminal comprend une unité de réception qui reçoit un PDCCH auquel des DCI pour planifier un PUSCH sont attribuées, et une unité de transmission qui transmet le PUSCH, un premier paramètre RRC et un second paramètre RRC étant définis, et une matrice de précodage pour le PUSCH étant déterminée, au moins sur la base des DCI, du premier paramètre RRC et du second paramètre RRC.
PCT/JP2023/027914 2022-08-08 2023-07-31 Dispositif terminal, dispositif de station de base et procédé de communication WO2024034443A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2022125992 2022-08-08
JP2022-125992 2022-08-08

Publications (1)

Publication Number Publication Date
WO2024034443A1 true WO2024034443A1 (fr) 2024-02-15

Family

ID=89851575

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/027914 WO2024034443A1 (fr) 2022-08-08 2023-07-31 Dispositif terminal, dispositif de station de base et procédé de communication

Country Status (1)

Country Link
WO (1) WO2024034443A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021027895A1 (fr) * 2019-08-15 2021-02-18 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé et dispositif de détermination d'un sous-ensemble de livre de codes et équipement utilisateur

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021027895A1 (fr) * 2019-08-15 2021-02-18 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé et dispositif de détermination d'un sous-ensemble de livre de codes et équipement utilisateur

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Physical layer procedures for data (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 38.214, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. V17.2.0, 23 June 2022 (2022-06-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 229, XP052183196 *

Similar Documents

Publication Publication Date Title
JP7156887B2 (ja) 端末装置、基地局装置、および、通信方法
WO2022071171A1 (fr) Dispositif terminal, dispositif de station de base, et procédé de communication
WO2022030479A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
JP2020072425A (ja) 端末装置、基地局装置、および、通信方法
WO2022181597A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
US20230093299A1 (en) Terminal apparatus, base station apparatus, and communication method
JP7245109B2 (ja) 端末装置、基地局装置、および、通信方法
JP2024033020A (ja) 端末装置、基地局装置、および、通信方法
WO2024034443A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2024034441A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2024034447A1 (fr) Dispositif terminal, dispositif station de base et procédé de communication
WO2023190165A1 (fr) Équipement terminal, dispositif de station de base et procédé de communication
WO2024070601A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2024096012A1 (fr) Équipement terminal, dispositif de station de base et procédé de communication
WO2024096105A1 (fr) Dispositif terminal, dispositif de station de base, et procédé de communication
WO2023243529A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2024062952A1 (fr) Dispositif terminal et dispositif de station de base
WO2023243536A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2024029468A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2024096062A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2024062939A1 (fr) Équipement terminal et dispositif de station de base
WO2023188892A1 (fr) Dispositif terminal et dispositif station de base
WO2024084986A1 (fr) Équipement terminal et dispositif de station de base
WO2023100751A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2022215470A1 (fr) Dispositif terminal, dispositif station de base et procédé de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23852415

Country of ref document: EP

Kind code of ref document: A1