Method and apparatus for transmitting and receiving uplink channels in a wireless communication system

Abstract

A method according to one embodiment of this specification includes 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. Based on the configuration information, a parameter relating to the presence of a transform precoder indicator field within the DCI is set, and the transform precoder indicator field is characterized in that the transform precoder indicator field is based on 1 bit, i) the CRC associated with the DCI is scrambled by CS-RNTI, and ii) the value of the NDI field is "0", the 1 bit is reserved.

Description

Technical Field

[0001] This specification relates to a method and apparatus for transmission and reception of an uplink channel in a wireless communication system.

Background Art

[0002] Mobile communication systems have been developed to provide voice services while ensuring user mobility. However, mobile communication systems have expanded their scope to include not only voice but also data services, and currently, due to an explosive increase in traffic, a shortage of resources has occurred, and users are demanding faster services, so more advanced mobile communication systems are required.

[0003] The requirements for next-generation mobile communication systems are significant and must support accommodation of explosive data traffic, an epochal increase in transmission rate per user, accommodation of a significantly increased number of connected devices, very low end-to-end latency, and high energy efficiency. Therefore, various technologies such as dual connectivity, massive multiple input multiple output (Massive MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking are being studied.

[0004] On the other hand, according to existing operations, the UL waveform is set in an inverse manner. The UL waveform may vary based on the presence / absence or enablement of transform precoding. This will be specifically described below.

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

[0006] 2) If transform precoding is not applied (i.e., if transform precoding is disabled), the waveform is based on Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM).

[0007] Whether or not the transform precoding is enabled is set / instructed semi-statically.

[0008] For example, whether or not transform precoding is enabled may be determined based on the RRC parameter. i) If the transformPrecoder parameter is set based on PUSCH-config, whether or not transform precoding is enabled may be determined based on the corresponding transformPrecoder parameter. ii) If the transformPrecoder parameter is not set, whether or not transform precoding is enabled may be determined based on the msg3-transformPrecoder parameter.

[0009] Regarding Rel-18 coverage enhancement, the Dynamic Waveform Switching (DWS) operation associated with the aforementioned UL waveform is supported. A field related to the DWS (e.g., a transform precoder indicator) has been introduced into the DCI format (0_1 / 0_2). The transform precoder indicator field can be applied to Dynamic Grant (DG)PUSCH and Configured Grant (CG)PUSCH.

[0010] On the other hand, in the case of DG PUSCH, it is scheduled by C-RNTI-based DCI. (Type 2) In the case of CG PUSCH, it is activated by CS-RNTI-based DCI. According to DCI size alignment, it is assumed that the bit width of a field in the DCI format based on C-RNTI is the same as the bit width of the same field in the DCI format based on CS-RNTI. [Overview of the project] [Problems that the invention aims to solve]

[0011] When the DWS is enabled by the RRC parameter (i.e., when the RRC parameter indicating the presence of the transform precoder indicator field within the DCI format is set), the transform precoder indicator field (1 bit) becomes present within the DCI format.

[0012] Even if the CRC associated with the DCI format is scrambled by different RNTIs (e.g., C-RNTI or CS-RNTI), the RRC parameters and DCI size alignment ensure that the DCI format has the same bit-width conversion precoder indicator field. However, for DG PUSCH and CG PUSCH based on different scheduling schemes, the relevant field must be interpreted differently.

[0013] The purpose of this specification is to propose a method for interpreting / applying the enable / enable status of transform precoding and related fields in the DCI format according to the uplink scheduling scheme (e.g., dynamic grant or configured-grant).

[0014] The technical problems to be addressed in this specification are not limited to those mentioned above, and other technical problems not mentioned can be clearly understood by a person skilled in the art to which the present invention pertains from the following description. [Means for solving the problem]

[0015] A method performed by a terminal according to one embodiment of this specification includes the steps of receiving configuration information related to a Physical Uplink Shared Channel (PUSCH), receiving Downlink Control Information (DCI) including an NDI (New Data Indicator) field, and transmitting the PUSCH based on the DCI.

[0016] Based on the aforementioned configuration information, and based on the parameter regarding the presence of the DCI internal transform precoder indicator field being set, the transform precoder indicator field is based on 1 bit.

[0017] The value of the aforementioned 1 bit indicates whether the transform precoder is enabled or disabled.

[0018] i) The Cyclic Redundancy Check (CRC) associated with the DCI is scrambled by the Configured Scheduling (CS)-Radio Network Temporary Indenter (RNTI), and ii) based on the value of the NDI field being "0", the 1 bit is reserved.

[0019] Based on the fact that the aforementioned parameter is not set, the conversion precoder indicator field may be 0 bits.

[0020] The grant associated with the aforementioned PUSCH may be a dynamic grant or a configured grant.

[0021] The DCI format associated with the aforementioned DCI (DCI format) may be DCI format 0_1 ​​or DCI format 0_2.

[0022] The CRC may be scrambled by CS-RNTI, C(Cell)-RNTI, SP(Semi-Persistent)-CSI(Channel State Information)-RNTI, or MCS(Modulation Coding Scheme)-C-RNTI.

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

[0024] The transmission of the PUSCH can be based on PUSCH retransmission.

[0025] The parameters within the configuration information excluding at least one parameter can be applied to the PUSCH retransmission. The at least one parameter can include a transformPrecoder parameter.

[0026] Based on the CRC being scrambled by the C-RNTI or the MCS-C-RNTI: the transform precoding for the PUSCH can be enabled or disabled based on the transform precoder indicator field.

[0027] For the same serving cell, the bit width of the first field within DCI format 0_1 or DCI format 0_2 based on the CS-RNTI may be the same as the bit width of the same field within DCI format 0_1 or DCI format 0_2 based on the C-RNTI.

[0028] The first field can be the transform precoder indicator field.

[0029] Based on the fact that the payload size of the DCI format associated with the DCI is smaller than a defined value, zeros (0) can be added to the DCI format until the payload size becomes equal to the defined value.

[0030] i) The CRC is scrambled by the CS-RNTI, and ii) the value of the NDI field is "0": The DCI may be validated for scheduling activation based on a configured grant.

[0031] Based on the fields within the DCI, the validation of the DCI can be achieved.

[0032] A terminal according to another embodiment of this specification includes one or more transceivers, one or more processors, and one or more memories connected to the one or more processors for storing instructions.

[0033] The instruction is characterized in that, based on the fact that it is executed by one or more processors, the one or more processors are configured to execute all the steps of any one of the methods.

[0034] Apparatus according to other embodiments of this specification includes one or more memories and one or more processors functionally connected to the one or more memories.

[0035] The one or more memory units are characterized by storing instructions that, based on being executed by the one or more processors, cause the one or more processors to execute all steps of any one of the methods.

[0036] One or more non-transitory computer-readable media according to other embodiments of this specification store instructions. The instructions, executable by one or more processors, are configured such that the one or more processors execute all steps of any one of the methods.

[0037] A method performed by a base station according to another embodiment of this specification includes the steps of transmitting configuration information related to a Physical Uplink Shared Channel (PUSCH), transmitting Downlink Control Information (DCI) including a New Data Indicator (NDI) field, and receiving the PUSCH based on the DCI.

[0038] Based on the aforementioned configuration information, and based on the parameter regarding the presence of the DCI internal transform precoder indicator field being set, the transform precoder indicator field is based on 1 bit.

[0039] The value of the aforementioned 1 bit indicates whether the transform precoder is enabled or disabled.

