METHOD FOR TRANSMITTING AND RECEIVING PUSCH IN A WIRELESS COMMUNICATION SYSTEM AND APPARATUS THEREFOR

Abstract

This specification proposes a method for transmitting a PUSCH in a wireless communication system. The method performed by a terminal may include receiving configuration information for a time domain window from a base station, receiving downlink control information (DCI) including scheduling information for the PUSCH and frequency hopping information for the PUSCH from the base station, transmitting the PUSCH to the base station in a first frequency hop having a length equal to a first time domain window, and transmitting the PUSCH to the base station in a second frequency hop having a length equal to a second time domain window.

Description

[Technical field]

[0001] The present specification relates to a wireless communication system, and more particularly, to a method and apparatus for transmitting and receiving a physical uplink shared channel (PUSCH). [Background technology]

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, the scope of mobile communication systems has expanded beyond voice to data services, and currently, the explosive increase in traffic has caused resource shortages and users are demanding faster services, so there is a demand for more advanced mobile communication systems.

[0003] The next generation mobile communication system has many requirements, including the ability to accommodate explosive data traffic, a dramatic increase in transmission rate per user, a significantly increased number of connected devices, extremely low end-to-end latency, and high energy efficiency. To achieve this, various technologies are being researched, 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, a technique for repeatedly transmitting the PUSCH / PUCCH for the purpose of coverage enhancement is being discussed. Summary of the Invention [Problem to be solved by the invention]

[0005] This specification proposes a method and apparatus for defining / configuring a time domain window for demodulation reference signal (DMRS) bundling (or inter-slot bundling).

[0006] This specification also proposes a method and an apparatus for defining / setting a time domain window based on the number of repeated transmissions of PUSCH / PUCCH.

[0007] This specification also proposes a method and apparatus for defining / setting a hopping interval having the same length as the time domain window.

[0008] The technical problems to be achieved in this specification are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by a person having ordinary skill in the art to which the present invention pertains from the following description. [Means for solving the problem]

[0009] This specification proposes a method for transmitting a physical uplink shared channel (PUSCH) in a wireless communication system.

[0010] The method performed by the terminal may include receiving configuration information for a time domain window from a base station, receiving downlink control information (DCI) from the base station including scheduling information for the PUSCH and frequency hopping information for the PUSCH, transmitting the PUSCH to the base station at a first frequency hop having the same length as a first time domain window, and transmitting the PUSCH to the base station at a second frequency hop having the same length as a second time domain window.

[0011] Also, in the method herein, the length of the first frequency hop and the second frequency hop may be determined based on a length of the time domain window and a slot number within a radio frame.

[0012] Also, in the method herein, a starting resource block (RB) of the second frequency hop may be determined based on a starting RB of the first frequency hop and a frequency offset.

[0013] Additionally, in the method herein, the first frequency hop may be an even numbered hop and the second frequency hop may be an odd numbered hop.

[0014] In the method of the present specification, a slot for the PUSCH A starting resource block (RB) for JPEG0007656722000001.jpg67 may be determined based on the following formula:

[0015]

number

[0016] Where: JPEG0007656722000003.jpg714 indicates the start RB of the first frequency hop, JPEG0007656722000004.jpg715 indicates a frequency offset between the first frequency hop and the second frequency hop; JPEG0007656722000005.jpg710 indicates the size of the uplink bandwidth part (BWP), JPEG0007656722000006.jpg56 indicates the length of the time domain window.

[0017] Also, in the method herein, the time domain window may be a time domain window for demodulation reference signal (DMRS) bundling.

[0018] Also, in the method herein, the same phase and transmission power may be maintained within the time domain window.

[0019] In the method of the present specification, the time domain window may be set based on the number of PUSCH repetitions.

[0020] Also, in the method herein, the PUSCH may be transmitted based on frequency hopping over multiple slots.

[0021] In addition, in the wireless communication system of the present specification, a terminal configured to transmit a physical uplink shared channel (PUSCH) may include at least one transceiver, at least one processor, and at least one memory operably connected to the at least one processor and storing instructions for performing operations based on being executed by the at least one processor, and the operations may include a step of receiving configuration information for a time domain window from a base station, a step of receiving downlink control information (DCI) from a base station, the DCI including scheduling information for the PUSCH and frequency hopping information for the PUSCH, a step of transmitting the PUSCH to the base station at a first frequency hop having the same length as a first time domain window, and a step of transmitting the PUSCH to the base station at a second frequency hop having the same length as a second time domain window.

[0022] Also, a method for receiving a physical uplink shared channel (PUSCH) in a wireless communication system of the present specification is proposed. The method performed by a base station may include transmitting configuration information for a time domain window to a terminal, transmitting downlink control information (DCI) including scheduling information for the PUSCH and frequency hopping information for the PUSCH to the terminal, receiving the PUSCH from the terminal at a first frequency hop having the same length as a first time domain window, and receiving the PUSCH from the terminal at a second frequency hop having the same length as a second time domain window.

[0023] Also, in the method herein, a starting resource block (RB) of the second frequency hop may be determined based on a starting RB of the first frequency hop and a frequency offset.

[0024] Additionally, in the method herein, the first frequency hop may be an even numbered hop and the second frequency hop may be an odd numbered hop.

[0025] In the method of the present specification, a slot for the PUSCH A starting resource block (RB) for JPEG0007656722000007.jpg67 may be determined based on the following formula:

[0026]

number

[0027] Where: JPEG0007656722000009.jpg714 indicates the start RB of the first frequency hop, JPEG0007656722000010.jpg715 indicates a frequency offset between the first frequency hop and the second frequency hop; JPEG0007656722000011.jpg710 indicates the size of the uplink bandwidth part (BWP), JPEG0007656722000012.jpg56 indicates the length of the time domain window.

[0028] Also, in the method herein, the time domain window may be a time domain window for demodulation reference signal (DMRS) bundling.

[0029] Also, in the method herein, the same phase and transmission power may be maintained within the time domain window.

[0030] In the method of the present specification, the time domain window may be set based on the number of PUSCH repetitions.

[0031] In addition, in the wireless communication system of the present specification, a base station configured to receive a physical uplink shared channel (PUSCH) may include at least one transceiver, at least one processor, and at least one memory operatively connected to the at least one processor and storing instructions for performing operations based on being executed by the at least one processor, and the operations may include a step of transmitting configuration information for a time domain window to a terminal, a step of transmitting downlink control information (DCI) to the terminal, the DCI including scheduling information for the PUSCH and frequency hopping information for the PUSCH, a step of receiving the PUSCH from the terminal at a first frequency hop having the same length as a first time domain window, and a step of receiving the PUSCH from the terminal at a second frequency hop having the same length as a second time domain window.

[0032] In addition, a processing apparatus configured to control a terminal to transmit a physical uplink shared channel (PUSCH) in a wireless communication system of the present specification may include at least one processor and at least one memory operably connected to the at least one processor and storing instructions to perform operations based on being executed by the at least one processor, and the operations may include receiving configuration information for a time domain window from a base station, receiving downlink control information (DCI) from the base station including scheduling information for the PUSCH and frequency hopping information for the PUSCH, transmitting the PUSCH to the base station at a first frequency hop having the same length as a first time domain window, and transmitting the PUSCH to the base station at a second frequency hop having the same length as a second time domain window.

[0033] In addition, in a computer-readable storage medium storing at least one instruction for causing the at least one processor to control operations based on being executed by at least one processor of the present specification, the operations may include receiving configuration information for a time domain window from a base station, receiving downlink control information (DCI) from the base station including scheduling information for a physical uplink shared channel (PUSCH) and frequency hopping information for the PUSCH, transmitting the PUSCH to the base station at a first frequency hop having the same length as a first time domain window, and transmitting the PUSCH to the base station at a second frequency hop having the same length as a second time domain window. Effect of the Invention

[0034] According to this specification, defining / configuring a time domain window for DMRS bundling (or inter-slot bundling) has the effect of improving coverage.

[0035] Moreover, according to this specification, by defining / setting a time domain window based on the number of times PUSCH / PUCCH are repeatedly transmitted, it is possible to efficiently perform joint channel estimation.

[0036] In addition, according to the present specification, by defining / setting a hopping interval having the same length as the time domain window, it is possible to perform joint channel estimation simultaneously with inter-slot frequency hopping.

[0037] The effects obtained by the present invention are not limited to those mentioned above, and another effect not mentioned will be clearly understood by a person having ordinary skill in the art to which the present invention pertains from the following description. [Brief description of the drawings]

[0038] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present invention, provide embodiments of the present invention and, together with the detailed description, explain the technical features of the present invention.

[0039] [Figure 1] An example of the overall system structure of NR to which the method proposed in this specification can be applied is shown.

[0040] [Diagram 2] 2 illustrates the relationship between uplink and downlink frames in a wireless communication system in which the method proposed herein can be applied;

[0041] [Diagram 3] 1 shows an example of a frame structure in an NR system.

[0042] [Figure 4] 1 shows an example of a resource grid supported by a wireless communication system in which the method proposed herein can be applied.

[0043] [Diagram 5] 1 shows the slot structure of an NR frame to which the method proposed in this specification can be applied.

[0044] [Figure 6] 1 shows an example of an antenna port and neurology specific resource grid to which the method proposed in this specification can be applied.

[0045] [Figure 7] 1 shows the physical channels and general signal transmission.

[0046] [Figure 8] An example of PUSCH repetition type A is shown.

[0047] [Figure 9] An example of PUSCH repetition type B is shown.

[0048] [Figure 10] 13 shows an example of DMRS positions according to mapping type and number of OFDM symbols.

[0049] [Figure 11] 1 is a flowchart for explaining a method of operating a terminal proposed in this specification.

[0050] [Figure 12] 1 is a flowchart for explaining a method of operating a base station proposed in this specification.

[0051] [Figure 13] 1 shows a communication system 1 to which the present specification is applied.

[0052] [Figure 14] 1 illustrates a wireless device to which the present invention can be applied.

[0053] [Figure 15] 1 shows another example of a wireless device to which the present specification is applied.

[0054] [Figure 16] 1 illustrates a mobile device to which the present specification is applied. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0055] Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings. The detailed description disclosed below in conjunction with the accompanying drawings is intended to describe exemplary embodiments of the present invention, and is not intended to show the only embodiments in which the present invention can be practiced. The following detailed description includes specific details to provide a complete understanding of the present invention. However, those skilled in the art will appreciate that the present invention can be practiced without such specific details.

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

[0057] Hereinafter, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, a transmitter may be a part of the base station, and a receiver may be a part of the terminal. In the uplink, a transmitter may be a part of the terminal, and a receiver may be a part of the base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. A base station (BS) may be replaced with terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP), 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, a terminal may be fixed or mobile, and may be replaced with terms such as User Equipment (UE), Mobile Station (MS), user terminal (UT), Mobile Subscriber Station (MSS), Subscriber Station (SS), Advanced Mobile Station (AMS), Wireless terminal (WT), Machine-Type Communication (MTC) device, Machine-to-Machine (M2M) device, Device-to-Device (D2D) device, vehicle, robot, AI module, Unmanned Aerial Vehicle (UAV), Augmented Reality (AR) device, Virtual Reality (VR) device, etc.

[0058] The following technologies may be used for various wireless access systems, such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA may be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented in a wireless technology such as GSM (Global System for Mobile communications / GPRS (General Packet Radio Service / EDGE (Enhanced Data Rates for GSM Evolution)). OFDMA may be implemented in a wireless technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (Evolved UTRA), etc. UTRA is a part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0059] For clarity of explanation, the following description will be based on a 3GPP communication system (e.g., LTE-A, NR), but the technical idea of ​​the present invention is not limited thereto. LTE refers to technology from 3GPP TS 36.xxx Release 8 onwards. In detail, LTE technology from 3GPP TS 36.xxx Release 10 onwards is called LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onwards is called LTE-A pro. 3GPP NR refers to technology from TS 38.xxx Release 15 onwards. LTE / NR may be referred to as a 3GPP (registered trademark) system. "xxx" refers to the detailed number of a standard document. LTE / NR may be commonly referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present invention, reference may be made to matters described in standard documents published before the present invention. For example, the following documents may be referenced.

