Method and apparatus for uplink transmission and reception

Abstract

A method according to an embodiment of the present specification comprises the steps of: receiving a PDSCH; receiving DCI for scheduling of a PUSCH; and transmitting the PUSCH. The DCI is based on DCI format 0_0 having a cyclic redundancy check (CRC) scrambled by a cell (C)-radio network temporary identifier (RNTI). The PUSCH is transmitted on the basis of the number of repetitions. On the basis that multiple values related to the number of repetitions are set, the number of repetitions is determined as an indicated value among the multiple values.

Description

Method and device for uplink transmission and reception

[0001] This specification relates to a method and device for uplink transmission and reception.

[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 setting / indicating the number of repetitions for a PUSCH scheduled by DCI format 0_0 having 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 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.

[0009] The above PDSCH includes a contention resolution identity.

[0010] 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).

[0011] The above PUSCH is transmitted based on the number of repetitions. At least one value related to the number of repetitions is set.

[0012] Based on the setting of multiple values ​​related to the number of repetitions, the number of repetitions is characterized in that the number of repetitions is determined as a value indicated among the multiple values.

[0013] One of the above multiple values ​​may be indicated based on the DCI.

[0014] One of the above multiple values ​​may be indicated based on the PDSCH.

[0015] One of the above multiple values ​​may be indicated based on the DCI for scheduling the PDSCH.

[0016] The at least one value may be set based on a System Information Block (SIB) or the PDSCH.

[0017] Based on one value being set related to the number of repetitions, the number of repetitions can be determined as the one value.

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

[0019] Based on the first information being included in the performance information, the performance information may further include second information. The second information may include i) information indicating whether repetition of a PUSCH scheduled by a Random Access Response (RAR, UL grant) is supported and / or ii) information indicating whether repetition of the PDSCH is supported.

[0020] Based on the first information indicating that the repetition of the PUSCH is supported, the second information may indicate that i) the repetition of the PUSCH scheduled by the UL grant and / or ii) the repetition of the PDSCH is supported.

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

[0022] The above instructions are characterized in that they cause the terminal to perform all steps of any one of the above methods based on being executed by the one or more processors.

[0023] According to another embodiment of the present disclosure, a device comprises one or more memories and one or more processors connected to the one or more memories. The one or more memories are characterized in that they store instructions that cause the device to perform all steps of any one of the above methods based on instructions executed by the one or more processors.

[0024] A non-transitory computer-readable medium according to another embodiment of the present disclosure stores instructions.

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

[0026] A method 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.

[0027] The above PDSCH includes a contention resolution identity.

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

[0029] The above PUSCH is received based on the number of repetitions. At least one value related to the number of repetitions is set.

[0030] Based on the setting of multiple values ​​related to the number of repetitions, the number of repetitions is characterized in that the number of repetitions is determined as a value indicated among the multiple values.

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

[0032] The above instructions are characterized in that they cause the base station to perform all steps of the method based on being executed by the one or more processors.

[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] Additionally, the ambiguity in terminal operation related to determining the number of repetitions for PUSCH for MSG5 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 according to one embodiment of the present specification.

[0042] FIG. 6 is a flowchart illustrating a method 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 to support repeated transmissions on the Msg5 PUSCH. Specifically, we examine the method for determining the repetition factor.

[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] Repetition factor determination for Msg5 PUSCH repeated transmission

[0098] In this specification, 'repetition factor' can be interpreted / replaced with 'number of repetitions'.

[0099] [Method 1]

[0100] One way to set the repetition factor is to use semi-static indications only. This is explained in detail below.

[0101] A method of setting / indicating a repetition factor value for Msg5 PUSCH repetitive transmission may be considered through a System Information Block (SIB). Specifically, the base station may set / indicate only one repetition factor value (e.g., one of the positive integers greater than or equal to 2) to be used for Msg5 PUSCH transmission in the corresponding cell based on the SIB. UEs capable of Msg5 PUSCH repetitive transmission within the corresponding cell may be configured to always perform repetitive transmissions equal to the repetition factor value.

[0102] This embodiment has an advantage in that it can set / indicate the repetition factor for Msg5 PUSCH in a simpler and more streamlined manner.

