Terminal, wireless communication method, base station and system

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

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

[0002] Long Term Evolution (LTE) has been specified for the Universal Mobile Telecommunications System (UMTS) network with the aim of achieving higher data rates and lower latency (Non-Patent Document 1). Also, LTE-Advanced (3GPP Rel. 10-14) has been specified with the aim of achieving higher capacity and more advanced features than LTE (Third Generation Partnership Project (3GPP) Release (Rel.) 8, 9).

[0003] Successor systems to LTE (e.g., 5th generation mobile communication system (5G), 5G+ (plus), 6th generation mobile communication system (6G), New Radio (NR), 3GPP Rel. 15 or later, etc.) are also being considered.

[0004] 3GPP TS 36.300 V8.12.0 “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8)”, April 2010

[0005] In NR, a terminal (user terminal, User Equipment (UE)) can transmit uplink control information (Uplink Control Information (UCI)) using a physical uplink shared channel (PUSCH). The operation of transmitting UCI on PUSCH is also called UCI on PUSCH.

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

[0007] In Rel. 15 / 16 NR, a UE transmits one codeword (CW) using one PUSCH. In future wireless communication systems (e.g., Rel. 17 NR), it is being considered that a UE will transmit more than one CW using one PUSCH.

[0008] However, how to set the beta offset for a PUSCH that transmits more than one CW has not yet been studied. If UCI on PUSCH transmission for multiple CWs is not performed appropriately, there is a risk that throughput will decrease and communication quality will deteriorate.

[0009] Therefore, an 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.

[0010] A terminal according to one aspect of the present disclosure includes a receiving unit that receives first configuration information regarding beta offsets for a physical uplink shared channel for one codeword and second configuration information regarding beta offsets for the physical uplink shared channel for two codewords, and a control unit that determines beta offsets for transmission of the physical uplink shared channel for the two codewords based on the second configuration information.

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

[0012] Fig. 1 is a diagram showing an example of a set of information elements related to multiple beta offsets in Rel. 15 / 16 NR. Fig. 2 is a diagram showing an example of PUSCH configuration information including a beta offset information element in Rel. 15 / 16 NR. Fig. 3 is a diagram showing an example of CG PUSCH configuration information including a beta offset information element in Rel. 15 / 16 NR. Fig. 4 is a diagram showing an example of a UCI-OnPUSCH information element for a UCI-on-1 CW PUSCH and a UCI-OnPUSCH information element for a UCI-on-2 CW PUSCH for a dynamic PUSCH according to the first embodiment. Fig. 5 is a diagram showing an example of betaOffsets parameters and scaling parameters for a UCI on 1 CW PUSCH and a betaOffsets parameter and a scaling parameter for a UCI on 2 CW PUSCH for a dynamic PUSCH according to the first embodiment. Fig. 6 is a diagram showing an example of UCI-OnPUSCH information elements for a UCI on 1 CW PUSCH and a UCI on 2 CW PUSCH for a dynamic PUSCH according to the first embodiment. Fig. 7 is a diagram showing an example of betaOffsets parameters and scaling parameters for a UCI on 1 CW PUSCH and a betaOffsets parameter and a scaling parameter for a UCI on 2 CW PUSCH for a dynamic PUSCH according to the second embodiment. Fig. 8 is a diagram illustrating an example of a CG-UCI-OnPUSCH information element for a UCI-on-1 CW PUSCH and a CG-UCI-OnPUSCH information element for a UCI-on-2 CW PUSCH, with respect to a CG PUSCH according to the third embodiment. Fig. 9 is a diagram illustrating an example of a CG-UCI-OnPUSCH information element for a UCI-on-1 CW PUSCH and a UCI-on-2 CW PUSCH, with respect to a CG PUSCH according to 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 a configuration of a base station according to an embodiment. Fig. 12 is a diagram illustrating an example of a configuration of a user terminal according to an embodiment.Fig. 13 is a diagram illustrating an example of a 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.

[0013] (Beta Offset) In NR, a UE can transmit uplink control information (UCI) using a physical uplink shared channel (PUSCH). The operation of transmitting UCI on PUSCH is also called UCI on PUSCH.

[0014] In the case of UCI on PUSCH, the UE may determine the coding rate of the UCI to be transmitted using the PUSCH based on the amount of resources used to transmit the UCI (e.g., the number of coded modulation symbols per layer, the number of resource elements (REs)), the number of bits of the UCI, the modulation order, etc.

[0015] The UE determines the amount of resources (e.g., the number of coded modulation symbols per layer) for transmitting the UCI based on a beta offset. The beta offset is expressed as β Ｏｆｆｓｅｔ The beta offset may be different for each type or content of UCI (HARQ-ACK, CSI Part 1, CSI Part 2, etc.), and may be different for each type or content of UCI. In addition, the transmission power of the PUSCH including the UCI may be determined based on the beta offset.

[0016] A set of multiple beta offsets may be configured in the UE by higher layer signaling (eg, Radio Resource Control (RRC) signaling).

[0017] 1 is a diagram showing an example of a set of information elements related to multiple beta offsets in Rel. 15 / 16 NR. This example is described using Abstract Syntax Notation One (ASN.1) notation (note that this is merely an example and is not necessarily a complete description, and the same applies to subsequent similar drawings).

[0018] An information element (BetaOffsets IE) for a set of multiple beta offsets includes seven parameters indicating indexes for the beta offsets.

[0019] The parameters betaOffsetACK-Index1, betaOffsetACK-Index2, and betaOffsetACK-Index3 indicate an index for the beta offset that is applied when transmitting HARQ-ACK of up to 2 bits, up to 11 bits, and more than 11 bits on the PUSCH, respectively.

[0020] The parameters betaOffsetCSI-Part1-Index1 and betaOffsetCSI-Part1-Index2 indicate the indexes for the beta offsets that are applied when transmitting CSI Part 1 up to 11 bits and more than 11 bits on the PUSCH, respectively.

[0021] The parameters betaOffsetCSI-Part2-Index1 and betaOffsetCSI-Part2-Index2 indicate the indexes for the beta offsets that are applied when transmitting CSI Part 2 up to 11 bits and more than 11 bits, respectively, on the PUSCH.

[0022] The UE refers to one index in one set based on the type (or content) and number of bits (payload size) of the UCI to be transmitted, and determines the corresponding beta offset value. Note that the correspondence between the index and the beta offset value is specified by the standard. The correspondence may be different for each UCI content.

[0023] In NR, a dynamic beta offset and a semi-static beta offset are specified. When a dynamic beta offset is configured in a UE, one of up to four offset indexes is specified by a beta offset indicator field included in a downlink control information (DCI) format that schedules a PUSCH. The UE uses the beta offset information element corresponding to the specified offset index to determine the beta offset for the UCI transmitted in the PUSCH.

[0024] When a semi-static beta offset is configured, the UE determines that the beta offset indicator field included in the DCI format that schedules the PUSCH is set to 0. The UE also uses one beta offset information element configured by the RRC to determine the beta offset for the UCI transmitted in the PUSCH.

[0025] A beta offset information element related to a dynamic beta offset or a semi-static beta offset for a PUSCH scheduled by a DCI format (which may be referred to as a dynamic PUSCH, a dynamically scheduled PUSCH, or the like) is included in PUSCH configuration information (PUSCH-Config information element) and configured in a UE. Note that a DCI that schedules a PUSCH may be referred to as a dynamic grant, and DCI formats 0_0, 0_1, 0_2, and the like are defined for this purpose.

[0026] 2 is a diagram illustrating an example of PUSCH configuration information including a beta offset information element in Rel. 15 / 16 NR.

[0027] The UCI-OnPUSCH information element (UCI-OnPUSCH IE) specified in Rel. 15 / 16 NR may include a betaOffsets parameter (betaOffsets) and a scaling parameter (scaling). When the betaOffsets parameter includes "dynamic", it indicates that a dynamic beta offset is used for DCI formats other than DCI format 0_2, and when it includes "semiStatic", it indicates that a semi-static beta offset is used for DCI formats other than DCI format 0_2. "Dynamic" includes a betaOffsets information element of size 4 (i.e., four), and "semiStatic" includes one betaOffsets information element.

[0028] 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.

[0029] The UCI-OnPUSCH-DCI-0-2 information element (UCI-OnPUSCH-DCI-0-2 IE) specified in Rel. 16 NR indicates the betaOffsets parameter (betaOffsetsDCI-0-2) and scaling parameter (scalingDCI-0-2) for DCI format 0_2. It differs from the UCI-OnPUSCH information element in that a beta offset information element of size 2 can be configured instead of a beta offset information element of size 4 for a dynamic beta offset. 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 semi-static beta offset is configured, the size of the beta offset indicator field included in DCI format 0_2 is also 0 bits.

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

[0031] The first HARQ-ACK codebook is associated with a Physical Uplink Control Channel (PUCCH) with a priority index of 0, and the second HARQ-ACK codebook is associated with a PUCCH with a priority index of 1. The larger the priority index value, the higher the priority. Priority will be described later.

[0032] An uplink transmission without a dynamic grant (PUSCH transmission) is also called a configured grant (CG) PUSCH. The actual uplink grant (UL grant) for the CG PUSCH is configured by RRC signaling (ConfiguredGrantConfig information element) for a type-1 CG PUSCH, and is provided by the PDCCH (DCI) for a type-2 CG PUSCH.

[0033] A beta offset information element regarding a dynamic beta offset or a semi-static beta offset for the CG PUSCH is included in CG PUSCH configuration information (ConfiguredGrantConfig information element) and configured in the UE.

[0034] 3 is a diagram illustrating an example of CG PUSCH configuration information including a beta offset information element in Rel. 15 / 16 NR.

[0035] The CG-UCI-OnPUSCH information element (CG-UCI-OnPUSCH IE) specified in Rel. 15 / 16 NR includes settings (one or more BetaOffsets information elements corresponding to "dynamic" or "semi-static") for transmitting UCI (HARQ-ACK / CSI) that does not include CG-UCI on CG PUSCH. If the CG-UCI-OnPUSCH information element includes "dynamic", it indicates that a dynamic beta offset is used for UCI on CG PUSCH, and if it includes "semi-static", it indicates that a semi-static beta offset is used for UCI on CG PUSCH. "Dynamic" includes a BetaOffsets information element of size 1 to 4, and "semiStatic" includes one BetaOffsets information element.

