Method and apparatus for transmitting and receiving uplink channel in wireless communication system

Abstract

A method according to an embodiment of the present specification comprises the steps of: receiving configuration information related to a PUSCH; receiving a DCI including an NDI field; and transmitting the PUSCH based on the DCI. The transform precoder indicator field is based on one bit based on configuring a parameter related to the presence of the transform precoder indicator field within the DCI according to the configuration information. The 1-bit is characterized by being reserved based on i) the CRC related to the DCI being scrambled by the RNTI and ii) the value of the NDI field being 0.

Description

Technical Field

[0001] This disclosure relates to methods and apparatus for transmitting and receiving uplink channels in a wireless communication system. Background Technology

[0002] Mobile communication systems have been developed to provide voice services while ensuring user activity. However, mobile communication systems have expanded beyond voice to include data services. Currently, due to the explosive growth of business, resources are insufficient, and users demand higher-speed services. Therefore, more advanced mobile communication systems are needed.

[0003] The requirements for next-generation mobile communication systems necessitate support for explosive data traffic acceptance, a dramatic increase in data rates per user, a significant increase in the number of connected devices, very low end-to-end latency, and high energy efficiency. To this end, various technologies have been investigated, including dual connectivity, massive MIMO, in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, and networking devices.

[0004] On the other hand, the UL waveform is configured semi-statically according to existing operations. The UL waveform can vary based on whether transform precoding is applied or enabled. This will be described in detail below.

[0005] 1) When transform precoding is applied (i.e., when transform precoding is enabled), the waveform is based on Discrete Fourier Transform-Extended-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM).

[0006] 2) When transform precoding is not applied (i.e., when transform precoding is disabled), the waveform is based on cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM).

[0007] Semi-static configuration / indication of whether transform precoding is enabled.

[0008] For example, whether to enable transform precoding can be determined based on the RRC parameter: i) when the transformPrecoder parameter is configured based on PUSCH-config, whether to enable transform precoding can be determined based on the transformPrecoder parameter; ii) when the transformPrecoder parameter is not configured, whether to enable transform precoding can be determined based on the msg3-transformPrecoder parameter.

[0009] With the Rel-18 coverage enhancements, Dynamic Waveform Switching (DWS) operations related to the aforementioned UL waveforms are supported. Fields related to DWS (e.g., Transform Precoder Indicator) have been introduced into the DCI format (0_1 / 0_2). The Transform Precoder Indicator field can be applied to both Dynamic License (DG) PUSCH and Configuration License (CG) PUSCH.

[0010] DG PUSCH is scheduled by C-RNTI-based DCI. (Type 2) CG PUSCH is activated by CS-RNTI-based DCI. Based on DCI size alignment, it is assumed that the bit width of a field in the C-RNTI-based DCI format is equal to the bit width of the same field in the CS-RNTI-based DCI format. Summary of the Invention

[0011] Technical issues

[0012] When Dynamic Waveform Switching (DWS) is enabled via the RRC parameter (i.e., when the RRC parameter is set to indicate that a transform precoder indicator field exists in the DCI format), a transform precoder indicator field (1 bit) exists in the DCI format.

[0013] Even if the CRC associated with the DCI format is scrambled by different RNTIs (e.g., C-RNTI or CS-RNTI), the transform precoder indicator field with the same bit width also exists in the DCI format because the RRC parameters and DCI size are aligned. However, the corresponding fields need to be interpreted differently for DG PUSCH and CG PUSCH based on different scheduling methods.

[0014] The purpose of this disclosure is to propose a method for interpreting / applying fields related to whether or not transform precoding is enabled in the DCI format based on an uplink scheduling method (e.g., dynamic licensing or configuration licensing).

[0015] The technical objectives to be achieved by this disclosure are not limited to those described above by way of example only, and other technical objectives not mentioned can be clearly understood by those skilled in the art from the following description.

[0016] Technical solution

[0017] A method performed by a user equipment (UE) according to an embodiment of the present disclosure includes the following steps: receiving configuration information related to a physical uplink shared channel (PUSCH), receiving downlink control information (DCI) including a new data indicator (NDI) field, and transmitting the PUSCH based on the DCI.

[0018] Based on the configuration information, parameters related to the transform precoder indicator field in the DCI are configured. The transform precoder indicator field is based on 1 bit.

[0019] The 1-bit value indicates whether the transform precoder is enabled or disabled.

[0020] i) The Cyclic Redundancy Check (CRC) associated with DCI is scrambled by Configuration Scheduling (CS) - Radio Network Temporary Identifier (RNTI) and ii) the value of the NDI field is “0”: 1 bit is reserved.

[0021] Based on unconfigured parameters, the transformation precoder indicator field can be based on 0 bits.

[0022] Licenses associated with PUSCH can be dynamic licenses or configuration licenses.

[0023] The DCI format associated with DCI can be either DCI format 0_1 ​​or DCI format 0_2.

[0024] CRC can be scrambled by CS-RNTI, cell (C)-RNTI, semi-persistent (SP)-channel state information (CSI)-RNTI, or modulation and coding scheme (MCS)-C-RNTI.

[0025] Based on i) CRC scrambling by CS-RNTI and ii) the value of the NDI field being "1": transform precoding for PUSCH can be enabled or disabled based on the transform precoder indicator field.

[0026] PUSCH transmission can be based on PUSCH retransmission.

[0027] Parameters in the configuration information, except for at least one parameter, can be applied to PUSCH retransmission. At least one parameter may include the transformPrecoder parameter.

[0028] Scrambling based on CRC by C-RNTI or MCS-C-RNTI: Transform precoding for PUSCH can be enabled or disabled based on the transform precoder indicator field.

[0029] For the same serving cell, the bit width of the first field in DCI format 0_1 ​​or DCI format 0_2 based on CS-RNTI can be equal to the bit width of the same field in DCI format 0_1 ​​or DCI format 0_2 based on C-RNTI.

[0030] The first field can be the transformation precoder indicator field.

[0031] If the payload size of the DCI format associated with DCI is less than the defined value, zeros can be appended to the DCI format until the payload size equals the defined value.

[0032] Based on i) CRC scrambling by CS-RNTI and ii) the value of the NDI field being “0”: DCI verification can be performed for scheduling activation based on configuration license.

[0033] DCI validation can be implemented based on fields in the DCI.

[0034] A user equipment (UE) according to another embodiment of the present disclosure includes: one or more transceivers, one or more processors, and one or more memories, wherein the memories are connected to the processors and configured to store instructions.

[0035] The instructions are based on all steps of configuring one or more processors to perform any of the methods in the method, and are executed by one or more processors.

[0036] An apparatus according to another embodiment of the present disclosure includes one or more memories and one or more processors, the processors being operatively connected to one or more memories.

[0037] One or more memories are configured to store instructions based on instructions executed by one or more processors, and the instructions are configured to allow one or more processors to perform all steps of any of the methods in the method.

[0038] One or more non-transitory computer-readable medium storage instructions according to another embodiment of this disclosure. The instructions, executable by one or more processors, are configured to allow one or more processors to perform all steps of any of the methods described.