[0103] Meanwhile, it's common for not all terminals to be in the same situation. That is, the required number of repetitions may vary depending on the channel conditions of each terminal. In other words, terminal-specific repetition factors may be required. A related embodiment is described in detail in Method 2.

[0104] [Method 2]

[0105] A method for setting the repetition factor only through dynamic indication is considered. Below, 1) a method for setting the repetition factor based on the PDSCH (Msg4 PDSCH) and 2) a method for setting the repetition factor based on the PDCCH that schedules the PDSCH are described in turn.

[0106] < Configured via Msg4 PDSCH payload (UE specific value) >

[0107] During the RACH procedure, the terminal receives information based on Msg4 PDSCH and transmits information to the base station via Msg5 PUSCH. A repetition factor can be set / indicated in conjunction with these operations, as described in detail below.

[0108] For example, the base station can configure / instruct the UE to use the Msg4 PDSCH payload to set a repetition factor for repeated Msg5 PUSCH transmissions. Additionally, a repetition factor set for Msg5 PUSCH can be defined in advance. The base station can configure / instruct one of the values ​​within the set.

[0109] According to this embodiment, since the repetition factor is set to a UE-specific value, it has the advantage of allowing each UE to set an appropriate repetition factor when the number of repetitions required for each UE varies depending on channel conditions. This prevents cases where excessively small or excessive repetition factors are set for each UE. Consequently, unnecessary signaling overhead and PUSCH retransmissions can be reduced.

[0110] < Configured via PDCCH scheduling for Msg4 PDSCH (UE specific value) >

[0111] One may consider a method in which the base station indicates the Msg5 PUSCH repetition factor based on a specific field in the PDCCH (i.e., DCI format 1_0 with a CRC (Cyclic Redundancy Check) scrambled by a TC (Temporary Cell)-RNTI) for scheduling the Msg4 PDSCH.

[0112] For example, the repetition factor for Msg5 PUSCH can be dynamically indicated based on a specific DCI field associated with the PDCCH (i.e., DCI format 1_0 with CRC scrambled by TC (Temporary Cell)-RNTI) that schedules Msg4 PDSCH.

[0113] At this time, the specific DCI field may include i) a DAI (Downlink Assignment Index) field, ii) an MCS (Modulation and Coding Scheme) field, and / or iii) other fields (e.g., fields of DCI format 1_0). The MSB K bits of the specific DCI field may be configured to indicate a Msg5 PUSCH repetition factor (in this case, the remaining bits may be used for the original purpose of the field). Additionally, a repetition factor set for Msg5 PUSCH may be defined in advance. The base station may set / indicate one of the values ​​in the set.

[0114] [Method 3]

[0115] < Semi-static indication and / or dynamic indication >

[0116] A method of setting / indicating repetition factors by combining semi-static indications and dynamic indications can be considered.

[0117] In one embodiment, the base station may configure / indicate one or more repetition factors (e.g., cell specific repetition factor(s)) for Msg5 PUSCH repetitive transmission via SIB. If the base station configures / indicates only one repetition factor (e.g., one of the positive integers greater than or equal to 2) via SIB, UEs capable of Msg5 PUSCH repetitive transmission within the corresponding cell may be configured to always perform repetitive transmissions equal to the repetition factor value.

[0118] In one embodiment, the base station may configure / instruct the terminal to perform only one repetition factor (e.g., one of the positive integers greater than or equal to 2) through the Msg4 PDSCH payload. The terminal may be configured to always perform repeated transmissions for the repetition factor value.

[0119] In one embodiment, a base station can configure / indicate multiple repetition factors (e.g., two or more different positive integers) via SIB. In this case, a dynamic indication is required to indicate the final repetition factor to be used. This dynamic indication can be performed as described in Method 2, which will be described in detail below.

[0120] For example, one of the plurality of repetition factors may be dynamically configured / indicated based on the Msg4 PDSCH payload. For example, one of the plurality of repetition factors may be dynamically configured / indicated based on the PDCCH scheduling the Msg4 PDSCH. A more specific configuration method may follow [Method 2].