[0036] Note that "semiStatic" is configured for Type 1 CG PUSCH. Furthermore, when "dynamic" is configured for Type 2 CG PUSCH, the UE is assigned one of up to four offset indexes by the beta offset indicator field included in the DCI for CG PUSCH activation. The UE uses the beta offset information element corresponding to the assigned offset index to determine the beta offset for the UCI transmitted in the CG PUSCH.

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

[0038] In addition, the CG-UCI may include a HARQ Process Number (HPN) field, a Redundancy Version (RV) field, a New Data Indicator (NDI) field, and a Channel Occupancy Time (COT) sharing information field.

[0039] (Priority) In NR Rel. 16 and later, multiple levels (e.g., two levels) of priority can be set for signals / channels. For example, it is expected that different priorities will be set for signals / channels corresponding to different traffic types (also referred to as services, service types, communication types, use cases, etc.) to control communications (e.g., transmission control in the event of a collision). This makes it possible to control communications for the same signal / channel based on different priorities depending on the service type, etc.

[0040] Priority may be set / defined for at least one of information (e.g., UCI, Channel State Information (CSI)), channels (Physical Downlink Shared Channel (PDSCH), PUSCH, PUCCH, etc.), reference signals (e.g., CSI-RS, SRS, etc.), and HARQ-ACK codebook. Also, different priorities may be set for the PUCCH used to transmit SR, the PUCCH used to transmit HARQ-ACK, and the PUCCH used to transmit CSI.

[0041] The priority may be defined as a first priority (e.g., high, 1, etc.) and a second priority (e.g., low, 0, etc.) lower than the first priority. Alternatively, three or more types of priority may be set. The priority may be represented by a priority index, and a larger priority index may correspond to a higher priority.

[0042] High priority may be expressed as high priority (HP), and low priority may be expressed as low priority (LP). For example, a high-priority PUSCH may be expressed as HP PUSCH, and a low-priority HARQ-ACK may be expressed as LP HARQ-ACK.

[0043] Priorities may be set for HARQ-ACK for dynamically scheduled PDSCH, HARQ-ACK for semi-persistent scheduling (SPS) PDSCH, and HARQ-ACK for SPS PDSCH release. Priorities may also be set for HARQ-ACK codebooks corresponding to these HARQ-ACKs. When setting a priority for a PDSCH, the priority of the PDSCH may be read as the priority of the HARQ-ACK for that PDSCH.

[0044] Furthermore, priorities may be set for dynamic PUSCH, CG PUSCH, and the like.

[0045] Priority information may be notified from the base station to the UE using at least one of higher layer signaling and DCI. For example, the priority of a scheduling request may be configured by a higher layer parameter (e.g., schedulingRequestPriority). The priority of HARQ-ACK for a PDSCH scheduled by a DCI (e.g., a dynamic PDSCH) may be signaled by the DCI. The priority of HARQ-ACK for an SPS PDSCH may be configured by a higher layer parameter (e.g., HARQ-ACK-Codebook-indicator-forSPS) or may be signaled by a DCI indicating activation of the SPS PDSCH.

[0046] A predetermined priority (e.g., low) may be set for aperiodic CSI (A-CSI) / semi-persistent CSI (SP-CSI) transmitted on the PUCCH. On the other hand, the priority of aperiodic CSI (A-CSI) / SP-CSI transmitted on the PUSCH may be indicated by DCI (e.g., trigger DCI or activation DCI).

[0047] The priority of the dynamic grant-based PUSCH may be indicated by a priority indicator field of the DCI that schedules the PUSCH. The priority of the configured grant-based PUSCH may be configured by a higher layer parameter (e.g., priority). A predetermined priority (e.g., low) may be configured for the P-SRS / SP-SRS and the A-SRS triggered by the DCI (e.g., DCI format 0_1 / DCI format 2_3).

[0048] The UE may control UL transmissions based on priority when multiple UL signals / UL channels overlap (or collide).

[0049] The overlap of multiple UL signals / UL channels may refer to the case where the time resources (or the time resources and the frequency resources) of multiple UL signals / UL channels overlap, or the case where the transmission timings of multiple UL signals / UL channels overlap. The time resource may be interpreted as the time domain. The time resource may be in units of a symbol, a slot, a subslot, or a subframe.

[0050] Overlapping UL signals / UL channels at the same UE (e.g., intra-UE) may mean overlapping UL signals / UL channels at least in the same time resource (e.g., symbol), and colliding UL signals / UL channels at different UEs (e.g., inter-UE) may mean overlapping UL signals / UL channels in the same time resource (e.g., symbol) and frequency resource (e.g., RB).

[0051] For example, when multiple UL signals / UL channels with the same priority overlap, the UE may control the multiple UL signals / UL channels to be multiplexed into one UL channel and transmitted.

[0052] For example, when a HARQ-ACK (or a PUCCH for transmitting the HARQ-ACK) set to the first priority (high) overlaps with UL data / UL-SCH (or a PUSCH for transmitting the UL data / UL-SCH) set to the first priority (high), the UE may multiplex (or map) the HARQ-ACK onto the PUSCH and transmit both the UL data and the HARQ-ACK.

[0053] When multiple UL signals / UL channels with different priorities overlap, the UE may control the UL transmission with the higher priority (e.g., prioritize the UL transmission with the higher priority) and not perform the UL transmission with the lower priority (e.g., drop it).

[0054] When UL data / HARQ-ACK (or UL channel for transmitting UL data / HARQ-ACK) set to a first priority (high) overlaps with UL data / HARQ-ACK (or UL channel for transmitting UL data / HARQ-ACK) set to a second priority (low), the UE may perform control to drop the UL data / HARQ-ACK with a lower priority and prioritize the transmission of the UL data / HARQ-ACK with a higher priority. Note that the UE may change (e.g., postpone or shift) the transmission timing of the UL transmission with a lower priority.

[0055] When more than two (or three or more) UL signals / UL channels overlap in the time domain, transmission may be controlled in two steps: In step 1, one UL channel is selected to multiplex UL signals transmitted by UL transmissions with the same priority; and in step 2, among UL transmissions with different priorities, control may be performed so that UL transmissions with higher priority are transmitted first and UL transmissions with lower priority are dropped.

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

[0057] (Simultaneous Transmission / Multiplexing of UL Transmissions with Different Priorities) There may be cases where multiple UL transmissions transmitted on different carriers (or cells, CCs) overlap in the time domain and have different priorities.

[0058] For example, when UL channels / UL signals are scheduled on different inter-cell carriers supported by different RFs (Radio Frequencies), transmitting each UL channel / UL signal is beneficial from the viewpoint of low latency and spectral efficiency. When a UE supports RF processing for each of different carriers (CCs), transmitting each UL channel / UL signal on each carrier can improve resource utilization efficiency and reduce latency.

[0059] For example, for each UE that supports inter-band carrier aggregation (e.g., inter-band CA) functionality, it may be supported that simultaneous PUCCH / PUSCH transmissions with different priorities (e.g., PHY priorities) in different cells are RRC configured within the same PUCCH group.

[0060] Alternatively, when multiple UL transmissions with different priorities are scheduled intra-cell / inter-cell, multiplexing of UL transmissions with different priorities (e.g., transmitting using the same UL channel) may be supported. For example, multiple UL transmissions with a certain priority may be multiplexed onto an UL channel for UL transmissions with another priority.

[0061] Whether or not to multiplex / map (e.g., enable / disable, or activate / deactivate) a UCI (e.g., HARQ-ACK) to an UL channel (e.g., PUSCH) having a different priority from the UCI may be configured by higher layer signaling.

[0062] In Rel. 17, when a low-priority HARQ-ACK (LP HARQ-ACK) is multiplexed onto a high-priority PUSCH (HP PUSCH), support for a beta offset of 0 < beta offset < 1 is being considered. Also, for the case where LP HARQ-ACK is multiplexed onto the HP PUSCH and the case where HP HARQ-ACK is multiplexed onto the LP PUSCH, setting an index related to the beta offset that is different from that for other cases is being considered.

[0063] For example, it is under consideration to newly define a beta offset information element for LP HARQ-ACK multiplexed in HP dynamic PUSCH (which may be referred to as BetaOffsetsCrossPri0 IE, for example), a beta offset information element for HP HARQ-ACK multiplexed in LP dynamic PUSCH (which may be referred to as BetaOffsetsCrossPri1 IE, for example), etc. Note that these beta offset information elements may include parameters equivalent to betaOffsetACK-Index1, betaOffsetACK-Index2, and betaOffsetACK-Index3 of the existing beta offset information element (BetaOffsets IE) (parameters related to CSI Part 1 and CSI Part 2 may not be included).

[0064] Also under consideration are parameters / information elements in which the existing betaOffsets parameter (betaOffsets), the betaOffsets parameter for DCI format 0_2 (betaOffsetsDCI-0-2), and the existing beta offset information element (BetaOffsets IE) in the CG-UCI-OnPUSCH information element (CG-UCI-OnPUSCH IE) are replaced with the above-mentioned BetaOffsetsCrossPri0 IE or BetaOffsetsCrossPri1 IE (for example, betaOffsetsCrossPri0-r17, betaOffsetsCrossPri1-r17, betaOffsetsCrossPri0DCI-0-2-r17, betaOffsetsCrossPri1DCI-0-2-r17, CG-betaOffsetsCrossPri0, CG-betaOffsetsCrossPri1).

[0065] (Two-Codeword PUSCH Transmission) In Rel. 15 / 16 NR, a UE transmits one codeword (CW) using one PUSCH. In Rel. 17 NR, support for a UE to transmit more than one CW using one PUSCH is being considered. For example, support for two CW transmissions for ranks 5-8 and two CW transmissions for ranks 2-8 is being considered.

[0066] Also, while Rel. 15 and Rel. 16 UEs are expected to use only one beam and panel for UL transmission at a given time, Rel. 17 and later consider simultaneous UL transmission (e.g., PUSCH transmission) of multiple beams and multiple panels for one or more TRPs to improve UL throughput and reliability.

[0067] The base station may use the UL TCI or panel ID to configure or indicate panel-specific transmission for UL transmission. The UL TCI (UL TCI state) may be based on signaling similar to the DL beam indication supported in Rel. 15. The panel ID may be implicitly or explicitly applied to the target RS resource (or target RS resource set) and / or PUCCH / PUSCH / SRS / PRACH transmissions. When the panel ID is explicitly signaled, the panel ID may be configured in at least one of the target RS, target channel, and reference RS (e.g., DL RS resource configuration or spatial relationship information).