[0060] 3GPP LTE

[0061] -36.211:Physical channels and modulation

[0062] -36.212:Multiplexing and channel coding

[0063] -36.213:Physical layer procedures

[0064] -36.300:Overall description

[0065] -36.331:Radio Resource Control (RRC)

[0066] 3GPP NR

[0067] -38.211:Physical channels and modulation

[0068] -38.212:Multiplexing and channel coding

[0069] -38.213:Physical layer procedures for control

[0070] -38.214:Physical layer procedures for data

[0071] -38.300:NR and NG-RAN Overall Description

[0072] -38.331:Radio Resource Control (RRC) protocol specification

[0073] As more communication devices require larger communication capacity, the need for improved mobile broadband communication compared to conventional radio access technology is emerging. In addition, massive MTC (Machine Type Communications), which connects a large number of devices and things and provides various services anytime and anywhere, is also one of the important issues to be considered in next-generation communication. In addition, the design of communication systems that take into account reliability and latency-sensitive services / terminals is being discussed. Thus, the introduction of next-generation radio access technology that takes into account eMBB (enhanced mobile broadband communication), Mmtc (massive MTC), URLLC (Ultra-Reliable and Low Latency Communication), etc. is being discussed, and for convenience, the technology is referred to as NR in this specification. NR is an expression that shows an example of 5G wireless access technology (radio access technology, RAT).

[0074] The three main requirement areas for 5G include (1) the Enhanced Mobile Broadband (eMBB) area, (2) the massive Machine Type Communication (mMTC) area, and (3) the Ultra-reliable and Low Latency Communications (URLLC) area.

[0075] Some use cases may require multiple areas for optimization, while others may only be focused on one Key Performance Indicator (KPI). 5G will support such diverse use cases in a flexible and reliable way.

[0076] eMBB goes far beyond basic mobile Internet access and covers rich interactive work, media and entertainment applications in the cloud or augmented reality. Data is one of the core drivers of 5G, and it is possible that we will not see dedicated voice services for the first time in the 5G era. In 5G, voice is expected to be handled simply as an application using the data connection provided by the communication system. The main causes for the increased traffic volume are the increase in content size and the increase in the number of applications that require high data transmission rates. Streaming services (audio and video), interactive video and mobile Internet connections are more widely used as more devices are connected to the Internet. Many such applications require always-on connectivity to push real-time information and notifications to users. Cloud storage and applications are rapidly increasing on mobile communication platforms, which can be applied to both work and entertainment, and cloud storage is a particular use case that is driving the growth of uplink data transmission rates. 5G will also be used for remote work in the cloud, which requires much lower end-to-end latency to maintain an excellent user experience when haptic interfaces are used. Entertainment, e.g., cloud gaming and video streaming, is another key factor that increases the demand for mobile broadband capabilities. Entertainment is essential on smartphones and tablets everywhere, including in high mobility environments such as trains, cars, and airplanes. Another use case is augmented reality and information retrieval for entertainment, where augmented reality requires very low latency and instantaneous data volume.

[0077] Also, one of the most anticipated use cases for 5G is its ability to seamlessly connect embedded sensors in all sectors, i.e. mMTC. It is predicted that the number of potential IoT devices will reach 20.4 billion by 2020. Industrial IoT is one area where 5G will play a key role in enabling smart cities, asset tracking, smart utilities, agriculture and security infrastructure.

[0078] URLLC includes new services transforming industries through ultra-reliable / available low-latency links such as remote control of critical infrastructure and self-driving vehicles. Reliability and latency levels are essential for smart grid control, industrial automation, robotics, drone control and coordination.

[0079] A number of use cases will be described in more detail below.

[0080] 5G can complement fiber-to-the-home (FTTH) and cable-based broadband (or DOCSIS) as a means of delivering streams rated at hundreds of megabits per second to gigabits per second. Such high speeds are required to deliver TV at resolutions of 4K and above (6K, 8K and beyond), as well as virtual and augmented reality. Virtual reality (VR) and augmented reality (AR) applications include most immersive sports. Certain application programs may require special network configurations. For example, in the case of VR games, gaming companies may have to integrate their core servers with the network operator's edge network servers to minimize latency.

[0081] Automotive is expected to be an important new driver in 5G with many use cases for mobile communications to vehicles. For example, entertainment for passengers will require simultaneous high capacity and high mobility mobile broadband, because future users will expect continuous high quality connectivity regardless of their location and speed. Another use case in the automotive field is the augmented reality dashboard, which displays information overlaid on top of what the driver sees through the front window, identifying objects in the dark and informing the driver about the object's distance and movement. In the future, wireless modules will enable communication between vehicles, information exchange between vehicles and supporting infrastructure, and between cars and other connected devices (e.g. devices carried by pedestrians). Safety systems will be able to guide drivers on alternative courses of action to drive more safely and reduce the risk of accidents. The next step will be remotely piloted or self-driven vehicles, which will require very reliable and very fast communication between different autonomous vehicles and between cars and infrastructure. In the future, autonomous vehicles will perform all driving activities, leaving the driver to focus only on traffic anomalies that the vehicle itself cannot identify. The technical requirements for autonomous vehicles demand ultra-low latency and ultra-high speed reliability to increase traffic safety to a level unattainable by humans.

[0082] Smart cities and smart homes, also referred to as smart society, are embedded with high density wireless sensor networks. A distributed network of intelligent sensors identifies requirements for cost and energy efficient maintenance of the city or home. A similar setup can be made for each home. Temperature sensors, window and heating controllers, burglar alarms and home appliances are all wirelessly connected. Many of these sensors typically have low data transmission rates, low power consumption and low cost. However, for example, real-time HD video may be required by certain types of devices for surveillance.

[0083] The consumption and distribution of energy, including heat or gas, is highly decentralized, requiring automated control of distributed sensor networks. A smart grid interconnects such sensors using digital information and communication technologies to collect and act upon information. This information can include supplier and consumer actions, allowing the smart grid to improve the efficiency, reliability, economy, sustainability of production, and distribution of fuels, such as electricity, in an automated manner. A smart grid can also be viewed as another sensor network with low latency.

[0084] The health sector has many applications that can benefit from mobile communications. Communication systems can support telemedicine to provide clinical care over long distances. This helps to reduce the barriers of distance and can improve access to medical services that are not sustainably available in remote rural areas. It can also be used to save lives in critical care and emergency situations. Mobile-based wireless sensor networks can provide remote monitoring and sensing for parameters such as heart rate and blood pressure.

[0085] Wireless and mobile communications are becoming more and more important in industrial applications. Wiring is expensive to install and maintain. The possibility to replace cables with reconfigurable wireless links is therefore an attractive opportunity in many industrial sectors. However, achieving this requires that wireless connections operate with similar latency, reliability and capacity as cables, and that their management is simplified. Low latency and very low error probability are new requirements that need to be addressed with 5G.

[0086] Logistics and freight tracking are important use cases for mobile communications that use location-based information systems to enable tracking of inventory and packages anywhere. Logistics and freight tracking use cases typically require low data rates, but require wide range and reliable location information.

[0087] New RAT systems including NR use OFDM transmission schemes or similar transmission schemes. New RAT systems may follow OFDM parameters different from those of LTE. Or, new RAT systems may follow the existing LTE / LTE-A numerology but have a larger system bandwidth (e.g., 100 MHz). Or, one cell may support multiple numerologies. That is, terminals operating with different numerologies may coexist in one cell.

[0088] A numerology corresponds to one subcarrier spacing in the frequency domain. By scaling the reference subcarrier spacing to an integer N, different numerologies can be defined.

[0089] Definition of Terms

[0090] eLTE eNB: The eLTE eNB is an evolution of the eNB that supports connectivity to the EPC and NGC.

[0091] gNB: A node that supports NR as well as linking with NGC.

[0092] New RAN: A radio access network that supports NR or E-UTRA or interworks with NGC.

[0093] Network slice: A network slice is a network defined by an operator to provide an optimized solution for a specific market scenario that dictates specific requirements with end-to-end reach.

[0094] network function: A network function is a logical node within the network infrastructure with a well-defined external interface and a well-defined functional behavior.

[0095] NG-C: A control plane interface used as the NG2 reference point between the new RAN and NGC.

[0096] NG-U: User plane interface used as the NG3 reference point between the new RAN and NGC.

[0097] Non-standalone NR: A deployment configuration in which a gNB requests an LTE eNB to an EPC as an anchor for control plane connection, or requests an eLTE eNB to an NGC as an anchor for control plane connection.

[0098] Non-independent E-UTRA: A deployment configuration in which an eLTE eNB requests a gNB from the NGC as an anchor for control plane connectivity.

[0099] User Plane Gateway: The termination point of the NG-U interface.

[0100] System in general

[0101] Figure 1 shows an example of the overall system architecture of NR to which the method proposed in this specification can be applied.

[0102] Referring to Figure 1, the NG-RAN consists of the gNB, which provides the NG-RA user plane (new AS sublayer / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol termination for the UE (user equipment).

[0103] The gNBs are interconnected via an Xn interface.

[0104] In addition, the gNB is connected to the NGC via an NG interface.

[0105] More specifically, the gNB is connected to an Access and Mobility Management Function (AMF) via an N2 interface and to a User Plane Function (UPF) via an N3 interface.

[0106] NR (New RAT) Numerology and Frame Structure

[0107] In the NR system, multiple numerologies can be supported. Here, the numerology can be defined by the subcarrier spacing and CP (Cyclic Prefix) overhead. In this case, the spacing between multiple subcarriers can be derived by scaling the spacing between the basic subcarriers to an integer N (or μ). In addition, the numerology used can be selected independently of the frequency band, even if it is assumed that very low subcarrier spacing is not used at very high carrier frequencies.

[0108] In addition, NR systems can support a variety of frame structures according to multiple numerologies.

[0109] Below, we will explain the Orthogonal Frequency Division Multiplexing (OFDM) numerology and frame structure that can be considered in an NR system.

[0110] The multiple OFDM numerologies supported in the NR system can be defined as shown in Table 1.

[0111] [Table 1]

[0112] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, a 15kHz SCS supports wide areas in traditional mobile phone bands, a 30kHz / 60kHz SCS supports dense-urban, lower latency and wider carrier bandwidth, and a 60kHz or higher SCS supports bandwidths larger than 24.25GHz to overcome phase noise.

[0113] 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 2 below. FR2 can also refer to millimeter wave (mmW).

[0114] [Table 2]

[0115] As described above, the numerical values ​​of the frequency range of the NR system may be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz as shown in Table 3 below. That is, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, the frequency band of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included in FR1 may include an unlicensed band. The unlicensed band can be used for various purposes, and can also be used for communication for vehicles (e.g., autonomous driving).

[0116] [Table 3]

[0117] In relation to the frame structure in the NR system, the sizes of the various fields in the time domain are It is expressed as a multiple of the time unit JPEG0007656722000016.jpg13106, where: JPEG0007656722000017.jpg1395, JPEG0007656722000018.jpg1397. Downlink and uplink transmission is JPEG0007656722000019.jpg1491 radio frames. Here, each radio frame is JPEG0007656722000020.jpg is made up of 10 subframes with a duration of 12112. In this case, there may be one set of frames for the uplink and one set of frames for the downlink.

[0118] FIG. 2 shows the relationship between uplink and downlink frames in a wireless communication system in which the method proposed herein can be applied.

[0119] As shown in FIG. 2, the transmission of uplink frame number i from a terminal (user equipment, UE) starts from the start of the corresponding downlink frame at the terminal. Must start before JPEG0007656722000021.jpg12100.

[0120] For numerology μ, a slot is a subframe JPEG0007656722000022.jpg1398 is numbered in increasing order and JPEG0007656722000023.jpg1394 is numbered in increasing order. One slot is JPEG0007656722000024.jpg consists of 1391 consecutive OFDM symbols. JPEG0007656722000025.jpg15107 is determined by the numerology and slot configuration used. JPEG0007656722000026.jpg1197 starts in the same subframe as the OFDM symbol It is time-aligned with the start of JPEG0007656722000027.jpg1298.

[0121] Not all terminals can transmit and receive simultaneously, which means that not all OFDM symbols in a downlink slot or an uplink slot can be used.

[0122] Table 4 shows the number of OFDM symbols per slot in normal CP. JPEG0007656722000028.jpg1494, Number of slots per wireless frame JPEG0007656722000029.jpg1475, Number of slots by subframe JPEG0007656722000030.jpg1584, and Table 5 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0123] [Table 4]