[0039] A method performed by a base station according to another embodiment of the present disclosure includes the following steps: sending configuration information related to the Physical Uplink Shared Channel (PUSCH), sending downlink control information (DCI) including a New Data Indicator (NDI) field, and receiving the PUSCH based on the DCI.

[0040] Based on the configuration information, parameters related to the transform precoder indicator field in the DCI are configured. The transform precoder indicator field is based on 1 bit.

[0041] The 1-bit value indicates whether the transform precoder is enabled or disabled.

[0042] i) The Cyclic Redundancy Check (CRC) associated with DCI is scrambled by Configuration Scheduling (CS) - Radio Network Temporary Identifier (RNTI) and ii) the value of the NDI field is “0”: 1 bit is reserved.

[0043] A base station according to another embodiment of the present disclosure includes one or more transceivers, one or more processors, and one or more memories, wherein the memories are connected to one or more processors and store instructions.

[0044] The instructions are based on all steps of configuring one or more processors to perform the method, which are executed by one or more processors.

[0045] Beneficial effects

[0046] According to embodiments of this disclosure, when a transform precoder indicator field of the same bit width exists in a DCI with CRCs scrambled based on different RNTIs (e.g., CS-RNTI, C-RNTI), how the field should be interpreted is clearly defined. Therefore, ambiguity regarding whether transform precoding using DG PUSCH / CG PUSCH can be prevented.

[0047] Furthermore, it is clearly defined that the following situation exists: a transform precoder indicator field exists in the DCI, but operations based on the interpretation of the field are not applied (e.g., when CG PUSCH is active (= NDI field value is 0), operations indicated by the field are not applied). Dynamic waveform switching is not applied in all cases where a transform precoder indicator field exists in the DCI, but can be applied in limited ways to specific cases where dynamic waveform switching is required. For example, in the case of CG PUSCH retransmission (when NDI field value is 1), operations indicated by the transform precoder indicator field can be applied. Therefore, the delay caused by waveform switching can be minimized by limiting the unnecessary execution of waveform switching.

[0048] In addition, the effectiveness of dynamic waveform switching operations introduced to utilize waveforms more suitable for the channel environment can be ensured.

[0049] The effects that can be achieved using this disclosure are not limited to those described above by way of example only, and those skilled in the art to which this disclosure pertains will more clearly understand other effects and advantages of this disclosure based on the following description. Attached Figure Description

[0050] Figure 1 An example of uplink send / receive operation is shown.

[0051] Figure 2This is a flowchart illustrating a method performed by a user equipment according to an embodiment of the present disclosure.

[0052] Figure 3 This is a flowchart illustrating a method performed by a base station according to another embodiment of the present disclosure.

[0053] Figure 4 The configurations of the first and second devices according to embodiments of the present disclosure are illustrated. Detailed Implementation

[0054] Embodiments of this disclosure will now be described in detail, examples of which are illustrated in the accompanying drawings. The following will be discussed in conjunction with the accompanying drawings. Figure 1 The detailed description provided herein is intended to describe exemplary embodiments of the present disclosure, and not to describe unique embodiments for carrying out the present disclosure. The following detailed description includes details to provide a thorough understanding of the present disclosure. However, those skilled in the art will recognize that the present disclosure can be carried out without these details.

[0055] In some cases, to prevent ambiguity of the concepts in this disclosure, known structures and devices may be omitted or illustrated in block diagram format based on the core functions of each structure and device.

[0056] In the following text, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In the downlink, the sender can be part of the base station, and the receiver can be part of the terminal. In the uplink, the sender can be part of the terminal, and the receiver can be part of the base station. A base station can be referred to as a first communication device, and a terminal can be referred to as a second communication device. The term base station (BS) can be replaced by terms including fixed station, Node B, evolved Node B (eNB), next-generation Node B (gNB), base transceiver system (BTS), access point (AP), network (5G network), AI system, roadside unit (RSU), vehicle, robot, unmanned aerial vehicle (UAV), augmented reality (AR) device, virtual reality (VR) device, etc. Furthermore, the terminal can be fixed or mobile, and can be replaced by terms including user equipment (UE), mobile station (MS), user terminal (UT), mobile subscriber station (MSS), subscriber station (SS), advanced mobile station (AMS), wireless terminal (WT), machine-type communication (MTC) device, machine-to-machine (M2M) device and device-to-device (D2D) device, vehicle, robot, AI module, unmanned aerial vehicle (UAV), augmented reality (AR) device, virtual reality (VR) device, etc.

[0057] Uplink channel structure

[0058] The UE sends relevant signals to the base station through the uplink channel described below, and the base station receives relevant signals from the UE through the uplink channel described below.

[0059] (1) Physical Uplink Shared Channel (PUSCH)

[0060] PUSCH transmission carries uplink data (e.g., UL Shared Channel Transport Block (UL-SCH TB) and / or Uplink Control Information (UCI)) and is based on a Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform or a Discrete Fourier Transform-Extended-Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform. When PUSCH is transmitted based on a DFT-s-OFDM waveform, the UE transmits PUSCH by applying transform precoding. As an example, when transform precoding is disabled (e.g., transform precoding is disabled), the UE transmits PUSCH based on a CP-OFDM waveform, and when transform precoding is enabled (e.g., transform precoding is enabled), the UE can transmit PUSCH based on either a CP-OFDM waveform or a DFT-s-OFDM waveform. PUSCH transmission is dynamically scheduled by UL authorization in the DCI or semi-statically scheduled based on higher-layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling (e.g., PDCCH)) (configuration authorization). PUSCH transfers can be performed based on either the codebook or non-codebook.

[0061] (2) Physical Uplink Control Channel (PUCCH)

[0062] PUCCH transmits uplink control information, HARQ-ACK, and / or scheduling requests (SR), and is divided into short PUCCH and long PUCCH based on the transmission length. Table 1 shows the PUCCH format.

[0063] [Table 1]

[0064]

[0065] PUCCH format 0 transmits a UCI of maximum size of 2 bits and is mapped and sent based on a sequence. Specifically, the UE sends a specific UCI to the base station by transmitting one of a series of sequences using a PUCCH as PUCCH format 0. The UE only transmits a PUCCH as PUCCH format 0 within the PUCCH resources used to configure the corresponding SR when transmitting an affirmative SR.

[0066] PUCCH format 1 transmits a maximum 2-bit UCI, and the modulated signal is extended in the time domain by an orthogonal overlay code (OCC) (configured differently depending on whether frequency hopping is performed). DMRS is transmitted in symbols where the modulated symbols are not transmitted (i.e., not time-division multiplexed (TDM) and transmitted).

[0067] PUCCH format 2 transmits a UCI with a bit size greater than 2 bits, and the modulated symbols are frequency-division multiplexed (FDM) with DM-RS and transmitted. DM-RS is located in symbol indices #1, #4, #7, and #10 within the resource block, given at a density of 1 / 3. A pseudo-noise (PN) sequence is used for the DM-RS sequence. Frequency hopping can be activated for 2-symbol PUCCH format 2.