[0068] For simultaneous multi-panel UL transmission, support for 2CW PUSCHs with ranks (layers) of 4 or less is being considered.

[0069] In the case where UCI on PUSCH is used in 2CW PUSCH (hereinafter also referred to as UCI on 2CW PUSCH), the UCI may be multiplexed only on one transport block (TB) (e.g., only on the TB corresponding to the lower TB index), or may be divided into two parts and each part may be multiplexed on a different transport block (TB), or may be copied and the same UCI may be multiplexed on each TB.

[0070] However, how to set a beta offset for a UCI-on-2 CW PUSCH has not yet been studied. For example, whether the same beta offset setting should be used in a case where a UCI-on-PUSCH is used in a 1 CW PUSCH (hereinafter also referred to as a UCI-on-1 CW PUSCH) and in a case where a UCI-on-2 CW PUSCH is used has not yet been studied. If UCI-on-PUSCH transmission for multiple CWs is not performed appropriately, there is a risk that throughput will decrease and communication quality will deteriorate.

[0071] Therefore, the present inventors have devised a method for setting a beta offset suitable for 2 CW PUSCH.

[0072] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the drawings. Wireless communication methods according to the embodiments may be applied independently or in combination.

[0073] In the present disclosure, "A / B" and "at least one of A and B" may be interpreted interchangeably. Also, in the present disclosure, "A / B / C" may mean "at least one of A, B, and C."

[0074] In the present disclosure, terms such as activate, deactivate, indicate, select, configure, update, and determine may be read interchangeably. In the present disclosure, terms such as support, control, controllable, operate, and operate may be read interchangeably.

[0075] In the present disclosure, Radio Resource Control (RRC), RRC parameters, RRC messages, higher layer parameters, information elements (IEs), configuration, etc. may be interchangeable. In the present disclosure, Medium Access Control control elements (MAC Control Elements (CEs)), update commands, activation / deactivation commands, etc. may be interchangeable. Note that configuration may be performed (or notified) based on RRC signaling, and activation / deactivation may be performed (or notified) based on MAC CEs.

[0076] In the present disclosure, higher layer signaling may be, for example, any one of Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information, etc., or a combination thereof.

[0077] In the present disclosure, MAC signaling may use, for example, a MAC Control Element (MAC CE), a MAC Protocol Data Unit (PDU), etc. Broadcast information may be, for example, a Master Information Block (MIB), a System Information Block (SIB), Remaining Minimum System Information (RMSI), Other System Information (OSI), etc.

[0078] In the present disclosure, physical layer signaling may be, for example, Downlink Control Information (DCI), Uplink Control Information (UCI), and the like.

[0079] In the present disclosure, the terms index, identifier (ID), indicator, resource ID, etc. may be interchangeable. In the present disclosure, the terms sequence, list, set, group, cluster, subset, etc. may be interchangeable.

[0080] In the present disclosure, the terms panel, UE panel, panel group, beam, beam group, precoder, Uplink (UL) transmitting entity, Transmission / Reception Point (TRP), base station, Spatial Relation Information (SRI), spatial relation, SRS Resource Indicator (SRI), Control Resource Set (CORESET), Physical Downlink Shared Channel (PDSCH), Codeword (CW), Transport Block (TB), Reference Signal (RS), antenna port (e.g., Demodulation Reference Signal (DMRS) port), antenna port group (e.g., DMRS port group), group (e.g., spatial relation group, Code Division Multiplexing (CDM) group, reference signal group, CORESET group, Physical Uplink Control Channel (PUCCH) group, PUCCH resource group), resource (e.g., reference signal resource, SRS resource), resource set (e.g., reference signal resource set), CORESET pool, downlink Transmission Configuration Indication state (TCI state) (DL TCI state), uplink TCI state (UL TCI state), unified TCI state, common TCI state, Quasi-Co-Location (QCL), QCL assumption, etc. may be read as interchangeable.

[0081] Furthermore, the spatial relationship information identifier (ID) (TCI state ID) and the spatial relationship information (TCI state) may be interchangeable. The "spatial relationship information" may be interchangeable with "set of spatial relationship information," "one or more pieces of spatial relationship information," etc. The TCI state and the TCI may be interchangeable with each other.

[0082] In the present disclosure, X CW PUSCH (X is an integer, for example, X=1, 2, ...) may be interchangeably read as a PUSCH for transmitting X CWs, a PUSCH for X CWs, etc. Also, 1 CW PUSCH and 2 CW PUSCH may be interchangeably read as a PUSCH for a first number of CWs and a PUSCH for a second number of CWs, respectively. The first number and the second number may each be any integer.

[0083] In the present disclosure, UCI on PUSCH for X CW PUSCH (or transmission of UCI using X CW PUSCH) may be read as UCI on X CW PUSCH, and vice versa.

[0084] Dynamic PUSCH may be interchangeably read as PUSCH that is dynamically scheduled by the DCI format.

[0085] The subsequent DCI format 0_2 may be replaced with a specific DCI format (e.g., any future DCI format).

[0086] In the present disclosure, the terms field, parameter, information element (IE), etc. may be read interchangeably.

[0087] In the present disclosure, the terms repetition (one repetition), occasion, and channel may be interchangeable. In the present disclosure, the terms UL data, TB, CW, and UCI may be interchangeable.

[0088] In the present disclosure, two CWs transmitted using a PUSCH may have different contents or the same contents, and the PUSCH transmitting the two CWs may be regarded as one PUSCH transmitted simultaneously or repeatedly.

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

[0090] The number of layers for PUSCH transmission in the following embodiments may be greater than 4 or less than 4. For example, PUSCH transmission of two CWs in the present disclosure may be performed with a number of layers less than 4 (for example, 2). In addition, the maximum number of layers is not limited to 4 or more, and may be less than 4.

[0091] Furthermore, PUSCH transmission in the following embodiments may or may not be based on the premise that multiple panels are used (it may be applied regardless of the panels).

[0092] (Wireless Communication Method) First Embodiment The first embodiment relates to a dynamic PUSCH (hereinafter referred to as a dynamic PUSCH of the first embodiment) scheduled by a DCI format other than DCI format 0_2.

[0093] For the dynamic PUSCH of the first embodiment, the UE may configure the RRC parameters for the UCI on 1 CW PUSCH and the RRC parameters for the UCI on 2 CW PUSCH separately (or independently or differently).

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

[0095] In the case of transmitting UCI on 1 CW PUSCH, the UE determines the beta offset to use based on the beta offset information element corresponding to the RRC parameters for UCI on 1 CW PUSCH. In the case of transmitting UCI on 2 CW PUSCH, the UE determines the beta offset to use based on the beta offset information element corresponding to the RRC parameters for UCI on 2 CW PUSCH.

[0096] FIG. 4 is a diagram illustrating an example of a UCI-OnPUSCH information element for a UCI on 1 CW PUSCH and a UCI-OnPUSCH information element for a UCI on 2 CW PUSCH for a dynamic PUSCH according to the first embodiment.

[0097] Note that "-rXX" in the present disclosure indicates a parameter that will be defined in 3GPP Rel. XX. The parameter name is not limited to the exemplified name (for example, the "-rXX" may be omitted). Hereinafter, parameters with "-rXX" attached may be referred to by names without the "-rXX". The 3GPP release to which the present disclosure applies is not limited to Rel. 18.

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

[0099] Furthermore, the UCI-OnPUSCH-2codeword-r18 information element includes settings for UCI on 2 CW PUSCH (betaOffsets parameter (betaOffsets-2codeword-r18), scaling parameter (scaling-2codeword-r18)) for the dynamic PUSCH of the first embodiment.

[0100] When the 2 CW PUSCH is configured in the UE, PUSCH configuration information (PUSCH-Config information element) as shown in the example of FIG. 4 may be configured in the UE, the PUSCH configuration information including a UCI-OnPUSCH information element for the UCI on 1 CW PUSCH and a UCI-OnPUSCH-2codeword-r18 information element for the UCI on 2 CW PUSCH.

[0101] FIG. 5 is a diagram illustrating an example of betaOffsets parameters and scaling parameters for UCI on 1 CW PUSCH and betaOffsets parameters and scaling parameters for UCI on 2 CW PUSCH for the dynamic PUSCH according to the first embodiment.

[0102] In the example of Fig. 5, the betaOffsets parameter (betaOffsets) and the scaling parameter (scaling) defined in Rel. 15 / 16 NR, which are included in one UCI-OnPUSCH information element, correspond to the betaOffsets parameter and the scaling parameter for the UCI on 1 CW PUSCH for the dynamic PUSCH of the first embodiment.

[0103] Furthermore, a new betaOffsets parameter (betaOffsets-2codeword-r18) and a new scaling parameter (scaling-2codeword-r18) included in one UCI-OnPUSCH information element correspond to the betaOffsets parameter and the scaling parameter for the UCI on 2 CW PUSCH for the dynamic PUSCH of the first embodiment.

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

[0105] 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 the dynamic PUSCH according to the first embodiment.

[0106] In the example of Fig. 6, the new UCI-OnPUSCH information element (UCI-OnPUSCH-r18) includes a setting for a UCI on 1 CW PUSCH and a setting for a UCI on 2 CW PUSCH for the dynamic PUSCH of the first embodiment. For example, when the betaOffsets parameter includes "dynamic," the first four of the BetaOffsets information elements of size 8 (i.e., eight) corresponding to the "dynamic" setting may correspond to the BetaOffsets information elements for the UCI on 1 CW PUSCH, and the last four may correspond to the BetaOffsets information elements for the UCI on 2 CW PUSCH. Note that "first" and "last" may be reversed.

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

[0108] Furthermore, among the enumeration types (ENUMERATED types) of size 2 (i.e., two types) corresponding to the scaling parameters, the first one may correspond to the scaling parameter for UCI on 1 CW PUSCH, and the last one may correspond to the scaling parameter for UCI on 2 CW PUSCH. Note that the terms "first" and "last" may be reversed.

[0109] 2. When the CW 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 the new UCI-OnPUSCH information element is notified, the existing UCI-OnPUSCH information element (UCI-OnPUSCH) may be ignored by the UE. When the new UCI-OnPUSCH information element is notified, the UE does not need to expect the existing UCI-OnPUSCH information element (UCI-OnPUSCH) to be notified.