[0124] [Table 5]

[0125] An example of a frame structure in an NR system is shown in Figure 3. Figure 8 is for convenience of explanation only and does not limit the scope of this specification.

[0126] In the case of Table 5, In the case of JPEG0007656722000033.jpg1293, that is, an example where the subcarrier spacing (SCS) is 60 kHz, referring to Table 7, one subframe (or frame) can include three slots, and one subframe = {1, 2, 4} slots shown in FIG. 3 is an example, and the number of slots that can be included in one subframe can be defined as shown in Table 4.

[0127] A mini-slot may also consist of 2, 4 or 7 symbols, and may consist of more or less symbols.

[0128] In relation to physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. can be considered.

[0129] Hereinafter, the physical resources that can be considered in an NR system will be described in detail.

[0130] First, with respect to antenna ports, an antenna port is defined such that the channel on which a symbol on an antenna port is carried can be inferred from the channel on which another symbol on the same antenna port is carried. If the large-scale properties of the channel on which a symbol on one antenna port is carried can be inferred from the channel on which a symbol on the other antenna port is carried, the two antenna ports can be said to be in a quasi co-located (QC / QCL) relationship. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0131] FIG. 4 illustrates an example of a resource grid that may be supported in a wireless communication system in accordance with some embodiments herein.

[0132] Referring to Figure 4, the resource grid is JPEG0007656722000034.jpg is described as being composed of 1286 subcarriers, and one subframe is composed of 14·2μ OFDM symbols, but is not limited to this example.

[0133] In an NR system, the transmitted signal is JPEG0007656722000035.jpgOne or more resource grids consisting of 1389 subcarriers, and This is illustrated by the OFDM symbols in JPEG0007656722000036.jpg1584, where: JPEG0007656722000037.jpg1484. JPEG0007656722000038.jpg1277 indicates the maximum transmission bandwidth, which can differ not only with numerology but also between uplink and downlink.

[0134] In this case, as shown in Figure 6, One resource grid is set for JPEG0007656722000039.jpg1382 and antenna port p.

[0135] FIG. 5 shows the slot structure of an NR frame to which the method proposed herein can be applied.

[0136] A slot includes multiple symbols in the time domain. For example, in the case of normal CP, one slot includes seven symbols, and in the case of extended CP, one slot includes six symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) is defined as multiple (P) consecutive RBs in the frequency domain and may correspond to one numerology (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication is performed via the activated BWPs, and only one BWP may be activated for one terminal. Each element in the resource grid is called a resource element (RE), and one complex symbol may be mapped to it.

[0137] FIG. 6 shows an example of a resource grid by antenna port and numerology to which the method proposed in this specification can be applied.

[0138] Each element of the resource grid for numerology μ and antenna port p is called a resource element, and is represented by an index pair It is uniquely identified by JPEG0007656722000040.jpg1499, where: JPEG0007656722000041.jpg1295 is the index in the frequency domain, JPEG0007656722000042.jpg1390 refers to the position of a symbol in a subframe. When referring to a resource element in a slot, the index pair JPEG0007656722000043.jpg1393 is used, where The image is JPEG0007656722000044.jpg12101.

[0139] Numerology μ and resource element for antenna port p JPEG0007656722000045.jpg1389 is a complex value JPEG0007656722000046.jpg1396. If there is no risk of confusion, or if a particular antenna port or numerology is not specified, the indices p and μ can be dropped, so that the complex value is JPEG0007656722000047.jpg1486 or Sometimes it becomes JPEG0007656722000048.jpg1284.

[0140] In addition, a physical resource block is a frequency domain JPEG0007656722000049.jpg is defined as 1278 contiguous subcarriers.

[0141] Point A serves as a common reference point for the resource block grid and can be obtained as follows:

[0142] - offsetToPointA for the PCell downlink represents the frequency offset between Point A and the lowest subcarrier of the lowest resource block overlapping with the SS / PBCH block used by the UE for initial cell selection, expressed in resource block units assuming a subcarrier spacing of 15 kHz for FR1 and a subcarrier spacing of 60 kHz for FR2;

[0143] -absoluteFrequencyPointA represents the frequency-location of Point A expressed as ARFCN (absolute radio-frequency channel number).

[0144] Common resource blocks are numbered from 0 upwards in the frequency domain relative to the spacing of subcarriers.

[0145] Subcarrier The center of subcarrier 0 of common resource block 0 for JPEG0007656722000050.jpg1369 coincides with "Point A". Common resource block number in the frequency domain JPEG0007656722000051.jpg1268 and subcarrier The resource element (k, l) for JPEG0007656722000052.jpg1294 can be given as Equation 1 below.

[0146] [Number 1] JPEG0007656722000053.jpg1691

[0147] During the ceremony, JPEG0007656722000054.jpg1466 is JPEG0007656722000055.jpg1380 can be defined relative to Point A so that it corresponds to a subcarrier centered on Point A. A physical resource block is a set of 0 to 16 bits in the bandwidth part (BWP). JPEG0007656722000056.jpg1284 is numbered, JPEG0007656722000057.jpg1175 is the BWP number. JPEG0007656722000058.jpg1287 and common resource blocks The relationship between JPEG0007656722000059.jpg1282 can be given by the following Equation 2:

[0148] [Number 2] JPEG0007656722000060.jpg1394

[0149] During the ceremony, JPEG0007656722000061.jpg1479 could be the common resource block where the BWP begins relative to common resource block 0

[0150] Physical Channels and General Signaling

[0151] Figure 7 illustrates physical channels and general signal transmission. In a wireless communication system, a terminal receives information from a base station via a downlink (DL), and transmits information to the base station via an uplink (UL standard). Information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist according to the type / application of the information transmitted and received.

[0152] When the terminal is powered on or newly enters a cell, the terminal performs an initial cell search such as synchronizing with the base station (S701). To this end, the terminal can receive 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. Then, 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) in the initial cell search stage to check the state of the downlink channel.

[0153] After completing the initial cell search, the terminal can obtain more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on information carried on the PDCCH (S702).

[0154] Meanwhile, when the terminal first connects to the base station or there are no radio resources for signal transmission, the terminal can perform a random access procedure (RACH) to the base station (S703 to S706). To this end, the terminal can transmit a specific sequence as a preamble through a physical random access channel (PRACH) (S703 and S705) and receive a response message (RAR Random Access Response) to the preamble through a PDCCH and a corresponding PDSCH. In the case of a contention-based RACH, the terminal can further perform a contention resolution procedure (S706).