[0068] PUCCH format 3 does not perform UE multiplexing within the same physical resource block and transmits UCI in a bit size greater than 2 bits. In other words, the PUCCH resource of PUCCH format 3 does not include orthogonal overlay codes. Modulation symbols are time-division multiplexed (TDM) with DMRS and transmitted.

[0069] PUCCH format 4 supports multiplexing up to four UEs in the same physical resource block and transmits UCIs with a bit size greater than 2 bits. In other words, the PUCCH resource of PUCCH format 3 includes orthogonal overlay codes. Modulation symbols are time-division multiplexed with DMRS (TDM) and transmitted.

[0070] Uplink transmit / receive operations

[0071] Figure 1 Examples of uplink send and receive operations are shown.

[0072] Reference Figure 1 The eNB can schedule uplink transmissions (such as frequency / time resources, transport layer, uplink precoder, MCS, etc.) (S110). Specifically, the eNB can determine the beam for the PUSCH transmission for the UE through the beam management operation described above. Furthermore, the UE can receive a DCI for uplink scheduling (i.e., scheduling information including PUSCH) from the eNB on the PDCCH (S120). DCI format 0_0 or 0_1 can be used for uplink scheduling, and specifically, DCI format 0_1 ​​can include information such as: an identifier for the DCI format, a UL / Supplementary Uplink (SUL) indicator, a bandwidth portion indicator, frequency domain resource assignment, time domain resource assignment, frequency hopping flag, modulation and coding scheme (MCS), SRS resource indicator (SRI), precoding information and layer number, antenna port, SRS request, DMRS sequence initialization, and uplink shared channel (UL-SCH) indicator.

[0073] Specifically, the configuration SRS resources in the SRS resource set associated with the high-level parameter "usage" can be indicated by the SRS resource indicator field. Furthermore, "spatialRelationInfo" can be configured for each SRS resource, and the value of "spatialRelationInfo" can be one of {CRI, SSB, and SRI}.

[0074] Additionally, the UE can send uplink data to the eNB on the PUSCH (S130). When the UE detects a PDCCH containing DCI format 0_0 or 1_1, the UE can send the corresponding PUSCH according to the indication of the corresponding DCI. For PUSCH transmission, two schemes are supported (codebook-based transmission scheme and non-codebook-based transmission scheme).

[0075] In codebook-based transmission, the UE is configured for codebook-based transmission when the higher-layer parameter "txConfig" is set to "codebook". Conversely, the UE is configured for non-codebook-based transmission when the higher-layer parameter "txConfig" is set to "nonCodebook". When the higher-layer parameter "txConfig" is not configured, the UE does not predict PUSCH scheduling via DCI format 0_1. When PUSCH is scheduled via DCI format 0_0, PUSCH transmission is based on a single antenna port. In codebook-based transmission, PUSCH can be scheduled via DCI format 0_0, DCI format 0_1, or semi-statically. When PUSCH is scheduled via DCI format 0_1, the UE determines the PUSCH transmission precoder based on the SRI, the Transmit Precoding Matrix Indicator (TPMI), and the transmission rank from the DCI (as given by the SRS resource indicator and precoding information and layer digital segment). The TPMI indicates the precoder to be applied on the antenna port, and when multiple SRS resources are configured, the TPMI corresponds to the SRS resource selected by the SRI. Alternatively, when a single SRS resource is configured, the TPMI is used to indicate the precoder to be applied on the antenna port, corresponding to the specific SRS resource. A transmission precoder is selected from the uplink codebook having the same antenna port number as the higher-layer parameter “nrofSRS-Ports”. When the UE is set to the higher-layer parameter “txConfig” as “codebook”, at least one SRS resource is configured in the UE. The SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, and here, the SRS resource precedes the PDCCH carrying the SRI (i.e., slot n).

[0076] In the case of non-codebook-based transmission, PUSCH can be scheduled via DCI format 0_0, DCI format 0_1, or semi-statically. When multiple SRS resources are configured, the UE can determine the PUSCH precoder and transmission rank based on the wideband SRI, where the SRI is given by the SRS resource indicator in the DCI or by the higher-layer parameter "srs-ResourceIndicator". The UE can use one or more SRS resources for SRS transmission, and multiple SRS resources can be configured for simultaneous transmission in the same RB based on the UE's capabilities. Only one SRS port is configured for each SRS resource. Only one SRS resource can be configured with the higher-layer parameter "usage" set to "nonCodebook". The maximum number of SRS resources that can be configured for non-codebook-based uplink transmission is 4. The SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, and the SRS transmission precedes the PDCCH carrying the SRI (i.e., slot n).

[0077] Transform precoder field

[0078] The following will describe the configurations associated with the transform precoder that can be applied to the implementations described below.

[0079] [Table 2]

[0080]

[0081]

[0082]

[0083]

[0084]

[0085]

[0086]

[0087]

[0088]

[0089]

[0090] Referring to Table 2, RACH-ConfigCommon includes the msg3-transformPrecoder parameter.

[0091] [Table 3]

[0092]

[0093]

[0094]

[0095]

[0096]

[0097]

[0098]

[0099]

[0100]

[0101] Referring to Table 3, MsgA-PUSCH-Config includes the msgA-TransformPrecoder parameter.

[0102] [Table 4]

[0103]

[0104]

[0105]

[0106]

[0107]

[0108]

[0109]

[0110]

[0111]

[0112]

[0113]

[0114]

[0115]

[0116]

[0117]

[0118]

[0119]

[0120]

[0121]

[0122]

[0123]

[0124]

[0125]

[0126]

[0127]

[0128]

[0129] Referring to Table 4, PUSCH-Config includes the transformPrecoder parameter.

[0130] The content described above (uplink channel structure, uplink transmit / receive operation, and transformation precoder related configuration (Tables 2 to 4), etc.) can be applied in conjunction with the methods proposed in this disclosure as described below, or can be supplemented to clarify the technical features of the methods proposed in this disclosure. For convenience, only the methods described below are distinguished, and it is not necessary to say that some components of any one method can be replaced by some components of another method, or can be combined with each other.

[0131] Dynamic waveform switching (DWS) can be supported for coverage enhancement in NR. The following section describes in detail how to configure the UE's UL waveform based on the DCI format type and whether an indication field for DWS is supported.

[0132] In the current NR, which waveform to use, CP-OFDM or DFT-S-OFDM, is defined and indicated by RRC signaling (e.g., SIB1, UE-specific RRC signaling, etc.).

[0133] Specifically, during the 4-step RACH process, the waveform of Msg.3 PUSCH can be configured / indicated / determined as follows.

[0134] When “msg3-transformPrecoder” is configured / indicated to be enabled (that is, when the UE receives a configuration including the msg3-transformPrecoder parameter from the base station (e.g., RACH-ConfigCommon in Table 2)), the transform precoder for Msg3 transmission is enabled. In other words, transform precoding for transmitting the Msg.3 PUSCH is enabled. In this case, the UE uses DFT-S-OFDM as the waveform for the Msg.3 PUSCH.