[0040] i) The Cyclic Redundancy Check (CRC) associated with the DCI is scrambled by the Configured Scheduling (CS)-Radio Network Temporary Indenter (RNTI), and ii) based on the value of the NDI field being "0", the 1 bit is reserved.

[0041] A base station according to a further different embodiment of this specification includes one or more transceivers, one or more processors, and one or more memories connected to the one or more processors for storing instructions.

[0042] The instructions are characterized in that, based on the fact that they are to be executed by one or more processors, the one or more processors are configured to perform all the steps of the method. [Effects of the Invention]

[0043] In embodiments of this specification, when DCIs have CRCs scrambled based on different RNTIs (e.g., CS-RNTI, C-RNTI) and have transform precoder indicator fields of the same bit width, it is clearly defined how such fields should be interpreted. This thus prevents ambiguity related to the application of transform precoding in DG PUSCH / CG PUSCH.

[0044] Furthermore, even if the transform precoder indicator field exists in the DCI, there are clearly defined cases in which the operation based on the analysis of that field is not applied (for example, when CG PUSCH is activated (= the value of the NDI field is 0), the operation based on the indication of that field is applied X). Dynamic waveform switching is not applied in all cases where the transform precoder indicator field exists in the DCI, but can be applied only to specific cases in which dynamic waveform switching is required. For example, in the case of retransmission of CG PUSCH (when the value of the NDI field is 1), the operation according to the indication of the transform precoder indicator field may be applied. Therefore, delays due to waveform switching can be minimized by limiting the cases in which waveform switching is performed unnecessarily.

[0045] Furthermore, the effectiveness of dynamic waveform switching, which was introduced to utilize waveforms better suited to the channel environment, can be ensured.

[0046] The effects described herein are not limited to those mentioned above, and other effects not mentioned can be clearly understood by a person skilled in the art to which the present invention pertains from the following description. [Brief explanation of the drawing]

[0047] [Figure 1] This figure shows an example of uplink transmission and reception operation. [Figure 2] This is a flowchart illustrating a method performed by a terminal according to one embodiment of this specification. [Figure 3] This is a flowchart illustrating the method performed by a base station according to other embodiments of this specification. [Figure 4] This figure shows the configurations of the first and second apparatus according to embodiments of this specification. [Modes for carrying out the invention]

[0048] Preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary embodiments of the present invention and not to show only the embodiments in which the invention can be carried out. The following detailed description includes specific details in order to provide a complete understanding of the invention. However, those skilled in the art will see that the invention can be carried out without such specific details.

[0049] In some cases, known structures and devices may be omitted or shown in the form of block diagrams focusing on the core function of each structure and device, in order to avoid ambiguity of the concept of the present invention.

[0050] In the following, 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 downlink, the transmitter can be part of the base station, and the receiver can be part of the terminal. In uplink, the transmitter can be part of the terminal, and the receiver can be part of the base station. The base station can also be described as the first communication device, and the terminal as the second communication device. The term base station (BS) can be replaced with terms such as fixed station, NodeB, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP), network (5G network), AI system, RSU (roadside unit), vehicle, robot, drone (unmanned aerial vehicle, UAV), AR (Augmented Reality) device, and VR (Virtual Reality) device. Furthermore, a terminal can be fixed or mobile, and can be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) equipment, M2M (Machine-to-Machine) equipment, D2D (Device-to-Device) equipment, vehicle, robot, AI module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) equipment, and VR (Virtual Reality) equipment.

[0051] Uplink Channel Structure

[0052] The terminal transmits the relevant signals to the base station via the uplink channel described later, and the base station receives the relevant signals from the terminal via the uplink channel described later.

[0053] (1) Physical uplink shared channel (PUSCH)

[0054] PUSCH carries uplink data (e.g., UL-shared channel transport block, UL-SCH TB) and / or uplink control information (UCI) and is transmitted based on a CP-OFDM (Cyclic Prefix - Orthogonal Frequency Division Multiplexing) waveform or a DFT-S-OFDM (Discrete Fourier Transform - spread - Orthogonal Frequency Division Multiplexing) waveform. When PUSCH is transmitted based on a DFT-S-OFDM waveform, the terminal applies transform precoding to transmit PUSCH. For example, if transform precoding is not possible (e.g., transform precoding is disabled), the terminal transmits PUSCH based on a CP-OFDM waveform, and if transform precoding is possible (e.g., transform precoding is enabled), the terminal can transmit PUSCH based on a CP-OFDM waveform or a DFT-S-OFDM waveform. PUSCH transmissions can be dynamically scheduled by UL grants within DCI, or semi-statically scheduled based on higher-layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling (e.g., PDCCH)). PUSCH transmissions can be performed in a codebook-based or non-codebook-based manner.

[0055] (2) Physical uplink control channel (PUCCH)

[0056] A PUCCH carries uplink control information, HARQ-ACK, and / or scheduling requests (SRs), and is divided into Short PUCCH and Long PUCCH depending on the PUCCH transmission length. Table 1 below illustrates the PUCCH format.

[0057] [Table 1]

[0058] PUCCH format 0 carries UCIs up to 2 bits in size and is mapped to a sequence base for transmission. Specifically, a terminal transmits one sequence out of several sequences via a PUCCH, which is PUCCH format 0, and transmits a specific UCI to the base station. A terminal transmits a PUCCH, which is PUCCH format 0, within the PUCCH resource for the corresponding SR configuration only when transmitting a positive SR.

[0059] PUCCH format 1 carries UCIs up to 2 bits in size, and the modulation symbols are spread in the time domain by orthogonal cover codes (OCCs) (which are set depending on whether the frequency is hopping). DMRS transmits the modulation symbols with symbols that are not transmitted (i.e., they are transmitted via TDM (Time Division Multiplexing)).

[0060] PUCCH format 2 carries UCIs with bit sizes greater than 2 bits, and the modulated symbols are transmitted via DMRS and FDM (Frequency Division Multiplexing). DM-RS is located at symbol indices #1, #4, #7, and #10 within a given resource block at 1 / 3 density. PN (Pseudo Noise) sequences are used for DM_RS sequences. Frequency hopping can be activated for 2-symbol PUCCH format 2.

[0061] PUCCH format 3 carries UCIs with bit sizes greater than 2 bits that are not terminally multiplexed within the same physical resource block. In other words, PUCCH resources in PUCCH format 3 do not contain orthogonal cover codes. Modulation symbols are transmitted via DMRS and TDM (Time Division Multiplexing).

[0062] PUCCH format 4 supports multiplexing of up to four terminals within the same physical resource block and carries UCIs with bit sizes greater than 2 bits. In other words, PUCCH resources in PUCCH format 3 include orthogonal cover codes. Modulated symbols are transmitted via DMRS and TDM (Time Division Multiplexing).

[0063] Uplink transmission and reception operation

[0064] Figure 1 shows an example of uplink transmission and reception operation.

[0065] As shown in Figure 1, the base station schedules uplink transmissions such as frequency / time resources, transmission layer, uplink precoder, and MCS (S110). In particular, the base station enables the terminal to determine the beam for PUSCH transmission through beam management operations. The terminal then receives a DCI from the base station on the PDCCH for uplink scheduling (i.e., including PUSCH scheduling information) (S120). DCI format 0_0 or 0_1 can be used for uplink scheduling. In particular, DCI format 0_1 ​​includes the following information: DCI format identifier, UL / SUL (Supplementary uplink) indicator, Bandwidth part indicator, Frequency domain resource assignment, Time domain resource assignment, Frequency hopping flag, Modulation and coding scheme (MCS), SRS resource indicator (SRI), Precoding information and number of layers, Antenna port(s), SRS request, DMS sequence initialization, and UL-SCH (Uplink Shared Channel) indicator.

