JP7390112B2 - Terminal device and communication method - Google Patents

Description

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

Currently, the Third Generation Partnership Project (3GPP) is developing LTE (Long Term Evolution)-Advanced Pro and NR (New Radio) as radio access methods and radio network technologies for fifth generation cellular systems. (Non-Patent Document 1).

Fifth-generation cellular systems include eMBB (enhanced Mobile BroadBand), which achieves high-speed and large-capacity transmission, URLLC (Ultra-Reliable and Low Latency Communication), which realizes low-latency and highly reliable communication, and IoT (Internet of Things). Three possible service scenarios are required: mmTC (massive machine type communication), where a large number of machine type devices are connected.

RP-161214, NTT DOCOMO, “Revision of SI: Study on New Radio Access Technology”, June 2016

An object of the present invention is to provide a terminal device, a base station device, a communication method, and an integrated circuit that enable efficient communication in a wireless communication system as described above.

(1) In order to achieve the above object, aspects of the present invention take the following measures. That is, a communication method for a terminal device according to one aspect of the present invention receives upper layer settings including parameters applied to transmission power control and parameters related to one or more HARQ-ACK codebooks, and performs uplink control. A first HARQ-ACK codebook corresponding to the channel is identified, and transmission power to be applied to transmission of the uplink control channel is determined based on a correction value of the TPC command corresponding to the first HARQ-ACK codebook. calculate.

(2) In addition to the communication method of the first aspect, the first HARQ-ACK codebook includes the format type of the downlink control channel, the downlink control It is specified by the RNTI applied to CRC scrambling of the channel, the value of a specific field on the downlink control channel, and the identifier or search space type of the control resource set for detecting the downlink control channel.

(3) Furthermore, the communication method of the base station device in one aspect of the present invention provides the terminal device with upper layer settings including parameters applied to transmission power control and parameters related to one or more HARQ-ACK codebooks. transmit, identify a first HARQ-ACK codebook corresponding to an uplink control channel, and specify the transmission power to be applied to transmission of the uplink control channel using a TPC command corresponding to the first HARQ-ACK codebook. Receives an uplink control channel that is calculated based on the correction value of and performs power control.

(4) The terminal device according to one aspect of the present invention also includes a receiving unit that receives upper layer settings including parameters applied to transmission power control and parameters related to one or more HARQ-ACK codebooks; A first HARQ-ACK codebook corresponding to an uplink control channel is specified, and the transmission power to be applied to transmission of the uplink control channel is determined by a correction value of the TPC command corresponding to the first HARQ-ACK codebook. and a transmitter that performs power control based on the calculation.

(5) In addition, the base station device in one aspect of the present invention transmits upper layer settings including parameters applied to transmission power control and parameters related to one or more HARQ-ACK codebooks to the terminal device. and a first HARQ-ACK codebook corresponding to the uplink control channel, and specify the transmission power to be applied to transmission of the uplink control channel using a TPC command corresponding to the first HARQ-ACK codebook. and a receiving unit that receives an uplink control channel that calculates and performs power control based on the correction value of.

(6) The integrated circuit of the terminal device according to one aspect of the present invention also receives upper layer settings including parameters applied to transmission power control and parameters related to one or more HARQ-ACK codebooks. and specifying a first HARQ-ACK codebook corresponding to an uplink control channel, and specifying a transmission power to be applied to transmission of the uplink control channel using a TPC command corresponding to the first HARQ-ACK codebook. and transmitting means that performs power control based on the correction value.

(7) In addition, the integrated circuit of the base station device in one aspect of the present invention provides the terminal device with upper layer settings including parameters applied to transmission power control and parameters related to one or more HARQ-ACK codebooks. A transmitter to transmit and a first HARQ-ACK codebook corresponding to the uplink control channel are specified, and the transmission power to be applied to the transmission of the uplink control channel is determined corresponding to the first HARQ-ACK codebook. and receiving means for receiving an uplink control channel, which calculates and performs power control based on a correction value of a TPC command.

According to this invention, a base station device and a terminal device can communicate efficiently.

1 is a diagram showing the concept of a wireless communication system according to an embodiment of the present invention. FIG. 3 is a diagram illustrating an example of an SS/PBCH block and an SS burst set according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of a schematic configuration of uplink and downlink slots according to an embodiment of the present invention. FIG. 3 is a diagram showing the relationship in the time domain among subframes, slots, and minislots according to an embodiment of the present invention. FIG. 3 is a diagram illustrating an example of a slot or subframe according to an embodiment of the present invention. FIG. 3 is a diagram showing an example of beamforming according to an embodiment of the present invention. FIG. 3 is a diagram showing an example of TPC command settings according to an embodiment of the present invention. 1 is a schematic block diagram showing the configuration of a terminal device 1 according to an embodiment of the present invention. 1 is a schematic block diagram showing the configuration of a base station device 3 according to an embodiment of the present invention. FIG.

Embodiments of the present invention will be described below.

FIG. 1 is a conceptual diagram of a wireless communication system in this embodiment. In FIG. 1, the wireless communication system includes a terminal device 1A, a terminal device 1B, and a base station device 3. Hereinafter, the terminal device 1A and the terminal device 1B will also be referred to as the terminal device 1.

The terminal device 1 is also referred to as a user terminal, mobile station device, communication terminal, mobile device, terminal, UE (User Equipment), or MS (Mobile Station). The base station device 3 includes a wireless base station device, base station, wireless base station, fixed station, NB (Node B), eNB (evolved Node B), BTS (Base Transceiver Station), BS (Base Station), NR NB ( Also referred to as NR Node B), NNB, TRP (Transmission and Reception Point), and gNB. The base station device 3 may include a core network device. Furthermore, the base station device 3 may include one or more transmission reception points 4. At least some of the functions/processing of the base station device 3 described below may be functions/processing at each transmission/reception point 4 included in the base station device 3. The base station device 3 may serve the terminal device 1 by using one or more cells as a communicable range (communication area) controlled by the base station device 3. Furthermore, the base station device 3 may serve the terminal device 1 by using one or more cells as a communicable range (communication area) controlled by one or more transmission/reception points 4 . Alternatively, one cell may be divided into a plurality of partial areas (Beamed areas), and the terminal device 1 may be served in each partial area. Here, the partial region may be identified based on a beam index used in beamforming or a precoding index.

The wireless communication link from the base station device 3 to the terminal device 1 is referred to as a downlink. The wireless communication link from the terminal device 1 to the base station device 3 is referred to as an uplink.

In FIG. 1, wireless communication between a terminal device 1 and a base station device 3 uses orthogonal frequency division multiplexing (OFDM) including a cyclic prefix (CP), single carrier frequency division multiplexing (SC- Single-Carrier Frequency Division Multiplexing (FDM), Discrete Fourier Transform Spread OFDM (DFT-S-OFDM), and Multi-Carrier Code Division Multiplexing (MC-CDM) are used. Good too.

In addition, in FIG. 1, in wireless communication between the terminal device 1 and the base station device 3, universal filter multi-carrier (UFMC), filtered OFDM (F-OFDM), and window function are used. Multiplied OFDM (Windowed OFDM) and Filter-Bank Multi-Carrier (FBMC) may be used.

Note that in this embodiment, OFDM is used as the transmission method and will be explained using OFDM symbols, but the present invention also includes cases where other transmission methods described above are used.

Further, in FIG. 1, in wireless communication between the terminal device 1 and the base station device 3, the above-described transmission method that does not use CP or uses zero padding instead of CP may be used. Furthermore, CP and zero padding may be added to both the front and rear.

One aspect of this embodiment may operate in carrier aggregation or dual connectivity with Radio Access Technology (RAT) such as LTE and LTE-A/LTE-A Pro. At this time, some or all cells or cell groups, carriers or carrier groups (for example, primary cell (PCell), secondary cell (SCell), primary secondary cell (PSCell), MCG (Master Cell Group) ), SCG (Secondary Cell Group), etc.). It may also be used as a stand-alone device that operates independently. In dual connectivity operation, the SpCell (Special Cell) is a PCell of the MCG or a PSCell of the SCG, depending on whether the MAC (Medium Access Control) entity is associated with the MCG or the SCG, respectively. It is called. Unless it is a dual connectivity operation, SpCell (Special Cell) is called PCell. SpCell (Special Cell) supports PUCCH transmission and contention-based random access.

In this embodiment, one or more serving cells may be configured for the terminal device 1. The configured serving cells may include one primary cell and one or more secondary cells. The primary cell may be the serving cell on which the initial connection establishment procedure was performed, the serving cell that initiated the connection re-establishment procedure, or the cell designated as the primary cell in the handover procedure. good. One or more secondary cells may be configured at the time or after the RRC (Radio Resource Control) connection is established. However, the plurality of configured serving cells may include one primary secondary cell. The primary secondary cell may be one of one or more secondary cells to which the terminal device 1 is configured, and which can transmit control information on the uplink. Further, two types of serving cell subsets, a master cell group and a secondary cell group, may be configured for the terminal device 1. A master cell group may include one primary cell and zero or more secondary cells. A secondary cell group may include one primary secondary cell and zero or more secondary cells.

The wireless communication system of this embodiment may apply TDD (Time Division Duplex) and/or FDD (Frequency Division Duplex). TD for all multiple cells
A D (Time Division Duplex) method or an FDD (Frequency Division Duplex) method may be applied. Furthermore, cells to which the TDD scheme is applied and cells to which the FDD scheme is applied may be aggregated.

In the downlink, a carrier corresponding to a serving cell is referred to as a downlink component carrier (or downlink carrier). In the uplink, a carrier corresponding to a serving cell is referred to as an uplink component carrier (or uplink carrier). In the sidelink, a carrier corresponding to a serving cell is called a sidelink component carrier (or sidelink carrier). A downlink component carrier, an uplink component carrier, and/or a sidelink component carrier are collectively referred to as a component carrier (or carrier).

The physical channel and physical signal of this embodiment will be explained.

In FIG. 1, the following physical channels are used in wireless communication between the terminal device 1 and the base station device 3.

・PBCH (Physical Broadcast CHannel)
・PDCCH (Physical Downlink Control CHannel)
・PDSCH (Physical Downlink Shared CHannel)
・PUCCH (Physical Uplink Control CHannel)
・PUSCH (Physical Uplink Shared CHannel)
・PRACH (Physical Random Access CHannel)

The PBCH is used by the terminal device 1 to broadcast important information blocks (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) containing important system information necessary.

Further, the PBCH (also referred to as a physical broadcast channel) may be used to broadcast a time index within the period of a synchronization signal block (also referred to as an SS/PBCH block). Here, the time index is information indicating the index of the synchronization signal and PBCH within the cell. For example, when transmitting an SS/PBCH block using the assumption of three transmit beams (transmit filter settings, quasi co-location (QCL) regarding receive spatial parameters), within a predetermined period or set may indicate the time order within the cycle. Furthermore, the terminal device may recognize a difference in time index as a difference in transmission beams. The synchronization signal block may include a primary synchronization signal, a secondary synchronization signal, a physical broadcast channel, and a reference signal for demodulating the physical broadcast channel. The primary synchronization signal, the secondary synchronization signal, and the reference signal for demodulating the physical broadcast channel will be described later.

The PDCCH is used to transmit (or carry) downlink control information (DCI) in downlink wireless communication (wireless communication from the base station device 3 to the terminal device 1). Here, one or more DCIs (which may be referred to as DCI formats) are defined for transmission of downlink control information. That is, a field for downlink control information is defined as DCI and mapped to information bits.

For example, the following DCI format may be defined:
・DCI format 0_0
・DCI format 0_1
・DCI format 0_2
・DCI format 1_0
・DCI format 1_1
・DCI format 1_2
・DCI format 2_0
・DCI format 2_1
・DCI format 2_2
・DCI format 2_3

DCI format 0_0 may be used for PUSCH scheduling in a certain serving cell. DCI format 0_0 may include information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation). DCI format 0_0 is an identifier of Radio Network Temporary Identifier (RNTI), Cell-RNTI (C-RNTI), Configured Scheduling (CS)-RNTI), MCS-C-RNTI, and/or T temporary C-NRTI A CRC (Cyclic Redundancy Check) scrambled by either (TC-RNTI) may be added. DCI format 0_0 may be monitored in the common search space or the UE-specific search space.

DCI format 0_1 may be used for PUSCH scheduling in a certain serving cell. DCI format 0_1 includes information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating band part (BWP: BandWidth Part), channel state information (CSI) request, and sounding reference. Signal (SRS: Sounding Reference
eSignal) request and/or information regarding the antenna port. DCI format 0_1 is C-RNTI, CS-RNTI, Semi
A CRC scrambled by either Persistent (SP)-CSI-RNTI and/or MCS-C-RNTI may be added. DCI format 0_1 may be monitored in the UE specific search space.

DCI format 0_2 may be used for PUSCH scheduling in a certain serving cell. DCI format 0_2 may include information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating BWP, CSI request, SRS request, and/or information regarding antenna ports. DCI format 0_2 may include a CRC scrambled by any one of C-RNTI, CSI-RNTI, SP-CSI-RNTI, and/or MCS-C-RNTI among RNTIs. DCI format 0_2 may be monitored in the UE specific search space. DCI format 0_2 may be referred to as DCI format 0_1A, etc.

DCI format 1_0 may be used for PDSCH scheduling in a certain serving cell. DCI format 1_0 may include information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation). Among the identifiers, DCI format 1_0 is C-RNTI, CS-RNTI, MCS-C-RNTI, Paging RNTI (P-RNTI), System Information (SI)-RNTI, Random Access (RA)-RNTI, and/or , TC-RNTI may be added. DCI format 1_0 may be monitored in the common search space or the UE-specific search space.

DCI format 1_1 may be used for PDSCH scheduling in a certain serving cell. DCI format 1_1 includes information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating band portion (BWP), transmission configuration indication (TCI), and/or antenna port. may contain information regarding. The DCI format 1_1 may include a CRC scrambled by any one of the C-RNTI, CS-RNTI, and/or MCS-C-RNTI among the RNTIs. DCI format 1_1 may be monitored in the UE specific search space.

DCI format 1_2 may be used for PDSCH scheduling in a certain serving cell. DCI format 1_2 may include information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating BWP, TCI, and/or information regarding antenna ports. DCI format 1_2 may include a CRC scrambled by any one of the C-RNTI, CS-RNTI, and/or MCS-C-RNTI among the RNTIs. DCI format 1_2 may be monitored in the UE specific search space. DCI format 1_2 may be referred to as DCI format 1_1A, etc.

DCI format 2_0 is used to notify the slot format of one or more slots. The slot format is defined as each OFDM symbol within the slot classified as one of downlink, flexible, and uplink. For example, when the slot format is 28, DDDDDDDDDDDDFU is applied to 14 OFDM symbols in the slot in which slot format 28 is designated. Here, D is a downlink symbol, F is a flexible symbol, and U is an uplink symbol. Note that the slot will be described later.

DCI format 2_1 is used to notify the terminal device 1 of physical resource blocks and OFDM symbols that can be assumed not to be transmitted. Note that this information may be referred to as a preemption instruction (intermittent transmission instruction).

DCI format 2_2 is used for transmitting transmit power control (TPC) commands for PUCCH and PUSCH.