[0155] After performing the above-mentioned procedures, the terminal may then perform PDCCH / PDSCH reception (S707) and Physical Uplink Shared Channel (PUSCH / Physical Uplink Control Channel (PUCCH) transmission (S708) as a general uplink / downlink signal transmission procedure. In particular, the terminal may receive downlink control information (DCI) via the PDCCH. Here, the DCI includes control information such as resource allocation information of the terminal, and may be applied in different formats depending on the purpose of use.

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

[0157] NR PUCCH format

[0158] NR supports a total of five PUCCH formats, which are divided into short PUCCH and long PUCCH according to duration. Table 6 shows the five PUCCH formats.

[0159] Shot duration PUCCH

[0160] -Format 0:for UCI up to 2 bits, with multiplexing

[0161] -Format 2:for UCI of more than 2 bits, no multiplexing

[0162] Long duration PUCCH

[0163] -Format 1:for UCI of up to 2 bits, with multiplexing

[0164] -Format 3:for UCI of more than 2 bits, no multiplexing

[0165] -Format 4:for UCI of more than 2 bits, with multiplexing

[0166] [Table 6]

[0167] PUCCH coverage enhancement(CE)

[0168] In relation to PUCCH enhancements, the following schemes may be considered for improving PUCCH coverage.

[0169] -DMRS-less PUCCH: Design details for DMRS-less PUCCH are being further studied (e.g., sequence based PUCCH transmission, vs. reusing the Rel-15 scheme to transmit UCI without DMRS)

[0170] - Rel-16 PUSCH-repetition-Type-B, same as PUCCH repetition for minimum UCI <= 11 bits

[0171] -(explicit or implicit)dynamic PUCCH repetition factor indication

[0172] -DMRS bundling across PUCCH repetitions: Studies include transmitting a subset of PUCCH repetitions without DMRS for at least UCI <= 11 bits

[0173] DMRS bundling for PUCCH repetitions may be considered together with DMRS bundling for PUSCH repetitions.

[0174] The PUCCH repetitions scheme must describe the resources used by the PUSCH to meet the throughput target and is compared to the Rel-15 / 16 PUCCH repetitions.

[0175] Table 7 shows the PUCCH coverage enhancement techniques under consideration.

[0176] [Table 7]

[0177] PUSCH repetition

[0178] PUSCH repetition types A and B are introduced in NR Rel-15 / 16, and transmission is performed as follows depending on the PUSCH repetition type.

[0179] PUSCH repetition Type A

[0180] FIG. 8 shows an example of PUSCH repetition type A. PUSCH repetition type A is slot-based repetition, and as shown in FIG. 8, repetition is performed with the same PUSCH transmission start symbol position and PUSCH transmission symbol length for each slot. At this time, if there is an invalid symbol that cannot be used for PUSCH transmission among the symbol resources constituting a specific PUSCH repetition, the transmission of the PUSCH repetition is dropped and not performed. That is, when a total of four PUSCH repetition transmissions of Rep0, Rep1, Rep2, and Rep3 are performed, if an invalid symbol is included in the symbol resource constituting Rep1, the transmission of Rep1 is dropped and only the transmissions of Rep0, Rep2, and Rep3 are performed. Therefore, the number of repetitions actually performed may be smaller than the number of repetitions set.

[0181] In the case of PUSCH repetition type A, frequency hopping is configured in the terminal by higher layer parameters.

[0182] One of the following two frequency hopping modes can be set:

[0183] - Intra-slot frequency hopping applicable to single slot PUSCH transmission and multi-slot PUSCH transmission

[0184] -Inter-slot frequency hopping applicable to multi-slot PUSCH transmission

[0185] PUSCH repetition type B

[0186] 9 shows an example of PUSCH repetition type B. In PUSCH repetition type B, repetition is performed in units of the symbol length by which the PUSCH is actually transmitted.

[0187] That is, as shown in (a) of FIG 9, when the PUSCH is transmitted with 10 symbols, PUSCH repetition is performed in units of 10 consecutive symbols. Repetition that determines the PUSCH repetition transmission time resource without considering slot boundaries, invalid symbols, etc. is called nominal repetition.

[0188] However, in the case of actual PUSCH repetition, one PUSCH cannot be transmitted on a slot boundary. When PUSCH transmission includes a slot boundary, two actual repetitions are performed with the slot boundary as a boundary, as shown in FIG. 9(b). Also, one PUSCH transmission can only be performed by consecutive symbols. When an invalid symbol exists in a time resource where a PUSCH repetition must be transmitted, an actual repetition is configured using consecutive symbols with the invalid symbol as a boundary. For example, when symbols #0 to #9 constitute one nominal repetition and symbols #3 to #5 are invalid symbols, symbols #0 to #2 and symbols #6 to #9 excluding the invalid symbol each constitute one actual repetition.

[0189] If one actual repetition resource includes a symbol that cannot be used for PUSCH transmission (eg, a DL symbol indicated by DCI format 2_0), the actual repetition transmission is dropped and not performed.

[0190] For PUSCH repetition type B, the UE is configured for frequency hopping by higher layer parameters.

[0191] The frequency hopping mode for Type2 configured PUSCH transmission follows the setting of the activating DCI format. One of two frequency hopping modes can be set.

[0192] -inter-repetition frequency hopping

[0193] -inter-slot frequency hopping

[0194] DMRS for PDSCH / PUSCH

[0195] The DMRS for the PDSCH / PUSCH consists of a front load DMRS and an additional DMRS.

[0196] -front load DMRS

[0197] The transmission time resource location of the front load DMRS is determined by the following factors:

[0198] The mapping type varies depending on whether the mapping type of the Data channel (PDSCH mapping type / PUSCH mapping type) is Type A or Type B (slot based or non-slot based), and is set by RRC.

[0199] In the case of slot based transmission, the transmission start OFDM symbol position of the front load DMRS may be the third or fourth OFDM symbol of the data transmission resource, and an indication as to whether the transmission start OFDM symbol position is the third or fourth OFDM symbol is transmitted via the PBCH.

[0200] The front load DMRS is composed of one or two consecutive OFDM symbols, and the number of OFDM symbols (whether it is one or two) is configured by the RRC.

[0201] There are two types of mapping types in the transmission OFDM symbol resource of the front load DMRS (Type 1 or Type 2), and information regarding the applicable type is configured in the RRC. Type 1 supports four or eight antenna ports depending on whether the DMRS symbol length is one or two using F-CDM (CDM in frequency domain), T-CDM (CDM in time domain), and / or FDM techniques. Type 2 supports six or twelve antenna ports depending on whether the DMRS symbol length is one or two using F-CDM, T-CDM, and / or FDM techniques.

[0202] -Additional DMRS

[0203] The number of additional DMRSs is determined to be 0, 1, 2, or 3. The maximum number of additional DMRSs to be transmitted is determined by RRC, and the number of additional DMRSs actually transmitted within each maximum number of DMRSs and the transmission OFDM symbol position are determined according to the length of the OFDM symbol in which data is transmitted. The symbol locations of the front load DMRS and additional DMRS according to the data symbol length are as shown in Figure 10.

[0204] The number of OFDM symbols and the mapping type of each additional DMRS are determined to be the same as the number of OFDM symbols and the mapping type of the front load DMRS.

[0205] FIG. 10 shows an example of DMRS positions according to mapping type and the number of OFDM symbols.

[0206] The location and number of symbols of the current PUSCH DMRS vary depending on the length of the symbol used to transmit the PUSCH. In particular, when PUSCH repetition type B is used, the location and number of symbols of the DMRS are determined based on the actual repetition length of the PUSCH. In this case, the location of the DMRS changes for each PUSCH repetition.

[0207] According to the RAN4 Liaison Statement, in order to perform joint channel estimation, transmission must be performed on the same physical resource block (PRB). That is, when joint channel estimation is configured, inter-slot frequency hopping cannot be performed according to the existing rule. Therefore, an enhancement of inter-slot frequency hopping is needed.

[0208] Next, the technology for frequency hopping of PUSCH in subclause 6.3.1 and 6.3.2 of 3GPP technical specification (TS) 38.214 is described.

[0209] Frequency hopping for PUSCH repetition type A

[0210] In the case of PUSCH repetition type A, a terminal (user equipment, UE) can configure frequency hopping by a higher layer parameter frequencyHopping-ForDCIFormat0_2 of PUSCH-Config for PUSCH transmission scheduled with DCI Format 0_2, by frequencyHopping provided in PUSCH-Config for PUSCH transmission scheduled with DCI format other than 0_2, and by frequencyHopping provided in configureGrantConfig for configured PUSCH transmission. One of two frequency hopping modes can be configured.

[0211] - Intra-slot frequency hopping applicable to single slot and multi-slot PUSCH transmission

[0212] -Inter-slot frequency hopping applicable to multi-slot PUSCH transmission

[0213] In the case of resource allocation type 2, the terminal can transmit the PUSCH without frequency hopping.

[0214] In the case of resource allocation type 1, depending on whether transform precoding for PUSCH transmission is activated, the terminal may perform PUSCH frequency hopping if the frequency hopping field in the corresponding detected DCI format or random access response UL grant is set to 1, or if the upper layer parameter frequencyHoppingOffset is provided for Type 1 PUSCH transmission with configured grant.

[0215] Otherwise, PUSCH frequency hopping may not be performed. If frequency hopping is activated for PUSCH, RE mapping may be defined in a predefined standard (eg, 3GPP TS 38.211, clause 6.3.1.6).

[0216] In case of PUSCH scheduled by RAR UL grant, fallbackRAR UL grant or DCI format 0_0 with cyclic redundancy check (CRC) scrambled by temporary cell (TC)-radio network temporary identifier (RNTI), the frequency offset can be obtained as described in the predefined standard (3GPP TS 38.213, clause 8.3).

[0217] For PUSCH scheduled with DCI format 0_0 / 0_1 or PUSCH based on Type 2 configured UL grant activated with DCI format 0_0 / 0_1 and resource allocation type 1, the frequency offset can be configured by the higher layer parameter frequencyHoppingOffsetLists of PUSCH-Config. For PUSCH scheduled with DCI format 0_2 or PUSCH based on Type 2 configured UL grant activated with DCI format 0_2 and resource allocation type 1, the frequency offset can be configured by the higher layer parameter frequencyHoppingOffsetLists-ForDCIFormat0_2 of pusch-Config.

[0218] -If the size of the active BWP is less than 50 PRB, one of two higher layer configured offsets may be indicated in the UL grant.

[0219] -If the size of the active BWP is 50 PRB or more, one of four higher layer configured offsets can be indicated in the UL grant.

[0220] For PUSCH based on a Type 1 configured UL grant, the frequency offset is provided by the higher layer parameter frequencyHoppingOffset in rrc-ConfiguredUplinkGrant.

[0221] In the case of frequency hopping within a slot, the starting RB for each hop is given by Equation 3.

[0222]

number

[0223] where i=0 and i=1 are the first and second hops, respectively. JPEG0007656722000065.jpg712 is a starting RB in the UL BWP and is calculated using the resource block assignment information of resource allocation type 1. JPEG0007656722000066.jpg513 is the frequency offset in RBs between both frequency hops. The number of symbols in the first hop is The number of symbols in the second hop is given by JPEG0007656722000067.jpg821. JPEG0007656722000068.jpg1871, where: JPEG0007656722000069.jpg715 may be the length of a PUSCH transmission in OFDM symbols of one slot.

[0224] In the case of inter-slot frequency hopping, the slot The starting RB in JPEG0007656722000070.jpg55 is given by Equation 4.

[0225]

number

[0226] Where: JPEG0007656722000072.jpg55 is the current slot number in the radio frame where multi-slot PUSCH transmission can occur, JPEG0007656722000073.jpg510 may be a starting RB in the UL BWP calculated in the resource block allocation information of resource allocation type 1. JPEG0007656722000074.jpg513 may be the frequency offset in RBs between both frequency hops.

[0227] Frequency hopping for PUSCH repetition type B

[0228] For PUSCH repetition type B, the terminal can be configured for frequency hopping by the higher layer parameter frequencyHopping-ForDCIFormat0_2 of pusch-Config for PUSCH transmission scheduled with DCI Format 0_2, by frequencyHopping-ForDCIFormat0_1 provided in pusch-Config for PUSCH transmission scheduled with DCI format 0_1, and by frequencyHopping-PUSCHRepTypeB provided in rrc-ConfiguredUplinkGrant for Type 1 configured PUSCH transmission. The frequency hopping mode for Type 2 configured PUSCH transmission follows the configuration of the activating DCI format. One of two frequency hopping modes can be configured.

[0229] -Inter-repetition frequency hopping

[0230] -Inter-slot frequency hopping

[0231] In the case of resource allocation type 1, depending on whether transform precoding for PUSCH transmission is activated, if the frequency hopping field is set to 1 in the detected DCI format or if the higher layer parameter frequencyHopping-PUSCHRepTypeB for Type 1 PUSCH transmission with configured grant is provided, the UE can perform PUSCH frequency hopping. Otherwise, PUSCH frequency hopping is not performed. If frequency hopping is activated for PUSCH, RE mapping is defined in a predefined standard (e.g., 3GPP TS 38.211, clause 6.3.1.6).

[0232] For PUSCH scheduled with DCI format 0_1 ​​or PUSCH based on a Type 2 configured UL grant activated with DCI format 0_1 ​​and resource allocation type 1, the frequency offset is configured by the higher layer parameter frequencyHoppingOffsetLists of pusch-Config. For PUSCH scheduled with DCI format 0_2 or PUSCH based on a Type 2 configured UL grant activated with DCI format 0_2 and resource allocation type 1, the frequency offset is configured by the higher layer parameter frequencyHoppingOffsetLists-ForDCIFormat0_2 of pusch-Config.

[0233] -If the size of the active BWP is less than 50 PRB, one of the two higher layer configured offsets is indicated in the UL grant.

[0234] -If the size of the active BWP is 50 PRB or more, one of the four higher layer configured offsets is indicated in the UL grant.

[0235] For PUSCH based on a Type 1 configured UL grant, the frequency offset is provided by the higher layer parameter frequencyHoppingOffset in rrc-ConfiguredUplinkGrant.

[0236] In the case of inter-repetition frequency hopping, the starting RB in the n-th nominal repetition is given by Equation 5.

[0237]

number

[0238] Where: JPEG0007656722000076.jpg612 is the starting RB in the UL BWP calculated in the resource block assignment information of resource allocation type 1, JPEG0007656722000077.jpg715 may be the frequency offset in RBs between both frequency hops.

[0239] In the case of inter-slot frequency hopping, the starting RB in a slot follows the starting RB of inter-slot frequency hopping for PUSCH repetition Type A in the predefined standard (3GPP TS 38.214, clause 6.3.1).

[0240] As described above, in the conventional inter-slot frequency hopping, which of the two PRBs is used to transmit a corresponding transmission occasion is determined according to an index within a subframe of a slot in which the PUSCH or PUCCH is transmitted, which contradicts the conditions for performing joint channel estimation.

[0241] Therefore, this specification proposes a method of inter-slot bundling and inter-slot frequency hopping for joint channel estimation suitable for coverage enhancement, including the above-mentioned problems.

[0242] Specifically, this specification proposes a method for determining / setting / defining a time-domain window size for inter-slot bundling (hereinafter, referred to as the first embodiment), and a method for setting / defining an inter-slot frequency hopping boundary for inter-slot bundling (hereinafter, referred to as the second embodiment).

[0243] It will be appreciated that the embodiments described herein are divided for the convenience of explanation, and that some methods and / or configurations of one embodiment may be replaced with methods and / or configurations of another embodiment, or may be combined with each other.

[0244] Although this specification is described in terms of the transmission of a physical uplink shared channel (PUSCH), the proposed method herein can also be applied to the transmission of other channels, such as the physical uplink control channel (PUCCH), the physical downlink shared channel (PDSCH) and the physical downlink control channel (PDCCH), as well as the PUSCH.

[0245] The terms "slot," "subframe," "frame," etc. referred to in the embodiments described herein are specific examples of a certain time unit used in a wireless communication system. That is, in application of the method proposed in the present specification, the time unit, etc. may be substituted for other time units applied in other wireless communication systems.

[0246] In this specification, L1 signaling refers to DCI-based dynamic signaling between a base station and a terminal, and L2 signaling refers to radio resource control (RRC) / medium access control-control element (MAC-CE)-based higher layer signaling between a base station and a terminal.

[0247] The above contents (3GPP system, frame structure, NR system, etc.) can be applied in combination with the method proposed in this specification described later, and / or can be supplemented to clarify the technical features of the method proposed in this specification.

[0248] Additional advantages, objects and features of the specification will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art upon examination of the following or may be learned by practice of the specification. The objectives and other advantages of the specification will be realized and attained by the structure particularly pointed out in the description and claims hereof as well as the appended drawings.

[0249] As used herein, "A or B" can mean "A only," "B only," or "both A and B." In other words, as used herein, "A or B" can be interpreted as "A and / or B." For example, as used herein, "A, B or C" can mean "A only," "B only," "C only," or "any combination of A, B and C."

[0250] As used herein, a slash ( / ) or a comma can mean "and / or." For example, "A / B" can mean "A and / or B." Thus, "A / B" can mean "A only," "B only," or "both A and B." For example, "A, B, C" can mean "A, B, or C."

[0251] In this specification, "at least one of A and B" can mean "A only," "B only," or "both A and B." In addition, in this specification, the expressions "at least one of A or B" and "at least one of A and / or B" may be interpreted similarly to "at least one of A and B."

[0252] In addition, in this specification, "at least one of A, B and C" can mean "A only," "B only," "C only," or "any combination of A, B and C." Furthermore, "at least one of A, B or C" and "at least one of A, B and / or C" can mean "at least one of A, B and C."

[0253] In addition, parentheses used in this specification may mean "for example." Specifically, when "control information (PDCCH)" is displayed, "PDCCH" may be proposed as an example of "control information." In other words, "control information" in this specification is not limited to "PDCCH," and "PDDCH" may be proposed as an example of "control information." Also, when "control information (i.e., PDCCH)" is displayed, "PDCCH" may be proposed as an example of "control information."

[0254] Technical features described individually in one drawing in this specification may be realized individually or simultaneously.

[0255] The following drawings are created to explain a specific example of the present specification. The names of specific devices and names of specific signals / messages / fields described in the drawings are presented for illustrative purposes only, and the technical features of the present specification are not limited to the specific names used in the following drawings.

[0256] The effects obtained from a specific example of the present specification are not limited to the effects described. For example, there are various technical effects that a person having ordinary skill in the related art can understand or derive from the present specification. Thus, the specific effects of the present specification are not limited to those explicitly described in the present specification, and may include various effects that can be understood or derive from the technical features of the present specification.

[0257] First, the first embodiment will be described.

[0258] First embodiment

[0259] In this embodiment, a method for determining / setting / defining a time-domain window size for inter-slot bundling will be described.

[0260] The methods described below are divided for the convenience of explanation, and it goes without saying that the components of one method can be replaced with the components of another method or can be mutually combined and applied.

[0261] The method proposed in this specification is described assuming PUSCH repetition, but can also be applied to PUCCH repetition in the same manner.

[0262] The definition of the time-domain window size for inter-slot bundling is under discussion in RAN1. Here, inter-slot bundling means continuous and / or non-continuous transmission occasions in which phase and / or power continuity are guaranteed for the purpose of joint channel estimation for PUSCH / PUCCH transmitted by a terminal with repetition setting. In other words, inter-slot bundling means continuous and / or non-continuous transmission occasions in which the same phase and transmission power are guaranteed for PUSCH / PUCCH transmitted by a terminal with repetition setting. And / or, inter-slot bundling may be referred to as DMRS bundling.

[0263] And / or, the time-domain window size for inter-slot bundling / inter-slot bundling may be a value reported according to the capability of the terminal or according to the channel state of the terminal. And / or, the time-domain window size for inter-slot bundling / inter-slot bundling may be a value instructed to the base station (e.g., gNB). If the base station is instructed, the following method may be considered.

[0264] (Method 1-1) -Instruction by RRC / MAC-CE / DCI

[0265] The time-domain window size may be a UE-specific value depending on the channel of the terminal, and / or may be a cell-specific value for resource management of a base station (e.g., gNB).

[0266] When the time-domain window size is a cell-specific value, the time-domain window size may be a value that is semi-statically assigned to radio resource control (RRC) / medium access control-control element (MAC-CE), etc.

[0267] When the time-domain window size is a UE-specific value, the terminal may configure or receive a candidate list of the time-domain window using RRC / MAC-CE, etc., and / or the terminal may be assigned / instructed to use a value from the list corresponding to the terminal via downlink control information (DCI).

[0268] And / or the time-domain window and / or the time-domain window size are received / configured via RRC signaling.

[0269] And / or the time-domain window and / or the time-domain window size can be indicated only in the DCI for the purpose of dynamic indication, and / or 2^N time-domain windows can be indicated using the N bit DCI by prior agreement.

[0270] (Method 1-2) -Repetition size based on instructions / settings / decisions

[0271] The time-domain window may be indicated / set / determined based on the number of repetitions, for example, the time-domain window may be determined based on the time duration of consecutive slots of the repetitions, in order to indicate a relatively small time-domain window for low repetitions and a relatively large time-domain window for high repetitions.

[0272] For example, if repetition is specified N times, then a pre-agreed value M will result in JPEG0007656722000078.jpg714 or The time-domain window may be indicated by a value such as JPEG0007656722000079.jpg613. Here, M may be indicated to the terminal via RRC / MAC-CE / DCI, etc. Alternatively, M may be a UE-specific value or a Cell-specific value.

[0273] (Method 1-3) - Based on total number of slots

[0274] TBoMS (transmit block over multiple slots) is currently under discussion in the coverage enhancement of RAN1. TBoMS means mapping one transport block (TB) to multiple slots, and / or TBoMS means a bundle of multiple transmission occasions, or one transmission can be treated as one transmission occasion and correspond to multiple slots.

[0275] In this case, the time-domain window for joint channel estimation / inter-slot bundling / DMRS bundling can be specified in the same manner as in the TBoMS unit, and / or the time-domain window is specified by calculation using the number of slots of the TBoMS.

[0276] (Method 1-4) -Divide / instruct / set based on frequency resources

[0277] In order to ensure smooth operation in terms of resource management of a base station (e.g., gNB), different joint channel estimation windows (or time domain windows) are assigned according to frequency resources.

[0278] For example, different time-domain windows and / or time-domain window sizes and / or time-domain window values ​​may be indicated / set / defined according to FR1 (Frequency Range 1) and FR2 (Frequency Range 2).And / or, by further subdividing this, different joint channel estimation windows may be set according to bands.

[0279] And / or, the setting of the time-domain window according to the frequency can be performed implicitly or explicitly at the same time as the setting of the uplink-bandwidth part (UL-BWP) of the UE. For example, it can be considered that the UL-BWP includes information on the time-domain window for joint channel estimation / inter-slot bundling / DMRS bundling.

[0280] And / or, in order to multiplex together terminals having the same hopping pattern, the time-domain window is partitioned / indicated / set based on frequency resources.

[0281] (Method 1-5) -Adaptive structure based on TDD structure

[0282] Other number of time-domain windows may be set based on the slot format configuration of the terminal. That is, it may be set according to the number of downlink, flexible, and uplink slots in a subframe. This may be a value based on the slot format set by radio resource control (RRC), or may be included in and indicated by a value indicated by DCI.

[0283] Second embodiment

[0284] In this embodiment, a method for setting / defining inter-slot frequency hopping boundaries for inter-slot bundling will be described.

[0285] The methods described below are divided for the convenience of explanation, and it goes without saying that the components of one method can be substituted for the components of another method or can be mutually combined and applied.

[0286] The UE may be configured with inter-slot bundling / DMRS bundling that performs joint channel estimation for channel estimation performance, and / or the UE may indicate to the base station (e.g., gNB) that inter-slot bundling / DMRS bundling is not configured and transmit while maintaining phase, power, timing advance, etc. across multiple slots for the purpose of inter-slot bundling / DMRS bundling.

[0287] And / or, the UE may be configured to perform inter-slot frequency hopping for the purpose of channel diversity gain, etc. In this case, according to the existing inter-slot frequency hopping rule, one of two PRBs is selected for transmission depending on whether the slot index in a subframe is odd or even. This contradicts the conditions for joint channel estimation. That is, the characteristics of transmission may change in the time domain window.

[0288] Therefore, an enhancement to this is necessary, and the second embodiment proposes the following method. Hereinafter, in this specification, the "time domain window" may be referred to as the "CH window". And / or, in this specification, the terms "boundary", "interval" and "length" may be applied interchangeably.

[0289] (Method 2-1) - Hopping interval and CH window are always determined the same

[0290] The UE determines that the time domain window for joint channel estimation / inter-slot bundling / DMRS bundling set by the above method is the same as the frequency hopping boundary. As a method for doing so, the following can be considered. If the time domain window for joint channel estimation / inter-slot bundling / DMRS bundling is W, the resource block (RB) (or starting RB) of the transmission occasion can be determined by replacing Equations 4 to 5 of a predefined standard (e.g., 3GPP TS 38.214, subclause 6.3.1, 6.3.2) with Equation 6.

[0291]

number

[0292] Here, if the time domain window W is set by the above-mentioned method, the value is applied, and if not set, RB is determined / calculated based on W=1. And / or, the method is applied when the time domain window W is cell-specific.

[0293] And / or, W may denote the size of a time domain window, for example, W may be set in units of slots, and / or W may be set by the number of slots.

[0294] (Method 2-2) - Set the hopping interval to a multiple of the CH window size

[0295] Unlike the above, the time domain window W may be a UE-specific value. That is, when W is different between different terminals in a cell, a method of adjusting the frequency hopping boundary may be considered for the convenience of multi-user resource management of a base station (e.g., gNB).

[0296] In this case, a value W2 for determining a hopping boundary of a terminal for which bundling is instructed in Cell-specific is additionally provided, and / or W2 may be instructed to the terminal by RRC / MAC-CE / DCI, etc., and / or, if W2 is provided as a single value, it is provided in the RRC connection phase of the terminal.

[0297] And / or, if the frequency hopping boundary of the terminal is set to a multiple of the time domain window, the corresponding multiple can be given. For example, if the time domain window of the terminal is W, m is given, and the pre-agreed mW=W 2 In this way, the frequency hopping boundary can be set / defined or obtained. 2 A physical resource block (PRB) (or starting RB) of a transmission occasion for frequency hopping of a given UE is defined as Equation 7.

[0298]

number

[0299] Hereinafter, in this specification, the first embodiment, the second embodiment, or embodiments other than the first embodiment will be described from the standard viewpoint.

[0300] The contents of the present specification may supplement all or part of the above-described embodiments (i.e., the first and second embodiments), may be applied together with all or part of the embodiments, or may be applied in place of all or part of the embodiments. Alternatively, the contents of the present specification may be applied separately from the first and second embodiments.

[0301] In this specification, the "first embodiment and second embodiment" may mean including the following proposed contents / methods.

[0302] In relation to inter-slot frequency hopping and DMRS bundling, an agreement shall be made in RAN1#107-e as shown in Table 8, and the remaining FFS points shall also be discussed.

[0303] [Table 8]

[0304] First, the frequency hopping pattern determination needs to be defined. Although the existing PUSCH and PUCCH are both based on the same rules, there are differences in the contents described in the standard documents.

[0305] For frequency hopping of the PUSCH, the start RB is applied when the slot index is an even number, and an offset to the start RB is applied when the slot index is an odd number.

[0306] For PUCCH, if the slot index is even, startingPRB is applied, and if it is odd, secondHopPRB is applied. That is, the frequency hop is determined depending on whether the physical slot index is even or odd. The frequency hop is determined depending on the physical slot index, and it is most preferable to extend the same rule for simplicity.

[0307] In addition, if the hopping boundaries between terminals are not aligned, all terminals performing frequency hopping occupy two RBs, which is undesirable in terms of resource management. That is, it is preferable to align the hopping boundaries between terminals in consideration of multi-user multiplexing. This is possible when the hopping pattern is determined by a physical slot index.

[0308] Therefore, according to the method proposed herein, the frequency hopping pattern for inter-slot frequency hopping can be determined only by the physical slot index.

[0309] Secondly, the frequency hopping patterns of PUCCH and PUSCH must be determined based on a unified method. Defining the frequency hopping pattern only by the physical slot index may be for multi-user multiplexing. For this, the hopping boundary between users must match. However, since the time domain window (TDW) of PUSCH and PUCCH is set separately, the hopping window (or TDW) of PUCCH and PUSCH may be different. To solve this, multi-user multiplexing is achieved by not pairing different channels with each other. That is, PUSCH and PUCCH may not be paired with each other.

[0310] Therefore, according to the proposed method herein, the determination of the frequency hopping pattern for PUCCH and PUSCH is based on the same rule, and / or the size of each frequency hopping window for PUSCH and PUCCH is the same or different according to each configuration.

[0311] It has been agreed that separate RRC configurations are supported for the hopping interval and the length of the set TDW. In consideration of this, a specific method for determining frequency hop of the PUSCH is as follows.

[0312] When inter slot frequency hopping is configured and the hopping interval for PUSCH W (e.g., HoppingIntervalPUSCH) is configured, JPEG0007656722000083.jpg The resource block (RB) of the transmission occasion in the 76th slot is set according to Equation 8. That is, depending on whether a value obtained by dividing the slot index by a hopping interval for joint channel estimation of PUSCH is even or odd, start RB or start RB + offset RB should be applied.

[0313] The same rule can be applied to PUCCH. That is, startingPRB and secondHopPRB may be applied depending on whether the value obtained by dividing the slot index by the hopping interval for joint channel estimation of PUCCH described in HoppingIntervalPUCCH is even or odd. In this case, if the set TDW of PUCCH is not set according to the PUCCH format, the hopping interval for joint channel estimation of PUCCH does not need to be set for each format. As mentioned above, it is not preferable to have different boundaries for each format in consideration of multi-user multiplexing. Therefore, the hopping interval of PUCCH should also be applied regardless of the format.

[0314] The last FFS point is the default terminal behavior when the hopping interval and TDW are not set but joint channel estimation and frequency hopping are activated. It is natural to think that the terminal behavior is clear because the default configured TDW value is defined even if the hopping interval and TDW length are not all set. In other words, when joint channel estimation is activated and hopping is indicated without the hopping interval and configured TDW, the default configured TDW value must be the hopping interval.

[0315] Therefore, according to the proposed method herein, when joint channel estimation is activated and frequency hopping is indicated without a hopping interval and a configured TDW, the default value for the hopping interval and the configured TDW shall be applied as the base value for the hopping interval.

[0316] And / or, according to the proposed method of this specification, the following contents may be proposed in technical standards (e.g., 3GPP TS38.214):

[0317] Frequency hopping for PUSCH repetition Type A

[0318] In the case of inter-slot frequency hopping and when PUSCH-DMRS-Bundling is not activated, While JPEG0007656722000084.jpg55, the starting RB is given by Equation 8.

[0319]

number

[0320] Where: JPEG0007656722000086.jpg55 is the current slot number in a radio frame where multi-slot PUSCH transmission can occur, JPEG0007656722000087.jpg510 is a starting RB in the UL BWP calculated from resource block assignment information of resource allocation type 1 (as described in 3GPP TS 38.214, clause 6.1.2.2.2). JPEG0007656722000088.jpg513 is the frequency offset in RBs between both frequency hops.

[0321] In the case of inter-slot frequency hopping and when PUSCH-DMRS-Bundling is activated, While JPEG0007656722000089.jpg55, the starting RB is given by Equation 9.

[0322]

number

[0323] Where: JPEG0007656722000091.jpg55 is the current slot number in a radio frame where multi-slot PUSCH transmission can occur, JPEG0007656722000092.jpg510 is a starting RB in the UL BWP calculated from resource block assignment information of resource allocation type 1 (as described in 3GPP TS 38.214, clause 6.1.2.2.2). And, JPEG0007656722000093.jpg513 is the frequency offset in RBs between both frequency hops.

[0324] Then, W is HoppingIntervalPUSCH (if configured), or W is PUSCH-TimeDomainWindowLength (if configured) if HoppingIntervalPUSCH is not configured, or W can be calculated as min([maxDMRS-BundlingDuration], M) if PUSCH-TimeDomainWindowLength is not configured and HoppingIntervalPUSCH is not configured, where M is the time duration in consecutive slots of N·K PUSCH transmissions.

[0325] Here, in the case of PUSCH transmission of PUSCH repetition Type A, N=1, and K is the number of repetitions as defined in a predefined standard (eg, 3GPP TS 38.214, clause 6.1.2.1).

[0326] For PUSCH transmission of PUSCH repetition Type B, N=1 and K is the number of nominal repetitions as defined in a predefined standard (eg, 3GPP TS 38.214, clause 6.1.2.1).

[0327] For PUSCH transmission with TB processing over multiple slots, N is the number of slots used to determine the TBS and K is the number of repetitions of the number of slots N used to determine the TBS as defined in a predefined standard (e.g., 3GPP TS 38.214, clause 6.1.2.1).

[0328] And / or, according to the method proposed in this specification, the following is proposed in technical standards (e.g., 3GPP TS38.213):

[0329] PUCCH repetition procedure

[0330] If JPEG0007656722000094.jpg712>1,

[0331] -The device is JPEG0007656722000095.jpg PUCCH transmission with UCI is repeated over 712 slots.

[0332] - JPEG0007656722000096.jpg In each of the 712 slots the PUCCH transmission has the same number of consecutive symbols as provided by nrofSymbols.

[0333] - JPEG0007656722000097.jpgThe PUCCH transmission in each of the 712 slots shall have the same first symbol as provided by startingSymbolIndex if subslotLengthForPUCCH is not provided, otherwise it shall have symbols according to mod(startingSymbolIndex, subslotLengthForPUCCH).

[0334] The UE is configured by interslotFrequencyHopping to determine whether to perform frequency hopping for PUCCH transmission in different slots.

[0335] - if the terminal is configured to frequency hop for PUCCH transmission across different slots and PUCCH-DMRS-Bundling is not activated, the terminal frequency hops on a slot-by-slot basis; and / or the terminal transmits PUSCCH starting from the first PRB provided by startingPRB in even slots and transmits PUCCH starting from the second PRB provided by secondHopPRB in odd slots; and / or the slot indicated to the terminal for the first PUCCH transmission has number 0 and the terminal Until the terminal transmits a PUCCH in slot 712, each subsequent slot is counted regardless of whether the terminal transmits a PUCCH in that slot and / or the terminal is not expected to be configured to perform frequency hopping for PUCCH transmission in the slot.

[0336] - If the terminal is configured to perform frequency hopping for transmission of PUCCH across different slots and PUCCH-DMRS-Bundling is activated, the terminal performs frequency hopping per W slots, where W is HoppingIntervalPUCCH (if configured), or W is PUCCH-TimeDomainWindowLength (if configured) if HoppingIntervalPUCCH is not configured, or W is calculated as min([maxDMRS-BundlingDuration], M) if TimeDomainWindowLength is not configured and HoppingIntervalPUCCH is not configured, where M is the time duration in consecutive slots from the first slot determined for PUCCH transmission of the PUCCH repetition to the last slot determined for PUCCH transmission of the PUCCH repetition, and / or the terminal On the first PRB provided by startingPRB in the slot where JPEG0007656722000099.jpg712 is even, Transmit PUCCH on the second PRB provided by secondHopPRB in slots where JPEG0007656722000100.jpg712 is odd. Here, JPEG0007656722000101.jpg55 is the current slot number in the radio frame. The first slot indicated to the terminal for PUCCH transmission has number 0, Each subsequent slot is counted until the terminal transmits a PUCCH in slot 712, regardless of whether the terminal transmits a PUCCH in that slot and / or the terminal is not expected to be configured to perform frequency hopping for PUCCH transmission in the slot.

[0337] -If the terminal is not configured to perform frequency hopping for PUCCH transmissions across different slots, and the terminal is configured to perform frequency hopping for PUCCH transmissions within one slot, the frequency hopping pattern between the first PRB and the second PRB is the same within each slot.

[0338] And / or there is an agreement as in Table 9 in RAN1#104b-e regarding frequency hopping with inter-slot bundling.

[0339] [Table 9]

[0340] Considering the RAN1#107-e agreement, which is arranged in the order of "hopping intervals determination" -> "configured TDW determination" and "actual TDW determination", Option 2 is naturally supported. It is also necessary to organize the FFS points. That is, bundle size and time domain hopping interval are explicitly and independently configured, and bundle size is not configured separately for FDD and TDD.

[0341] According to the method proposed herein, the bundle size may be the same as or different from the time domain window size.

[0342] FIG. 11 is a flowchart for explaining the operation method of the terminal proposed in this specification.

[0343] 11, first, a terminal (100 / 200 in FIG. 13 to FIG. 16) receives configuration information for a time domain window from a base station in step S1101. For example, the configuration information may include information regarding the length / boundary / spacing of the time domain window.

[0344] And / or the time domain window may include one or more time domain windows, or alternatively the time domain window may be one or more time domain windows, for example the time domain window may include a first time domain window and a second time domain window.

[0345] And / or the time-domain window may be a time-domain window for demodulation reference signal (DMRS) bundling or inter-slot bundling or joint channel estimation.

[0346] And / or, within a time domain window, the same phase and transmission power can be maintained / guaranteed.

[0347] And / or the time domain window is set based on the number of PUSCH repetitions. For example, if the number of PUCCH repetitions is set / indicated to be “N”, the length of the time domain window is JPEG0007656722000104.jpg712, JPEG0007656722000105.jpg713, where "M" may be a pre-set value, and / or "M" may be indicated by RRC / MAC-CE / DCI, etc., and / or "M" may be a UE-specific value or a Cell-specific value.

[0348] For example, the operation of the terminal receiving the configuration information in step S1101 can be realized by the above-mentioned devices of Figures 13 to 16. For example, referring to Figure 14, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to receive the configuration information.

[0349] And / or, the terminal (100 / 200 in FIG. 13 to FIG. 16) receives downlink control information (DCI) including scheduling information for the PUSCH and frequency hopping information for the PUSCH from the base station in step S1102, and / or the PUSCH repetition or PUSCH repeat transmission may be scheduled by the DCI.

[0350] For example, the scheduling information may include information about time resources and / or information about frequency resources, and / or the frequency hopping information may be information indicating PUSCH frequency hopping. For example, the terminal may transmit the PUSCH at a first frequency hop and a second frequency hop based on the frequency hopping information.

[0351] And / or, the PUSCH (based on the DCI) may be transmitted over multiple slots based on frequency hopping.

[0352] Although the operation method of Figure 11 is described with reference to an example in which frequency hopping is indicated by DCI, frequency hopping can be set / indicated in various manners, for which details please refer to the contents of this specification.

[0353] For example, the operation of the terminal receiving DCI in step S1102 can be realized by the above-mentioned devices of Figures 13 to 16. For example, referring to Figure 14, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to receive DCI.

[0354] And / or, the terminal (100 / 200 in FIG. 13 to FIG. 16) transmits the PUSCH to the base station in a first frequency hop having the same length / boundary / spacing as the first time domain window in step S1103.

[0355] For example, the operation of the terminal transmitting the PUSCH in step S1103 can be realized by the above-mentioned devices of Figures 13 to 16. For example, referring to Figure 14, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to transmit the PUSCH.

[0356] And / or, the terminal (100 / 200 in FIGs. 13 to 16) transmits the PUSCH to the base station in a second frequency hop having the same length / boundary / interval as the second time domain window in step S1104, and / or the first frequency hop may be an even-numbered hop and the second frequency hop may be an odd-numbered hop.

[0357] For example, the length / spacing / boundaries of a first frequency hop may be set to be the same as a first time domain window, and / or the length / spacing / boundaries of a second frequency hop may be set to be the same as a second time domain window.

[0358] And / or the boundary of the first frequency hop may be identical to the first time domain window, and / or the boundary of the second frequency hop may be identical to the second time domain window.

[0359] And / or the length / spacing / boundary of the first and second frequency hops is determined based on a length / spacing / boundary of a time domain window and a slot number within a radio frame, and / or a starting resource block (RB) of the second frequency hop is determined based on a starting RB and a frequency offset of the first frequency hop.

[0360] And / or slots for PUSCH The starting resource block (RB) for JPEG0007656722000106.jpg67 can be determined based on the following formula:

[0361]

number

[0362] Where: JPEG0007656722000108.jpg714 indicates the starting RB of the first frequency hop, JPEG0007656722000109.jpg715 shows the frequency offset between the first and second frequency hops, JPEG0007656722000110.jpg710 indicates the size of the uplink bandwidth part (BWP), JPEG0007656722000111.jpg56 indicates the length of the time domain window.

[0363] For example, the operation of the terminal transmitting the PUSCH in step S1104 can be realized by the above-mentioned devices of Figures 13 to 16. For example, referring to Figure 14, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206 to transmit the PUSCH.

[0364] Although the operational method of FIG. 11 has been described mainly for PUSCH transmission, it goes without saying that it can also be applied to PUCCH.

[0365] The operation of the terminal described with reference to Figure 11 is the same as the operation of the terminal described with reference to Figures 1 to 10 (e.g., first and second embodiments), so detailed explanations thereof will be omitted.

[0366] The above signaling and operations may be realized by the apparatuses (e.g., FIGS. 13 to 16) described below. For example, the above signaling and operations may be processed by one or more processors of FIGS. 13 to 16, and the above signaling and operations may be stored in a memory in the form of instructions / programs (e.g., instructions, executable codes) for driving at least one processor of FIGS. 13 to 16.

[0367] For example, a processing apparatus configured to control a terminal to transmit a PUSCH in a wireless communication system may include at least one processor and at least one memory operatively connected to the at least one processor and storing instructions to perform operations based on being executed by the at least one processor, and the operations may include receiving configuration information regarding a time domain window from a base station, receiving DCI from the base station including scheduling information for the PUSCH and frequency hopping information for the PUSCH, transmitting the PUSCH to the base station at a first frequency hop having the same length as a first time domain window, and transmitting the PUSCH to the base station at a second frequency hop having the same length as a second time domain window.

[0368] For example, in a computer-readable storage medium storing at least one instruction that, when executed by at least one processor, causes the at least one processor to control operations, the operations may include receiving configuration information for a time domain window from a base station, receiving DCI from the base station including scheduling information for a PUSCH and frequency hopping information for the PUSCH, transmitting the PUSCH to the base station at a first frequency hop having the same length as a first time domain window, and transmitting the PUSCH to the base station at a second frequency hop having the same length as a second time domain window.

[0369] FIG. 12 is a flow chart for explaining the operation method of the base station proposed in this specification.

[0370] 12, first, a base station (100 / 200 in FIG. 13 to FIG. 16) transmits configuration information for a time domain window to a terminal in step S1201. For example, the configuration information includes information regarding the length / boundary / interval of the time domain window.

[0371] And / or the time domain window may include one or more time domain windows, or alternatively the time domain window may be one or more time domain windows, for example the time domain window may include a first time domain window and a second time domain window.

[0372] And / or the time-domain window may be a time-domain window for demodulation reference signal (DMRS) bundling or inter-slot bundling or joint channel estimation.

[0373] And / or within a time domain window, the same phase and transmission power can be maintained / guaranteed.

[0374] And / or the time domain window is set based on the number of PUSCH repetitions. For example, if the number of PUCCH repetitions is set / indicated to be “N”, the length of the time domain window is JPEG0007656722000112.jpg712, JPEG0007656722000113.jpg713 is indicated / determined / set, where "M" may be a previously set value, and / or "M" may be indicated by RRC / MAC-CE / DCI, etc., and / or "M" may be a UE-specific value or a cell-specific value.

[0375] For example, the operation of the base station transmitting the configuration information in step S1201 can be realized by the above-mentioned devices of Figures 13 to 16. For example, referring to Figure 14, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to transmit the configuration information.

[0376] And / or, the base station (100 / 200 in FIG. 13 to FIG. 16) transmits downlink control information (DCI) including scheduling information for the PUSCH and frequency hopping information for the PUSCH to the terminal in step S1202. And / or, the PUSCH repetition or PUSCH repeated transmission may be scheduled by the DCI.

[0377] For example, the scheduling information may include information about time resources and / or information about frequency resources, and / or the frequency hopping information may be information indicating PUSCH frequency hopping, for example, the base station receives the PUSCH at a first frequency hop and a second frequency hop based on the frequency hopping information.

[0378] And / or, the PUSCH (based on the DCI) may be received based on frequency hopping over multiple slots.

[0379] Although the operation method of Figure 12 is described with reference to an example in which frequency hopping is indicated by DCI, frequency hopping can be set / indicated in various manners, for which details may be found in the above specification.

[0380] For example, the operation of the base station transmitting DCI in step S1202 can be realized by the devices of Figures 13 to 16. For example, referring to Figure 14, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to transmit DCI.

[0381] And / or, the base station (100 / 200 in FIG. 13 to FIG. 16) receives a PUSCH from the terminal in a first frequency hop having the same length / boundary / spacing as the first time domain window in step S1203.

[0382] For example, the operation of the base station receiving the PUSCH in step S1203 can be realized by the above-mentioned devices of Figures 13 to 16. For example, referring to Figure 14, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to receive the PUSCH.

[0383] And / or, the base station (100 / 200 in FIGs. 13 to 16) receives the PUSCH from the terminal in a second frequency hop having the same length / boundary / spacing as the second time domain window in step S1204, and / or the first frequency hop may be an even-numbered hop and the second frequency hop may be an odd-numbered hop.

[0384] For example, the length / boundaries / spacing of the first frequency hop may be set to be the same as the first time domain window, and / or the length / boundaries / spacing of the second frequency hop may be set to be the same as the second time domain window. For example, the boundaries of the first frequency hop may be the same as the first time domain window, and / or the boundaries of the second frequency hop may be the same as the second time domain window.

[0385] And / or the length / boundary / spacing of the first and second frequency hops may be determined based on a length / boundary / spacing of a time domain window and a slot number within a radio frame, and / or a starting resource block (RB) of the second frequency hop may be determined based on a starting RB and a frequency offset of the first frequency hop.

[0386] And / or slots for PUSCH The starting resource block (RB) for JPEG0007656722000114.jpg67 can be determined based on the following formula:

[0387]

number

[0388] Where: JPEG0007656722000116.jpg714 indicates the start RB of the first frequency hop, JPEG0007656722000117.jpg715 shows the frequency offset between the first and second frequency hops, JPEG0007656722000118.jpg710 indicates the size of the uplink bandwidth part (BWP), JPEG0007656722000119.jpg56 indicates the length of the time domain window.

[0389] For example, the operation of the base station receiving the PUSCH in step S1204 can be realized by the above-mentioned devices of Figures 13 to 16. For example, referring to Figure 14, one or more processors 102 / 202 can control one or more memories 104 / 204 and / or one or more transceivers 106 / 206, etc. to receive the PUSCH.

[0390] Although the operational method of FIG. 12 has been described mainly for PUSCH transmission, it goes without saying that it can also be applied to PUCCH.

[0391] The operation of the base station described with reference to Figure 12 is the same as the operation of the base station described with reference to Figures 1 to 11 (e.g., first and second embodiments), so detailed explanations thereof will be omitted.

[0392] The above signaling and operations may be realized by the apparatuses (e.g., FIGS. 13 to 16) described below. For example, the above signaling and operations may be processed by one or more processors of FIGS. 13 to 16, and the above signaling and operations may be stored in a memory in the form of instructions / programs (e.g., instructions, executable codes) for driving at least one processor of FIGS. 13 to 16.

[0393] For example, a processing apparatus configured to control a base station to receive a PUSCH in a wireless communication system may include at least one processor and at least one memory operatively connected to the at least one processor and storing instructions for performing operations based on being executed by the at least one processor, the operations may include transmitting configuration information for a time domain window to a terminal, transmitting DCI to the terminal, the DCI including scheduling information for the PUSCH and frequency hopping information for the PUSCH, receiving the PUSCH from the terminal at a first frequency hop having the same length as a first time domain window, and receiving the PUSCH from the terminal at a second frequency hop having the same length as a second time domain window.

[0394] For example, in a computer-readable storage medium storing at least one instruction that, when executed by at least one processor, causes the at least one processor to control an operation, the operation may include transmitting configuration information for a time domain window to a terminal, transmitting DCI to the terminal, the DCI including scheduling information for a PUSCH and frequency hopping information for the PUSCH, receiving a PUSCH from the terminal at a first frequency hop having the same length as a first time domain window, and receiving a PUSCH from the terminal at a second frequency hop having the same length as a second time domain window.

[0395] An example of a communication system to which the present invention is applied

[0396] Without being limited thereto, the various descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present invention disclosed in this document may be applied to a variety of fields requiring wireless communication / connection (e.g., 5G) between devices.

[0397] Hereinafter, the present invention will be described in more detail with reference to the drawings. In the following drawings and description, the same reference numerals may represent the same or corresponding hardware blocks, software blocks, or function blocks unless otherwise stated.

[0398] FIG. 13 illustrates a communication system 1 to which the present invention is applied.

[0399] Referring to FIG. 13, the communication system 1 applied to the present invention includes a wireless device, a base station, and a network. Here, the wireless device means a device that communicates using a wireless connection technology (e.g., 5GNR (New RAT), LTE (Long Term Evolution)), and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot 100a, a vehicle 100b-1, 100b-2, an XR (eXtended Reality) device 100c, a handheld device (Hand-held device) 100d, a home appliance 100e, an IoT (Internet of Things) device 100f, and an AI device / server 400. For example, the vehicle may include a vehicle with a wireless communication function, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, and the like. Here, the vehicle may include a UAV (Unmanned Aerial Vehicle) (e.g., a drone). The XR devices include Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) devices, and may be embodied in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) installed in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and the like. The mobile devices may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, a smart glass), a computer (e.g., a laptop, and the like), and the like. The home appliances may include a TV, a refrigerator, a washing machine, and the like. The IoT devices may include a sensor, a smart meter, and the like. For example, a base station and a network may be embodied by a wireless device, and a specific wireless device 200a may operate as a base station / network node for other wireless devices.

