Method and apparatus for transmitting and receiving uplink shared channel

Abstract

A method according to an embodiment of the present specification comprises the steps of: receiving a PDSCH; receiving DCI for scheduling a PUSCH; and transmitting the PUSCH. The PDSCH includes a contention resolution identity. The DCI is based on DCI format 0_0 having a cyclic redundancy check (CRC) scrambled by a cell (C)-radio network temporary indentifier (RNTI). Whether to enable repetition related to the PUSCH is determined on the basis of higher layer parameters.

Description

Method and device for transmitting and receiving on an uplink shared channel

[0001] The present specification relates to a method and device for transmitting and receiving an uplink shared channel.

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, they have expanded beyond voice to include data services. Currently, explosive growth in traffic is leading to resource shortages and users are demanding faster services, necessitating a more advanced mobile communication system.

[0003] Next-generation mobile communication systems must support explosive data traffic growth, dramatically increasing data rates per user, a vastly increased number of connected devices, ultra-low end-to-end latency, and high energy efficiency. To achieve these goals, various technologies are being studied, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.

[0004] Meanwhile, MSG5 PUSCH refers to the PUSCH transmitted by the terminal that received MSG4 (contention resolution) in the RACH procedure to convey the RRC connection setup complete message. In other words, MSG5 PUSCH may refer to the PUSCH transmitted before establishing a dedicated PUSCH. The PUSCH may be scheduled based on DCI format 0_0 with a CRC scrambled with C-RNTI.

[0005] Repetition is supported for MSG1 (PRACH) and MSG3 (PUSCH) in Rel-18. Furthermore, repetition is also supported for PUCCH for HARQ-ACK transmission for MSG4. Therefore, repetition support for MSG5 PUSCH is also needed to enhance coverage.

[0006] The purpose of this specification is to propose a method for supporting repetition for MSG5 PUSCH. More specifically, the purpose of this specification is to propose a method for supporting repetition for PUSCH scheduled by DCI format 0_0 with a Cyclic Redundancy Check (CRC) scrambled with a C-RNTI.

[0007] The technical problems to be achieved in this specification are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0008] A method performed by a terminal according to one embodiment of the present disclosure includes the steps of receiving a physical downlink shared channel (PDSCH), receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), and transmitting the PUSCH. The PDSCH includes a contention resolution identity.

[0009] The above DCI is based on DCI format 0_0 with a CRC (Cyclic Redundancy Check) scrambled by a C(Cell)-RNTI (Radio Network Temporary Identifier).

[0010] It is characterized in that whether repetition related to the PUSCH is enabled is determined based on a higher layer parameter.

[0011] The above upper layer parameter can indicate enabling or disabling of the above repetition.

[0012] The above upper layer parameter can indicate the number of repetitions.

[0013] The method may further include a step of receiving a System Information Block (SIB) including the upper layer parameters.

[0014] Based on the above repetition being enabled, the PUSCH can be transmitted based on time domain resources associated with the number of repetitions.

[0015] Based on the above upper layer parameters not being set, the PUSCH can be transmitted once.

[0016] The method may further include a step of transmitting capability information. The capability information may include first information indicating whether the repetition is supported by the terminal.

[0017] Based on the inclusion of the first information in the performance information, the performance information may further include second information. The second information may indicate whether repetition of a PUSCH scheduled by a Random Access Response (RAR, UL grant) is supported.

[0018] The method may further comprise the step of transmitting information including a request for said repetition.

[0019] The information including the request may be transmitted based on i) whether the repetition is supported by the terminal and / or ii) a condition related to the repetition.

[0020] The above condition may be satisfied based on the RSRP (Reference Signal Received Power) being less than the RSRP threshold.

[0021] i) based on the repetition being supported by the terminal and ii) the condition being met: the information including the request may be transmitted.

[0022] A terminal according to another embodiment of the present disclosure includes one or more transceivers, one or more processors, and one or more memories connected to the one or more processors and storing instructions.

[0023] The instructions are characterized in that, based on being executed by the one or more processors, the one or more processors are set to perform all steps of any one of the methods.

[0024] A device according to another embodiment of the present disclosure comprises one or more memories and one or more processors functionally connected to the one or more memories.

[0025] Said one or more memories are characterized in that they store instructions that cause said one or more processors to perform all steps of any one of said methods based on what is executed by said one or more processors.

[0026] In another embodiment of the present disclosure, one or more non-transitory computer-readable media store instructions.

[0027] The instructions executable by one or more processors are characterized by configuring the one or more processors to perform all steps of any one of the methods.

[0028] A method performed by a base station according to another embodiment of the present disclosure includes the steps of transmitting a physical downlink shared channel (PDSCH), transmitting downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH), and receiving the PUSCH. The PDSCH includes a contention resolution identity.

[0029] The above DCI is based on DCI format 0_0 with a CRC (Cyclic Redundancy Check) scrambled by a C(Cell)-RNTI (Radio Network Temporary Identifier).

[0030] It is characterized in that whether repetition related to the PUSCH is enabled is determined based on a higher layer parameter.

[0031] According to another embodiment of the present disclosure, a base station includes one or more transceivers, one or more processors, and one or more memories coupled to the one or more processors and storing instructions.

[0032] The instructions are characterized in that they are executed by the one or more processors, and the one or more processors are set to perform all steps of the method.

[0033] According to the embodiment of the present specification, repetition of PUSCH for MSG5 is supported, so that the RACH procedure can be successfully completed even in poor channel conditions (e.g., when MSG1 and MSG3 are repeatedly transmitted).