DCI format 2_3 is used to transmit a group of TPC commands for sounding reference signal (SRS) transmission by one or more terminal devices 1. Further, an SRS request may be sent together with the TPC command. Further, an SRS request and a TPC command may be defined in DCI format 2_3 for an uplink without PUSCH and PUCCH, or for an uplink in which SRS transmission power control is not linked to PUSCH transmission power control.

The control resource set (CORESET) in this embodiment will be explained below.

A control resource set (CORESET) is a time and frequency resource for searching downlink control information. The CORESET configuration information includes a CORESET identifier (ControlResourceSetId, CORESET-ID) and information that identifies the CORESET frequency resource. The information element ControlResourceSetId (CORESET identifier) is used to identify a control resource set in a certain serving cell. The CORESET identifier is used between BWPs in a certain serving cell. The CORESET identifier is unique among BWPs in the serving cell. The number of CORESETs in each BWP is limited to 3, including the initial CORESET. In a certain serving cell, the value of the CORESET identifier takes a value from 0 to 11.

DCI for downlink is also referred to as downlink grant or downlink assignment. Here, the DCI for uplink is also referred to as uplink grant or uplink assignment. The CRC (Cyclic Redundancy Check) parity bits added to the DCI format transmitted on one PDCCH are SI-RNTI (System Information-Radio Network Temporary Identifier), P-RNTI (Paging-Radio Network Temporary Identifier), and C-RNTI (System Information-Radio Network Temporary Identifier). Scramble with RNTI (Cell-Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling-Radio Network Temporary Identifier), RA-RNTI (Random Access-Radio Network Temporary Identity), or Temporary C-RNTI be done. SI-RNTI may be an identifier used for broadcasting system information. The P-RNTI may be an identifier used for paging and notification of system information changes. C-RNTI, MCS-C-RNTI, and CS-RNTI are identifiers for identifying terminal devices within a cell. The Temporary C-RNTI is an identifier for identifying the terminal device 1 that transmitted the random access preamble during a contention based random access procedure. C-RNTI (terminal device identifier (identification information)) is used to control PDSCH or PUSCH in one or more slots. CS-RNTI is used to periodically allocate PDSCH or PUSCH resources. MCS-C-RNTI is used to indicate the use of a predetermined MCS table for grant-based transmission. Temporary C-RNTI (TC-RNTI) is used to control PDSCH transmission or PUSCH transmission in one or more slots. The Temporary C-RNTI is used to schedule the retransmission of random access message 3 and the transmission of random access message 4. The RA-RNTI is determined according to the frequency and time location information of the physical random access channel that transmitted the random access preamble.

PUCCH is used to transmit uplink control information (UCI) in uplink wireless communication (wireless communication from the terminal device 1 to the base station device 3). Here, the uplink control information may include channel state information (CSI) used to indicate the state of a downlink channel. Further, the uplink control information may include a scheduling request (SR) used for requesting UL-SCH resources. Further, the uplink control information may include part or all of HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement). HARQ-ACK may include a HARQ-ACK bit for downlink data (Transport block, Medium Access Control Protocol Data Unit: MAC PDU, Downlink-Shared Channel: DL-SCH). The HARQ-ACK bit may indicate ACK (acknowledgement) or NACK (negative-acknowledgement) corresponding to one or more transport blocks. That is, the HARQ-ACK bit may correspond to a PDSCH that includes one or more transport blocks. HARQ-ACK may include a HARQ-ACK codebook that includes one or more HARQ-ACK bits. HARQ-ACK is also referred to as HARQ feedback, HARQ information, and HARQ control information. When the HARQ-ACK includes a HARQ-ACK codebook that includes one or more HARQ-ACK bits, the base station device 3 may instruct the terminal to the upper layer parameter pdsch-HARQ-ACK-Codebook.

PDSCH is used for transmitting downlink data (DL-SCH: Downlink Shared CHannel) from a medium access control (MAC) layer. In the case of downlink, it is also used to transmit system information (SI), random access response (RAR), etc.

PUSCH is uplink data from the MAC layer (UL-SCH: Uplink Shared CHannel)
Alternatively, it may be used to transmit HARQ-ACK and/or CSI along with uplink data. Furthermore, it may be used to transmit only CSI or only HARQ-ACK and CSI. That is, it may be used to transmit only the UCI.

Here, the base station device 3 and the terminal device 1 exchange (transmit and receive) signals in a higher layer. For example, the base station device 3 and the terminal device 1 transmit and receive RRC signaling (also referred to as RRC message: Radio Resource Control message, RRC information: Radio Resource Control information) in the radio resource control (RRC) layer. You may. Furthermore, the base station device 3 and the terminal device 1 may transmit and receive MAC control elements in a MAC (Medium Access Control) layer. Here, RRC signaling and/or MAC control element is also referred to as higher layer signaling. The upper layer here means an upper layer seen from the physical layer, and may therefore include one or more of a MAC layer, an RRC layer, an RLC layer, a PDCP layer, a NAS (Non Access Stratum) layer, and the like. For example, in the processing of the MAC layer, the upper layer may include one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, and the like.

PDSCH or PUSCH may be used to transmit RRC signaling and MAC control elements. Here, in the PDSCH, the RRC signaling transmitted from the base station device 3 may be common signaling to a plurality of terminal devices 1 within the cell. Further, the RRC signaling transmitted from the base station device 3 may be dedicated signaling (also referred to as dedicated signaling) for a certain terminal device 1. That is, the terminal device-specific (UE-specific) information may be transmitted to a certain terminal device 1 using dedicated signaling. Furthermore, PUSCH may be used to transmit UE Capability in the uplink.

In FIG. 1, the following downlink physical signals are used in downlink wireless communication. Here, the downlink physical signal is not used to transmit information output from the upper layer, but is used by the physical layer.
・Synchronization signal (SS)
・Reference Signal (RS)

The synchronization signal may include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). Cell ID may be detected using PSS and SSS.

The synchronization signal is used by the terminal device 1 to synchronize the downlink frequency domain and time domain. Here, the synchronization signal may be used by the terminal device 1 for precoding or beam selection in precoding or beamforming by the base station device 3. Note that a beam may also be referred to as a transmit or receive filter setting, or a spatial domain transmit filter or a spatial domain receive filter.

The reference signal is used by the terminal device 1 to perform propagation path compensation for the physical channel. Here, the reference signal may also be used by the terminal device 1 to calculate the downlink CSI. Further, the reference signal may be used for fine synchronization such as numerology such as radio parameters and subcarrier spacing, and window synchronization of FFT.

In this embodiment, one or more of the following downlink reference signals are used.
・DMRS (Demodulation Reference Signal)
・CSI-RS (Channel State Information Reference Signal)
・PTRS (Phase Tracking Reference Signal)
・TRS (Tracking Reference Signal)

DMRS is used to demodulate modulated signals. Note that two types of DMRS may be defined: a reference signal for demodulating PBCH and a reference signal for demodulating PDSCH, and both may be referred to as DMRS. The CSI-RS is used for channel state information (CSI) measurement and beam management, and a periodic, semi-persistent, or aperiodic CSI reference signal transmission method is applied. As the CSI-RS, a non-zero power (NZP) CSI-RS and a zero power (ZP) CSI-RS whose transmission power (or reception power) is zero may be defined. Here, ZP CSI-RS may be defined as a CSI-RS resource with zero transmission power or not transmitted. PTRS is a CSI-RS resource that has zero transmission power or is not transmitted. PTRS is a CSI-RS resource that has zero transmission power or is not transmitted. PTRS is a CSI-RS resource that has zero transmission power or is not transmitted. TRS is used to guarantee Doppler shift during high-speed movement. Note that TRS may be used as one setting for CSI-RS. For example, 1-port CSI-RS is used as TRS. Radio resources may be configured.

In this embodiment, any one or more of the following uplink reference signals are used.
・DMRS (Demodulation Reference Signal)
・PTRS (Phase Tracking Reference Signal)
・SRS (Sounding Reference Signal)

DMRS is used to demodulate modulated signals. Note that two types of DMRS, a reference signal for demodulating PUCCH and a reference signal for demodulating PUSCH, may be defined, and both may be referred to as DMRS. Transmitting both the PUCCH and the DMRS associated with the PUCCH may simply be referred to as transmitting the PUCCH. SRS is used for uplink channel state information (CSI) measurement, channel sounding, and beam management. PTRS is used to track phase in time to account for frequency offsets due to phase noise.

Downlink physical channels and/or downlink physical signals are collectively referred to as downlink signals. Uplink physical channels and/or uplink physical signals are collectively referred to as uplink signals. A downlink physical channel and/or an uplink physical channel are collectively referred to as a physical channel. A downlink physical signal and/or an uplink physical signal are collectively referred to as a physical signal.

BCH, UL-SCH and DL-SCH are transport channels. A channel used in a medium access control (MAC) layer is called a transport channel. The unit of transport channel used in the MAC layer is also referred to as a transport block (TB) and/or a MAC PDU (Protocol Data Unit). HARQ (Hybrid Automatic Repeat reQuest) control is performed for each transport block in the MAC layer. A transport block is a unit of data that the MAC layer delivers to the physical layer. At the physical layer, transport blocks are mapped to codewords, and encoding processing is performed for each codeword.

FIG. 2 is a diagram illustrating an example of an SS/PBCH block (also referred to as a synchronization signal block, SS block, or SSB) and an SS burst set (also referred to as a synchronization signal burst set) according to the present embodiment. FIG. 2 shows an example in which two SS/PBCH blocks are included in an SS burst set that is periodically transmitted, and each SS/PBCH block is composed of 4 OFDM symbols.

The SS/PBCH block is a unit block that includes at least a synchronization signal (PSS, SSS) and/or PBCH. Transmitting the signals/channels included in the SS/PBCH block is expressed as transmitting the SS/PBCH block. When transmitting a synchronization signal and/or PBCH using one or more SS/PBCH blocks in the SS burst set, the base station device 3 may use an independent downlink transmission beam for each SS/PBCH block. good.

In FIG. 2, PSS, SSS, and PBCH are time/frequency multiplexed in one SS/PBCH block. However, the order in which PSS, SSS, and/or PBCH are multiplexed in the time domain may be different from the example shown in FIG. 2 .

The SS burst set may be sent periodically. For example, a cycle to be used for initial access and a cycle to be set for a connected (Connected or RRC_Connected) terminal device may be defined. Further, the cycle set for a connected (Connected or RRC_Connected) terminal device may be set in the RRC layer. Furthermore, the cycle set for a connected (Connected or RRC_Connected) terminal is the cycle of radio resources in the time domain that may potentially transmit, and whether the base station device 3 actually transmits or not. You can decide what to do. Furthermore, the cycle used for initial access may be defined in advance in specifications or the like.

The SS burst set may be determined based on a system frame number (SFN). Further, the starting position (boundary) of the SS burst set may be determined based on the SFN and the cycle.

An SS/PBCH block is assigned an SSB index (which may be referred to as an SSB/PBCH block index) according to its temporal position within the SS burst set. The terminal device 1 calculates an SSB index based on PBCH information and/or reference signal information included in the detected SS/PBCH block.

SS/PBCH blocks having the same relative time within each SS burst set in multiple SS burst sets are assigned the same SSB index. SS/PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assumed to be QCL (or have the same downlink transmission beam applied). Also, antenna ports in SS/PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assumed to be QCL with respect to average delay, Doppler shift, and spatial correlation.

Within a period of a given SS burst set, SS/PBCH blocks that are assigned the same SSB index may be assumed to be QCL with respect to average delay, average gain, Doppler spread, Doppler shift, and spatial correlation. A configuration corresponding to one or more SS/PBCH blocks that are QCL (or may be a reference signal) may be referred to as a QCL configuration.

The number of SS/PBCH blocks (also referred to as the number of SS blocks or the number of SSBs) is, for example, the number of SS/PBCH blocks within an SS burst, or an SS burst set, or within a period of an SS/PBCH block. May be defined. Additionally, the number of SS/PBCH blocks may indicate the number of beam groups for cell selection within an SS burst, within an SS burst set, or within a period of an SS/PBCH block. Here, a beam group may be defined as the number of different SS/PBCH blocks or the number of different beams included within an SS burst, or within an SS burst set, or within a period of an SS/PBCH block.

Hereinafter, the reference signals described in this embodiment include a downlink reference signal, a synchronization signal, an SS/PBCH block, a downlink DM-RS, a CSI-RS, an uplink reference signal, an SRS, and/or an uplink DM-RS. Including RS. For example, a downlink reference signal, a synchronization signal, and/or an SS/PBCH block may be referred to as a reference signal. Reference signals used in the downlink include downlink reference signals, synchronization signals, SS/PBCH blocks, downlink DM-RSs, CSI-RSs, and the like. Reference signals used in uplinks include uplink reference signals, SRSs, and/or uplink DM-RSs.

Further, the reference signal may be used for radio resource measurement (RRM). Additionally, the reference signal may be used for beam management.

Beam management is the process of managing analog and/or digital beams at the transmitting device (base station device 3 in the case of downlink, terminal device 1 in the case of uplink) and the analog and/or digital beams in the transmitting device (base station device 3 in the case of downlink, terminal device 1 in the case of uplink) and the This may be a procedure of the base station device 3 and/or the terminal device 1 to match the directivity of analog and/or digital beams in the base station device 3 (in the case of uplink) and obtain a beam gain.

Note that the procedure for configuring, setting, or establishing a beam pair link may include the following procedure.
・Beam selection
・Beam refinement
・Beam recovery

For example, beam selection may be a procedure for selecting a beam in communication between the base station device 3 and the terminal device 1. Furthermore, the beam improvement may be a procedure of selecting a beam with a higher gain or changing the beam between the base station device 3 and the terminal device 1 to be optimal by moving the terminal device 1. Beam recovery may be a procedure for reselecting a beam when the quality of the communication link is degraded due to blockage caused by obstructions or people passing during communication between the base station device 3 and the terminal device 1.

Beam management may include beam selection, beam improvement. Beam recovery may include the following procedures.
・Detecting beam failures ・Discovering new beams ・Sending beam recovery requests ・Monitoring responses to beam recovery requests

For example, when selecting the transmission beam of the base station device 3 in the terminal device 1, the RSRP (Reference Signal Received Power) of the SSS included in the CSI-RS or the SS/PBCH block may be used, or the CSI may be used. good. Additionally, a CSI-RS Resource Index (CRI) may be used as a report to the base station device 3, and a demodulation index used for demodulating the PBCH and/or PBCH included in the SS/PBCH block may be used. An index indicated by a reference signal (DMRS) sequence may be used.

In addition, the base station device 3 instructs the CRI or SS/PBCH time index when instructing the terminal device 1 to transmit a beam, and the terminal device 1 receives the signal based on the instructed CRI or SS/PBCH time index. do. At this time, the terminal device 1 may set a spatial filter based on the instructed CRI or SS/PBCH time index and receive the signal. Furthermore, the terminal device 1 may receive using the assumption of quasi co-location (QCL). When a signal (antenna port, synchronization signal, reference signal, etc.) is "in QCL" with another signal (antenna port, synchronization signal, reference signal, etc.) or "QCL assumptions are used", it means that a signal is It can be interpreted as being associated with another signal.

Two antenna ports are said to be QCL if the Long Term Property of the channel over which a symbol at one antenna port is carried can be inferred from the channel over which a symbol at another antenna port is carried. . The long-term characteristics of the channel include one or more of delay spread, Doppler spread, Doppler shift, average gain, and average delay. For example, if antenna port 1 and antenna port 2 are QCL with respect to average delay, it means that the reception timing of antenna port 2 can be inferred from the reception timing of antenna port 1.