[0135] When the “msg3-transformPrecoder” parameter field is empty (that is, when the UE receives a configuration from the base station that does not have the msg3-transformPrecoder parameter (e.g., RACH-ConfigCommon in Table 2)), the transform precoder for Msg3 transmission is disabled. In other words, transform precoding for transmitting Msg.3 PUSCH is disabled. In this case, the UE uses CF-OFDM as the waveform for Msg.3 PUSCH.

[0136] In the case of a 2-step RACH process, the waveform of MsgA PUSCH can be configured / indicated / determined as follows.

[0137] When “msgA-TransformPrecoder” is configured / indicated to be enabled (that is, when the UE receives a configuration from the base station including the msgA-TransformPrecoder parameter configured to be “enabled” (e.g., MsgA-PUSCH-Config in Table 3)), the transform precoder for MsgA transmission is enabled. In other words, transform precoding for transmitting MsgAPUSCH is enabled. In this case, the UE uses DFT-S-OFDM as the waveform for MsgA PUSCH.

[0138] When “msgA-TransformPrecoder” is configured / indicated to be disabled (that is, when the UE receives a configuration from the base station that includes the msgA-TransformPrecoder parameter configured to be “disabled” (e.g., MsgA-PUSCH-Config in Table 3)), the transform precoder for MsgA transmissions is disabled. In other words, transform precoding for transmitting the MsgA PUSCH is disabled. In this case, the UE uses CP-OFDM as the waveform for the MsgA PUSCH.

[0139] The UL channels other than Msg. 3 PUSCH and Msg. A PUSCH can be configured / indicated as follows (e.g., normal PUSCH, configuration PUSCH, etc.).

[0140] When "transformPrecoder" is configured / indicated to be enabled (that is, when the UE receives a configuration from the base station including the "enabled" transformPrecoder parameter (e.g., PUSCH-Config in Table 4)), the transform precoder used to transmit another UL channel (e.g., PUSCH) is enabled. In other words, transform precoding for transmitting another UL channel (e.g., PUSCH) is enabled. In this case, the UE uses DFT-S-OFDM as the waveform for the other UL channel (e.g., PUSCH).

[0141] When "transformPrecoder" is configured / indicated to be disabled (that is, when the UE receives a configuration from the base station that includes the "disabled" transformPrecoder parameter (e.g., PUSCH-Config in Table 4)), the transform precoder used to transmit another UL channel (e.g., PUSCH) is disabled. In other words, the transform precoding used to transmit another UL channel (e.g., PUSCH) is disabled. In this case, the UE uses CP-OFDM as the waveform for the other UL channel (e.g., PUSCH).

[0142] Furthermore, when no separate "transformPrecoder" parameter is specified, the UE operates based on the configuration of "msg3-transformPrecother". Transform precoding is applied or not applied based on the configuration (enabled or disabled) of msgA-TransformPrecoder. In other words, whether transform precoding is applied to uplink transmission can be determined based on the configuration (enabled or disabled) of msgA-TransformPrecoder.

[0143] Dynamic waveform switching operation is considered for enhancing UL coverage of existing NR systems.

[0144] In a recent standardization meeting, the interpretation / definition of UE / base station operations when introducing a dynamic waveform switching indication field into DCI information was discussed. For example, discrepancies may exist in the interpretation between DCI formats utilizing C-RNTI and / or CS-RNTI scrambling, based on DG PUSCH and / or CG PUSCH Type 2 applications, which are PUSCH transmission methods supporting dynamic waveform switching. Furthermore, by introducing a dynamic waveform switching indication field, a waveform-dependent field is generated if it is determined which waveform is indicated to the UE (i.e., CP-OFDM or DFT-S-OFDM), thus addressing the issue of differences in DCI payload size. On the other hand, CG PUSCH Type 1 has the characteristic of making transmission operations difficult to expect via DCI reception, as PUSCH transmission is performed solely based on its definition via higher-layer (via RRC signaling) parameters. Therefore, in order to equally match the differences in DCI payload size caused by the above issues, when introducing the dynamic waveform switching indicator field, it is necessary to redefine / determine how to perform DCI size alignment for each PUSCH transmission method (i.e., DG-PUSCH or CG-PUSCH type 2).

[0145] First, the conventional DCI size alignment is conceptually described. A DCI size alignment method based on each format is defined, which performs zero padding at the end of the shorter DCI among the compared DCIs to ensure that the total payload size is the same. When performing DCI size alignment between DCIs corresponding to C-RNTI / CS-RNTI, the operation of performing zero padding (i.e., per-field alignment) for each field of the DCI corresponding to CS-RNTI from the MSB of each field of the DCI corresponding to C-RNTI to match the size is shown in Table 5 below.

[0146] [Table 5]

[0147]

[0148] If a DCI indicator field is introduced to support dynamic waveform switching based on per-format or per-field DCI size alignment, which is the regular DCI size alignment method, its interpretation may need to be redefined.

[0149] Therefore, when introducing and supporting the Dynamic Waveform Switching Indication field (hereinafter referred to as the DWS field), this disclosure proposes a method to interpret / determine the DWS field based on the DCI monitored by the UE and received via the PDCCH.

[0150] Dynamic Waveform Switching (DWS) is the operation that enables or disables the dynamic transform precoder.

[0151] Therefore, in this disclosure, the "Dynamic Waveform Switching Field" and the "DWS Field" can be interpreted / replaced by the "Transform Precoder Indicator Field". Additionally, high-level parameters (RRC parameters) related to enabled (or disabled) DWS can be interpreted / replaced by high-level parameters (RRC parameters) related to the presence of the Transform Precoder Indicator Field within the DCI. Furthermore, waveform indications (e.g., DFT-S-OFDM or CP-OFDM) can be interpreted / replaced by indications of enabling / disabling the transform precoder / transform precoding.

[0152] When an indication field for dynamic waveform switching is supported, the following describes a method for interpreting / determining the DWS field size of the UE based on the DCI format type and situation.

[0153] In this disclosure, for the sake of brevity, the phrase “the cyclic redundancy check (CRC) of a particular DCI (e.g., DCI format 0_1, 0_2) has been scrambled with a particular radio network temporary identifier (RNTI) (e.g., cell (C)-RNTI, configuration scheduling (CS)-RNTI)” can be replaced and written as “DCI corresponding to a particular RNTI” or “DCI of a particular RNTI” or similar expressions, all of which have the same meaning.

[0154] It is necessary to determine how configuration license (CG) configurations (e.g., CG-PUSCH type 2), each with different waveforms, can be matched with each field of the DCI corresponding to the C-RNTI, where the field size varies depending on the value of the DWS field. For example, per-field matching can be performed assuming that the DWS field of the DCI corresponding to the C-RNTI indicates a waveform value equal to that indicated in the CG configuration (e.g., CG-PUSCH type 2).

[0155] Method 1

[0156] The following describes a method for interpreting DWS fields when they are introduced (or exist) in DCI format 0_1 / 0_2. Specifically, a method for interpreting DWS fields in DCI format 0_1 / 0_2 for PUSCH transport methods (e.g., DG PUSCH or CG PUSCH) is described when i) DWS enable (and / or disable) configuration is supported based on higher-level parameters, and ii) DWS is enabled.