[0066] In particular, the SRS resource indicator field can indicate an SRS resource set within the SRS resource set associated with the higher-level parameter "usage". Additionally, "spatialRelationInfo" can be set for each SRS resource, and its value may be one of {CRI, SSB, SRI}.

[0067] The terminal then transmits uplink data to the base station on a PUSCH (S130). When the terminal detects a PDCCH containing DCI format 0_0 or 0_1, it transmits the corresponding PUSCH according to the instructions of the DCI. Two transmission methods are supported for PUSCH transmission: codebook-based transmission and non-codebook-based transmission.

[0068] In the case of codebook-based transmission, when the upper layer parameter "txConfig" is set to "codebook", the terminal is configured for codebook-based transmission. Conversely, when the upper layer parameter "txConfig" is set to "nonCodebook", the terminal is configured for non-codebook-based transmission. If the upper layer parameter "txConfig" is not set, the terminal does not expect to be scheduled by DCI format 0_1. When PUSCH is scheduled by DCI format 0_0, PUSCH transmission is based on a single antenna port. In the case of codebook-based transmission, PUSCH can be scheduled by DCI format 0_0, DCI format 0_1, or semi-statically. When this PUSCH is scheduled by DCI format 0_1, the terminal determines the PUSCH transmission precoder based on the SRI, TPMI (Transmit Precoding Matrix Indicator), and transmit rank from DCI, as given by the SRS resource indicator field and precoding information and layer count field. TPMI is used to specify the precoder to be applied across antenna ports, corresponding to the SRS resource selected by SRI when multiple SRS resources are configured. Alternatively, when a single SRS resource is configured, TPMI is used to specify the precoder to be applied across antenna ports, corresponding to that single SRS resource. A transmission precoder is selected from the uplink codebook having the same number of antenna ports as the upper-layer parameter "nrofSRS-Ports". When the upper layer, set to "codebook", is set to the parameter "txConfig", the terminal is configured with at least one SRS resource. The SRI specified in slot n relates to the most recent transmission of the SRS resource identified by the SRI, where the SRS resource precedes the PDCCH (i.e., slot n) carrying the SRI.

[0069] For non-codebook-based transmissions, PUSCH can be scheduled in DCI format 0_0, DCI format 0_1, or semi-statically. When multiple SRS resources are configured, the terminal can determine the PUSCH precoder and transmit rank based on the broadband SRI, which is given by the SRS resource indicator in DCI or by the higher-layer parameter "srs-resource Indicator". The terminal utilizes one or multiple SRS resources for SRS transmission, where the number of SRS resources can be configured for simultaneous transmission within the same RB based on UE capability. Only one SRS port can be configured per 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 transmissions is four. The SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS transmission precedes the PDCCH (i.e., slot n) carrying the SRI.

[0070] Transform Precoder field

[0071] The following describes the settings for the Transform Precoder that can be applied to the embodiments described later.

[0072] [Table 2] JPEG2026515670000004.jpg51141

[0073] JPEG2026515670000005.jpg195143JPEG2026515670000006.jpg26141

[0074] JPEG2026515670000007.jpg192143JPEG2026515670000008.jpg82141

[0075] JPEG2026515670000009.jpg192144

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

[0077] [Table 3] JPEG2026515670000011.jpg104143

[0078] JPEG2026515670000012.jpg166143

[0079] JPEG2026515670000013.jpg177144JPEG2026515670000014.jpg86142

[0080] JPEG2026515670000015.jpg101142JPEG2026515670000016.jpg155142

[0081] JPEG2026515670000017.jpg93142

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

[0083] [Table 4] JPEG2026515670000019.jpg47141

[0084] JPEG2026515670000020.jpg150142JPEG2026515670000021.jpg137143

[0085] JPEG2026515670000022.jpg193142JPEG2026515670000023.jpg80142

[0086] JPEG2026515670000024.jpg117142JPEG2026515670000025.jpg162142

[0087] JPEG2026515670000026.jpg195143JPEG2026515670000027.jpg47141

[0088] JPEG2026515670000028.jpg139142JPEG2026515670000029.jpg139143

[0089] JPEG2026515670000030.jpg183143JPEG2026515670000031.jpg133142

[0090] JPEG2026515670000032.jpg52141

[0091] JPEG2026515670000033.jpg196143JPEG2026515670000034.jpg103143

[0092] JPEG2026515670000035.jpg88142JPEG2026515670000036.jpg187142

[0093] JPEG2026515670000037.jpg192143JPEG2026515670000038.jpg102142

[0094] JPEG2026515670000039.jpg56141

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

[0096] The details carefully examined earlier (uplink channel structure, uplink transmit / receive operation, transform precoder related settings (Tables 2-4), etc.) may be applied in combination with the methods proposed herein, or may be supplemented to clarify the technical features of the methods proposed herein. Of course, the methods described below, separated only for the convenience of explanation, may have some configurations of one method replaced with some configurations of another, or may be applied in combination with each other.

[0097] Dynamic waveform switching (DWS) may be supported to improve coverage in NR. Below, we will carefully examine how to configure the terminal's ULwaveform depending on the type and context of the DCI format, assuming that an indication field for DWS is supported.

[0098] Currently, in NR, it can be defined that base stations can specify which waveform to use, CP-OFDM or DFT-S-OFDM, through RRC signaling (e.g., SIB1, UE-specific RRC signaling, etc.).

[0099] Specifically, in the 4-step RACH procedure, the waveform of Msg.3PUSCH can be set / instructed / determined as follows:

[0100] When “msg3-transformPrecoder” is set to enable (i.e., when the terminal receives a configuration from the base station that includes the msg3-transformPrecoder parameter (e.g., RACH-ConfigCommon in Table 2)), the transform precoder for Msg3 transmission is enabled. In other words, transform precoding for Msg.3PUSCH transmission is enabled. In this case, the terminal uses DFT-S-OFDM as the waveform for Msg.3PUSCH.