This QCL can also be extended to beam management. For this purpose, a spatially extended QCL may be newly defined. For example, the long term property of the channel in the spatial domain QCL assumption is the angle of arrival (AoA (Angle of Arrival), ZoA (Zenith angle of Arrival), etc.) and/or angular spread in the wireless link or channel. (Angle Spread, such as ASA (Angle Spread of Arrival) and ZSA (Zenith angle Spread of Arrival)), delivery angle (AoD, ZoD, etc.) and its angular spread (Angle Spread, such as ASD (Angle Spread of Departure) and ZSD ( Zenith angle Spread of Departure), spatial correlation, and reception spatial parameters may be used.

For example, if it can be considered that QCL exists between antenna port 1 and antenna port 2 with respect to reception spatial parameters, the reception beam (reception spatial filter) that receives the signal from antenna port 1 receives the signal from antenna port 2. This means that the beam can be inferred.

As a QCL type, a combination of long-range characteristics that may be considered to be a QCL may be defined. For example, the following types may be defined:
・Type A: Doppler shift, Doppler spread, average delay, delay spread ・Type B: Doppler shift, Doppler spread ・Type C: Average delay, Doppler shift ・Type D: Receiving spatial parameters

The above-mentioned QCL type sets and/or assumes QCL of one or two reference signals and PDCCH or PDSCH DMRS in RRC and/or MAC layer and/or DCI as Transmission Configuration Indication (TCI). You may give instructions. For example, if SS/PBCH block index #2 and QCL type A + QCL type D are set and/or instructed as one state of TCI when terminal device 1 receives PDCCH, terminal device 1 receives PDCCH DMRS. When receiving the SS/PBCH block index #2, the Doppler shift, Doppler spread, average delay, delay spread, reception spatial parameters and long-range characteristics of the channel are considered to be used to receive the DMRS of the PDCCH, and the synchronization and propagation path are determined. You can make an estimate. At this time, the reference signal indicated by the TCI (SS/PBCH block in the above example) is used as the source reference signal, and the reference signal is a reference signal that is influenced by the long-term characteristics inferred from the long-term characteristics of the channel when receiving the source reference signal. The signal (PDCCH DMRS in the above example) may be referred to as a target reference signal. Further, the TCI may be configured with a plurality of TCI states and a combination of a source reference signal and a QCL type for each state in RRC, and may be instructed to the terminal device 1 by the MAC layer or DCI.

With this method, operations of the base station device 3 and terminal device 1 that are equivalent to beam management are defined by assuming QCL in the spatial domain and radio resources (time and/or frequency) as beam management and beam instructions/reports. good.

Similarly, as a setting regarding uplink QCL assumption, spatial relation information (SpatialRelationInfo) may be set for the uplink physical channel and/or the sounding reference signal. The spatial relationship information is information for applying separately applied reception or transmission filter settings to the transmission filter of the sounding reference signal to obtain a beam gain. In order to specify the separately applied reception or transmission filter settings, a block of synchronization signals, a CSI reference signal, or a sounding reference signal is set as a signal to be received or transmitted. With this method, beam gain can be obtained for uplink physical channels and/or sounding reference signals.

The subframe will be explained below. In this embodiment, it is called a subframe, but it may also be called a resource unit, a radio frame, a time section, a time interval, etc.

FIG. 3 is a diagram showing an example of a schematic configuration of uplink and downlink slots according to the first embodiment of the present invention. Each radio frame is 10ms long. Furthermore, each radio frame is composed of 10 subframes and W slots. Furthermore, one slot is composed of X OFDM symbols. That is, the length of one subframe is 1 ms. The time length of each slot is defined by the subcarrier spacing. For example, when the OFDM symbol subcarrier interval is 15 kHz and NCP (Normal Cyclic Prefix), X=7 or X=14, which are 0.5 ms and 1 ms, respectively. Furthermore, when the subcarrier interval is 60 kHz, X=7 or X=14, which are 0.125 ms and 0.25 ms, respectively. Further, for example, when X=14, when the subcarrier interval is 15 kHz, W=10, and when the subcarrier interval is 60 kHz, W=40. FIG. 3 shows the case where X=7 as an example. Note that this can be similarly extended to the case where X=14. Further, uplink slots may be defined similarly, and downlink slots and uplink slots may be defined separately. Further, the bandwidth of the cell in FIG. 3 may be defined as a part of the band (BWP: BandWidth Part). Further, a slot may be defined as a transmission time interval (TTI). A slot may not be defined as a TTI. The TTI may be a transport block transmission period.

The signals or physical channels transmitted in each of the slots may be represented by a resource grid. A resource grid is defined by multiple subcarriers and multiple OFDM symbols. The number of subcarriers constituting one slot depends on the downlink and uplink bandwidths of the cell, respectively. Each element within the resource grid is referred to as a resource element. Resource elements may be identified using subcarrier numbers and OFDM symbol numbers.

A resource grid is used to express the mapping of resource elements of a certain physical downlink channel (such as PDSCH) or uplink channel (such as PUSCH). For example, when the subcarrier interval is 15 kHz, the number of OFDM symbols included in a subframe is X = 14, and in the case of NCP, one physical resource block consists of 14 consecutive OFDM symbols in the time domain and 14 consecutive OFDM symbols in the frequency domain. 12*Nmax consecutive subcarriers. Nmax is the maximum number of resource blocks determined by subcarrier interval setting μ, which will be described later. In other words, the resource grid is composed of (14*12*Nmax, μ) resource elements. In the case of ECP (Extended CP), it is supported only at a subcarrier interval of 60 kHz, and one physical resource block is, for example, 12 (number of OFDM symbols included in 1 slot) * 4 (number of slots included in 1 subframe) in the time domain. number) = 48 consecutive OFDM symbols and 12*Nmax, μ consecutive subcarriers in the frequency domain. In other words, the resource grid is composed of (48*12*Nmax, μ) resource elements.

Common resource blocks, physical resource blocks, and virtual resource blocks are defined as resource blocks. One resource block is defined as 12 consecutive subcarriers in the frequency domain. Subcarrier index 0 in common resource block index 0 may be referred to as a reference point (may be referred to as point A). The common resource blocks are resource blocks that are numbered in ascending order starting from 0 in each subcarrier interval setting μ from the reference point A. The resource grid described above is defined by this common resource block. A physical resource block is a resource block numbered in ascending order from 0 included in a bandwidth part (BWP), which will be described later. It is a numbered resource block. A certain physical uplink channel is first mapped to a virtual resource block. The virtual resource blocks are then mapped to physical resource blocks.

Next, the subcarrier interval setting μ will be explained. As mentioned above, NR supports multiple OFDM numerologies. In a certain BWP, the subcarrier interval setting μ (μ = 0, 1, ..., 5) and the cyclic prefix length are given in the upper layer (upper layer) for the downlink BWP, and It is given in the upper layer in BWP. Here, when μ is given, the subcarrier interval Δf is given by Δf=2^μ·15 (kHz).

In the subcarrier spacing setting μ, slots are counted in ascending order from 0 to N^{subframe,μ}_{slot}-1 within a subframe, and from 0 to N^{frame,μ}_{slot within a frame. }-1 in ascending order. There are N^{slot}_{symb} consecutive OFDM symbols in a slot based on the slot configuration and cyclic prefix. N^{slot}_{symb} is 14. The start of slot n^{μ}_{s} in a subframe is at the same time as the start of the n^{μ}_{s} N^{slot}_{symb}th OFDM symbol in the same subframe. Aligned.

Next, subframes, slots, and minislots will be explained. FIG. 4 is a diagram showing the relationship among subframes, slots, and minislots in the time domain. As shown in the figure, three types of time units are defined. A subframe is 1 ms regardless of the subcarrier interval, the number of OFDM symbols included in a slot is 7 or 14, and the slot length differs depending on the subcarrier interval. Here, when the subcarrier interval is 15 kHz, one subframe includes 14 OFDM symbols. The downlink slot may be referred to as PDSCH mapping type A. The uplink slot may be referred to as PUSCH mapping type A.

A minislot (which may also be referred to as a subslot) is a time unit made up of fewer OFDM symbols than the number of OFDM symbols included in the slot. The figure shows, as an example, a case where a minislot is composed of two OFDM symbols. OFDM symbols within a minislot may match the timing of the OFDM symbols that make up the slot. Note that the minimum unit of scheduling may be a slot or a minislot. Also, assigning minislots may be referred to as non-slot-based scheduling. Further, the fact that a mini-slot is scheduled may be expressed as a resource in which the relative time position of the reference signal and the start position of data is fixed. The downlink minislot may be referred to as PDSCH mapping type B. The uplink minislot may be referred to as PUSCH mapping type B.

Uplink minislots may be referred to as PUCCH subslots. One uplink slot may include one or more PUCCH subslots. Further, the number of PUCCH transmissions started in one PUCCH subslot may be at least one for PUCCH used for HARQ-ACK transmission. Further, the unit configuring the HARQ-ACK codebook may be a PUCCH subslot. The number of symbols (length) of PUCCH subslots and/or the number of PUCCH subslots in uplink may be given to each terminal in an upper layer.

FIG. 5 is a diagram showing an example of a slot format. Here, a case where the subcarrier interval is 15 kHz and the slot length is 1 ms is shown as an example. In the figure, D indicates a downlink and U indicates an uplink. As shown in the figure, within a certain time interval (for example, the minimum time interval that must be allocated to one UE in the system),
- May include one or more of downlink symbols, flexible symbols, and uplink symbols. Note that these ratios may be predetermined as a slot format. Alternatively, it may be defined by the number of downlink OFDM symbols included in a slot or the start position and end position in the slot. Furthermore, it may be defined by the number of uplink OFDM symbols or DFT-S-OFDM symbols included in a slot, or the start position and end position in a slot. Note that the fact that a slot is scheduled may be expressed as a resource in which the relative time position of the reference signal and the slot boundary is fixed.

The terminal device 1 may receive a downlink signal or a downlink channel using a downlink symbol or a flexible symbol. The terminal device 1 may transmit uplink signals or downlink channels using uplink symbols or flexible symbols.

FIG. 5A shows a certain time interval (for example, it may also be referred to as the minimum unit of time resources that can be allocated to one UE, or a time unit. Also, a plurality of minimum units of time resources may be bundled together and referred to as a time unit. ), all of which are used for downlink transmission, and FIG. 5(b) shows an example in which uplink scheduling is performed using the first time resource, for example, via PDCCH, and the PDCCH processing delay and downlink are Uplink signals are transmitted via flexible symbols that include uplink switching time and generation of transmission signals. FIG. 5(c) shows that the first time resource is used for transmitting PDCCH and/or downlink PDSCH, processing delay and switching time from downlink to uplink, and gap for generation of transmission signal to PUSCH or PUCCH. It is used for sending. Here, as an example, the uplink signal may be used for transmitting HARQ-ACK and/or CSI, ie, UCI. FIG. 5(d) shows that the first time resource is used for transmitting the PDCCH and/or PDSCH, processing delay and switching time from downlink to uplink, and the uplink PUSCH and/or Or used for PUCCH transmission. Here, as an example, the uplink signal may be used for transmitting uplink data, ie, UL-SCH. FIG. 5(e) is an example in which all channels are used for uplink transmission (PUSCH or PUCCH).

The above-mentioned downlink part and uplink part may be composed of a plurality of OFDM symbols as in LTE.

FIG. 6 is a diagram showing an example of beamforming. A plurality of antenna elements are connected to one transmitter unit (TXRU: Transceiver unit) 50, the phase is controlled by a phase shifter 51 for each antenna element, and the transmission signal is transmitted from the antenna element 52 in any direction. You can direct the beam. Typically, a TXRU may be defined as an antenna port, and only an antenna port may be defined in the terminal device 1. Since the directivity can be directed in any direction by controlling the phase shifter 51, the base station device 3 can communicate with the terminal device 1 using a beam with a high gain.

The band portion (BWP) will be explained below. BWP is also referred to as carrier BWP. BWP may be configured for each of the downlink and uplink. A BWP is defined as a set of contiguous physical resources selected from contiguous subsets of common resource blocks. The terminal device 1 can be configured with up to four BWPs, with one downlink carrier BWP being activated at a certain time. The terminal device 1 can be configured with up to four BWPs, with one uplink carrier BWP being activated at a certain time. In case of carrier aggregation, BWP may be configured in each serving cell. At this time, the fact that one BWP is configured in a certain serving cell may be expressed as no BWP is configured. Furthermore, the fact that two or more BWPs are set may be expressed as BWPs being set.

<MAC entity operation>
In an activated serving cell, there is always one active (activated) BWP. BWP switching for a serving cell is used to activate inactive BWPs and deactivate active BWPs. be done. BWP switching for a certain serving cell is controlled by PDCCH indicating downlink allocation or uplink grant. BWP switching for a certain serving cell may also be controlled by a BWP inactivity timer or by the MAC entity itself at the start of a random access procedure. Upon addition of a SpCell (PCell or PSCell) or activation of an SCell, one BWP is initially active without receiving a PDCCH indicating a downlink assignment or an uplink grant. The initially active BWP may be specified in an RRC message sent from the base station device 3 to the terminal device 1. An active BWP for a certain serving cell is specified by RRC or PDCCH sent from the base station device 3 to the terminal device 1. In an unpaired spectrum (TDD band, etc.), DL BWP and UL BWP are paired, and BWP switching is common for UL and DL. In the active BWP for each activated serving cell in which BWP is configured, the MAC entity of the terminal device 1 applies normal processing. Normal processing includes transmitting UL-SCH, transmitting RACH, monitoring PDCCH, transmitting PUCCH, transmitting SRS, and receiving DL-SCH. In the inactive BWP for each activated serving cell in which BWP is configured, the MAC entity of the terminal device 1 does not transmit UL-SCH, does not transmit RACH, does not monitor PDCCH, does not transmit PUCCH, Do not transmit SRS and do not receive DL-SCH. If a serving cell is deactivated, the active BWP may not exist (eg, the active BWP is deactivated).

<RRC operation>
A BWP information element (IE) included in an RRC message (broadcast system information or information sent in a dedicated RRC message) is used to configure BWP. The RRC message transmitted from the base station device 3 is received by the terminal device 1. For each serving cell, the network (such as the base station device 3) has at least one downlink BWP and one (if the serving cell is configured for uplink) or two (supplementary uplink) At least an initial BWP (initial BWP) including an uplink BWP (for example, when the terminal device 1 is used) is set for the terminal device 1. Furthermore, the network may configure additional uplink BWPs or downlink BWPs for a certain serving cell. BWP settings are divided into uplink parameters and downlink parameters. Further, BWP settings are divided into common parameters and dedicated parameters. Common parameters (BWP uplink common IE, BWP downlink common IE, etc.) are cell-specific. The common parameters of the primary cell's initial BWP are also provided in the system information. For all other serving cells, the network provides common parameters in dedicated signals. A BWP is identified by a BWP ID. The initial BWP has a BWP ID of 0. BWP IDs of other BWPs take values from 1 to 4.

The uplink BWP dedicated parameters include SRS configuration. An uplink BWP corresponding to the dedicated parameters of the uplink BWP is associated with one or more SRSs corresponding to the SRS configuration included in the dedicated parameters of the uplink BWP.