[0400] The wireless devices 100a to 100f can be connected to a network 300 via a base station 200. AI (Artificial Intelligence) technology can be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f can be connected to an AI server 400 via a network 3000. The network 300 can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f can communicate with each other via the base station 200 / network 300, but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, the vehicles 100b-1 and 100b-2 can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Furthermore, an IoT device (eg, a sensor) can directly communicate with other IoT devices (eg, sensors) or other wireless devices 100a to 100f.

[0401] Wireless communications / connections 150a, 150b, and 150c can be established between the wireless devices 100a to 100f and the base station 200, and between the base stations 200 and 200. Here, the wireless communication / connection may be performed via various wireless connection technologies (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), and inter-base station communication 150c (e.g., relay, IAB (Integrated Access Backhaul)). Through the wireless communication / connection 150a, 150b, 1500c, the wireless device and the base station / wireless device, and the base station and the base station can transmit / receive wireless signals to each other. For example, the wireless communication / connection 150a, 150b, 150c can transmit / receive signals via various physical channels. To this end, based on various proposals of the present invention, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc. may be performed.

[0402] Examples of wireless devices to which the present invention can be applied

[0403] FIG. 14 illustrates a wireless device to which the present invention can be applied.

[0404] 14, a first wireless device 100 and a second wireless device 200 can transmit and receive wireless signals via various wireless access technologies (e.g., LTE, NR). Here, {first wireless device 100, second wireless device 200} may correspond to {wireless device 100x, base station 200} and / or {wireless device 100x, wireless device 100x} in FIG. 13.