[0157] Case 1. For DCI format 0_1 / 0_2 corresponding to C-RNTI, which includes the DWS field, the size of the DWS field can be set / determined to 1 bit.

[0158] For example, a 1-bit value can represent a waveform value for dynamic waveform switching (e.g., CP-OFDM = 0 (or 1), DFT-S-OFDM = 1 (or 0)). For example, a 1-bit value can represent the enabling or disabling of the transform precoder.

[0159] When the UE receives the DCI format 0_1 / 0_2 from the C-RNTI, including the DWS field, the UE can interpret the DWS field as a 1-bit size and determine it as an indication waveform for dynamic waveform switching based on a value of 0 or 1 (e.g., CP-OFDM=0 (or 1), DFT-S-OFDM=1 (or 0)). The UE can further interpret fields (e.g., FDRA, TPMI, antenna port) in subsequent DCI interpretation processes, which can vary depending on the indicated waveform value.

[0160] Case 2. For DCI format 0_1 / 0_2 corresponding to CS-RNTI, which includes the DWS field, when performing activation / deactivation / release related to PUSCH (i.e., NDI=0), the size of the DWS field can be set / determined to 1 bit.

[0161] The value of the DWS field can be determined based on at least one of the following implementation methods.

[0162] Alternative Option 1: The value of the DWS field can be defined / indicated as the same waveform that is semi-statically configured in the higher-level parameters.

[0163] The value of the DWS field can be defined as having the same waveform as the value set to a higher-layer parameter (e.g., transformPrecoder). For example, if transformPrecoder=enabled, the DWS field can be indicated as the value corresponding to DFT-S-OFDM. When receiving DCI format 0_1 / 0_2 of CS-RNTI with the DWS field set to "NDI=0", the UE can interpret the DWS field as a 1-bit size. "NDI=0" means that the value of the New Data Indication (NDI) field in DCI format 0_1 / 0_2 is 0. The UE can check whether the waveform indicated by the set higher-layer parameter (transformPrecoder) is the same as the waveform indicated by the DWS field. The waveform can be interpreted / replaced as enabling / disabling transform precoder / transform precoding. The UE expects the waveform indicated by the DWS field to be the same as the waveform configured / indicated via higher-layer signaling. Otherwise, the UE can determine that the activation / deactivation / release operation corresponding to CG-PUSCH is invalid (=error case).

[0164] Alternative Option 2. Definition of Reserved Bits

[0165] The DWS field can be defined as a reserved bit. When the UE receives a DCI format 0_1 / 0_2 with the CS-RNTI set to "NDI=0" including the DWS field, the UE does not perform a separate interpretation because the DWS field is a reserved bit. The fact that the UE does not perform a separate interpretation may mean that it does not perform any operation (determine whether to apply transform precoding) based on the value of the DWS field.

[0166] Alternative Option 3: DWS field values ​​do not have individual definitions / restrictions.

[0167] The value of the DWS field can be defined regardless of the value set to higher-layer parameters (e.g., transformPrecoder). That is, from the base station's perspective, there may be no separate restriction on the value of the DWS field. When the UE receives a DCI format 0_1 / 0_2 with the CS-RNTI set to "NDI=0" including the DWS field, the UE interprets the DWS field as a 1-bit size, but does not interpret the value of the DWS field separately.

[0168] In the subsequent process of interpreting the DCI, the UE may interpret additional fields (e.g., FDRA, TPMI, antenna port), which can vary based on the waveform values ​​indicated by the DWS field of the DCI corresponding to C-RNTI and the waveform values ​​of CG-PUSCH indicated by higher-layer signaling.

[0169] Case 3. It can be assumed that the DCI format 0_1 / 0_2 corresponding to CS-RNTI, including the DWS field, is used for retransmission (i.e., retransmission of CG PUSCH) (i.e., NDI=1). That is, if the value of the NDI field of DCI format 0_1 / 0_2 is 1, the size of the DWS field can be set / determined to 1 bit.

[0170] For example, a 1-bit value can represent a waveform value for dynamic waveform switching (e.g., CP-OFDM=0 (or 1), DFT-S-OFDM=1 (or 0)). For example, a 1-bit value can represent the enabling or disabling of the transform precoder.

[0171] When the UE receives a DCI format 0_1 / 0_2 with the CS-RNTI set to "NDI=1" including the DWS field, the UE can interpret the DWS field as a 1-bit size and determine it as an indication waveform for dynamic waveform switching based on a value of 0 or 1 (e.g., CP-OFDM=0 (or 1), DFT-S-OFDM=1 (or 0)). The UE can further interpret fields (e.g., FDRA, TPMI, antenna port) in subsequent DCI interpretation processes, which can vary depending on the indicated waveform value.

[0172] Method 2

[0173] The following describes a method for interpreting the DWS field when it is introduced (or exists) in DCI format 0_1 / 0_2. Specifically, a method for interpreting the DWS field in DCI format 0_1 / 0_2 for PUSCH transport methods (e.g., DG PUSCH or CG PUSCH) is described when i) DWS enable (and / or disable) configuration is supported based on higher-level parameters, and ii) DWS is disabled.

[0174] Clearly, even without supporting dynamic waveform switching, PUSCH transmission can still be performed via dynamic indication because the higher-layer parameters are set to disable DWS. In this case, the UE's interpretation method can differ based on the presence or absence of the DWS field when configuring the DCI payload.

[0175] Method 1. Interpretation of the DWS field when it exists

[0176] Alternative Option 1: The value of the DWS field can be defined / indicated as the same waveform that is semi-statically configured in the higher-level parameters.

[0177] The value of the DWS field can be defined as having the same waveform as the value set to a higher-layer parameter (e.g., transformPrecoder). For example, if transformPrecoder=enabled, the DWS field can be indicated as the value corresponding to DFT-S-OFDM. When receiving DCI format 0_1 / 0_2 of C-RNTI / CS-RNTI including the DWS field, the UE can interpret the DWS field as a 1-bit size and check whether the waveform indicated by the transformPrecoder set to a higher-layer parameter is the same as the waveform indicated by the DWS field. The UE expects the waveform indicated by the DWS field to be the same as the waveform configured / indicated via higher-layer signaling. Otherwise, the UE can determine that the activation / deactivation / release operation corresponding to the CG-PUSCH is invalid (=error case).

[0178] Alternatively, since dynamic waveform switching is not supported, the UE can be defined / configured to not interpret the corresponding value.

[0179] Alternative Option 2. Definition of Reserved Bits

[0180] The DWS field can be defined as a reserved bit. When the UE receives a DCI format 0_1 / 0_2 containing a C-RNTI / CS-RNTI with the DWS field, the UE does not perform a separate interpretation because the DWS field is a reserved bit.

[0181] Alternative Option 3: DWS field values ​​do not have individual definitions / restrictions.

[0182] The value of the DWS field can be defined regardless of the value set to higher-layer parameters (e.g., transformPrecoder). That is, from the base station's perspective, there may be no separate restriction on the value of the DWS field. When the UE receives a DCI format 0_1 / 0_2 containing a C-RNTI / CS-RNTI that includes the DWS field, the UE interprets the DWS field as a 1-bit value, but does not interpret the DWS field value separately.

