WO2023175786A1

WO2023175786A1 - Terminal, wireless communication method, and base station

Info

Publication number: WO2023175786A1
Application number: PCT/JP2022/011983
Authority: WO
Inventors: 祐輝松村; 聡永田; ジンワン; ウェイチースン; ランチン
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2022-03-16
Filing date: 2022-03-16
Publication date: 2023-09-21

Abstract

A terminal according to one aspect of the present disclosure comprises: a reception unit that receives first setting information pertaining to the beta offset for a physical uplink shared channel for one code word, and second setting information pertaining to the beta offset for the physical uplink shared channel for two code words; and a control unit that, on the basis of the second setting information, determines the beta offset for transmission via the physical uplink shared channel for the two code words. According to one aspect of the present disclosure, a UCI on PUSCH transmission for a plurality of code words can be appropriately performed.

Description

Terminal, wireless communication method and base station

The present disclosure relates to a terminal, a wireless communication method, and a base station in a next-generation mobile communication system.

In the Universal Mobile Telecommunications System (UMTS) network, Long Term Evolution (LTE) has been specified for the purpose of higher data rates, lower delays, etc. (Non-Patent Document 1). Additionally, LTE-Advanced (3GPP Rel. 10-14) has been specified for the purpose of further increasing capacity and sophistication of LTE (Third Generation Partnership Project (3GPP) Releases (Rel.) 8 and 9).

Successor systems to LTE (for example, also referred to as 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later) are also being considered. .

In NR, a terminal (user terminal, User Equipment (UE)) uses a physical uplink shared channel (PUSCH) to transmit uplink control information (UCI). ) can be sent. The operation of transmitting UCI on PUSCH is also referred to as UCI on PUSCH.

In the case of UCI on PUSCH, the UE determines the amount of resources (for example, the number of coded modulation symbols per layer) for the transmission of the UCI based on the beta offset. A set of multiple beta offsets may be configured in the UE by higher layer signaling (eg, RRC (Radio Resource Control) signaling).

Rel. 15/16 In NR, the UE transmits one codeword (CW) using one PUSCH. In future wireless communication systems (eg, Rel. 17 NR), it is being considered that the UE will transmit more than one CW using one PUSCH.

However, consideration has not yet been made as to how to set the beta offset for PUSCH that transmits more than one CW. If UCI on PUSCH transmission for multiple CWs is not performed appropriately, there is a risk that throughput may decrease or communication quality may deteriorate.

Therefore, one object of the present disclosure is to provide a terminal, a wireless communication method, and a base station that can appropriately perform UCI on PUSCH transmission for multiple codewords.

A terminal according to an aspect of the present disclosure includes first configuration information regarding a beta offset for a physical uplink shared channel for one codeword and for the physical uplink shared channel for two codewords. second configuration information regarding a beta offset for the two codewords; and a control unit that makes the decision.

According to one aspect of the present disclosure, UCI on PUSCH transmission for multiple codewords can be appropriately performed.

FIG. 1 shows Rel. 15/16 is a diagram illustrating an example of a set of information elements regarding a plurality of beta offsets in NR. FIG. 2 shows Rel. 15/16 is a diagram showing an example of PUSCH configuration information including a beta offset information element in NR. FIG. 3 shows Rel. 15/16 is a diagram showing an example of CG PUSCH setting information including a beta offset information element in NR. FIG. 4 shows an example of the UCI-OnPUSCH information element for UCI on 1 CW PUSCH and the UCI-OnPUSCH information element for UCI on 2 CW PUSCH for the dynamic PUSCH of the first embodiment. It is a diagram. FIG. 5 shows an example of the betaOffsets parameters and scaling parameters for UCI on 1 CW PUSCH and the betaOffsets parameters and scaling parameters for UCI on 2 CW PUSCH regarding the dynamic PUSCH of the first embodiment. show It is a diagram. FIG. 6 is a diagram illustrating an example of UCI-OnPUSCH information elements for UCI on 1 CW PUSCH and UCI on 2 CW PUSCH for dynamic PUSCH of the first embodiment. FIG. 7 shows an example of the betaOffsets parameters and scaling parameters for UCI on 1 CW PUSCH and the betaOffsets parameters and scaling parameters for UCI on 2 CW PUSCH regarding the dynamic PUSCH of the second embodiment. show It is a diagram. FIG. 8 shows the CG-UCI-OnPUSCH information element for UCI on 1 CW PUSCH and the CG-UCI-OnPUSCH information element for UCI on 2 CW PUSCH regarding CG PUSCH of the third embodiment. It is a figure showing an example. FIG. 9 is a diagram illustrating an example of CG-UCI-OnPUSCH information elements for UCI on 1 CW PUSCH and UCI on 2 CW PUSCH for CG PUSCH of the third embodiment. FIG. 10 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. FIG. 11 is a diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 12 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. FIG. 13 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. FIG. 14 is a diagram illustrating an example of a vehicle according to an embodiment.

(beta offset)
In NR, the UE can transmit uplink control information (UCI) using a physical uplink shared channel (PUSCH). The operation of transmitting UCI on PUSCH is also referred to as UCI on PUSCH.