[0405] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may be configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. For example, the processor 102 may process information in the memory 104 to generate a first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver 106. The processor 102 may also receive a wireless signal including a second information / signal via the transceiver 106, and then store information obtained from signal processing of the second information / signal in the memory 104. The memory 104 may be coupled to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for performing some or all of the processes controlled by the processor 102 or for performing the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in this document. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 may be connected to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be mixed with an RF (Radio Frequency) unit. In the present invention, a wireless device may also refer to a communication modem / circuit / chip.

[0406] The second wireless device 200 may include one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 2080. The processor 202 may be configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. For example, the processor 202 may process information in the memory 204 to generate a third information / signal, and then transmit a wireless signal including the third information / signal via the transceiver 206. The processor 202 may also receive a wireless signal including a fourth information / signal via the transceiver 206, and then store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be coupled to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions for performing some or all of the processes controlled by the processor 202 or for performing the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed in this document. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 206 may be connected to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be mixed with an RF unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

[0407] The hardware elements of the wireless device 100, 200 are described in more detail below. Without limitation, one or more protocol layers may be embodied by one or more processors 102, 202. For example, one or more processors 102, 202 may embody one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102, 202 may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein. The one or more processors 102, 202 can generate and provide signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information to the one or more transceivers 106, 206 according to the functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein.