[0101] If the “msg3-transformPrecoder” parameter field is empty (i.e., the terminal receives a setting from the base station that does not include 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 Msg.3PUSCH transmission is disabled. In this case, the terminal uses CP-OFDM as the waveform for Msg.3PUSCH.

[0102] For a 2-step RACH procedure, the waveform of MsgA PUSCH can be set / instructed / determined as follows:

[0103] When "MsgA-TransformPrecoder" is set to enable (i.e., when the terminal receives a configuration from the base station that includes the "enabled" MsgA-TransformPrecoder parameter (e.g., MsgA-PUSCH-Config in Table 3)), the transform precoder for MsgA transmission, or in other words, the transform precoding for MsgA PUSCH transmission, is enabled. In this case, the terminal uses DFT-S-OFDM as the waveform for MsgA PUSCH.

[0104] When "MsgA-TransformPrecoder" is set to disabled (i.e., when the terminal receives a configuration from the base station that includes the MsgA-TransformPrecoder parameter set to 'disabled' (e.g., MsgA-PUSCH-Config in Table 3)), the transform precoder for MsgA transmission is disabled. In other words, the transform precoding for MsgA PUSCH transmission is disabled. In this case, the terminal uses CP-OFDM as the waveform for MsgA PUSCH.

[0105] The waveforms of other UL channels (e.g., normal PUSCH, configured PUSCH, etc.), excluding Msg.3PUSCH and Msg.A PUSCH, can be set / instructed / determined as follows:

[0106] When "transformPrecoder" is set to enable (i.e., when the terminal receives a configuration from the base station that includes the transformPrecoder parameter set to "enabled" (e.g., PUSCH-Config in Table 4)), the transform precoder for transmission on other UL channels (e.g., PUSCH) is enabled. In other words, transform precoding for transmission on other UL channels (e.g., PUSCH) is enabled. In this case, the terminal uses DFT-S-OFDM as the waveform for other UL channels (e.g., PUSCH).

[0107] When "transformPrecoder" is set to disabled (i.e., when the terminal receives a configuration from the base station that includes the transformPrecoder parameter set to "disabled" (e.g., PUSCH-Config in Table 4)), the transform precoder for transmission on other UL channels (e.g., PUSCH) is disabled. In other words, transform precoding for transmission on other UL channels (e.g., PUSCH) is disabled. In this case, the terminal uses CP-OFDM as the waveform for other UL channels (e.g., PUSCH).

[0108] Furthermore, unless the corresponding "transformPrecoder" parameter is specified separately, the terminal will operate according to the "msg3-transformPrecoder" setting. Transform precoding will be applied or not applied based on the MsgA-TransformPrecoder setting (enabled or disabled). In other words, whether or not transform precoding is applied to uplink transmission may be determined based on the MsgA-TransformPrecoder setting (enabled or disabled).

[0109] On the other hand, dynamic waveform switching operation is being considered to enhance UL coverage in existing NR systems.

[0110] Recently, standardization meetings have been discussing how to interpret / define terminal / base station operation when a dynamic waveform switching indication field is introduced into DCI information. For example, differences in analysis between DCI formats scrambled with C-RNTI and / or CS-RNTI may occur depending on the PUSCH transmission method that supports dynamic waveform switching, DG PUSCH and / or CG PUSCH Type 2. Another example is that when the introduction of the dynamic waveform switching indication field determines what waveform (i.e., CP-OFDM or DFT-S-OFDM) the terminal is instructed to receive, a field dependent on that will be created, and differences in DCI payload size are also being treated as an issue. On the other hand, in the case of CG PUSCH Type 1, depending on its definition, PUSCH transmission is performed only via higher layer (by RRCsignalling) parameters, making it difficult to expect transmission operation via DCI reception. Therefore, in order to equalize the differences in DCI payload size caused by the issues mentioned earlier, a new definition / determination must be established regarding how DCI size alignment should be performed for each PUSCH transmission scheme, i.e., DG-PUSCH or CG-PUSCH Type 2, when introducing a dynamic waveform switching indication field.

[0111] First, a careful conceptual examination of conventional DCI size alignment defines a per-format-based DCI size alignment method that performs zero padding on the end of the shorter DCI among those being compared, thereby equalizing the overall payload size. In performing DCI size alignment between DCIs corresponding to C-RNTI / CS-RNTI, the operation of zero padding (i.e., per-field alignment) from the MSB of each field of the DCI corresponding to C-RNTI to match the size of each field of the DCI corresponding to CS-RNTI is defined as shown in Table 5 below.

[0112] [Table 5]

[0113] When a DCI indication field for dynamic waveform switching support is introduced based on the aforementioned conventional DCI size alignment method, which is per-format or per-field based, the interpretation of this field may need to be redefined.

[0114] Therefore, in this specification, when a dynamic wave switching indication field (hereinafter referred to as the DWS field) is introduced, a method for analyzing / determining the DWS field is proposed, which is monitored by the terminal and received via the PDCCH according to the DCI.

[0115] Dynamic waveform switching (DWS) is the operation of dynamically enabling or disabling the conversion precoder.

[0116] Therefore, in this specification, “dynamic waveform switching field” and “DWS field” may be interpreted / substituted with “transform precoder indicator field.” Furthermore, higher layer parameters (RRC parameters) related to enabling or disabling the DWS may be interpreted / substituted with higher layer parameters (RRC parameters) related to the presence of the transform precoder indicator field in the DCI. Furthermore, indications of waveform (e.g., DFT-S-OFDM or CP-OFDM) may be interpreted / substituted with indications of enabling / disabling the transform precoder.

[0117] In the following sections, we will carefully examine the terminal's DWS field size analysis / determination method depending on the type and context of the DCI format, assuming that an indication field for dynamic waveform switching is supported.

[0118] In this specification, the phrase "the CRC (Cyclic Redundancy Check) of a specific DCI (e.g., DCI format 0_1, 0_2) has been scrambled to a specific RNTI (Radio Network Temporary Indenter) (e.g., C(Cell)-RNTI, CS(Configured Scheduling)-RNTI)" may be replaced for the sake of brevity with the phrases "DCI corresponding to a specific RNTI" or "DCI of a specific RNTI" or similar expressions, all of which have the same meaning.

[0119] It needs to be determined how per-field matching will occur between a CG (Configured Grant) setting (e.g., CG-PUSCH Type 2), which can each have a different waveform, and a DCI corresponding to a C-RNTI whose field size changes depending on the value of the DWS field. As an example, per-field matching can be performed by assuming that the same waveform as the waveform value specified in the CG setting (e.g., CG-PUSCH Type 2) is specified in the DWS field of the DCI corresponding to the C-RNTI.

[0120] Method 1

[0121] In the following sections, we will carefully examine how the DWS field is interpreted when it is introduced (or present) in DCI formats 0_1 and 0_2. Specifically, we will examine how the DWS field in DCI formats 0_1 and 0_2 is interpreted for PUSCH transmission methods (e.g., DG PUSCH or CG PUSCH) when i) DWS enable (and / or disable) settings are supported based on higher layer parameters, and ii) DWS is enabled.

[0122] Case 1. For DCI formats 0_1 and 0_2 corresponding to C-RNTI that include a DWS field, the size of the DWS field can be set / determined as 1 bit.

[0123] For example, the 1-bit value can represent the waveform value for dynamic waveform switching (e.g., CP-OFDM = 0 (or 1), DFT-S-OFDM = 1 (or 0)). For example, the 1-bit value can represent the enable or disable state of the transform precoder.

[0124] When the terminal receives DCI formats 0_1, 0_2 of C-RNTI, which include the DWS field, it can interpret the DWS field as 1 bit in size and determine the waveform indicated for dynamic waveform switching according to 0 or 1 (e.g., CP-OFDM = 0 (or 1), DFT-S-OFDM = 1 (or 0)). The terminal can then further analyze fields (e.g., FDRA, TPMI, antenna port) that may change depending on the indicated waveform value during the DCI analysis process.

[0125] Case 2. In the case of DCI formats 0_1 and 0_2 corresponding to CS-RNTI that include a 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.

[0126] The value of the DWS field may be defined based on at least one of the following embodiments.

[0127] The value of the Alt 1.DWS field can be defined / indicated in the same way as the waveform set to semi-static in the Higher layer parameter.