[0034] Additionally, the delay until terminal-specific RRC settings for UL / DL are made after the RACH procedure can be minimized.

[0035] In addition, since whether repetition of PUSCH for MSG5 is enabled is indicated by a higher layer parameter, ambiguity in terminal operation related to the RACH procedure can be resolved.

[0036] The effects that can be obtained from this specification are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the technical field to which this specification belongs from the description below.

[0037] Figure 1 illustrates physical channels and typical signal transmission used in a 3GPP system.

[0038] Figure 2 illustrates the process of acquiring system information (SI).

[0039] Figure 3 illustrates a random access procedure.

[0040] Figure 4 is a diagram showing an example of an uplink transmission and reception operation.

[0041] FIG. 5 is a flowchart illustrating a method performed by a terminal according to one embodiment of the present specification.

[0042] FIG. 6 is a flowchart illustrating a method performed by a base station according to another embodiment of the present specification.

[0043] FIG. 7 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

[0044] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to illustrate exemplary embodiments of the present invention and is not intended to represent the only embodiments in which the present invention may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present invention. However, one of ordinary skill in the art will appreciate that the present invention may be practiced without these specific details.

[0045] In some cases, to avoid obscuring the concept of the present invention, well-known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.

[0046] Hereinafter, 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, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal, and a receiver may be part of a base station. A base station may be expressed as a first communication device, and a terminal may be expressed as a second communication device. A base station (BS) may be replaced by terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP: Access Point), network (5G network), AI system, RSU (road side unit), vehicle, robot, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, the terminal may be fixed or mobile, and may 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) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, robot, AI module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0047] Physical channels and general signal transmission

[0048] Figure 1 illustrates the physical channels and typical signal transmission used in the 3GPP system. In a wireless communication system, a terminal receives information from a base station via the downlink (DL), and the terminal transmits information to the base station via the uplink (UL). The information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information they transmit and receive.

[0049] When a terminal is powered on or enters a new cell, it performs an initial cell search operation, such as synchronizing with the base station (S101). To this end, the terminal receives a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell ID. Afterwards, the terminal can receive a Physical Broadcast Channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, the terminal can receive a Downlink Reference Signal (DL RS) during the initial cell search phase to check the downlink channel status.

[0050] A terminal that has completed initial cell search can obtain more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S102).

[0051] Meanwhile, when accessing a base station for the first time or when there are no radio resources for signal transmission, the terminal may perform a random access procedure (RACH) for the base station (S103 to S106). To this end, the terminal may transmit a specific sequence as a preamble via a physical random access channel (PRACH) (S103 and S105) and receive a response message (RAR (Random Access Response) message) to the preamble via a PDCCH and a corresponding PDSCH. In the case of a contention-based RACH, a contention resolution procedure may additionally be performed (S106).

[0052] The terminal that has performed the procedure described above can then perform PDCCH / PDSCH reception (S107) and physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission (S108) as general uplink / downlink signal transmission procedures. In particular, the terminal can receive downlink control information (DCI) through the PDCCH. Here, the DCI includes control information such as resource allocation information for the terminal, and different formats can be applied depending on the purpose of use.

[0053] Meanwhile, the control information that the terminal transmits to the base station via the uplink or that the terminal receives from the base station may include downlink / uplink ACK / NACK signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Index), RI (Rank Indicator), etc. The terminal may transmit the above-described control information such as CQI / PMI / RI via PUSCH and / or PUCCH.

[0054] Figure 2 illustrates the process of acquiring system information (SI).

[0055] A terminal can acquire AS / NAS information through the SI acquisition process. The SI acquisition process can be applied to terminals in the RRC_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state.

[0056] SI is divided into a Master Information Block (MIB) and multiple System Information Blocks (SIBs). SI outside of the MIB can be referred to as Remaining Minimum System Information (RMSI). For more details, see the following:

[0057] - MIB contains information / parameters related to reception of SIB1 (System Information Block 1) and is transmitted via PBCH of SSB. During initial cell selection, the UE assumes that half-frames with SSB are repeated at a cycle of 20 ms. The UE can check whether a CORESET (Control Resource Set) for a Type0-PDCCH common search space exists based on the MIB. The Type0-PDCCH common search space is a type of PDCCH search space and is used to transmit a PDCCH that schedules an SI message. If the Type0-PDCCH common search space exists, the UE can determine (i) multiple consecutive RBs and one or more consecutive symbols that constitute a CORESET and (ii) a PDCCH opportunity (i.e., a time domain location for PDCCH reception) based on the information in the MIB (e.g., pdcch-ConfigSIB1). If Type0-PDCCH common search space does not exist, pdcch-ConfigSIB1 provides information about the frequency location where SSB / SIB1 exists and the frequency range where SSB / SIB1 does not exist.

[0058] - SIB1 includes information related to the availability and scheduling (e.g., transmission period, SI window size) of the remaining SIBs (hereinafter, SIBx, where x is an integer greater than or equal to 2). For example, SIB1 may indicate whether SIBx is broadcast periodically or provided on-demand upon request of a terminal. If SIBx is provided on-demand, SIB1 may include information necessary for a terminal to perform an SI request. SIB1 is transmitted through a PDSCH, a PDCCH that schedules SIB1 is transmitted through a Type0-PDCCH common search space, and SIB1 is transmitted through a PDSCH indicated by the PDCCH.

[0059] - SIBx is included in SI messages and transmitted over the PDSCH. Each SI message is transmitted within a periodically occurring time window (i.e., SI-window).