[0121] In one embodiment, the base station can configure / indicate multiple repetition factors (e.g., two or more different positive integers) to the terminal based on the Msg4 PDSCH payload. In this case, a dynamic indication is required to indicate the repetition factor to be finally used. In this case, the dynamic indication can be performed as follows. One of the multiple repetition factors (i.e., the repetition factor to be used by the terminal) can be configured / indicated based on a specific DCI field of a PDCCH (i.e., DCI format 0_0 having a CRC scrambled with C-RNTI) that schedules the Msg5 PUSCH to be transmitted thereafter. In this case, the specific DCI field can include i) a DAI (Downlink Assignment Index) field, ii) an MCS (Modulation and Coding Scheme) field, and / or iii) other fields (e.g., a field of DCI format 0_0). The MSB K bits of the specific field can be configured to indicate the Msg5 PUSCH repetition factor (in this case, the remaining bits can be used for the original purpose of the field). In the present embodiment, the following effects are achieved.

[0122] By setting / indicating multiple repetition factors (e.g., repetition factor set) via the Msg4 PDSCH payload rather than the SIB, appropriate values ​​can be set / indicated differently for each terminal depending on its circumstances. This provides the advantage of increased freedom for the base station in setting repetition factors.

[0123] [Method 4]

[0124] < Linkage based on previous channels >

[0125] A method may be considered to configure the repetition factor of Msg5 PUSCH to be related to the repetition factor used for other UL channels previously (e.g., Msg3 PUSCH, Msg4 HARQ-ACK PUCCH). Specifically, the UE may use a value for Msg5 PUSCH based on the repetition factor used for other UL channels prior to Msg5 PUSCH. The value based on the repetition factor may be i) the same value or ii) a relative value, which will be described in detail later.

[0126] This embodiment has the following advantages. The UL channel environment may not change significantly between the time when the UE transmits the UL channels (e.g., Msg3 PUSCH, Msg4 HARQ-ACK PUCCH) before transmitting Msg5 PUSCH and the time when Msg5 PUSCH is transmitted. In other words, the channel environment related to Msg5 PUSCH may be similar to the channel environment related to previous UL channels. Therefore, this embodiment can be a reasonable method for setting the Msg5 PUSCH repetition factor. In addition, this method has the advantage that there is no need to define a separate repetition factor set or consider a separate instruction method for Msg5 PUSCH.

[0127] < Same repetition factor as repetition factor of previous channels >

[0128] The repetition factor of Msg5 PUSCH can be set to the same repetition factor used for other UL channels previously.

[0129] For example, the repetition factor of Msg3 PUSCH to be transmitted before Msg5 PUSCH can be configured to be used as is for Msg5 PUSCH transmission. That is, if the base station configures / instructs a repetition factor of Msg3 PUSCH to a specific UE, the UE can be configured to use the same value as the repetition factor used as the repetition factor of Msg5 PUSCH. Meanwhile, since Msg3 PUSCH is an example of a UL channel before Msg5 PUSCH, Msg3 PUSCH can be replaced with another UL channel. As a specific example, in the operation according to the example described above, 'Msg3 PUSCH' can be replaced with 'Msg4 HARQ-ACK PUCCH' or 'PUCCH before receiving dedicated PUCCH resource configuration'.

[0130] < Relative repetition factor based on repetition factor of previous channels >

[0131] In one embodiment, the repetition factor of Msg5 PUSCH may be set to have dependency with the repetition factor used by another previous UL channel (e.g., Msg3 PUSCH, Msg4 HARQ-ACK PUCCH).

[0132] For example, the repetition factor of the Msg5 PUSCH may be determined based on the repetition factor value of the Msg3 PUSCH transmitted prior to the Msg5 PUSCH. If the base station sets / indicates the repetition factor of the Msg3 PUSCH transmitted by a specific UE, the UE may be configured to obtain the repetition factor value of the Msg5 PUSCH from the repetition factor used at that time. Specific examples related to the determination of the Msg5 PUSCH repetition factor are as follows: 1) and 2).

[0133] 1) The Msg5 PUSCH repetition factor can be determined by adding an offset value to the Msg3 PUSCH repetition factor.

[0134] 2) The Msg5 PUSCH repetition factor can be determined by multiplying the Msg3 PUSCH repetition factor by a scaling value.

[0135] The above offset value and / or the above scaling value may be defined so that the base station provides it through SIB.