[0110] Note that a new BetaOffsets information element (e.g., BetaOffsets-r18) composed 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 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. Also, in the example of Fig. 6, "semiStatic" may include BetaOffsets-r18 instead of the BetaOffsets information element of size 2.

[0111] In the first embodiment, at least one RRC parameter (e.g., at least one of a UCI-OnPUSCH information element, a betaOffsets parameter, a scaling parameter, and a BetaOffsets information element) may be commonly used between the UCI on 1 CW PUSCH and the UCI on 2 CW PUSCH. In this case, for example, the betaOffsets-2codeword-r18, scaling-2codeword-r18, and the like described above in Figs. 4 and 5 may not be included in UCI-OnPUSCH-2codeword-r18 or UCI-OnPUSCH, and the scaling parameter in Fig. 6 may include only one enumeration type.

[0112] [First Modification of First Embodiment] The above-described first embodiment is based on the assumption that, for UCI on 2 CW PUSCH, the same betaOffsets / scaling is referenced (used) when UCI is multiplexed into a first CW (e.g., referred to as CW1, but may also be referred to as CW0) and when UCI is multiplexed into a second CW (e.g., referred to as CW2, but may also be referred to as CW1). On the other hand, different betaOffsets / scaling may be referenced in these cases. This modification will be described below.

[0113] [[Modification 1-1 of First Embodiment]] In Modification 1-1 of the first embodiment, the RRC parameters defined in Rel. 15 / 16 NR (e.g., at least one of a UCI-OnPUSCH information element, a betaOffsets parameter, a scaling parameter, and a BetaOffsets information element) may correspond to a setting for UCI on 1 CW PUSCH and a setting for the first CW in UCI on 2 CW PUSCH.

[0114] When the UCI on 2 CW PUSCH is configured for a UE, the UE may be configured with one set of new RRC parameters for the UCI on 2 CW PUSCH (at least one of betaOffsets-2codeword-r18, scaling-2codeword-r18, UCI-OnPUSCH-2codeword-r18, etc.) as described in the first embodiment.

[0115] When UCI on 2 CW PUSCH is configured for a UE, the RRC parameters defined in Rel. 15 / 16 NR may be used for the first CW in UCI on 2 CW PUSCH, and one set of the new RRC parameters may be used for the second CW in UCI on 2 CW PUSCH.

[0116] [[Modification 1-2 of First Embodiment]] In Modification 1-2 of the first embodiment, the RRC parameters defined in Rel. 15 / 16 NR (for example, at least one of the UCI-OnPUSCH information element, the betaOffsets parameter, the scaling parameter, and the BetaOffsets information element) may correspond only to the configuration for UCI on 1 CW PUSCH and may not correspond to the configuration for UCI on 2 CW PUSCH.

[0117] When the UE is configured with UCI on 2 CW PUSCH, the UE may be configured with two sets of new RRC parameters for UCI on 2 CW PUSCH (at least one of betaOffsets-2codeword-r18, scaling-2codeword-r18, UCI-OnPUSCH-2codeword-r18, etc.) as described in the first embodiment.

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

[0119] [[Variant 1-3 of First Embodiment]] In variant 1-3 of the first embodiment, the same betaOffsets / scaling may be referenced when UCI is multiplexed into a PUSH related to the same panel and when UCI is multiplexed into a PUSH related to a different panel, or different betaOffsets / scaling may be referenced.

[0120] Modification 1-3 of the first embodiment may correspond to an embodiment in which, in the above-mentioned modifications 1-1 / 1-2, "the first CW in the UCI on 2 CW PUSCH" is read as "a case in which UCI is multiplexed in a PUSCH related to the same panel," and "the second CW in the UCI on 2 CW PUSCH" is read as "a case in which UCI is multiplexed in a PUSCH related to a different panel." Note that these readings may be reversed.

[0121] [Modification 2 of First Embodiment] In the first embodiment and Modification 1, of "dynamic (or dynamic-2codeword-r18)" and "semiStatic (or semiStatic-2codeword-r18)" constituting the betaOffsets parameter (betaOffsets or betaOffsets-2codeword-r18), both may be used for the UCI on 2 CW PUSCH, or only one of them (for example, only "dynamic (or dynamic-2codeword-r18)") may be used for the UCI on 2 CW PUSCH. Note that when only one of them (for example, only "dynamic (or dynamic-2codeword-r18)") is used for the UCI on 2 CW PUSCH, the other (for example, "semiStatic (or semiStatic-2codeword-r18)") does not need to be included in the betaOffsets parameter.

[0122] [Variation 3 of First Embodiment] In the first embodiment and variations 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 and may be used to determine a beta offset for transmitting UCI on 2 CW PUSCH for DCI format 0_1.

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

[0124] Second Embodiment The second embodiment relates to a dynamic PUSCH scheduled by DCI format 0_2 (hereinafter referred to as a dynamic PUSCH of the second embodiment).

[0125] For the dynamic PUSCH of the second embodiment, the UE may configure the RRC parameters for the UCI on 1 CW PUSCH and the RRC parameters for the UCI on 2 CW PUSCH separately (or independently or differently).

[0126] These RRC parameters may correspond to at least one of a UCI-OnPUSCH information element for DCI format 0_2 (UCI-OnPUSCH-DCI-0-2 IE), a 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).

[0127] The second embodiment is a modification of the first embodiment (including modifications 1-5) in that the RRC parameters defined in Rel. 15 / 16 NR (for example, a UCI-OnPUSCH information element (UCI-OnPUSCH IE), a betaOffsets parameter (betaOffsets), a scaling parameter (scaling), and a BetaOffsets information element (BetaOffsets IE)) are replaced with RRC parameters defined in Rel. 16 NR (for example, a UCI-OnPUSCH information element for DCI format 0_2 (UCI-OnPUSCH-DCI-0-2 IE), a betaOffsets parameter for DCI format 0_2 (betaOffsetsDCI-0-2), a scaling parameter for DCI format 0_2 (scalingDCI-0-2), a BetaOffsets information element (BetaOffsets IE)).

[0128] The second embodiment is a modification of the first embodiment (including Modification 1-5) in that new RRC parameters for UCI on 2 CW PUSCH (e.g., UCI-OnPUSCH information element (UCI-OnPUSCH-2codeword-r18 IE / UCI-OnPUSCH-r18 IE), betaOffsets parameter (betaOffsets-2codeword-r18), scaling parameter (scaling-2codeword-r18), BetaOffsets information element (BetaOffsets IE / BetaOffsets-2codeword-r18)) are added to corresponding new RRC parameters for DCI format 0_2 (e.g., UCI-OnPUSCH information element for DCI format 0_2 (UCI-OnPUSCH-DCI-0-2-2codeword-r18)). IE), a betaOffsets parameter for DCI format 0_2 (betaOffsetsDCI-0-2-2codeword-r18), a scaling parameter for DCI format 0_2 (scalingDCI-0-2-2codeword-r18), or a BetaOffsets information element (BetaOffsets IE / BetaOffsets-2codeword-r18). Note that the BetaOffsets information element may be replaced with a new BetaOffsets information element for DCI format 0_2.

[0129] FIG. 7 is a diagram illustrating an example of betaOffsets parameters and scaling parameters for UCI on 1 CW PUSCH and betaOffsets parameters and scaling parameters for UCI on 2 CW PUSCH for a dynamic PUSCH according to the second embodiment.

[0130] In the example of Figure 7, the betaOffsets parameter (betaOffsetsDCI-0-2-r16) and the scaling parameter (scalingDCI-0-2) defined in Rel. 16 NR and included in one UCI-OnPUSCH information element (UCI-OnPUSCH-DCI-0-2-r16) may correspond to the betaOffsets parameter and the scaling parameter for the UCI on 1 CW PUSCH for the dynamic PUSCH of the second embodiment.

[0131] Furthermore, a new betaOffsets parameter (betaOffsetsDCI-0-2-2codeword-r18) and a new scaling parameter (scalingDCI-0-2-2codeword-r18) included in one UCI-OnPUSCH information element (UCI-OnPUSCH-DCI-0-2-r16) may correspond to the betaOffsets parameter and the scaling parameter for the UCI on 2 CW PUSCH for the dynamic PUSCH of the second embodiment.

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

[0133] <Third Embodiment> The third embodiment relates to CG PUSCH.

[0134] For the CG PUSCH of the third embodiment, the UE may configure the RRC parameters for the UCI on 1 CW PUSCH and the RRC parameters for the UCI on 2 CW PUSCH separately (or independently or differently).

[0135] These RRC parameters may correspond to at least one of a CG-UCI-OnPUSCH information element for CG PUSCH (CG-UCI-OnPUSCH IE), a BetaOffsets information element (BetaOffsets IE), and a betaOffset parameter for CG-UCI in CG PUSCH (betaOffsetCG-UCI-r16).

[0136] In the case of transmitting UCI on 1 CW PUSCH, the UE determines the beta offset to use based on the beta offset information element corresponding to the RRC parameters for UCI on 1 CW PUSCH. In the case of transmitting UCI on 2 CW PUSCH, the UE determines the beta offset to use based on the beta offset information element corresponding to the RRC parameters for UCI on 2 CW PUSCH.

[0137] FIG. 8 is a diagram illustrating an example of a CG-UCI-OnPUSCH information element for a UCI-on-1 CW PUSCH and a CG-UCI-OnPUSCH information element for a UCI-on-2 CW PUSCH, for the CG PUSCH according to the third embodiment.

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

[0139] Furthermore, the CG-UCI-OnPUSCH-2codeword-r18 information element includes a setting for UCI on 2 CW PUSCH (one or more BetaOffsets information elements corresponding to "dynamic" or "semiStatic") when UCI (HARQ-ACK / CSI) not including CG-UCI is transmitted on CG PUSCH.

[0140] Furthermore, in the example of Figure 8, the betaOffset parameter for CG-UCI in CG PUSCH (betaOffsetCG-UCI-r16) defined in Rel. 16 NR indicates an index related to the beta offset for UCI on 1 CW PUSCH when only CG-UCI is transmitted on the CG PUSCH.

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

[0142] When a 2 CW PUSCH (or a 2 CW CG PUSCH) is configured in a UE, CG PUSCH configuration information (ConfiguredGrantConfig information element) as shown in the example of FIG. 8 may be configured in the UE. The CG-UCI-OnPUSCH information element / CG-UCI for a UCI on 1 CW PUSCH and the CG-UCI-OnPUSCH information element / CG-UCI for a UCI on 2 CW PUSCH include a new betaOffset parameter for the CG-UCI.