[0060] Figure 3 illustrates a random access procedure.

[0061] Figure 3 (a) shows a contention-based RACH procedure, and Figure 3 (b) shows a contention-free RACH procedure.

[0062] Below, we will look at MSG1 transmission.

[0063] Subcarrier spacing for MSG1 is set in the RACH configuration and provided in the handover command for contention-free RA procedures for handover.

[0064] Preamble indices for contention based random access (CBRA) and contention free random access (CFRA) are mapped consecutively to one SSB in one RACH transmission occasion.

[0065] CBRA: The association between a SS block (SSB) and a subset of RACH resources and / or preamble indices within an SS burst set is established by a parameter set in the RMSI.

[0066] CFRA: The UE may be configured to transmit multiple MSG1s via dedicated multi-RACH transmission opportunities in the time domain before the end of the monitored RAR window.

[0067] And, the association between CFRA preamble and SSB is reestablished via UE-specific RRC.

[0068] The random access procedure can be a Type-1 random access procedure (4-step RA) or a Type-2 random access procedure (2-step RA).

[0069] The above Type-1 random access procedure may include transmitting a random access preamble (Msg1) on a physical random access channel (PRACH), receiving a random access response (RAR) (Msg2), transmitting a PUSCH scheduled by an UL grant of the RAR (Msg3), and transmitting a PDSCH for contention resolution (Msg4). If the random access procedure is contention-free random access (CFRA), the Msg3 transmission and Msg4 reception operations are omitted.

[0070] The above Type-2 random access procedure may include transmission of a random access preamble and PUSCH (MsgA) and reception of a RAR (MsgB).

[0071] Figure 4 is a diagram showing an example of an uplink transmission and reception operation.

[0072] Referring to FIG. 4, the base station schedules uplink transmissions, such as frequency / time resources, transmission layers, uplink precoder, and MCS (S410). In particular, the base station can determine a beam for PUSCH transmission by the terminal through beam management operations. Then, the terminal receives DCI for uplink scheduling (i.e., including PUSCH scheduling information) from the base station on the PDCCH (S420). DCI format 0_0 or 0_1 can be used for uplink scheduling, and in particular, DCI format 0_1 ​​includes the following information: DCI format identifier, UL / SUL (Supplementary uplink) indicator, UL / SUL 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, DMRS sequence initialization, UL-SCH (Uplink Shared Channel) indicator.

[0073] In particular, SRS resources set within the SRS resource set associated with the upper layer parameter 'usage' can be indicated by the SRS resource indicator field. In addition, 'spatialRelationInfo' can be set for each SRS resource, and its value can be one of {CRI, SSB, SRI}.

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

[0075] For codebook-based transmission, when the upper layer parameter 'txConfig' is set to 'codebook', the terminal is configured for codebook-based transmission. On the other hand, 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. For 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 UE determines a 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 field and the Precoding information and number of layers field. The TPMI is used to indicate a precoder to be applied across antenna ports, and corresponds to the SRS resource selected by the SRI when multiple SRS resources are configured. Alternatively, when a single SRS resource is configured, the TPMI is used to indicate a precoder to be applied across antenna ports, and corresponds to the single SRS resource. The transmission precoder is selected from an uplink codebook having the same number of antenna ports as the upper layer parameter 'nrofSRS-Ports'. When the upper layer in which the UE is set to 'codebook' is configured with the parameter 'txConfig', the UE is configured with at least one SRS resource.The SRI indicated in slot n is associated with the most recent transmission of the SRS resource identified by the SRI, where the SRS resource precedes the PDCCH carrying the SRI (i.e., slot n).

[0076] For non-codebook based transmission, PUSCH can be scheduled in 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, which is given by the SRS resource indicator in the DCI or the higher layer parameter 'srs-ResourceIndicator'. The UE uses one or multiple SRS resources for SRS transmission, and the number of SRS resources can be configured for simultaneous transmission within the same RB based on the UE capability. 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, where the SRS transmission precedes the PDCCH carrying the SRI (i.e., slot n).

[0077] Below, we will look at PUSCH Repetition in detail.

[0078] The pusch-TimeDomainAllocationList is configured based on the upper layer parameter PUSCH-config. The parameters in the pusch-TimeDomainAllocationList are as follows.

[0079]

[0080] Referring to Table 1, the numberOfRepetitions and numberOfRepetitionsExt parameters in pusch-TimeDomainAllocationList are related to dynamic indication.

[0081] A semi-static indication related to PUSCH repetition may be performed. Specifically, referring to Table 2 below, the pusch-AggregationFactor parameter may be set based on the upper layer parameter PUSCH-config.

[0082]

[0083] Based on the settings / instructions according to Table 1 and Table 2 described above, the number of PUSCH repetitions can be determined according to Table 3 below.

[0084]

[0085] The contents discussed above can be applied in combination with the methods proposed in this specification, which will be described later, or can be supplemented to clarify the technical features of the methods proposed in this specification.

[0086] In addition, the methods related to PUSCH transmission described below are related to uplink transmission and can be equally applied to the uplink signal transmission method in the NR system (licensed band) or U-Band system (unlicensed band) described above, and of course, the technical idea proposed in this specification can be modified or replaced to fit the terms, expressions, structures, etc. defined in each system so that it can be implemented in the relevant system as well.