The terminal device 1 may be configured with one primary cell and up to 15 secondary cells.

The random access procedure will be explained below. Random access procedures are classified into two procedures: contention-based (CB) and non-contention-based (non-CB) (which may also be referred to as contention free (CF)). Contention-based random access is also called CBRA, and non-contention-based random access is also called CFRA. The random access procedure is initiated by a PDCCH order, a MAC entity, a beam failure notification from a lower layer, or RRC.

The contention-based random access procedure is initiated by a PDCCH order, a MAC entity, a beam failure notification from a lower layer, or RRC, etc. When a beam failure notification is provided to the MAC entity of the terminal device 1 from the physical layer of the terminal device 1 and a certain condition is satisfied, the MAC entity of the terminal device 1 starts a random access procedure. When a beam failure notification is provided to the MAC entity of the terminal device 1 from the physical layer of the terminal device 1, a procedure for determining whether a certain condition is satisfied and starting a random access procedure is referred to as a beam failure recovery procedure. It's okay. This random access procedure is a random access procedure for beam failure recovery requests. Random access procedures initiated by the MAC entity include random access procedures initiated by a scheduling request procedure. The random access procedure for beam failure recovery request may or may not be considered a random access procedure initiated by the MAC entity. A random access procedure for a beam failure recovery request and a random access procedure initiated by a scheduling request procedure may perform different procedures, so a random access procedure for a beam failure recovery request and a scheduling request procedure are distinguished. You can do it like this. The random access procedure for beam failure recovery request and the scheduling request procedure may be random access procedures initiated by the MAC entity. In some embodiments, a random access procedure initiated by a scheduling request procedure is referred to as a random access procedure initiated by a MAC entity, and a random access procedure for a beam failure recovery request is referred to as a random access procedure initiated by a beam failure notification from a lower layer. It may also be called a procedure. Hereinafter, starting a random access procedure upon receiving a beam failure notification from a lower layer may mean starting a random access procedure for a beam failure recovery request.

At the time of initial access from a state where the terminal device 1 is not connected (communicating) with the base station device 3, and/or while connected to the base station device 3, uplink data or transmission that can be transmitted to the terminal device 1 is transmitted. A contention-based random access procedure is performed, such as during a scheduling request when possible sidelink data occurs. However, the applications of contention-based random access are not limited to these. The occurrence of uplink data that can be transmitted to the terminal device 1 may include that a buffer status report corresponding to the uplink data that can be transmitted is triggered. The fact that uplink data that can be transmitted to the terminal device 1 has occurred may include that a scheduling request that is triggered based on the generation of uplink data that can be transmitted is pending. The occurrence of sidelink data that can be transmitted to the terminal device 1 may include that a buffer status report corresponding to the sidelink data that can be transmitted is triggered. The occurrence of sidelink data that can be transmitted to the terminal device 1 may include that a scheduling request triggered based on the generation of sidelink data that can be transmitted is pending.

The non-contention-based random access procedure may be started when the terminal device 1 receives information from the base station device 3 instructing the start of the random access procedure. The non-contention-based random access procedure may be started when the MAC layer of the terminal device 1 receives notification of beam failure from a lower layer. Non-contention-based random access allows for quick access between the terminal device 1 and the base station device 3 when the base station device 3 and the terminal device 1 are connected but the handover or the transmission timing of the mobile station device is not valid. may be used for uplink synchronization. Non-contention-based random access may be used to send a beam failure recovery request in case a beam failure occurs at the terminal device 1. However, the uses of non-contention-based random access are not limited to these. However, the information instructing the start of the random access procedure is message 0, Msg. 0, NR-PDCCH order, PDCCH order, etc. However, if the random access preamble index specified in message 0 is a predetermined value (for example, when all the bits indicating the index are 0), the terminal device 1 can select the preamble that can be used by the terminal device 1. A contention-based random access procedure may be performed in which one is randomly selected from the set and transmitted.

The terminal device 1 receives random access configuration information via an upper layer before initiating a random access procedure. The random access configuration information includes resources available for preamble transmission, various parameters for preamble transmission (number of transmissions and power settings), information on associated SS/PBCH blocks, or information for determining/setting such information. May be included. However, the random access setting information may include information common within the cell, or may include dedicated information that differs for each terminal. However, part of the random access configuration information may be associated with all SS/PBCH blocks within the SS burst set. However, part of the random access configuration information may be associated with all of the configured one or more CSI-RSs. However, part of the random access configuration information may be associated with one downlink transmission beam (or beam index). However, part of the random access configuration information may be associated with one SS/PBCH block within the SS burst set. However, part of the random access configuration information may be associated with one of the configured one or more CSI-RSs. However, part of the random access configuration information may be associated with one downlink transmission beam (or beam index). However, information associated with one SS/PBCH block, one CSI-RS, and/or one downlink transmission beam includes the corresponding one SS/PBCH block, one CSI-RS, and/or Index information for identifying one downlink transmission beam (for example, it may be an SSB index, a beam index, or a QCL setting index) may be included. However, random access setting information may be set for each SS/PBCH block within the SS burst set, or one random access setting information common to all SS/PBCH blocks within the SS burst set may be set. good. The terminal device 1 receives one or more pieces of random access configuration information via a downlink signal, and each of the one or more pieces of random access configuration information is an SS/PBCH block (CSI-RS or downlink transmission beam). may be associated with The terminal device 1 selects one of the received one or more SS/PBCH blocks (which may be a CSI-RS or a downlink transmission beam), and A random access procedure may be performed using random access configuration information.

The random access procedure when the terminal device 1 receives message 0 from the base station device 3 is realized by transmitting and receiving a plurality of messages between the terminal device 1 and the base station device 3.
<Message 0>
The base station device 3 allocates one or more contention-free random access preambles to the terminal device 1 by downlink dedicated signaling (also referred to as message 0 or Msg0). However, the contention-free random access preamble may be a random access preamble that is not included in the set notified by broadcast signaling. When transmitting a plurality of reference signals, the base station device 3 allocates to the terminal device 1 a plurality of non-contention-based random access preambles corresponding to at least some of the plurality of reference signals. Good too.
Message 0 may be instruction information that instructs the base station device 3 to start a random access procedure from the terminal device 1. Message 0 may be a handover (HO) command generated by the target base station device 3 and transmitted by the source base station device 3 for handover. Message 0 may be an SCG change command sent by the base station device 3 to change the secondary cell group. The handover command and SCG change command are also referred to as synchronization resetting. This synchronization reconfiguration (such as reconfiguration with sync) is sent in an RRC message. Synchronous reconfiguration is used for RRC reconfiguration that involves synchronization to PCell (handover command, etc.) and RRC reconfiguration that involves synchronization to PSCell (SCG change command, etc.). Message 0 may be sent on RRC signals and/or PDCCH. Message 0 sent on the PDCCH may be referred to as a PDCCH order. A PDCCH order may be transmitted on a DCI of a certain DCI format. Message 0 may include information to allocate a non-contention-based random access preamble. The bit information notified in message 0 includes preamble index information, SSB index information, mask index information (also referred to as RACH opportunity index), SUL (Supplemental UpLink) information, BWP index information, and SRI (SRS Resource Indicator). ) information, Reference Signal Selection Indicator, Random Access Configuration Selection Indicator, RS type selection instruction information, Single/Multiple Msg. 1 Transmission Indicator) and/or TCI. Preamble index information is information indicating one or more preamble indexes used to generate a random access preamble. However, when the preamble index information is a predetermined value, the terminal device 1 may randomly select one from one or more random access preambles available in the contention-based random access procedure. The SSB index information is information indicating an SSB index corresponding to any one of one or more SS/PBCH blocks transmitted by the base station device 3. The terminal device 1 that has received the message 0 identifies the group of PRACH opportunities to which the SSB index indicated by the SSB index information is mapped. The SSB index mapped to each PRACH opportunity is determined by the PRACH configuration index and the upper layer parameter SB-perRACH-Occasion and the upper layer parameter cb-preamblePerSSB. Mask index information is information indicating an index of a PRACH opportunity that can be used to transmit a random access preamble. However, the PRACH opportunity indicated by the mask index information may be one specific PRACH opportunity, or may indicate multiple selectable PRACH opportunities, and different indexes may be selected as one PRACH opportunity. Each of the possible PRACH opportunities may be indicated. The mask index information may be information indicating a PRACH opportunity that is part of a group of one or more PRACH opportunities defined by the prach-ConfigurationIndex. However, the mask index information may be information indicating some PRACH opportunities within a group of PRACH opportunities to which a specific SSB index specified by the SSB index information is mapped.
<Message 1>
The terminal device 1 that has received the message 0 transmits the assigned non-contention-based random access preamble via the physical random access channel. This transmitted random access preamble may be referred to as message 1 or Msg1. The random access preamble is configured to notify information to the base station device 3 using a plurality of sequences. For example, when 64 types of sequences are prepared, 6-bit information (which may be ra-PreambleIndex or preamble index) can be shown to the base station device 3. This information is the random access preamble identifier (Random
By monitoring the random access response (message 2) corresponding to this information, the terminal device 1 can identify the message 2 addressed to the terminal device from the base station device 3. A preamble sequence is selected from a preamble sequence set using a preamble index. A procedure for selecting random access resources (including time/frequency resources and/or preamble index) in the MAC layer of the terminal device 1 will be described. The terminal device 1 sets a value for a preamble index (which may be referred to as PREAMBLE_INDEX) of a random access preamble to be transmitted using the following procedure. The terminal device 1 (1) starts a random access procedure by the notification of beam failure from the lower layer, and (2) uses the beam associated with the SS/PBCH block (also referred to as SSB) or CSI-RS in the RRC parameters. random access resources (which may be PRACH opportunities) are provided for non-contention-based random access for failure recovery requests, and (3) RSRP of one or more SS/PBCH blocks or CSI-RS. exceeds a predetermined threshold, selects an SS/PBCH block or CSI-RS whose RSRP exceeds the predetermined threshold, and preambles the ra-PreambleIndex associated with the selected SS/PBCH block. Set to index. The terminal device 1 (1) is provided with ra-PreambleIndex on PDCCH or RRC, (2) the value of the ra-PreambleIndex is not a value indicating a contention-based random access procedure (for example, 0b000000), and (3) RRC The signaled ra-PreambleIndex is set to the preamble index when the SS/PBCH block or CSI-RS is not associated with a random access resource for non-contention-based random access. 0bxxxxxx means a bit string arranged in a 6-bit information field. The terminal device 1 is configured such that (1) SS/PBCH blocks are associated with random access resources for non-contention-based random access in RRC, and (2) RSRP of the associated SS/PBCH blocks is a predetermined threshold value. If one or more SS/PBCH blocks exceeding the predetermined threshold are available, select one of the SS/PBCH blocks for which the RSRP exceeds the predetermined threshold and the SS/PBCH block associated with the selected SS/PBCH block Set ra-PreambleIndex to the preamble index.

The terminal device 1 is configured such that (1) a CSI-RS is associated with a random access resource for non-contention-based random access in RRC, and (2) an RSRP among the associated CSI-RSs exceeds a predetermined threshold. If one or more CSI-RSs are available, select one of the CSI-RSs whose RSRP exceeds the predetermined threshold, and preamble the ra-PreambleIndex associated with the selected CSI-RS. Set to index. If the terminal device 1 does not satisfy any of the above conditions, it performs a contention-based random access procedure. In the contention-based random access procedure, the terminal device 1 selects an SS/PBCH block whose RSRP exceeds a set threshold, and selects a preamble group. If the relationship between the SS/PBCH block and the random access preamble is set, the terminal device 1
Randomly select an ra-PreambleIndex from one or more random access preambles associated with the S/PBCH block and the selected preamble group, and set the selected ra-PreambleIndex to the preamble index. However, the terminal device 1 may perform the contention-based random access procedure when the ra-PreambleIndex indicated by message 0 is a predetermined value (for example, 0b000000). However, if the ra-PreambleIndex indicated by message 0 is a predetermined value (for example, 0b000000), the terminal device 1 randomly selects one random access preamble index from one or more random access preamble indexes available for contention-based random access. may be selected. The base station device 3 may transmit resource settings for each SS/PBCH block and/or resource settings for each CSI-RS to the terminal device 1 in an RRC message. The terminal device 1 receives resource settings for each SS/PBCH block and/or resource settings for each CSI-RS from the base station device 3 using an RRC message. The base station device 3 may transmit mask index information and/or SSB index information to the terminal device 1 in message 0. The terminal device 1 obtains mask index information and/or SSB index information from the base station device 3 in message 0. The terminal device 1 may select a reference signal (SS/PBCH block or CSI-RS) based on a certain condition. The terminal device 1 determines the next available PRACH opportunity based on the mask index information, SSB index information, resource configuration configured by RRC parameters, and the selected reference signal (SS/PBCH block or CSI-RS). May be specified. The MAC entity of the terminal device 1 may instruct the physical layer to transmit the random access preamble using the selected PRACH opportunity. However, if message 0 indicates SRI configuration information, terminal device 1 selects the antenna port and/or uplink transmission beam corresponding to one or more SRS transmission resources indicated in the SRI configuration information. one or more random access preambles.

<Message 2>
The base station device 3 that has received the message 1 generates a random access response including an uplink grant for instructing the terminal device 1 to transmit, and transmits the generated random access response to the terminal device 1 on the DL-SCH. The random access response may be referred to as message 2 or Msg2. The base station device 3 also calculates the transmission timing shift between the terminal device 1 and the base station device 3 from the received random access preamble, and transmits timing advance command information (Timing Advance Command) for adjusting the shift. ) in message 2. Furthermore, the base station device 3 includes in the message 2 a random access preamble identifier corresponding to the received random access preamble. Furthermore, the base station device 3 transmits an RA-RNTI for indicating a random access response addressed to the terminal device 1 that has transmitted the random access preamble, on the downlink PDCCH. The RA-RNTI is determined according to the frequency and time location information of the physical random access channel that transmitted the random access preamble. Here, message 2 (downlink PSCH) may include the index of the uplink transmission beam used for transmitting the random access preamble. In addition, downlink PDCCH and/or message 2 (downlink PSC
H) may be used to transmit information for determining an uplink transmission beam to be used for transmitting message 3. Here, the information for determining the uplink transmission beam used for transmitting message 3 includes information indicating the difference (adjustment, correction) from the precoding index used for transmitting the random access preamble. You may be Further, the random access response may include a transmission power control command (TPC command) indicating a correction value for the power control adjustment value used for the transmission power of message 3.

By transmitting and receiving the plurality of messages as described above, the terminal device 1 can synchronize with the base station device 3 and perform uplink data transmission to the base station device 3.

Hereinafter, slot aggregation transmission (multi-slot transmission) in this embodiment will be explained.

The upper layer parameter push-AggregationFactor is the data (transport block)
This is used to indicate the number of repetition transmissions. The upper layer parameter push-AggregationFactor indicates a value of 2, 4, or 8. The base station device 3 uses an upper layer parameter push-AggregationFactor that indicates the number of repetitions of data transmission.
may be transmitted to the terminal device 1. The base station device 3 uses pushch-AggregationFactor,
It is possible to cause the terminal device 1 to repeat transmission of the transport block a predetermined number of times. The terminal device 1 may receive the upper layer parameter push-AggregationFactor from the base station device 3, and repeat transmission of the transport block using the number of repetitions indicated by the push-AggregationFactor. However, when the terminal device 1 does not receive the push-AggregationFactor from the base station device, the terminal device 1 may consider that the number of repeated transmissions of the transport block is 1. That is, in this case, the terminal device 1 may transmit the transport block scheduled by the PDCCH only once. That is, when the terminal device 1 does not receive push-AggregationFactor from the base station device, it is not necessary to perform slot aggregation transmission (multi-slot transmission) for the transport block scheduled by the PDCCH.