In the case of UCI on PUSCH, the UE determines the amount of resources used for UCI transmission (for example, the number of coded modulation symbols for each layer, the number of resource elements (Resource Elements (RE)), the number of UCI bits, The coding rate of UCI transmitted using the PUSCH may be determined based on the modulation order or the like.

The UE determines the amount of resources (eg, the number of coded modulation symbols per layer) for the transmission of the UCI based on the beta offset. The beta offset is also expressed as β _Offset , and may differ depending on the type or content of UCI (HARQ-ACK, CSI part 1, CSI part 2, etc.). Furthermore, the transmission power of PUSCH including UCI may be determined based on the beta offset.

A set of multiple beta offsets may be configured in the UE by upper layer signaling (for example, RRC (Radio Resource Control) signaling).

Figure 1 shows Rel. 15/16 is a diagram illustrating an example of a set of information elements regarding a plurality of beta offsets in NR. This example is described using Abstract Syntax Notation One (ASN.1) notation (note that this is just an example and is not necessarily a complete description. The same applies to similar drawings that follow).

The information element of the set regarding multiple beta offsets (BetaOffsets information element (BetaOffsets IE)) includes seven parameters indicating the index regarding the beta offsets.

The parameters betaOffsetACK-Index1, betaOffsetACK-Index2, and betaOffsetACK-Index3 indicate the index regarding the beta offset applied when transmitting HARQ-ACK up to 2 bits, up to 11 bits, and larger than 11 bits on the PUSCH, respectively.

The parameters betaOffsetCSI-Part1-Index1 and betaOffsetCSI-Part1-Index2 indicate the index regarding the beta offset applied when transmitting CSI part 1 up to 11 bits and larger than 11 bits on the PUSCH, respectively.

The parameters betaOffsetCSI-Part2-Index1 and betaOffsetCSI-Part2-Index2 indicate the index regarding the beta offset applied when transmitting CSI part 2 up to 11 bits and larger than 11 bits on the PUSCH, respectively.

Based on the type (or content) and number of bits (payload size) of the UCI to be transmitted, the UE refers to one index in one set and determines the corresponding beta offset value. Note that the correspondence between the index and the beta offset value is defined by the standard. The correspondence relationship may differ depending on the contents of the UCI.

In NR, a dynamic beta offset and a semi-static beta offset are defined. When configured with a dynamic beta offset, the UE selects one of up to four offset indices by the beta offset indicator field included in the Downlink Control Information (DCI) format for scheduling the PUSCH. It is specified. The UE uses the beta offsets information element corresponding to the specified offset index to determine the beta offset for the UCI transmitted on the PUSCH.

When the UE is configured with a semi-static beta offset, it determines that the beta offset indicator field included in the DCI format for scheduling the PUSCH is 0 bits. The UE also uses one beta offsets information element configured by RRC to determine the beta offset for the UCI transmitted on the PUSCH.

The Beta Offsets information element regarding the dynamic beta offset or quasi-static beta offset for the PUSCH (which may be referred to as dynamic PUSCH, dynamic scheduling PUSCH, etc.) scheduled according to the DCI format is: It is included in the PUSCH configuration information (PUSCH-Config information element) and configured in the UE. Note that the DCI that schedules PUSCH may be called a dynamic grant, and for example, DCI formats 0_0, 0_1, 0_2, etc. are defined.

FIG. 2 shows Rel. 15/16 is a diagram showing an example of PUSCH configuration information including a beta offset information element in NR.

Rel. The UCI-OnPUSCH information element (UCI-OnPUSCH IE) defined in 15/16 NR may include a betaOffsets parameter (betaOffsets) and a scaling parameter (scaling). If the betaOffsets parameter contains "dynamic", it indicates that dynamic beta offsets are used for DCI formats other than DCI format 0_2, and if it contains "semiStatic", it indicates that dynamic beta offsets are used for DCI formats other than DCI format 0_2. Indicates that a static beta offset is used. "dynamic" includes a BetaOffsets information element of size 4 (ie, four), and "semiStatic" includes one BetaOffsets information element.

The scaling parameter indicates a scaling factor for limiting the number of REs allocated to UCI on PUSCH for DCI formats other than DCI format 0_2. For example, f0p5 corresponds to 0.5.

Rel. The UCI-OnPUSCH-DCI-0-2 information element (UCI-OnPUSCH-DCI-0-2 IE) specified in 16 NR includes the betaOffsets parameter (betaOffsetsDCI-0-2) and the scaling parameter ( scalingDCI-0-2). Regarding the dynamic beta offset, it differs from the UCI-OnPUSCH information element in that a beta offsets information element of size 2 can be set instead of a beta offsets information element of size 4. Depending on this size, the size of the beta offset indicator field included in DCI format 0_2 varies from 1 bit to 2 bits. Note that when a quasi-static beta offset is set, the size of the beta offset indicator field included in DCI format 0_2 is also 0 bits.

Rel. In NR.16, the UE may be configured by an upper layer parameter (pdsch-HARQ-ACK-CodebookList) to generate two HARQ-ACK codebooks. In this case, the UE may be configured with two UCI-OnPUSCH information elements (UCI-OnPUSCH IE) for DCI format 0_1 by a list (UCI-OnPUSCH-ListDCI-0-1-r16). The UE also lists two UCI-OnPUSCH-DCI-0-2 information elements (UCI-OnPUSCH-DCI-0-2 IE) for DCI format 0_2 (UCI-OnPUSCH-ListDCI-0-2-r16). can be set by A first entry in these lists may correspond to a first HARQ-ACK codebook and a second entry may correspond to a second HARQ-ACK codebook.

Note that the first HARQ-ACK codebook is related to the Physical Uplink Control Channel (PUCCH) with a priority index of 0, and the second HARQ-ACK codebook is related to the PUCCH with a priority index of 1. do. The larger the value of the priority index, the higher the priority. The priority will be described later.

Uplink transmission without dynamic grant (PUSCH transmission) is also called configured grant (CG) PUSCH. The actual uplink grant (UL grant) of CG PUSCH is configured by RRC signaling (ConfiguredGrantConfig information element) for type 1 CG PUSCH, and provided by PDCCH (DCI) for type 2 CG PUSCH.

The Beta Offsets information element regarding the dynamic beta offset or quasi-static beta offset for the CG PUSCH is included in the CG PUSCH configuration information (ConfiguredGrantConfig information element) and configured in the UE.

FIG. 3 shows Rel. 15/16 is a diagram showing an example of CG PUSCH setting information including a beta offset information element in NR.

Rel. 15/16 The CG-UCI-OnPUSCH information element (CG-UCI-OnPUSCH IE) specified in NR is the setting (“ one or more BetaOffsets information elements corresponding to "dynamic" or "semiStatic"). If the CG-UCI-OnPUSCH information element contains “dynamic”, it indicates that a dynamic beta offset is used for UCI on CG PUSCH, and if it contains “semiStatic”, it indicates that a semi-static beta offset is used for UCI on CG PUSCH. indicates that a standard beta offset is used. "Dynamic" includes a BetaOffsets information element of size 1 to 4, and "semiStatic" includes one BetaOffsets information element.

Note that "semiStatic" is set for type 1 CG PUSCH. In addition, when “dynamic” is set for type 2 CG PUSCH, the UE can specify one of up to four offset indexes by the beta offset indicator field included in the DCI for CG PUSCH activation. Ru. The UE uses the beta offsets information element corresponding to the specified offset index to determine the beta offset for the UCI transmitted on the CG PUSCH.

Rel. The betaOffset parameter (betaOffsetCG-UCI-r16) for CG-UCI in CG PUSCH specified in 16 NR indicates an index regarding the beta offset when only CG-UCI is transmitted on CG PUSCH. Note that when HARQ-ACK and CG-UCI are transmitted on CG PUSCH, the applied beta offset may be a beta offset for HARQ-ACK.

Note that CG-UCI includes the HARQ Process Number (HPN) field, Redundancy Version (RV) field, New Data Indicator (NDI) field, and Channel Occupancy Time (Channel Occupancy Time (COT) sharing information field may also be included.

(priority)
Rel. In NR 16 and above, multiple levels (eg, two levels) of priority can be set for signals/channels. For example, communication is controlled by setting separate priorities for signals/channels corresponding to different traffic types (also called services, service types, communication types, use cases, etc.) (e.g., transmission control in case of collision) It is assumed that This enables communication control for the same signal/channel based on different priorities depending on the service type and the like.

The priorities are information (e.g. UCI, channel state information (CSI)), channel (Physical Downlink Shared Channel (PDSCH), PUSCH, PUCCH, etc.), reference signal (e.g. CSI-RS, SRS, etc.), and HARQ- It may be set/defined for at least one of the ACK codebooks. Furthermore, different priorities may be set for the PUCCH used for SR transmission, the PUCCH used for HARQ-ACK transmission, and the PUCCH used for CSI transmission.

The priority may be defined as a first priority (for example, high, 1, etc.) and a second priority (for example, low, 0, etc.) that is lower in priority than the first priority. Alternatively, three or more types of priorities may be set. The priority may be expressed by a priority index, and the larger the priority index, the higher the priority.

A high priority may be expressed as high priority (HP), and a low priority may be expressed as low priority (LP). For example, PUSCH with a high priority may be expressed as HP PUSCH, and HARQ-ACK with a low priority may be expressed as LP HARQ-ACK.

Priority is set for HARQ-ACK for dynamically scheduled PDSCH, Semi-persistent scheduling (SPS) HARQ-ACK for PDSCH, SPS HARQ-ACK for PDSCH release Good too. Priorities may be set for HARQ-ACK codebooks corresponding to these HARQ-ACKs. Note that when setting a priority to a PDSCH, the priority of the PDSCH may be replaced with the priority of HARQ-ACK for the PDSCH.

Additionally, priorities may be set for dynamic PUSCH, CG PUSCH, etc.

Information regarding the priority may be notified from the base station to the UE using at least one of upper layer signaling and DCI. For example, the priority of a scheduling request may be set with an upper layer parameter (eg, schedulingRequestPriority). The priority of HARQ-ACK for a PDSCH (eg, dynamic PDSCH) scheduled on a DCI may be notified by the DCI. The priority of HARQ-ACK for SPS PDSCH may be set by a higher-level parameter (for example, HARQ-ACK-Codebook-indicator-forSPS), or may be notified by DCI that instructs activation of SPS PDSCH.

Aperiodic CSI (A-CSI)/Semi-persistent CSI (SP-CSI) transmitted on PUCCH is good. On the other hand, the priority of aperiodic CSI (A-CSI)/SP-CSI transmitted on PUSCH may be notified by DCI (for example, trigger DCI or activation DCI).

The priority of a dynamic grant-based PUSCH may be notified by the priority indicator field of the DCI that schedules the PUSCH. The configuration grant-based PUSCH priority may be configured with an upper layer parameter (eg, priority). A predetermined priority (eg, low) may be set for P-SRS/SP-SRS and A-SRS triggered by DCI (eg, DCI format 0_1/DCI format 2_3).

The UE may control UL transmission based on priority when multiple UL signals/UL channels overlap (or collide).

Multiple UL signals/UL channels overlap when the time resources (or time resources and frequency resources) of multiple UL signals/UL channels overlap, or when the transmission timings of multiple UL signals/UL channels overlap. They may overlap. Time resources may be read as time domain or time domain. The time resource may be in units of symbols, slots, subslots, or subframes.

Overlapping of multiple UL signals/UL channels in the same UE (e.g., intra-UE) means that multiple UL signals/UL channels overlap at least in the same time resource (e.g., symbol). It's okay. Also, collision of UL signals/UL channels in different UEs (e.g., inter-UE) means that multiple UL signals/UL channels overlap in the same time resource (e.g., symbol) and frequency resource (e.g., RB). It can also mean wrapping.

For example, when multiple UL signals/UL channels with the same priority overlap, the UE controls the multiplexed UL signals/UL channels to be multiplexed into one UL channel and transmitted. Good too.

For example, HARQ-ACK (or PUCCH for HARQ-ACK transmission) to which the first priority (high) is set, and UL data/UL-SCH (or , UL data/PUSCH for UL-SCH transmission) overlap, the UE may multiplex (or map) HARQ-ACK onto PUSCH and transmit both UL data and HARQ-ACK.

When multiple UL signals/UL channels with different priorities overlap, the UE performs the UL transmission with the higher priority (e.g., prioritizes the UL transmission with the higher priority) and the UL transmission with the lower priority. It may also be controlled so that it does not occur (for example, it is dropped).

UL data/HARQ-ACK (or UL channel for UL data/HARQ-ACK transmission) to which the first priority (high) is set and UL data/HARQ-ACK to which the second priority (low) is set. If the HARQ-ACKs (or UL channels for UL data/HARQ-ACK transmission) overlap, the UE drops the UL data/HARQ-ACK with lower priority and drops the UL data/HARQ-ACK with higher priority. Control may be performed to prioritize and transmit ACK. Note that the UE may change (eg, postpone or shift) the transmission timing of UL transmission with low priority.

If more than two (or three or more) UL signals/UL channels overlap in the time domain, the transmission may be controlled by two steps. In step 1, one UL channel is selected that multiplexes UL signals transmitted in UL transmissions with the same priority. In step 2, control may be performed such that among UL transmissions with different priorities, UL transmissions with a higher priority are transmitted with priority, and UL transmissions with a lower priority are dropped.

In this way, the UE can resolve collisions between multiple UL transmissions with the same priority through step 1 and resolve collisions between multiple UL transmissions with different priorities through step 2.

(Simultaneous transmission/multiplexing of UL transmissions with different priorities)
There may also be a case in which multiple UL transmissions transmitted using different carriers (or cells, CCs) overlap in the time domain, and the priorities among the multiple UL transmissions differ.

For example, if UL channels/UL signals are scheduled on different carriers inter-cell supported by different RF (Radio Frequency), transmitting each UL channel/UL signal can be and useful from the viewpoint of spectral efficiency. When the UE supports RF processing for different carriers (CCs), it is possible to improve resource utilization efficiency and reduce delay by transmitting UL channels/UL signals on each carrier.

For example, for each UE that supports inter-band carrier aggregation (e.g., inter-band CA) function, simultaneous transmission of PUCCH/PUSCH with different priorities (e.g., PHY priority) in different cells may be configured using RRC within the same PUCCH group. may be supported.

Alternatively, if multiple UL transmissions with different priorities are scheduled intra-cell/inter-cell, UL transmissions with different priorities can be multiplexed (e.g. on the same UL channel). may also be supported. For example, multiple UL transmissions may be supported by multiplexing UL transmissions of one priority onto UL channels for UL transmissions of other priorities.

Whether to multiplex/map a UCI (for example, HARQ-ACK) to a UL channel (for example, PUSCH) with a different priority from that of the UCI (for example, enable/disable, or activate/deactivate) is determined by the upper layer. It may also be set by signaling.

Rel. 17, when multiplexing HARQ-ACK (LP HARQ-ACK) with low priority to PUSCH (HP PUSCH) with high priority, supporting 0<beta offset<1 is considered. Furthermore, setting indexes related to beta offsets that are different from those for other cases is being considered for the case where LP HARQ-ACK is multiplexed on HP PUSCH and the case where HP HARQ-ACK is multiplexed on LP PUSCH.

For example, BetaOffsets information element for LP HARQ-ACK multiplexed on HP dynamic PUSCH (e.g., may be called BetaOffsetsCrossPri0 IE), for HP HARQ-ACK multiplexed on LP dynamic PUSCH It is being considered that a new BetaOffsets information element (for example, it may be called BetaOffsetsCrossPri1IE) will be defined. Note that these beta offsets information elements may include parameters corresponding to betaOffsetACK-Index1, betaOffsetACK-Index2, and betaOffsetACK-Index3 of existing betaoffsets information elements (BetaOffsets IE) (CSI Part 1, CSI Part 2 parameters may not be included).

In addition, the existing betaOffsets parameter (betaOffsets), the betaOffsets parameter (betaOffsetsDCI-0-2) for DCI format 0_2, and the existing betaoffsets information element (CG-UCI-OnPUSCH IE) in the CG-UCI-OnPUSCH information element (CG-UCI-OnPUSCH IE) Parameters/information elements (for example, betaOffsetsCrossPri0-r17, betaOffsetsCrossPri1-r17, betaOffsetsCrossPri0DCI-0-2-r17, betaOffsetsCrossPri1DCI -0-2-r17,CG-betaOffsetsCrossPri0,CG -betaOffsetsCrossPri1) is being considered.

(PUSCH transmission of 2 code words)
Rel. In 15/16 NR, the UE transmits one codeword (CW) using one PUSCH. Rel. In T.17 NR, it is considered that the UE transmits more than one CW using one PUSCH. For example, support for 2CW transmission for ranks 5-8, support for 2CW transmission for ranks 2-8, etc. are being considered.

Also, Rel. 15 and Rel. 16 UEs, it is assumed that only one beam and panel is used for UL transmission at a given time, but Rel. In order to improve UL throughput and reliability, simultaneous UL transmission of multiple beams and multiple panels (eg, PUSCH transmission) for one or more TRPs is being considered.

The base station may use the UL TCI or panel ID to configure or direct panel-specific transmission for UL transmission. UL TCI (UL TCI status) is Rel. It may be based on signaling similar to the DL beam indication supported in X.15. The panel ID may be implicitly or explicitly applied to a target RS resource (or target RS resource set) and at least one transmission of PUCCH/PUSCH/SRS/PRACH. If the panel ID is explicitly notified, the panel ID may be configured in at least one of the target RS, target channel, and reference RS (eg, DL RS resource configuration or spatial relationship information).

For simultaneous multi-panel UL transmission, support for 2CW PUSCH with ranks (layers) of 4 or lower is being considered.

When UCI on PUSCH is used in 2CW PUSCH (hereinafter also referred to as UCI on 2CW PUSCH), UCI is assigned to only one transport block (TB) (for example, corresponding to a lower TB index). It may be multiplexed (only on the TB), it may be divided into two parts and each is multiplexed on a different Transport Block (TB), or it may be copied and the same UCI is multiplexed on each TB. may be done.

However, consideration has not yet been made as to how to set the beta offset for UCI on 2 CW PUSCH. For example, it is still being considered whether to use the same beta offset settings in the case where UCI on PUSCH is used in 1CW PUSCH (hereinafter also referred to as UCI on 1 CW PUSCH) and in the case of UCI on 2 CW PUSCH. Not yet. If UCI on PUSCH transmission for multiple CWs is not performed appropriately, there is a risk that throughput may decrease or communication quality may deteriorate.

Therefore, the present inventors conceived of a beta offset setting method suitable for 2 CW PUSCH.

Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. The wireless communication methods according to each embodiment may be applied singly or in combination.

In the present disclosure, "A/B" and "at least one of A and B" may be read interchangeably. Furthermore, in the present disclosure, "A/B/C" may mean "at least one of A, B, and C."

In the present disclosure, "activate", "deactivate", "indicate", "select", "configure", "update", "determine", etc. may be read interchangeably. In this disclosure, supporting, controlling, being able to control, operating, capable of operating, etc. may be read interchangeably.

In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, upper layer parameters, information elements (IEs), settings, etc. may be read interchangeably. In the present disclosure, the terms Medium Access Control Element (CE), update command, activation/deactivation command, etc. may be read interchangeably. Note that configuration may be performed (or notified) based on RRC signaling, and activation/deactivation may be performed (or notified) based on MAC CE.

In the present disclosure, the upper layer signaling may be, for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.

In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), or the like. Broadcast information includes, for example, a master information block (MIB), a system information block (SIB), a minimum system information (RMSI), and other system information ( Other System Information (OSI)) may also be used.

In the present disclosure, the physical layer signaling may be, for example, downlink control information (DCI), uplink control information (UCI), etc.

In this disclosure, an index, an identifier (ID), an indicator, a resource ID, etc. may be read interchangeably. In this disclosure, sequences, lists, sets, groups, groups, clusters, subsets, etc. may be used interchangeably.

In this disclosure, a panel, a UE panel, a panel group, a beam, a beam group, a precoder, an uplink (UL) transmitting entity, a transmission/reception point (TRP), a base station, and a spatial relation information (SRI) are described. )), spatial relationship, SRS resource indicator (SRI), control resource set (CONtrol REsource SET (CORESET)), Physical Downlink Shared Channel (PDSCH), codeword (CW), transport Block (Transport Block (TB)), reference signal (RS), antenna port (e.g. demodulation reference signal (DMRS) port), antenna port group (e.g. DMRS port group), groups (e.g., spatial relationship groups, Code Division Multiplexing (CDM) groups, reference signal groups, CORESET groups, Physical Uplink Control Channel (PUCCH) groups, PUCCH resource groups), resources (e.g., reference signal resources, SRS resource), resource set (for example, reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI Unified TCI state, common TCI state, quasi-co-location (QCL), QCL assumption, etc. may be read interchangeably.

Additionally, the spatial relationship information identifier (ID) (TCI status ID) and the spatial relationship information (TCI status) may be read interchangeably. “Spatial relationship information” may be interchangeably read as “a set of spatial relationship information”, “one or more pieces of spatial relationship information”, etc. TCI status and TCI may be read interchangeably.

In this disclosure, X CW PUSCH (X is an integer. For example, X = 1, 2, ...) may be interchanged with PUSCH for transmitting X CWs, PUSCH for X CWs, etc. good. Furthermore, 1 CW PUSCH and 2 CW PUSCH may be read as PUSCH for the first number of CWs and PUSCH for the second number of CWs, respectively. The first number and the second number may each be arbitrary integers.

In the present disclosure, UCI on PUSCH for XCW PUSCH (or transmission of UCI using XCW PUSCH) may be mutually read as UCI on XCW PUSCH.

Dynamic PUSCH may be interchanged with PUSCH dynamically scheduled according to the DCI format.

The subsequent DCI format 0_2 may be replaced with a specific DCI format (for example, any future DCI format).

In the present disclosure, fields, parameters, information elements (IEs), etc. may be read interchangeably.

In this disclosure, repetition (one repetition), occasion, and channel may be read interchangeably. In this disclosure, UL data, TB, CW, and UCI may be read interchangeably.

In the present disclosure, two CWs transmitted using PUSCH may have different contents or may have the same contents. A PUSCH transmitting two CWs may be considered as one PUSCH transmitted simultaneously or repeatedly.

In the following embodiments, "plurality" and "two" may be read interchangeably.

The number of layers of PUSCH transmission in the following embodiments may be greater than 4 or may be less than or equal to 4. For example, PUSCH transmission of two CWs in the present disclosure may be performed using four or fewer layers (for example, two). Furthermore, the maximum number of layers is not limited to four or more, and may be less than four.

Furthermore, PUSCH transmission in the following embodiments may or may not be based on the use of multiple panels (it may be applied regardless of the panel).

(Wireless communication method)
<First embodiment>
The first embodiment relates to a dynamic PUSCH scheduled by a DCI format other than DCI format 0_2 (hereinafter referred to as dynamic PUSCH of the first embodiment).

Regarding the dynamic PUSCH of the first embodiment, the UE separately (or independently or differently) RRC parameters for UCI on 1 CW PUSCH and RRC parameters for UCI on 2 CW PUSCH. May be set.

These RRC parameters may correspond to at least one of the UCI-OnPUSCH information element, the betaOffsets parameter, the scaling parameter, and the BetaOffsets information element.

In the case of UCI on 1 CW PUSCH transmission, the UE determines the beta offset to utilize based on the Beta Offsets information element corresponding to the RRC parameter for UCI on 1 CW PUSCH. In the case of UCI on 2 CW PUSCH transmission, the UE determines the beta offset to utilize based on the beta offsets information element corresponding to the RRC parameters for UCI on 2 CW PUSCH.

FIG. 4 shows an example of the UCI-OnPUSCH information element for UCI on 1 CW PUSCH and the UCI-OnPUSCH information element for UCI on 2 CW PUSCH for the dynamic PUSCH of the first embodiment. It is a diagram.

Note that "-rXX" in this disclosure refers to 3GPP Rel. Indicates that the parameter is scheduled to be specified in XX. The name of the parameter is not limited to the example name (for example, "-rXX" may not be included). In the following, parameters marked with "-rXX" may be referred to by names with "-rXX" removed. The 3GPP release to which this disclosure applies is Rel. It is not limited to 18.

In the example of FIG. 4, Rel. The UCI-OnPUSCH information element defined in 15/16 NR includes settings for UCI on 1 CW PUSCH (betaOffsets parameter, scaling parameter) for the dynamic PUSCH of the first embodiment.

Further, the UCI-OnPUSCH-2codeword-r18 information element includes settings for UCI on 2CW PUSCH (betaOffsets parameter (betaOffsets-2codeword-r18), scaling parameter (scaling- 2codeword-r18)).

When 2 CW PUSCH is configured in the UE, a UCI-OnPUSCH information element for UCI on 1 CW PUSCH and a UCI-OnPUSCH-2 codeword-r18 information element for UCI on 2 CW PUSCH; Diagram containing PUSCH configuration information (PUSCH-Config information element) as shown in example 4 may be configured in the UE.

FIG. 5 shows an example of the betaOffsets parameters and scaling parameters for UCI on 1 CW PUSCH and the betaOffsets parameters and scaling parameters for UCI on 2 CW PUSCH regarding the dynamic PUSCH of the first embodiment. show It is a diagram.

In the example of FIG. 5, Rel. The betaOffsets parameter (betaOffsets) and the scaling parameter (scaling) defined in 15/16 NR correspond to the betaOffsets parameter and scaling parameter for the UCI on 1 CW PUSCH for the dynamic PUSCH of the first embodiment.

In addition, the new betaOffsets parameter (betaOffsets-2codeword-r18) and the new scaling parameter (scaling-2codeword-r18) included in one UCI-OnPUSCH information element are as follows for the dynamic PUSCH of the first embodiment: This corresponds to the betaOffsets parameter and scaling parameter for UCI on 2 CW PUSCH.

2. CW When PUSCH is configured in a UE, PUSCH configuration information (PUSCH-Config information element) including a UCI-OnPUSCH information element as shown in FIG. 5 may be configured in the UE.

FIG. 6 is a diagram illustrating an example of UCI-OnPUSCH information elements for UCI on 1 CW PUSCH and UCI on 2 CW PUSCH for dynamic PUSCH of the first embodiment.

In the example of FIG. 6, the new UCI-OnPUSCH information element (UCI-OnPUSCH-r18) includes the settings for UCI on 1 CW PUSCH and the settings for UCI on 2 CW PUSCH regarding the dynamic PUSCH of the first embodiment. Contains settings for. For example, if the betaOffsets parameter includes "dynamic", the first four of the BetaOffsets information elements of size 8 (that is, eight) corresponding to "dynamic" are the BetaOffsets information elements for UCI on 1 CW PUSCH. and the last four may correspond to the BetaOffsets information element for UCI on 2 CW PUSCH. Note that "first" and "last" may be reversed.

Furthermore, if the betaOffsets parameter includes "semiStatic", the first one of the size 2 (that is, two) BetaOffsets information elements corresponding to "semiStatic" is the BetaOffsets information element for UCI on 1 CW PUSCH. , and the last one may correspond to the BetaOffsets information element for UCI on 2 CW PUSCH. Note that "first" and "last" may be reversed.

Also, among the enumerated types (ENUMERATED types) of size 2 (that is, two) corresponding to the scaling parameters, the first one corresponds to the scaling parameter for UCI on 1 CW PUSCH, and the last one corresponds to the scaling parameter for UCI on 1 CW PUSCH. 2 CW It may correspond to the scaling parameter for PUSCH. Note that "first" and "last" may be reversed.

2. CW When PUSCH is configured in a UE, PUSCH configuration information (PUSCH-Config information element) including a new UCI-OnPUSCH information element as shown in FIG. 6 may be configured in the UE. Note that when a new UCI-OnPUSCH information element is notified, the existing UCI-OnPUSCH information element (UCI-OnPUSCH) may be ignored by the UE. If a new UCI-OnPUSCH information element is signaled, the UE may not expect an existing UCI-OnPUSCH information element (UCI-OnPUSCH) to be signaled.

Note that the new BetaOffsets consists of the existing BetaOffsets information element (BetaOffsets) for UCI on 1 CW PUSCH and the existing BetaOffsets information element (BetaOffsets) for UCI on 2 CW PUSCH. Information elements (e.g. BetaOffsets-r18) may be introduced. For example, in the example of FIG. 6, "dynamic" may include BetaOffsets-r18 of size 4 instead of the BetaOffsets information element of size 8. Furthermore, in the example of FIG. 6, "semiStatic" may include BetaOffsets-r18 instead of the BetaOffsets information element of size 2.

Note that in the first embodiment, UCI on 1 CW PUSCH and UCI on 2 CW PUSCH have at least one RRC parameter (for example, UCI-OnPUSCH information element, betaOffsets parameter, scaling parameter, BetaOffsets information at least one of the elements ) may be commonly used. In this case, for example, betaOffsets-2codeword-r18, scaling-2codeword-r18, etc. described above in FIGS. 4 and 5 may not be included in UCI-OnPUSCH-2codeword-r18 or UCI-OnPUSCH, and scaling in FIG. A parameter may contain only one enumerated type.

[Modification 1 of the first embodiment]
In the first embodiment described above, regarding UCI on 2 CW PUSCH, there are cases where UCI is multiplexed on the first CW (for example, called CW1, but may also be called CW0), and cases where UCI is multiplexed on the second CW (for example, called CW1, but may also be called CW0). For example, the assumption is that the same betaOffsets/scaling is referenced (used) in the case where UCI is multiplexed in CW2 (which may also be called CW1). On the other hand, different betaOffsets/scaling may be referenced in these cases. This modification will be explained below.

[[Modification 1-1 of the first embodiment]]
In modification 1-1 of the first embodiment, Rel. 15/16 The RRC parameters defined in the NR (e.g., at least one of the UCI-OnPUSCH information element, the betaOffsets parameter, the scaling parameter, the BetaOffsets information element) are configured for UCI on 1 CW PUSCH and UCI on 2 CW. The configuration for the first CW in PUSCH may also apply.

When 2 CW PUSCH is configured in a UE, the UE sets new RRC parameters for UCI on 2 CW PUSCH (betaOffsets-2codeword-r18, scaling-2codeword-r18, One set of at least one codeword such as UCI-OnPUSCH-2codeword-r18 may be set.

2 CW When PUSCH is configured in the UE, Rel. The RRC parameters defined in 15/16 NR are used for the first CW in UCI on 2 CW PUSCH, and the above set of new RRC parameters is used for the second CW in UCI on 2 CW PUSCH. May be used for.

[[Modification 1-2 of the first embodiment]]
In modification 1-2 of the first embodiment, Rel. 15/16 The RRC parameters defined in the NR (e.g., at least one of the UCI-OnPUSCH information element, the betaOffsets parameter, the scaling parameter, the BetaOffsets information element) apply only to the configuration for UCI on 1 CW PUSCH. 2. It may not apply to the settings for CW PUSCH.

When 2 CW PUSCH is configured in a UE, the UE sets new RRC parameters for UCI on 2 CW PUSCH (betaOffsets-2codeword-r18, scaling-2codeword-r18, Two sets of at least one codeword such as UCI-OnPUSCH-2codeword-r18 may be set.

If 2 CW PUSCH is configured in the UE, the first set of new RRC parameters is used for the first CW in UCI on 2 CW PUSCH, and the second set of new RRC parameters is , UCI on 2 CW may be used for the second CW in PUSCH.

[[Modification 1-3 of the first embodiment]]
In modification 1-3 of the first embodiment, the same betaOffsets/scaling is used when UCIs are multiplexed on PUSCHs related to the same panel and when UCIs are multiplexed on PUSCHs related to different panels. or different betaOffsets/scaling may be referenced.

Modification 1-3 of the first embodiment is modified from Modification 1-1/1-2 above by changing "UCI on 2 CW first CW in PUSCH" to "UCI is multiplexed on PUSCH related to the same panel". This may correspond to an embodiment in which "UCI on 2 CW second CW in PUSCH" is replaced with "case where UCI is multiplexed on PUSCHs related to different panels". Note that these readings may be reversed.

[Modification 2 of the first embodiment]
In the first embodiment and modification 1, among "dynamic (or dynamic-2codeword-r18)" and "semiStatic (or semiStatic-2codeword-r18)" that constitute the betaOffsets parameter (betaOffsets or betaOffsets-2codeword-r18), , both may be used for UCI on 2 CW PUSCH, or only one (for example only "dynamic (or dynamic-2codeword-r18)") may be used for UCI on 2 CW PUSCH. In addition, if only one (for example, "dynamic (or dynamic-2codeword-r18)" only) is used for UCI on 2 CW PUSCH, the other (for example, "semiStatic (or semiStatic-2codeword-r18)") is used for the above betaOffsets. It does not need to be included in the parameters.

[Modification 3 of the first embodiment]
In the first embodiment and

modifications

1 and 2, the UCI-OnPUSCH information element (UCI-OnPUSCH or UCI-OnPUSCH-2codeword-r18) may be included in UCI-OnPUSCH-ListDCI-0-1-r16. , may be used to determine the beta offset for the transmission of UCI on 2 CW PUSCH for DCI format 0_1.

According to the first embodiment described above, the UE can appropriately determine the beta offset for 2 CW PUSCH for dynamic PUSCH scheduled by a DCI format other than DCI format 0_2.

<Second embodiment>
The second embodiment relates to a dynamic PUSCH scheduled by DCI format 0_2 (hereinafter referred to as dynamic PUSCH of the second embodiment).

Regarding the dynamic PUSCH of the second embodiment, the UE separately (or independently or differently) sets the RRC parameters for UCI on 1 CW PUSCH and the RRC parameters for UCI on 2 CW PUSCH. May be set.

These RRC parameters are the UCI-OnPUSCH information element (UCI-OnPUSCH-DCI-0-2 IE) for DCI format 0_2, the betaOffsets parameter (betaOffsetsDCI-0-2) for DCI format 0_2, and the scaling for DCI format 0_2. It may correspond to at least one of the parameter (scalingDCI-0-2) and the BetaOffsets information element (BetaOffsets IE).

In the second embodiment, Rel. 15/16 RRC parameters defined in NR (for example, UCI-OnPUSCH information element (UCI-OnPUSCH IE), betaOffsets parameter (betaOffsets), scaling parameter (scaling), BetaOffsets information element (BetaOffsets IE)) are defined in Rel. 16 Corresponding RRC parameters for DCI format 0_2 defined in NR (e.g. UCI-OnPUSCH information element for DCI format 0_2 (UCI-OnPUSCH-DCI-0-2 IE), betaOffsets parameter for DCI format 0_2 (betaOffsetsDCI -0-2), a scaling parameter for DCI format 0_2 (scalingDCI-0-2), and a BetaOffsets information element (BetaOffsets IE)).

The second embodiment adds new RRC parameters for UCI on 2 CW PUSCH (for example, UCI-OnPUSCH information element (UCI-OnPUSCH-2codeword- DCI format 0_2 corresponding new RRC parameters for the 2-2codeword-r18), scaling parameter for DCI format 0_2 (scalingDCI-0-2-2codeword-r18), BetaOffsets information element (BetaOffsets IE/BetaOffsets-2codeword-r18)) good. Note that the BetaOffsets information element may be replaced with a new BetaOffsets information element for DCI format 0_2.

FIG. 7 shows an example of the betaOffsets parameters and scaling parameters for UCI on 1 CW PUSCH and the betaOffsets parameters and scaling parameters for UCI on 2 CW PUSCH regarding the dynamic PUSCH of the second embodiment. show It is a diagram.

In the example of FIG. 7, Rel. The betaOffsets parameter (betaOffsetsDCI-0-2-r16) and scaling parameter (scalingDCI-0-2) defined in 16 NR are the betaOffsets for UCI on 1 CW PUSCH for dynamic PUSCH of the second embodiment. It may also correspond to parameters and scaling parameters.

In addition, a new betaOffsets parameter (betaOffsetsDCI-0-2-2codeword-r18) and a new scaling parameter (scalingDCI-0 -2-2codeword-r18) may correspond to the betaOffsets parameter and scaling parameter for UCI on 2CW PUSCH for the dynamic PUSCH of the second embodiment.

According to the second embodiment described above, the UE can appropriately determine the beta offset for the 2 CW PUSCH for the dynamic PUSCH scheduled by DCI format 0_2.

<Third embodiment>
The third embodiment relates to CG PUSCH.

Regarding the CG PUSCH of the third embodiment, the UE configures RRC parameters for UCI on 1 CW PUSCH and RRC parameters for UCI on 2 CW PUSCH separately (or independently or differently). may be done.

These RRC parameters include the CG-UCI-OnPUSCH information element (CG-UCI-OnPUSCH IE) for CG PUSCH, the BetaOffsets information element (BetaOffsets IE), and the betaOffset parameter for CG-UCI in CG PUSCH (betaOffsetCG-UCI- r16) may apply.

FIG. 8 shows the CG-UCI-OnPUSCH information element for UCI on 1 CW PUSCH and the CG-UCI-OnPUSCH information element for UCI on 2 CW PUSCH regarding CG PUSCH of the third embodiment. It is a figure showing an example.

In the example of FIG. 8, Rel. 15/16 The CG-UCI-OnPUSCH information element defined in NR is the configuration for UCI on 1 CW PUSCH when transmitting UCI (HARQ-ACK/CSI) not including CG-UCI on CG PUSCH ( one or more BetaOffsets information elements corresponding to "dynamic" or "semiStatic").

In addition, the CG-UCI-OnPUSCH-2 codeword-r18 information element is the configuration for UCI on 2 CW PUSCH (“dynamic ” or one or more BetaOffsets information elements corresponding to “semiStatic”).

Furthermore, in the example of FIG. 8, Rel. The betaOffset parameter (betaOffsetCG-UCI-r16) for CG-UCI in CG PUSCH defined in 16 NR relates to the beta offset for UCI on 1 CW PUSCH when only CG-UCI is transmitted on CG PUSCH. Indicates the index.

In addition, the new betaOffset parameter (betaOffsetCG-UCI-2codeword-r18) for CG-UCI in CG PUSCH is related to the beta offset for UCI on 2 CW PUSCH when only CG-UCI is transmitted on CG PUSCH. Indicates the index.

If 2 CW PUSCH (or 2 CW CG PUSCH) is configured in the UE, UCI on 1 CW PUSCH CG-UCI-OnPUSCH information element/CG-UCI new betaOffset parameter for UCI CG PUSCH configuration information (ConfiguredGrantConfig information element) as shown in the example of FIG. may be set to .

FIG. 9 is a diagram illustrating an example of CG-UCI-OnPUSCH information elements for UCI on 1 CW PUSCH and UCI on 2 CW PUSCH for CG PUSCH of the third embodiment.

In the example of FIG. 9, the new CG-UCI-OnPUSCH information element (CG-UCI-OnPUSCH-r18) includes settings for UCI on 1 CW PUSCH and UCI on 2. Contains settings for CW PUSCH.

In the example of FIG. 9, the new betaOffsets parameter (betaOffsets-18) included in one CG-UCI-OnPUSCH information element corresponds to the betaOffsets parameter for UCI on 1 CW PUSCH. The betaOffsets parameter is the setting for UCI on 1 CW PUSCH (one corresponding to "dynamic" or "semiStatic") when transmitting UCI (HARQ-ACK/CSI) that does not include CG-UCI on CG PUSCH. BetaOffsets information element).

Additionally, the new betaOffsets parameter (betaOffsets-2codeword-r18) included in one UCI-OnPUSCH information element corresponds to the betaOffsets parameter for UCI on 2 CW PUSCH. The betaOffsets parameter is the setting for UCI on 2 CW PUSCH (one corresponding to "dynamic" or "semiStatic") when transmitting UCI (HARQ-ACK/CSI) that does not include CG-UCI on CG PUSCH. BetaOffsets information element).

The betaOffset parameters for CG-UCI (betaOffsetCG-UCI-r16, betaOffsetCG-UCI-2codeword-r18) are the same as those described with respect to FIG. 8, so a redundant explanation will not be provided.

2. When CW PUSCH is configured in the UE, CG PUSCH configuration information (ConfiguredGrantConfig information element) including the CG-UCI-OnPUSCH-r18 information element as shown in FIG. 9 may be configured in the UE.

According to the third embodiment described above, the UE can appropriately determine the beta offset for 2 CW PUSCH for CG PUSCH.

<Fourth embodiment>
The fourth embodiment relates to multiplexing of different priorities (in other words, multiplexing of the UCI on the PUSCH in a case where the priority of the UCI and the priority of the PUSCH are different (UCI on PUSCH)).

The fourth embodiment may correspond to an embodiment in which the first to third embodiments described above are replaced with respect to the above case.

One embodiment of the fourth embodiment may correspond to an embodiment in which the following readings have been made in the first embodiment (including variations 1-5):
・Rel. 15/16 The RRC parameters defined in NR (eg, betaOffsets parameter (betaOffsets), BetaOffsets information element (BetaOffsets IE)) are defined in Rel. 17 NR, corresponding RRC parameters for multiplexing of different priorities (e.g. betaOffsets parameters (betaOffsetsCrossPri0-r17) for LP HARQ-ACK multiplexed on HP dynamic PUSCH, multiplexed on LP dynamic PUSCH) betaOffsets parameter for HP HARQ-ACK (betaOffsetsCrossPri1-r17), betaOffsets information element (BetaOffsetsCrossPri0 IE) for LP HARQ-ACK multiplexed on HP dynamic PUSCH, HP multiplexed on LP dynamic PUSCH BetaOffsets information element for HARQ-ACK (BetaOffsetsCrossPri1 IE))
- Add new RRC parameters (for example, betaOffsets parameter (betaOffsets-2codeword-r18), BetaOffsets information element (BetaOffsets IE/BetaOffsets-2codeword-r18)) for UCI on 2 CW PUSCH to UCI on 2 CW PUSCH. , corresponding new RRC parameters for multiplexing of different priorities (e.g. betaOffsets parameters (e.g. betaOffsetsCrossPri0-2codeword-r18) for LP HARQ-ACK multiplexed on HP dynamic PUSCH, multiplexed on LP dynamic PUSCH betaOffsets parameter for HP HARQ-ACK (e.g., betaOffsetsCrossPri1-2codeword-r18), betaOffsets information element for LP HARQ-ACK multiplexed on HP dynamic PUSCH (e.g., BetaOffsetsCrossPri0-2codeword-r18 IE) , LP Replaced with BetaOffsets information element (eg, BetaOffsetsCrossPri1-2codeword-r18 IE) for HP HARQ-ACK multiplexed on dynamic PUSCH.

One embodiment of the fourth embodiment may correspond to an embodiment in which the following readings have been made in the second embodiment (including variations 1-5):
・Rel. The corresponding RRC parameters for DCI format 0_2 defined in Rel.16 NR (e.g., betaOffsets parameter for DCI format 0_2 (betaOffsetsDCI-0-2), BetaOffsets information element (BetaOffsets IE)) are defined in Rel.16 NR. 17 Corresponding RRC parameters for multiplexing of different priorities that may be defined in NR (e.g. betaOffsets parameter for LP HARQ-ACK multiplexed in HP dynamic PUSCH (betaOffsetsCrossPri0DCI-0-2-r17), LP dynamic betaOffsets parameter for HP HARQ-ACK multiplexed on PUSCH (betaOffsetsCrossPri1DCI-0-2-r17), betaoffsets information element for LP HARQ-ACK multiplexed on HP dynamic PUSCH (BetaOffsetsCrossPri0 IE), LP BetaOffsets information element (BetaOffsetsCrossPri1 IE) for HP HARQ-ACK multiplexed on dynamic PUSCH)
- New RRC parameters for UCI on 2 CW PUSCH (e.g. betaOffsets parameter for DCI format 0_2 (betaOffsetsDCI-0-2-2codeword-r18), BetaOffsets information element (BetaOffsets IE/BetaOffsets-2codeword-r18 IE)) and corresponding new RRC parameters for multiplexing of different priorities for UCI on 2 CW PUSCH (e.g. betaOffsets parameters for LP HARQ-ACK multiplexed on HP dynamic PUSCH (e.g. betaOffsetsCrossPri0DCI-0- 2-2codeword-r18), betaOffsets parameter for HP HARQ-ACK multiplexed on LP dynamic PUSCH (for example, betaOffsetsCrossPri1DCI-0-2-2codeword-r18), LP HARQ-ACK multiplexed on HP dynamic PUSCH BetaOffsets information element (e.g., BetaOffsetsCrossPri0-2codeword-r18 IE) for HP HARQ-ACK multiplexed on LP dynamic PUSCH (e.g., BetaOffsetsCrossPri1-2codeword-r18 IE) Replace it with .

One embodiment of the fourth embodiment may correspond to an embodiment in which at least one of the following readings is replaced in the third embodiment:
・Rel. 15/16 RRC parameters defined in NR or new RRC parameters for UCI on 1 CW PUSCH (e.g. CG-UCI-OnPUSCH information element (CG-UCI-OnPUSCH IE) for CG PUSCH, betaOffsets parameter (betaOffsets -r18), BetaOffsets information element (BetaOffsets IE)) in Rel. 17 Corresponding RRC parameters for multiplexing of different priorities that may be defined in NR (e.g. betaOffsets parameter corresponding to CG-UCI-OnPUSCH information element for LP HARQ-ACK multiplexed on HP CG PUSCH (CG-betaOffsetsCrossPri0) , LP CG PUSCH, multiply in the BetaoffSets parameter (CG-BetaoffsetSetscrosspri1) and HP PUSCH (CG PUSCH) for CG-UCI-ONPUSCH information elements equivalent to HP HP HARQ-ACK. BetaoffSets for LP HARQ -ACK BetaoftSets parameters (eg, BetaoftSetsCrospri1-R17), BetaoftSets (eg, BetaoftSetsCrosspri1-R17), for HP HP HARQ-ACK, which are multiple in parameters (, BetaoftSetsCrosspri0-R17) and LP PUSCH (CG PUSCH). LP HARQ -ACK, which is multiple in HP PUSCH (CG PUSCH) BetaOffsets information element (BetaOffsetsCrossPri0 IE) for HP HARQ-ACK multiplexed on LP PUSCH (CG PUSCH) (BetaOffsetsCrossPri1 IE))
- New RRC parameters for UCI on 2 CW PUSCH (e.g. CG-UCI-OnPUSCH information element (CG-UCI-OnPUSCH-2codeword-r18 IE) for CG PUSCH, betaOffsets parameter (betaOffsets-2codeword-r18), BetaOffsets information element (BetaOffsets-2codeword-r18 IE)) and corresponding new RRC parameters for multiplexing of different priorities for UCI on 2 CW PUSCH (e.g. for LP HARQ-ACK multiplexed on HP CG PUSCH). betaOffsets parameter (for example, CG-betaOffsetsCrossPri0-2codeword-r18) equivalent to the CG-UCI-OnPUSCH information element for betaOffsets parameters for LP HARQ-ACK multiplexed on HP PUSCH (CG PUSCH) (e.g. betaOffsetsCrossPri0-2codeword-r18), LP PUSCH (CG PUSCH) PUSCH) betaOffsets parameter for HP HARQ-ACK multiplexed in the HP 2codeword-r18 IE), BetaOffsets information element for HP HARQ-ACK multiplexed on LP PUSCH (CG PUSCH) (for example, BetaOffsetsCrossPri1-2codeword-r18 IE)).