[0087] For example, uplink transmission through methods related to PUSCH transmission, which will be described later, can be performed in an L-cell (a cell operating in a licensed band (L-band)) and / or a U-cell (a cell operating in an unlicensed band (U-band)) defined in an NR system or a U-Band system. In addition, uplink transmission through methods related to PUSCH transmission, which will be described later, can be performed in a TN (Terrestrial Networks) system, and additionally, can be performed in an NTN (Non-Terrestrial Networks) system.

[0088] NR supports multiple numerologies (or subcarrier spacings (SCS)) to support various 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0089] The NR frequency band is defined by two types of frequency ranges (FR1 and FR2). FR1 and FR2 can be configured as shown in Table 4 below. FR2 can also mean millimeter wave (mmW).

[0090]

[0091] Meanwhile, UL signals / channels related to the RACH procedure may include Msg1 PRACH, Msg3 PUSCH, Msg4 HARQ-ACK PUCCH, Msg5 PUSCH, etc. Repeated transmissions for Msg1 PRACH, Msg3 PUSCH, Msg4 HARQ-ACK PUCCH, etc. have been introduced or will be introduced through Rel-17 coverage enhancement and / or Rel-18 coverage enhancement.

[0092] Additionally, a terminal that has entered the RRC connected state receives a PUSCH-config from a base station via dedicated RRC signaling. The base station can configure the terminal that has received the PUSCH-config to perform repeated transmissions on the PUSCH that can be transmitted using a semi-static method and / or a dynamic method.

[0093] On the other hand, since Msg5 PUSCH is transmitted before the UE receives PUSCH-config, repeated transmissions for Msg5 PUSCH are not currently supported. Repeated transmissions for Msg5 PUSCH may be considered in Rel-19 or later releases.

[0094] Below, we examine the terminal / base station operations for supporting repeated transmissions on the Msg5 PUSCH. Specifically, we describe 1) how to enable / disable repeated transmissions on the Msg5 PUSCH and 2) how to set the RSRP threshold for repeated transmissions on the Msg5 PUSCH.

[0095] The Msg5 PUSCH mentioned in this specification can be defined as follows.

[0096] After the terminal receives the Msg4 PDSCH and completes the HARQ-ACK PUCCH transmission for the Msg4 PDSCH, the terminal may transmit the Msg5 PUSCH. Specifically, the Msg5 PUSCH may refer to a PUSCH that is dynamically configured / indicated / scheduled based on the DCI format 0_0 scrambled with C-RNTI, etc., before the terminal receives the dedicated RRC signaling including the PUSCH-config.

[0097] Enable / disable methods for Msg5 PUSCH repeated transmission

[0098] [Method 1]

[0099] A method utilizing explicit indication based on upper layer parameters may be considered.

[0100] Specifically, it may be considered to transmit to the terminal an explicit parameter indicating whether to enable / disable Msg5 PUSCH repeated transmission based on higher layer signaling (e.g., SIB, etc.).

[0101] More specifically, a new parameter may be introduced in higher layer signaling (e.g., SIB, etc.) to indicate whether to perform repeated Msg5 PUSCH transmissions. Depending on the value indicated by the parameter, whether to enable / disable repeated Msg5 PUSCH transmissions performed by the UE may be determined.

[0102] If the above parameter is indicated as enable, the terminal may be configured to repeatedly transmit the configured / indicated Msg5 PUSCH. If the above parameter is indicated as disable, the terminal may be configured to transmit the configured / indicated Msg5 PUSCH only once in the conventional manner.

[0103] For example, the following default operation can be defined / configured for cases where the above parameter is not provided / configured. If the parameter is not provided based on the higher layer signaling (e.g., SIB, etc.), the terminal and / or the base station can assume that the Msg5 PUSCH transmission is always performed as a single transmission and operate based on this. That is, when the above method is applied, the parameter can be set as follows. Only when the base station determines that repeated transmission for the Msg5 PUSCH is necessary, the base station can set the parameter to enable and instruct the terminal. In this case, the parameter can also be set without including any value.

[0104] For example, if the parameter is not provided / configured, the terminal and / or the base station may assume that the Msg5 PUSCH transmission is always performed as a repetitive transmission and operate based on this. That is, if the above method is applied, the parameter may be configured as follows. Only when the base station determines that repetitive transmission for the Msg5 PUSCH is not necessary, the base station may instruct the terminal to set the parameter to disable. In this case, the parameter may be configured without including any value.

[0105] For example, the parameter indicating whether to enable / disable the above-described Msg5 PUSCH repeated transmission can be set / indicated cell-specifically. That is, the parameter can be set for each cell.

[0106] For example, a parameter indicating whether to enable / disable Msg5 PUSCH repeated transmission can be set / indicated in a BWP-specific manner. In other words, the parameter can be set for each BWP.

[0107] In the examples described above, it is assumed that parameters are set / indicated based on higher layer signaling (SIB). These parameters may also be set based on messages related to the RACH procedure.

[0108] For example, an additional parameter may be introduced to an RRC connection resolution message transmitted based on Msg4 PDSCH. Whether to enable / disable Msg5 PUSCH repetitive transmission may be indicated based on the additionally introduced parameter as described above. For example, whether to enable / disable Msg5 PUSCH repetitive transmission may be indicated together with the RRC connection resolution message transmitted on Msg4 PDSCH. In other words, whether to enable / disable Msg5 PUSCH repetitive transmission may be indicated based on information other than the parameters in the RRC connection resolution message.