Specifically, the terminal device 1 receives a PDCCH including a DCI format to which a CRC scrambled with C-RNTI and MCS-C-RNTI is added, and transmits a PUSCH scheduled by the PDCCH. good. When the push-AggregationFactor is set in the terminal device 1, the terminal device 1 may transmit the PUSCH N times in N consecutive slots starting from the slot in which the PUSCH is first transmitted. PUSCH transmission (transport block transmission) may be performed once per slot. In other words, the same transport block is transmitted (repeatedly transmitted) only once within one slot. The value of N is indicated by pushch-AggregationFactor. If the push-AggregationFactor is not set in the terminal device 1, the value of N may be 1. The slot in which PUSCH is first transmitted may be given by the slot in which PDCCH is detected, etc. As an example, the following (Equation 2) may be given.

(Math. 2) Floor(n*2 ^μPUSCH /2 ^μPDCCH )+K ₂

In (Equation 2), the function Floor(A) outputs the largest integer that does not exceed A. Here n is P
It is assumed that this is the slot in which the PDCCH that schedules the USCH is detected, μ _PUSCH is the subcarrier interval setting for PUSCH, and μ _PDCCH is the subcarrier interval setting for PDCCH. Further, the value of K ₂ is any one of j, j+1, j+2, or j+3. The value of j is a value specified for the subcarrier spacing of the PUSCH. For example, when the subcarrier spacing to which PUSCH is applied is 15 kHz or 30 kHz, the value of j may be 1 slot. For example, if the subcarrier spacing to which PUSCH is applied is 60 kHz, the value of j may be 2 slots. For example, if the subcarrier spacing to which PUSCH is applied is 120 kHz, the value of j may be 3 slots.

Furthermore, the terminal device 1 may receive settings and/or instructions regarding PUSCH time domain resource allocation. The settings and/or instructions regarding the PUSCH time-domain resource allocation may be an index giving a valid combination of the PUSCH start symbol S and the number L of consecutive allocated symbols, with a start and length indicator SLIV (start and length indicator). Also, the PUSCH time-domain resource allocation given based on the PDCCH that schedules the PUSCH may be applied to N consecutive slots. That is, the same symbol allocation (the same start symbol S and the same number L of consecutively allocated symbols) may be applied to N consecutive slots. The terminal device 1 may repeatedly transmit the transport block over N consecutive slots starting from the slot in which PUSCH is first transmitted. The terminal device 1 may repeatedly transmit transport blocks using the same symbol allocation in each slot. The slot aggregation transmission performed by the terminal device 1 when the upper layer parameter push-AggregationFactor is set may be referred to as first slot aggregation transmission. That is, the upper layer parameter push-AggregationFactor is used to indicate the number of repetition transmissions for the first slot aggregation transmission. The upper layer parameter push-AggregationFactor is also called the first aggregation transmission parameter. Here, the Ceiling function may be used instead of the Floor function in the calculation formula for specifying the slot. The function Ceiling(A) outputs the smallest integer not less than A.

In the first aggregation transmission, the 0th transmission occasion may be in the slot in which the PUSCH is first transmitted. Here, the transmission occasion may be referred to as an uplink period (UL period). The second transmission occasion (1st transmission occasion) may be in the slot following the slot in which PUSCH is first transmitted. The Nth transmission occasion ((N-1)th transmission occasion) may be in the Nth slot from the slot in which the PUSCH is first transmitted. The redundancy version applied to the transmission of a transport block is the (n-1)th transmission occasion of that transport block and the rv indicated by the DCI that schedules the PUSCH. It may be determined based on _{the id} . The sequence of the redundant version is {0, 2, 3, 1}. The variable rv _id is an index into the sequence of redundant versions. The variable is updated modulo 4. The redundant version is used for encoding (rate matching) of transport blocks transmitted on the PUSCH. The redundancy version may be incremented in the order of 0, 2, 3, 1. The repeated transmission of transport blocks may be performed in order of redundancy version.

If at least one symbol in the symbol allocation for a certain transmission occasion is indicated by an upper layer parameter as a downlink symbol, the terminal device 1 may not transmit a transport block in the slot in that transmission occasion. .

In this embodiment, the base station device 3 may transmit the upper layer parameter push-AggregationFactor-r16 to the terminal device 1. The upper layer parameter push-AggregationFactor-r16 may be used to indicate the number of repetition transmissions of data (transport blocks). The upper layer parameter push-AggregationFactor-r16 may be used to indicate the number of repeated transmissions for slot aggregation transmission and/or minislot aggregation transmission. Slot aggregation transmission and mini-slot aggregation transmission will be described later.

In this embodiment, pusch-AggregationFactor-r16 is set to, for example, any value among n1, n2, and n3. The values of n1, n2, and n3 may be 2, 4, or 8, or may be other values. n1, n2, n3 indicate the number of times the transport block is repeatedly transmitted. In other words, pusch-AggregationFactor-r16 may indicate the value of the number of times one repeated transmission is performed. The number of repeated transmissions of a transport block is the number of repeated transmissions within a slot (
N _rep , etc.), the number of repeated transmissions including within a slot and between slots (N _total, etc.), or the number of repeated transmissions between slots (N _total , etc.).
Alternatively, the base station device 3 may transmit push-AggregationFactor-r16 including more than one element to the terminal device 1 so that the number of repeated transmissions can be set more flexibly to the terminal device 1. An element (information element, entry) may be used to indicate the number of repeated transmissions of a transport block. That is, pusch-AggregationFactor-r16 may indicate the number of times of multiple repeated transmissions, which is more than one. In this embodiment, the slot aggregation transmission performed by the terminal device 1 when the upper layer parameter push-AggregationFactor-r16 is set may be referred to as second aggregation transmission. That is, the upper layer parameter push-AggregationFactor-r16 may be used to indicate the number of repetition transmissions for at least the second aggregation transmission. The upper layer parameter push-AggregationFactor-r16 is also referred to as a second aggregation transmission parameter. Then, the base station device 3 may indicate any element via a field included in the DCI that schedules the transport block, and notify the terminal device 1 of the number of times the transport block is repeatedly transmitted. The specific procedure will be described later. Furthermore, the base station device 3 may indicate any element via a MAC CE (MAC Control Element) and notify the terminal device 1 of the number of times the transport block is repeatedly transmitted. That is, the base station device 3 may indicate any element via the field included in the DCI and/or the MAC CE, and dynamically notify the terminal device 1 of the number of times of repeated transmission. Applying the dynamic repeat count function to the terminal device 1 may mean that the terminal device 1 is dynamically notified of the repeat transmission count from the base station device 3.

As a first example, the base station device 3 does not need to transmit pushch-AggregationFactor and pushch-AggregationFactor-r16 to the terminal device 1. In other words, pushch-AggregationFactor and pushch-AggregationFactor-r16 do not need to be set in the terminal device 1. In other words, the terminal device 1 may receive from the base station device 3 an RRC message that does not include (do not set) pushch-AggregationFactor and pushch-AggregationFactor-r16. In this case, the terminal device 1 may transmit the PUSCH in the slot given by (Equation 2) as described above. In other words, the number of repeated transmissions of the transport block may be one. In other words, the terminal device 1 does not need to perform slot aggregation transmission and/or mini-slot aggregation transmission.

As mentioned above, if the function when pushch-AggregationFactor-r16 is set is not applied, if pushch-AggregationFactor is set, the first aggregation transmission will be used for PUSCH transmission scheduled by that DCI. may be performed. That is, the terminal device 1 may repeatedly transmit the transport block N times in N consecutive slots. The value of N may be given by pushh-AggregationFactor. The same symbol allocation may be applied in the N slots. Furthermore, in a case where the function when pushch-AggregationFactor-r16 is set is not applied, if pushch-AggregationFactor is not set, PUSCH transmission scheduled by that DCI may be performed once. That is, the terminal device 1 may transmit the transport block once.

As described above, in slot aggregation transmission (slot aggregation transmission in the first aggregation transmission and the second aggregation transmission), one uplink grant may schedule PUSCH repeated transmission twice or more than twice. Each repeat transmission occurs in each consecutive slot (or each available slot). In other words, in slot aggregation, the same transport block can be repeatedly transmitted only once within one slot (one available slot). The available slots may be slots in which repeated transmissions of transport blocks are actually performed.

In minislot aggregation transmission, one uplink grant may schedule two or more PUSCH repetition transmissions. Repeated transmissions may occur within the same slot or over consecutive available slots. For the scheduled PUSCH repeat transmission, the number of repeat transmissions performed within each slot may be different based on the symbols available for PUSCH repeat transmission within the slot (available slots). That is, in minislot aggregation transmission, the same transport block may be repeatedly transmitted once or more than once within one slot (one available slot). That is, in minislot aggregation transmission, the terminal device 1 can repeatedly transmit the same transport block one or more times to the base station device 3 within one slot. In other words, minislot aggregation transmission can also be said to mean a mode that supports intra-slot aggregation. The above-described symbol allocation extensions (start symbol extension and/or symbol number extension) and/or dynamic repetition number may be applied to the minislot aggregation transmission.

In this embodiment, the terminal device 1 performs aggregation transmission on the PUSCH transmission for which the uplink grant is scheduled based at least on (I) upper layer parameters and/or (II) fields included in the uplink grant. or whether any aggregation transmission type applies. The types of aggregation transmissions may include first aggregation transmissions and second aggregation transmissions. As another example, the second aggregation transmission may be divided into slot aggregation transmission and minislot aggregation transmission. That is, the types of aggregation transmissions may include first slot aggregation transmissions (first aggregation transmissions), second slot aggregation transmissions (slot aggregation in second aggregation transmissions), and minislot aggregation transmissions.

In an aspect of the present embodiment, the base station device 3 may notify the terminal device 1 which of slot aggregation transmission and minislot aggregation transmission is to be set using upper layer parameters. Which of slot aggregation transmission and mini-slot aggregation transmission is set may mean which of slot aggregation transmission and mini-slot aggregation transmission is applied. For example, push-AggregationFactor may be used to indicate the number of repeated transmissions of the first aggregation transmission (first slot aggregation transmission). pusch-AggregationFactor-r16 may be used to indicate the number of repeated transmissions of the second slot aggregation transmission and/or minislot aggregation transmission. pusch-AggregationFactor-r16 may be a common parameter for the second slot aggregation transmission and/or the mini-slot aggregation transmission. The upper layer parameter repTxWithinSlot-r16 may be used to indicate minislot aggregation transmission. If the upper layer parameter repTxWithinSlot-r16 is set to valid, the terminal device 1 may assume that minislot aggregation transmission is applied to transport block transmission and may perform minislot aggregation transmission. In other words, if pusch-AggregationFactor-r16 is set in terminal device 1 and repTxWithinSlot-r16 is set (set to valid), terminal device 1 assumes that minislot aggregation transmission is applied. It may be considered. The number of repeated transmissions for minislot aggregation transmission may be indicated by pusch-AggregationFactor-r16. Furthermore, if pushch-AggregationFactor-r16 is set in the terminal device 1 and repTxWithinSlot-r16 is not set, the terminal device 1 may consider that the second slot aggregation transmission is applied. The number of repeated transmissions for the second slot aggregation transmission may be indicated by pusch-AggregationFactor-r16. Further, if pushch-AggregationFactor is set in the terminal device 1 and pushch-AggregationFactor-r16 is not set, the terminal device 1 may consider that the first slot aggregation transmission is applied. Furthermore, if pushch-AggregationFactor and pushch-AggregationFactor-r16 are not set in the terminal device 1, the terminal device 1 may consider that aggregation transmission is not applied and may transmit the PUSCH on which the uplink grant is scheduled once. . In this embodiment, setting an upper layer parameter (for example, repTxWithinSlot-r16) may mean that the upper layer parameter (for example, repTxWithinSlot-r16) is set effectively, or It may also mean that the layer parameter (for example, repTxWithinSlot-r16) is transmitted from the base station device 3. In this embodiment, not setting an upper layer parameter (for example, repTxWithinSlot-r16) may mean that the upper layer parameter (for example, repTxWithinSlot-r16) is set to invalid, or It may also mean that the parameter (for example, repTxWithinSlot-r16) is not transmitted from the base station device 3.

Next, the terminal device 1 further determines which of slot aggregation transmission or minislot aggregation transmission is applied based on the field included in the uplink grant that schedules PUSCH transmission (PUSCH repeated transmission). Good too. As an example, a certain field included in the uplink grant may be used to indicate whether slotted aggregation transmission or minislot aggregation transmission is applied. The field may be 1 bit. Furthermore, the terminal device 1 may determine whether slot aggregation transmission or minislot aggregation transmission is applied based on the field included in the uplink grant transmitted from the base station device 3. The terminal device 1 may determine that slot aggregation transmission is applied when the field indicates 0, and may determine that minislot aggregation transmission is applied when the field indicates 1. .

Further, as an example, the terminal device 1 applies either slot aggregation transmission or minislot aggregation transmission based on the 'Time domain resource assignment' field included in the uplink grant transmitted from the base station device 3. You may decide whether As mentioned above, the 'Time domain resource assignment' field is
Used to indicate CH time domain resource allocation. The terminal device 1 determines whether to perform slot aggregation transmission or minislot aggregation transmission based on whether the number L of consecutively allocated symbols obtained based on the 'Time domain resource assignment' field exceeds a predetermined value. You may decide whether it applies. The terminal device 1 may determine that slot aggregation transmission is applied when the number of symbols L exceeds a predetermined value. Furthermore, the terminal device 1 may determine that minislot aggregation transmission is applied when the number of symbols L does not exceed a predetermined value. The predetermined value may be a value indicated from a parameter of an upper layer. The predetermined value may be a value defined in advance in specifications or the like. For example, the predetermined value may be 7 symbols.

The terminal device 1 may determine N _total . N _total is the total number of times the same transport block scheduled in one uplink grant is repeatedly transmitted (the total number of PUSCHs that are repeatedly transmitted). In other words, N _total is the number of one or more PUSCHs scheduled in one uplink grant. The terminal device 1 may determine N _rep . N _rep is the number of times the same transport block is repeatedly transmitted within a slot (the number of PUSCHs that are repeatedly transmitted). In other words, N _rep is the number of one or more PUSCHs arranged in a slot for one or more PUSCHs scheduled in one uplink grant. The terminal device 1 may determine N _slots . N _slots is the number of slots in which the same transport block scheduled in one uplink grant is repeatedly transmitted. In other words, N _slots is the number of slots used for one or more PUSCHs scheduled in one uplink grant. The terminal device 1 may derive N _total from N _rep and N _slots . The terminal device 1 may derive N _rep from N _total and N _slots . The terminal device 1 is
N _slots may be derived from N _rep and N _total . N _slots may be 1 or 2. N _rep may be a different value between slots. N _rep may be the same value between slots.