[0408] The one or more processors 102, 202 may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. The one or more processors 102, 202 may be embodied in hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein may be embodied using firmware or software, and the firmware or software may be embodied to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein may be included in one or more processors 102, 202 or may be stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or operational flowcharts disclosed herein may be embodied using firmware or software in the form of code, instructions and / or collections of instructions.

[0409] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, code, instructions, and / or instructions. The one or more memories 104, 204 may comprise ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Also, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various techniques, such as wired or wireless connections.

[0410] One or more transceivers 106, 206 can transmit user data, control information, wireless signals / channels, etc., as referenced in the methods and / or operational flowcharts, etc., of this document to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, wireless signals / channels, etc., as referenced in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts, etc., disclosed in this document from one or more other devices. For example, one or more transceivers 106, 206 can be coupled to one or more processors 102, 202 and can transmit and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Also, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed herein, via one or more antennas 108, 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may convert the received wireless signals / channels, etc., from RF band signals to baseband signals for processing the received user data, control information, wireless signals / channels, etc., using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, wireless signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. To this end, one or more of the transceivers 106, 206 may include (analog) oscillators and / or filters.

[0411] Examples of wireless device applications to which this invention can be applied

[0412] 15 shows another example of a wireless device to which the present invention is applied. The wireless device may be embodied in various forms depending on the use case / service.