[0109] If the terminal successfully receives the Msg4 PDSCH, the terminal can determine / determine whether repeated transmissions for the Msg5 PUSCH are permitted. Based on this, the terminal can perform repeated transmissions for the Msg5 PUSCH. At this time, the default operation described above can also be applied to the present method. Specifically, if the parameter indicating whether to enable / disable the above is not provided or if enable / disable information is not provided, the default operation described above can be configured / defined to be applied.

[0110] [Method 2]

[0111] A method utilizing implicit determination based on repetition of other uplink channels may be considered.

[0112] Specifically, whether to enable / disable repeated transmission for Msg 5 PUSCH can be determined based on the following 1) and 2).

[0113] 1) When the base station provides parameters related to Msg5 PUSCH repeated transmission to the terminal through higher layer signaling (e.g., SIB, etc.), and;

[0114] 2) When the terminal requests repeated transmission of Msg3 PUSCH (and / or Msg1 PRACH preamble and / or Msg4 HARQ-ACK PUCCH), or when a specific condition is satisfied and the terminal determines that repeated transmission for the above signals / channels is required (e.g., when the RSRP value acquired by the terminal is lower than the RSRP Threshold indicated by the base station, the terminal determines that repeated transmission is required).

[0115] The terminal can implicitly determine / determine that repeated transmission of Msg5 PUSCH is also necessary. Based on this, the terminal can perform repeated transmission of Msg5 PUSCH.

[0116] To apply the above method, the UE capability for Msg5 PUSCH repeated transmission can be defined to be set in association with the UE capability for other UL channel repeated transmission.

[0117] Specifically, it can be assumed that Msg5 PUSCH repetitive transmission is defined in association with Msg3 PUSCH repetitive transmission. If whether Msg5 PUSCH repetitive transmission is enabled / disabled is determined based on whether Msg3 PUSCH repetitive transmission is enabled / disabled, the UE capability can be defined / configured as follows.

[0118] A UE that supports Msg5 PUSCH repetition transmission must always support Msg3 PUSCH repetition transmission. That is, when a UE reports the Msg5 PUSCH repetition transmission capability, the UE can be configured / defined to also report the Msg3 PUSCH repetition transmission capability.

[0119] For example, a terminal supporting Msg5 PUSCH repeated transmission may be configured / defined to include information indicating that Msg3 PUSCH repeated transmission is supported in addition to information indicating that Msg5 PUSCH repeated transmission is supported in its capability information. For example, based on the fact that the capability information includes information indicating that Msg5 PUSCH repeated transmission is supported, the capability information may also include information indicating that Msg3 PUSCH repeated transmission is supported.

[0120] For example, the UE capability for repeated Msg5 PUSCH transmission may include the UE capability for repeated Msg3 PUSCH transmission. When the base station receives the UE capability for repeated Msg5 PUSCH transmission from the terminal, the base station may configure the terminal to understand that the terminal is capable of repeated transmission of not only Msg5 PUSCH but also Msg3 PUSCH.

[0121] The UL signal / channel that can be associated with the repeated transmission of Msg5 PUSCH is not limited to the Msg3 PUSCH described above. For example, instead of Msg3 PUSCH, Msg1 PRACH preamble and / or Msg4 HARQ-ACK PUCCH can be associated with the repeated transmission of Msg5 PUSCH. That is, in the example described above, 'Msg3 PUSCH' can be interpreted / replaced with 'Msg1 PRACH preamble' and / or 'Msg4 HARQ-ACK PUCCH'.

[0122] [Method 3]

[0123] A method utilizing implicit decisions based on repetition factor signaling via higher layer signaling may be considered.

[0124] Specifically, the base station can set / instruct the terminal to set one or more repetition factors for Msg5 PUSCH repetitive transmission through higher layer signaling (e.g., SIB, etc.).

[0125] Based on the repetition factor parameter being set / indicated, the terminal may be configured to operate by considering that Msg5 PUSCH repeated transmission is enabled from the base station.

[0126] For example, when the above repetition factor is indicated, one of the positive integer values ​​(excluding 1) (e.g., exponentiation of 2, i.e., 2, 4, 8, etc.) may be indicated.

[0127] For example, when the above multiple repetition factors are indicated, two or more repetition factors may be combined and set / indicated among positive integers including 1. For a specific example, it may be assumed that the repetition factors to be indicated by the base station are 1, 2, 4, and 8. At this time, combinations that may be composed of two or more repetition factors may include {1, 2}, {1, 4}, {1, 8}, {2, 4}, {2, 8}, {4, 8}, {1, 2, 4}, {1, 2, 8}, {1, 4, 8}, {2, 4, 8}, {1, 2, 4, 8}, and the like.

[0128] Consequently, if the repetition factor parameter for Msg5 PUSCH repetitive transmission is indicated by the base station, the terminal can consider that Msg5 PUSCH is enabled in the cell. If the terminal has Msg5 PUSCH repetitive transmission capability and / or satisfies specific conditions that require Msg5 PUSCH repetitive transmission to be requested, the terminal can be configured to report the capability to the base station or request repetitive transmission. Depending on the capability or request content reported by the terminal, the base station can schedule the Msg5 PUSCH as a single transmission or repetitive transmission. Specifically, the base station can determine whether to allocate the Msg5 PUSCH as a single transmission or as multiple transmissions, and the base station can be configured to schedule the Msg5 PUSCH based on the determination. The terminal can perform Msg5 PUSCH transmission as a single transmission or repetitive transmission through the scheduling information.

[0129] RSRP Threshold for Msg5 PUSCH repeated transmission

[0130] The base station can set / indicate an RSRP Threshold so that the terminal can determine (by itself) whether to repeat the Msg5 PUSCH transmission. In this case, one of the following options can be defined for use.