The terminal device 1 may be set (provided) with an upper layer parameter frequencyHopping. The upper layer parameter frequencyHopping may be set to either 'intraSlot' or 'interSlot'. When frequencyHopping is set to 'intraSlot', the terminal device 1 may perform PUSCH transmission with intra-slot frequency hopping. In other words, intra-slot frequency hopping is configured for the terminal device 1 when frequencyHopping is set to 'intraSlot' and the value of the 'Frequency hopping flag' field included in the DCI that schedules that PUSCH is set to 1. It may also mean that. When frequencyHopping is set to 'interSlot', the terminal device 1 may perform PUSCH transmission with inter-slot frequency hopping. In other words, inter-slot frequency hopping is configured in the terminal device 1 when frequencyHopping is set to 'interSlot' and the value of the 'Frequency hopping flag' field included in the DCI that schedules that PUSCH is set to 1. It may also mean that. Further, when the base station device 3 does not transmit frequencyHopping to the terminal device 1, the terminal device 1 may perform PUSCH transmission without frequency hopping. That is, not setting frequency hopping to the terminal device 1 may include not transmitting frequencyHopping. Furthermore, the fact that frequency hopping is not set in the terminal device 1 may include that even if frequencyHopping is transmitted, the value of the 'Frequency hopping flag' field included in the DCI that schedules the PUSCH is set to 0. .

In the uplink transmission of this embodiment, the available symbols are those that are indicated as flexible and/or uplink by at least the upper layer parameters TDD-UL-DL-ConfigurationCommon and/or TDD-UL-DL-ConfigDedicated. It's okay. That is, the available symbols are not those indicated as downlink by the upper layer parameters TDD-UL-DL-ConfigurationCommon and/or TDD-UL-DL-ConfigDedicated. The upper layer parameters TDD-UL-DL-ConfigurationCommon and/or TDD-UL-DL-ConfigDedicated are used to determine the uplink/downlink TDD configuration.
However, the available symbols are at least not the symbols indicated by the upper layer parameter ssb-PositionsInBurst. ssb-PositionsInBurst is used to indicate the time domain position of the SS/PBCH block transmitted to the base station device 3. That is, the terminal device 1 knows the position of the symbol in which the SS/PBCH block is transmitted by ssb-PositionsInBurst. The symbols on which SS/PBCH blocks are transmitted may be referred to as SS/PBCH block symbols. That is, the available symbols are not SS/PBCH block symbols.
However, the available symbols are not at least the symbols indicated by pdcch-ConfigSIB1. That is, the available symbols are not the symbols indicated by pdcch-ConfigSIB1 for CORESET of type 0 PDCCH common search space set. pdcch-ConfigSIB1 may be included in the MIB or ServingCellConfigCommon.

The terminal device 1 may receive settings and/or instructions regarding spatial relationship information applied to PUSCH transmission (PUSCH repeated transmission) from the base station device 3. A more specific explanation is given below.

As a first example, when the terminal device 1 receives an uplink grant including an SRI field using upper parameters of settings and/or instructions regarding one or more spatial relationship information received from the base station device, The spatial relationship information to be applied to the n-th repeated transmission of the transport block may be determined as the spatial relationship information set in the SRS resource defined as (SRI _d + n) mod N _srs . Function (A) mod (B) divides A and B and outputs the remainder that cannot be divided. Here, SRI _d indicates the SRI notified in the uplink grant, and N _srs indicates the total number of SRS resources configured in the terminal device 1. In addition, not only when receiving an uplink grant including the SRI field, but also when the terminal device 1 has not received the setting of the upper layer parameter rrc-ConfiguredUplinkGrant, the upper layer parameter including the SRI field (srs-ResourceIndicator) When ConfiguredGrantConfig is received from the base station device, the spatial relationship information applied to the n-th repeated transmission of the transport block is the spatial relationship set in the SRS resource defined as (SRI _d + n) mod N _srs . It may be determined as information.

As a second example, when the terminal device 1 receives an uplink grant that does not include the SRI field, the terminal device 1 uses the upper parameters of the settings and/or instructions regarding one or more spatial relationship information received from the base station device. is (PUCCH _{spatialrelation} + n) mod N _{spatialrelation}
It may be determined as spatial relationship information (PUCCH-SpatialRelationInfo) defined as PUCCH-SpatialRelationInfo. Here, PUCCH _{spatialrelation} indicates spatial relationship information associated with the resource with the smallest ID among one or more PUCCH resources set from the base station device 3, and N _{spatialrelation} indicates the PUCCH- Indicates the total number of SpatialRelationInfo. In addition, not only when receiving an uplink grant that does not include the SRI field, but also when the terminal device 1 receives the setting of the upper layer parameter rrc-ConfiguredUplinkGrant and/or including the SRI field (srs-ResourceIndicator). When the upper layer parameter ConfiguredGrantConfig is received from the base station device, the spatial relationship information to be applied to the n-th repeated transmission of the transport block is defined as the spatial relationship information (PUCCH _{spatialrelation} + n) mod N _{spatialrelation} . PUCCH-SpatialRelationInfo).

As a third example, the terminal device 1 uses upper-level parameters of settings and/or instructions regarding one or more pieces of spatial relationship information received from the base station device, and uses upper-level parameters for repeated transmission of the n-th transport block. When receiving an uplink grant that includes the corresponding SRS Resource Indicator Set but does not include the SRI field, the spatial relationship information to be applied to the n-th repeated transmission of the transport block is set to the SRS Resource Indicator Set configuration information. It may also be determined as spatial relationship information set in the SRS resource determined from. Also, the SRS Resource Indicator Set settings are SRS Resource Indicator Set setting example A in Figure 7.
As shown in , it may be configured as a table of the total number of SRI resources and the size of push-AggregationFactor, and when the terminal device receives an uplink grant that does not include the SRI field, the Even if the spatial relationship information to be applied to repeated transmission is determined from the table as the spatial relationship information set in the SRS resource determined from the combination of the value indicated by the predetermined SRI field and the number of repeated transmissions n of the transport block. good. In addition, not only when receiving an uplink grant that does not include the SRI field, but also when the terminal device 1 receives the setting of the upper layer parameter rrc-ConfiguredUplinkGrant and/or including the SRI field (srs-ResourceIndicator). When receiving the upper layer parameter ConfiguredGrantConfig from the base station device, the spatial relationship information set in the SRS resource determined from the combination of the value indicated by the predetermined SRI field and the number of repeated transmissions n of the transport block from the table. You may decide. Here, the value indicated by the predetermined SRI field may be a value predetermined in the specifications, or may be a value received by the terminal device 1 as a higher-level parameter from the base station device.

As a fourth example, the terminal device 1 uses the higher-level parameters of the settings and/or instructions regarding one or more pieces of spatial relationship information received from the base station device, and uses the higher-level parameters for the n-th repeated transmission of the transport block. When an uplink grant that includes a corresponding SRS Resource Indicator Set but does not include an SRI field is received, the spatial relationship information to be applied to the n-th repeated transmission of the transport block is set in the SRS Resource Indicator Set. It may be determined as spatial relationship information (PUCCH-SpatialRelationInfo) determined from the information. Further, the SRS Resource Indicator Set setting may be set as a table of the total number of PUCCH-SpatialRelationInfo and the size of pushch-AggregationFactor, as shown in SRS Resource Indicator Set setting example B in FIG. When receiving an uplink grant that does not contain uplink grants, the spatial relationship information to be applied to the n-th repeated transmission of the transport block is determined from the table based on the value indicated by the predetermined SRI field and the number n of repeated transmissions of the transport block. It may be determined as spatial relationship information (PUCCH-SpatialRelationInfo) determined from a combination of. In addition, not only when receiving an uplink grant that does not include the SRI field, but also when the terminal device 1 receives the setting of the upper layer parameter rrc-ConfiguredUplinkGrant and/or including the SRI field (srs-ResourceIndicator). When receiving the upper layer parameter ConfiguredGrantConfig from the base station device, the spatial relationship information set in the SRS resource determined from the combination of the value indicated by the predetermined SRI field and the number of repeated transmissions n of the transport block from the table. You may decide. Here, the value indicated by the predetermined SRI field may be a value predetermined in the specifications, or may be a value received by the terminal device 1 as a higher-level parameter from the base station device.

Thereby, the terminal device 1 can perform uplink data transmission to the base station device 3.

Next, a reference for the downlink path loss used for the uplink physical channel and/or the transmission power of the sounding reference signal according to this embodiment will be described.
Note that applying a power adjustment control value obtained by accumulating and calculating correction values obtained from TPC commands received by the terminal device 1 to the transmission power may be referred to as TPC accumulation. Alternatively, the terminal device 1 may use one correction value received immediately before as a power control adjustment value for transmission power without accumulating and calculating correction values obtained from TPC commands, which may be referred to as TPC absolute. .
The downlink path loss is based on the transmission power (transmission power of the base station device 3) of the (downlink) path loss reference (for example, SS/PBCH block or CSI-RS) and the RSRP (measurement result of the path loss reference in the terminal device 1). The terminal device 1 may also calculate it. Here, the path loss reference is a downlink reference signal (for example, SS block or CSI-RS) used as an RSRP measurement object used to calculate path loss in the terminal device 1 configured by the base station device 3. There may be.
The terminal device 1 and the base station device 3 may communicate with each other in a state where the dedicated upper layer setting is not transmitted from the base station device 3 to the terminal device 1. The dedicated upper layer settings include a set of reference signals to be used for PUSCH path loss estimation, a set of reference signals to be used for PUCCH path loss estimation, and a set of reference signals to be used for SRS path loss estimation. Or it may include more than one.
The base station device 3 may transmit an upper layer setting called pathlossReferenceRSToAddModList to the terminal device 1. pathlossReferenceRSToAddModList indicates a set of reference signals to be used for PUSCH path loss estimation. This parameter corresponds to the path loss reference applied to the following PUSCH transmission. The terminal device 1 may receive an upper layer setting called pathlossReferenceRSToAddModList from the base station device 3.
The base station device 3 may include an upper layer setting called pathlossReferenceRS in the PUCCH setting information and transmit it to the terminal device 1. pathlossRe included in PUCCH configuration information
referenceRS indicates a set of reference signals to be used for PUCCH path loss estimation.
This parameter corresponds to the path loss reference applied to the following PUCCH transmission. The terminal device 1 may receive from the base station device 3 an upper layer configuration called pathlossReferenceRS included in the PUCCH configuration information.
The base station device 3 may include an upper layer setting called pathlossReferenceRS in the SRS setting information and transmit it to the terminal device 1. pathlossReferenceRS included in the SRS configuration information indicates a set of reference signals to be used for SRS path loss estimation. This parameter corresponds to the path loss reference applied to the following SRS transmission. The terminal device 1 may receive upper layer settings called pathlossReferenceRS included in the SRS setting information from the base station device 3.

Here, an example of TPC command setting will be explained using FIG. 7. As shown in TPC command setting example A in Figure 7, when the 2-bit TPC command field value is 0, the TPC command is interpreted as -1 dB (1 dB decrease), and similarly when the field value is 1, the TPC command is interpreted as -1 dB (1 dB decrease). None), a field value of 2 may be interpreted as +1 dB (increase by 1 dB), and a field value of 3 may be interpreted as +2 dB (increase by 2 dB). Also, as shown in TPC command setting example B in Figure 7, when the 3-bit TPC command field value is 0, the TPC command is interpreted as -5 dB (5 dB reduction), and similarly, when the field value is 1, - It can also be interpreted as 3dB (3dB reduction). In addition, as shown in TPC command setting example C in FIG. 7, when the 3-bit TPC command field value is 0, the terminal uses the setting values Interpret the TPC command as -XdB (decrease by XdB), and similarly when the field value is 1, -YdB (decrease by YdB),
It may be interpreted as +YdB (increases by YdB) when the field value is 6, and +XdB (increases by XdB) when the field value is 7.

Next, a procedure for applying the correction value obtained from the TPC command to obtain a transmission power control adjustment value to be applied to PUCCH transmission will be described. As shown in Equation 1, the transmission power control value g_{b, f, c}(i, l) at PUCCH transmission opportunity i is applied to the b-th uplink BWP included in the c-th serving cell of the f-th carrier. It may also be expressed as

In (Equation 1), the parameter l is a parameter specified by being linked to the HARQ-ACK codebook, and the details will be described later. In addition, δ_{PUCCH, b, f, c}(m, l) is the correction value obtained from the TPC command at timing m corresponding to candidate C (C_i), and corresponds to the PUCCH transmission as shown in (Equation 1). The transmission power control adjustment value is calculated using the cumulative value of TPC commands received in the interval past the PUCCH transmission opportunity by a predetermined number of symbols K_{PUCCH}(i - i_0)-1 specified from the downlink PDCCH instruction. It may also be calculated. Here, i_0 is the smallest positive integer that is K_{PUCCH}(i) symbols before transmission opportunity i and K_{PUCCH}(i - i_0) symbols before transmission opportunity i - i_0.

Next, the parameter l that is linked and specified in the HARQ-ACK codebook will be explained.

When the terminal device 1 detects the PDSCH schedule based on the DCI, the terminal device 1 may specify the HARQ-ACK codebook based on a plurality of elements. The terminal device 1 may identify the HARQ-ACK codebook based on at least some or all of the following elements (A) to (D).
Element (A): Type of DCI format
Element (B): Type of RNTI that scrambles the CRC added to the DCI
Element (C): Identifier of the CORESET where the DCI is found Element (D): Type of search space where the DCI is found

In element (A), the type of DCI format is any one of DCI format 1_0, DCI format 1_1, DCI format 1_2, and DCI format 2_2.

In element (B), the type of RNTI used to scramble the CRC added to the DCI is SI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, C-RNTI, MCS-C-RNTI, or CS-RNTI. This is one of the RNTIs. Alternatively, it may be an RNTI used to control the PDSCH or PUSCH of data of a given service in one or more slots.

In element (C), the identifier of the CORESET in which the DCI is detected may be a value from 0 to 11.

In element (D), the type of search space in which DCI is detected is a common search space or a UE-specific search space. The common search space includes a type 0 common search space, a type 1 common search space, and a type 2 common search space.

The terminal device 1 identifies the HARQ-ACK codebook based on at least some or all of the elements (A) to (D) described above. Furthermore, the terminal device 1 specifies a parameter l for identifying a transmission power control adjustment value from the specified HARQ-ACK codebook. As an example, l = 0 for codebook A, while l = 1 for codebook B. Alternatively, while l = 0 for codebook A, l = 0 may also be set for codebook B. Alternatively, let l = 0 for codebook A, while l = 1 for codebook B.
and l = 2 for codebook C.

The terminal device 1 performs the PUCC according to (Equation 1) using the parameter l specified as described above.
A transmission power control adjustment value to be applied to H transmission may be calculated. Thereby, the terminal device 1 can perform PUCCH transmission to the base station device 3.