[0413] 15, the wireless devices 100, 200 correspond to the wireless devices 100, 200 of FIG. 14 and may be configured with various elements, components, units, and / or modules. For example, the wireless devices 100, 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional element 140. The communication unit may include a communication circuit 112 and a transceiver(s) 114. For example, the communication circuit 112 may include one or more processors 102, 202 and / or one or more memories 104, 204 of FIG. 14. For example, the transceiver(s) 114 may include one or more transceivers 106, 206 and / or one or more antennas 108, 208 of FIG. 14. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140, and controls the overall operation of the wireless device. For example, the control unit 120 can control electrical / mechanical operations of the wireless device based on the programs / codes / instructions / information stored in the memory unit 130. In addition, the control unit 120 can transmit information stored in the memory unit 130 to an external device (e.g., another communication device) via the communication unit 110 through a wireless / wired interface, or store information received from an external device (e.g., another communication device) via the communication unit 110 through a wireless / wired interface in the memory unit 130.

[0414] The additional element 140 may be configured in various ways depending on the type of wireless device. For example, the additional element 140 may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computer unit. Without being limited thereto, the wireless device may be embodied in the form of a robot (FIG. 13, 100a), a vehicle (FIG. 13, 100b-1, 100b-2), an XR device (FIG. 13, 100c), a mobile device (FIG. 13, 100d), a home appliance (FIG. 13, 100e), an IoT device (FIG. 13, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a Fintech device (or a financial device), a security device, a climate / environment device, an AI server / device (FIG. 13, 400), a base station (FIG. 13, 200), a network node, or the like. The wireless device may be mobile or fixed depending on the use case / service.

[0415] In FIG. 15, various elements, components, units / parts, and / or modules in the wireless devices 100 and 200 may be interconnected entirely via a wired interface, or at least some of them may be connected wirelessly via the communication unit 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be connected via a wire, and the control unit 120 and the first unit (e.g., 130, 140) may be connected wirelessly via the communication unit 110. Also, each element, component, unit / part, and / or module in the wireless devices 100 and 200 may further include one or more elements. For example, the control unit 120 may be configured with one or more processor sets. For example, the control unit 120 may be configured with a set of a communication control processor, an application processor, an ECU (Electronic Control Unit), a graphics processor, a memory control processor, etc. As another example, the memory unit 130 may be composed of a Random Access Memory (RAM), a Dynamic RAM (DRAM), a Read Only Memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0416] Examples of portable devices to which this specification applies

[0417] FIG. 16 illustrates a mobile device to which the present invention is applied. The mobile device may include a smartphone, a smart pad, a wearable device (e.g., a smart watch, a smart glass), a mobile computer (e.g., a notebook computer, etc.). The mobile device may be referred to as a Mobile Station (MS), a user terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless terminal (WT).

[0418] 16, the portable device 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an input / output unit 140c. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 to 130 / 140a to 140c correspond to blocks 110 to 130 / 140 in FIG. 15, respectively.

[0419] The communication unit 110 can transmit and receive signals (e.g., data, control signals, etc.) to and from other wireless devices and base stations. The control unit 120 can control components of the portable device 100 to perform various operations. The control unit 120 can include an AP (Application Processor). The memory unit 130 can store data / parameters / programs / codes / commands required for operating the portable device 100. The memory unit 130 can also store input / output data / information, etc. The power supply unit 140a supplies power to the portable device 100 and can include wired / wireless charging circuits, a battery, etc. The interface unit 140b can support connection between the portable device 100 and other external devices. The interface unit 140b can include various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit 140c can receive or output video information / signals, audio information / signals, data, and / or information input by a user. The input / output unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and / or a haptic module.

[0420] For example, in the case of data communication, the input / output unit 140c may acquire information / signals (e.g., touch, text, voice, image, video) input by a user, and the acquired information / signals may be stored in the memory unit 130. The communication unit 110 may convert the information / signals stored in the memory into wireless signals, and transmit the converted wireless signals directly to another wireless device or to a base station. In addition, the communication unit 110 may receive wireless signals from another wireless device or a base station, and then restore the received wireless signals to the original information / signals. The restored information / signals may be stored in the memory unit 130 and then output in various forms (e.g., text, voice, image, video, haptic) via the input / output unit 140c.

[0421] The wireless communication technology realized in the wireless device (e.g., 100, 200) of this specification includes not only LTE, NR, and 6G, but also Narrowband Internet of Things for low power communication. At this time, for example, NB-IoT technology is an example of LPWAN (Low Power Wide Area Network) technology, and is realized in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally or alternatively, the wireless communication technology realized in the wireless device (e.g., 100, 200) of this specification communicates based on LTE-M technology. At this time, as an example, LTE-M technology is an example of LPWAN technology, and may be called various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology is realized in at least one of various standards such as 1) LTE CAT0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (e.g., 100, 200) of this specification may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) that consider low power communication, but is not limited to the above names. As an example, ZigBee technology can create personal area networks (PANs) related to small / low power digital communication based on various standards such as IEEE802.15.4, and may be called by various names.

[0422] The embodiments described above are combinations of the components and features of the present invention in a predetermined form. Each component or feature should be considered as optional unless otherwise expressly stated. Each component or feature may be implemented in a form not combined with other components or features. It is also possible to combine some components and / or features to constitute an embodiment of the present invention. The order of operations described in the embodiments of the present invention may be changed. Some configurations or features of an embodiment may be included in other embodiments, or may be replaced with corresponding configurations or features of other embodiments. It is obvious that claims that do not have an explicit reference relationship in the claims may be combined to constitute an embodiment, or may be included in a new claim by amendment after filing.

[0423] Embodiments of the present invention may be implemented by various means, such as hardware, firmware, software, or a combination thereof. In a hardware implementation, an embodiment of the present invention may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0424] In the case of a firmware or software implementation, an embodiment of the present invention may be implemented in the form of a module, procedure, function, etc. that performs the functions or operations described above. The software code may be stored in a memory and executed by a processor. The memory may be located inside or outside the processor and may exchange data with the processor by various means known in the art.

[0425] It is obvious to those skilled in the art that the present invention can be embodied in other specific forms without departing from the essential features of the present invention. Therefore, the above detailed description should not be interpreted as limiting in all respects, but should be considered as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the equivalent scope of the present invention are included in the scope of the present invention. [Industrial Applicability]

[0426] In the present specification, the method for transmitting and receiving a PUSCH in a wireless communication system has been described mainly with reference to examples applied to a 3GPP LTE / LTE-A system and a 5G system (New RAT system), but can also be applied to various other wireless communication systems such as Beyond 5G, 6G, and Beyond 6G.

Claims

1. receiving configuration information from a base station (BS), the configuration information including information related to a length of a time domain window, the time domain window being related to demodulation reference signal (DMRS) bundling for a physical uplink shared channel (PUSCH); receiving downlink control information (DCI) for scheduling the PUSCH from the BS; i) inter-slot frequency hopping; and ii) transmitting the PUSCH to the BS based on the DMRS bundling; a number of consecutive slots associated with a frequency hopping interval is determined based on the length of the time domain window; 2. The method of claim 1, wherein a starting resource block (RB) for the second frequency hop is determined based on a starting RB and a frequency offset for the first frequency hop.

3. The method of claim 1, wherein the first frequency hop is an even-numbered hop and the second frequency hop is an odd-numbered hop. 【Request 4】 【Number】 [0010] 【number】

5. The method of claim 1 , wherein within the time domain window, phase and transmit power are maintained.

6. The method of claim 1 , wherein the time domain window is set based on a number of repeated transmissions of the PUSCH.

7. The method of claim 1 , wherein the PUSCH is transmitted based on frequency hopping over multiple slots.

8. A UE (user equipment), At least one transceiver; At least one processor; at least one memory operatively coupled to the at least one processor and storing instructions for performing operations based on being executed by the at least one processor; The operation includes: receiving configuration information from a base station (BS), the configuration information including information related to a length of a time domain window, the time domain window being related to demodulation reference signal (DMRS) bundling for a physical uplink shared channel (PUSCH); receiving downlink control information (DCI) for scheduling the PUSCH from the BS; i) inter-slot frequency hopping; and ii) transmitting the PUSCH to the BS based on the DMRS bundling; a number of consecutive slots associated with a frequency hopping interval is determined based on the length of the time domain window;

9. A base station, At least one transceiver; At least one processor; at least one memory operatively coupled to the at least one processor and storing instructions for performing operations based on being executed by the at least one processor; The operation includes: transmitting configuration information to a user equipment (UE), the configuration information including information related to a length of a time domain window, the time domain window being related to demodulation reference signal (DMRS) bundling for a physical uplink shared channel (PUSCH); transmitting downlink control information (DCI) for scheduling the PUSCH to the UE; i) inter-slot frequency hopping; and ii) receiving the PUSCH from the UE based on the DMRS bundling; a number of consecutive slots associated with a frequency hopping interval is determined based on the length of the time domain window; 10. The base station of claim 9, wherein the first frequency hop is an even-numbered hop and the second frequency hop is an odd-numbered hop. 【Request 11】 【Amount】 [0025] 【number】

12. The base station of claim 9, wherein within the time domain window, phase and transmit power are maintained.

Images