[0131] Option 1)

[0132] The RSRP Threshold, which was previously provided for determining other signal / channel repeat transmissions, can be reused for determining Msg5 PUSCH repeat transmissions.

[0133] For example, the RSRP Threshold value provided / set for determining Msg1 PRACH preamble repetition transmission can be defined to be reused for determining Msg5 PUSCH repetition transmission.

[0134] For example, the RSRP Threshold value provided / set for determining Msg3 PUSCH repeated transmission may be defined to be reused for determining Msg5 PUSCH repeated transmission.

[0135] For example, the RSRP Threshold value provided / set for determining Msg4 HARQ-ACK PUCCH repeated transmission can be defined to be reused for determining Msg5 PUSCH repeated transmission.

[0136] This embodiment achieves the following benefits: Reusing the existing RSRP Threshold value eliminates the need to introduce, configure, or provide additional parameters for Msg5 PUSCH. This minimizes the implementation complexity and signaling overhead required to support the determination of whether Msg5 PUSCH should be repeated.

[0137] Option 2)

[0138] The base station can set / provide a new RSRP Threshold to the terminal for determining Msg5 PUSCH repeated transmission, separate from the previously used RSRP Threshold value.

[0139] According to this embodiment, the base station can manage whether to repeat Msg5 PUSCH transmission for terminals capable of repeat Msg5 PUSCH transmission within the cell independently from whether to repeat other signals / channels. Therefore, there is an advantage of increased freedom in network operation.

[0140] After the RSRP Threshold value for determining Msg5 PUSCH repeated transmission is defined / indicated, the following actions can be performed.

[0141] For example, if the currently measured RSRP value by the terminal (using a specific reference signal) is lower than the RSRP Threshold value provided (or instructed to be reused) by the base station, the terminal may determine that repeated transmission of the Msg5 PUSCH is required. The terminal may be configured to notify the base station that repeated transmission of the Msg5 PUSCH is required.

[0142] For example, if the RSRP value currently measured by the terminal is higher than the RSRP Threshold value provided (or instructed to be reused) by the base station, the terminal may determine that repeated transmission of the Msg5 PUSCH is not necessary. The terminal may be configured to inform the base station that only a single transmission is required for the Msg5 PUSCH.

[0143] In addition, the proposed method can be set / applied to other UL signals / channels such as PUSCH / PUCCH / PRACH. In addition, it is clear that examples of the proposed method described above can also be included as one of the implementation methods of the present specification, and thus can be considered as a type of proposed method. In addition, the proposed methods described above can be implemented independently, but can also be implemented in the form of a combination (or merge) of some of the proposed methods. Information on whether the methods are applied (or information on the rules of the methods) can be defined as a rule so that the base station notifies the terminal of the application of the methods through a predefined signal (e.g., a physical layer signal or a higher layer signal). The higher layer can include one or more of functional layers such as MAC, RLC, PDCP, RRC, and SDAP, for example.

[0144] The methods, embodiments or descriptions for implementing the method proposed in this specification may be applied separately, or one or more methods (or embodiments or descriptions) may be applied in combination.

[0145] In terms of implementation, the operations of the base station / terminal according to the embodiments described above (e.g., operations related to PUSCH repeated transmission based on at least one of Methods 1 to 3, Option 1 and / or Option 2) can be processed by the device of FIG. 7 described below (e.g., processor (110, 210) of FIG. 7).

[0146] In addition, the operations of the base station / terminal according to the above-described embodiment (e.g., operations related to PUSCH repeated transmission based on at least one of Method 1 to Method 3, Option 1 and / or Option 2) may be stored in a memory (e.g., 140, 240 of FIG. 7) in the form of a command / program (e.g., instruction, executable code) for driving at least one processor (e.g., 110, 210 of FIG. 7).

[0147] The embodiments described below are specifically described with reference to FIGS. 5 and 6 in terms of the operation of the terminal and base station. The methods described below are distinguished for convenience of explanation, and it is understood that some components of one method may be substituted for or combined with some components of another method.

[0148] FIG. 5 is a flowchart illustrating a method performed by a terminal according to one embodiment of the present specification.

[0149] Referring to FIG. 5, a method performed by a terminal according to one embodiment of the present specification includes a PDSCH reception step (S510), a DCI reception step (S520), and a PUSCH transmission step (S530).

[0150] In step S510, the terminal receives a Physical Downlink Shared Channel (PDSCH) from the base station. The PDSCH may include a contention resolution identity. For example, the PDSCH may be associated with a message (Msg4) for contention resolution in a random access procedure.

[0151] In S520, the terminal receives downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) from the base station.

[0152] In S530, the terminal transmits the PUSCH to the base station.

[0153] For example, the DCI may be based on DCI format 0_0 having a CRC (Cyclic Redundancy Check) scrambled by a C(Cell)-RNTI (Radio Network Temporary Identifier). The PUSCH may refer to a PUSCH related to an RRC setup complete message (e.g., Msg5 PUSCH).

[0154] Whether repetition related to the PUSCH is enabled can be set / instructed / determined based on at least one of the above-described methods 1 to 3.

[0155] In one embodiment, whether repetition associated with the PUSCH is enabled may be determined based on a higher layer parameter.

[0156] For example, the upper layer parameter may indicate enabling or disabling the repetition. This embodiment may be based on Method 1.

[0157] For example, the upper layer parameter may indicate the number of repetitions. That is, based on the setting of the upper layer parameter, the repetition may be determined to be enabled. This embodiment may be based on Method 3.