Note that in the fourth embodiment, when the RRC parameter regarding the activation (application) of beta offset configuration extension regarding multiplexing of different priorities is configured, the UE configures the existing Rel. The RRC parameters related to the beta offset of 15/16 are used as settings for HP (LP) HARQ-ACK multiplexed on the LP (HP) PUSCH, and the RRC parameters related to the newly defined beta offset are ) It may be used as a setting for LP (HP) HARQ-ACK multiplexed on PUSCH.

Furthermore, in the fourth embodiment, when the RRC parameter regarding the activation (application) of beta offset configuration extension for multiplexing of different priorities is configured, the UE configures the existing Rel. The RRC parameter for the 15/16 beta offset may be ignored (if set at all). The UE may be configured with two sets of RRC parameters for beta offsets if the RRC parameters for enabling (applying) beta offset configuration extensions for multiplexes of different priorities are configured. In this case, the UE uses the RRC parameters related to the beta offset of the first set of the above two sets as settings for HP (LP) HARQ-ACK multiplexed on the LP (HP) PUSCH, and The RRC parameters regarding the beta offset of the second set of the two sets may be used as settings for LP(HP) HARQ-ACK multiplexed on HP(LP) PUSCH.

In addition, in the fourth embodiment, if the RRC parameter regarding the activation (application) of beta offset configuration extension regarding multiplexing of different priorities is not configured, the UE performs an existing Rel. RRC parameters for a beta offset of 15/16 may be used to determine the beta offset.