[0143] 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 the CG PUSCH according to the third embodiment.

[0144] In the example of FIG. 9, the new CG-UCI-OnPUSCH information element (CG-UCI-OnPUSCH-r18) includes configuration for UCI on 1 CW PUSCH and configuration for UCI on 2 CW PUSCH for the dynamic PUSCH of the first embodiment.

[0145] In the example of Fig. 9, a 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 includes configurations for UCI on 1 CW PUSCH (one or more BetaOffsets information elements corresponding to "dynamic" or "semiStatic") when UCI (HARQ-ACK / CSI) not including CG-UCI is transmitted on CG PUSCH.

[0146] Furthermore, a 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 includes configurations for UCI on 2 CW PUSCH (one or more BetaOffsets information elements corresponding to "dynamic" or "semiStatic") when UCI (HARQ-ACK / CSI) not including CG-UCI is transmitted on CG PUSCH.

[0147] The betaOffset parameters for CG-UCI (betaOffsetCG-UCI-r16, betaOffsetCG-UCI-2codeword-r18) are the same as those described with reference to FIG. 8, and therefore will not be described again.

[0148] 2. When the 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.

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

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

[0151] The fourth embodiment may correspond to an embodiment in which the first to third embodiments described so far are reinterpreted in the above case.

[0152] One embodiment of the fourth embodiment may correspond to an embodiment in which the following changes are made to the first embodiment (including modifications 1-5): RRC parameters defined in Rel. 15 / 16 NR (for example, betaOffsets parameter (betaOffsets), beta offsets information element (BetaOffsets IE)) are changed to those defined in Rel. 17 NR may be defined in the corresponding RRC parameters related to multiplexing of different priorities (for example, the betaOffsets parameter (betaOffsetsCrossPri0-r17) for the LP HARQ-ACK multiplexed in the HP dynamic PUSCH, the betaOffsets parameter (betaOffsetsCrossPri1-r17) for the HP HARQ-ACK multiplexed in the LP dynamic PUSCH, the beta offset information element (BetaOffsetsCrossPri0 IE) for the LP HARQ-ACK multiplexed in the HP dynamic PUSCH, and the beta offset information element (BetaOffsetsCrossPri1 IE) for the HP HARQ-ACK multiplexed in the LP dynamic PUSCH),New RRC parameters for UCI on 2 CW PUSCH (e.g., betaOffsets parameter (betaOffsets-2codeword-r18), BetaOffsets information element (BetaOffsets IE / BetaOffsets-2codeword-r18)) are combined with corresponding new RRC parameters for multiplexing different priorities for UCI on 2 CW PUSCH (e.g., betaOffsets parameter for LP HARQ-ACK multiplexed in HP dynamic PUSCH (e.g., betaOffsetsCrossPri0-2codeword-r18), betaOffsets parameter for HP HARQ-ACK multiplexed in LP dynamic PUSCH (e.g., betaOffsetsCrossPri1-2codeword-r18), LP multiplexed in HP dynamic PUSCH (e.g., betaOffsetsCrossPri1-2codeword-r18)). Replaced with the beta offset information element for HARQ-ACK (e.g., BetaOffsetsCrossPri0-2codeword-r18 IE) and the beta offset information element for HP HARQ-ACK multiplexed in LP dynamic PUSCH (e.g., BetaOffsetsCrossPri1-2codeword-r18 IE).

[0153] One embodiment of the fourth embodiment may correspond to an embodiment in which the following modifications are made to the second embodiment (including Modifications 1-5): Corresponding RRC parameters for DCI format 0_2 defined in Rel. 16 NR (for example, the betaOffsets parameter (betaOffsetsDCI-0-2) and the BetaOffsets information element (BetaOffsets IE) for DCI format 0_2) are replaced with the corresponding RRC parameters for DCI format 0_2 defined in Rel. 16 NR. 17 NR may be defined in the corresponding RRC parameters related to multiplexing of different priorities (for example, the betaOffsets parameter for LP HARQ-ACK multiplexed in HP dynamic PUSCH (betaOffsetsCrossPri0DCI-0-2-r17), the betaOffsets parameter for HP HARQ-ACK multiplexed in LP dynamic PUSCH (betaOffsetsCrossPri1DCI-0-2-r17), the beta offset information element for LP HARQ-ACK multiplexed in HP dynamic PUSCH (BetaOffsetsCrossPri0 IE), the beta offset information element for HP HARQ-ACK multiplexed in LP dynamic PUSCH (BetaOffsetsCrossPri1 IE)),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)) are combined with corresponding new RRC parameters for UCI on 2 CW PUSCH related to multiplexing of different priorities (e.g., betaOffsets parameter for LP HARQ-ACK multiplexed in HP dynamic PUSCH (e.g., betaOffsetsCrossPri0DCI-0-2-2codeword-r18), BetaOffsets information element (BetaOffsets IE / BetaOffsets-2codeword-r18 IE)). Replace with the betaOffsets parameter for HARQ-ACK (e.g., betaOffsetsCrossPri1DCI-0-2-2codeword-r18), the beta offset information element for LP HARQ-ACK multiplexed in HP dynamic PUSCH (e.g., BetaOffsetsCrossPri0-2codeword-r18 IE), and the beta offset information element for HP HARQ-ACK multiplexed in LP dynamic PUSCH (e.g., BetaOffsetsCrossPri1-2codeword-r18 IE).