[0136] Meanwhile, Msg3 PUSCH is an example of a UL channel prior to Msg5 PUSCH, and thus Msg3 PUSCH may be replaced with another UL channel. For example, in the operation according to the above-described example, 'Msg3 PUSCH' may be replaced with 'Msg4 HARQ-ACK PUCCH' or 'PUCCH before receiving dedicated PUCCH resource configuration'.

[0137] In one embodiment, the repetition factor set to be used for Msg5 PUSCH may be configured to have dependency with the repetition factor set used in another previous UL channel (e.g., Msg3 PUSCH, Msg4 HARQ-ACK PUCCH).

[0138] For example, the repetition factor set of the Msg5 PUSCH may be configured to be determined based on the repetition factor set of the Msg3 PUSCH transmitted prior to the Msg5 PUSCH. If the base station configures / indicates the repetition factor set of the Msg3 PUSCH transmitted by a specific UE, the UE may be configured to obtain the repetition factor set of the Msg5 PUSCH from the repetition factor set used at that time.

[0139] Specific examples related to determining the Msg5 PUSCH repetition factor set are as follows: 1) and 2).

[0140] 1) The Msg5 PUSCH repetition factor set can be determined by adding the (common) offset value to the factors in the Msg3 PUSCH repetition factor set.

[0141] 2) The Msg5 PUSCH repetition factor set can be determined by multiplying the factors in the Msg3 PUSCH repetition factor set by a (common) scaling value.

[0142] The above offset value and / or the above scaling value may be defined so that the base station provides it via SIB. Meanwhile, after the repetition factor set is determined in this way, the dynamic indication method of Method 2 or Method 3 may be applied to determine / set / indicate the repetition factor used by the terminal.

[0143] Meanwhile, Msg3 PUSCH is an example of a UL channel prior to Msg5 PUSCH, and thus Msg3 PUSCH may be replaced with another UL channel. For example, in the operation according to the above-described example, 'Msg3 PUSCH' may be replaced with 'Msg4 HARQ-ACK PUCCH' or 'PUCCH before receiving dedicated PUCCH resource configuration'.

[0144] Additionally, a method may be considered in which the UE dynamically sets / indicates an offset to be additionally applied to the repetition factor value (e.g., R) used for the most recently transmitted Msg3 PUSCH. That is, the base station may use a dynamic indication (e.g., DCI format 0_0 scrambling with C-RNTI) to indicate one of {0, offset1, offset2, offset3} to the UE through a specific DCI field. Thereafter, the UE may determine the repetition factor for Msg5 PUSCH as one of {R, R+offset1, R+offset2, R+offset3} based on the information and be configured to perform repeated Msg5 PUSCH transmission.

[0145] Meanwhile, in order to apply the method according to the present embodiment, the UE capability may be defined as follows. A UE capable of Msg5 PUSCH repetition may be configured to always be capable of Msg3 PUSCH repetition (or Msg4 HARQ-ACK PUCCH repetition). In other words, a UE supporting Msg5 PUSCH repetition may be configured / defined to also support Msg3 PUSCH repetition (or Msg4 HARQ-ACK PUCCH repetition). In this case, the UE may report UE capability information to the base station as follows.

[0146] Based on the fact that the UE capability information includes information indicating whether Msg5 PUSCH repetition is supported, the UE capability information may further include information indicating whether Msg3 PUSCH repetition and / or Msg4 HARQ-ACK PUCCH repetition is supported. More specifically, based on the fact that Msg5 PUSCH repetition is supported by the UE, the UE capability information may further include information indicating whether Msg3 PUSCH repetition and / or Msg4 HARQ-ACK PUCCH repetition is supported.

[0147] In the above methods, if it is determined that Msg5 PUSCH repetition is enabled and dynamic indication for Msg5 PUSCH repetition factor is performed, the terminal may operate as follows.

[0148] Before receiving PUSCH-config, the UE may be configured to receive DCI, expecting that there will be a specific field in the DCI for indicating the Msg5 PUSCH repetition factor. The DCI may include DCI format 1_0 with a CRC scrambled by TC-RNTI and / or DCI format 0_0 with a CRC scrambled by C-RNTI.

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

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

[0151] 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 4) can be processed by the device of FIG. 7 described below (e.g., processor (110, 210) of FIG. 7).