[0128] The value of the DWS field can be defined to have the same waveform as the value set in a higher layer parameter (e.g., transformPrecoder). For example, if transformPrecoder = enabled, the DWS field may be indicated with a value corresponding to DFT-S-OFDM. When a terminal receives DCI formats 0_1, 0_2 of CS-RNTI with NDI = 0 and containing the DWS field, it can interpret the DWS field as being 1 bit in size. "NDI = 0" means that the value of the New Data Indicator (NDI) field in the corresponding DCI formats 0_1, 0_2 is 0. The terminal confirms that the waveform indicated by the set higher layer parameter (transformPrecoder) is the same as the waveform indicated by the DWS field. The said waveform can be interpreted / replaced as enable / disable the transform precoder. The terminal expects the same waveform as the one set / indicated through higher layer signaling to be indicated via the DWS field. Otherwise, the terminal can determine that the activation / deactivation / release operation of the corresponding CG-PUSCH is invalid (=error case).

[0129] Alt 2. Defined by the Reserved bit

[0130] The DWS field may be defined as a Reserved bit. When a terminal receives DCI formats 0_1 and 0_2 of a CS-RNTI set to NDI=0, which includes a DWS field, the terminal does not perform any further analysis because the DWS field is a Reserved bit. The fact that the terminal does not perform a separate interpretation means that it does not perform any action based on the value of the DWS field (such as deciding whether or not to apply transform precoding).

[0131] Alt 3. DWS field value is defined separately / no restrictions.

[0132] The value of the DWS field can be defined regardless of the value set in the Higher layer parameter (e.g., transformPrecoder). In other words, from the base station's perspective, there may be no separate restriction on the value of the DWS field. When a terminal receives DCI format 0_1, 0_2 of a CS-RNTI set to NDI = 0 that includes the DWS field, it interprets the DWS field as 1 bit in size, but does not interpret the value of the DWS field separately.

[0133] The terminal can subsequently interpret additional fields (e.g., FDRA, TPMI, antenna port) that may change depending on the waveform value indicated through the DCI DWS field corresponding to C-RNTI and the waveform value for CG-PUSCH indicated through higher layer signaling during the DCI analysis process.

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

[0135] For example, the 1-bit value can represent the waveform value for dynamic waveform switching (e.g., CP-OFDM=0 (or 1), DFT-S-OFDM=1 (or 0)). For example, the 1-bit value can represent the enable or disable status of the transform precoder.

[0136] When the terminal receives DCI formats 0_1, 0_2 of a CS-RNTI set to NDI=1 and containing the DWS field, it can interpret the DWS field as 1 bit in size and determine it as the waveform indicated for dynamic waveform switching according to 0 or 1 (e.g., CP-OFDM = 0 (or 1), DFT-S-OFDM = 1 (or 0)). The terminal can then further analyze fields (e.g., FDRA, TPMI, antenna port) that may change depending on the indicated waveform value during the DCI analysis process.

[0137] Method 2

[0138] In the following sections, we will carefully examine how the DWS field is interpreted when it is introduced (or present) in DCI formats 0_1 and 0_2. Specifically, we will carefully examine how the DWS field in DCI formats 0_1 and 0_2 is interpreted for PUSCH transmission methods (e.g., DG PUSCH or CG PUSCH) when i) DWS enabled or disabled is supported based on the higher layer parameter, and ii) DWS is disabled.

[0139] It is a clear fact that by setting the Higher layer parameter to DWS disabled, push transmission can be performed via dynamic indication even without supporting dynamic waveform switching. In this case, when configuring the DCI payload, the method of analyzing the terminal can be differentiated depending on whether or not a DWS field is present.

[0140] Approach 1. Analysis method when a DWS field is present

[0141] Alt 1. The value of the DWS field can be defined / indicated in the same way as the waveform set to semi-static in the Higher layer parameter.

[0142] The value of the DWS field can be defined to have the same waveform as the value set in the Higher layer parameter (e.g., transformPrecoder). For example, if transformPrecoder=enabled, the DWS field may be indicated with a value corresponding to DFT-S-OFDM. When the terminal receives DCI format 0_1, 0_2 of C-RNTI / CS-RNTI that includes the DWS field, it interprets the DWS field as 1 bit in size and checks whether the waveform pointed to by transformPrecoder set in the Higher layer parameter is the same as the waveform indicated by the DWS field. The terminal expects the same waveform as the one set / indicated through Higher layer signaling to be indicated via the DWS field. If not, the terminal can determine that the activation / deactivation / release operation of the corresponding CG-PUSCH is invalid (=error case).

[0143] Alternatively, since dynamic waveform switching is not supported, the terminal may be defined / configured not to interpret the relevant value.

[0144] Alt 2. Reserved bit is defined

[0145] The DWS field can be defined with a Reserved bit. When a terminal receives DCI format 0_1 ​​or 0_2 of C-RNTI / CS-RNTI that includes the DWS field, it does not perform any further analysis because the DWS field is a Reserved bit.

[0146] Alt 3. DWS field value is not defined separately / no restrictions.

[0147] The value of the DWS field can be defined regardless of the value set in the Higher layer parameter (e.g., transformPrecoder). In other words, from the base station's perspective, there may be no separate restrictions on the value of the DWS field. When a terminal receives DCI format 0_1 ​​or 0_2 of C-RNTI / CS-RNTI that includes the DWS field, it interprets the DWS field as 1 bit in size, but does not interpret the value of the DWS field separately. [

[0148] The terminal can subsequently interpret additional fields (e.g., FDRA, TPMI, antenna port) that may change depending on the waveform value for DG-PUSCH and the waveform value for CG-PUSCH indicated via higher layer signaling during the DCI analysis process.

[0149] Approach 2. Analysis method when the DWS field does not exist.

[0150] The absence of a DWS field could mean that the field is either absent from the DCI format or that the field is set to 0 bits.

[0151] If the higher layer 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.

[0152] -> 0 bit if the higher layer parameter DWS_Support-r18= disabled

[0153] If a new value, "dynamic," is defined in the higher layer parameter conversion precoder for dynamic waveform switching, the number of bits in the DWS field according to this embodiment can be expressed in the following form.

[0154] -> 0 bit unless the higher layer parameter transformPrecoder=dynamic

[0155] In this case, the terminal performs the same analysis operation as it would for an existing DCI payload size without a DWS field.

[0156] The embodiments described above were described as a method for defining a 1-bit DWS field and the corresponding terminal / base station operation, assuming a single-cell environment. However, the scope of application of the embodiments herein is not limited to a single-cell environment. Specifically, the embodiments described above may be similarly or substantially applied when a multi-bit DWS field is introduced in a multi-cell environment.

[0157] In other words, among the DWS fields composed of multiple bits, the field size that indicates a specific cell as the target may be 1 bit, and the aforementioned embodiments can be applied to the method for defining such 1-bit DWS field and the corresponding terminal / base station operation. In this case, one proposed method may be applied commonly to multiple cells, or an independent proposed method may be set / applied to each cell.

[0158] Embodiments based on the proposed methods 1 and 2 can be configured / applied to other UL signals / channels such as MSG3 PUSCH, MSGA preamble / PUSCH, and / or PUSCH / PUCCH. Furthermore, it is clear that an example of the proposed method described above can also be considered a type of proposed scheme, as it may also be included as one of the implementations described herein. Moreover, while the proposed schemes described above can be implemented independently, they may also be implemented in the form of a combination (or merger) of some of the proposed methods. The rules may be defined so that the base station notifies the terminal of information regarding the applicability of the proposed method (or information regarding the rules of the proposed method) via a predefined signal (e.g., a physical layer signal or a higher layer signal). The higher layer may include one or more functional layers such as MAC, RLC, PDCP, RRC, and SDAP.