[0183] In the subsequent process of interpreting DCI, the UE can interpret additional fields (e.g., FDRA, TPMI, antenna port), which can vary based on the waveform values ​​for DG-PUSCH indicated by higher-layer signaling and the waveform values ​​for CG-PUSCH indicated by higher-layer signaling.

[0184] Method 2. Explanation of when the DWS field does not exist.

[0185] The absence of the DWS field can indicate that the field is not present in the DCI format or that the field is set to 0 bits in the DCI format.

[0186] If the high-level parameter for dynamic waveform switching is set to "DWS_Support-r18", the number of bits in the DWS field according to this embodiment can be expressed in the following form.

[0187] If the higher-level parameter DWS_Support-r18 is disabled, then 0 bits...

[0188] If the new value "dynamic" is defined as the high-level parameter "transformPrecoder" for dynamic waveform switching, then the number of bits in the DWS field according to this embodiment can be expressed in the following form.

[0189] 0 bits, unless the higher-level parameter transformPrecoder is set to dynamic.

[0190] In this scenario, when the DWS field is absent, the UE performs an interpretation operation based on the existing DCI payload size.

[0191] The above embodiments describe a method for defining a DWS field of size 1 bit and its UE / base station operation under the assumption of a single-cell environment. However, the application scope of the embodiments of this disclosure is not limited to a single-cell environment. Specifically, even when introducing a DWS field consisting of multiple bits in a multi-cell environment, the above embodiments can be applied equivalently or similarly.

[0192] In other words, in a DWS field consisting of multiple bits, the field size for a specific cell can be 1 bit, and the above implementation can be applied to methods for defining 1-bit DWS fields and their UE / base station operations. In this case, a proposed method can be applied to multiple cells together, or a proposed method can be configured / applied independently for each cell.

[0193] The implementations based on methods 1 and 2 above can be configured / applied to other UL signals / channels, such as MSG3 PUSCH, MSGA preamble / PUSCH, and / or PUSCH / PUCCH. Since examples of the methods described above can also be included as implementations of this disclosure, it is evident that they can be considered as a proposed method. Furthermore, the methods described above can be implemented independently, but also in combination (or merged) of some proposed methods. Information regarding whether to apply the proposed methods (or information regarding rules governing the proposed methods) can be defined as rules that allow the base station to notify the UE via predefined signals (e.g., physical layer signals or higher-layer signals). For example, higher layers may include one or more functional layers, such as MAC, RLC, PDCP, RRC, and SDAP.

[0194] The methods, implementations, or descriptions used to implement the methods proposed in this disclosure may be applied individually, or one or more methods (or implementations or descriptions) may be applied in combination.

[0195] For example, the operation of at least one of the implementations based on method 1 and / or method 2 can be based on Table 6 below.

[0196] [Table 6]

[0197]

[0198]

[0199]

[0200] For example, the DCI format including the DWS field (Transform Precoder Indicator Field) in at least one of the implementations of Method 1 and / or Method 2 can be based on Table 7 below.

[0201] [Table 7]

[0202]

[0203] From an implementation perspective, the operation of the base station / UE according to the above embodiments (e.g., operation based on at least one of method 1 and / or method 2) can be described below. Figure 4The device (e.g., reference numerals 100 and 200) is used to process it.

[0204] Furthermore, the operation of the base station / UE according to the above embodiments (e.g., operation based on at least one of method 1 and / or method 2) can be used to run at least one processor (e.g., Figure 4 The commands / programs (e.g., instructions, executable code) of the processors 110 and 210 are stored in memory (e.g., Figure 4 In the memory (140 and 240).

[0205] Below, refer to Figure 2 and Figure 3 The above implementation methods are described in detail from the perspective of UE and base station operation. The methods described below are distinguished only for ease of explanation. Therefore, it is obvious that any partial configuration of any method can be replaced by partial configuration of another method or combined with partial configuration of another method.

[0206] Figure 2 This is a flowchart illustrating a method performed by a user equipment according to an embodiment of the present disclosure.

[0207] Reference Figure 2 The method performed by a user equipment (UE) according to an embodiment of the present disclosure includes: step S210 of receiving configuration information related to PUSCH, step S220 of receiving DCI including NDI, and step S230 of sending PUSCH based on DCI.

[0208] In step S210, the UE receives configuration information related to the Physical Uplink Shared Channel (PUSCH) from the base station.

[0209] Configuration information can be based on PUSCH-config. Configuration information may include high-level parameters based on at least one of Method 1 and / or Method 2 described above. For example, configuration information may include parameters related to the presence of the transform precoder indicator field in DCI format 0_1 / DCI format 0_2 (e.g., dynamicTransformPrecoderFieldPresenceDCI-0-1, dynamicTransformPrecoderFieldPresenceDCI-0-2 in Table 4).

[0210] In step S220, the UE receives downlink control information (DCI) from the base station, including a New Data Indicator (NDI) field.

[0211] According to the implementation, parameters related to the presence of a transform precoder indicator field in the DCI are configured based on configuration information, and the transform precoder indicator field can be based on 1 bit. This implementation can be based on method 1 and / or method 2. More specifically, i) the transform precoder indicator field can exist in the DCI based on configured parameters, and ii) the size of the transform precoder indicator field in the DCI can be set to 0 based on unconfigured parameters.

[0212] For example, a 1-bit value can indicate whether the transform precoder is enabled or disabled.

[0213] For example, based on i) the Cyclic Redundancy Check (CRC) associated with DCI being scrambled by Configuration Scheduling (CS) - Radio Network Temporary Identifier (RNTI) and ii) the value of the NDI field being "0", 1 bit can be reserved.

[0214] For example, the transform precoder indicator field can be 0 bits based on unconfigured parameters. This implementation can be based on method 2. Based on the payload size of the DCI format associated with the DCI being less than a defined value (e.g., 12 in Table 5), 0s can be appended to the DCI format until the payload size equals the defined value. That is, one or more padding bits set to 0 for DCI size alignment can be appended to the DCI format.

[0215] For example, the DCI format associated with DCI can be DCI format 0_1 ​​or DCI format 0_2.

[0216] CRC can be scrambled using CS-RNTI, cell (C)-RNTI, semi-persistent (SP)-channel state information (CSI)-RNTI, or modulation and coding scheme (MCS)-C-RNTI.

[0217] In step S230, the UE sends a PUSCH to the base station based on the DCI.

[0218] According to the implementation method, the license associated with PUSCH can be a dynamic license (DG) or a configuration license (CG). PUSCH can be a DG PUSCH or a CG PUSCH. For example, PUSCH can be scheduled based on DCI. For example, PUSCH scheduling can be activated based on DCI. The configuration license can be configuration license type 2.

[0219] According to the implementation method, the above-described dynamic waveform switching can be applied to PUSCH retransmission (based on type 2 configuration permission). Specifically, based on i) CRC scrambling via CS-RNTI and ii) the value of the NDI field being "1", transform precoding for PUSCH can be enabled or disabled based on the transform precoder indicator field. PUSCH transmission can be based on PUSCH retransmission. This implementation method can be based on case 3 of method 1.