Regarding the path loss reference that the terminal device 1 applies to PUSCH transmission, the base station device 3 instructs the configuration of multiple SS blocks and/or the configuration of the CSI-RS using an upper layer signal (RRC message and/or MAC CE). In this case, the information indicating the path loss reference is information indicating the path loss reference associated with the SRS transmission resource indicated by the SRI information instructed by the base station device 3 in the uplink grant by the terminal device 1. Alternatively, the ID may be set to zero among the settings of a plurality of SS blocks and/or the settings of the CSI-RS instructed by the upper layer signal from the base station device 3, The information may be information indicating a path loss reference associated with the resource with the smallest ID among one or more PUCCH resources configured from the base station device 3, or information indicating the path loss reference included in the random access response. (For example, a reference signal applied as a path loss reference when transmitting message 1 in terminal device 1) may be used. In addition, if the terminal device 1 is not instructed to configure the SS block and/or the CSI-RS by the upper layer signal from the base station device 3, the information indicating the path loss reference is randomly transmitted to the terminal device 1. It may also be a reference signal (SS block and/or CSI-RS) specified through the access procedure. Here, the random access procedure may be initiated due to a specific factor. For example, if the terminal device 1 is not provided with a path loss reference applied to PUSCH transmission from the base station device 3, or before the terminal device 1 is provided with dedicated upper layer settings from the base station device 3, , the terminal device 1 receives reference signal resources from the SS/PBCH block selected at the terminal device 1 through a recently occurring random access procedure that has not been initiated in the PDCCH order triggering a contention-free random access procedure. may be used to calculate the downlink path loss estimate. The above process is performed by the terminal device 1 when the upper layer is configured to calculate the downlink path loss estimation used for transmission power control applied to PUSCH transmission using the downlink reference signal of activated BWP. It's okay. The base station device 3 may perform power control based on the assumption that the terminal device 1 is performing the above processing. Furthermore, the base station device 3 may transmit the upper layer settings so that the terminal device 1 performs the above processing.

Regarding the path loss reference that the terminal device 1 applies to PUCCH transmission, the base station device 3 instructs the configuration of multiple SS blocks and/or the configuration of the CSI-RS using an upper layer signal (RRC message and/or MAC CE). In this case, the information indicating the path loss reference may be information indicating the path loss reference associated with the PUCCH resource by the base station device 3, or information indicating the path loss reference associated with the PUCCH resource by the base station device 3, or the information indicating the path loss reference from the base station device 3. Among the settings of multiple SS blocks and/or the settings of CSI-RS, the ID may be set to zero, or the path loss reference may be associated with a layer signal higher than the base station device 3. The information may be information indicating a path loss reference associated with a resource with the smallest ID among one or more PUCCH resources for a cell configured with . In addition, if the terminal device 1 is not instructed to configure the SS block and/or the CSI-RS by the upper layer signal from the base station device 3, the information indicating the path loss reference is randomly transmitted to the terminal device 1. It may also be a reference signal (SS block and/or CSI-RS) specified through the access procedure. Here, the random access procedure may be initiated due to a specific factor. For example, if the terminal device 1 is not provided with a path loss reference applied to PUCCH transmission from the base station device 3, or before the terminal device 1 is provided with dedicated upper layer settings from the base station device 3, , the terminal device 1 receives reference signal resources from the SS/PBCH block selected at the terminal device 1 through a recently occurring random access procedure that has not been initiated in the PDCCH order triggering a contention-free random access procedure. may be used to calculate the downlink path loss estimate. The above process is performed by the terminal device 1 when the upper layer is configured to use the activated BWP downlink reference signal to calculate the downlink path loss estimation used for transmission power control applied to PUCCH transmission. It's okay. The base station device 3 may perform power control based on the assumption that the terminal device 1 is performing the above processing. Furthermore, the base station device 3 may transmit the upper layer settings so that the terminal device 1 performs the above processing.

Regarding the path loss reference that the terminal device 1 applies to SRS transmission, the base station device 3 instructs the configuration of multiple SS blocks and/or the configuration of the CSI-RS using an upper layer signal (RRC message and/or MAC CE). In this case, the information indicating the path loss reference may be information indicating the path loss reference associated with the SRS transmission resource by the base station device 3, or may be information indicating the path loss reference associated with the SRS transmission resource by the base station device 3, or The information may be information indicating a path loss reference of a cell in which a path loss reference association associated with an SRS transmission resource is set in a layer signal. In addition, if the terminal device 1 is not instructed to configure the SS block and/or the CSI-RS by the upper layer signal from the base station device 3, the information indicating the path loss reference is randomly transmitted to the terminal device 1. It may also be a reference signal (SS block and/or CSI-RS) specified through the access procedure. Here, the random access procedure may be initiated due to a specific factor. For example, if the terminal device 1 is not provided with a path loss reference applied to SRS transmission from the base station device 3, or before the terminal device 1 is provided with dedicated upper layer settings from the base station device 3, , the terminal device 1 receives reference signal resources from the SS/PBCH block selected at the terminal device 1 through a recently occurring random access procedure that has not been initiated in the PDCCH order triggering a contention-free random access procedure. may be used to calculate the downlink path loss estimate. The above process is performed by the terminal device 1 when the upper layer is configured to calculate the downlink path loss estimation used for transmission power control applied to SRS transmission using the activated BWP downlink reference signal. It's okay. The base station device 3 may perform power control based on the assumption that the terminal device 1 is performing the above processing. Furthermore, the base station device 3 may transmit the upper layer settings so that the terminal device 1 performs the above processing.

The transmission power of PUSCH and message 3 used by terminal device 1 depends on the subcarrier interval setting μ, the bandwidth (number of resource blocks) allocated to PUSCH, the reference power of PUSCH, the terminal device-specific power of PUSCH, and the modulation method of PUSCH. The downlink path loss compensation coefficient, the downlink path loss, and the correction value of the PUSCH TPC command are set based on the power offset based on the downlink path loss, the downlink path loss, and the correction value of the PUSCH TPC command. Note that the subcarrier interval setting μ, the PUSCH reference power, the PUSCH terminal device-specific power, and the downlink path loss compensation coefficient are set by the base station device 3 as upper layer settings. Further, these upper layer settings may be configured from the base station device 3 to the terminal device 1 for each type of uplink grant, for each cell, and for each uplink subframe set.

The transmission power of the PUCCH used by the terminal device 1 is determined based on the subcarrier interval setting μ, the bandwidth (number of resource blocks) allocated to the PUCCH, the reference power of the PUCCH, the terminal device-specific power of the PUCCH, and the downlink path loss compensation coefficient. , a power offset based on the PUCCH format, a downlink path loss, and a correction value of the PUCCH TPC command. Note that the subcarrier interval setting μ, the PUCCH reference power, the PUCCH terminal device-specific power, the power offset based on the PUCCH format, and the downlink path loss compensation coefficient are set by the base station device 3 as upper layer settings. Further, these upper layer settings may be set for the terminal device 1 by the base station device 3 for each cell group.

The SRS transmission power used by the terminal device 1 is based on the subcarrier interval setting μ, the bandwidth (number of resource blocks) allocated to the SRS, the SRS reference power, the downlink path loss compensation coefficient, the downlink path loss, the SRS Set based on the correction value of the TPC command. Note that the subcarrier interval setting μ, the SRS reference power, and the downlink path loss compensation coefficient are set by the base station device 3 as upper layer settings. Further, these upper layer settings may be configured from the base station device 3 to the terminal device 1 for each type of uplink grant, for each cell, and for each uplink subframe set.

The terminal device 1 may receive settings and/or instructions regarding the path loss reference applied to PUSCH repeat transmission from the base station device 3. A more specific explanation is shown below.

As an example, when the terminal device 1 receives an uplink grant including an SRI field using the upper parameters of the settings and/or instructions regarding the path loss reference received from the base station device, the terminal device 1 repeats the n-th transport block. The path loss reference applied to the transmission may be determined as a path loss reference defined as (q _{d, sri} + n) mod N _qd . Here, q _d,sri indicates PUSCH-PathlossReferenceRs-Id associated with the SRI notified in the uplink grant, and N _qd indicates the total number of PUSCH-PathlossReferenceRs configured in the terminal device 1. In addition, not only when receiving an uplink grant including the SRI field, but also when the terminal device 1 has not received the setting of the upper layer parameter rrc-ConfiguredUplinkGrant, the upper layer parameter including the SRI field (srs-ResourceIndicator) Even if the path loss reference to be applied to the n-th repeated transmission of the transport block is determined as the path loss reference defined as (q _{d, sri} + n) mod N _qd when ConfiguredGrantConfig is received from the base station device. good. In addition, as a modification of the first example, when an uplink grant including an SRI field is received, the path loss reference to be applied to the transport block that is repeatedly transmitted N times is determined as q _d,sri regardless of n. Good too. As another modification, when applying mini-slot aggregation transmission, the value of n may be the same value between slots within the same slot, and the value of n may be increased during repeated transmission around the slot boundary. It may also be a thing.

Note that the information regarding the relevant path loss reference may be information indicating the path loss reference of the relevant cell, or the information regarding the path loss reference of the cell to which the path loss reference mapping associated with the upper layer signal is set from the base station device 3. It may also be information that indicates.

The power of PUSCH, PUCCH, and SRS is adjusted by the terminal device 1 based on TPC commands corresponding to the respective physical channels.
The base station device 3 may set for the terminal device 1 whether TPC accumulation is performed for each cell, each physical channel, each subframe set, and each SRS resource set. Furthermore, the terminal device 1 may use the PUSCH TPC accumulation as the SRS TPC accumulation.

In this way, the terminal device 1 can appropriately set uplink transmission power based on the path loss reference. As another modification, when one or more PUSCH-PathlossReferenceRs is set, the average value of path losses calculated using the set Rs may be applied, or the minimum or maximum path loss may also be applied.

The configuration of the device in this embodiment will be described below.

FIG. 8 is a schematic block diagram showing the configuration of the terminal device 1 of this embodiment. As illustrated, the terminal device 1 includes a wireless transmitter/receiver 10 and an upper layer processor 14. The radio transmitter/receiver 10 includes an antenna section 11, an RF (Radio Frequency) section 12, and a baseband section 13. The upper layer processing section 14 includes a medium access control layer processing section 15 and a radio resource control layer processing section 16. The wireless transmitter/receiver 10 is also referred to as a transmitter, a receiver, a monitor, or a physical layer processor. The upper layer processing section 14 is also referred to as a measuring section, a selecting section, or a controlling section.

The upper layer processing unit 14 outputs uplink data (which may be referred to as a transport block) generated by a user's operation or the like to the wireless transmitting/receiving unit 10. The upper layer processing unit 14 processes a medium access control (MAC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a radio resource control (Radio resource control) layer. Performs part or all of the Resource Control (RRC) layer processing. The upper layer processing unit 14 may have a function of determining whether to repeatedly transmit the transport block based on the upper layer signal received from the base station device 3. The upper layer processing unit 14 may determine whether to perform the first aggregation transmission and/or the second aggregation transmission based on the upper layer signal received from the base station device 3. The upper layer processing unit 14 performs symbol allocation extension (start symbol extension and/or symbol number extension) for aggregation transmission (second aggregation transmission) based on the upper layer signal received from the base station device 3. It may have the ability to control dynamic repetition times and/or minislot aggregation transmission. The upper layer processing unit 14 may determine whether to perform frequency hopping transmission of the transport block based on the upper layer signal received from the base station device 3. The upper layer processing unit 14 may output frequency hopping information, aggregation transmission information, etc. to the wireless transmitting/receiving unit 10. The upper layer processing unit 14 may have a function of selecting one reference signal from one or more reference signals based on the measured value of each reference signal. The upper layer processing unit 14 may have a function of selecting a PRACH opportunity associated with one selected reference signal from one or more PRACH opportunities. When the bit information included in the information instructing the start of a random access procedure received by the radio transmitting/receiving unit 10 is a predetermined value, the upper layer processing unit 14 performs a 1 It may also have a function of specifying one index from one or more indexes and setting it as the preamble index. The upper layer processing unit 14 may have a function of identifying an index associated with the selected reference signal from among one or more indexes set in RRC, and setting the index as the preamble index. The upper layer processing unit 14 may have a function of determining the next available PRACH opportunity based on the received information (for example, SSB index information and/or mask index information). The upper layer processing unit 14 may have a function of selecting an SS/PBCH block based on received information (for example, SSB index information). The upper layer processing unit uses information indicating a path loss reference indicated by an upper layer signal, and/or SRI information indicated by an uplink grant (for example, information indicating a path loss reference associated with an SRS transmission resource), and / or information on one or more configured PUCCH resources (for example, information indicating a path loss reference associated with the resource with the smallest ID), and / or information on a reference signal applied as a path loss reference when transmitting message 1 , and/or has a function of identifying the reference of the downlink path loss used for the transmission power of the uplink physical channel (PUSCH, PUCCH) and/or the sounding reference signal using the information of the reference number identified through the random access procedure. You may do so. The upper layer processing unit determines the subcarrier interval setting μ set in the upper layer signal, the reference power of the uplink physical channel (PUSCH, PUCCH) and/or the sounding reference signal, the uplink physical channel (PUSCH, PUCCH) and/or It may have a function of specifying the terminal device-specific power of the sounding reference signal and the compensation coefficient of downlink path loss. The upper layer processing unit 14 may have a function of controlling the second number based on the upper layer signal including the first number of repeated transmissions and/or the DCI field including the first number. The first number may be the number of repeated transmissions of the same transport block, including within and between slots. The second number may be the number of repeated transmissions of the same transport block within the slot.

The medium access control layer processing section 15 included in the upper layer processing section 14 performs MAC layer (medium access control layer) processing. The medium access control layer processing unit 15 controls transmission of scheduling requests based on various setting information/parameters managed by the radio resource control layer processing unit 16.

A radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs RRC layer (radio resource control layer) processing. The radio resource control layer processing unit 16 manages various setting information/parameters of its own device. The radio resource control layer processing unit 16 sets various setting information/parameters based on the upper layer signal received from the base station device 3. That is, the radio resource control layer processing unit 16 sets various setting information/parameters based on information indicating the various setting information/parameters received from the base station device 3.

The wireless transmitter/receiver 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The wireless transmitting/receiving unit 10 separates, demodulates, and decodes the signal received from the base station device 3, and outputs the decoded information to the upper layer processing unit 14. The wireless transmitter/receiver 10 generates a transmission signal by modulating and encoding data, and transmits it to the base station device 3. The radio transmitter/receiver 10 outputs the upper layer signal (RRC message), DCI, etc. received from the base station device 3 to the upper layer processor 14 . Furthermore, the wireless transmitter/receiver 10 generates and transmits an uplink signal based on instructions from the upper layer processor 14 . The wireless transmitting/receiving unit 10 may have a function of repeatedly transmitting transport blocks to the base station device 3 based on instructions from the upper layer processing unit 14. The wireless transmitter/receiver 10 may repeatedly transmit the same transport block if repeated transmission of the transport block is set. The number of repeated transmissions may be given based on an instruction from the upper layer processing unit 14. The wireless transmitting/receiving unit 10 is characterized in that it transmits PUSCH by aggregation transmission based on information regarding the first number of repetitions, the first number, and the second number instructed by the upper layer processing unit 14. The wireless transmitter/receiver 10 may have a function of controlling aggregation transmission based on predetermined conditions. Specifically, when the first condition is satisfied and when the second aggregation transmission parameter is set, the radio transmitting/receiving unit 10 continuously transmits transport blocks by applying the same symbol allocation in each slot. The transport block may have a function of repeatedly transmitting the transport block N times in N slots, and transmitting the transport block once when the second aggregation transmission parameter is not set. Here, the value of N is indicated in the second aggregation transmission parameter. Furthermore, the wireless transmitter/receiver 10 may have a function of applying minislot aggregation transmission to transmit the transport block when the second condition is satisfied. The first condition includes at least that the PUSCH mapping type is indicated as type A in the DCI received from the base station device 3. The second condition includes at least that the PUSCH mapping type is indicated as type B in the DCI received from the base station device 3. The radio transmitter/receiver 10 may have a function of receiving one or more reference signals in a certain cell. The wireless transceiver 10 may have a function of receiving information that identifies one or more PRACH opportunities (eg, SSB index information and/or mask index information). The wireless transmitter/receiver 10 may have a function of receiving a signal including instruction information instructing to start a random access procedure. The wireless transmitter/receiver 10 may have a function of receiving information that specifies a predetermined index. The wireless transmitter/receiver 10 may have a function of receiving information specifying the index of the random access preamble. The wireless transmitting/receiving unit 10 may have a function of transmitting a random access preamble using the PRACH opportunity determined by the upper layer processing unit 14.