[0159] The methods, embodiments, or descriptions for implementing the methods proposed herein may be applied separately or in combination of one or more methods (or embodiments or descriptions).

[0160] As an example, an operation based on at least one embodiment of Method 1 and / or Method 2 may be based on Table 6 below.

[0161] [Table 6] JPEG2026515670000042.jpg96142

[0162] JPEG2026515670000043.jpg101142

[0163] As an example, a DCI format including a DWS field (Conversion Precoder Indicator Field) based on at least one embodiment of Method 1 and / or Method 2 may be based on Table 7 below.

[0164] [Table 7]

[0165] In terms of implementation, the operation of the base station / terminal according to the above embodiment (for example, operation based on at least one of Method 1 and / or Method 2) can be handled by the device shown in Figure 4 (e.g., 100, 200), which will be described later.

[0166] Furthermore, the operation of the base station / terminal according to the above embodiment (for example, operation based on at least one of Method 1 and / or Method 2) can be stored in memory (for example, 140, 240 in Figure 4) in the form of instructions / programs (e.g., instructions, executable code) for driving at least one processor (e.g., 110, 210 in Figure 4).

[0167] The embodiments described above will now be specifically explained below with reference to Figures 2 and 3, focusing on the operation of the terminal and base station. It goes without saying that, for the sake of clarity, some components of one method may be replaced by components of another, or they may be applied in combination.

[0168] Figure 2 is a flowchart illustrating a method performed by a terminal according to one embodiment of this specification.

[0169] Referring to Figure 2, a method performed by a terminal according to one embodiment of this specification includes a step S210 of receiving configuration information n related to PUSCH, a step S220 of receiving DCI including NDI, and a step S230 of transmitting PUSCH based on DCI.

[0170] In S210, the terminal receives configuration information related to the Physical Uplink Channel (PUSCH) from the base station.

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

[0172] In S220, the terminal receives Downlink Control Information (DCI), which includes the NDI (New Data Indicator) field, from the base station.

[0173] In one embodiment, the transform precoder indicator field may be based on 1 bit, based on the setting information, a parameter relating to the presence of the transform precoder indicator field within the DCI is set. This embodiment may be based on Method 1 and / or Method 2. More specifically, i) the transform precoder indicator field may exist within the DCI based on the setting of the parameter, and ii) the size of the transform precoder indicator field within the DCI may be set to 0 based on the absence of the parameter.

[0174] For example, a single bit value can indicate whether the transform precoder is enabled or disabled.

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

[0176] As an example, the conversion precoder indicator field may be 0 bits based on the fact that the parameter is not set. This embodiment may be based on Method 2. Based on the fact that the payload size of the DCI format associated with the DCI is smaller than a defined value (e.g., 12 in Table 5), zeros may be added to the DCI format until the payload size is equal to the defined value. That is, one or more padding bits set to 0 for DCI size alignment may be added to the DCI format.

[0177] As an example, the DCI format associated with the aforementioned DCI (DCI format) may be DCI format 0_1 ​​or DCI format 0_2.

[0178] The CRC may be scrambled by CS-RNTI, C(Cell)-RNTI, SP(Semi-Persistent)-CSI(Channel State Information)-RNTI, or MCS(Modulation Coding Scheme)-C-RNTI.

[0179] In S230, the terminal transmits the PUSCH to the base station based on the DCI.

[0180] In one embodiment, the grant associated with the PUSCH may be a dynamic grant (DG) or a configured grant (CG). The PUSCH may be a DG PUSCH or a CG PUSCH. For example, the PUSCH may be scheduled based on the DCI. For example, the scheduling of the PUSCH may be activated based on the DCI. The configured grant may be configured grant Type 2.

[0181] In one embodiment, the aforementioned Dynamic waveform switching may be applied for PUSCH retransmission (based on Type 2 configured grant). Specifically, the transform precoding for the PUSCH may be enabled or disabled based on the transform precoder indicator field, i) the CRC is scrambled by the CS-RNTI, and ii) the value of the NDI field is "1". The transmission of the PUSCH may be based on PUSCH retransmission. This embodiment may be based on Case 3 of Method 1.

[0182] In this case, the parameters in the configuration information, excluding those related to the transform precoder, may be applied to the PUSCH retransmission. Specifically, instead of higher-layer parameters (e.g., transformPrecoder parameters), the enable or disable status of the transform precoder is indicated based on the transform precoder indicator field. As an example, the parameters in the configuration information, excluding at least one parameter, may be applied to the PUSCH retransmission. This at least one parameter may include the transformPrecoder parameter.

[0183] In one embodiment, the transform precoder indicator field is applied to a PUSCH scheduled by a DCI based on an RNTI different from the CS-RNTI. Specifically, based on the fact that the CRC has been scrambled by the C-RNTI or the MCS-C-RNTI: transform precoding for the PUSCH can be enabled or disabled based on the transform precoder indicator field.

[0184] In one embodiment, referring to Table 5, the size of a first field in a DCI format based on a first RNTI (e.g., CS-RNTI) may be the same as the size of the same field in a DCI format based on a second RNTI (e.g., C-RNTI). That is, the terminal does not expect the size of the first field to be larger than the size of the same field in a DCI format based on a second RNTI. Specifically, for the same serving cell, the bit width of the first field in the CS-RNTI-based DCI format 0_1 ​​or the DCI format 0_2 may be the same as the bit width of the same field in the C-RNTI-based DCI format 0_1 ​​or the DCI format 0_2. The first field may be the conversion precoder indicator field. In other words, the bit width (1) of the conversion precoder indicator field in a CS-RNTI-based DCI format is the same as the bit width (1) of the conversion precoder indicator field in a C-RNTI-based DCI format. However, as mentioned above, the same field having the same bit width can be interpreted / applied differently. For example, based on the value of the NDI field in the CS-RNTI-based DCI format being zero, the bits in the conversion precoder indicator field are reserved. For example, based on the value of the conversion precoder indicator field in the C-RNTI-based DCI format (or the CS-RNTI-based DCI format where the value of the NDI field is 1), the enable or disable of the conversion precoder is indicated.

[0185] In one embodiment, validation of the DCI format may be performed for the aforementioned scheduling activation. Specifically, based on the CRC being scrambled by the CS-RNTI and ii) the value of the NDI field being "0", validation of the DCI (i.e., the DCI format) may be performed for scheduling activation based on a configured grant. Based on the fields within the DCI, the validation of the DCI may be achieved. More specifically, the validation may be achieved based on the value of each of the fields being set as defined.

[0186] Based on the completion of the aforementioned verification, the terminal can consider the information within DCI to be a valid activation or valid release of the configured grant (i.e., a configured UL grant Type 2).

[0187] If the aforementioned verification is not completed, the terminal may discard all information within the DCI.

[0188] The field 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.

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

[0190] The operations based on S210 to S230 described above can be realized by the device shown in Figure 4. For example, terminal 200 can control one or more transceivers 230 and / or one or more memories 240 to perform the operations based on S210 to S230.

[0191] The above-mentioned embodiment will now be described in detail from the perspective of the base station's operation.

[0192] The S310-S330 described later correspond to the S210-S230 explained in Figure 2. Considering this correspondence, redundant explanations will be omitted. That is, the specific explanations of base station operations described later can be replaced by the explanations / embodiments in Figure 2 corresponding to those operations. For example, the explanations / embodiments of S210-S230 in Figure 2 can be further applied to the base station operations of S310-S330 described later.