[0154] One embodiment of the fourth embodiment may correspond to an embodiment in which at least one of the following modifications is made to the third embodiment: RRC parameters defined in Rel. 15 / 16 NR or new RRC parameters for UCI on 1 CW PUSCH (e.g., CG-UCI-OnPUSCH information element (CG-UCI-OnPUSCH IE), betaOffsets parameter (betaOffsets-r18), BetaOffsets information element (BetaOffsets IE) for CG PUSCH) are added to the Rel. Corresponding RRC parameters related to multiplexing of different priorities that may be defined in 17 NR (e.g., betaOffsets parameter (CG-betaOffsetsCrossPri0) equivalent to the CG-UCI-OnPUSCH information element for LP HARQ-ACK multiplexed in HP CG PUSCH, betaOffsets parameter (CG-betaOffsetsCrossPri1) equivalent to the CG-UCI-OnPUSCH information element for HP HARQ-ACK multiplexed in LP CG PUSCH, betaOffsets parameter (e.g., betaOffsetsCrossPri0-r17) for LP HARQ-ACK multiplexed in HP PUSCH (CG PUSCH), betaOffsets parameter for HARQ-ACK (e.g., betaOffsetsCrossPri1-r17), beta offset information element for LP HARQ-ACK multiplexed in HP PUSCH (CG PUSCH) (BetaOffsetsCrossPri0 IE), beta offset information element for HP HARQ-ACK multiplexed in LP PUSCH (CG PUSCH) (BetaOffsetsCrossPri1 IE)),New RRC parameters for UCI on 2 CW PUSCH (e.g., CG-UCI-OnPUSCH information element for CG PUSCH (CG-UCI-OnPUSCH-2codeword-r18 IE), betaOffsets parameter (betaOffsets-2codeword-r18), BetaOffsets information element (BetaOffsets-2codeword-r18 IE)) are combined with corresponding new RRC parameters for multiplexing different priorities for UCI on 2 CW PUSCH (e.g., betaOffsets parameter (betaOffsets-2codeword-r18), equivalent to the CG-UCI-OnPUSCH information element for LP HARQ-ACK multiplexed in HP CG PUSCH (e.g., CG-betaOffsetsCrossPri0-2codeword-r18), betaOffsets parameter corresponding to the CG-UCI-OnPUSCH information element for HP HARQ-ACK multiplexed in the HP PUSCH (CG PUSCH) (e.g., CG-betaOffsetsCrossPri1-2codeword-r18), betaOffsets parameter corresponding to the CG-UCI-OnPUSCH information element for HP HARQ-ACK multiplexed in the HP PUSCH (CG PUSCH) (e.g., betaOffsetsCrossPri0-2codeword-r18), betaOffsets parameter corresponding to the CG-UCI-OnPUSCH information element for HP HARQ-ACK multiplexed in the HP PUSCH (CG PUSCH) (e.g., be ... Replaced with the beta offset information element for HARQ-ACK (e.g., BetaOffsetsCrossPri0-2codeword-r18 IE) and the beta offset information element for HP HARQ-ACK multiplexed in LP PUSCH (CG PUSCH) (e.g., BetaOffsetsCrossPri1-2codeword-r18 IE).

[0155] In the fourth embodiment, when an RRC parameter related to enabling (application of) a configuration extension of a beta offset for multiplexing different priorities is configured, the UE may use the existing RRC parameter related to the beta offset of Rel. 15 / 16 as a configuration for the HP (LP) HARQ-ACK multiplexed in the LP (HP) PUSCH, and may use the newly defined RRC parameter related to the beta offset as a configuration for the LP (HP) HARQ-ACK multiplexed in the HP (LP) PUSCH.

[0156] Furthermore, in the fourth embodiment, when an RRC parameter related to enabling (applying) a configuration extension of a beta offset for multiplexing of different priorities is configured, the UE may ignore the RRC parameters related to the beta offset of the existing Rel. 15 / 16 (even if configured). When an RRC parameter related to enabling (applying) a configuration extension of a beta offset for multiplexing of different priorities is configured, the UE may be configured with two sets of RRC parameters related to the beta offset. In this case, the UE may use the RRC parameters related to the beta offset of the first set of the two sets as a configuration for the HP (LP) HARQ-ACK multiplexed in the LP (HP) PUSCH, and may use the RRC parameters related to the beta offset of the second set of the two sets as a configuration for the LP (HP) HARQ-ACK multiplexed in the HP (LP) PUSCH.

[0157] Furthermore, in the fourth embodiment, if an RRC parameter related to enabling (applying) an extension to the beta offset configuration for multiplexing different priorities is not configured, the UE may use an RRC parameter related to the beta offset of the existing Rel. 15 / 16 to determine the beta offset.

[0158] According to the fourth embodiment described above, the UE can appropriately determine the beta offset for 2 CW PUSCHs even in the case of multiplexing of different priorities (for example, the case of multiplexing HP HARQ-ACK in LP PUSCH, or the case of multiplexing LP HARQ-ACK in HP PUSCH).

[0159] <Supplementary Note> In the above-described embodiment, the beta offset indicator field of the DCI may not be extended, but the interpretation of the bit value may differ from the existing one. When the DCI schedules (indicates / implies) a 2CW PUSCH, the beta offset indicator field may indicate the configuration for the 2CW PUSCH. For example, a beta offset indicator field of "01" included in a DCI scheduling a 2CW PUSCH may indicate the second offset index (corresponding to the beta offset information element) provided by the RRC for the 2CW PUSCH.

[0160] Furthermore, the extension may not be necessary, but the interpretation of the bit value may differ from the existing one. When a DCI schedules a 2CW PUSCH and different beta offsets are used for the first CW and the second CW, the beta offset indicator field may indicate the configuration for the first CW and the configuration for the second CW. For example, a beta offset indicator field of "01" included in a DCI scheduling a 2CW PUSCH may indicate the second offset index (the corresponding beta offset information element for the first CW and the beta offset information element for the second CW) provided by the RRC.

[0161] Furthermore, if the DCI schedules (indicates / implies) 1CW PUSCH, the beta offset indicator field may indicate the configuration for the 1CW PUSCH. For example, a beta offset indicator field value of "01" included in the DCI scheduling 1CW PUSCH may indicate a second offset index (corresponding to a beta offset information element) provided by the RRC for the 1CW PUSCH.

[0162] In the above-described embodiments, for the UCI on 2 CW PUSCH, the UCI may be multiplexed into only one TB (e.g., only into the TB corresponding to a lower TB index), or may be divided into two parts and multiplexed into different TBs, or may be copied and the same UCI may be multiplexed into each TB. In a case where the UCI on 2 CW PUSCH is multiplexed into only one TB, the UE may be configured with a beta offset setting for that TB (such as the information elements and parameters described in the above-described embodiments), but may not be configured with beta offset settings for other TBs.

[0163] It should be noted that at least one of the above-described embodiments may be applied only to UEs that have reported or support a particular UE capability.

[0164] The specific UE capability may indicate at least one of the following: - for PUSCHs scheduled by DCI formats other than DCI format 0_2, whether separate configurations are supported for UCI on 1 CW PUSCH and UCI on 2 CW PUSCH; - for PUSCHs scheduled by DCI format 0_2, whether separate configurations are supported for UCI on 1 CW PUSCH and UCI on 2 CW PUSCH; - for PUSCHs scheduled by any DCI format, whether separate configurations are supported for UCI on 1 CW PUSCH and UCI on 2 CW PUSCH; - for CG PUSCH, whether separate configurations are supported for UCI on 1 CW PUSCH and UCI on 2 CW PUSCH; Regarding PUSCH, whether or not separate settings are supported for CG-UCI on 1 CW PUSCH and CG-UCI on 2 CW PUSCH; In the case of multiplexing different priorities (for example, a case where HP HARQ-ACK is multiplexed on LP PUSCH, or a case where LP HARQ-ACK is multiplexed on HP PUSCH), whether or not separate settings are supported for CG-UCI on 1 CW PUSCH and CG-UCI on 2 CW PUSCH; Whether or not 2 CW PUSCH is supported.

[0165] Furthermore, the above-mentioned specific UE capabilities may be capabilities that apply across all frequencies (commonly regardless of frequency), capabilities for each frequency (e.g., cell, band, BWP), capabilities for each frequency range (e.g., FR1, FR2, FR3, FR4, FR5), or capabilities for each subcarrier spacing.

[0166] Furthermore, the specific UE capability may be a capability that is applied to all duplexing methods (commonly regardless of the duplexing method), or may be a capability for each duplexing method (e.g., Time Division Duplex (TDD) or Frequency Division Duplex (FDD)).

[0167] Furthermore, at least one of the above-described embodiments may be applied when specific information related to the above-described embodiments is configured in the UE by higher layer signaling. For example, the specific information may be configuration information for UCI on 2 CW PUSCH, any RRC parameters for a specific release (e.g., Rel. 18), etc.

[0168] If the UE does not support at least one of the specific UE capabilities or is not configured with the specific information, the UE may, for example, apply the behavior of Rel. 15 / 16, or may assume the same configuration (e.g., default configuration) for 1 CW PUSCH and 2 CW PUSCH, or may assume the same configuration for 1 CW PUSCH and 2 CW PUSCH if new RRC parameters indicate that this assumption is valid.

[0169] (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 embodiments of the present disclosure or a combination thereof.

[0170] 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) or 5th generation mobile communication system New Radio (5G NR) specified by the Third Generation Partnership Project (3GPP).

[0171] The wireless communication system 1 may also support dual connectivity between multiple Radio Access Technologies (RATs) (Multi-RAT Dual Connectivity (MR-DC)). MR-DC may include dual connectivity between LTE (Evolved Universal Terrestrial Radio Access (E-UTRA)) and NR (E-UTRA-NR Dual Connectivity (EN-DC)), dual connectivity between NR and LTE (NR-E-UTRA Dual Connectivity (NE-DC)), etc.

[0172] 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.

[0173] The wireless communication system 1 may support dual connectivity between multiple base stations within the same RAT (for example, dual connectivity in which both the MN and SN are NR base stations (gNBs) (NR-NR Dual Connectivity (NN-DC))).

[0174] The wireless communication system 1 may include a base station 11 that forms a macrocell C1 with a relatively wide coverage, and base stations 12 (12a-12c) that are located within the macrocell C1 and form small cells C2 that are smaller than the macrocell C1. A user terminal 20 may be located within at least one of the cells. The locations and numbers of the cells and user terminals 20 are not limited to the embodiment shown in the figure. Hereinafter, when there is no need to distinguish between the base stations 11 and 12, they will be collectively referred to as base station 10.

[0175] The user terminal 20 may be connected to at least one of the multiple base stations 10. The user terminal 20 may utilize at least one of carrier aggregation (CA) using multiple component carriers (CCs) and dual connectivity (DC).

[0176] 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)). The macro cell C1 may be included in FR1, and the small cell C2 may be included in FR2. For example, FR1 may be a frequency band of 6 GHz or less (sub-6 GHz), and FR2 may be a frequency band higher than 24 GHz (above-24 GHz). Note that the frequency bands and definitions of FR1 and FR2 are not limited to these, and for example, FR1 may correspond to a higher frequency band than FR2.

[0177] Furthermore, the user terminal 20 may perform communication using at least one of time division duplex (TDD) and frequency division duplex (FDD) in each CC.

[0178] The multiple base stations 10 may be connected by wire (e.g., optical fiber compliant with the Common Public Radio Interface (CPRI), an X2 interface, etc.) or wirelessly (e.g., NR communication). For example, when NR communication is used as a backhaul between the base stations 11 and 12, the base station 11 corresponding to the upper station may be called an Integrated Access Backhaul (IAB) donor, and the base station 12 corresponding to the relay station (relay) may be called an IAB node.

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

[0180] The user terminal 20 may be a terminal that supports at least one of communication methods such as LTE, LTE-A, and 5G.

[0181] An Orthogonal Frequency Division Multiplexing (OFDM)-based radio access scheme may be used in the wireless communication system 1. For example, 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), or the like may be used in at least one of the downlink (DL) and uplink (UL).

[0182] The radio access scheme may also be called a waveform. Note that in the wireless communication system 1, other radio access schemes (e.g., other single-carrier transmission schemes, other multi-carrier transmission schemes) may be used as the UL and DL radio access schemes.

[0183] In the wireless communication system 1, a downlink shared channel (Physical Downlink Shared Channel (PDSCH)) shared by each user terminal 20, a broadcast channel (Physical Broadcast Channel (PBCH)), a downlink control channel (Physical Downlink Control Channel (PDCCH)), etc. may be used as the downlink channel.

[0184] Furthermore, in the wireless communication system 1, an uplink shared channel (Physical Uplink Shared Channel (PUSCH)) shared by each user terminal 20, an uplink control channel (Physical Uplink Control Channel (PUCCH)), a random access channel (Physical Random Access Channel (PRACH)), or the like may be used as an uplink channel.

[0185] The PDSCH transmits user data, higher layer control information, a System Information Block (SIB), etc. The PUSCH may transmit user data, higher layer control information, etc. Furthermore, the PBCH may transmit a Master Information Block (MIB).

[0186] Lower layer control information may be transmitted by the PDCCH. The lower layer control information may include, for example, Downlink Control Information (DCI) including scheduling information for at least one of the PDSCH and the PUSCH.

[0187] Note that the DCI for scheduling the PDSCH may be referred to as a DL assignment, a DL DCI, etc., and the DCI for scheduling the PUSCH may be referred to as a UL grant, a UL DCI, etc. Note that the PDSCH may be replaced with DL data, and the PUSCH may be replaced with UL data.

[0188] A control resource set (CORESET) and a search space may be used to detect the PDCCH. The CORESET corresponds to resources for searching for DCI. The search space corresponds to a search region and a search method for 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.

[0189] 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 the terms "search space," "search space set," "search space configuration," "search space set configuration," "CORESET," "CORESET configuration," and the like in the present disclosure may be read interchangeably.

[0190] The PUCCH may transmit uplink control information (UCI) including at least one of channel state information (CSI), delivery confirmation information (which may be called, for example, Hybrid Automatic Repeat reQuest ACKnowledgement (HARQ-ACK), ACK / NACK, etc.), and scheduling request (SR). The PRACH may transmit a random access preamble for establishing a connection with a cell.

[0191] In the present disclosure, downlink, uplink, etc. may be expressed without adding "link." Also, various channels may be expressed without adding "Physical" to the beginning.

[0192] In the wireless communication system 1, a synchronization signal (SS), a downlink reference signal (DL-RS), etc. may be transmitted. In the wireless communication system 1, as the DL-RS, a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a positioning reference signal (PRS), a phase tracking reference signal (PTRS), etc. may be transmitted.

[0193] 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 an SS (PSS, SSS) and a PBCH (and a DMRS for the PBCH) may be referred to as an SS / PBCH block, an SS Block (SSB), or the like. Note that the SS, SSB, and the like may also be referred to as a reference signal.

[0194] Furthermore, in the wireless communication system 1, a sounding reference signal (SRS), a demodulation reference signal (DMRS), or the like may be transmitted as an uplink reference signal (UL-RS). Note that the DMRS may also be called a user equipment-specific reference signal (UE-specific reference signal).