The RF section 12 converts the signal received via the antenna section 11 into a baseband signal by orthogonal demodulation (down-conversion: down covert), and removes unnecessary frequency components. RF
The section 12 outputs the processed analog signal to the baseband section.

The baseband section 13 converts the analog signal input from the RF section 12 into a digital signal. The baseband section 13 converts the converted digital signal into CP (Cyclic
A fast Fourier transform (FFT) is performed on the signal with the CP removed, and a frequency domain signal is extracted.

The baseband unit 13 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 13 outputs the converted analog signal to the RF section 12.

The RF unit 12 removes extra frequency components from the analog signal input from the baseband unit 13 using a low-pass filter, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 11. do. Furthermore, the RF section 12 amplifies power. Further, the RF unit 12 may have a function of determining the transmission power of the uplink physical channel (PUSCH, PUCCH) and/or the sounding reference signal to be transmitted in the serving cell. The RF section 12 is also referred to as a transmission power control section. The transmission power control unit uses TPC commands and/or parameters (subcarrier interval setting μ, uplink physical channels (PUSCH, PUCCH) and/or or the reference power of the sounding reference signal, the terminal device-specific power of the uplink physical channel (PUSCH, PUCCH)), and/or the function to adjust the transmission power of the uplink signal using the compensation coefficient of the downlink path loss. It's okay.

FIG. 9 is a schematic block diagram showing the configuration of the base station device 3 of this embodiment. As illustrated, the base station device 3 includes a wireless transmitter/receiver 30 and an upper layer processor 34. The radio transmitting/receiving section 30 includes an antenna section 31, an RF section 32, and a baseband section 33. The upper layer processing section 34 includes a medium access control layer processing section 35 and a radio resource control layer processing section 36. The wireless transmitter/receiver 30 is also referred to as a transmitter, a receiver, a monitor, or a physical layer processor. Further, a control section may be separately provided to control the operation of each section based on various conditions. The upper layer processing section 34 is also referred to as a terminal control section.

The upper layer processing unit 34 processes a medium access control (MAC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a radio resource control (Radio resource control) layer. Performs part or all of the Resource Control (RRC) layer processing. The upper layer processing unit 34 may have a function of determining whether to repeatedly transmit the transport block based on the upper layer signal transmitted to the terminal device 1. The upper layer processing unit 34 may determine whether to perform the first aggregation transmission and/or the second aggregation transmission based on the upper layer signal transmitted to the terminal device 1. The upper layer processing unit 34 performs symbol allocation expansion (start symbol expansion and/or symbol number expansion), movement It may also have a function to control the number of target repetitions and/or minislot aggregation transmission. The upper layer processing unit 34 may determine whether to perform frequency hopping transmission of the transport block based on the upper layer signal transmitted to the terminal device 1. The upper layer processing unit 34 may have a function of controlling the second number based on the upper layer signal including the first number of repeated transmissions and/or the DCI field including the first number. The first number may be the number of repeated transmissions of the same transport block, including within and between slots. The second number may be the number of repeated transmissions of the same transport block within the slot. It may have a function of specifying one reference signal from one or more reference signals based on the random access preamble received by the wireless transmitter/receiver 30. The upper layer processing unit 34 may identify a PRACH opportunity to monitor the random access preamble from at least the SSB index information and the mask index information.

The medium access control layer processing unit 35 included in the upper layer processing unit 34 performs MAC layer processing. The medium access control layer processing unit 35 performs processing related to scheduling requests based on various setting information/parameters managed by the radio resource control layer processing unit 36.

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 generates downlink data (transport blocks), system information, RRC messages, MAC CE (Control Element), etc. arranged in the physical downlink shared channel, or acquires them from upper nodes. , wireless transmitter/receiver 30
Output to. Further, the radio resource control layer processing unit 36 manages various setting information/parameters of each terminal device 1. The radio resource control layer processing unit 36 may set various setting information/parameters for each terminal device 1 via upper layer signals. That is, the radio resource control layer processing unit 36 transmits/broadcasts information indicating various setting information/parameters. The radio resource control layer processing unit 36 may transmit/broadcast information for specifying settings of a plurality of reference signals in a certain cell.

When the base station device 3 transmits an RRC message, MAC CE, and/or PDCCH to the terminal device 1, and the terminal device 1 performs processing based on the reception, the base station device 3 transmits the RRC message, MAC CE, and/or PDCCH to the terminal device 1. Processing (controlling the terminal device 1 and the system) is performed assuming that the terminal device 1 and the system are being executed. That is, the base station device 3 sends to the terminal device 1 an RRC message, a MAC CE, and/or a PDCCH that causes the terminal device to perform processing based on the reception thereof.

The wireless transmitter/receiver 30 transmits upper layer signals (RRC messages), DCI, etc. to the terminal device 1 . Furthermore, the wireless transmitting/receiving unit 30 receives an uplink signal transmitted from the terminal device 1 based on an instruction from the upper layer processing unit 34. The wireless transmitting/receiving unit 30 may have a function of receiving repeated transmissions of transport blocks from the terminal device 1 based on instructions from the upper layer processing unit 34. If repeated transmission of a transport block is set, the wireless transmitting/receiving unit 30 receives repeated transmission of the same transport block. The number of repeated transmissions may be given based on an instruction from the upper layer processing unit 34. The wireless transmitting/receiving unit 30 is characterized in that it receives PUSCH through aggregation transmission based on information regarding the first number of repetitions, the first number, and the second number instructed by the upper layer processing unit 34. The wireless transmitter/receiver 30 may have a function of controlling aggregation transmission based on predetermined conditions. Specifically, when the first condition is satisfied and the second aggregation transmission parameter is set, the wireless transmitter/receiver 30 consecutively transmits transport blocks by applying the same symbol allocation in each slot. It has a function of repeatedly receiving the transport block N times in N slots, and receiving the transport block once when the second aggregation transmission parameter is not set. Here, the value of N is indicated in the second aggregation transmission parameter. Further, the wireless transmitter/receiver 30 may have a function of applying minislot aggregation transmission to receive the transport block when the second condition is satisfied. The first condition includes at least that the PUSCH mapping type is indicated as type A in the DCI transmitted to the terminal device 1. The second condition includes at least that the PUSCH mapping type is indicated as type B in the DCI transmitted to the terminal device 1. The wireless transmitter/receiver 30 has a function of transmitting one or more reference signals. Furthermore, the wireless transmitting/receiving unit 30 may have a function of receiving a signal including a beam failure recovery request transmitted from the terminal device 1. The wireless transmitting/receiving unit 30 may have a function of transmitting information (for example, SSB index information and/or mask index information) specifying one or more PRACH opportunities to the terminal device 1. The wireless transmitter/receiver 30 may have a function of transmitting information specifying a predetermined index. The wireless transmitter/receiver 30 may have a function of transmitting information specifying the index of the random access preamble. The wireless transmitting/receiving unit 30 may have a function of monitoring the random access preamble using the PRACH opportunity specified by the upper layer processing unit 34. Some other functions of the wireless transmitter/receiver 30 are the same as those of the wireless transmitter/receiver 10, so description thereof will be omitted. Note that when the base station device 3 is connected to one or more transmitting/receiving points 4, a part or all of the functions of the wireless transmitting/receiving section 30 may be included in each transmitting/receiving point 4.

The upper layer processing unit 34 also transmits (transfers) control messages or user data between the base station devices 3 or between an upper network device (MME, S-GW (Serving-GW)) and the base station device 3. ) or receive. In FIG. 9, other components of the base station device 3 and transmission paths for data (control information) between the components are omitted, but other functions necessary for operating as the base station device 3 are omitted. It is clear that it has a plurality of blocks as constituent elements. For example, the upper layer processing section 34 includes a radio resource management layer processing section and an application layer processing section. Further, the upper layer processing section 34 may have a function of setting a plurality of scheduling request resources corresponding to each of the plurality of reference signals transmitted from the wireless transmitting/receiving section 30.

Note that the "unit" in the figure is an element that realizes the functions and procedures of the terminal device 1 and the base station device 3, which is also expressed by terms such as section, circuit, component device, device, and unit.

Each of the units labeled 10 to 16 included in the terminal device 1 may be configured as a circuit. Each of the units 30 to 36 included in the base station device 3 may be configured as a circuit.

(1) More specifically, the communication method of the terminal device according to the first aspect of the present invention includes an upper layer that includes parameters applied to transmission power control and parameters related to one or more HARQ-ACK codebooks. configuration, identifies a first HARQ-ACK codebook corresponding to an uplink control channel, and determines transmission power to be applied to transmission of the uplink control channel corresponding to the first HARQ-ACK codebook. Calculated based on the correction value of the TPC command.

(2) In addition to the communication method of the first aspect, the communication method of the terminal device according to the second aspect of the present invention includes the first HARQ-ACK codebook that includes the format type of the downlink control channel, the downlink control It is specified by the RNTI applied to CRC scrambling of the channel, the value of a specific field on the downlink control channel, and the identifier or search space type of the control resource set for detecting the downlink control channel.

(3) A communication method for a base station device in the third aspect of the present invention provides a terminal device with upper layer settings including parameters applied to transmission power control and parameters related to one or more HARQ-ACK codebooks. transmit, identify a first HARQ-ACK codebook corresponding to an uplink control channel, and specify the transmission power to be applied to transmission of the uplink control channel using a TPC command corresponding to the first HARQ-ACK codebook. Receives an uplink control channel that is calculated based on the correction value of and performs power control.

(4) The terminal device according to the fourth aspect of the present invention includes a receiving unit that receives upper layer settings including parameters applied to transmission power control and parameters related to one or more HARQ-ACK codebooks; A first HARQ-ACK codebook corresponding to an uplink control channel is specified, and the transmission power to be applied to transmission of the uplink control channel is determined by a correction value of the TPC command corresponding to the first HARQ-ACK codebook. and a transmitter that performs power control based on the calculation.

(5) The base station device according to the fifth aspect of the present invention transmits upper layer settings including parameters applied to transmission power control and parameters related to one or more HARQ-ACK codebooks to the terminal device. and a first HARQ-ACK codebook corresponding to the uplink control channel, and specify the transmission power to be applied to transmission of the uplink control channel using a TPC command corresponding to the first HARQ-ACK codebook. and a receiving unit that receives an uplink control channel that calculates and performs power control based on the correction value of.

(6) The integrated circuit of the terminal device according to the sixth aspect of the present invention receives upper layer settings including parameters applied to transmission power control and parameters related to one or more HARQ-ACK codebooks. and specifying a first HARQ-ACK codebook corresponding to an uplink control channel, and specifying a transmission power to be applied to transmission of the uplink control channel using a TPC command corresponding to the first HARQ-ACK codebook. and transmitting means that performs power control based on the correction value.

(7) The integrated circuit of the base station device in the seventh aspect of the present invention provides the terminal device with upper layer settings including parameters applied to transmission power control and parameters related to one or more HARQ-ACK codebooks. A transmitter to transmit and a first HARQ-ACK codebook corresponding to the uplink control channel are specified, and the transmission power to be applied to the transmission of the uplink control channel is determined corresponding to the first HARQ-ACK codebook. and receiving means for receiving an uplink control channel, which calculates and performs power control based on a correction value of a TPC command.

The program that runs on the device related to the present invention may be a program that controls a central processing unit (CPU) or the like to cause the computer to function so as to realize the functions of the embodiments related to the present invention. Programs or information handled by programs are temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, Hard Disk Drive (HDD), or other storage system.

Note that a program for realizing the functions of the embodiments related to the present invention may be recorded on a computer-readable recording medium. The program recorded on this recording medium may be read into a computer system and executed. The "computer system" herein refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. Furthermore, a "computer-readable recording medium" refers to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or any other computer-readable recording medium. Also good.

Additionally, each functional block or feature of the device used in the embodiments described above may be implemented or executed in an electrical circuit, such as an integrated circuit or multiple integrated circuits. An electrical circuit designed to perform the functions described herein may be a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general purpose processor may be a microprocessor or a conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. Further, if an integrated circuit technology that replaces the current integrated circuit emerges due to advances in semiconductor technology, one or more aspects of the present invention can also use a new integrated circuit based on this technology.

In the embodiments related to the present invention, an example has been described in which the present invention is applied to a communication system composed of a base station device and a terminal device. is also applicable.

Note that the present invention is not limited to the above-described embodiments. Although an example of the device has been described in the embodiment, the present invention is not limited thereto, and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as AV devices, kitchen devices, It can be applied to terminal devices or communication devices such as cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household equipment.

Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to these embodiments, and may include design changes within the scope of the gist of the present invention. Further, the present invention can be modified in various ways within the scope shown in the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also included within the technical scope of the present invention. It will be done. Also included are configurations in which the elements described in each of the above embodiments are replaced with each other and have similar effects.

1 (1A, 1B) Terminal device 3 Base station device 4 Transmission/reception point (TRP)
10 Radio transceiver section 11 Antenna section 12 RF section 13 Baseband section 14 Upper layer processing section 15 Medium access control layer processing section 16 Radio resource control layer processing section 30 Radio transceiver section 31 Antenna section 32 RF section 33 Baseband section 34 Upper layer Processing unit 35 Medium access control layer processing unit 36 Radio resource control layer processing unit 50 Transmission unit (TXRU)
51 Phase shifter 52 Antenna element

Claims (2)

A terminal device,
a control unit that calculates a first transmission power control adjustment value and a second transmission power control adjustment value;
identifying a first HARQ-ACK codebook corresponding to the uplink control channel by a specific field value on the downlink control channel ;
determining the transmission power to be applied to transmission of the uplink control channel based on the first transmission power control adjustment value or the second transmission power control adjustment value;
When the first HARQ-ACK codebook is codebook A, power control is performed on the first HARQ-ACK codebook using the first transmission power control adjustment value,
When the first HARQ-ACK codebook is codebook B, a transmitter that performs power control on the first HARQ-ACK codebook using the second transmission power control adjustment value;
Equipped with
Terminal device. A communication method for a terminal device, the computer of the terminal device:
Calculating a first transmission power control adjustment value and a second transmission power control adjustment value,
identifying a first HARQ-ACK codebook corresponding to the uplink control channel by a specific field value on the downlink control channel;
determining the transmission power to be applied to transmission of the uplink control channel based on the first transmission power control adjustment value or the second transmission power control adjustment value;
When the first HARQ-ACK codebook is codebook A, power control is performed on the first HARQ-ACK codebook using the first transmission power control adjustment value,
When the first HARQ-ACK codebook is codebook B, power control is performed on the first HARQ-ACK codebook using the second transmission power control adjustment value.
Communication method.

Images