According to the fourth embodiment described above, the UE can perform multiplexing with different priorities (for example, a case of multiplexing HP HARQ-ACK on LP PUSCH, a case of multiplexing LP HARQ-ACK on HP PUSCH), Even if there is, the beta offset for 2 CW PUSCH can be appropriately determined.

<Supplement>
In the embodiments described above, the beta offset indicator field of the DCI may not be expanded, but the interpretation of the bit value may be different from the existing one. If the DCI schedules (indicates/implies) 2CW PUSCH, the configuration for 2CW PUSCH may be indicated by the beta offset indicator field. For example, the beta offset indicator field = "01" included in the DCI that schedules 2CW PUSCH may mean the second offset index (corresponding beta offsets information element) provided by RRC for 2CW PUSCH. good.

Note that although it does not need to be expanded, the interpretation of the bit value may be different from the existing one. If the DCI schedules a 2CW PUSCH and separate beta offsets are used for the first and second CWs, the Beta Offset Indicator field determines the settings for the first CW and the second CW. Settings for CW may be indicated. For example, the beta offset indicator field="01" included in the DCI that schedules the 2CW PUSCH is the beta offsets information element for the first CW and the second offset index (corresponding to the second offset index provided by RRC). Beta Offsets information element for CW).

Additionally, when the DCI schedules (indicates/implies) 1CW PUSCH, the configuration for 1CW PUSCH may be indicated by the beta offset indicator field. For example, the beta offset indicator field = "01" included in the DCI that schedules 1CW PUSCH may mean the second offset index (corresponding beta offsets information element) provided by RRC for 1CW PUSCH. good.

