CN117461280A

CN117461280A - Method for transmitting/receiving PUSCH in wireless communication system and apparatus therefor

Info

Publication number: CN117461280A
Application number: CN202280040056.2A
Authority: CN
Inventors: 沈载南; 高贤秀; 梁锡喆; 柳向善; 黄升溪
Original assignee: LG Electronics Inc
Current assignee: LG Electronics Inc
Priority date: 2021-04-06
Filing date: 2022-04-06
Publication date: 2024-01-26

Abstract

The present specification presents a method of transmitting PUSCH in a wireless communication system. The method executed by the terminal comprises the following steps: receiving configuration information related to a time domain window from a base station; receiving Downlink Control Information (DCI) including scheduling information for PUSCH and frequency hopping information for PUSCH from a base station; transmitting PUSCH to the base station at a first frequency hopping having the same length as the first time domain window; and transmitting the PUSCH to the base station at a second frequency hopping having the same length as the second time domain window.

Description

Method for transmitting/receiving PUSCH in wireless communication system and apparatus therefor

Technical Field

The present disclosure relates to a wireless communication system, and more particularly, to a method of transmitting and receiving a Physical Uplink Shared Channel (PUSCH) and an apparatus thereof.

Background

Mobile communication systems have been developed to provide voice services while ensuring the activity of users. However, in the mobile communication system, not only voice but also data services are extended. Currently, there is a shortage of resources due to explosive growth of business, and users demand higher-speed services. As a result, a more advanced mobile communication system is required.

The requirements for the next generation mobile communication system should be able to support acceptance of explosive data traffic, a sharp increase in data rate per user, a significant increase in the number of accepted connection devices, very low end-to-end delay and energy efficiency. For this, various technologies including dual connectivity, massive Multiple Input Multiple Output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), ultra wideband support, device networking, etc. have been studied.

In addition, for coverage enhancement, a technique for repeated transmission of PUSCH/PUCCH is being discussed.

Disclosure of Invention

Technical problem

The present disclosure proposes a method and apparatus for defining/configuring a time domain window for demodulation reference signal (DMRS) bundling (or inter-slot bundling).

In addition, the present disclosure proposes a method and apparatus for defining/configuring a time domain window based on the number of repeated transmissions of PUSCH/PUCCH.

In addition, the present disclosure proposes a method and apparatus for defining/configuring a hop interval having the same length as a time domain window.

Technical objects to be achieved by the present disclosure are not limited to the above technical objects, and other technical objects not described above will be clearly understood from the following description by those of ordinary skill in the art to which the present disclosure pertains.

Technical proposal

The present disclosure proposes a method of transmitting a Physical Uplink Shared Channel (PUSCH) in a wireless communication system.

The method performed by a User Equipment (UE) may include the steps of: receiving configuration information related to a time domain window from a base station; receiving Downlink Control Information (DCI) including scheduling information for PUSCH and frequency hopping information for PUSCH from a base station; transmitting PUSCH to the base station in a first frequency hopping having the same length as the first time domain window; and transmitting the PUSCH to the base station in a second frequency hopping having the same length as the second time domain window.

In addition, in the above method of the present disclosure, the lengths of the first frequency hopping and the second frequency hopping may be determined based on the length of the time domain window and the slot number within the radio frame.

In addition, in the above method of the present disclosure, a start Resource Block (RB) of the second frequency hopping may be determined based on the start RB of the first frequency hopping and the frequency offset.

In addition, in the above method of the present disclosure, the first frequency hopping may be an even frequency hopping, and the second frequency hopping may be an odd frequency hopping.

In addition, in the above method of the present disclosure, a slot for PUSCHThe starting Resource Block (RB) of the period may be determined based on the following equation.

[ type ]

Wherein RB is _start Initial RB, which may represent the first frequency hopping _offset A frequency offset between the first frequency hop and the second frequency hop may be represented,the size of an uplink bandwidth portion (BWP) may be represented, and W may represent the length of a time domain window.

In addition, in the above method of the present disclosure, the time domain window may be a time domain window for demodulation reference signal (DMRS) bundling.

In addition, in the above method of the present disclosure, the same phase and transmission power may be maintained in the time domain window.

In addition, in the above method of the present disclosure, the time domain window may be configured based on the number of PUSCH repeated transmissions.

In addition, in the above method of the present disclosure, PUSCH may be transmitted on a frequency hopping basis over a plurality of slots.

In addition, a User Equipment (UE) configured to transmit a Physical Uplink Shared Channel (PUSCH) in a wireless communication system, the UE 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 that, based on execution by the at least one processor, perform operations, wherein the operations may comprise: receiving configuration information related to a time domain window from a base station; receiving Downlink Control Information (DCI) including scheduling information for PUSCH and frequency hopping information for PUSCH from a base station; transmitting PUSCH to the base station in a first frequency hopping having the same length as the first time domain window; and transmitting the PUSCH to the base station in a second frequency hopping having the same length as the second time domain window.

In addition, the present disclosure proposes a method of receiving a Physical Uplink Shared Channel (PUSCH) in a wireless communication system. The method performed by the base station may comprise the steps of: transmitting configuration information related to a time domain window to a User Equipment (UE); transmitting Downlink Control Information (DCI) including scheduling information for PUSCH and frequency hopping information for PUSCH to the UE; receiving PUSCH from the UE in a first frequency hopping having the same length as the first time domain window; and receiving a PUSCH from the UE in a second frequency hopping having the same length as the second time domain window.

[ type ]

In addition, a base station configured to receive a Physical Uplink Shared Channel (PUSCH) in a wireless communication system is presented, the base station 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 that, based on execution by the at least one processor, perform operations, wherein the operations may include: transmitting configuration information related to a time domain window to a User Equipment (UE); transmitting Downlink Control Information (DCI) including scheduling information for PUSCH and frequency hopping information for PUSCH to the UE; receiving PUSCH from the UE in a first frequency hopping having the same length as the first time domain window; and receiving a PUSCH from the UE in a second frequency hopping having the same length as the second time domain window.

Additionally, in the present disclosure, a processing device configured to control a User Equipment (UE) to transmit a Physical Uplink Shared Channel (PUSCH) in a wireless communication system is presented, the processing device may include at least one processor and at least one memory operatively connected to the at least one processor and storing instructions that, based on execution by the at least one processor, perform operations, wherein the operations may include: receiving configuration information related to a time domain window from a base station; receiving Downlink Control Information (DCI) including scheduling information for PUSCH and frequency hopping information for PUSCH from a base station; transmitting PUSCH to the base station in a first frequency hopping having the same length as the first time domain window; and transmitting the PUSCH to the base station in a second frequency hopping having the same length as the second time domain window.

Additionally, a computer-readable storage medium storing at least one instruction is presented, wherein the at least one instruction, based on execution by at least one processor, causes the at least one processor to control operations, wherein the operations may include: receiving configuration information related to a time domain window from a base station; receiving Downlink Control Information (DCI) including scheduling information for a physical uplink shared channel PUSCH and frequency hopping information for the PUSCH from a base station; transmitting PUSCH to the base station in a first frequency hopping having the same length as the first time domain window; and transmitting the PUSCH to the base station in a second frequency hopping having the same length as the second time domain window.

Advantageous effects

According to the present disclosure, there is an effect of improving coverage by defining/configuring a time domain window for DMRS bundling (or inter-slot bundling).

In addition, according to the present disclosure, there is an effect of efficiently performing joint channel estimation by defining/configuring a time domain window based on the number of repeated transmissions of PUSCH/PUCCH.

In addition, according to the present disclosure, there is an effect of simultaneously performing inter-slot frequency hopping and joint channel estimation by defining/configuring a hopping interval having the same length as a time domain window.

The effects obtainable by the present disclosure are not limited to the above-described effects, and other technical effects not described above will be apparent to those skilled in the art to which the present disclosure pertains from the following description.

Drawings

The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the principles of the disclosure.

Fig. 1 is a diagram showing an example of an overall system structure of NR to which the method proposed in the present disclosure is applicable.

Fig. 2 illustrates a relationship between uplink frames and downlink frames in a wireless communication system to which the method proposed in the present disclosure is applicable.

Fig. 3 shows an example of a frame structure in an NR system.

Fig. 4 illustrates an example of a resource grid supported by a wireless communication system to which the method presented in the present disclosure may be applied.

Fig. 5 shows a slot structure of an NR frame to which the method proposed in the present disclosure is applicable.

Fig. 6 illustrates an example of a resource grid and parameter set of each antenna port to which the method proposed in the present disclosure may be applied.

Fig. 7 illustrates physical channels and general signal transmission.

Fig. 8 shows an example of PUSCH repetition type a.

Fig. 9 shows an example of PUSCH repetition type B.

Fig. 10 shows an example of DMRS positions and the number of OFDM symbols according to a mapping type.

Fig. 11 is a flowchart for explaining an operation method of the UE proposed in the present disclosure.

Fig. 12 is a flowchart for explaining an operation method of the base station proposed in the present disclosure.

Fig. 13 shows a communication system 1 applied to the present disclosure.

Fig. 14 illustrates a wireless device suitable for use in the present disclosure.

Fig. 15 shows another example of a wireless device applied to the present disclosure.

Fig. 16 shows a portable device applied to the present disclosure.

Detailed Description

Reference will now be made in detail to embodiments of the present disclosure, examples of which are illustrated in the accompanying drawings. The detailed description to be disclosed in connection with the accompanying drawings is intended to describe exemplary embodiments of the disclosure, and not to describe the only embodiments for practicing the disclosure. The following detailed description includes details to provide a thorough understanding of the present disclosure. However, it will be apparent to one skilled in the art that the present disclosure may be practiced without these specific details.

In some cases, to prevent ambiguity of the concepts of the present disclosure, known structures and devices may be omitted or shown in block diagram format based on core functions of the respective structures and devices.

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 part of a base station and a receiver may be part of a terminal. In the uplink, the transmitter may be part of a terminal and the receiver may be part of a base station. The base station may be denoted as a first communication device and the terminal may be denoted as a second communication device. A Base Station (BS) may be replaced by terms including a fixed station, a node B, an evolved node B (eNB), a next generation node B (gNB), a Base Transceiver System (BTS), an Access Point (AP), a network (5G network), an AI system, a roadside unit (RSU), a vehicle, a robot, an Unmanned Aerial Vehicle (UAV), an Augmented Reality (AR) device, a Virtual Reality (VR) device, and the like. Further, a terminal may be fixed or mobile and may be replaced by terms including User Equipment (UE), a Mobile Station (MS), a User Terminal (UT), a mobile subscriber station (MSs), a Subscriber Station (SS), an Advanced Mobile Station (AMS), a Wireless Terminal (WT), a machine-type communication (MTC) device, a machine-to-machine (M2M) device and a device-to-device (D2D) device, a vehicle, a robot, an AI module, an Unmanned Aerial Vehicle (UAV), an Augmented Reality (AR) device, a Virtual Reality (VR) device, and the like.

The following techniques may be used in various radio access systems including CDMA, FDMA, TDMA, OFDMA, SC-FDMA and the like. CDMA may be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA 2000. TDMA may be implemented as a radio technology such as global system for mobile communications (GSM)/General Packet Radio Service (GPRS)/enhanced data rates for GSM evolution (EDGE). OFDMA may be implemented as a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, evolved UTRA (E-UTRA), and so forth. UTRA is part of Universal Mobile Telecommunications System (UMTS). The 3 rd generation partnership project (3 GPP) Long Term Evolution (LTE) is part of evolved UMTS (E-UMTS) using E-UTRA, and LTE-Advanced (A)/LTE-A pro is an evolved version of 3GPP LTE. The 3GPP NR (New radio or New radio Access technology) is an evolved version of 3GPP LTE/LTE-A/LTE-A pro.