[0220] In this example, parameters from the configuration information, excluding those related to the transform precoder, can be applied to PUSCH retransmissions. Specifically, the enablement of the transform precoder is indicated based on the transform precoder indicator field rather than higher-level parameters (e.g., the transformPrecoder parameter). For example, parameters from the configuration information other than at least one parameter can be applied to PUSCH retransmissions. At least one parameter may include the transformPrecoder parameter.

[0221] According to the implementation method, the transform precoder indicator field is applied to the PUSCH scheduled by DCI based on an RNTI different from the CS-RNTI. Specifically, transform precoding for the PUSCH can be enabled or disabled based on the transform precoder indicator field by scrambling with CRC via C-RNTI or MCS-C-RNTI.

[0222] According to the implementation method, referring to Table 5, the size of the first field in the DCI format based on the first RNTI (e.g., CS-RNTI) can be equal to the size of the same field in the DCI format based on the second RNTI (e.g., C-RNTI). That is, the UE does not expect the size of the first field to be greater than the size of the same field in the DCI format based on the second RNTI. Specifically, for the same serving cell, the bit width of the first field in DCI format 0_1 ​​or DCI format 0_2 based on CS-RNTI can be equal to the bit width of the same field in DCI format 0_1 ​​or DCI format 0_2 based on C-RNTI. The first field can be the transform precoder indicator field. In other words, the bit width (1) of the transform precoder indicator field in the DCI format based on CS-RNTI is the same as the bit width (1) of the transform precoder indicator field in the DCI format based on C-RNTI. However, as described above, the same field with the same bit width can be interpreted / applied differently. For example, the bits of the transform precoder indicator field are reserved based on the value of the NDI field being 0 in the DCI format based on CS-RNTI. For example, whether the transform precoder is enabled is indicated by the value of the transform precoder indicator field in the DCI format based on C-RNTI (or the DCI format based on the value of 1 in the NDI field of CS-RNTI).

[0223] According to the implementation method, in order to activate the above-mentioned scheduling, DCI format verification can be performed. Specifically, based on i) CRC scrambling via CS-RNTI and ii) the value of the NDI field being "0", DCI (i.e., DCI format) verification can be performed for scheduling activation based on configuration permissions. DCI verification can be implemented based on the fields in the DCI. More specifically, verification can be implemented based on the value of each field in the fields set as defined.

[0224] Based on the verification, the UE can regard the information in the DCI as a valid activation or release of the configuration license (i.e., configuration UL license type 2).

[0225] Since verification is not implemented, the UE can discard all information in the DCI.

[0226] The fields may include at least one of the following: i) HARQ process number field, ii) redundancy version field, iii) modulation and coding scheme field and / or iv) frequency domain resource assignment field.

[0227] For example, the waveform associated with the transmission of PUSCH can be based on i) Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) or ii) Discrete Fourier Transform-Extended-OFDM (DFT-S-OFDM). Transform precoding can be associated with DFT-S-OFDM.

[0228] Based on the operations of steps S210 to S230 above, it can be done by... Figure 4 The device implementation. For example, UE 200 may control one or more transceivers 230 and / or one or more memories 240 to perform operations based on steps S210 to S230.

[0229] The above implementation method will now be described in detail from the perspective of base station operation.

[0230] Steps S310 to S330 described below correspond to reference Figure 2 Steps S210 to S230 are described below. Considering the above correspondence, redundant descriptions have been omitted. That is, the detailed description of the base station operation described below can be replaced with... Figure 2 The description / implementation method corresponding to base station operation. For example, Figure 2 The description / implementation of steps S210 to S230 can be further applied to the base station operation of steps S310 to S330 described below.

[0231] Figure 3 This is a flowchart illustrating a method performed by a base station according to another embodiment of the present disclosure.

[0232] Reference Figure 3 According to another embodiment of the present disclosure, the method performed by the base station includes: step S310 of sending configuration information related to PUSCH, step S320 of sending DCI including NDI, and step S330 of receiving PUSCH based on DCI.

[0233] In step S310, the base station sends configuration information related to the Physical Uplink Shared Channel (PUSCH) to the UE.

[0234] In step S320, the base station sends downlink control information (DCI) including a New Data Indicator (NDI) field to the UE.

[0235] In step S330, the base station receives PUSCH from the UE based on DCI.

[0236] Based on the operations of steps S310 to S330 above, it can be done by... Figure 4 The device is implemented in this way. For example, base station 100 may control one or more transceivers 130 and / or one or more memories 140 to perform the operations based on steps S310 to S330.

[0237] The operations / terminology based on the above embodiments have been described under the assumption of a 5G system. However, this is merely for illustrative purposes and is not intended to limit the application of the technical problems and solutions to be solved by this disclosure to a specific system. That is, the technical challenges / problems / difficulties mentioned in this disclosure may also exist in other systems (e.g., 6G systems). Obviously, the embodiments of this disclosure can be extended and applied to solve the same problems in other systems. Therefore, in order to extend the embodiments of this disclosure to other systems, the terminology defined / described based on the 5G system can be replaced / changed with terminology defined in other systems (or broad terminology not specific to a single system).

[0238] For example, the Physical Uplink Shared Channel (PUSCH) can be replaced / changed with the First Uplink Channel.

[0239] For example, configuration information can be replaced / changed with the first information.

[0240] For example, downlink control information (DCI) can be replaced / changed with second information.

[0241] The following reference Figure 4 Describes the apparatus to which embodiments of this disclosure are applicable (apparatus for implementing the methods / operations according to embodiments of this disclosure).

[0242] Figure 4The configurations of the first and second devices according to embodiments of the present disclosure are illustrated.

[0243] The first device 100 may include a processor 110, an antenna unit 120, a transceiver 130, and a memory 140.

[0244] Processor 110 can perform baseband-related signal processing and includes a higher-layer processing unit 111 and a physical layer processing unit 115. Higher-layer processing unit 111 can handle operations at the MAC layer, RRC layer, or higher layers. Physical layer processing unit 115 can handle PHY layer operations. For example, if the first device 100 is a base station (BS) device in BS-UE communication, physical layer processing unit 115 can perform uplink receive signal processing, downlink transmit signal processing, etc. For example, if the first device 100 is a first UE device in UE-to-UE communication, physical layer processing unit 115 can perform downlink receive signal processing, uplink transmit signal processing, sidelink transmit signal processing, etc. In addition to performing baseband-related signal processing, processor 110 can also control the overall operation of the first device 100.

[0245] Antenna unit 120 may include one or more physical antennas, and if antenna unit 120 includes multiple antennas, MIMO transmission / reception is supported. Transceiver 130 may include a radio frequency (RF) transmitter and an RF receiver. Memory 140 may store information processed by processor 110, as well as software, operating system, and applications related to the operation of first device 100. Memory 140 may also include components such as buffers.

[0246] In the embodiments described in this disclosure, the processor 110 of the first device 100 may be configured to implement the operation of the BS in BS-UE communication (or the operation of the first UE device in UE-UE communication).