Note that in the embodiments described above, for UCI on 2 CW PUSCH, the UCI may be multiplexed only on one TB (for example, only on the TB corresponding to a lower TB index) or may be divided into two parts. They may be copied and multiplexed onto different TBs, or they may be copied and the same UCI may be multiplexed onto each TB. Regarding UCI on 2 CW PUSCH, in the case where UCI is multiplexed into only one TB, the UE is configured with settings regarding the beta offset for the TB (information elements, parameters, etc. described in each of the above embodiments), Settings regarding beta offsets for other TBs may not be configured.

Note that at least one of the embodiments described above may be applied only to UEs that have reported or support a specific UE capability.

The particular UE capability may indicate at least one of the following:
- Regarding PUSCH scheduled by a DCI format other than DCI format 0_2, whether to support separate settings for UCI on 1 CW PUSCH and UCI on 2 CW PUSCH,
- Regarding PUSCH scheduled by DCI format 0_2, whether to support separate settings for UCI on 1 CW PUSCH and UCI on 2 CW PUSCH,
- Whether to support separate settings for UCI on 1 CW PUSCH and UCI on 2 CW PUSCH for PUSCH scheduled by any DCI format;
- Regarding CG PUSCH, whether to support separate settings for UCI on 1 CW PUSCH and UCI on 2 CW PUSCH,
- Regarding CG PUSCH, whether to support separate settings for CG-UCI on 1 CW PUSCH and CG-UCI on 2 CW PUSCH,
- For multiplexing cases with different priorities (for example, multiplexing HP HARQ-ACK on LP PUSCH, multiplexing LP HARQ-ACK on HP PUSCH), CG-UCI on 1 CW PUSCH and CG-UCI on 2 Whether or not to support separate settings for CW PUSCH,
・Whether or not to support 2 CW PUSCH.

Further, the above-mentioned specific UE capability may be a capability that is applied across all frequencies (commonly regardless of frequency), or may be a capability for each frequency (for example, cell, band, BWP). , the capability may be for each frequency range (for example, FR1, FR2, FR3, FR4, FR5), or the capability may be for each subcarrier interval.

Furthermore, the above-mentioned specific UE capability may be a capability that is applied across all duplex schemes (commonly regardless of the duplex scheme), or may be a capability that is applied across all duplex schemes (for example, Time Division Duplex). The capability may be for each frequency division duplex (TDD)) or frequency division duplex (FDD)).

Also, at least one of the embodiments described above may be applied when the UE is configured with specific information related to the embodiment described above by upper layer signaling. For example, the specific information may be configuration information for UCI on 2 CW PUSCH, arbitrary RRC parameters for a specific release (for example, Rel. 18), etc.

If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, for example, Rel. 15/16 operation may be applied, it may be assumed that the same settings (e.g. default settings) are applied to 1 CW PUSCH and 2 CW PUSCH, or new RRC parameters are applied to 1 CW PUSCH and 2 CW PUSCH. If it indicates that the assumption that the same settings are applied to PUSCH is enabled, then such an assumption may be made.

(wireless communication system)
The configuration of a wireless communication system according to an embodiment of the present disclosure will be described below. In this wireless communication system, communication is performed using any one of the wireless communication methods according to the above-described embodiments of the present disclosure or a combination thereof.