For clarity of description, the technical spirit of the present disclosure is described based on a 3GPP communication system (e.g., LTE-a or NR), but the technical spirit of the present disclosure is not limited thereto. LTE means technology after 3GPP TS 36.xxx Release 8. In detail, the LTE technology after 3GPP TS 36.xxx Release 10 is called LTE-a, and the LTE technology after 3GPP TS 36.xxx Release 13 is called LTE-a pro.3GPP NR means a technology after TS 38.xxx Release 15. LTE/NR may be referred to as a 3GPP system. "xxx" means detailed standard document numbering. LTE/NR may be collectively referred to as 3GPP systems. For background art, terms, omissions, and the like used to describe the present disclosure, reference may be made to what is disclosed in the standard documents previously disclosed in the present disclosure. For example, reference may be made to the following documents.

3GPP LTE

-36.211: physical channel and modulation

-36.212: multiplexing and channel coding

-36.213: physical layer procedure

-36.300: general description

-36.331: radio Resource Control (RRC)

3GPP NR

-38.211: physical channel and modulation

-38.212: multiplexing and channel coding

-38.213: physical layer process for control

-38.214: physical layer procedure for data

-38.300: NR and NG-RAN general description

-38.331: radio Resource Control (RRC) protocol specification

As more and more communication devices require greater communication capacity, improved mobile broadband communication compared to existing Radio Access Technologies (RATs) is required. In addition, large-scale Machine Type Communication (MTC) that provides various services anytime and anywhere by connecting a number of devices and objects is one of the main problems to be considered in next-generation communication. In addition, communication system designs that consider reliability and delay sensitive services/UEs are being discussed. The discussion introduces next generation radio access technology that considers enhanced mobile broadband communication (emmbb), large-scale MTC (mctc), ultra-reliable low latency communication (URLLC), and for convenience in this disclosure this technology is referred to as a new RAT. NR is an expression representing an example of a 5G Radio Access Technology (RAT).

Three main areas of demand for 5G include (1) the enhanced mobile broadband (emmbb) area, (2) the large-scale machine type communication (mctc) area, and (3) the Ultra Reliable Low Latency Communication (URLLC) area.

Some use cases may require multiple domains to optimize, and other use cases may focus on only one Key Performance Indicator (KPI). The 5G supports these various use cases in a flexible and reliable manner.

embbs far exceed basic mobile internet access and cover rich bi-directional tasks, media and entertainment applications in the cloud or augmented reality. Data is a key driving force for 5G, and dedicated voice services may not be seen for the first time in the 5G age. In 5G, it is expected that voice will be processed as an application using a data connection simply provided by the communication system. The main reasons for the increase in traffic include an increase in content size and an increase in the number of applications requiring high data transfer rates. As more and more devices are connected to the internet, streaming services (audio and video), conversational video, and mobile internet connections will be more widely used. Many of these applications require a normally open connection in order to push real-time information and notifications to the user. Cloud storage and applications are suddenly increased in mobile communication platforms, and this is applicable to both business and entertainment. Furthermore, cloud storage is a special use case that drives an increase in uplink data transfer rate. 5G is also used for remote cloud services. When using a haptic interface, lower end-to-end delay is required to maintain an excellent user experience. Entertainment (e.g., cloud gaming and video streaming) is another key element that increases the demand for mobile broadband capabilities. Entertainment is essential in smart phones and tablets wherever high mobility environments are included, such as trains, vehicles and airplanes. Another use case is augmented reality and information searching for entertainment. In this case, augmented reality requires very low latency and an instantaneous amount of data.

Furthermore, one of the most promising 5G use cases relates to a function capable of smoothly connecting embedded sensors (i.e., mctc) in all fields. By 2020, potential IoT devices are expected to reach 204 billion. Industrial IoT is one of the areas where 5G plays a major role to enable smart cities, asset tracking, smart public facilities, agriculture, and security infrastructure.

URLLC includes new services that will change industries through remote control of the primary infrastructure and links with ultra-reliability/low available latency, such as self-driving vehicles. The level of reliability and delay is critical for smart grid control, industrial automation, robotics, unmanned aerial vehicle control and regulation.

More particularly, a number of use cases are described.

5G may supplement Fiber To The Home (FTTH) and cable-based broadband (or DOCSIS) as a means of providing streams ranging from gigabits per second to hundreds of megabits per second. In addition to virtual reality and augmented reality, such a fast speed is required to transmit a TV with a resolution of 4K or higher (6K, 8K or higher). Virtual Reality (VR) and Augmented Reality (AR) applications include immersive sporting events. A particular application may require a particular network configuration. For example, in the case of VR games, the core server may need to be integrated with the network operator's edge network server in order for the gaming establishment to minimize latency.

With many use cases for automotive mobile communications, automobiles are expected to be an important new driving force in 5G. For example, entertainment for passengers requires both high capacity and high mobility mobile broadband. The reason for this is that future users continue to expect high quality connections regardless of their location and speed. Another example of use in the automotive field is augmented reality instrument panels. The augmented reality dashboard overlays and displays information identifying objects in the dark and informing the driver of the distance and movement of the objects over what the driver sees through the front window. In the future, wireless modules enable communication between vehicles, information exchange between vehicles and supported infrastructure, and information exchange between vehicles and other connected devices (e.g., devices carried by pedestrians). The safety system directs alternative behavioral routes so that the driver can drive more safely, thereby reducing the risk of accidents. The next step would be to remotely control or self-drive the vehicle. This requires very reliable, very fast communication between different self-driving vehicles and between the car and the infrastructure. In the future, all driving activities may be performed by the self-driving vehicle and the driver will be concerned with something other than traffic that the car itself cannot recognize. The technical requirements of self-driving vehicles require ultra-low delay and ultra-high speed reliability to increase traffic safety to levels that cannot be reached by humans.

Smart cities and smart households mentioned as smart society will be embedded as a high density radio sensor network. The distributed network of intelligent sensors will identify the cost of the city or home and the conditions for energy conservation maintenance. Similar configurations may be performed for individual households. The temperature sensor, the window and the heating controller are all in wireless connection with the burglar alarm and the household appliance. Many of these sensors are typically low data transfer rates, low energy and low cost. However, for example, a particular type of monitoring device may require real-time HD video.

The consumption and distribution of energy, including heat or gas, is highly distributed and therefore requires automated control of the distributed sensor network. The smart grid gathers information and interconnects the sensors using digital information and communication technology so that the sensors operate based on the information. The information may include the behavior of suppliers and consumers, so the smart grid may improve the distribution of fuel, such as electricity, in an efficient, reliable, economical, production sustainable and automated manner. The smart grid may be considered as another sensor network with small delay.

The health part has many applications that benefit from mobile communications. The communication system may support remote therapy that provides clinical therapy at a remote location. This helps reduce the obstruction of distances and may improve the acquisition of medical services that cannot be used continuously in remote rural areas. Furthermore, this is used to save lives in important therapeutic and emergency situations. A mobile communication based radio sensor network may provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

Radio and mobile communication are becoming increasingly important in the field of industrial applications. Wiring requires high installation and maintenance costs. Thus, in many industrial fields the possibility of replacing the cable with a reconfigurable radio link is an attractive opportunity. However, implementing this possibility requires a radio connection to operate with similar delay, reliability and capacity as the cable and management simplicity. Low latency and low error probability are new requirements for 5G connections.

Logistics and shipping tracking are important uses of mobile communications that allow inventory and packages to be tracked anywhere using location-based information systems. Logistics and freight tracking usage typically require lower data speeds, but a wider area and reliable location information.

An OFDM transmission scheme or a similar transmission scheme is used in a new RAT system including NR. The new RAT system may follow different OFDM parameters than those of LTE. Alternatively, the new RAT system may follow the parameter set of legacy LTE/LTE-a as such or have a larger system bandwidth (e.g., 100 MHz). Alternatively, one cell may support multiple parameter sets. In other words, UEs operating with different parameter sets may coexist in one cell.

The parameter set corresponds to one subcarrier spacing in the frequency domain. Different parameter sets may be defined by scaling the reference subcarrier spacing to an integer N.

Definition of terms

eLTE eNB: an eLTE eNB is an evolution of an eNB that supports connectivity with EPC and NGC.

gNB: nodes supporting NR and connectivity to NGC.

The new RAN: a radio access network supporting NR or E-UTRA or an interface with NGC.

Network slice: network slicing is a network created by an operator that is customized to provide an optimized solution for a particular market scenario requiring a particular requirement with an end-to-end scope.

Network function: a network function is a logical node within the network infrastructure that has well-defined external interfaces and well-defined functional behavior.

NG-C: control plane interface used on NG2 reference point between new RAN and NGC.

NG-U: user plane interface used on NG3 reference point between new RAN and NGC.

Non-independent NR: the gNB requires the LTE eNB as an anchor for control plane connectivity with the EPC or the deployment configuration of the elteeenb as an anchor for control plane connectivity with the NGC.

Non-independent E-UTRA: the elteeenb requires deployment configuration of the gNB as an anchor point for control plane connectivity with the NGC.

User plane gateway: termination point of NG-U interface.

Overview of the system

Fig. 1 shows an example of the overall structure of an NR system to which the method proposed in the present disclosure is applicable.

Referring to fig. 1, the NG-RAN consists of a gNB providing a User Equipment (UE) with NG-RA user plane (new AS sublayer/PDCP/RLC/MAC/PHY) and control plane (RRC) protocol termination.

The gNBs are interconnected with each other through an Xn interface.

The gNB is also connected to the NGC through an NG interface.

More specifically, the gNB is connected to an access and mobility management function (AMF) through an N2 interface and to a User Plane Function (UPF) through an N3 interface.

New set of Rat (NR) parameters and frame structure

In an NR system, multiple parameter sets may be supported. The parameter set may be defined by a subcarrier spacing and CP (cyclic prefix) overhead. The spacing between the multiple subcarriers may be derived by scaling the base subcarrier spacing to an integer N (or μ). In addition, although it is assumed that a very low subcarrier spacing is not used at a very high subcarrier frequency, a parameter set to be used may be selected independently of a frequency band.

In addition, in the NR system, various frame structures according to a plurality of parameter sets may be supported.

Hereinafter, orthogonal Frequency Division Multiplexing (OFDM) parameter sets and frame structures that can be considered in the NR system will be described.

The multiple OFDM parameter sets supported in the NR system may be as defined in table 1.

TABLE 1

μ	Δf＝2 ^μ ·15[kHz]	Cyclic prefix
			0	15	Normal state
1	30	Normal state
			2	60	Normal, extended
3	120	Normal state
			4	240	Normal state

The NR supports a plurality of parameter sets (or subcarrier spacing (SCS)) for supporting various 5G services. For example, when the SCS is 15kHz, a wide area in the conventional cellular band is supported, when the SCS is 30kHz/60kHz, dense urban areas, lower delays and wider carrier bandwidths are supported, and when the SCS exceeds 60kHz, bandwidths greater than 24.25GHz are supported in order to overcome phase noise.

The NR frequency bands are defined as two types of frequency ranges (FR 1 and FR 2). FR1 and FR2 may be configured as shown in table 2 below. For convenience of explanation, in a frequency range used in the NR system, FR1 may represent "a 6GHz or lower range", FR2 may represent "a 6GHz or higher range", and further, FR2 may refer to millimeter wave (mmW).