[0152] 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 methods 1 to 4) may be stored in a memory (e.g., 140, 240 of FIG. 7) in the form of commands / programs (e.g., instructions, executable codes) for driving at least one processor (e.g., 110, 210 of FIG. 7).

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

[0154] FIG. 5 is a flowchart illustrating a method according to one embodiment of the present specification.

[0155] Referring to FIG. 5, a method according to one embodiment of the present specification includes a physical downlink shared channel receiving step (S510), a downlink control information receiving step (S520), and a physical uplink shared channel transmitting step (S530).

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

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

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

[0159] 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).

[0160] The above PUSCH can be transmitted based on a number of repetitions. The number of repetitions can be set / indicated / determined based on at least one of the above-described methods 1 to 4. This will be described in detail below.

[0161] In one embodiment, at least one value related to the number of repetitions may be set. The present embodiment may be based on at least one of Methods 1 to 3.

[0162] For example, based on a value set related to the number of repetitions, the number of repetitions may be determined as the one value. This embodiment may be based on Method 1.

[0163] For example, based on the setting of multiple values ​​related to the number of repetitions, the number of repetitions may be determined as a value indicated among the multiple values. Hereinafter, embodiments related to the indication of one of the multiple values ​​will be described.

[0164] In one embodiment, one of the plurality of values ​​may be indicated based on the DCI. Specifically, one of the plurality of values ​​may be indicated based on a field in the DCI that schedules the PUSCH (e.g., Msg5 PUSCH). The field may include i) a DAI (Downlink Assignment Index) field, ii) an MCS (Modulation and Coding Scheme) field, and / or iii) another field (e.g., a field of DCI format 0_0). The present embodiment may be based on Method 3. As a specific example, one of the plurality of values ​​may be indicated based on K bit(s) among bits of the field, based on whether the field is the DAI field or the MCS field.

[0165] For example, the K bit(s) may be based on the MSB (Most Significant Bit) K bit(s) of the field. As a specific example, one of the plurality of values ​​may be indicated based on the leftmost K (e.g., 2) bit(s) (e.g., 10) in the bit value (e.g., '1001') according to the number of bits (e.g., 4) of the field. The K value may be defined in advance or set / indicated based on upper layer signaling.

[0166] In one embodiment, one of the plurality of values ​​may be indicated based on the PDSCH. Specifically, the PDSCH (e.g., Msg4 PDSCH) may include information indicating one of the plurality of values. This embodiment may be based on Method 3.

[0167] In one embodiment, one of the plurality of values ​​may be indicated based on DCI for scheduling the PDSCH. Specifically, one of the plurality of values ​​may be indicated based on a field in the DCI for scheduling the PDSCH (e.g., Msg4 PDSCH). The present embodiment may be based on Method 2 and Method 3. The field may include i) a DAI (Downlink Assignment Index) field, ii) an MCS (Modulation and Coding Scheme) field, and / or iii) other fields (e.g., fields of DCI format 1_0). As a specific example, one of the plurality of values ​​may be indicated based on K bit(s) among bits of the field, based on whether the field is the DAI field or the MCS field.

[0168] For example, the K bit(s) may be based on the MSB (Most Significant Bit) K bit(s) of the field. As a specific example, one of the plurality of values ​​may be indicated based on the leftmost K (e.g., 2) bit(s) (e.g., 10) in the bit value (e.g., '1001') according to the number of bits (e.g., 4) of the field. The K value may be defined in advance or set / indicated based on upper layer signaling.

[0169] Below, the operation related to setting at least one value related to the number of repetitions is specifically described.

[0170] In one embodiment, the at least one value may be set based on a System Information Block (SIB) or the PDSCH. This embodiment may be based on Method 3.

[0171] Although the operations related to determining the number of repetitions described above have been described based on at least one of Methods 1 to 3, it is obvious that operations of other embodiments (i.e., Method 4) may be combined as long as they are not mutually exclusive. For example, the number of repetitions may be set / determined / indicated based on at least one of Methods 1 to 3, and the UE capability related to the repetition of the PUSCH (e.g., msg5 PUSCH) may be defined / configured based on Method 4. This will be described in detail below.