FIG. 10 is a diagram illustrating an example of a schematic configuration of a wireless communication system according to an embodiment. The wireless communication system 1 may be a system that realizes communication using Long Term Evolution (LTE), 5th generation mobile communication system New Radio (5G NR), etc. specified by the Third Generation Partnership Project (3GPP). .

Additionally, the wireless communication system 1 may support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC has dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), and dual connectivity between NR and LTE (NR-E -UTRA Dual Connectivity (NE-DC)).

In EN-DC, the LTE (E-UTRA) base station (eNB) is the master node (Master Node (MN)), and the NR base station (gNB) is the secondary node (Secondary Node (SN)). In NE-DC, the NR base station (gNB) is the MN, and the LTE (E-UTRA) base station (eNB) is the SN.

The wireless communication system 1 has dual connectivity between multiple base stations within the same RAT (for example, dual connectivity (NR-NR Dual Connectivity (NN-DC) where both the MN and SN are NR base stations (gNB)). )) may be supported.

The wireless communication system 1 includes a base station 11 that forms a macro cell C1 with relatively wide coverage, and base stations 12 (12a-12c) that are located within the macro cell C1 and form a small cell C2 that is narrower than the macro cell C1. You may prepare. User terminal 20 may be located within at least one cell. The arrangement, number, etc. of each cell and user terminal 20 are not limited to the embodiment shown in the figure. Hereinafter, when base stations 11 and 12 are not distinguished, they will be collectively referred to as base station 10.

The user terminal 20 may be connected to at least one of the plurality of base stations 10. The user terminal 20 may use at least one of carrier aggregation (CA) using a plurality of component carriers (CC) and dual connectivity (DC).

Each CC may be included in at least one of a first frequency band (Frequency Range 1 (FR1)) and a second frequency band (Frequency Range 2 (FR2)). Macro cell C1 may be included in FR1, and small cell C2 may be included in FR2. For example, FR1 may be a frequency band below 6 GHz (sub-6 GHz), and FR2 may be a frequency band above 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and FR1 may correspond to a higher frequency band than FR2, for example.

Further, the user terminal 20 may communicate using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

The plurality of base stations 10 may be connected by wire (for example, optical fiber, X2 interface, etc. compliant with Common Public Radio Interface (CPRI)) or wirelessly (for example, NR communication). For example, when NR communication is used as a backhaul between base stations 11 and 12, base station 11, which is an upper station, is an Integrated Access Backhaul (IAB) donor, and base station 12, which is a relay station, is an IAB donor. May also be called a node.

The base station 10 may be connected to the core network 30 via another base station 10 or directly. The core network 30 may include, for example, at least one of Evolved Packet Core (EPC), 5G Core Network (5GCN), Next Generation Core (NGC), and the like.

The user terminal 20 may be a terminal compatible with at least one of communication systems such as LTE, LTE-A, and 5G.

In the wireless communication system 1, an orthogonal frequency division multiplexing (OFDM)-based wireless access method may be used. For example, in at least one of the downlink (DL) and uplink (UL), Cyclic Prefix OFDM (CP-OFDM), Discrete Fourier Transform Spread OFDM (DFT-s-OFDM), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), etc. may be used.

A wireless access method may also be called a waveform. Note that in the wireless communication system 1, other wireless access methods (for example, other single carrier transmission methods, other multicarrier transmission methods) may be used as the UL and DL radio access methods.

In the wireless communication system 1, the downlink channels include a physical downlink shared channel (PDSCH) shared by each user terminal 20, a broadcast channel (physical broadcast channel (PBCH)), and a downlink control channel (physical downlink control). Channel (PDCCH)) or the like may be used.

In the wireless communication system 1, uplink channels include a physical uplink shared channel (PUSCH) shared by each user terminal 20, an uplink control channel (PUCCH), and a random access channel. (Physical Random Access Channel (PRACH)) or the like may be used.

User data, upper layer control information, System Information Block (SIB), etc. are transmitted by the PDSCH. User data, upper layer control information, etc. may be transmitted by PUSCH. Furthermore, a Master Information Block (MIB) may be transmitted via the PBCH.

Lower layer control information may be transmitted by PDCCH. The lower layer control information may include, for example, downlink control information (DCI) that includes scheduling information for at least one of PDSCH and PUSCH.

Note that the DCI that schedules PDSCH may be called DL assignment, DL DCI, etc., and the DCI that schedules PUSCH may be called UL grant, UL DCI, etc. Note that PDSCH may be replaced with DL data, and PUSCH may be replaced with UL data.

A control resource set (CONtrol REsource SET (CORESET)) and a search space may be used to detect the PDCCH. CORESET corresponds to a resource for searching DCI. The search space corresponds to a search area and a search method for PDCCH candidates (PDCCH candidates). One CORESET may be associated with one or more search spaces. The UE may monitor the CORESET associated with a certain search space based on the search space configuration.

One search space may correspond to PDCCH candidates corresponding to one or more aggregation levels. One or more search spaces may be referred to as a search space set. Note that "search space", "search space set", "search space setting", "search space set setting", "CORESET", "CORESET setting", etc. in the present disclosure may be read interchangeably.

The PUCCH allows channel state information (CSI), delivery confirmation information (for example, may be called Hybrid Automatic Repeat Request ACKnowledgement (HARQ-ACK), ACK/NACK, etc.), and scheduling request ( Uplink Control Information (UCI) including at least one of SR)) may be transmitted. A random access preamble for establishing a connection with a cell may be transmitted by PRACH.

Note that in this disclosure, downlinks, uplinks, etc. may be expressed without adding "link". Furthermore, various channels may be expressed without adding "Physical" at the beginning.

In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), and the like may be transmitted. In the wireless communication system 1, the DL-RS includes a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), and a demodulation reference signal (DeModulation). Reference Signal (DMRS)), Positioning Reference Signal (PRS), Phase Tracking Reference Signal (PTRS), etc. may be transmitted.

The synchronization signal may be, for example, at least one of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). A signal block including SS (PSS, SSS) and PBCH (and DMRS for PBCH) may be called an SS/PBCH block, SS Block (SSB), etc. Note that SS, SSB, etc. may also be called reference signals.

In addition, in the wireless communication system 1, measurement reference signals (Sounding Reference Signal (SRS)), demodulation reference signals (DMRS), etc. are transmitted as uplink reference signals (UL-RS). good. Note that DMRS may be called a user terminal-specific reference signal (UE-specific reference signal).

(base station)
FIG. 11 is a diagram illustrating an example of the configuration of a base station according to an embodiment. The base station 10 includes a control section 110, a transmitting/receiving section 120, a transmitting/receiving antenna 130, and a transmission line interface 140. Note that one or more of each of the control unit 110, the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140 may be provided.

Note that this example mainly shows functional blocks that are characteristic of the present embodiment, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

The control unit 110 controls the entire base station 10. The control unit 110 can be configured from a controller, a control circuit, etc., which will be explained based on common recognition in the technical field related to the present disclosure.

The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), and the like. The control unit 110 may control transmission and reception, measurement, etc. using the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140. The control unit 110 may generate data, control information, a sequence, etc. to be transmitted as a signal, and may transfer the generated data to the transmitting/receiving unit 120. The control unit 110 may perform communication channel call processing (setting, release, etc.), status management of the base station 10, radio resource management, and the like.

The transmitting/receiving section 120 may include a baseband section 121, a radio frequency (RF) section 122, and a measuring section 123. The baseband section 121 may include a transmission processing section 1211 and a reception processing section 1212. The transmitter/receiver unit 120 includes a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transmitter/receiver circuit, etc., which are explained based on common understanding in the technical field related to the present disclosure. be able to.

The transmitting/receiving section 120 may be configured as an integrated transmitting/receiving section, or may be configured from a transmitting section and a receiving section. The transmitting section may include a transmitting processing section 1211 and an RF section 122. The reception section may include a reception processing section 1212, an RF section 122, and a measurement section 123.

The transmitting/receiving antenna 130 can be configured from an antenna described based on common recognition in the technical field related to the present disclosure, such as an array antenna.

The transmitter/receiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitter/receiver 120 may receive the above-mentioned uplink channel, uplink reference signal, and the like.

The transmitting/receiving unit 120 may form at least one of a transmitting beam and a receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

The transmitting/receiving unit 120 (transmission processing unit 1211) performs Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (for example, RLC retransmission control), Medium Access Control (MAC) layer processing (for example, HARQ retransmission control), etc. may be performed to generate a bit string to be transmitted.

The transmitting/receiving unit 120 (transmission processing unit 1211) performs channel encoding (which may include error correction encoding), modulation, mapping, filter processing, and discrete Fourier transform (DFT) on the bit string to be transmitted. A baseband signal may be output by performing transmission processing such as processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion.

The transmitting/receiving unit 120 (RF unit 122) may perform modulation, filter processing, amplification, etc. on the baseband signal in a radio frequency band, and may transmit the signal in the radio frequency band via the transmitting/receiving antenna 130. .

On the other hand, the transmitting/receiving section 120 (RF section 122) may perform amplification, filter processing, demodulation into a baseband signal, etc. on the radio frequency band signal received by the transmitting/receiving antenna 130.

The transmitting/receiving unit 120 (reception processing unit 1212) performs analog-to-digital conversion, fast Fourier transform (FFT) processing, and inverse discrete Fourier transform (IDFT) on the acquired baseband signal. )) processing (if necessary), applying reception processing such as filter processing, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing and PDCP layer processing, User data etc. may also be acquired.

The transmitting/receiving unit 120 (measuring unit 123) may perform measurements regarding the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurement, Channel State Information (CSI) measurement, etc. based on the received signal. The measurement unit 123 measures received power (for example, Reference Signal Received Power (RSRP)), reception quality (for example, Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR) )) , signal strength (for example, Received Signal Strength Indicator (RSSI)), propagation path information (for example, CSI), etc. may be measured. The measurement results may be output to the control unit 110.

The transmission path interface 140 transmits and receives signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and transmits and receives user data (user plane data) for the user terminal 20, control plane It is also possible to acquire and transmit data.

Note that the transmitting unit and receiving unit of the base station 10 in the present disclosure may be configured by at least one of the transmitting/receiving unit 120, the transmitting/receiving antenna 130, and the transmission path interface 140.

Note that the control unit 110 provides first configuration information regarding beta offsets for the physical uplink shared channel for one codeword (for example, betaOffsets, scaling, UCI-OnPUSCH) and information for two codewords. Second configuration information regarding beta offsets for the physical uplink shared channel (eg, betaOffsets-2codeword-r18, scaling-2codeword-r18, UCI-OnPUSCH-2codeword-r18) may be generated.

The transmitting/receiving unit 120 may transmit the first setting information and the second setting information to the user terminal 20.

(user terminal)
FIG. 12 is a diagram illustrating an example of the configuration of a user terminal according to an embodiment. The user terminal 20 includes a control section 210, a transmitting/receiving section 220, and a transmitting/receiving antenna 230. Note that one or more of each of the control unit 210, the transmitting/receiving unit 220, and the transmitting/receiving antenna 230 may be provided.

Note that this example mainly shows functional blocks that are characteristic of the present embodiment, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. A part of the processing of each unit described below may be omitted.

The control unit 210 controls the entire user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which will be explained based on common recognition in the technical field related to the present disclosure.

The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission and reception using the transmitting/receiving unit 220 and the transmitting/receiving antenna 230, measurement, and the like. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as a signal, and may transfer the generated data to the transmitting/receiving unit 220.

The transmitting/receiving section 220 may include a baseband section 221, an RF section 222, and a measuring section 223. The baseband section 221 may include a transmission processing section 2211 and a reception processing section 2212. The transmitting/receiving unit 220 can be configured from a transmitter/receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measuring circuit, a transmitting/receiving circuit, etc., which are explained based on common recognition in the technical field related to the present disclosure.