TABLE 2

Frequency range assignment	Corresponding frequency range	Subcarrier spacing
			FR1	450MHz-6000MHz	15,30,60kHz
FR2	24250MHz-52600MHz	60,120,240kHz

As described above, the value of the frequency range of the NR system may be changed. For example, FR1 may include a frequency band of 410MHz to 7125MHz, as shown in table 3 below. That is, FR1 may include a frequency band of 6GHz (or 5850, 5900, 5925MHz, etc.) or above. For example, the frequency bands above 6GHz (or 5850, 5900, 5925MHz, etc.) included in FR1 may include unlicensed frequency bands. The unlicensed frequency band may be used for various purposes, such as for communication of vehicles (e.g., autonomous driving).

TABLE 3

Frequency rangeEnclosure designation	Corresponding frequency range	Subcarrier spacing
			FR1	410MHz-7125MHz	15,30,60kHz
FR2	24250MHz-52600MHz	60,120,240kHz

Regarding the frame structure in the NR system, the sizes of various fields in the time domain are expressed as time units T _s ＝1/(Δf _max ·N _f ) Is a multiple of (2). In this case Δf _max ＝480·10 ³ And N _f =4096. DL and UL transmissions are configured with T _f ＝(Δf _max N _f /100)·T _s Radio frame of 10ms segment. Radio frames are formed by having T each _sf ＝(Δf _max N _f /1000)·T _s Ten subframes of a 1ms section. In this case, there may be a UL frame set and a DL frame set.

As shown in fig. 2, an uplink frame number i for transmission from a User Equipment (UE) should be T before the start of a corresponding downlink frame at the corresponding UE _TA ＝N _TA T _s Starting.

Regarding parameter set μ, slots are per subframeIs numbered in ascending order and is in +.>Is numbered in ascending order. One time slot is defined by->Each successive OFDM symbol is composed, and->Determined according to the parameter set used and the slot configuration. Time slot ∈>Is time-wise +.>Is aligned with the beginning of the alignment.

Not all UEs are able to transmit and receive simultaneously, which means that not all OFDM symbols in a downlink or uplink slot may be used.

Table 4 shows the number of OFDM symbols per slot in the normal CPNumber of time slots per radio frameAnd the number of slots per subframe +.>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.

TABLE 4

TABLE 5

Fig. 3 shows an example of a frame structure in an NR system. Fig. 3 is for convenience of illustration only and does not limit the scope of the present disclosure.

In table 5, in the case where μ=2, that is, as an example where the subcarrier spacing (SCS) is 60kHz, one subframe (or frame) may include four slots with reference to table 3, and one subframe= {1,2,4} slots shown in fig. 3, for example, the number of slots that may be included in one subframe may be defined as in table 3.

Further, the mini-slot may include 2,4, or 7 symbols, or may include more symbols or fewer symbols.

Regarding physical resources in the NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. may be considered.

The above-mentioned physical resources that can be considered in the NR system are described in more detail below.

First, with respect to an antenna port, an antenna port is defined such that a channel transmitting a symbol on the antenna port can be inferred from a channel transmitting another symbol on the same antenna port. Two antenna ports may be considered to be in a quasi co-located or quasi co-located (QC/QCL) relationship when the massive nature of the channel transmitting symbols on one antenna port may be inferred from the channel transmitting symbols on the other antenna port. Here, the large-scale property may include at least one of delay spread, doppler spread, frequency shift, average received power, and received timing.

Fig. 4 illustrates an example of a resource grid supported in a wireless communication system to which the method proposed in the present disclosure is applicable.

Referring to fig. 4, the resource grid is formed of the frequency domainSub-carrier composition, each sub-frame comprising 14.2 ^μ OFDM symbols, but the present disclosure is not limited thereto.

In an NR system, the transmitted signal is composed ofSub-carriers and->One or more resource grid descriptions of the OFDM symbols, wherein +.> Represents the maximum transmission bandwidth and may vary not only between parameter sets, but also between uplink and downlink.

In this case, as shown in fig. 6, one resource grid may be configured per parameter set μ and antenna port p.

In the time domain, a slot includes a plurality of symbols. For example, in the case of a normal CP, one slot includes 7 symbols, but in the case of an extended CP, one slot includes 6 symbols. In the frequency domain, a carrier includes a plurality of subcarriers. In the frequency domain, a Resource Block (RB) is defined to a plurality (e.g., 12) of consecutive subcarriers. In the frequency domain, a bandwidth part (BWP) is defined as a plurality of consecutive (P) RBs, and may correspond to one parameter set (e.g., SCS, CP length, etc.). The carrier may include a maximum of N (e.g., 5) BWPs. The data communication is performed through the enabled BWP, and only one BWP may be enabled for one terminal. Each element in the resource grid is referred to as a Resource Element (RE) and may map one complex symbol.

Fig. 6 shows an example of a resource grid and parameter set for each port of a wireless port to which the method proposed in the present disclosure is applicable.

The individual elements of the resource grid for parameter set μ and antenna port p are referred to as resource elements and are paired by an indexUniquely identifying, wherein->Is an index in the frequency domain,>refers to the location of the symbol in the subframe. Index pair (k, l) is used to refer to the resource element in the slot, wherein +.>

Resource elements for parameter set μ and antenna port pCorresponding to complex value +.>When there is no risk of confusion or when no specific antenna port or parameter set is specified, the indices p and μmay be discarded, as a result, the complex value may be +.>Or->

Further, the physical resource blocks are defined as in the frequency domainSuccessive subcarriers.

Point a serves as a common reference point for the resource block grid and may be obtained as follows.

-offsetToPointA for PCell downlink denotes 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 and expressed in resource block units, assuming 15kHz subcarrier spacing for FR1 and 60kHz subcarrier spacing for FR 2;

-absoltatefrequencypinta represents the frequency location of point a in Absolute Radio Frequency Channel Number (ARFCN);

For a subcarrier spacing configuration μ, the common resource blocks are numbered upward in the frequency domain starting from 0.

The center of subcarrier 0 of common resource block 0 of subcarrier spacing configuration μ coincides with "point a". Common resource block number in the frequency domainAnd the resource element (k, l) of the subcarrier spacing configuration μ can be given by the following equation 1.

[ 1]

Here, k may be defined with respect to the point a such that k=0 corresponds to a subcarrier centered on the point a. Physical resource blocks are defined within a bandwidth part (BWP) and range from 0 to 0Number, where i is the number of BWP. Physical resource block n in BWP i _PRB And common resource block n _CRB The relationship between them can be given by the following equation 2.

[ 2]

Here the number of the elements is the number,may be a common resource block where BWP starts with respect to common resource block 0.

Physical channel and general signal transmission

Fig. 7 illustrates physical channels and general signal transmission. In a wireless communication system, a UE receives information from an eNB through a Downlink (DL) and the UE transmits information from the eNB through an Uplink (UL). The information transmitted and received by the eNB and the UE includes data and various control information, and there are various physical channels according to the type/purpose of the information transmitted and received by the eNB and the UE.

When the UE powers on or newly enters a cell, the UE performs an initial cell search operation (e.g., synchronization with the eNB) (S701). To this end, the UE may receive a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) from the eNB and synchronize with the eNB, and acquire information such as a cell ID. Thereafter, the UE may receive a Physical Broadcast Channel (PBCH) from the eNB and acquire intra-cell broadcast information. Further, the UE receives a downlink reference signal (DL RS) to check a downlink channel state in the initial cell search step.

The UE that completed the initial cell search receives a Physical Downlink Control Channel (PDCCH) and a physical downlink control channel (PDSCH) according to information loaded on the PDCCH to acquire more specific system information (S702).

Further, when there is no radio resource for first accessing the eNB or for signal transmission, the UE may perform a random access procedure (RACH) for the eNB (S703 to S706). To this end, the UE may transmit a specific sequence to a preamble through a Physical Random Access Channel (PRACH) (S703 and S705) and receive a response message (random access response (RAR) message) to the preamble through a PDCCH and a corresponding PDSCH. In case of the contention-based RACH, a contention resolution procedure may be additionally performed (S706).

The UE performing the above procedure 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. Specifically, the UE may receive Downlink Control Information (DCI) through the PDCCH. Here, the DCI may include control information such as resource allocation information of the UE, and formats may be differently applied according to purposes of use.

Further, the control information that the UE transmits to the eNB through the uplink or the UE receives from the eNB may include a downlink/uplink ACK/NACK signal, a Channel Quality Indicator (CQI), a Precoding Matrix Index (PMI), a Rank Indicator (RI), and the like. The UE may transmit control information such as CQI/PMI/RI via PUSCH and/or PUCCH.

PUCCH format of NR

NR supports a total of 5 PUCCH formats, which may be divided into a short PUCCH and a long PUCCH according to duration. Table 6 shows 5 PUCCH formats.

Short duration PUCCH

-format 0: UCI for up to 2 bits with multiplexing

-format 2: UCI for more than 2 bits without multiplexing

Long duration PUCCH

-format 1: UCI for up to 2 bits with multiplexing

-format 3: UCI for more than 2 bits without multiplexing

-format 4: UCI for more than 2 bits with multiplexing

TABLE 6

PUCCH Coverage Enhancement (CE)

Regarding PUCCH enhancement, the following method may be considered to improve PUCCH coverage.

-DMRS-free PUCCH: design details of DMRS-free PUCCH (e.g., sequence-based PUCCH transmission, UCI transmission without DMRS versus reuse of Rel-15 scheme) may be further studied

PUCCH repetition like Rel-16 PUSCH repetition type B, for minimum UCI < = 11 bits

- (explicit or implicit) dynamic PUCCH repetition factor indication

-DMRS bundling on PUCCH repetition: including a study of a subset of PUCCH repetition transmitted without DMRS, at least for UCI < = 11 bits

DMRS bundling of PUCCH repetition may be considered together with DMRS bundling of PUSCH repetition.

The PUCCH repetition scheme must describe the resources that PUSCH uses to meet the throughput target and can be compared with Rel-15/16PUCCH repetition.

Table 7 shows the PUCCH coverage enhancement technique considered.

TABLE 7

PUCCH coverage enhancement technique under consideration
	Sequence-based DMRS-free PUCCH
PUCCH repetition similar to PUSCH repetition type B
	Dynamic PUCCH repetition factor indication (explicit or implicit)
PF 0/1 with Pi/2BPSK based on sequence
	Pre-DFT data RS multiplexing for PF2 with Pi/2BPSK
DMRS bundling for PUCCH
	Compact UCI
Frequency hopping enhancement for PUCCH
	Short/mini slot PUCCH repetition
Power control enhancement for PUCCH
	Increased max # allowed repetition for PUCCH
PUCCH transmit diversity scheme
	DMRS overhead reduction
UE antenna configuration for FR2Enhancement
	Higher DMRS density
A-CSI on PUCCH
	Symbol level PUCCH repetition
Relay (including side link relay)
	Reflection array
Split UCI payloads on short PUCCH and long PUCCH on adjacent S and U slots

PUSCH repetition

PUSCH repetition types a and B are introduced in NR Rel-15/16, and transmission is performed as follows according to the PUSCH repetition type.

PUSCH repetition type A