[0195] 11 is a diagram showing an example of the configuration of a base station according to an embodiment. The base station 10 includes a control unit 110, a transceiver unit 120, a transceiver antenna 130, and a transmission line interface 140. Note that the base station may include one or more of each of the control unit 110, the transceiver unit 120, the transceiver antenna 130, and the transmission line interface 140.

[0196] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the base station 10 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0197] The control unit 110 performs overall control of the base station 10. The control unit 110 can be configured from a controller, a control circuit, and the like that are explained based on common understanding in the technical field to which the present disclosure relates.

[0198] The control unit 110 may control signal generation, scheduling (e.g., resource allocation, mapping), etc. The control unit 110 may control transmission and reception using the transceiver unit 120, the transceiver antenna 130, and the transmission path interface 140, measurement, etc. The control unit 110 may generate data, control information, sequences, etc. to be transmitted as signals, and transfer them to the transceiver unit 120. The control unit 110 may perform call processing (setting up, releasing, etc.) of communication channels, status management of the base station 10, management of radio resources, etc.

[0199] The transceiver unit 120 may include a baseband unit 121, a radio frequency (RF) unit 122, and a measurement unit 123. The baseband unit 121 may include a transmission processing unit 1211 and a reception processing unit 1212. The transceiver unit 120 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0200] The transmitting / receiving unit 120 may be configured as an integrated transmitting / receiving unit, or may be configured from a transmitting unit and a receiving unit. The transmitting unit may be configured from a transmission processing unit 1211 and an RF unit 122. The receiving unit may be configured from a reception processing unit 1212, the RF unit 122, and a measurement unit 123.

[0201] The transmitting and receiving antenna 130 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0202] The transceiver 120 may transmit the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 120 may receive the above-mentioned uplink channel, uplink reference signal, etc.

[0203] The transceiver 120 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0204] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform Packet Data Convergence Protocol (PDCP) layer processing, Radio Link Control (RLC) layer processing (e.g., RLC retransmission control), Medium Access Control (MAC) layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 110, and generate a bit string to be transmitted.

[0205] The transmitter / receiver unit 120 (transmission processing unit 1211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, Discrete Fourier Transform (DFT) processing (if necessary), Inverse Fast Fourier Transform (IFFT) processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0206] The transceiver unit 120 (RF unit 122) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 130.

[0207] On the other hand, the transceiver unit 120 (RF unit 122) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 130.

[0208] The transceiver 120 (reception processing unit 1212) may apply reception processing such as analog-to-digital conversion, Fast Fourier Transform (FFT) processing, Inverse Discrete Fourier Transform (IDFT) processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, thereby acquiring user data, etc.

[0209] The transceiver 120 (measurement unit 123) may perform measurements on the received signal. For example, the measurement unit 123 may perform Radio Resource Management (RRM) measurements, Channel State Information (CSI) measurements, etc. based on the received signal. The measurement unit 123 may measure received power (e.g., Reference Signal Received Power (RSRP)), received quality (e.g., Reference Signal Received Quality (RSRQ), Signal to Interference plus Noise Ratio (SINR), Signal to Noise Ratio (SNR)), signal strength (e.g., Received Signal Strength Indicator (RSSI)), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 110.

[0210] The transmission path interface 140 may transmit and receive signals (backhaul signaling) between devices included in the core network 30, other base stations 10, etc., and may acquire and transmit user data (user plane data), control plane data, etc. for the user terminal 20.

[0211] The transmitting section and receiving section of the base station 10 in the present disclosure may be configured by at least one of the transmitting / receiving section 120, the transmitting / receiving antenna 130, and the transmission path interface 140.

[0212] In addition, the control unit 110 may generate first configuration information (e.g., betaOffsets, scaling, UCI-OnPUSCH) related to beta offsets for the Physical Uplink Shared Channel for one codeword, and second configuration information (e.g., betaOffsets-2codeword-r18, scaling-2codeword-r18, UCI-OnPUSCH-2codeword-r18) related to beta offsets for the Physical Uplink Shared Channel for two codewords.

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

[0214] (User Terminal) Fig. 12 is a diagram showing an example of the configuration of a user terminal according to one embodiment. The user terminal 20 includes a control unit 210, a transceiver unit 220, and a transceiver antenna 230. Note that the user terminal 20 may include one or more of each of the control unit 210, the transceiver unit 220, and the transceiver antenna 230.

[0215] In this example, the functional blocks of the characteristic parts of the present embodiment are mainly shown, and it may be assumed that the user terminal 20 also has other functional blocks necessary for wireless communication. Some of the processing of each unit described below may be omitted.

[0216] The control unit 210 performs overall control of the user terminal 20. The control unit 210 can be configured from a controller, a control circuit, etc., which are described based on common understanding in the technical field to which the present disclosure relates.

[0217] The control unit 210 may control signal generation, mapping, etc. The control unit 210 may control transmission and reception, measurement, etc. using the transceiver unit 220 and the transceiver antenna 230. The control unit 210 may generate data, control information, sequences, etc. to be transmitted as signals and transfer them to the transceiver unit 220.

[0218] The transceiver unit 220 may include a baseband unit 221, an RF unit 222, and a measurement unit 223. The baseband unit 221 may include a transmission processing unit 2211 and a reception processing unit 2212. The transceiver unit 220 may be configured with a transmitter / receiver, an RF circuit, a baseband circuit, a filter, a phase shifter, a measurement circuit, a transceiver circuit, etc., which are described based on common understanding in the technical field related to the present disclosure.

[0219] The transmitting / receiving unit 220 may be configured as an integrated transmitting / receiving unit, or may be composed of a transmitting unit and a receiving unit. The transmitting unit may be composed of a transmission processing unit 2211 and an RF unit 222. The receiving unit may be composed of a reception processing unit 2212, an RF unit 222, and a measurement unit 223.

[0220] The transmitting / receiving antenna 230 can be configured from an antenna described based on common understanding in the technical field to which the present disclosure relates, such as an array antenna.

[0221] The transceiver 220 may receive the above-mentioned downlink channel, synchronization signal, downlink reference signal, etc. The transceiver 220 may transmit the above-mentioned uplink channel, uplink reference signal, etc.

[0222] The transceiver unit 220 may form at least one of the transmit beam and the receive beam using digital beamforming (e.g., precoding), analog beamforming (e.g., phase rotation), or the like.

[0223] The transceiver unit 220 (transmission processing unit 2211) may perform PDCP layer processing, RLC layer processing (e.g., RLC retransmission control), MAC layer processing (e.g., HARQ retransmission control), etc. on data, control information, etc. obtained from the control unit 210, and generate a bit string to be transmitted.

[0224] The transmitter / receiver unit 220 (transmission processing unit 2211) may perform transmission processing such as channel coding (which may include error correction coding), modulation, mapping, filtering, DFT processing (if necessary), IFFT processing, precoding, and digital-to-analog conversion on the bit string to be transmitted, and output a baseband signal.

[0225] Whether or not to apply DFT processing may be based on the setting of transform precoding. When transform precoding is enabled for a certain channel (e.g., PUSCH), the transceiver unit 220 (transmission processing unit 2211) may perform DFT processing as the transmission processing to transmit the channel using a DFT-s-OFDM waveform, and if not, it may not be necessary to perform DFT processing as the transmission processing.

[0226] The transceiver unit 220 (RF unit 222) may perform modulation, filtering, amplification, etc. on the baseband signal to a radio frequency band, and transmit the radio frequency band signal via the transceiver antenna 230.

[0227] On the other hand, the transceiver unit 220 (RF unit 222) may perform amplification, filtering, demodulation to a baseband signal, etc. on the radio frequency band signal received by the transceiver antenna 230.

[0228] The transceiver unit 220 (reception processing unit 2212) may apply reception processing such as analog-to-digital conversion, FFT processing, IDFT processing (if necessary), filtering, demapping, demodulation, decoding (which may include error correction decoding), MAC layer processing, RLC layer processing, and PDCP layer processing to the acquired baseband signal, and acquire user data, etc.

[0229] The transceiver 220 (measurement unit 223) may perform measurements on the received signal. For example, the measurement unit 223 may perform RRM measurements, CSI measurements, etc. based on the received signal. The measurement unit 223 may measure received power (e.g., RSRP), received quality (e.g., RSRQ, SINR, SNR), signal strength (e.g., RSSI), propagation path information (e.g., CSI), etc. The measurement results may be output to the control unit 210.

[0230] 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.

[0231] In addition, the transceiver unit 220 may receive first configuration information regarding beta offsets for the Physical Uplink Shared Channel for one codeword (e.g., betaOffsets, scaling, UCI-OnPUSCH) and second configuration information regarding beta offsets for the Physical Uplink Shared Channel for two codewords (e.g., betaOffsets-2codeword-r18, scaling-2codeword-r18, UCI-OnPUSCH-2codeword-r18).

[0232] The controller 210 may determine beta offsets for transmission of the physical uplink shared channel for the two codewords based on the second configuration information.

[0233] The physical uplink shared channel may be a physical uplink shared channel scheduled by a Downlink Control Information (DCI) format other than DCI format 0_2.

[0234] The physical uplink shared channel may be a physical uplink shared channel scheduled by Downlink Control Information (DCI) format 0_2.

[0235] The physical uplink shared channel may be a configured grant physical uplink shared channel.

[0236] (Hardware Configuration) Note that the block diagrams used to explain the above embodiments show functional blocks. 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 a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0237] Here, the functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, deeming, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission may be called a transmitting unit, transmitter, etc. As described above, the implementation method of each is not particularly limited.

[0238] For example, a base station, a user terminal, or the like according to 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 above-described base station 10 and user terminal 20 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, and the like.

[0239] In the present disclosure, the terms apparatus, circuit, device, section, unit, etc. may be used interchangeably. The hardware configurations of the base station 10 and the user terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

[0240] For example, although only one processor 1001 is shown, there may be multiple processors. Furthermore, processing may be performed by one processor, or processing may be performed by two or more processors simultaneously, serially, or in other ways. Furthermore, processor 1001 may be implemented by one or more chips.

[0241] Each function in the base station 10 and the user terminal 20 is realized, for example, by loading specified software (programs) onto hardware such as a processor 1001 and a memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0242] The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, at least a part of the above-mentioned control unit 110 (210), transceiver unit 120 (220), etc. may be realized by the processor 1001.

[0243] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 110 (210) may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and the other functional blocks may be implemented in a similar manner.

[0244] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically EEPROM (EEPROM), Random Access Memory (RAM), or other suitable storage medium. The memory 1002 may also be referred to as a register, cache, main memory, etc. The memory 1002 may store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.