[0193] Figure 3 is a flowchart illustrating a method performed by a base station according to other embodiments of this specification.

[0194] Referring to Figure 3, a method performed by a base station according to another embodiment of this specification includes a step S310 of transmitting configuration information related to PUSCH, a step S320 of transmitting DCI including NDI, and a step S330 of receiving PUSCH based on DCI.

[0195] In S310, the base station transmits configuration information regarding the Physical Uplink Channel (PUSCH) to the terminal.

[0196] In S320, the base station transmits Downlink Control Information (DCI), which includes an NDI (New Data Indicator) field, to the terminal.

[0197] In S330, the base station receives the PUSCH from the terminal based on the DCI.

[0198] The operations based on S310 to S330 described above can be realized by the device shown in Figure 4. For example, the base station 100 can control one or more transceivers 130 and / or one or more memories 140 to perform the operations based on S310 to S330.

[0199] The operations / terminology based on the embodiments described above were written assuming a 5G system. However, this is for illustrative purposes only and is not intended to limit the scope of the technical problems and solutions that this specification seeks to address to any particular system. In other words, the technical problems / issues / problems mentioned herein may also exist in other systems (e.g., 6G systems). It is clear that the embodiments of this specification can be extended to address problems that may also exist in such other systems. Therefore, for the extension of the embodiments of this specification to other systems, terms defined / described based on a 5G system may be replaced / modified with terms defined in such other systems (or generalized terms not specific to one system).

[0200] For example, a physical uplink shared channel (PUSCH) may be replaced / changed to the first uplink channel.

[0201] For example, configuration information can be replaced / modified with the first information.

[0202] For example, downlink control information (DCI) may be replaced / modified with second-party information.

[0203] In the following section, the apparatus to which the embodiments of this specification can be applied (apparatus that realizes the methods / operations according to the embodiments of this specification) will be described with reference to Figure 4.

[0204] Figure 4 shows the configurations of the first and second apparatus according to the embodiments of this specification.

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

[0206] The processor 110 performs baseband-related signal processing and may include a higher layer processing unit 111 and a physical layer processing unit 115. The higher layer processing unit 111 can process the operation of the MAC layer, RRC layer, or higher layers. The physical layer processing unit 115 can process the operation of the PHY layer. For example, if the first device 100 is a base station device in base station-terminal communication, the physical layer processing unit 115 can perform uplink received signal processing, downlink transmitted signal processing, etc. For example, if the first device 100 is a first terminal device in terminal-terminal communication, the physical layer processing unit 115 can perform downlink received signal processing, uplink transmitted signal processing, sidelink transmitted signal processing, etc. In addition to performing baseband-related signal processing, the processor 110 can also control the overall operation of the first device 100.

[0207] The antenna unit 120 may include one or more physical antennas, and if it includes multiple antennas, it can support MIMO transmission and reception. The transceiver 130 may include an RF (Radio Frequency) transmitter and an RF receiver. The memory 140 can store information processed by the processor 110, as well as software, an operating system, applications, etc., related to the operation of the first device 100, and may also include components such as buffers.

[0208] The processor 110 of the first device 100 can be configured to implement the operation of the base station in base station-terminal communication (or the operation of the first terminal device in terminal-terminal communication) in the embodiments described herein.

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

[0210] The processor 210 performs baseband-related signal processing and may include a higher layer processing unit 211 and a physical layer processing unit 215. The higher layer processing unit 211 can process the MAC layer, RRC layer, or higher layers. The physical layer processing unit 215 can process the PHY layer. For example, if the second device 200 is a terminal device in base station-terminal communication, the physical layer processing unit 215 can perform downlink received signal processing, uplink transmitted signal processing, etc. For example, if the second device 200 is a second terminal device in terminal-to-terminal communication, the physical layer processing unit 215 can perform downlink received signal processing, uplink transmitted signal processing, sidelink received signal processing, etc. In addition to performing baseband-related signal processing, the processor 210 can also control the overall operation of the second device 200.

[0211] The antenna unit 220 may include one or more physical antennas, and if it includes multiple antennas, it can support MIMO transmission and reception. The transceiver 230 may include an RF transmitter and an RF receiver. The memory 240 can store information processed by the processor 210, and software, an operating system, applications, etc., related to the operation of the second device 200, and may also include components such as buffers.

[0212] The processor 210 of the second device 200 can be configured to implement the operation of a terminal in base station-terminal communication (or the operation of a second terminal device in terminal-terminal communication) in the embodiments described herein.

[0213] In the operation of the first device 100 and the second device 200, the matters described in the examples of this disclosure regarding the base station and terminal in base station-terminal communication (or the first terminal and second terminal in terminal-terminal communication) can be applied in the same manner, and redundant explanations will be omitted.

[0214] Here, the wireless communication technologies implemented in the devices 100 and 200 of this disclosure may include not only LTE, NR, and 6G, but also Narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology is an example of LPWAN (Low Power Wide Area Network) technology and can be implemented using standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the aforementioned names.

[0215] Additionally or alternatively, the wireless communication technology implemented in the devices 100, 200 of this disclosure can communicate based on LTE-M technology. For example, LTE-M technology is an example of LPWAN technology and is known by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented using at least one of various standards such as 1) LTE CAT 0, 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, and is not limited to the names mentioned above.

[0216] Additionally or alternatively, the wireless communication technologies implemented in the devices 100, 200 of this disclosure may include, but are not limited to, at least one of ZigBee, Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN) technologies, with regard to low-power communication. For example, ZigBee technology can generate personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be referred to by a variety of names.