Fig. 8 shows an example of PUSCH repetition type a. As shown in fig. 8, for slot-based repetition, PUSCH repetition type a performs repetition at the same PUSCH transmission start symbol position and PUSCH transmission symbol length for each slot. At this time, if there are invalid symbols that cannot be used for PUSCH transmission among symbol resources constituting a specific PUSCH repetition, transmission corresponding to the PUSCH repetition is discarded and not performed. That is, when performing a total of 4 PUSCH repetition transmissions of Rep0, rep1, rep2, and Rep3, if an invalid symbol is included in symbol resources constituting Rep1, transmission of Rep1 is discarded, and only transmission of Rep0, rep2, and Rep3 is performed. Thus, the number of repetitions actually performed may be smaller than the number of repetitions of the configuration.

In case of PUSCH repetition type a, the UE is configured for frequency hopping through upper layer parameters.

One of the following two frequency hopping patterns may be configured.

Intra-slot frequency hopping applicable to single-slot PUSCH transmission and multislot PUSCH transmission

Inter-slot frequency hopping applicable to multi-slot PUSCH transmissions

PUSCH repetition type B

Fig. 9 shows an example of PUSCH repetition type B. In PUSCH repetition type B, repetition is performed in units of symbol length of transmitting an actual PUSCH.

That is, when PUSCH is transmitted in 10 symbols as shown in (a) of fig. 9, PUSCH repetition is performed in units of 10 consecutive symbols. Determining repetition of PUSCH repetition transmission time resources without considering slot boundaries, invalid symbols, etc. is referred to as nominal repetition.

However, in the case of actual PUSCH repetition, one PUSCH cannot be transmitted at a slot boundary. When the PUSCH transmission includes a slot boundary, as shown in (b) of fig. 9, two actual repetitions are performed around the slot boundary. In addition, one PUSCH transmission may be performed through only consecutive symbols. If there is an invalid symbol in the time resource in which PUSCH repetition should be transmitted, the actual repetition is constructed using consecutive symbols bordered by the invalid symbol. For example, if 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 other than the invalid symbols each constitute one actual repetition.

If a symbol that cannot be used for PUSCH transmission (e.g., DL symbol indicated by DCI format 2_0) is included in one actual repetition resource, the actual repetition transmission is discarded and not performed.

For PUSCH repetition type B, the UE is configured for frequency hopping by upper layer parameters.

The frequency hopping pattern of PUSCH transmission configured for type 2 follows the configuration of enabling DCI formats. One of two hopping patterns may be configured.

Inter-repetition frequency hopping

Inter-slot frequency hopping

DMRS for PDSCH/PUSCH

The DMRS for PDSCH/PUSCH consists of a preamble DMRS and an additional DMRS.

-pre-loaded DMRS

The transmission time resource location of the preloaded DMRS is determined by the following factors.

The mapping type (PDSCH mapping type/PUSCH mapping type) of the data channel may vary according to whether it is type a or type B (slot-based or non slot-based), and the mapping type is configured through RRC.

In the case of slot-based transmission, the transmission start OFDM symbol position of the preamble DMRS may be the 3 rd or 4 th OFDM symbol of the data transmission resource, and an indication as to whether the transmission start OFDM symbol position is the 3 rd OFDM symbol or the 4 th OFDM symbol is transmitted through the PBCH.

The preamble DMRS may be composed of one or two consecutive OFDM symbols, and whether the number of OFDM symbols is one or two is configured through RRC.

The mapping type within the transmission OFDM symbol resource of the preloaded DMRS may have two types (type 1 or type 2), and information about the applicable type is configured as RRC. For type 1, T-CDM (CDM in the time domain) and/or FDM techniques are used to support 4 or 8 antenna ports, respectively, depending on whether the DMRS symbol length is 1 or 2,F-CDM (CDM in the frequency domain). For type 2, the techniques of CDM, T-CDM, and/or FDM are used to support 6 or 12 antenna ports, respectively, depending on whether the DMRS symbol length is 1 or 2,F-CDM.

-additional DMRS

The number of additional DMRSs is determined to be 0, 1, 2, or 3. The maximum number of additional DMRSs transmitted is determined by RRC, and the number of additional DMRSs actually transmitted and the OFDM symbol position transmitted within each maximum number of DMRSs are determined according to the length of the OFDM symbol of the transmission data. The symbol positions of the pre-loaded DMRS and the additional DMRS according to the data symbol length are shown in fig. 10.

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 preamble DMRS.

Fig. 10 shows an example of DMRS positions according to a mapping type and the number of OFDM symbols.

The position and number of symbols of the current PUSCH DMRS vary according to the length of the symbol transmitting PUSCH. In particular, when PUSCH repetition type B is used, the location and number of DMRS symbols are determined based on the actual repetition length of PUSCH. In this case, the location of the DMRS may vary for each PUSCH repetition.

According to the contact statement (LS) of the RAN4, in order to perform joint channel estimation, it must be transmitted in the same Physical Resource Block (PRB). That is, when joint channel estimation is configured, inter-slot frequency hopping should not occur according to existing rules. Therefore, it is necessary to enhance the frequency hopping between time slots.

The following is a description of frequency hopping of PUSCH in sub-clauses 6.3.1 and 6.3.2 of 3GPP Technical Specification (TS) 38.214.

Frequency hopping of PUSCH repetition type a

In case of PUSCH repetition type a, the UE may schedule the frequency hopping by the higher layer parameter frequency hophoping-fordciformat0_2 of the PUSCH transmission scheduled by the DCI format0_2, by the frequency hoping provided in the PUSCH-Config of the PUSCH transmission scheduled by the DCI format other than 0_2, and be configured for the frequency hopping by the frequency hoping provided in the configured constructeghentconfig of the PUSCH transmission. One of two hopping patterns may be configured.

Intra-slot frequency hopping for single-slot and multislot PUSCH transmissions

Inter-slot frequency hopping for multislot PUSCH transmission

In case of resource allocation type 2, the UE may transmit PUSCH without frequency hopping.

In case of resource allocation type 1, depending on whether or not the transition precoding of PUSCH transmission is enabled, the UE may perform PUSCH hopping if a hopping field is configured to 1 in a corresponding detected DCI format or random access response UL grant, or if an upper layer parameter frequency hopingoffset is provided for a type 1PUSCH transmission configured with a grant.

Otherwise, PUSCH frequency hopping may not be performed. If frequency hopping is enabled for PUSCH, RE mapping may be defined in a predefined specification (e.g., 3gpp TS 38.211, clause 6.3.1.6).

In case of PUSCH scheduled by RAR UL grant, fallback RAR 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 may be obtained as described in predefined specifications (3 gpp TS 38.213, clause 8.3).

In the case of PUSCH scheduled through DCI format 0_0/0_1 or PUSCH based on UL grant configured by type 2 enabled by DCI format 0_0/0_1, and in the case of resource allocation type 1, frequency offset may be configured by frequency hophopkingoffsetlists as an upper layer parameter of PUSCH-Config. In the case of PUSCH scheduled through DCI format0_2 or PUSCH based on UL grant configured by type 2 enabled by DCI format0_2, and in the case of resource allocation type 1, frequency offset may be configured by frequencyhopappingoffsetlists-fordcifromat0_2 as an upper layer parameter of PUSCH-Config.

If the size of the active BWP is smaller than 50 PRBs, one of the offsets of the two higher layer configurations may be indicated in the UL grant.

If the size of the active BWP is 50PRB or more, one of the offsets of the four higher layer configurations may be indicated in the UL grant.

In the case of PUSCH based on UL grant configured in type 1, the frequency offset may be provided by the upper layer parameter freequencyhopkingoffset of the rrc-configurable uplink grant.

In case of intra-slot hopping, the starting RB of each hop can be given as equation 3.

[ 3]

Here, i=0 and i=1 are the first hop and the second hop, respectively, RB _start Is the starting RB in UL BWP and can be calculated from the resource block assignment information of resource allocation type 1. RB (radio bearer) _offset Is the frequency offset in RB between two hops. The number of symbols in the first hop may be determined byGiven. The number of symbols in the second hop may be defined by +.>Given. Here, a->May be the length of PUSCH transmission in an OFDM symbol of one slot.

In case of inter-slot frequency hopping, slotsThe initial RB among them can be given as formula 4.

[ 4]

Here the number of the elements is the number,may be the current slot number, RB, in a radio frame where a multislot PUSCH transmission may occur _start May be a starting RB in UL BWP calculated from the resource block allocation information of the resource allocation type 1. RB (radio bearer) _offset There may be a frequency offset in RB between two hops.

Frequency hopping of PUSCH repetition type B

In case of PUSCH repetition type B, the UE may configure frequency hopping through an upper layer parameter frequency hophoping-fordcifformat0_2 of a PUSCH transmission scheduled by DCI format0_2, frequency hoping-fordcifformat0_1 provided in a PUSCH transmission scheduled by DCI format0_1, and frequency hoping-puscheptype provided in a rrc-configurable uplink grant configured by type 1. The frequency hopping pattern of PUSCH transmission in a type 2 configuration may follow a configuration that enables DCI formats. One of two hopping patterns may be configured.

Inter-repetition frequency hopping

Inter-slot frequency hopping

In case of resource allocation type 1, depending on whether or not the transition precoding of PUSCH transmission is enabled, the UE may perform PUSCH hopping if a hopping field is configured to 1 in a corresponding detected DCI format or an upper layer parameter frequency hoping-PUSCH type b configured with a grant is provided. Otherwise, PUSCH frequency hopping may not be performed. If frequency hopping is enabled for PUSCH, RE mapping may be defined in a predefined specification (e.g., 3gpp TS 38.211, clause 6.3.1.6).

In the case of PUSCH scheduled by DCI format0_1 or PUSCH based on UL grant configured by type 2 enabled by DCI format0_1, and in the case of resource allocation type 1, the frequency offset may be configured by frequencyhopappingoffsetlists as an upper layer parameter of PUSCH-Config. In the case of PUSCH scheduled by DCI format0_2 or PUSCH based on UL grant configured by type 2 enabled by DCI format0_2, and in the case of resource allocation type 1, frequency offset may be configured by frequencyhopappingoffsetlists-fordcifromat0_2 as an upper layer parameter of PUSCH-Config.

In the case of inter-repetition frequency hopping, the starting RB within the n-th nominal repetition may be given as in equation 5.

[ 5]

Here, RB _start May be a starting RB, RB in UL BWP calculated from resource block assignment information of resource allocation type 1 _offset There may be a frequency offset in RB between two hops.

In the case of inter-slot hopping, a starting RB among slots may follow a starting RB of inter-slot hopping of PUSCH repetition type a of a predefined specification (3 gpp TS 38.214, clause 6.3.1).

As described above, the existing inter-slot hopping determines to which of two PRBs a corresponding transmission occasion is transmitted according to an index within a subframe of a slot in which PUSCH or PUCCH is transmitted. This violates the condition for performing joint channel estimation.

Accordingly, including the above-mentioned problems, the present disclosure proposes a method of inter-slot bundling and inter-slot frequency hopping for joint channel estimation suitable for coverage enhancement.

Specifically, the present disclosure proposes a method of determining/configuring/defining a time domain window size for inter-slot bundling (hereinafter, first embodiment) and a method of configuring/defining an inter-slot frequency hopping boundary for inter-slot bundling (hereinafter, second embodiment).

Hereinafter, the embodiments described in this disclosure are divided for convenience of description only, and it goes without saying that some methods and/or some configurations of one embodiment may be replaced with those of other embodiments or may be applied in combination with each other.

The present disclosure is described from the perspective of Physical Uplink Shared Channel (PUSCH) transmission, but the methods presented in the present disclosure may be applied not only to PUSCH, but also to transmission of other channels such as Physical Uplink Control Channel (PUCCH), physical Downlink Shared Channel (PDSCH), and Physical Downlink Control Channel (PDCCH).