[0158] For example, based on the repetition being enabled, the PUSCH may be transmitted based on time domain resources associated with the number of repetitions.

[0159] For example, based on the above-described upper layer parameter not being set, the PUSCH may be transmitted once. This embodiment may be based on the default operation described above.

[0160] In one embodiment, the method may further include a SIB receiving step. Specifically, the terminal may receive a System Information Block (SIB) including the upper layer parameters from the base station. This embodiment may be based on Method 1 and / or Method 3. The SIB receiving step may be performed before S510. For example, the SIB receiving step may be performed based on FIG. 2.

[0161] In one embodiment, the method may further include a capability information transmission step. Specifically, the terminal transmits capability information to the base station. This embodiment may be based on at least one of Methods 1 to 3. For example, the transmission of the capability information may mean reporting of capabilities by the terminal in Method 3. For example, the capability information transmission step may be performed before S510. For example, the capability information transmission step may be performed after the SIB reception step.

[0162] For example, the performance information may include first information indicating whether the repetition is supported by the terminal.

[0163] Embodiments of Proposals 1 to 3 may be combined and applied to terminal / base station operations, as long as they do not conflict with each other. For example, whether the repetition is enabled may be determined / indicated based on Method 1 or Method 3, and terminal capabilities (UE capabilities) related to the repetition may be defined / configured based on Method 2. As a specific example, based on the inclusion of the first information in the performance information, the performance information may further include second information. The second information may indicate whether repetition of a PUSCH (e.g., Msg3 PUSCH) scheduled by a Random Access Response (RAR, UL grant) is supported.

[0164] In one embodiment, the method may further include a request transmission step. Specifically, the terminal may transmit information including a request for the repetition to the base station. This embodiment may be based on Method 3. The request transmission step may be performed before S510 or S520. For example, the request transmission step may be performed after the SIB reception step.

[0165] For example, the information including the request may be transmitted based on i) whether the repetition is supported by the terminal and / or ii) a condition related to the repetition.

[0166] For example, the above condition may be satisfied based on the Reference Signal Received Power (RSRP) being less than an RSRP threshold. The RSRP threshold may be based on Option 1) or Option 2).

[0167] For example, based on i) the repetition being supported by the terminal and ii) the condition being met: the information including the request may be transmitted. In another embodiment, based on i) the repetition being supported by the terminal and ii) the condition being met: the performance information described above may be transmitted.

[0168] The operations based on the above-described S510 to S530, SIB reception step, performance information transmission step, and request transmission step can be implemented by the device of FIG. 7. For example, the terminal (200) can control one or more transceivers (230) and / or one or more memories (240) to perform operations based on S510 to S530, SIB reception step, performance information transmission step, and request transmission step.

[0169] The embodiments described below are specifically described in terms of base station operation.

[0170] The SIB transmission step, performance information reception step, and request reception step described below correspond to the SIB reception step, performance information transmission step, and request transmission step described in FIG. 5, S510 to S530. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the base station operation described below can be replaced with the description / example of FIG. 5 corresponding to the corresponding operation.

[0171] FIG. 6 is a flowchart illustrating a method performed by a base station according to another embodiment of the present specification.

[0172] Referring to FIG. 6, a method performed by a base station according to another embodiment of the present specification includes a PDSCH transmission step (S610), a DCI transmission step (S620), and a PUSCH reception step (S630).

[0173] At step S610, the base station transmits a Physical Downlink Shared Channel (PDSCH) to the terminal. The PDSCH may include a contention resolution identity. For example, the PDSCH may be associated with a message (Msg4) for contention resolution in a random access procedure.

[0174] In S620, the base station transmits downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH) to the terminal.

[0175] In S630, the base station receives the PUSCH from the terminal.

[0176] For example, the DCI may be based on DCI format 0_0 having a CRC (Cyclic Redundancy Check) scrambled by a C(Cell)-RNTI (Radio Network Temporary Identifier). The PUSCH may refer to a PUSCH related to an RRC setup complete message (e.g., Msg5 PUSCH).

[0177] Whether repetition related to the PUSCH is enabled can be set / instructed / determined based on at least one of the above-described methods 1 to 3.

[0178] In one embodiment, whether repetition associated with the PUSCH is enabled may be determined based on a higher layer parameter.

[0179] In one embodiment, the method may further include a SIB transmission step. Specifically, the base station may transmit a System Information Block (SIB) containing the upper layer parameters to the terminal. This embodiment may be based on Method 1 and / or Method 3. The SIB transmission step may be performed prior to S610.

[0180] In one embodiment, the method may further include a capability information receiving step. Specifically, the base station receives capability information from the terminal. The present embodiment may be based on at least one of Methods 1 to 3. For example, transmission of the capability information by the terminal may mean reporting of capability by the terminal in Method 3. For example, the capability information receiving step may be performed before S610. For example, the capability information receiving step may be performed after the SIB transmission step.

[0181] In one embodiment, the method may further include a request receiving step. Specifically, the base station may receive information including a request for the repetition from the terminal. The request receiving step may be performed before S610 or S620. For example, the request receiving step may be performed after the SIB transmission step.

[0182] The operations based on the above-described S610 to S630, SIB transmission step, performance information reception step, and request reception step can be implemented by the device of FIG. 7. For example, the base station (100) can control one or more transceivers (130) and / or one or more memories (140) to perform operations based on S610 to S630, SIB transmission step, performance information reception step, and request reception step.