[0217] [Claims when filing an international application] [Claim 1] A method performed by the terminal (user equipment: UE), The steps include receiving configuration information related to the Physical Uplink Shared Channel (PUSCH), The steps include receiving Downlink Control Information (DCI) which includes the NDI (NewDataIndicator) field, The process includes the step of transmitting the PUSCH based on the DCI, Based on the aforementioned configuration information, and based on the fact that the parameters related to the presence of the DCI internal transform precoder indicator field have been set, the transform precoder indicator field is based on 1 bit. The aforementioned 1-bit value indicates whether the transform precoder is enabled or disabled. i) The CRC (Cyclic Redundancy Check) related to the DCI is scrambled by CS (Configured Scheduling)-RNTI (Radio Network Temporary Indenter), ii) A method characterized in that the 1 bit is reserved based on the value of the NDI field being "0". [Claim 2] The method according to claim 1, characterized in that the conversion precoder indicator field is 0 bits based on the fact that the parameter is not set. [Claim 3] The method according to claim 1, characterized in that the grant associated with PUSCH is a dynamic grant or a configured grant. [Claim 4] The method according to claim 1, characterized in that the DCI Format (DCI format) related to the DCI is DCI format0_1 or DCI format0_2. [Claim 5] The method according to claim 4, characterized in that the CRC is scrambled by CS-RNTI, C(Cell)-RNTI, SP(Semi-Persistent)-CSI(Channel State Information)-RNTI, or MCS(Modulation Coding Scheme)-C-RNTI. [Claim 6] The method according to claim 5, characterized in that i) the CRC is scrambled by the CS-RNTI, and ii) based on the value of the NDI field being "1", the transform precoding for the PUSCH is enabled or disabled based on the transform precoder indicator field. [Claim 7] The method according to claim 6, characterized in that the transmission of PUSCH is based on PUSCH retransmission. [Claim 8] The parameters in the configuration information, excluding at least one parameter, are applied to the PUSCH retransmission. The method according to claim 7, characterized in that the at least one parameter includes a transformPrecoder parameter. [Claim 9] The method according to claim 5, characterized in that, based on the CRC being scrambled by the C-RNTI or the MCS-C-RNTI, the transform precoding for the PUSCH is enabled or disabled based on the transform precoder indicator field. [Claim 10] The method according to claim 5, characterized in that, for the same serving cell, the bit width of the first field in the DCI format 0_1 ​​or DCI format 0_2 based on the CS-RNTI is the same as the bit width of the same field in the DCI format 0_1 ​​or DCI format 0_2 based on the C-RNTI. [Claim 11] The method according to claim 10, characterized in that the first field is the conversion precoder indicator field. [Claim 12] The method according to claim 2, characterized in that, based on the fact that the payload size of the DCI format associated with the DCI is smaller than a defined value, zeros are appended to the DCI format until the payload size becomes equal to the defined value. [Claim 13] The method according to claim 1, characterized in that i) the CRC is scrambled by the CS-RNTI, and ii) validation of the DCI is performed for scheduling activation based on a configured grant, based on the value of the NDI field being "0". [Claim 14] The method according to claim 13, characterized in that the validation of the DCI is achieved based on the fields within the DCI. [Claim 15] It is a terminal (user equipment: UE), One or more transceivers and One or more processors, The system comprises one or more memories connected to one or more processors for storing instructions, A terminal characterized in that, based on the fact that the instructions are performed by the one or more processors, the one or more processors are configured to perform all the steps of the method according to any one of claims 1 to 14. [Claim 16] A device comprising one or more memory and one or more processors functionally connected to the one or more memory, The apparatus is characterized in that the one or more memory stores instructions that, based on being executed by the one or more processors, cause the one or more processors to perform all steps of the method according to any one of claims 1 to 14. [Claim 17] One or more non-transitory computer-readable media for storing instructions, One or more non-transitory computer-readable media, characterized in that the instructions, which can be executed by one or more processors, are configured to enable the one or more processors to perform all steps of the method according to any one of claims 1 to 14. [Claim 18] A method performed by a base station, Steps include transmitting configuration information related to the Physical Uplink Shared Channel (PUSCH), A step of transmitting Downlink Control Information (DCI) including an NDI (New Data Indicator) field, The process includes the step of receiving the PUSCH based on the DCI, Based on the aforementioned configuration information, and based on the fact that the parameters related to the presence of the DCI internal transform precoder indicator field have been set, the transform precoder indicator field is based on 1 bit. The aforementioned 1-bit value indicates whether the transform precoder is enabled or disabled. i) The CRC (Cyclic Redundancy Check) related to the DCI is scrambled by CS (Configured Scheduling)-RNTI (Radio Network Temporary Indenter), ii) A method characterized in that the 1 bit is reserved based on the value of the NDI field being "0". [Claim 19] It is a base station, One or more transceivers, One or more processors, The system comprises one or more memories connected to one or more processors for storing instructions, A base station characterized in that, based on the fact that the instructions are performed by the one or more processors, the one or more processors are configured to perform all the steps of the method according to claim 18.

Claims

1. A method performed by a terminal (user equipment: UE), The steps include receiving configuration information related to the Physical Uplink Shared Channel (PUSCH), The steps include receiving Downlink Control Information (DCI) including the NDI (New Data Indicator) field, The process includes the step of transmitting the PUSCH based on the DCI, Based on the aforementioned configuration information, and based on the fact that the parameters related to the presence of the DCI internal transform precoder indicator field have been set, the transform precoder indicator field is based on 1 bit. The value of the aforementioned 1 bit indicates that the transform precoder has been enabled or disabled. i) The CRC (Cyclic Redundancy Check) related to the DCI is scrambled by the CS (Configured Scheduling)-RNTI (Radio Network Temporary Indentifier), ii) A method characterized in that the 1 bit is reserved based on the value of the NDI field being "0".

2. The method according to claim 1, characterized in that the conversion precoder indicator field is 0 bits based on the fact that the parameter is not set.

3. The method according to claim 1, characterized in that the grant associated with the PUSCH is a dynamic grant or a configured grant.

4. The method according to claim 1, characterized in that the DCI format associated with the DCI is DCI format0_1 or DCI format0_2.

5. The method according to claim 4, characterized in that the CRC is scrambled by CS-RNTI, C(Cell)-RNTI, SP(Semi-Persistent)-CSI(Channel State Information)-RNTI, or MCS(Modulation Coding Scheme)-C-RNTI.

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

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

8. At least one parameter is excluded from the parameters in the configuration information that are applied to the PUSCH retransmission. The method according to claim 7, characterized in that the at least one parameter includes a transformPrecoder parameter.

9. The method according to claim 5, characterized in that, based on the CRC being scrambled by the C-RNTI or the MCS-C-RNTI, transform precoding for the PUSCH is enabled or disabled based on the transform precoder indicator field.

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

11. The method according to claim 10, characterized in that the first field is the conversion precoder indicator field.

12. The method according to claim 2, characterized in that, based on the fact that the payload size of the DCI format associated with the DCI is smaller than a defined value, zeros are added to the DCI format until the payload size becomes equal to the defined value.

13. The method according to claim 1, characterized in that i) the CRC is scrambled by the CS-RNTI, and ii) the DCI is validated for scheduling activation based on a configured grant, based on the value of the NDI field being "0".

14. The method according to claim 13, characterized in that the validation of the DCI is achieved based on the fields within the DCI.

15. A terminal (user equipment: UE), One or more transceivers and One or more processors, The system comprises one or more memories connected to one or more processors for storing instructions, A terminal characterized in that, based on the fact that the instructions are executed by one or more processors, one or more processors are configured to perform all steps of the method according to any one of claims 1 to 14.

16. A device comprising one or more memory and one or more processors functionally connected to the one or more memory, The apparatus is characterized in that the one or more memory stores instructions that, on the basis that they are to be executed by the one or more processors, cause the one or more processors to perform all steps of the method according to any one of claims 1 to 14.

17. One or more non-transitory computer-readable media for storing instructions, One or more non-transitory computer-readable media, characterized in that the instructions, which can be executed by one or more processors, are configured to cause the one or more processors to perform all steps of the method according to any one of claims 1 to 14.

18. A method performed by a base station, Steps include transmitting configuration information related to the Physical Uplink Shared Channel (PUSCH), The steps include transmitting Downlink Control Information (DCI) including an NDI (New Data Indicator) field, The process includes the step of receiving the PUSCH based on the DCI, Based on the aforementioned configuration information, and based on the fact that the parameters related to the presence of the DCI internal transform precoder indicator field have been set, the transform precoder indicator field is based on 1 bit. The value of the aforementioned 1 bit indicates that the transform precoder has been enabled or disabled. i) The CRC (Cyclic Redundancy Check) related to the DCI is scrambled by the CS (Configured Scheduling)-RNTI (Radio Network Temporary Indentifier), ii) A method characterized in that the 1 bit is reserved based on the value of the NDI field being "0".

19. It is a base station, One or more transceivers, One or more processors, The system comprises one or more memories connected to one or more processors for storing instructions, A base station characterized in that, based on the fact that the instructions are executed by the one or more processors, the one or more processors are configured to perform all the steps of the method according to claim 18.

Images