The time slots, subframes, frames, etc. mentioned in the embodiments described in this disclosure may correspond to specific examples of specific time units used in the wireless communication system. That is, when the method proposed in the present disclosure is applied, the time unit or the like may be replaced by other time units applied in another wireless communication system.

In the present disclosure, L1 signaling may refer to DCI-based dynamic signaling between a base station and a UE, and L2 signaling may refer to higher layer signaling between the base station and the UE based on Radio Resource Control (RRC)/medium access control-control element (MAC-CE).

The above-examined matters (3 GPP system, frame structure, NR system, etc.) may be applied in combination with the method proposed in the present disclosure to be described later, and/or may be supplemented to clarify technical characteristics of the method proposed in the present disclosure.

Additional advantages, objects, and features of the invention will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the disclosure. The objectives and other advantages of the disclosure will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.

In this disclosure, "a or B" may mean "a only", "B only" or "both a and B". In other words, in the present disclosure, "a or B" may be interpreted as "a and/or B". For example, in this disclosure, "A, B or C" may mean any combination of "a only", "B only", "C only" or "A, B, C".

Slash (/) or comma as used in this disclosure may mean "and/or". For example, "A/B" may mean "A and/or B". Thus, "a/B" may mean "a only", "B only" or "both a and B". For example, "A, B, C" may mean "A, B or C".

In the present disclosure, "at least one of a and B" may mean "a only", "B only", or "both a and B". In addition, in the present disclosure, the expression "at least one of a or B" or "at least one of a and/or B" may be interpreted as "at least one of a and B".

In addition, in the present disclosure, "at least one of A, B and C" may mean "a only", "B only", "C only", or "A, B and C in any combination. In addition, "at least one of A, B or C" or "A, B and/or at least one of C" may mean "at least one of A, B and C".

In addition, brackets used in this disclosure may mean "for example". Specifically, when "control information (PDCCH)" is indicated, the "PDCCH" may be proposed as an example of the "control information". In other words, the "control information" in the present disclosure is not limited to the "PDCCH", and the "PDCCH" may be proposed as an example of the "control information". In addition, even when "control information (i.e., PDCCH)" is indicated, the "PDCCH" may be proposed as an example of the "control information".

The technical features separately described in one drawing in the present disclosure may be implemented separately or simultaneously.

The following figures are prepared to illustrate specific examples of the disclosure. Since names of specific devices or specific signals/messages/fields described in the drawings are provided as examples, technical features of the present disclosure are not limited to specific names used in the following drawings.

The effects that can be achieved by the specific examples of the present disclosure are not limited to the listed effects. For example, there may be various technical effects that one of ordinary skill in the relevant art may understand or derive from the present disclosure. Thus, the specific effects of the present disclosure are not limited to those explicitly described in the present disclosure, and may include various effects that can be understood or deduced from the technical features of the present disclosure.

First, the first embodiment will be examined.

First embodiment

In this embodiment, a method of determining/configuring/defining a time domain window size for inter-slot bundling will be examined.

The methods described below are separated for convenience of explanation, and needless to say, the configuration of one method may be replaced by the configuration of another method or applied in combination with each other.

The method presented in this disclosure is described assuming PUSCH repetition, but is equally applicable to PUCCH repetition.

The definition of the time domain window size for inter-slot bundling is being discussed in RAN 1. Here, inter-slot bundling may mean continuous and/or discontinuous transmission occasions that guarantee phase and/or power continuity for the UE to be configured and transmit repeated joint channel estimation of PUSCH/PUCCH. In other words, inter-slot bundling may mean continuous and/or discontinuous transmission occasions that guarantee the same phase and transmission power for UEs configured and transmitting repeated PUSCH/PUCCHs. And/or, the inter-slot bundling may be referred to as DMRS bundling.

And/or the time domain window size for inter-slot bundling/inter-slot bundling may be a value reported according to the UE's capability or the UE's channel state. And/or the time domain window size for inter-slot bundling/inter-slot bundling may be a value indicated by the base station (e.g., gNB). If the base station so indicates, the following method can be considered.

(method 1-1)Indication via RRC/MAC-CE/DCI

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

If the time domain window size is a cell specific value, the time domain window size may be a value given semi-statically as Radio Resource Control (RRC)/medium access control-control element (MAC-CE) or the like.

If the time domain window size is a UE-specific value, the UE may be configured or receive a candidate list of time domain windows using RRC/MAC-CE or the like. And/or, the UE may be specified/indicated with a value corresponding to the UE through Downlink Control Information (DCI) in the list.

And/or the time domain window size may be received/configured through RRC signaling.

And/or, for dynamic indication, the time domain window and/or the time domain window size may be indicated by the DCI only. And/or, the 2N time domain windows may be indicated using N bits of DCI according to a pre-agreement.

(methods 1-2)-indication/configuration/determination based on repetition size

To indicate a relatively small time domain window in low repetition and a relatively large time domain window in high repetition, the time domain window may be indicated/configured/determined based on the number of repetitions. For example, the time domain window may be determined based on the duration of repeated consecutive time slots.

For example, when repetition is indicated N times, the time domain window may be indicated as a value by a value M agreed in advanceOr (b)Etc. Here, M may be indicated to the UE through RRC/MAC-CE/DCI or the like. Alternatively, M may be a UE-specific value or a cell-specific value.

(methods 1-3)-indication based on total number of time slots

The transmission of blocks (TBoMS) over multiple timeslots is currently being discussed in the coverage enhancement of RAN 1. Tboas may mean mapping one Transport Block (TB) to a plurality of slots. And/or tbomins may mean bundling of multiple transmission occasions or may be regarded as one transmission occasion, so one transmission may correspond to multiple time slots.

In this case, the time domain window for joint channel estimation/inter-slot bundling/DMRS bundling may be specified in the same manner as TBoMS units. And/or the time domain window may be specified by an operation in tbomins using the number of slots.

(methods 1-4)-frequency resource based classification/indication/configuration

For smooth operation in terms of resource management of a base station (e.g., a gNB), different joint channel estimation windows (or time domain windows) may be assigned according to frequency resources.

For example, different time domain windows and/or time domain window sizes and/or time domain window values may be indicated/configured/defined according to FR1 (frequency range 1) and FR2 (frequency range 2). And/or in additional detail, it is contemplated that the joint channel estimation window may be configured differently depending on the frequency band.

And/or the configuration of the time domain window according to the frequency may be performed implicitly or explicitly simultaneously with the configuration of the uplink-bandwidth part (UL-BWP) of the UE. For example, UL-BWP may be considered to include time domain window information for joint channel estimation/inter-slot bundling/DMRS bundling.

And/or, to multiplex UEs with the same hopping pattern, the time domain windows may be classified/indicated/configured based on frequency resources.

(methods 1-5)Adaptive architecture based on TDD architecture

Based on the slot format configuration of the UE, configurations of different numbers of time domain windows may be considered. In other words, it is contemplated that the configuration may be based on the number of downlink, flexible, and uplink slots in a subframe. This may be a value based on a slot format set by Radio Resource Control (RRC), or may be indicated by being included in a value indicated by DCI.

Second embodiment

In this embodiment, a method of configuring/defining inter-slot frequency hopping boundaries for inter-slot bundling will be examined.

The UE may be configured for inter-slot bundling/DMRS bundling, which performs joint channel estimation to improve channel estimation performance. And/or, in the case of being not configured for inter-slot bundling/DMRS bundling, the UE may transmit while maintaining phase, power, timing advance, etc. across multiple slots for inter-slot bundling/DMRS bundling by indicating to the base station (e.g., the gNB).

And/or, at the same time, the UE may be configured for inter-slot frequency hopping for channel diversity gain, etc. In this case, one of the two PRBs may be selected according to an existing inter-slot hopping rule, and transmission may be performed according to whether a slot index within a subframe is odd or even. This violates the conditions of joint channel estimation. In other words, the transmission characteristics may change in the time domain window.

Therefore, it is necessary to enhance this, and the second embodiment proposes the following method. Hereinafter, in the present disclosure, the "time domain window" may also be referred to as "CH window". And/or, "boundaries", "intervals" and "lengths" may be applied as alternatives to each other in this disclosure.

(method 2-1)-always determining that the hop interval is the same as the CH window.

The UE may determine that the time domain window for joint channel estimation/inter-slot bundling/DMRS bundling configured by the above method is equal to the frequency hopping boundary. The following can be considered as a method of doing so. When 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 opportunity may be determined by equations 4 to 5 replacing the predefined specification (e.g., 3gpp TS 38.214, sub-clauses 6.3.1, 6.3.2) with equation 6.

[ 6]

Here, if the time domain window W is configured by the above-described method, a corresponding value may be applied, and if not configured, RB may be determined/calculated based on w=1. And/or when the time domain window W is cell specific, a corresponding method may be applied.

And/or W may refer to the size of the time domain window. For example, W may be configured in units of slots. And/or W may be configured as a number of time slots.

(method 2-2)-configuring the hop interval as a multiple of the CH window size

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

In this case, a value W2 determining a hopping boundary indicating a cell-specific bundled UE may be additionally given. And/or W2 may be indicated to the UE as RRC/MAC-CE/DCI or the like. And/or when W2 is given as a single value, it may be given in the RRC connection phase of the UE.

And/or if the frequency hopping boundary of the UE is configured as a multiple of the time domain window, the multiple may be given. For example, if the time domain window of the UE is W, m is given, and the frequency hopping boundary may be configured/defined or obtained by a pre-agreed mw=w2. In this way, and the like, given W2, the Physical Resource Block (PRB) (or starting RB) of the UE's hopping transmission opportunity may be defined as in equation 7.

[ 7]

Hereinafter, in the present disclosure, the first to second embodiments or other embodiments will be examined from a standard perspective.

Hereinafter, the present disclosure may supplement all or part of the above-described embodiments (i.e., the first to second embodiments), or may be applied together with all or part of the embodiments, or may be applied by replacing all or part of the embodiments. Alternatively, hereinafter, the disclosure may be applied separately from the first to second embodiments.

In the present disclosure, "first to second embodiments" may be meant to include the contents/methods set forth below.

Regarding inter-slot frequency hopping and DMRS bundling, the remaining FFS points should also be discussed with respect to the convention in RANs 1#107-e as shown in table 8.

TABLE 8

First, it is necessary to define the determination of the hopping pattern. Both existing PUSCH and PUCCH are based on the same rule, but there are differences in what is described in the standard document.

For frequency hopping of PUSCH, when the slot index is even, a start RB is applied, and when the slot index is odd, an offset of the start RB is applied.

In case of PUCCH, startingPRB is applied if slot index is even, and secondHopPRB is applied if slot index is odd. I.e. the hopping is determined according to whether the physical slot index is even or odd. The frequency hopping is determined based on the physical slot index and, for simplicity, the same rules are preferably extended.

In addition, if the hopping boundaries between UEs are not aligned, all UEs performing frequency hopping occupy two RBs, which is not preferable in terms of resource management. In other words, a method of adjusting a hopping boundary between UEs in consideration of multi-user multiplexing is preferable. This is possible when the hopping pattern is determined by the physical slot index.

Thus, according to the method proposed in the present disclosure, the hopping pattern of inter-slot hopping may be determined only by the physical slot index.