The transmitting/receiving section 220 may be configured as an integrated transmitting/receiving section, or may be configured from a transmitting section and a receiving section. The transmitting section may include a transmitting processing section 2211 and an RF section 222. The reception section may include a reception processing section 2212, an RF section 222, and a measurement section 223.

The transmitting/receiving antenna 230 can be configured from an antenna, such as an array antenna, as described based on common recognition in the technical field related to the present disclosure.

The transmitter/receiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transmitter/receiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, and the like.

The transmitting/receiving unit 220 may form at least one of a transmitting beam and a receiving beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

The transmission/reception unit 220 (transmission processing unit 2211) performs PDCP layer processing, RLC layer processing (e.g. RLC retransmission control), MAC layer processing (e.g. , HARQ retransmission control), etc., to generate a bit string to be transmitted.

The transmitting/receiving unit 220 (transmission processing unit 2211) performs channel encoding (which may include error correction encoding), modulation, mapping, filter processing, DFT processing (as necessary), and IFFT processing on the bit string to be transmitted. , precoding, digital-to-analog conversion, etc., and output a baseband signal.

Note that whether or not to apply DFT processing may be based on the settings of transform precoding. When transform precoding is enabled for a certain channel (for example, PUSCH), the transmitting/receiving unit 220 (transmission processing unit 2211) performs the above processing in order to transmit the channel using the DFT-s-OFDM waveform. DFT processing may be performed as the transmission processing, or if not, DFT processing may not be performed as the transmission processing.

The transmitting/receiving unit 220 (RF unit 222) may perform modulation, filter processing, amplification, etc. on the baseband signal in a radio frequency band, and may transmit the signal in the radio frequency band via the transmitting/receiving antenna 230. .

On the other hand, the transmitting/receiving section 220 (RF section 222) may perform amplification, filter processing, demodulation into a baseband signal, etc. on the radio frequency band signal received by the transmitting/receiving antenna 230.

The transmission/reception unit 220 (reception processing unit 2212) performs analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filter processing, demapping, demodulation, and decoding (error correction) on the acquired baseband signal. (which may include decoding), MAC layer processing, RLC layer processing, and PDCP layer processing may be applied to obtain user data and the like.

The transmitting/receiving unit 220 (measuring unit 223) may perform measurements regarding the received signal. For example, the measurement unit 223 may perform RRM measurement, CSI measurement, etc. based on the received signal. The measurement unit 223 may measure received power (for example, RSRP), reception quality (for example, RSRQ, SINR, SNR), signal strength (for example, RSSI), propagation path information (for example, CSI), and the like. The measurement results may be output to the control unit 210.

Note that the transmitting unit and receiving unit of the user terminal 20 in the present disclosure may be configured by at least one of the transmitting/receiving unit 220 and the transmitting/receiving antenna 230.

Note that the transmitting/receiving unit 220 transmits first configuration information regarding beta offsets for the physical uplink shared channel for one codeword (for example, betaOffsets, scaling, UCI-OnPUSCH) and information for two codewords. Second configuration information regarding beta offsets for the physical uplink shared channel (eg, betaOffsets-2codeword-r18, scaling-2codeword-r18, UCI-OnPUSCH-2codeword-r18) may be received.

The control unit 210 may determine a beta offset for transmission on the physical uplink shared channel for the two codewords based on the second configuration information.

The physical uplink shared channel may be a physical uplink shared channel scheduled according to a DCI format other than Downlink Control Information (DCI) format 0_2.

The physical uplink shared channel may be a physical uplink shared channel scheduled according to Downlink Control Information (DCI) format 0_2.

The physical uplink shared channel may be a configured grant physical uplink shared channel.

(Hardware configuration)
It should be noted that the block diagram used to explain the above embodiment shows blocks in functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically coupled device, or may be realized using two or more physically or logically separated devices directly or indirectly (e.g. , wired, wireless, etc.) and may be realized using a plurality of these devices. The functional block may be realized by combining software with the one device or the plurality of devices.

Here, functions include judgment, decision, judgement, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and consideration. , broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. Not limited. For example, a functional block (configuration unit) that performs transmission may be called a transmitting unit, a transmitter, or the like. In either case, as described above, the implementation method is not particularly limited.

For example, a base station, a user terminal, etc. in an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 13 is a diagram illustrating an example of the hardware configuration of a base station and a user terminal according to an embodiment. The base station 10 and user terminal 20 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc. .

Note that in this disclosure, words such as apparatus, circuit, device, section, unit, etc. can be read interchangeably. The hardware configuration of the base station 10 and the user terminal 20 may be configured to include one or more of each device shown in the figure, or may be configured not to include some of the devices.

For example, although only one processor 1001 is illustrated, there may be multiple processors. Also, the processing may be performed by one processor, or the processing may be performed by two or more processors simultaneously, sequentially, or using other techniques. Note that the processor 1001 may be implemented using one or more chips.

Each function in the base station 10 and the user terminal 20 is performed by, for example, loading predetermined software (program) onto hardware such as a processor 1001 and a memory 1002, so that the processor 1001 performs calculations and communicates via the communication device 1004. This is achieved by controlling at least one of reading and writing data in the memory 1002 and storage 1003.

The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured by a central processing unit (CPU) that includes interfaces with peripheral devices, a control device, an arithmetic unit, registers, and the like. For example, at least a portion of the above-mentioned control unit 110 (210), transmitting/receiving unit 120 (220), etc. may be realized by the processor 1001.

Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes in accordance with these. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, the control unit 110 (210) may be realized by a control program stored in the memory 1002 and operated in the processor 1001, and other functional blocks may also be realized in the same way.

The memory 1002 is a computer-readable recording medium, and includes at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EPROM (EEPROM), Random Access Memory (RAM), and other suitable storage media. It may be composed of one. Memory 1002 may be called a register, cache, main memory, or the like. The memory 1002 can store executable programs (program codes), software modules, and the like to implement a wireless communication method according to an embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, such as a flexible disk, a floppy (registered trademark) disk, a magneto-optical disk (for example, a compact disk (CD-ROM), etc.), a digital versatile disk, removable disk, hard disk drive, smart card, flash memory device (e.g., card, stick, key drive), magnetic stripe, database, server, or other suitable storage medium. It may be configured by Storage 1003 may also be called an auxiliary storage device.

The communication device 1004 is hardware (transmission/reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc., for example. The communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). It may be configured to include. For example, the above-described transmitting/receiving unit 120 (220), transmitting/receiving antenna 130 (230), etc. may be realized by the communication device 1004. The transmitter/receiver 120 (220) may be physically or logically separated into a transmitter 120a (220a) and a receiver 120b (220b).

The input device 1005 is an input device (eg, keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (for example, a display, a speaker, a light emitting diode (LED) lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

Further, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses for each device.

The base station 10 and user terminal 20 also include a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), a field programmable gate array (FPGA), etc. It may be configured to include hardware, and a part or all of each functional block may be realized using the hardware. For example, processor 1001 may be implemented using at least one of these hardwares.

(Modified example)
Note that terms explained in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, channel, symbol and signal may be interchanged. Also, the signal may be a message. The reference signal may also be abbreviated as RS, and may be called a pilot, pilot signal, etc. depending on the applicable standard. Further, a component carrier (CC) may be called a cell, a frequency carrier, a carrier frequency, or the like.

A radio frame may be composed of one or more periods (frames) in the time domain. Each of the one or more periods (frames) constituting a radio frame may be called a subframe. Furthermore, a subframe may be composed of one or more slots in the time domain. A subframe may have a fixed time length (eg, 1 ms) that does not depend on numerology.

Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology includes, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, and radio frame structure. , a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the time domain, etc.

A slot may be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain. Furthermore, a slot may be a time unit based on numerology.

A slot may include multiple mini-slots. Each minislot may be made up of one or more symbols in the time domain. Furthermore, a mini-slot may also be called a sub-slot. A minislot may be made up of fewer symbols than a slot. PDSCH (or PUSCH) transmitted in time units larger than minislots may be referred to as PDSCH (PUSCH) mapping type A. PDSCH (or PUSCH) transmitted using minislots may be referred to as PDSCH (PUSCH) mapping type B.

Radio frames, subframes, slots, minislots, and symbols all represent time units when transmitting signals. Other names may be used for the radio frame, subframe, slot, minislot, and symbol. Note that time units such as frames, subframes, slots, minislots, and symbols in the present disclosure may be read interchangeably.

For example, one subframe may be called a TTI, a plurality of consecutive subframes may be called a TTI, and one slot or one minislot may be called a TTI. In other words, at least one of the subframe and TTI may be a subframe (1ms) in existing LTE, a period shorter than 1ms (for example, 1-13 symbols), or a period longer than 1ms. It may be. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used by each user terminal) to each user terminal on a TTI basis. Note that the definition of TTI is not limited to this.

The TTI may be a transmission time unit of a channel-coded data packet (transport block), a code block, a codeword, etc., or may be a processing unit of scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (for example, the number of symbols) to which transport blocks, code blocks, code words, etc. are actually mapped may be shorter than the TTI.

Note that when one slot or one minislot is called a TTI, one or more TTIs (that is, one or more slots or one or more minislots) may be the minimum time unit for scheduling. Further, the number of slots (minislot number) that constitutes the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI that is shorter than the normal TTI may be referred to as an abbreviated TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

Note that long TTI (for example, normal TTI, subframe, etc.) may be read as TTI with a time length exceeding 1 ms, and short TTI (for example, short TTI, etc.) It may also be read as a TTI having the above TTI length.

A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more continuous subcarriers (subcarriers) in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, and may be 12, for example. The number of subcarriers included in an RB may be determined based on numerology.

Additionally, an RB may include one or more symbols in the time domain, and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

Note that one or more RBs include a physical resource block (Physical RB (PRB)), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, and an RB. They may also be called pairs.

Additionally, a resource block may be configured by one or more resource elements (REs). For example, 1 RE may be a radio resource region of 1 subcarrier and 1 symbol.

Bandwidth Part (BWP) (also called partial bandwidth, etc.) refers to a subset of consecutive common resource blocks (RB) for a certain numerology in a certain carrier. Good too. Here, the common RB may be specified by an RB index based on a common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

BWP may include UL BWP (BWP for UL) and DL BWP (BWP for DL). One or more BWPs may be configured within one carrier for a UE.

At least one of the configured BWPs may be active and the UE may not expect to transmit or receive a given signal/channel outside of the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be replaced with "BWP".

Note that the structures of the radio frame, subframe, slot, minislot, symbol, etc. described above are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of symbols included in an RB, The number of subcarriers, the number of symbols within a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

In addition, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values from a predetermined value, or using other corresponding information. may be expressed. For example, radio resources may be indicated by a predetermined index.

The names used for parameters and the like in this disclosure are not limiting in any respect. Furthermore, the mathematical formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure. Since the various channels (PUCCH, PDCCH, etc.) and information elements can be identified by any suitable designation, the various names assigned to these various channels and information elements are not in any way exclusive designations. .

The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description, may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may also be represented by a combination of

Additionally, information, signals, etc. may be output from the upper layer to the lower layer and from the lower layer to at least one of the upper layer. Information, signals, etc. may be input and output via multiple network nodes.

Input/output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Information, signals, etc. that are input and output can be overwritten, updated, or added. The output information, signals, etc. may be deleted. The input information, signals, etc. may be transmitted to other devices.

Notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, the notification of information in this disclosure may be physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., Radio Resource Control (RRC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB), etc.), Medium Access Control (MAC) signaling), other signals, or a combination thereof It may be carried out by

Note that the physical layer signaling may also be called Layer 1/Layer 2 (L1/L2) control information (L1/L2 control signal), L1 control information (L1 control signal), etc. Further, RRC signaling may be called an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like. Further, MAC signaling may be notified using, for example, a MAC Control Element (CE).