[0247] The second device 200 may include a processor 210, an antenna unit 220, a transceiver 230, and a memory 240.

[0248] Processor 210 can perform baseband-related signal processing and includes a higher-layer processing unit 211 and a physical layer processing unit 215. Higher-layer processing unit 211 can handle operations at the MAC layer, RRC layer, or higher layers. Physical layer processing unit 215 can handle PHY layer operations. For example, if the second device 200 is a UE device in BS-UE communication, physical layer processing unit 215 can perform downlink receive signal processing, uplink transmit signal processing, etc. For example, if the second device 200 is a second UE device in inter-UE communication, physical layer processing unit 215 can perform downlink receive signal processing, uplink transmit signal processing, sidelink receive signal processing, etc. In addition to performing baseband-related signal processing, processor 210 can also control the overall operation of the second device 210.

[0249] Antenna unit 220 may include one or more physical antennas, and if antenna unit 220 includes multiple antennas, MIMO transmission / reception is supported. Transceiver 230 may include an RF transmitter and an RF receiver. Memory 240 may store information processed by processor 210, as well as software, operating system, and applications related to the operation of second device 200. Memory 240 may also include components such as buffers.

[0250] In the embodiments described in this disclosure, the processor 210 of the second device 200 may be configured to implement the operation of the UE in BS-UE communication (or the operation of the second UE device in inter-UE communication).

[0251] The descriptions of the BS and UE (or the first UE device and the second UE device in inter-UE communication) in the examples of this disclosure are equivalent to those for the operation of the first device 100 and the second device 200, and redundant descriptions are omitted.

[0252] In addition to LTE, NR, and 6G, the wireless communication technologies implemented in apparatus 100 and apparatus 200 according to this disclosure may also include narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2. NB-IoT technology is not limited to the names mentioned above.

[0253] Additionally or alternatively, the wireless communication technology implemented in apparatus 100 and apparatus 200 according to this disclosure may be based on LTE-M technology to perform communication. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names, such as enhanced machine-type communication (eMTC). For example, LTE-M technology may be implemented using at least one of various standards, such as 1) LTE Cat0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE machine-type communication, and / or 7) LTE M. LTE-M technology is not limited to the names mentioned above.

[0254] Additionally or alternatively, considering low-power communication, the wireless communication technologies implemented in apparatus 100 and apparatus 200 according to this disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN), and are not limited to the aforementioned names. For example, ZigBee technology can be based on various standards such as IEEE 802.15.4 to create personal area networks (PANs) associated with small / low-power digital communication, and may be referred to by various names.

Claims

1. A method performed by a user equipment (UE), the method comprising the following steps: Receive configuration information related to the Physical Uplink Shared Channel (PUSCH); Receive downlink control information (DCI) including the New Data Indicator (NDI) field; as well as The PUSCH is sent based on the DCI. Specifically, parameters related to the presence of a transform precoder indicator field in the DCI are configured based on the configuration information, and the transform precoder indicator field is based on 1 bit. The 1-bit value indicates whether the transform precoder is enabled or disabled, and Wherein, i) the Cyclic Redundancy Check (CRC) associated with the DCI is scrambled by the Configuration Scheduling CS-Radio Network Temporary Identifier (RNTI) and ii) the value of the NDI field is "0": the 1 bit is reserved.

2. The method according to claim 1, wherein, Since the parameters are not configured, the transform precoder indicator field is based on 0 bits.

3. The method according to claim 1, wherein, The license associated with the PUSCH is either a dynamic license or a configuration license.

4. The method according to claim 1, wherein, The DCI format associated with the DCI is either DCI format 0_1 ​​or DCI format 0_2.

5. The method according to claim 4, wherein, The CRC is scrambled by the CS-RNTI, cell C-RNTI, semi-persistent SP-channel state information CSI-RNTI, or modulation and coding scheme MCS-C-RNTI.

6. The method according to claim 5, wherein, Based on i) the CRC being scrambled by the CS-RNTI, and ii) the value of the NDI field being "1": transform precoding for the PUSCH is enabled or disabled based on the transform precoder indicator field.

7. The method according to claim 6, wherein, The transmission of the PUSCH is based on PUSCH retransmission.

8. The method according to claim 7, wherein, The parameters in the configuration information, except for at least one parameter, are applied to the PUSCH retransmission, and The at least one parameter includes the transformPrecoder parameter.

9. The method according to claim 5, wherein, Based on the CRC, scrambled by the C-RNTI or the MCS-C-RNTI: enable or disable transform precoding for the PUSCH based on the transform precoder indicator field.

10. The method according to claim 5, wherein, For the same serving cell, the bit width of the first field in the DCI format 0_1 ​​or the DCI format 0_2 based on the CS-RNTI is equal to the bit width of the same field in the DCI format 0_1 ​​or the DCI format 0_2 based on the C-RNTI.

11. The method according to claim 10, wherein, The first field is the transform precoder indicator field.

12. The method according to claim 2, wherein, If the payload size of the DCI format associated with the DCI is less than a defined value, 0 is appended to the DCI format until the payload size equals the defined value.

13. The method according to claim 1, wherein, Based on i) the CRC being scrambled by the CS-RNTI, and ii) the value of the NDI field being "0": perform the DCI verification to enable scheduling activation based on configuration license.

14. The method according to claim 13, wherein, The verification of the DCI is implemented based on the fields in the DCI.

15. A user equipment (UE), the UE comprising: One or more transceivers; One or more processors; as well as One or more memories, said one or more memories being connected to said one or more processors and storing instructions. The instructions are based on the one or more processors being executed to configure the one or more processors to perform all the steps of the method according to any one of claims 1 to 14.

16. An apparatus comprising: One or more memory units; as well as One or more processors, said one or more processors being operatively connected to said one or more memories, The one or more memory storage instructions are based on the one or more processors executing to configure the one or more processors to perform all the steps of the method according to any one of claims 1 to 14.

17. One or more non-transitory computer-readable media, wherein the one or more non-transitory computer-readable media stores instructions. in, The instructions, which can be executed by one or more processors, configure the one or more processors to perform all the steps of the method according to any one of claims 1 to 14.

18. A method performed by a base station, the method comprising the following steps: Send configuration information related to the Physical Uplink Shared Channel (PUSCH); Send downlink control information (DCI) including the New Data Indicator (NDI) field; as well as The PUSCH is received based on the DCI. Specifically, parameters related to the presence of a transform precoder indicator field in the DCI are configured based on the configuration information, and the transform precoder indicator field is based on 1 bit. The 1-bit value indicates whether the transform precoder is enabled or disabled, and Wherein, i) the Cyclic Redundancy Check (CRC) associated with the DCI is scrambled by the Configuration Scheduling CS-Radio Network Temporary Identifier (RNTI) and ii) the value of the NDI field is "0": the 1 bit is reserved.

19. A base station, the base station comprising: One or more transceivers; One or more processors; as well as One or more memories, said one or more memories being connected to said one or more processors and storing instructions. The instructions are based on the one or more processors being executed to configure the one or more processors to perform all the steps of the method according to claim 18.

Images