Second, the determination of the frequency hopping patterns of PUCCH and PUSCH may need to be based on a unified approach. The use of only physical slot indices to define the hopping pattern can be used for multi-user multiplexing. To achieve this, the jump boundaries between users may need to be matched. However, since the configured Time Domain Windows (TDWs) of the PUSCH and the PUCCH are separately configured, the hopping windows (or TDWs) of the PUCCH and the PUSCH may be different. To address this, multi-user multiplexing may be achieved by not pairing different channels. That is, PUSCH and PUCCH may not be paired with each other.

Thus, according to the method proposed in the present disclosure, the hopping pattern determination of PUCCH and PUSCH may be based on the same rule. And/or, the sizes of the respective hopping windows of PUSCH and PUCCH may be the same or different according to the respective configurations.

It is agreed that separate RRC configurations are supported for the hopping interval and configured TDW length. In view of this, a specific method of determining the frequency hopping of the PUSCH is as follows.

When inter-slot hopping is configured and the hopping interval of the PUSCH W (e.g., hoppringintervalpusch) is configured, the th The Resource Blocks (RBs) of the transmission occasions in the slots may be configured by equation 8. That is, depending on whether the slot index divided by the hopping interval for joint channel estimation of PUSCH is even or odd, the start RB or the start rb+offset RB may be applied.

The same rule may be applied to PUCCH. That is, depending on whether the value of the slot index divided by the hopping interval (described as hopmingintervalpucch) for joint channel estimation of PUCCH is even or odd, startingPRB and secondHopPRB may have to be applied. At this time, if the configured TDW of the PUCCH is not configured according to the PUCCH format, a hopping interval for joint channel estimation of the PUCCH does not need to be configured for each format. As described above, it may be undesirable to have different boundaries for each format in view of multi-user multiplexing. Therefore, it is also possible that the hopping interval of the PUCCH must be applied regardless of the format.

The final FFS point is the default UE behavior when the hopping interval and TDW are not configured, but joint channel estimation and hopping is enabled. It is naturally believed that the operation of the UE is clear, since the default configured TDW values are defined even if neither the hopping interval nor the TDW length is configured. That is, when joint channel estimation is enabled without a hopping interval and configured TDW and hopping is indicated, the default configured TDW value may be the hopping interval.

Thus, according to the method proposed in the present disclosure, when joint channel estimation is enabled without a hopping interval and a configured TDW and frequency hopping is indicated, a default value of the configured TDW hopping interval may be applied as a default value of the hopping interval.

And/or, according to the methods presented in this disclosure, the following may be presented in a technical specification (e.g., 3gpp ts 38.214).

Frequency hopping of PUSCH repetition type a

In case of inter-slot frequency hopping, and when PUSCH-DMRS bundling is not enabled, in slotsDuring this period, the initial RB can be given by equation 8.

[ 8]

Here the number of the elements is the number,is the current slot number, RB, within a radio frame where a multislot PUSCH transmission may occur _start Is a resource block assignment from resource allocation type 1The starting RB in the UL BWP for information calculation (described in 3gpp TS38.214, clause 6.1.2.2.2). RB (radio bearer) _offset Is the frequency offset in RB between two hops.

In case of inter-slot frequency hopping, and when PUSCH-DMRS bundling is enabled, slotsThe initial RB of the period can be given by equation 9.

[ 9]

Here the number of the elements is the number,is the current slot number, RB, within a radio frame where a multislot PUSCH transmission may occur _start Is the starting RB in UL BWP calculated from the resource block assignment information of resource allocation type 1 (described in 3gpp TS38.214, clause 6.1.2.2.2). And RB (RB) _offset Is the frequency offset in RB between two hops.

And, if (configured) hopdingIntervalpusch, or if hopdingIntervalpusch is not configured, if PUSCH-timedomainWindowLength is not configured, or if PUSCH-timedomainWindowLength is not configured and hopdingIntervalpusch is not configured, then W may be calculated as min ([ maxdrs-BundlingDuration ], M). Here, M is the duration in consecutive slots of n·k PUSCH transmissions.

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 specification (e.g., 3gpp TS 38.214, clause 6.1.2.1).

In the case of PUSCH transmission of PUSCH repetition type B, n=1, and K is the nominal number of repetitions, as defined in a predefined specification (e.g., 3gpp TS 38.214, clause 6.1.2.1).

In the case of PUSCH transmission processed across TBs of multiple slots, N is the number of slots used for TBs determination, and K is the number of repetitions of the number of slots N used for TBs determination, as defined in a predefined specification (e.g., 3gpp TS 38.214, clause 6.1.2.1).

And/or, according to the methods presented in this disclosure, the following may be presented in a technical specification (e.g., 3gpp ts 38.213).

PUCCH repetition procedure

At the position ofIn the case of (a) the number of the cells,

UE cross-overThe PUCCH transmission is repeated in UCI for each slot.

-The PUCCH transmissions in each of the slots have the same number of consecutive symbols as provided by nrofSymbols.

-if subslotLengthForPUCCH is not providedThe PUCCH transmission in each of the slots has the same first symbol as provided by startingsymbol index. Otherwise, it has a sign per mod (startingSymbolIndex, subslotLengthForPUCCH).

Whether the UE performs frequency hopping for PUCCH transmissions in different slots may be configured by interlinearyhopping.

-when the UE is configured to perform frequency hopping for PUCCH transmissions across different slots and PUCCH-DMRS bundling is not enabled, the UE performs frequency hopping for individual slots. And/or the UE starts transmitting the PUSCCH from a first PRB provided by startingPRB in an even slot and starts transmitting the PUCCH from a second PRB provided by second hopprb in an odd slot. And/or the slot indicated to the UE for the first PUCCH transmission has number 0 and until the UE is inThe PUCCH is transmitted in each slot, and each subsequent slot is counted regardless of whether the UE transmits the PUCCH in the corresponding slot. And/or, it is not expected that the UE is configured to perform frequency hopping for PUCCH transmissions within a slot.

-when the UE is configured to perform frequency hopping for PUCCH transmissions across different slots and PUCCH-DMRS bundling is enabled, the UE performs frequency hopping every W slots. Here, if (configured) hopingintelvalpucch, or if hopingintelvalpucch is not configured, if PUCCH-TimeDomainWindowLength is (configured), or if TimeDomainWindowLength is not configured and hopingintelvalpucch is not configured, W may be calculated as min ([ maxDMRS-bundling duration)]M). Here, M is a duration in consecutive slots from a first slot in which PUCCH transmission for PUCCH repetition is determined to a last slot in which PUCCH transmission for PUCCH repetition is determined. And/or the UE is atOn the first PRB provided for startingPRB in even slots and +.>The PUCCH is transmitted on a second PRB provided for the second condhopprb in the odd slots. Here, a->Is the current slot number within the radio frame. The slot indicated to the UE for the first PUCCH transmission has the number 0 and until the UE is +.>The PUCCH is transmitted in each slot, and each subsequent slot is counted regardless of whether the UE transmits the PUCCH in the corresponding slot. And/or, it is not expected that the UE is configured to perform frequency hopping for PUCCH transmissions within a slot.

-if the UE is not configured to perform frequency hopping for PUCCH transmissions across different slots, and if the UE 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.

And/or there are conventions in RANs 1#104b-e as shown in table 9 with respect to frequency hopping with inter-slot bundling.

TABLE 9

Option 2 is naturally supported in view of the RAN1#107-e convention arranged in the order of the TDW determination configured "hop interval determination" - > "and the actual TDW determination". It is also necessary to organize FFS points. That is, the bundling size and the time-domain hopping interval are explicitly and independently configured, and the bundling size is not separately configured for FDD and TDD.

According to the methods presented in this disclosure, the bundling size may be the same as or different from the time domain window size.

Referring to fig. 11, first, in step S1101, a UE (100/200 in fig. 13 to 16) may receive configuration information related to a time domain window from a base station. For example, the configuration information may include information about the length/boundary/interval of the time domain window.

And/or the time domain window may include one or more time domain windows. Alternatively, the time domain window may be replaced by 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.

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.

And/or the same phase and transmission power may be maintained/guaranteed within the time domain window.

And/or, the time domain window may be configured based on the number of PUSCH repeated transmissions. For example, when the number of times of PUCCH repeated transmission is configured/indicated as "N", the length of the time domain windowCan be indicated/determined/configured as +.>Here, "M" may be a preconfigured 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.

For example, the operation of the UE receiving the configuration information in step S1101 may be implemented by the apparatus of fig. 13 to 16 described above. For example, referring to FIG. 14, one or more processors 102/202 may control one or more memories 104/204 and/or one or more transceivers 106/206, etc. to receive the configuration information.

And/or, in step S1102, the UE (100/200 in fig. 13 to 16) may receive Downlink Control Information (DCI) including scheduling information for PUSCH and frequency hopping information for PUSCH from the base station. And/or PUSCH repetition transmission may be scheduled through DCI.

For example, the scheduling information may include information related to time resources and/or information related to frequency resources. And/or, the hopping information may be information indicating PUSCH hopping. For example, the UE may transmit PUSCH in the first frequency hopping and the second frequency hopping based on the frequency hopping information.

And/or PUSCH may be transmitted (based on DCI) on multiple slots based on frequency hopping.

The method of operation of fig. 11 is focused on the example described by DCI indicating frequency hopping, but frequency hopping may be configured/indicated in various ways. For specific details in this regard, reference may be made to the disclosure above.

For example, the operation of the UE receiving DCI in step S1102 may be implemented by the apparatus of fig. 13 to 16 described above. For example, referring to FIG. 14, one or more processors 102/202 may control one or more memories 104/204 and/or one or more transceivers 106/206, etc. to receive DCI.

And/or, in step S1103, the UE (100/200 in fig. 13 to 16) may transmit PUSCH to the base station in a first frequency hopping having the same length/boundary/interval as the first time domain window.

For example, the operation of the UE transmitting PUSCH in step S1103 may be implemented by the apparatus of fig. 13 to 16 described above. For example, referring to FIG. 14, one or more processors 102/202 may control one or more memories 104/204 and/or one or more transceivers 106/206, etc. to transmit PUSCH.

And/or, in step S1104, the UE (100/200 in fig. 13 to 16) may transmit PUSCH to the base station in a second frequency hopping having the same length/boundary/interval as the second time domain window. And/or the first frequency hop may be an even hop and the second frequency hop may be an odd hop.

For example, the length/interval/boundary of the first frequency hop may be configured to be the same as the first time domain window. And/or the length/spacing/boundary of the second frequency hop may be configured to be the same as the second time domain window.

And/or the boundary of the first frequency hopping may be the same as the first time domain window. And/or the boundary of the second frequency hopping may be the same as the second time domain window.

And/or the length/interval/boundary of the first frequency hop and the second frequency hop may be determined based on the length/interval/boundary of the time domain window and the slot number within the radio frame. And/or a starting Resource Block (RB) of the second frequency hopping may be determined based on the starting RB of the first frequency hopping and the frequency offset.

And/or time slots for PUSCHThe starting Resource Block (RB) of the period may be determined based on the following equation.

[ type ]

Wherein RB is _start Initial RB, which may represent the first frequency hopping _offset A frequency offset between the first frequency hop and the second frequency hop may be represented, The size of an uplink bandwidth portion (BWP) may be represented, and W may represent the length of a time domain window.

For example, the operation of the UE transmitting PUSCH in step S1104 may be implemented by the apparatus of fig. 13 to 16 described above. For example, referring to FIG. 14, one or more processors 102/202 may control one or more memories 104/204 and/or one or more transceivers 106/206, etc. to transmit PUSCH.

The method of operation of fig. 11 is described focusing on PUSCH transmission, but it is needless to say that it is also applicable to PUCCH.