[0183] The operations / terms based on the embodiments described above have been described assuming a 5G system. However, this is for convenience of explanation and is not intended to limit the scope of application of the technical problems and problem-solving means to be solved by this specification to a specific system. In other words, the technical problems / technical issues / problems mentioned in this specification may equally exist in other systems (e.g., 6G systems). It is self-evident that the embodiments of this specification can be expanded and applied to solve problems that equally exist in these other systems. Therefore, for the expanded application of the embodiments of this specification to other systems, the terms defined / described based on the 5G system can be replaced / changed with terms defined in the other systems (or generalized terms not specific to one system).

[0184] Hereinafter, a device to which an embodiment of the present specification can be applied (a device that implements a method / operation according to an embodiment of the present specification) is described with reference to FIG. 7.

[0185] FIG. 7 is a drawing showing the configuration of a first device and a second device according to an embodiment of the present specification.

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

[0187] 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) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (115) may process operations of a PHY layer. For example, when the first device (100) is a base station device in base station-terminal communication, the physical layer processing unit (115) may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, when the first device (100) is a first terminal device in terminal-to-terminal communication, the physical layer processing unit (115) may perform downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. In addition to performing baseband-related signal processing, the processor (110) may also control the overall operation of the first device (100).

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

[0189] The processor (110) of the first device (100) may be configured to implement the operation of the base station in the base station-to-terminal communication (or the operation of the first terminal device in the terminal-to-terminal communication) in the embodiments described in the present disclosure.

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

[0191] 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) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (215) may process operations of a PHY layer. For example, when the second device (200) is a terminal device in base station-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, when the second device (200) is a second terminal device in terminal-to-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor (210) may also control the overall operation of the second device (210).

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

[0193] The processor (210) of the second device (200) may be configured to implement operations of the terminal in base station-to-terminal communication (or operations of the second terminal device in terminal-to-terminal communication) in the embodiments described in the present disclosure.

[0194] In the operation of the first device (100) and the second device (200), the same explanations given for the base station and the terminal (or the first terminal and the second terminal in the terminal-to-terminal communication) in the examples of the present disclosure may be applied, and redundant explanations are omitted.

[0195] Here, the wireless communication technology implemented in the device (100, 200) of the present 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 may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names.

[0196] Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented by 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 above-described names.

[0197] Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) that take low-power communication into account, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.

Claims

1. In a method performed by a terminal, A step of receiving a physical downlink shared channel (PDSCH), wherein the PDSCH includes a contention resolution identity; A step of receiving downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH); and A step of transmitting the PUSCH; including: The above DCI is based on DCI format 0_0 with CRC (Cyclic Redundancy Check) scrambled by C(Cell)-RNTI (Radio Network Temporary Identifier), A method characterized in that whether to enable repetition related to the PUSCH is determined based on a higher layer parameter.

2. In paragraph 1, A method characterized in that the above upper layer parameter indicates enabling or disabling the repetition.

3. In paragraph 1, A method characterized in that the above upper layer parameter indicates the number of repetitions.

4. In paragraph 1, A method further comprising the step of receiving a System Information Block (SIB) including the above upper layer parameters.

5. In paragraph 1, A method characterized in that, based on the above repetition being enabled, the PUSCH is transmitted based on time domain resources associated with the number of repetitions.

6. In paragraph 1, A method characterized in that the PUSCH is transmitted once based on the above upper layer parameter not being set.

7. In paragraph 1, A method further comprising the step of transmitting capability information, wherein the capability information includes first information indicating whether the repetition is supported by the terminal.

8. In paragraph 7, Based on the first information being included in the performance information, the performance information further includes second information, A method characterized in that the second information indicates whether repetition of a PUSCH scheduled by a Random Access Response (RAR, UL grant) is supported.

9. In paragraph 1, Further comprising the step of transmitting information including a request for the above repetition, A method characterized in that the information including the request is transmitted based on i) whether the repetition is supported by the terminal and / or ii) a condition related to the repetition.

10. In paragraph 9, A method characterized in that the above condition is satisfied based on the RSRP (Reference Signal Received Power) being less than the RSRP threshold.

11. In paragraph 10, A method characterized in that: the information including the request is transmitted based on i) the repetition being supported by the terminal and ii) the condition being satisfied.

12. At the terminal, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A terminal characterized in that the instructions are set to cause the one or more processors to perform all steps of the method according to any one of claims 1 to 11, based on being executed by the one or more processors.

13. In a device comprising one or more memories and one or more processors functionally connected to the one or more memories, A device characterized in that said one or more memories store instructions that cause said one or more processors to perform all steps of a method according to any one of claims 1 to 11, based on being executed by said one or more processors.

14. In one or more non-transitory computer-readable media storing instructions, One or more non-transitory computer-readable media characterized in that the instructions executable by 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 11.

15. In a method performed by a base station, A step of transmitting a physical downlink shared channel (PDSCH), wherein the PDSCH includes a contention resolution identity; A step of transmitting downlink control information (DCI) for scheduling a physical uplink shared channel (PUSCH); and A step of receiving the PUSCH; including: The above DCI is based on DCI format 0_0 with CRC (Cyclic Redundancy Check) scrambled by C(Cell)-RNTI (Radio Network Temporary Identifier), A method characterized in that whether to enable repetition related to the PUSCH is determined based on a higher layer parameter.

16. At the base station, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A base station characterized in that the instructions are set to cause the one or more processors to perform all steps of the method according to claim 15, based on the instructions being executed by the one or more processors.

Images