Further, notification of prescribed information (for example, notification of "X") is not limited to explicit notification, but may be made implicitly (for example, by not notifying the prescribed information or by providing other information) (by notification).

The determination may be made by a value expressed by 1 bit (0 or 1), or by a boolean value expressed by true or false. , may be performed by numerical comparison (for example, comparison with a predetermined value).

Software includes instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, whether referred to as software, firmware, middleware, microcode, hardware description language, or by any other name. , should be broadly construed to mean an application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc.

Additionally, software, instructions, information, etc. may be sent and received via a transmission medium. For example, if the software uses wired technology (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (such as infrared, microwave, etc.) to , a server, or other remote source, these wired and/or wireless technologies are included within the definition of a transmission medium.

The terms "system" and "network" used in this disclosure may be used interchangeably. "Network" may refer to devices (eg, base stations) included in the network.

In this disclosure, "precoding", "precoder", "weight (precoding weight)", "quasi-co-location (QCL)", "Transmission Configuration Indication state (TCI state)", "space "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "number of layers", Terms such as "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", and "panel" are interchangeable. can be used.

In the present disclosure, "Base Station (BS)", "Wireless base station", "Fixed station", "NodeB", "eNB (eNodeB)", "gNB (gNodeB)", "Access point", "Transmission Point (TP)", "Reception Point (RP)", "Transmission/Reception Point (TRP)", "Panel" , "cell," "sector," "cell group," "carrier," "component carrier," and the like may be used interchangeably. A base station is sometimes referred to by terms such as macrocell, small cell, femtocell, and picocell.

A base station can accommodate one or more (eg, three) cells. If a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area is connected to a base station subsystem (e.g., an indoor small base station (Remote Radio Communication services can also be provided by the Head (RRH)). The term "cell" or "sector" refers to part or all of the coverage area of a base station and/or base station subsystem that provides communication services in this coverage.

In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" are used interchangeably. can be done.

A mobile station is a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal. , handset, user agent, mobile client, client, or some other suitable terminology.

At least one of a base station and a mobile station may be called a transmitting device, a receiving device, a wireless communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving object, the moving object itself, or the like.

The moving body refers to a movable object, and the moving speed is arbitrary, and naturally includes cases where the moving body is stopped. The mobile objects include, for example, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, carts, rickshaws, and ships (ships and other watercraft). , including, but not limited to, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and items mounted thereon. Furthermore, the mobile object may be a mobile object that autonomously travels based on a travel command.

The moving object may be a vehicle (for example, a car, an airplane, etc.), an unmanned moving object (for example, a drone, a self-driving car, etc.), or a robot (manned or unmanned). ). Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

FIG. 14 is a diagram illustrating an example of a vehicle according to an embodiment. The vehicle 40 includes a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, an axle 48, an electronic control unit 49, various sensors (current sensor 50, (including a rotation speed sensor 51, an air pressure sensor 52, a vehicle speed sensor 53, an acceleration sensor 54, an accelerator pedal sensor 55, a brake pedal sensor 56, a shift lever sensor 57, and an object detection sensor 58), an information service section 59, and a communication module 60. Be prepared.

The drive unit 41 is composed of, for example, at least one of an engine, a motor, and a hybrid of an engine and a motor. The steering unit 42 includes at least a steering wheel (also referred to as a steering wheel), and is configured to steer at least one of the front wheels 46 and the rear wheels 47 based on the operation of the steering wheel operated by the user.

The electronic control unit 49 includes a microprocessor 61, a memory (ROM, RAM) 62, and a communication port (for example, an input/output (IO) port) 63. Signals from various sensors 50-58 provided in the vehicle are input to the electronic control unit 49. The electronic control section 49 may be called an electronic control unit (ECU).

The signals from the various sensors 50 to 58 include a current signal from the current sensor 50 that senses the current of the motor, a rotation speed signal of the front wheel 46/rear wheel 47 obtained by the rotation speed sensor 51, and a signal obtained by the air pressure sensor 52. air pressure signals of the front wheels 46/rear wheels 47, a vehicle speed signal acquired by the vehicle speed sensor 53, an acceleration signal acquired by the acceleration sensor 54, a depression amount signal of the accelerator pedal 43 acquired by the accelerator pedal sensor 55, and a brake pedal sensor. 56, a shift lever 45 operation signal obtained by the shift lever sensor 57, and an object detection sensor 58 for detecting obstacles, vehicles, pedestrians, etc. There are signals etc.

The information service department 59 includes various devices such as car navigation systems, audio systems, speakers, displays, televisions, and radios that provide (output) various information such as driving information, traffic information, and entertainment information, and these devices. It consists of one or more ECUs that control the The information service unit 59 provides various information/services (for example, multimedia information/multimedia services) to the occupants of the vehicle 40 using information acquired from an external device via the communication module 60 or the like.

The information service unit 59 may include an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accepts input from the outside, and an output device that performs output to the outside (for example, display, speaker, LED lamp, touch panel, etc.).

The driving support system unit 64 includes millimeter wave radar, Light Detection and Ranging (LiDAR), a camera, a positioning locator (for example, Global Navigation Satellite System (GNSS), etc.), and map information (for example, High Definition (HD)). maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., inertial measurement units (IMUs), inertial navigation systems (INS), etc.), artificial intelligence ( Artificial Intelligence (AI) chips, AI processors, and other devices that provide functions to prevent accidents and reduce the driver's driving burden, as well as one or more devices that control these devices. It consists of an ECU. Further, the driving support system section 64 transmits and receives various information via the communication module 60, and realizes a driving support function or an automatic driving function.

The communication module 60 can communicate with the microprocessor 61 and components of the vehicle 40 via the communication port 63. For example, the communication module 60 communicates via the communication port 63 with a drive unit 41, a steering unit 42, an accelerator pedal 43, a brake pedal 44, a shift lever 45, left and right front wheels 46, left and right rear wheels 47, which are included in the vehicle 40. Data (information) is transmitted and received between the axle 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and various sensors 50-58.

The communication module 60 is a communication device that can be controlled by the microprocessor 61 of the electronic control unit 49 and can communicate with external devices. For example, various information is transmitted and received with an external device via wireless communication. The communication module 60 may be located either inside or outside the electronic control unit 49. The external device may be, for example, the base station 10, user terminal 20, etc. described above. Further, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (it may function as at least one of the base station 10 and the user terminal 20).

The communication module 60 receives signals from the various sensors 50 to 58 described above that are input to the electronic control unit 49, information obtained based on the signals, and input from the outside (user) obtained via the information service unit 59. At least one of the information based on the information may be transmitted to an external device via wireless communication. The electronic control unit 49, various sensors 50-58, information service unit 59, etc. may be called an input unit that receives input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above input.

The communication module 60 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device, and displays it on the information service section 59 provided in the vehicle. The information service unit 59 is an output unit that outputs information (for example, outputs information to devices such as a display and a speaker based on the PDSCH (or data/information decoded from the PDSCH) received by the communication module 60). may be called.

The communication module 60 also stores various information received from external devices into a memory 62 that can be used by the microprocessor 61. Based on the information stored in the memory 62, the microprocessor 61 controls the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, and left and right rear wheels provided in the vehicle 40. 47, axle 48, various sensors 50-58, etc. may be controlled.

Additionally, the base station in the present disclosure may be replaced by a user terminal. For example, communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, it may be called Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the user terminal 20 may have the functions that the base station 10 described above has. Further, words such as "uplink" and "downlink" may be replaced with words corresponding to inter-terminal communication (for example, "sidelink"). For example, uplink channels, downlink channels, etc. may be replaced with sidelink channels.

Similarly, the user terminal in the present disclosure may be replaced with a base station. In this case, the base station 10 may have the functions that the user terminal 20 described above has.

In this disclosure, the operations performed by the base station may be performed by its upper node in some cases. In a network that includes one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by the base station, one or more network nodes other than the base station (e.g. It is clear that this can be performed by a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc. (though not limited thereto), or a combination thereof.

Each aspect/embodiment described in this disclosure may be used alone, in combination, or may be switched and used in accordance with execution. Further, the order of the processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be changed as long as there is no contradiction. For example, the methods described in this disclosure use an example order to present elements of the various steps and are not limited to the particular order presented.

Each aspect/embodiment described in this disclosure includes Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system ( 4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG (x is an integer or decimal number, for example)), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications ), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802 .11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), and other appropriate wireless communication methods. The present invention may be applied to systems to be used, next-generation systems expanded, modified, created, or defined based on these systems. Furthermore, a combination of multiple systems (for example, a combination of LTE or LTE-A and 5G) may be applied.

As used in this disclosure, the phrase "based on" does not mean "based solely on" unless explicitly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

As used in this disclosure, any reference to elements using the designations "first," "second," etc. does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, reference to a first and second element does not imply that only two elements may be employed or that the first element must precede the second element in any way.

The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "judgment" can mean judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry ( For example, searching in a table, database, or other data structure), ascertaining, etc. may be considered to be "determining."

In addition, "judgment (decision)" includes receiving (e.g., receiving information), transmitting (e.g., sending information), input (input), output (output), access ( may be considered to be "determining", such as accessing data in memory (eg, accessing data in memory).

In addition, "judgment" is considered to mean "judging" resolving, selecting, choosing, establishing, comparing, etc. Good too. In other words, "judgment (decision)" may be considered to be "judgment (decision)" of some action.

Furthermore, "judgment (decision)" may be read as "assuming", "expecting", "considering", etc.

As used in this disclosure, the terms "connected", "coupled", or any variations thereof refer to any connection or coupling, direct or indirect, between two or more elements. can include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connection" may be replaced with "access."

In this disclosure, when two elements are connected, they may be connected using one or more electrical wires, cables, printed electrical connections, etc., as well as in the radio frequency domain, microwave can be considered to be "connected" or "coupled" to each other using electromagnetic energy having wavelengths in the light (both visible and invisible) range.

In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that the term may also mean that "A and B are each different from C". Terms such as "separate" and "coupled" may also be interpreted similarly to "different."

Where "include", "including" and variations thereof are used in this disclosure, these terms are inclusive, as is the term "comprising". It is intended that Furthermore, the term "or" as used in this disclosure is not intended to be exclusive or.

In this disclosure, when articles are added by translation, such as a, an, and the in English, the present disclosure may include that the nouns following these articles are plural.

Although the invention according to the present disclosure has been described in detail above, it is clear for those skilled in the art that the invention according to the present disclosure is not limited to the embodiments described in the present disclosure. The invention according to the present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the invention as determined based on the claims. Therefore, the description of the present disclosure is for the purpose of illustrative explanation and does not have any limiting meaning on the invention according to the present disclosure.

Claims

first configuration information regarding a beta offset for a physical uplink shared channel for one codeword; and second configuration information regarding a beta offset for the physical uplink shared channel for two codewords. a receiving unit that receives ,
a control unit that determines a beta offset for transmission of the physical uplink shared channel for the two codewords based on the second configuration information.
The terminal according to claim 1, wherein the physical uplink shared channel is a physical uplink shared channel scheduled by a DCI format other than Downlink Control Information (DCI) format 0_2.
The terminal according to claim 1, wherein the physical uplink shared channel is a physical uplink shared channel scheduled according to Downlink Control Information (DCI) format 0_2.
The terminal according to claim 1, wherein the physical uplink shared channel is a configured grant physical uplink shared channel.
first configuration information regarding a beta offset for a physical uplink shared channel for one codeword; and second configuration information regarding a beta offset for the physical uplink shared channel for two codewords. , a step of receiving ,
determining a beta offset for transmission on the physical uplink shared channel for the two codewords based on the second configuration information.
first configuration information regarding a beta offset for a physical uplink shared channel for one codeword; and second configuration information regarding a beta offset for the physical uplink shared channel for two codewords. a control unit that generates ,
A base station comprising: a transmitter that transmits the first configuration information and the second configuration information.