Since the operation of the UE described with reference to fig. 11 is the same as that of the UE described with reference to fig. 1 to 10 (e.g., first to second embodiments), the other detailed description is omitted.

The above-described signaling and operations may be implemented by an apparatus (e.g., fig. 13 to 16) to be described below. For example, the above-described signaling and operations may be processed by one or more processors of fig. 13-16, and the above-described signaling and operations may be stored in a memory in the form of instructions/programs (e.g., instructions, executable code) for driving at least one processor of fig. 13-16.

For example, a processing device configured to control a User Equipment (UE) to transmit PUSCH in a wireless communication system is proposed, the processing device may comprise at least one processor and at least one memory operatively connected to the at least one processor and storing instructions that, based on execution by the at least one processor, perform operations, wherein the operations may comprise: receiving configuration information related to a time domain window from a base station; receiving DCI including scheduling information for PUSCH and frequency hopping information for PUSCH from a base station; transmitting PUSCH to the base station in a first frequency hopping having the same length as the first time domain window; and transmitting the PUSCH to the base station in a second frequency hopping having the same length as the second time domain window.

For example, a computer-readable storage medium storing at least one instruction is presented, wherein the at least one instruction, based on execution by at least one processor, causes the at least one processor to control operations, wherein the operations may include: receiving configuration information related to a time domain window from a base station; receiving DCI including scheduling information for PUSCH and frequency hopping information for PUSCH from a base station; transmitting PUSCH to the base station in a first frequency hopping having the same length as the first time domain window; and transmitting the PUSCH to the base station in a second frequency hopping having the same length as the second time domain window.

Referring to fig. 12, first, in step S1201, a base station (100/200 in fig. 13 to 16) may transmit configuration information related to a time domain window to a UE. For example, the configuration information may include information about the length/boundary/interval of the time domain window.

For example, the operation of the base station transmitting the configuration information in step S1201 may be implemented by the apparatus of fig. 13 to 16 described above. For example, referring to FIG. 14, one or more processors 102/202 may control one or more memories 104/204 and/or one or more transceivers 106/206, etc. to transmit configuration information.

And/or, in step S1202, the base station (100/200 in fig. 13 to 16) may transmit Downlink Control Information (DCI) including scheduling information for PUSCH and frequency hopping information for PUSCH to the UE. And/or PUSCH repetition transmission may be scheduled through DCI.

For example, the scheduling information may include information related to time resources and/or information related to frequency resources. And/or, the hopping information may be information indicating PUSCH hopping. For example, the base station may receive PUSCH in the first frequency hopping and the second frequency hopping based on the frequency hopping information.

And/or PUSCH may be received (based on DCI) on multiple slots based on frequency hopping.

The method of operation of fig. 12 is focused on the example described by DCI indicating frequency hopping, but frequency hopping may be configured/indicated in various ways. For specific details in this regard, reference may be made to the disclosure above.

For example, the operation of the base station transmitting DCI in step S1202 may be implemented by the apparatus of fig. 13 to 16 described above. For example, referring to FIG. 14, one or more processors 102/202 may control one or more memories 104/204 and/or one or more transceivers 106/206, etc. to transmit DCI.

And/or, in step S1203, the base station (100/200 in fig. 13 to 16) may receive PUSCH from the UE in a first frequency hopping having the same length/boundary/interval as the first time domain window.

For example, the operation of the base station to receive PUSCH in step S1203 may be implemented by the apparatus of fig. 13 to 16 described above. For example, referring to FIG. 14, one or more processors 102/202 may control one or more memories 104/204 and/or one or more transceivers 106/206, etc. to receive the PUSCH.

And/or, in step S1204, the base station (100/200 in fig. 13 to 16) may receive PUSCH from the UE in a second frequency hopping having the same length/boundary/interval as the second time domain window. And/or the first frequency hop may be an even hop and the second frequency hop may be an odd hop.

For example, the length/interval/boundary of the first frequency hop may be configured to be the same as the first time domain window. And/or the length/spacing/boundary of the second frequency hop may be configured to be the same as the second time domain window. For example, the boundary of the first frequency hop may be the same as the first time domain window. And/or the boundary of the second frequency hopping may be the same as the second time domain window.

[ type ]

Wherein RB is _start Initial RB, which may represent the first frequency hopping _offset A frequency offset between the first frequency hop and the second frequency hop may be represented, The size of an uplink bandwidth portion (BWP) may be represented, and W may represent the length of a time domain window. />

For example, the operation of the base station to receive PUSCH in step S1204 may be implemented by the apparatus of fig. 13 to 16 described above. For example, referring to FIG. 14, one or more processors 102/202 may control one or more memories 104/204 and/or one or more transceivers 106/206, etc. to receive the PUSCH.

The method of operation in fig. 12 is described focusing on PUSCH transmission, but it is needless to say that it is also applicable to PUCCH.

Since the operation of the base station described with reference to fig. 12 is the same as that of the base station described with reference to fig. 1 to 11 (for example, the first to second embodiments), the other detailed description is omitted.

For example, a processing device configured to control a base station to receive PUSCH in a wireless communication system is proposed, which may comprise at least one processor and at least one memory operatively connected to the at least one processor and storing instructions that, based on execution by the at least one processor, perform operations, wherein the operations may comprise: transmitting configuration information related to a time domain window to a User Equipment (UE); transmitting DCI including scheduling information for PUSCH and frequency hopping information for PUSCH to the UE; receiving PUSCH from the UE in a first frequency hopping having the same length as the first time domain window; and receiving a PUSCH from the UE in a second frequency hopping having the same length as the second time domain window.

For example, a computer-readable storage medium storing at least one instruction is presented, wherein the at least one instruction, based on execution by at least one processor, causes the at least one processor to control operations, wherein the operations may include: transmitting configuration information related to a time domain window to a User Equipment (UE); transmitting DCI including scheduling information for PUSCH and frequency hopping information for PUSCH to the UE; receiving PUSCH from the UE in a first frequency hopping having the same length as the first time domain window; and receiving a PUSCH from the UE in a second frequency hopping having the same length as the second time domain window.

Examples of communication systems applicable to the present disclosure

The various descriptions, functions, procedures, proposals, methods and/or operational flowcharts of the present disclosure described in this document may be applied to, but are not limited to, various fields in which wireless communication/connection (e.g., 5G) between devices is required.

Hereinafter, a description will be given in more detail with reference to the accompanying drawings. In the following figures/descriptions, like reference numerals may designate like or corresponding hardware, software, or functional blocks unless otherwise described.

Fig. 13 shows a communication system 1 applied to the present disclosure.

Referring to fig. 13, a communication system 1 applied to the present disclosure includes a wireless device, a Base Station (BS), and a network. Herein, a wireless device refers to a device that performs communication using a Radio Access Technology (RAT) (e.g., 5G New RAT (NR)) or Long Term Evolution (LTE)), and may be referred to as a communication/radio/5G device. Wireless devices may include, but are not limited to, robots 100a, vehicles 100b-1 and 100b-2, augmented reality (XR) devices 100c, handheld devices 100d, home appliances 100e, internet of things (IoT) devices 100f, and Artificial Intelligence (AI) devices/servers 400. For example, the vehicles may include vehicles having wireless communication functions, autonomously driven vehicles, and vehicles capable of performing communication between the vehicles. Herein, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., an unmanned aerial vehicle). XR devices may include Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) devices, and may be implemented in the form of head-mounted devices (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, and the like. The handheld devices may include smart phones, smart boards, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebooks). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, the BS and network may be implemented as wireless devices, and a particular wireless device 200a may operate as a BS/network node with respect to other wireless devices.

The wireless devices 100a to 100f may connect to the network 300 via the BS 200. AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may connect to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other through the BS 200/network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without going through the BS/network. For example, the vehicles 100b-1 and 100b-2 may perform direct communications (e.g., vehicle-to-vehicle (V2V)/vehicle-to-everything (V2X) communications). The IoT devices (e.g., sensors) may perform direct communications with other IoT devices (e.g., sensors) or other wireless devices 100 a-100 f.

Wireless communication/connection 150a, 150b, or 150c may be established between wireless devices 100 a-100 f/BS200 or BS200/BS 200. Herein, wireless communication/connection may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication 150a, side link communication 150b (or D2D communication), or inter-BS communication (e.g., relay, integrated Access Backhaul (IAB)). The wireless device and BS/wireless device may transmit/receive radio signals to/from each other through wireless communication/connections 150a and 150 b. For example, wireless communication/connections 150a and 150b may transmit/receive signals over various physical channels. To this end, at least a portion of various configuration information configuration processes, various signal processing processes (e.g., channel coding/decoding, modulation/demodulation, and resource mapping/demapping) and resource allocation processes for transmitting/receiving radio signals may be performed based on various proposals of the present disclosure.

Examples of wireless devices applied to the present disclosure

Referring to fig. 14, the first and second wireless devices 100 and 200 may transmit radio signals through various RATs (e.g., LTE and NR). Herein, { first wireless device 100 and second wireless device 200} may correspond to { wireless device 100x and BS200} and/or { wireless device 100x and wireless device 100x } of fig. 13.

The first wireless device 100 may include one or more processors 102 and one or more memories 104, and additionally include one or more transceivers 106 and/or one or more antennas 108. The processor 102 may control the memory 104 and/or the transceiver 106 and may be configured to implement the descriptions, functions, procedures, proposals, methods and/or operational flowcharts disclosed in this document. For example, the processor 102 may process the information within the memory 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver 106. The processor 102 may receive a radio signal including the second information/signal through the transceiver 106 and then store information obtained by processing the second information/signal in the memory 104. The memory 104 may be connected 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 executing some or all of the processes controlled by the processor 102 or for executing descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in this document. Herein, the processor 102 and the memory 104 may be part of a communication modem/circuit/chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be coupled to the processor 102 and transmit and/or receive radio signals via one or more antennas 108. Each transceiver 106 may include a transmitter and/or a receiver. The transceiver 106 may be used interchangeably with a Radio Frequency (RF) unit. In this disclosure, a wireless device may represent a communication modem/circuit/chip.

The second wireless device 200 may include one or more processors 202 and one or more memories 204, and additionally include one or more transceivers 206 and/or one or more antennas 208. The processor 202 may control the memory 204 and/or the transceiver 206 and may be configured to implement the descriptions, functions, procedures, proposals, methods and/or operational flowcharts disclosed in this document. For example, the processor 202 may process the information within the memory 204 to generate a third information/signal and then transmit a radio signal including the third information/signal through the transceiver 206. The processor 202 may receive a radio signal including the fourth information/signal through the transceiver 206 and then store information obtained by processing the fourth information/signal in the memory 204. The memory 204 may be connected 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 executing some or all of the processes controlled by the processor 202 or for executing descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in this document. Herein, the processor 202 and the memory 204 may be part of a communication modem/circuit/chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and/or receive radio signals through one or more antennas 208. Each transceiver 206 can include a transmitter and/or a receiver. The transceiver 206 may be used interchangeably with a Radio Frequency (RF) unit. In this disclosure, a wireless device may represent a communication modem/circuit/chip.

Hereinafter, hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by, but are not limited to, one or more processors 102 and 202. For example, one or more of processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC and SDAP). The one or more processors 102 and 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, proposals, methods and/or operational flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information in accordance with the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document.

One or more of the processors 102 and 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more of the processors 102 and 202 may be implemented 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 and 202. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, procedures or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods and/or operational flow diagrams disclosed in this document may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, suggestions, methods and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, commands and/or command sets.