[0245] Storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, a flexible disk, a floppy disk, a magneto-optical disk (e.g., a compact disc (e.g., a Compact Disc ROM (CD-ROM)), a digital versatile disc, a Blu-ray disc), a removable disk, a hard disk drive, a smart card, a flash memory device (e.g., a card, a stick, a key drive), a magnetic stripe, a database, a server, or other suitable storage medium. Storage 1003 may also be referred to as an auxiliary storage device.

[0246] 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, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmission / reception unit 120 (220), transmission / reception antenna 130 (230), etc. may be realized by the communication device 1004. The transmission / reception unit 120 (220) may be implemented as a transmission unit 120a (220a) and a reception unit 120b (220b) that are physically or logically separated.

[0247] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, a light emitting diode (LED) lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0248] Furthermore, 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 between each device.

[0249] Furthermore, the base station 10 and the user terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized using this hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0250] (Modifications) Note that terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, a channel, a symbol, and a signal (signal or signaling) may be interchangeable. A signal may also be a message. A reference signal may be abbreviated as RS, and may also be called a pilot, pilot signal, etc. depending on the applicable standard. A component carrier (CC) may also be called a cell, frequency carrier, carrier frequency, etc.

[0251] 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 (e.g., 1 ms) that is independent of numerology.

[0252] Here, the numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, and may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering performed by a transceiver in the frequency domain, and specific windowing performed by a transceiver in the time domain.

[0253] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may also be a time unit based on numerology.

[0254] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (PUSCH) mapping type B.

[0255] A radio frame, a subframe, a slot, a minislot, and a symbol all represent time units for transmitting signals. The radio frame, the subframe, the slot, the minislot, and the symbol may be referred to by other names corresponding to the radio frame, the subframe, the slot, the minislot, and the symbol. Note that the time units such as a frame, a subframe, a slot, a minislot, and a symbol in the present disclosure may be interchangeable.

[0256] For example, one subframe may be referred to as a TTI, or multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0257] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.

[0258] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0259] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0260] A TTI having a time length of 1 ms may be called a regular TTI (TTI in 3GPP Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0261] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

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

[0263] In addition, 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, each of which may be composed of one or more resource blocks.

[0264] In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0265] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0266] A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

[0268] 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 the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0269] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. 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 subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be changed in various ways.

[0270] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by a predetermined index.

[0271] The names used for parameters and the like in this disclosure are not intended to be limiting in any way. Furthermore, the mathematical expressions and the like using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0272] 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. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0273] Furthermore, information, signals, etc. may be output from a higher layer to a lower layer and / or from a lower layer to a higher layer. Information, signals, etc. may be input / output via multiple network nodes.

[0274] Input and output information, signals, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information, signals, etc. may be overwritten, updated, or added. Output information, signals, etc. may be deleted. Input information, signals, etc. may be transmitted to another device.

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

[0276] Note that the physical layer signaling may be referred to as Layer 1 / Layer 2 (L1 / L2) control information (L1 / L2 control signal), L1 control information (L1 control signal), etc. Furthermore, the RRC signaling may be referred to as an RRC message, such as an RRC Connection Setup message or an RRC Connection Reconfiguration message. Furthermore, the MAC signaling may be notified using, for example, a MAC Control Element (CE).

[0277] Furthermore, notification of specified information (e.g., notification that "it is X") is not limited to explicit notification, but may be made implicitly (e.g., by not notifying the specified information or by notifying other information).

[0278] The determination may be made by a value represented by one bit (0 or 1), by a Boolean value represented by true or false, or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0279] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0280] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), these wired and / or wireless technologies are included within the definition of transmission media.

[0281] As used in this disclosure, the terms "system" and "network" may be used interchangeably. A "network" may refer to devices included in the network (e.g., base stations).

[0282] In the present disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," etc. may be used interchangeably.

[0283] In the present disclosure, terms such as "base station (BS)," "radio 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," etc. may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, picocell, etc.

[0284] A base station can accommodate one or more (e.g., three) cells. When 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 can be provided with communication service by a base station subsystem (e.g., a small indoor base station (Remote Radio Head (RRH))). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

[0285] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0286] A mobile station may also be referred to as 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.

[0287] At least one of the base station and the 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, etc.

[0288] The mobile body is a movable object that can move at any speed and naturally includes cases where the mobile body is stationary. Examples of the mobile body include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, multicopters, quadcopters, balloons, and objects mounted thereon. The mobile body may also be a mobile body that moves autonomously based on an operation command.

[0289] The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may also include 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.

[0290] 14 is a diagram showing 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, axles 48, an electronic control unit 49, various sensors (including a current sensor 50, an RPM 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 unit 59, and a communication module 60.

[0291] The drive unit 41 is configured with at least one of an engine, a motor, and a hybrid of an engine and a motor, for example. The steering unit 42 includes at least a steering wheel (also called a handle) 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 a user.

[0292] The electronic control unit 49 is composed of a microprocessor 61, memory (ROM, RAM) 62, and a communication port (for example, an input / output (IO) port) 63. Signals are input to the electronic control unit 49 from various sensors 50-58 provided in the vehicle. The electronic control unit 49 may also be called an Electronic Control Unit (ECU).

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

[0294] The information service unit 59 is composed of various devices, such as a car navigation system, an audio system, speakers, a display, a television, and a radio, for providing (outputting) various information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 59 uses information acquired from external devices via the communication module 60 or the like to provide various information / services (e.g., multimedia information / multimedia services) to the occupants of the vehicle 40.

[0295] The information service unit 59 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0296] The driving assistance system unit 64 includes various devices for providing functions to prevent accidents and reduce the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., Global Navigation Satellite System (GNSS)), map information (e.g., High Definition (HD) maps, Autonomous Vehicle (AV) maps), gyro systems (e.g., Inertial Measurement Units (IMUs), Inertial Navigation Systems (INSs)), artificial intelligence (AI) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 64 also transmits and receives various information via the communication module 60 to realize driving assistance functions or autonomous driving functions.

[0297] 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 transmits and receives data (information) via the communication port 63 to and from the drive unit 41, steering unit 42, accelerator pedal 43, brake pedal 44, shift lever 45, left and right front wheels 46, left and right rear wheels 47, axles 48, the microprocessor 61 and memory (ROM, RAM) 62 in the electronic control unit 49, and the various sensors 50-58, which are provided in the vehicle 40.

[0298] 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 an external device. For example, it transmits and receives various information to and from the 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 or the user terminal 20 described above. Furthermore, the communication module 60 may be, for example, at least one of the base station 10 and the user terminal 20 described above (or may function as at least one of the base station 10 and the user terminal 20).

[0299] The communication module 60 may transmit at least one of signals from the above-mentioned various sensors 50-58 input to the electronic control unit 49, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 59 to an external device via wireless communication. The electronic control unit 49, the various sensors 50-58, the information service unit 59, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 60 may include information based on the above-mentioned input.

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

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

[0302] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple user terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the user terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "sidelink"). For example, terms such as an uplink channel and a downlink channel may be read as a sidelink channel.

[0303] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station 10 may be configured to have the functions of the user terminal 20 described above.

[0304] In the present disclosure, an operation described as being performed by a base station may be performed by its upper node in some cases. It is apparent that in a network including 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 (such as, but not limited to, a Mobility Management Entity (MME), a Serving-Gateway (S-GW), etc.), or a combination thereof.

[0305] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, the order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0306] Each aspect / embodiment described in the present disclosure may be a technology other than 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, for example, an integer or decimal number)), 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 (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802. The present invention may be applied to systems that use IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable wireless communication methods, or to next-generation systems that are expanded, modified, created, or defined based on these. Furthermore, the present invention may be applied to a combination of multiple systems (e.g., a combination of LTE or LTE-A and 5G).

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

[0308] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0309] The term "determining" as used in this disclosure may encompass a wide variety of actions. For example, "determining" may be considered to be judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., looking up in a table, database, or another data structure), ascertaining, etc.

[0310] Additionally, "determining" may be considered to be "determining" receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), etc.

[0311] Also, "determination" may be considered to be "deciding" resolving, selecting, choosing, establishing, comparing, etc. In other words, "determination" may be considered to be "deciding" some action.

[0312] Furthermore, "judgment (decision)" may be read as "assuming," "expecting," "considering," or the like.

[0313] As used in this disclosure, the terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may 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, "connected" may be read as "access."

[0314] In this disclosure, when two elements are connected, they may be considered to be "connected" or "coupled" to one another using one or more wires, cables, printed electrical connections, etc., as well as using electromagnetic energy having wavelengths in the radio frequency range, microwave range, light (both visible and invisible) range, etc., as some non-limiting and non-exhaustive examples.

[0315] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0316] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0317] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0318] Although the invention according to the present disclosure has been described in detail above, it is clear to 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 in modified and altered forms without departing from the spirit and scope of the invention as defined by the description of the claims. Therefore, the description of the present disclosure is intended to be illustrative and explanatory and does not impose any limiting meaning on the invention according to the present disclosure.

Claims

1. A method for transmitting a beta offset of a physical uplink shared channel for two codewords, comprising: a control unit that determines a beta offset for transmitting the physical uplink shared channel based on the configuration information, When transmitting uplink control information using the physical uplink shared channel, the controller multiplexes the uplink control information into one of the two codewords.

2. The terminal of claim 1 , wherein the one codeword corresponds to a lower index.

3. A method for receiving configuration information regarding beta offsets of a physical uplink shared channel for two codewords; determining a beta offset for transmission of the physical uplink shared channel based on the configuration information; when transmitting uplink control information using the physical uplink shared channel, multiplexing the uplink control information into one of the two codewords.

4. A control unit that generates configuration information regarding a beta offset of a physical uplink shared channel for two codewords; A transmission unit that transmits the setting information, a base station, in a case where uplink control information is transmitted in a terminal using the physical uplink shared channel, the uplink control information is multiplexed into one of the two codewords.

5. A system having a terminal and a base station, The terminal includes a receiver for receiving configuration information regarding a beta offset of a physical uplink shared channel for two codewords; a control unit that determines a beta offset for transmitting the physical uplink shared channel based on the configuration information, When transmitting uplink control information using the physical uplink shared channel, the controller multiplexes the uplink control information into one of the two codewords; The base station includes a control unit that generates the setting information; A transmission unit that transmits the setting information.