[0172] 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 Method 4. The capability information may include first information indicating whether repetition of the PUSCH is supported by the terminal.

[0173] Based on the first information being included in the performance information, the performance information may further include second information. The second information may include i) information indicating whether repetition of a PUSCH (e.g., msg3 PUSCH) scheduled by a Random Access Response (RAR, UL grant) is supported and / or ii) information indicating whether repetition of the PDSCH (e.g., msg4 PDSCH) is supported.

[0174] For example, if the repetition of the PUSCH is supported, the capability of the terminal may be defined so that repetition of the PUSCH scheduled by the UL grant and / or repetition of the PDSCH are also mandatorily supported. Specifically, based on the first information indicating that the repetition of the PUSCH is supported, the second information may indicate that the repetition of the PUSCH scheduled by the UL grant and / or repetition of the PDSCH are supported.

[0175] For example, the performance information transmission step may be performed before S510.

[0176] The operations based on the above-described S510 to S530 and performance information transmission steps 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 and performance information transmission steps.

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

[0178] The steps S610 to S630 and the performance information reception steps described below correspond to the steps S510 to S530 and the performance information transmission steps described in FIG. 5. Considering the above correspondence, redundant descriptions are omitted. That is, the specific descriptions of the base station operations described below may be replaced with the corresponding descriptions / exemplifications of FIG. 5.

[0179] FIG. 6 is a flowchart illustrating a method according to another embodiment of the present specification.

[0180] Referring to FIG. 6, a method according to another embodiment of the present specification includes a physical downlink shared channel transmission step (S610), a downlink control information transmission step (S620), and a physical uplink shared channel reception step (S630).

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

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

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

[0184] 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).

[0185] The above PUSCH can be received based on the number of repetitions. The number of repetitions can be set / indicated / determined based on at least one of the above-described methods 1 to 4.

[0186] In one embodiment, the method may further include a capability information receiving step. Specifically, the base station receives capability information from the terminal.

[0187] The operations based on the above-described S610 to S630 and performance information receiving steps 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 the S610 to S630 and performance information receiving steps.

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

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

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

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

[0192] 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).

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

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

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

[0196] 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).

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

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

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

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

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

[0202] 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 the method, 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), The above PUSCH is transmitted based on the number of repetitions, At least one value related to the number of repetitions is set, A method characterized in that, based on the plurality of values ​​set in relation to the number of repetitions, the number of repetitions is determined as a value indicated among the plurality of values.

2. In paragraph 1, A method characterized in that one of the plurality of values ​​is indicated based on the DCI.

3. In paragraph 1, A method characterized in that one of the plurality of values ​​is indicated based on the PDSCH.

4. In paragraph 1, A method characterized in that one of the plurality of values ​​is indicated based on DCI for scheduling of the PDSCH.

5. In paragraph 1, A method characterized in that at least one of the values ​​is set based on a System Information Block (SIB) or the PDSCH.

6. In paragraph 1, A method characterized in that the number of repetitions is determined based on a value set in relation to the number of repetitions.

7. In paragraph 1, further comprising a step of transmitting performance information; A method characterized in that the performance information includes first information indicating whether repetition of the PUSCH 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 includes i) information indicating whether repetition of a PUSCH scheduled by a Random Access Response (RAR, UL grant) is supported and / or ii) information indicating whether repetition of the PDSCH is supported.

9. In paragraph 8, A method characterized in that, based on the first information indicating that the repetition of the PUSCH is supported, the second information indicates that i) the repetition of the PUSCH scheduled by the UL grant and / or ii) the repetition of the PDSCH is supported.

10. In 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, based on being executed by the one or more processors, cause the terminal to perform all steps of the method according to any one of claims 1 to 9.

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

12. In a non-transitory computer-readable medium storing instructions, A non-transitory computer-readable medium characterized in that the instructions executable by one or more processors cause a terminal to perform all steps of a method according to any one of claims 1 to 9.

13. In the method, 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), The above PUSCH is received based on the number of repetitions, At least one value related to the number of repetitions is set, A method characterized in that, based on the plurality of values ​​set in relation to the number of repetitions, the number of repetitions is determined as a value indicated among the plurality of values.

14. 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, based on being executed by the one or more processors, cause the base station to perform all steps of the method according to claim 13.

Images