One or more memories 104 and 204 may be coupled to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. One or more of the memories 104 and 204 may be configured by read-only memory (ROM), random Access Memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, a hard drive, registers, cache memory, a computer-readable storage medium, and/or combinations thereof. The one or more memories 104 and 204 may be located internal and/or external to the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 by various techniques, such as a wired or wireless connection.

One or more transceivers 106 and 206 may transmit the user data, control information, and/or radio signals/channels referred to in the methods and/or operational flow diagrams of this document to one or more other devices. One or more transceivers 106 and 206 may receive the user data, control information, and/or radio signals/channels mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control such that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control such that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to transmit and receive the user data, control information, and/or radio signals/channels mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document through one or more antennas 108 and 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 and 206 may convert received radio signals/channels, etc., from RF band signals to baseband signals for processing received user data, control information, radio signals/channels, etc., using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert user data, control information, radio signals/channels, etc., processed using the one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more of the transceivers 106 and 206 may include (analog) oscillators and/or filters.

Application examples applied to wireless devices of the present disclosure

Fig. 15 shows another example of a wireless device applied to the present disclosure. Wireless devices may be implemented in various forms depending on the use case/service.

Referring to fig. 15, wireless devices 100 and 200 may correspond to wireless devices 100 and 200 of fig. 14 and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional component 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include one or more processors 102 and 202 and/or one or more memories 104 and 204 of fig. 14. For example, transceiver 114 may include one or more transceivers 106 and 206 and/or one or more antennas 108 and 208 of fig. 14. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional components 140, and controls the overall operation of the wireless device. For example, the control unit 120 may control the electrical/mechanical operation of the wireless device based on programs/codes/commands/information stored in the memory unit 130. The control unit 120 may transmit information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless/wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 through a wireless/wired interface in the memory unit 130.

The additional components 140 may be configured differently depending on the type of wireless device. For example, the additional component 140 may include at least one of a power supply unit/battery, an input/output (I/O) unit, a driving unit, and a computing unit. The wireless device may be implemented in the form of, but not limited to, a robot (100 a of fig. 13), a vehicle (100 b-1 and 100b-2 of fig. 13), an XR device (100 c of fig. 13), a handheld device (100 d of fig. 13), a home appliance (100 e of fig. 13), an IoT device (100 f of fig.), a digital broadcast terminal, a holographic device, a public safety device, an MTC device, a medical device, a financial technological device (or financial device), a security device, a climate/environment device, an AI server/device (400 of fig. 13), a BS (200 of fig. 13), a network node, etc. The wireless device may be used in a mobile or fixed location depending on the use case/service.

In fig. 15, various elements, components, units/portions and/or modules in wireless devices 100 and 200 may all be connected to each other through wired interfaces, or at least a portion thereof may be connected wirelessly through communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be connected by wire, and the control unit 120 and the first unit (e.g., 130 and 140) may be connected wirelessly through the communication unit 110. The various elements, components, units/portions and/or modules within wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured by a set of one or more processors. As an example, the control unit 120 may be configured by a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphics processing unit, and a memory control processor. As another example, the memory unit 130 may be configured by Random Access Memory (RAM), dynamic RAM (DRAM), read Only Memory (ROM), flash memory, volatile memory, non-volatile memory, and/or combinations thereof.

Examples of hand-held devices applied to the present disclosure

Fig. 16 shows a hand-held device applied to the present disclosure. The handheld device may include a smart phone, a smart pad, a wearable device (e.g., a smart watch or smart glasses), or a portable computer (e.g., a notebook). A handheld 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).

Referring to fig. 16, the handheld 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 I/O unit 140c. The antenna unit 108 may be configured as part of the communication unit 110. Blocks 110 through 130/140a through 140c correspond to blocks 110 through 130/140, respectively, of fig. 15.

The communication unit 110 may transmit and receive signals (e.g., data and control signals) to and from other wireless devices or BSs. The control unit 120 may perform various operations by controlling constituent elements of the handheld device 100. The control unit 120 may include an Application Processor (AP). The memory unit 130 may store data/parameters/programs/codes/commands required to drive the handheld device 100. The memory unit 130 may store input/output data/information. The power supply unit 140a may supply power to the handheld device 100 and include a wired/wireless charging circuit, a battery, and the like. The interface unit 140b may support connection of the handheld device 100 to other external devices. The interface unit 140b may include various ports (e.g., an audio I/O port and a video I/O port) for connection with external devices. The I/O unit 140c may input or output video information/signals, audio information/signals, data, and/or information input by a user. The I/O unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and/or a haptic module.

As an example, in the case of data communication, the I/O unit 140c may acquire information/signals (e.g., touch, text, voice, image, or video) input by the user, and the acquired information/signals may be stored in the memory unit 130. The communication unit 110 may convert information/signals stored in the memory into radio signals and transmit the converted radio signals directly to other wireless devices or to the BS. The communication unit 110 may receive radio signals from other wireless devices or BSs and then restore the received radio signals to original information/signals. The recovered information/signals may be stored in the memory unit 130 and may be output as various types (e.g., text, voice, image, video, or haptic) through the I/O unit 140.

Here, the wireless communication technology implemented in the wireless devices 100 and 200 of the present disclosure may include narrowband internet of things for low power communication, and LTE, NR, and 6G. In this case, for example, the NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented in standards such as LTE Cat NB1 and/or LTE Cat NB2, but is not limited to the names described above. Additionally or alternatively, wireless communication techniques implemented in wireless devices 100 and 200 of the present disclosure may perform communications based on LTE-M techniques. In this case, as an example, the LTE-M technology may be an example of the LPWAN technology, and may be referred to by various names such as enhanced machine type communication (eMTC). For example, LTE-M technology may be implemented as at least any of a variety of standards, such as, but not limited to, 1) LTE CAT 0, 2) LTE CAT M1, 3) LTE CAT M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE machine type communications, and/or 7) LTE M. Additionally or alternatively, wireless communication techniques implemented in wireless devices 100 and 200 of the present disclosure may include at least any one of ZigBee, bluetooth, and Low Power Wide Area Network (LPWAN) that allows for low power communications, but are not limited to the above names. For example, zigBee technology may create Personal Area Networks (PANs) related to small/low power digital communications based on various standards such as IEEE 802.15.4 and may be referred to by various names.

The above-described embodiments are achieved by a combination of components and features of the present disclosure in a predetermined form. Individual components or features should be considered selectively unless indicated otherwise. Individual components or features may be implemented without being combined with another component or feature. Further, some components and/or features are combined with each other and embodiments of the present disclosure may be implemented. The order of operations described in embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced by corresponding components or features of another embodiment. It will be apparent that some claims referring to specific claims may be combined with other claims referring to claims other than the specific claims to constitute an embodiment or add new claims by modification after filing the application.

Embodiments of the present disclosure may be implemented by various means, such as hardware, firmware, software, or combinations thereof. When the embodiments are implemented in hardware, one embodiment of the disclosure 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.

When the embodiments are implemented in firmware or software, one embodiment of the present disclosure may be implemented by a module, process, function, etc. that performs the above-described functions or operations. The software codes may be stored in a memory and may be driven by a processor. The memory is provided within or external to the processor and can exchange data with the processor by various well-known means.

It will be apparent to those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the essential characteristics thereof. The foregoing detailed description is, therefore, not to be construed as limiting in all aspects, but rather as illustrative. The scope of the present disclosure should be determined by a fair interpretation of the accompanying claims, and all modifications that come within the equivalent scope of the present disclosure are intended to be included in the scope of the present disclosure.

Industrial applicability

The method of transmitting and receiving a PSSCH in a wireless communication system of the present disclosure is mainly described as an example applied to a 3GPP LTE/LTE-a system and a 5G system (new RAT system), but in addition, it is applicable to various wireless communication systems such as a Beyond 5G, 6G, and Beyond 6G.

Claims

1. A method of transmitting a physical uplink shared channel, PUSCH, in a wireless communication system, the method performed by a user equipment, UE, comprising the steps of:

Receiving configuration information related to 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 hopping having the same length as a first time domain window; and

the PUSCH is transmitted to the base station in a second frequency hop having the same length as the second time domain window.

2. The method of claim 1, wherein the length of the first frequency hop and the length of the second frequency hop are determined based on a length of the time domain window and a slot number within a radio frame.

3. The method of claim 2, wherein the starting resource block, RB, of the second frequency hopping is determined based on the starting RB of the first frequency hopping and a frequency offset.

4. A method according to claim 3, wherein the first frequency hop is an even hop and the second frequency hop is an odd hop.

5. The method of claim 1, wherein a slot n for the PUSCH _s ^μ The starting resource block RB of the period is determined based on the following equation,

[ type ]

Wherein RB is _start A start RB, representing the first frequency hopping _offset Representing a frequency offset, N, between the first frequency hop and the second frequency hop _bwp ^size The size of the uplink bandwidth portion BWP is represented and W represents the length of the time domain window.

6. The method of claim 1, wherein the time domain window is a time domain window for demodulation reference signal, DMRS, bundling.

7. The method of claim 6, wherein the same phase and transmission power are maintained within the time domain window.

8. The method of claim 1, wherein the time domain window is configured based on a number of PUSCH repetition transmissions.

9. The method of claim 1, wherein the PUSCH is transmitted on a frequency hopping basis over a plurality of slots.

10. A user equipment, UE, configured to transmit a physical uplink shared channel, PUSCH, in a wireless communication system, the UE comprising:

at least one transceiver;

at least one processor; and

at least one memory operatively connected to the at least one processor and storing instructions that, based on execution by the at least one processor, perform operations,

wherein the operations include:

11. A method of receiving a physical uplink shared channel, PUSCH, in a wireless communication system, the method performed by a base station comprising the steps of:

transmitting configuration information related to a time domain window to User Equipment (UE);

transmitting Downlink Control Information (DCI) including scheduling information for the PUSCH and frequency hopping information for the PUSCH to the UE;

receiving the PUSCH from the UE in a first frequency hopping having the same length as a first time domain window; and

the PUSCH is received from the UE in a second frequency hopping having the same length as a second time domain window.

12. The method of claim 11, wherein the starting resource block, RB, of the second frequency hopping is determined based on the starting RB of the first frequency hopping and a frequency offset.

13. The method of claim 12, wherein the first frequency hop is an even hop and the second frequency hop is an odd hop.

14. The method of claim 11, wherein a slot n for the PUSCH _s ^μ The starting resource block RB of the period is determined based on the following equation,

[ type ]

15. The method of claim 11, wherein the time domain window is a time domain window for demodulation reference signal, DMRS, bundling.

16. The method of claim 15, wherein the same phase and transmission power are maintained within the time domain window.

17. The method of claim 11, wherein the time domain window is configured based on a number of PUSCH repeated transmissions.

18. A base station configured to receive a physical uplink shared channel, PUSCH, in a wireless communication system, the base station comprising:

at least one transceiver;

at least one processor; and

wherein the operations include:

19. A processing device configured to control a user equipment, UE, to transmit a physical uplink shared channel, PUSCH, in a wireless communication system, the processing device comprising:

at least one processor; and

wherein the operations include:

20. A computer-readable storage medium storing at least one instruction, wherein the at least one instruction, based on execution by at least one processor, causes the at least one processor to control operations,

wherein the operations include:

receiving Downlink Control Information (DCI) including scheduling information for a Physical Uplink Shared Channel (PUSCH) and frequency hopping information for the PUSCH from the base station;