WO2020166843A1

WO2020166843A1 - Method whereby user equipment receives data signal on basis of initial connection to base station in wireless communication system, and user equipment and base station which support same

Info

Publication number: WO2020166843A1
Application number: PCT/KR2020/001099
Authority: WO
Inventors: 이길봄; 강지원; 김형태
Original assignee: 엘지전자 주식회사
Priority date: 2019-02-15
Filing date: 2020-01-22
Publication date: 2020-08-20

Abstract

Disclosed are a method whereby user equipment receives a data signal in a wireless communication system, and devices which support same. According to one embodiment applicable to the present disclosure, user equipment can establish a connection with a base station on the basis of a synchronization signal/physical broadcast channel (SS/PBCH) block received from the base station. Further, on the basis of (i) configuration information related to dynamic bundling for a precoding resource block (PRB) and (ii) control information for scheduling a first physical downlink shared channel (PDSCH), both pieces of information being received from the base station, the user equipment can receive a data signal via the first PDSCH on the basis of an assumption related to the first PDSCH.

Description

A method for receiving data signals by a terminal based on initial access to a base station in a wireless communication system, and a terminal and a base station supporting the same

The following description is for a wireless communication system, in which a terminal performs an initial access to a base station in a wireless communication system, and one or more physical downlink shared channels (PDSCHs) from one or more transmission reception points (TRPs) based on the initial access. The present invention relates to a method of operating a terminal and a base station related to an operation of receiving a data signal through and an apparatus supporting the same.

Wireless access systems have been widely deployed to provide various types of communication services such as voice and data. In general, a wireless access system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of multiple access systems include a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, and a single carrier frequency (SC-FDMA) system. division multiple access) system.

In particular, as more communication devices require a larger communication capacity, an improved mobile broadband communication technology compared to the existing radio access technology (RAT) has been proposed. In addition, a communication system considering a service/UE sensitive to reliability and latency as well as Massive MTC (Machine Type Communications) that provides various services anytime, anywhere by connecting a plurality of devices and objects has been proposed. Accordingly, improved mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) have been introduced, and various technical configurations for this have been proposed.

An object of the present disclosure is to provide a method of receiving a data signal by a terminal based on initial access to a base station in a wireless communication system and apparatuses supporting the same.

The technical objectives to be achieved in the present disclosure are not limited to those mentioned above, and other technical problems that are not mentioned are common knowledge in the technical field to which the technical configuration of the present disclosure is applied from the embodiments of the present disclosure to be described below. Can be considered by those who have.

The present disclosure provides a method of receiving a data signal by a terminal based on initial access to a base station in a wireless communication system and apparatuses supporting the same.

As an example of the present disclosure, in a method of receiving a data signal of a terminal in a wireless communication system, a synchronization signal including a synchronization signal (SS) and a physical broadcast channel (PBCH) from a base station / physical broadcast channel ( SS/PBCH) block; Performing an access procedure to the base station including transmission of a random access channel (RACH) preamble based on the received SS/PBCH block; Receiving, from the base station, configuration information related to dynamic bundling for a precoding resource block (PRB); Receiving, from the base station, first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH); Based on the configuration information and the first DCI, (i) there is no other PDSCH overlapping the first PDSCH in the time domain and the frequency domain, or (ii) the first PDSCH in the time domain and the frequency domain If there is a second PDSCH overlapping with, it is assumed that the first PDSCH and the second PDSCH in the frequency domain overlap in units of a precoding resource block group (PRB group) having the same size; And receiving the data signal through the first PDSCH based on the assumption.

In the present disclosure, when the terminal receives the data signal through the first PDSCH based on the assumption, the terminal receives the data signal through the first PDSCH based on the assumption-based interference channel estimation. It may include receiving the data signal.

In the present disclosure, the setting information may include one of the following.

-First bundling size setting information indicating that the size of the dynamic bundling is 2 PRB

-Second bundling size setting information indicating that the size of the dynamic bundling is 4 PRB

-3rd bundling size setting information indicating that the size of the dynamic bundling is wideband

In the present disclosure, the second PDSCH may be scheduled for (i) the terminal or (ii) another terminal.

In the present disclosure, the method of receiving a data signal of the terminal comprises: receiving a second DCI scheduling the second PDSCH from the base station; And receiving the data signal through the second PDSCH based on the configuration information and the assumption based on the second DCI.

In this case, the first PDSCH and the second PDSCH may be respectively received from different transmission reception points (TRPs).

In the present disclosure, the terminal may expect that the size of a resource block group (RBG) for the first PDSCH is greater than or equal to the size of the PRG for the first PDSCH.

In the present disclosure, based on the size of a resource block group (RBG) for the first PDSCH, the UE may expect candidate values of the PRG size for the first PDSCH.

In this case, as an example, based on the RGB size for the first PDSCH such as 2, the terminal indicates that the candidate values of the PRG size for the first PDSCH include 2 PRBs, 4PRBs, and a wideband. Can be expected.

As another example, based on the RGB size for the first PDSCH equal to or greater than 4, the terminal may expect that candidate values of the PRG size for the first PDSCH include 4PRB and a wideband.

In the present disclosure, the method of receiving a data signal by the terminal may further include transmitting acknowledgment information related to the data signal to the base station.

As another example of the present disclosure, in a terminal for receiving a data signal in a wireless communication system, at least one transmitter; At least one receiver; At least one processor; And at least one memory that is operatively connected to the at least one processor and stores instructions for causing the at least one processor to perform a specific operation when executed, wherein the specific operation is: from a base station Receiving a synchronization signal/physical broadcast channel (SS/PBCH) block including a sync signal (SS) and a physical broadcast channel (PBCH); Performing an access procedure to the base station including transmission of a random access channel (RACH) preamble based on the received SS/PBCH block; Receiving, from the base station, configuration information related to dynamic bundling for a precoding resource block (PRB); Receiving, from the base station, first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH); Based on the configuration information and the first DCI, (i) there is no other PDSCH overlapping the first PDSCH in the time domain and the frequency domain, or (ii) the first PDSCH in the time domain and the frequency domain If there is a second PDSCH overlapping with, it is assumed that the first PDSCH and the second PDSCH in the frequency domain overlap in units of a precoding resource block group (PRB group) having the same size; And receiving the data signal through the first PDSCH based on the assumption.

In the present disclosure, the terminal may communicate with at least one of a mobile terminal, a network, and an autonomous vehicle other than a vehicle including the terminal.

As another example of the present disclosure, a base station for transmitting a data signal in a wireless communication system, comprising: at least one transmitter; At least one receiver; At least one processor; And at least one memory that is operatively connected to the at least one processor and stores instructions for causing the at least one processor to perform a specific operation when executed, wherein the specific operation is: Transmitting a synchronization signal / physical broadcast channel (SS/PBCH) block including a sync signal (SS) and a physical broadcast channel (PBCH); Performing a connection establishment procedure with the terminal based on the transmitted SS/PBCH block; Transmitting configuration information related to dynamic bundling for a precoding resource block (PRB) to the terminal; To the terminal, (i) first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH) and (ii) a second for scheduling a second PDSCH Transmit DCI; And transmitting the first PDSCH and the second PDSCH to the terminal, and based on the configuration information, the first DCI, and the second DCI: The first PDSCH and the second PDSCH are in a time domain and When set not to overlap on the frequency domain, or when the first PDSC and the second PDSCH on the time domain and the frequency domain overlap, the first PDSCH and the second PDSCH on the frequency domain are of the same size. It may be set to overlap in units of a precoding resource block group (PRB group; PRG).

The above-described aspects of the present disclosure are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the present disclosure are detailed below by those of ordinary skill in the art. It can be derived and understood based on the description.

According to the embodiments of the present disclosure, the following effects are achieved.

According to the present disclosure, when a base station transmits a plurality of PDSCHs through all or partially overlapping time/frequency resources, the terminal(s) receiving the plurality of PDSCHs can efficiently detect the PDSCH(s). .

As a specific example, when a base station transmits a plurality of PDSCHs to a specific terminal through time/frequency resources overlapping in whole or in part, the terminal does not acquire information for scheduling at least one PDSCH among the plurality of PDSCHs. If not, it is possible to detect the remaining PDSCH(s) with a high probability.

The effects that can be obtained in the embodiments of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned are the technical fields to which the technical configuration of the present disclosure is applied from the description of the embodiments of the present disclosure below. Can be clearly derived and understood by those with ordinary knowledge. That is, unintended effects of implementing the configuration described in the present disclosure may also be derived from the embodiments of the present disclosure by a person of ordinary skill in the art.

The accompanying drawings are provided to aid understanding of the present disclosure, and provide embodiments of the present disclosure together with a detailed description. However, the technical features of the present disclosure are not limited to a specific drawing, and features disclosed in each drawing may be combined with each other to constitute a new embodiment. Reference numerals in each drawing refer to structural elements.

1 illustrates a communication system applied to the present disclosure.

2 illustrates a wireless device applicable to the present disclosure.

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

4 illustrates a portable device applied to the disclosure.

5 illustrates a vehicle or an autonomous vehicle applied to the present disclosure.

6 is a diagram illustrating physical channels and a signal transmission method using them.

7 is a diagram illustrating a structure of a radio frame based on an NR system to which embodiments of the present disclosure are applicable.

8 is a diagram illustrating a slot structure based on an NR system to which embodiments of the present disclosure are applicable.

9 is a diagram showing a self-contained slot structure based on an NR system to which embodiments of the present disclosure are applicable.

10 is a diagram illustrating one REG structure based on an NR system to which embodiments of the present disclosure are applicable.

11 is a diagram briefly showing an example of a front loaded DMRS of a first DMRS configuration type according to the present disclosure.

12 is a diagram illustrating an example of a case in which time and/or frequency resources of two PDSCHs applicable to the present disclosure overlap.

13 is a diagram briefly showing the operation of a single PDCCH system applicable to the present disclosure.

14 is a diagram briefly illustrating an operation of a UE receiving different PDSCHs from different TRPs according to the present disclosure.

15 is a diagram illustrating a case in which PRGs of different PDSCHs are the same according to the present disclosure.

16 is a diagram illustrating a case in which different PDSCHs partially overlap according to the present disclosure.

17 is a diagram illustrating an example of resource allocation by a base station, and FIG. 18 is a diagram illustrating a second operation example according to the present disclosure.

19 is a diagram illustrating a second operation example according to the present disclosure.

20 to 22 are diagrams illustrating examples of resource allocation by a base station.

23 and 24 are diagrams illustrating examples of resource allocation by a base station.

25 is a diagram briefly showing an example in which different PRGs are set between two Transmission Reception Points (TRPs).

26 is a diagram briefly showing another example in which different PRGs are set between two TRPs.

27 and 28 are diagrams illustrating a signaling method between a network side and a terminal in a multi-TRP situation to which the methods according to the present disclosure can be applied.

29 is a diagram briefly showing a network connection and communication process between a terminal and a base station applicable to the present disclosure.

30 is a diagram briefly showing the operation of a terminal and a base station according to an example of the present disclosure, FIG. 31 is a flowchart of an operation of a terminal according to an example of the present disclosure, and FIG. 32 is an operation of a base station according to an example of the present disclosure It is a flow chart.

The following embodiments are a combination of components and features of the present disclosure in a predetermined form. Each component or feature may be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form that is not combined with other components or features. In addition, some components and/or features may be combined to constitute an embodiment of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some configurations or features of one embodiment may be included in other embodiments, or may be replaced with corresponding configurations or features of other embodiments.

In the description of the drawings, procedures or steps that may obscure the subject matter of the present disclosure have not been described, and procedures or steps that can be understood by those skilled in the art have not been described.

Throughout the specification, when a part is said to "comprising or including" a certain component, it means that other components may be further included rather than excluding other components unless specifically stated to the contrary. do. In addition, terms such as "... unit", "... group", and "module" described in the specification mean a unit that processes at least one function or operation, which is a combination of hardware or software or hardware and software. It can be implemented as In addition, "a or an", "one", "the" and similar related words are different from this specification in the context of describing the present disclosure (especially in the context of the following claims). Unless otherwise indicated or clearly contradicted by context, it may be used in a sense encompassing both the singular and the plural.

In the present specification, embodiments of the present disclosure have been described centering on a data transmission/reception relationship between a base station and a mobile station. Here, the base station has a meaning as a terminal node of a network that directly communicates with the mobile station. The specific operation described as being performed by the base station in this document may be performed by an upper node of the base station in some cases.

That is, in a network comprising a plurality of network nodes including a base station, various operations performed for communication with a mobile station may be performed by the base station or network nodes other than the base station. At this time,'base station' is to be replaced by terms such as fixed station, Node B, eNode B (eNB), gNode B (gNB), advanced base station (ABS), or access point. I can.

In addition, in embodiments of the present disclosure, a terminal is a user equipment (UE), a mobile station (MS), a subscriber station (SS), and a mobile subscriber station (MSS). , May be replaced with terms such as a mobile terminal or an advanced mobile station (AMS).

Further, the transmitting end refers to a fixed and/or mobile node that provides a data service or a voice service, and the receiving end refers to a fixed and/or mobile node that receives a data service or a voice service. Accordingly, in the uplink, the mobile station may be the transmitting end and the base station may be the receiving end. Likewise, in the downlink, the mobile station may be the receiving end and the base station may be the transmitting end.

Embodiments of the present disclosure may be supported by standard documents disclosed in at least one of the IEEE 802.xx system, 3rd Generation Partnership Project (3GPP) system, 3GPP LTE system, 3GPP 5G NR system, and 3GPP2 system as radio access systems, In particular, embodiments of the present disclosure may be supported by 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.321 and 3GPP TS 38.331 documents. That is, obvious steps or parts not described among the embodiments of the present disclosure may be described with reference to the above documents. In addition, all terms disclosed in this document can be described by the standard document.

Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description to be disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present disclosure, and is not intended to represent the only embodiments in which the technical configuration of the present disclosure may be implemented.

In addition, specific terms used in the embodiments of the present disclosure are provided to aid understanding of the present disclosure, and the use of these specific terms may be changed in other forms without departing from the technical spirit of the present disclosure. .

Hereinafter, a 3GPP NR system will be described as an example of a wireless access system in which embodiments of the present disclosure can be used.

The following technologies include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and the like. It can be applied to various wireless access systems.

In order to clarify the description of the technical features of the present disclosure, embodiments of the present disclosure will be mainly described with a 3GPP NR system. However, the embodiment proposed in the present disclosure may be equally applied to other wireless systems (eg 3GPP LTE, IEEE 802.16, IEEE 802.11, etc.).

1. 본 개시가 적용되는 통신 시스템 예1. Example of a communication system to which the present disclosure is applied

Although not limited thereto, various descriptions, functions, procedures, proposals, methods, and/or operational flowcharts of the present disclosure disclosed in this document may be applied to various fields requiring wireless communication/connection (eg, 5G) between devices. have.

Hereinafter, it will be illustrated in more detail with reference to the drawings. In the following drawings/description, the same reference numerals may exemplify the same or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise indicated.

1 illustrates a communication system 1 applied to the present disclosure.

1, a communication system 1 applied to the present disclosure includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (eg, 5G NR (New RAT), LTE (Long Term Evolution)), and may be referred to as a communication/wireless/5G device. Although not limited thereto, wireless devices include robots 100a, vehicles 100b-1 and 100b-2, eXtended Reality (XR) devices 100c, hand-held devices 100d, and home appliances 100e. ), an Internet of Thing (IoT) device 100f, and an AI device/server 400. For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, and a vehicle capable of performing inter-vehicle communication. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (eg, a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, including HMD (Head-Mounted Device), HUD (Head-Up Display), TV, smartphone, It can be implemented in the form of a computer, wearable device, home appliance, digital signage, vehicle, robot, and the like. Portable devices may include smart phones, smart pads, wearable devices (eg, smart watches, smart glasses), computers (eg, notebook computers, etc.). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors, smart meters, and the like. For example, the base station and the network may be implemented as a wireless device, and the specific wireless device 200a may operate as a base station/network node to another wireless device.

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

Wireless communication/

connections

150a, 150b, and 150c may be established between the wireless devices 100a to 100f / base station 200 and the base station 200 / base station 200. Here, the wireless communication/connection includes various wireless access such as uplink/downlink communication 150a, sidelink communication 150b (or D2D communication), base station communication 150c (eg relay, Integrated Access Backhaul). This can be achieved through technology (eg 5G NR) Through wireless communication/

connections

150a, 150b, 150c, the wireless device and the base station/wireless device, and the base station and the base station can transmit/receive radio signals to each other. For example, the wireless communication/

connection

150a, 150b, 150c may transmit/receive signals through various physical channels. To this end, based on various proposals of the present disclosure, for transmission/reception of wireless signals At least some of a process of setting various configuration information, various signal processing processes (eg, channel encoding/decoding, modulation/demodulation, resource mapping/demapping, etc.), resource allocation process, and the like may be performed.

2. 본 개시가 적용되는 무선 기기 예2. Examples of wireless devices to which the present disclosure is applied

2 illustrates a wireless device applicable to the present disclosure.

Referring to FIG. 2, the first wireless device 100 and the second wireless device 200 may transmit and receive wireless signals through various wireless access technologies (eg, LTE and NR). Here, {the first wireless device 100, the second wireless device 200} is the {wireless device 100x, the base station 200} and/or {wireless device 100x, wireless device 100x) of FIG. } Can be matched.

The first wireless device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and/or one or more antennas 108. The processor 102 controls the memory 104 and/or the transceiver 106 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed herein. For example, the processor 102 may process information in the memory 104 to generate first information/signal, and then transmit a radio signal including the first information/signal through the transceiver 106. In addition, the processor 102 may store information obtained from signal processing of the second information/signal in the memory 104 after receiving a radio signal including the second information/signal through the transceiver 106. 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 perform some or all of the processes controlled by the processor 102, or instructions for performing the descriptions, functions, procedures, suggestions, methods, and/or operational flow charts disclosed in this document. It can store software code including Here, the processor 102 and the memory 104 may be part of a communication modem/circuit/chip designed to implement wireless communication technology (eg, LTE, NR). The transceiver 106 may be coupled with the processor 102 and may transmit and/or receive radio signals through one or more antennas 108. The transceiver 106 may include a transmitter and/or a receiver. The transceiver 106 may be mixed with an RF (Radio Frequency) unit. In the present disclosure, a wireless device may mean a communication modem/circuit/chip.

The second wireless device 200 includes one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and/or one or more antennas 208. The processor 202 controls the memory 204 and/or the transceiver 206 and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed herein. For example, the processor 202 may process information in the memory 204 to generate third information/signal, and then transmit a wireless signal including the third information/signal through the transceiver 206. In addition, the processor 202 may store information obtained from signal processing of the fourth information/signal in the memory 204 after receiving a radio signal including the fourth information/signal through the transceiver 206. 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 perform some or all of the processes controlled by the processor 202, or instructions for performing the descriptions, functions, procedures, suggestions, methods and/or operational flow charts disclosed in this document. It can store software code including Here, the processor 202 and the memory 204 may be part of a communication modem/circuit/chip designed to implement wireless communication technology (eg, LTE, NR). The transceiver 206 may be connected to the processor 202 and may transmit and/or receive radio signals through one or more antennas 208. The transceiver 206 may include a transmitter and/or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In the present disclosure, a wireless device may mean a communication modem/circuit/chip.

Hereinafter, the hardware elements of the

wireless devices

100 and 200 will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or

more processors

102, 202. For example, one or

more processors

102, 202 may implement one or more layers (eg, functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or

more processors

102, 202 may be configured to generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) according to the description, functions, procedures, proposals, methods, and/or operational flow charts disclosed in this document. Can be generated. One or

more processors

102, 202 may generate messages, control information, data, or information according to the description, function, procedure, suggestion, method, and/or operational flow chart disclosed herein. At least one processor (102, 202) generates a signal (e.g., a baseband signal) including PDU, SDU, message, control information, data or information according to the functions, procedures, proposals and/or methods disclosed herein. , It may be provided to one or more transceivers (106, 206). One or

more processors

102, 202 may receive signals (e.g., baseband signals) from one or

more transceivers

106, 206, and the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed herein PDUs, SDUs, messages, control information, data, or information may be obtained according to the parameters.

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 by hardware, firmware, software, or a combination thereof. For 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 one or

more processors

102 and 202. The description, functions, procedures, suggestions, methods, and/or operational flow charts disclosed in this document may be implemented using firmware or software, and firmware or software may be implemented to include modules, procedures, functions, and the like. The description, functions, procedures, proposals, methods and/or operational flow charts disclosed in this document are included in one or

more processors

102, 202, or stored in one or

more memories

104, 204, and are It may be driven by the

above processors

102 and 202. The descriptions, functions, procedures, proposals, methods and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and/or a set of instructions.

One or

more memories

104 and 204 may be connected to one or

more processors

102 and 202 and may store various types of data, signals, messages, information, programs, codes, instructions and/or instructions. One or

more memories

104 and 204 may be composed of ROM, RAM, EPROM, flash memory, hard drive, register, cache memory, computer readable storage medium, and/or combinations thereof. One or

more memories

104 and 204 may be located inside and/or outside of one or

more processors

102 and 202. In addition, one or

more memories

104, 204 may be connected to one or

more processors

102, 202 through various technologies such as wired or wireless connection.

The one or

more transceivers

106 and 206 may transmit user data, control information, radio signals/channels, and the like mentioned in the methods and/or operation flow charts of this document to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, radio signals/channels, etc. mentioned in the description, functions, procedures, suggestions, methods and/or operation flow charts disclosed in this document from one or more other devices. have. For example, one or

more transceivers

106 and 206 may be connected to one or

more processors

102 and 202, and may transmit and receive wireless signals. For example, one or

more processors

102, 202 may control one or

more transceivers

106, 206 to transmit user data, control information, or radio signals to one or more other devices. In addition, one or

more processors

102, 202 may control one or

more transceivers

106, 206 to receive user data, control information, or radio signals from one or more other devices. In addition, one or more transceivers (106, 206) may be connected with one or more antennas (108, 208), and one or more transceivers (106, 206) through one or more antennas (108, 208), the description and functionality disclosed in this document. It may be set to transmit and receive user data, control information, radio signals/channels, and the like mentioned in a procedure, a proposal, a method and/or an operation flowchart. In this document, one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (eg, antenna ports). One or more transceivers (106, 206) in order to process the received user data, control information, radio signal / channel, etc. using one or more processors (102, 202), the received radio signal / channel, etc. in the RF band signal. It can be converted into a baseband signal. One or

more transceivers

106 and 206 may convert user data, control information, radio signals/channels, etc. processed using one or

more processors

102 and 202 from a baseband signal to an RF band signal. To this end, one or more of the

transceivers

106 and 206 may include (analog) oscillators and/or filters.

3. 본 개시가 적용되는 무선 기기 활용 예3. Examples of wireless devices to which the present disclosure is applied

3 shows another example of a wireless device applied to the present disclosure. The wireless device may be implemented in various forms according to use-examples/services (see FIG. 1).

Referring to FIG. 3, the

wireless devices

100 and 200 correspond to the

wireless devices

100 and 200 of FIG. 2, and various elements, components, units/units, and/or modules ) Can be composed of. For example, the

wireless devices

100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and an additional element 140. The communication unit may include a communication circuit 112 and a transceiver(s) 114. For example, communication circuitry 112 may include one or more processors 102,202 and/or one or more memories 104,204 of FIG. 2. For example, the transceiver(s) 114 may include one or more transceivers 106,206 and/or one or more antennas 108,208 of FIG. 2. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140 and controls all operations of the wireless device. For example, the controller 120 may control the electrical/mechanical operation of the wireless device based on the program/code/command/information stored in the memory unit 130. In addition, the control unit 120 transmits the information stored in the memory unit 130 to an external (eg, other communication device) through the communication unit 110 through a wireless/wired interface, or through the communication unit 110 to the outside (eg, Information received through a wireless/wired interface from another communication device) may be stored in the memory unit 130.

The additional element 140 may be variously configured according to the type of wireless device. For example, the additional element 140 may include at least one of a power unit/battery, an I/O unit, a driving unit, and a computing unit. Although not limited to this, wireless devices include robots (Fig. 1, 100a), vehicles (Fig. 1, 100b-1, 100b-2), XR equipment (Fig. 1, 100c), portable equipment (Fig. 1, 100d), and home appliances. (Fig. 1, 100e), IoT device (Fig. 1, 100f), digital broadcasting terminal, hologram device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate/environment device, It may be implemented in the form of an AI server/device (Fig. 1, 400), a base station (Fig. 1, 200), and a network node. The wireless device can be used in a mobile or fixed location depending on the use-example/service.

In FIG. 3, various elements, components, units/units, and/or modules in the

wireless devices

100 and 200 may be entirely interconnected through a wired interface, or at least some may be wirelessly connected through the communication unit 110. For example, in the

wireless devices

100 and 200, the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and the first unit (eg, 130, 140) are connected through the communication unit 110. Can be connected wirelessly. In addition, each element, component, unit/unit, and/or module in the

wireless device

100 and 200 may further include one or more elements. For example, the controller 120 may be configured with one or more processor sets. For example, the control unit 120 may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphic processing processor, and a memory control processor. As another example, the memory unit 130 includes random access memory (RAM), dynamic RAM (DRAM), read only memory (ROM), flash memory, volatile memory, and non-volatile memory. volatile memory) and/or a combination thereof.

Hereinafter, an implementation example of FIG. 3 will be described in more detail with reference to the drawings.

3.1. 본 개시가 적용되는 휴대기기 예3.1. Examples of mobile devices to which the present disclosure applies

4 illustrates a portable device applied to the present disclosure. Portable devices may include smart phones, smart pads, wearable devices (eg, smart watches, smart glasses), and portable computers (eg, notebook computers). The portable 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. 4, the portable device 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an input/output unit 140c. ) Can be included. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 to 130/140a to 140c correspond to blocks 110 to 130/140 of FIG. 3, respectively.

The communication unit 110 may transmit and receive signals (eg, data, control signals, etc.) with other wireless devices and base stations. The controller 120 may perform various operations by controlling components of the portable device 100. The controller 120 may include an application processor (AP). The memory unit 130 may store data/parameters/programs/codes/commands required for driving the portable device 100. Also, the memory unit 130 may store input/output data/information, and the like. The power supply unit 140a supplies power to the portable device 100 and may include a wired/wireless charging circuit, a battery, and the like. The interface unit 140b may support connection between the portable device 100 and other external devices. The interface unit 140b may include various ports (eg, audio input/output ports, video input/output ports) for connection with external devices. The input/output unit 140c may receive or output image information/signal, audio information/signal, data, and/or information input from a user. The input/output unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and/or a haptic module.

For example, in the case of data communication, the input/output unit 140c acquires information/signals (eg, touch, text, voice, image, video) input from the user, and the obtained information/signals are stored in the memory unit 130. Can be saved. The communication unit 110 may convert information/signals stored in the memory into wireless signals, and may directly transmit the converted wireless signals to other wireless devices or to a base station. In addition, after receiving a radio signal from another radio device or a base station, the communication unit 110 may restore the received radio signal to the original information/signal. After the restored information/signal is stored in the memory unit 130, it may be output in various forms (eg, text, voice, image, video, heptic) through the input/output unit 140c.

3.2. 본 개시가 적용되는 차량 또는 자율 주행 차량 예3.2. Examples of vehicles or autonomous vehicles to which the present disclosure applies

5 illustrates a vehicle or an autonomous vehicle applied to the present disclosure. The vehicle or autonomous vehicle may be implemented as a mobile robot, a vehicle, a train, an aerial vehicle (AV), or a ship.

5, the vehicle or autonomous driving vehicle 100 includes an antenna unit 108, a communication unit 110, a control unit 120, a driving unit 140a, a power supply unit 140b, a sensor unit 140c, and autonomous driving. It may include a unit (140d). The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110/130/140a to 140d correspond to blocks 110/130/140 of FIG. 4, respectively.

The communication unit 110 may transmit and receive signals (eg, data, control signals, etc.) with external devices such as other vehicles, base stations (e.g. base stations, roadside base stations, etc.), and servers. The controller 120 may perform various operations by controlling elements of the vehicle or the autonomous vehicle 100. The control unit 120 may include an Electronic Control Unit (ECU). The driving unit 140a may cause the vehicle or the autonomous vehicle 100 to travel on the ground. The driving unit 140a may include an engine, a motor, a power train, a wheel, a brake, a steering device, and the like. The power supply unit 140b supplies power to the vehicle or the autonomous vehicle 100, and may include a wired/wireless charging circuit, a battery, and the like. The sensor unit 140c may obtain vehicle status, surrounding environment information, user information, and the like. The sensor unit 140c is an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight detection sensor, a heading sensor, a position module, and a vehicle advancement. /Reverse sensor, battery sensor, fuel sensor, tire sensor, steering sensor, temperature sensor, humidity sensor, ultrasonic sensor, illumination sensor, pedal position sensor, etc. may be included. The autonomous driving unit 140d is a technology for maintaining a driving lane, a technology for automatically adjusting the speed such as adaptive cruise control, a technology for automatically driving along a predetermined route, and for driving by automatically setting a route when a destination is set. Technology, etc. can be implemented.

For example, the communication unit 110 may receive map data and traffic information data from an external server. The autonomous driving unit 140d may generate an autonomous driving route and a driving plan based on the acquired data. The controller 120 may control the driving unit 140a so that the vehicle or the autonomous driving vehicle 100 moves along the autonomous driving path according to the driving plan (eg, speed/direction adjustment). During autonomous driving, the communication unit 110 asynchronously/periodically acquires the latest traffic information data from an external server, and may acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit 140c may acquire vehicle state and surrounding environment information. The autonomous driving unit 140d may update the autonomous driving route and the driving plan based on the newly acquired data/information. The communication unit 110 may transmit information about a vehicle location, an autonomous driving route, and a driving plan to an external server. The external server may predict traffic information data in advance using AI technology or the like, based on information collected from the vehicle or autonomous vehicles, and may provide the predicted traffic information data to the vehicle or autonomous vehicles.

4. NR 시스템4. NR system

4.1. 물리 채널들 및 일반적인 신호 전송4.1. Physical channels and general signal transmission

In a wireless access system, a terminal receives information from a base station through a downlink (DL) and transmits information to the base station through an uplink (UL). The information transmitted and received by the base station and the terminal includes general data information and various control information, and various physical channels exist according to the type/use of information transmitted and received by them.

6 is a diagram illustrating physical channels that can be used in embodiments of the present disclosure and a signal transmission method using them.

When the power is turned on again while the power is turned off, the terminal newly entering the cell performs an initial cell search operation such as synchronizing with the base station in step S11. To this end, the UE receives a Primary Synchronization Channel (P-SCH) and a Secondary Synchronization Channel (S-SCH) from the base station to synchronize with the base station, and obtains information such as cell ID.

Thereafter, the terminal may receive a physical broadcast channel (PBCH) signal from the base station to obtain intra-cell broadcast information.

Meanwhile, the UE may check the downlink channel state by receiving a downlink reference signal (DL RS) in the initial cell search step.

After completing the initial cell search, the UE receives a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to the physical downlink control channel information in step S12 and further Specific system information can be obtained.

Thereafter, the UE may perform a random access procedure, such as steps S13 to S16, to complete access to the base station. To this end, the UE transmits a preamble through a physical random access channel (PRACH) (S13), and a RAR for the preamble through a physical downlink control channel and a corresponding physical downlink shared channel ( Random Access Response) may be received (S14). The UE transmits a PUSCH (Physical Uplink Shared Channel) using the scheduling information in the RAR (S15), and a contention resolution procedure such as receiving a physical downlink control channel signal and a corresponding physical downlink shared channel signal. ) Can be performed (S16).

After performing the above-described procedure, the UE receives a physical downlink control channel signal and/or a physical downlink shared channel signal (S17) and a physical uplink shared channel (PUSCH) as a general uplink/downlink signal transmission procedure. Uplink Shared Channel) signal and/or a physical uplink control channel (PUCCH) signal may be transmitted (S18).

Control information transmitted by the UE to the base station is collectively referred to as uplink control information (UCI). UCI is HARQ-ACK/NACK (Hybrid Automatic Repeat and reQuest Acknowledgement/Negative-ACK), SR (Scheduling Request), CQI (Channel Quality Indication), PMI (Precoding Matrix Indication), RI (Rank Indication), BI (Beam Indication) ) Information, etc.

In the NR system, UCI is generally periodically transmitted through PUCCH, but may be transmitted through PUSCH according to embodiments (eg, when control information and traffic data are to be transmitted simultaneously). In addition, the UE may aperiodically transmit UCI through the PUSCH according to the request/instruction of the network.

4.2. 무선 프레임 (Radio Frame) 구조4.2. Radio Frame structure

Uplink and downlink transmission based on the NR system is based on the frame shown in FIG. 7. One radio frame has a length of 10 ms and is defined as two 5 ms half-frames (HF). One half-frame is defined as five 1ms subframes (Subframe, SF). One subframe is divided into one or more slots, and the number of slots in the subframe depends on Subcarrier Spacing (SCS). Each slot includes 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP). When a normal CP is used, each slot includes 14 symbols. When the extended CP is used, each slot includes 12 symbols. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol), an SC-FDMA symbol (or DFT-s-OFDM symbol).

Table 1 shows the number of symbols per slot according to the SCS, the number of slots per frame, and the number of slots per subframe when a general CP is used, and Table 2 shows the number of slots per SCS when the extended CSP is used. It indicates the number of symbols, the number of slots per frame, and the number of slots per subframe.

In the above table, ^slot N _symb denotes the number of a symbol in the slot, N ^{frame, μ} denotes a _slot number of a slot within a frame, ^{subframe N, μ} _slot is the number of slots within a subframe.

In an NR system to which the present disclosure can be applied, OFDM(A) numerology (eg, SCS, CP length, etc.) may be set differently between a plurality of cells merged into one terminal. Accordingly, the (absolute time) section of the time resource (eg, SF, slot or TTI) (for convenience, collectively referred to as TU (Time Unit)) composed of the same number of symbols may be set differently between the merged cells.

NR supports multiple numerology (or subcarrier spacing (SCS)) to support various 5G services. For example, when the SCS is 15 kHz, it supports a wide area in traditional cellular bands, and when the SCS is 30 kHz/60 kHz, it is dense-urban, lower latency. And a wider carrier bandwidth (wider carrier bandwidth) is supported, and when the SCS is 60 kHz or higher, a bandwidth greater than 24.25 GHz is supported to overcome phase noise.

The NR frequency band is defined as a frequency range of two types (FR1, FR2). FR1 and FR2 can be configured as shown in the table below. Further, FR2 may mean a millimeter wave (mmW).

One slot includes a plurality of symbols in the time domain. 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.

The carrier includes a plurality of subcarriers in the frequency domain. RB (Resource Block) is defined as a plurality of (eg, 12) consecutive subcarriers in the frequency domain.

The BWP (Bandwidth Part) is defined as a plurality of consecutive (P)RBs in the frequency domain, and may correspond to one numerology (eg, SCS, CP length, etc.).

The carrier may contain up to N (eg, 5) BWPs. Data communication is performed through the activated BWP, and only one BWP can be activated to one terminal. Each element in the resource grid is referred to as a resource element (RE), and one complex symbol may be mapped.

In FIG. 9, a hatched area (eg, symbol index = 0) indicates a downlink control area, and a black area (eg, symbol index = 13) indicates an uplink control area. Other areas (eg, symbol index = 1 to 12) may be used for downlink data transmission or uplink data transmission.

According to this structure, the base station and the UE can sequentially perform DL transmission and UL transmission within one slot, and can transmit and receive DL data and also transmit and receive UL ACK/NACK thereto within the one slot. As a result, this structure reduces the time required to retransmit data when a data transmission error occurs, thereby minimizing the delay in final data transmission.

In such a self-supporting slot structure, in order for the base station and the UE to switch from a transmission mode to a reception mode or from a reception mode to a transmission mode, a type gap of a certain length of time is required. To this end, some OFDM symbols at a time point at which the DL to UL is switched in the independent slot structure may be set as a guard period (GP).

In the foregoing detailed description, a case where the self-supporting slot structure includes both a DL control area and a UL control area has been described, but the control areas may be selectively included in the self-supporting slot structure. In other words, the self-supporting slot structure according to the present disclosure may include a case including both a DL control region and a UL control region as shown in FIG. 9 as well as a case including only a DL control region or a UL control region.

In addition, the order of the regions constituting one slot may vary according to embodiments. For example, one slot may be configured in the order of a DL control area / DL data area / UL control area / UL data area, or may be configured in the order of UL control area / UL data area / DL control area / DL data area.

The PDCCH may be transmitted in the DL control region, and the PDSCH may be transmitted in the DL data region. PUCCH may be transmitted in the UL control region, and PUSCH may be transmitted in the UL data region.

On the PDCCH, downlink control information (DCI), for example, DL data scheduling information, UL data scheduling information, and the like may be transmitted. In PUCCH, uplink control information (UCI), for example, positive acknowledgment/negative acknowledgment (ACK/NACK) information for DL data, channel state information (CSI) information, scheduling request (SR), and the like may be transmitted.

The PDSCH carries downlink data (e.g., DL-shared channel transport block, DL-SCH TB), and modulation methods such as Quadrature Phase Shift Keying (QPSK), Quadrature Amplitude Modulation (QAM), 64 QAM, and 256 QAM are used. Apply. A codeword is generated by encoding TB. The PDSCH can carry up to two codewords. Scrambling and modulation mapping are performed for each codeword, and modulation symbols generated from each codeword are mapped to one or more layers (Layer mapping). Each layer is mapped to a resource together with a demodulation reference signal (DMRS) to generate an OFDM symbol signal, and is transmitted through a corresponding antenna port.

The PDCCH carries downlink control information (DCI) and a QPSK modulation method is applied. One PDCCH is composed of 1, 2, 4, 8, 16 Control Channel Elements (CCEs) according to the Aggregation Level (AL). One CCE consists of 6 REGs (Resource Element Group). One REG is defined by one OFDM symbol and one (P)RB.

In FIG. 10, D represents a resource element (RE) to which DCI is mapped, and R represents an RE to which DMRS is mapped. The DMRS is mapped to the 1st, 5th, and 9th REs in the frequency domain direction within one symbol.

The PDCCH is transmitted through a control resource set (CORESET). CORESET is defined as a REG set with a given pneumonology (eg, SCS, CP length, etc.). A plurality of CORESETs for one terminal may overlap in the time/frequency domain. CORESET may be set through system information (eg, MIB) or UE-specific higher layer (eg, Radio Resource Control, RRC, layer) signaling. Specifically, the number of RBs constituting CORESET and the number of symbols (maximum 3) may be set by higher layer signaling.

PUSCH carries uplink data (e.g., UL-shared channel transport block, UL-SCH TB) and/or uplink control information (UCI), and CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplexing) waveform Alternatively, it is transmitted based on a DFT-s-OFDM (Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing) waveform. When the PUSCH is transmitted based on the DFT-s-OFDM waveform, the UE transmits the PUSCH by applying transform precoding. For example, when transform precoding is not possible (eg, transform precoding is disabled), the UE transmits a PUSCH based on the CP-OFDM waveform, and when transform precoding is possible (eg, transform precoding is enabled), the UE is CP-OFDM. PUSCH may be transmitted based on a waveform or a DFT-s-OFDM waveform. PUSCH transmission is dynamically scheduled by the UL grant in the DCI or is semi-static based on higher layer (e.g., RRC) signaling (and/or Layer 1 (L1) signaling (e.g., PDCCH)). Can be scheduled (configured grant). PUSCH transmission may be performed based on a codebook or a non-codebook.

PUCCH carries uplink control information, HARQ-ACK and/or scheduling request (SR), and is divided into Short PUCCH and Long PUCCH according to the PUCCH transmission length. Table 4 illustrates PUCCH formats.

PUCCH format 0 carries UCI of a maximum size of 2 bits, and is mapped and transmitted on a sequence basis. Specifically, the terminal transmits a specific UCI to the base station by transmitting one of the plurality of sequences through the PUCCH of PUCCH format 0. The UE transmits a PUCCH of PUCCH format 0 within a PUCCH resource for SR configuration corresponding to only when transmitting a positive SR.

PUCCH format 1 carries UCI of a maximum size of 2 bits, and the modulation symbol is spread by an orthogonal cover code (OCC) (set differently depending on whether or not frequency hopping) in the time domain. The DMRS is transmitted in a symbol in which a modulation symbol is not transmitted (that is, it is transmitted after time division multiplexing (TDM)).

PUCCH format 2 carries UCI of a bit size larger than 2 bits, and a modulation symbol is transmitted after DMRS and frequency division multiplexing (FDM). The DMRS is located at symbol indexes #1, #4, #7, and #10 in a given resource block with a density of 1/3. A PN (Pseudo Noise) sequence is used for the DMRS sequence. Frequency hopping may be activated for 2-symbol PUCCH format 2.

PUCCH format 3 does not perform multiplexing of terminals within the same physical resource blocks, and carries UCI with a bit size larger than 2 bits. In other words, the PUCCH resource of PUCCH format 3 does not include an orthogonal cover code. The modulation symbols are transmitted after DMRS and TDM (Time Division Multiplexing).

PUCCH format 4 supports multiplexing of up to 4 terminals in the same physical resource block, and carries UCI with a bit size larger than 2 bits. In other words, the PUCCH resource of PUCCH format 4 includes an orthogonal cover code. The modulation symbols are transmitted after DMRS and TDM (Time Division Multiplexing).

4.3. DCI 포맷4.3. DCI format

In an NR system to which the present disclosure is applicable, the following DCI formats may be supported. First, the NR system may support DCI format 0_0 and DCI format 0_1 as DCI formats for PUSCH scheduling, and DCI format 1_0 and DCI format 1_1 as DCI formats for PDSCH scheduling. In addition, as a DCI format that can be used for other purposes, the NR system may additionally support DCI format 2_0, DCI format 2_1, DCI format 2_2, and DCI format 2_3.

Here, DCI format 0_0 is used to schedule TB (Transmission Block)-based (or TB-level) PUSCH, DCI format 0_1 is TB (Transmission Block)-based (or TB-level) PUSCH or (CBG (Code Block Group)) When base signal transmission/reception is configured), it may be used to schedule a CBG-based (or CBG-level) PUSCH.

In addition, DCI format 1_0 is used to schedule a TB-based (or TB-level) PDSCH, and DCI format 1_1 is a TB-based (or TB-level) PDSCH or (when CBG-based signal transmission and reception is set) CBG-based (or CBG- level) Can be used to schedule PDSCH.

In addition, DCI format 2_0 is used to inform the slot format (used for notifying the slot format), DCI format 2_1 is used to inform the PRB and OFDM symbols assuming that a specific UE has no intended signal transmission ( used for notifying the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE), DCI format 2_2 is used for transmission of the PUCCH and PUSCH Transmission Power Control (TPC) commands. , DCI format 2_3 may be used for transmission of a TPC command group for SRS transmission by one or more UEs (used for the transmission of a group of TPC commands for SRS transmissions by one or more UEs).

More specifically, DCI format 1_1 includes an MCS/NDI (New Data Indicator)/RV (Redundancy Version) field for transport block (TB) 1, and the upper layer parameter maxNrofCodeWordsScheduledByDCI in the upper layer parameter PDSCH-Config is n2 (i.e. When set to 2), an MCS/NDI/RV field for transport block 2 may be further included.

In particular, when the upper layer parameter maxNrofCodeWordsScheduledByDCI is set to n2 (i.e., 2), whether or not the transport block is substantially usable (enable/disable) may be determined by a combination of the MCS field and the RV field. More specifically, when the MCS field for a specific transport block has a value of 26 and the RV field has a value of 1, the specific transport block may be disabled.

Specific characteristics of the DCI format may be supported by 3GPP TS 38.212 document. That is, obvious steps or parts that are not described among the DCI format related features may be described with reference to the document. In addition, all terms disclosed in this document can be described by the standard document.

4.4. CORESET (Control resource set)4.4. CORESET (Control resource set)

One CORESET includes N ^CORESET _RB RBs in the frequency domain, and N ^CORESET _symb (corresponding values have 1,2,3) symbols in the time domain.

One CCE (control channel element) includes 6 REG (resource element group), and one REG is the same as one RB on one OFDM symbol. REGs in CORESET are numbered in order according to a time-first manner. Specifically, the numbering starts from '0' for the first OFDM symbol and the lowest-numbered RB in CORESET.

A plurality of CORESETs may be set for one terminal. Each CORESET is associated with only one CCE-to-REG mapping.

CCE-to-REG mapping for one CORESET may be interleaved or non-interleaved.

The setting information for CORESET may be set by the upper layer parameter ControlResourceSet IE.

In addition, setting information for CORESET 0 (eg, common CORESET) may be set by the upper layer parameter ControlResourceSetZero IE.

4.5. 안테나 포트 의사 코-로케이션 (antenna ports quasi co-location)4.5. Antenna ports quasi co-location

A list of maximum M Transmission Configuration Indicator (TCI) state settings may be configured for one terminal. The maximum M TCI state setting may be set by a higher layer parameter PDSCH-Config so that (the terminal) can decode the PDSCH according to the detection of the PDCCH including the DCI intended for the terminal and a given serving cell. have. Here, the M value may be determined depending on the capability of the terminal.

Each TCI-state includes a parameter for setting a QCL (quasi co-location) relationship between one or two downlink reference signals and DMRS ports of the PDSCH. The QCL relationship is established based on an upper layer parameter qcl-Type1 for a first downlink reference signal (DL RS) and a higher layer parameter qcl-Type2 (if set) for a second DL RS. For the case of two DL RSs, regardless of whether the reference signals are the same DL RS or different DL RSs, the QCL types should not be the same (shall not be the same). The QCL types correspond to each DL RS given by the higher layer parameter qcl-Type in the higher layer parameter QCL-Info , and the QCL types may have one of the following values.

-'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread}

-'QCL-TypeB': {Doppler shift, Doppler spread}

-'QCL-TypeC': {Doppler shift, average delay}

-'QCL-TypeD': {Spatial Rx parameter}

The UE receives an activation command used to map the maximum of 8 TCI states with a codepoint of a Transmission Configuration Indication (TCI) field in DCI. When the HARQ-ACK signal corresponding to the PDSCH including the activation command is transmitted in slot #n, the mapping between the TCIs states and the code points of the TCI field in the DCI is slot #(n+3*N ^{subframe, μ} _slot + It can be applied from 1). Here, N ^{subframe and} _μslot are determined based on Table 1 or Table 2 described above. After the UE receives the initial higher layer configuration of the TCI states and before the UE receives the activation command, the UE has the DMRS port(s) of the PDSCH of the serving cell as'QCL-TypeA. From the point of view, it is assumed that the SS/PBCH (Synchronization Signal/Physical Broadcast Channel) block and QCL determined in the initial access procedure are performed. Additionally, at the time point, the UE may assume that the DMRS port(s) of the PDSCH of the serving cell are QCL with the SS/PBCH block determined in the initial access procedure in terms of'QCL-TypeD'.

When the upper layer parameter tci-PresentInDCI is set to'enabled ' for CORESET scheduling the PDSCH, the UE assumes that the TCI field exists in the PDCCH of DCI format 1_1 transmitted on the CORESET. For CORESET scheduling the PDSCH, the upper layer parameter tci-PresentInDCI is not set or the PDSCH is scheduled according to DCI format 1_0, and the time offset between the reception time of the DL DCI and the reception time of the corresponding PDSCH is a threshold Threshold-Sched -Offset (the threshold is determined based on the reported UE capability ), if greater than or equal to, in order to determine the PDSCH antenna port QCL, the UE uses the TCI state or QCL assumption for the PDSCH for PDCCH transmission. It is assumed to be the same as the TCI state or QCL assumption applied to.

When the upper layer parameter tci-PresentInDCI is set to'enabled ' and the TCI field in the DCI scheduling CC (component carrier) indicates the activated TCI states in the scheduled CC or DL BW (point to), the PDSCH Is scheduled according to DCI format 1_1, the UE uses the TCI-State based on the TCI field included in the DCI in the detected PDCCH to determine the PDSCH antenna port QCL. When the time offset between the DL DCI reception time and the corresponding PDSCH reception time is greater than or equal to the threshold Threshold-Sched-Offset (the threshold is determined based on the reported UE capability), the UE is the PDSCH of the serving cell. It is assumed that the DMRS port(s) are RS(s) and QCL in the TCI state for the QCL type parameter(s) given by the indicated TCI stated. When a single slot PDSCH is configured for the terminal, the indicated TCI state should be based on activated TCI states in the slot of the scheduled PDSCH. When a CORESET associated with a search space set for cross-carrier scheduling is set to the terminal, the terminal assumes that the upper layer parameter tci-PresentInDCI is set to'enabled ' for the CORESET, and the search When one or more TCI states set for a serving cell scheduled by a region set include'QCL-TypeD', the UE is a time offset between a reception time of a PDCCH detected in the search region set and a reception time of a corresponding PDSCH Expects to be greater than or equal to the threshold Threshold-Sched-Offset .

Higher layer parameters tci-PresentInDCI is set to 'enabled', or in RRC connected mode, the offset between the reception point of the PDSCH, which for both is not set is the upper layer parameter tci-PresentInDCI, if the response to the reception of DL DCI time threshold If it is smaller than Threshold-Sched-Offset , the UE assumes the following. (i) The DMRS port(s) of the PDSCH of the serving cell have a QCL relationship with the RS(s) of the TCI state and the QCL parameter(s). (ii) At this time, the QCL parameter(s) is the lowest CORESET-ID in the last slot in one or more CORESETs in the activation BWP of the serving cell monitored by the terminal for the PDCCH QCL indication of the CORESET associated with the monitored search area QCL parameter(s) used (For both the cases when higher layer parameter tci-PresentInDCI is set to'enabled ' and the higher layer parameter tci-PresentInDCI is not configured in RRC connected mode, if the offset between the reception of the DL DCI and the corresponding PDSCH is less than the threshold Threshold-Sched-Offset, the UE may assume that the DM-RS ports of PDSCH of a serving cell are quasi co-located with the RS(s) in the TCI state with respect to the QCL parameter(s) used for PDCCH quasi co-location indication of the CORESET associated with a monitored search space with the lowest CORESET-ID in the latest slot in which one or more CORESETs within the active BWP of the serving cell are monitored by the UE.)

In this case, when the'QCL-TypeD' of the PDSCH DMRS is different from the'QCL-TypeD' of the PDCCH DMRS overlapping on at least one symbol, the UE expects to prioritize reception of the PDCCH associated with the corresponding CORESET. This operation can also be applied equally to the case of intra-band CA (if PDSCH and CORESET are in different CCs). If there is no TCI state including'QCL-TypeD' among the configured TCI states, the terminal is the TCI indicated for the scheduled PDSCH, regardless of the time offset between the reception time of the DL DCI and the reception time of the corresponding PDSCH Another QCL assumption is obtained from state.

For periodic CSI-RS resources in the upper layer parameter NZP-CSI-RS-ResourceSet in which the upper layer parameter trs-Info is configured, the UE should assume that the TCI state indicates one of the following QCL type(s):

-'QCL-TypeC' for the SS/PBCH block, when applicable (when applicable),'QCL-TypeD' for the same SS/PBCH block, or

-'QCL-TypeC' for the SS/PBCH block and, if applicable (QCL-TypeD),'QCL for periodic CSI-RS resources in the upper layer parameter NZP-CSI-RS-ResourceSet in which the upper layer parameter repetition is set -TypeD'

For the CSI-RS resource in the higher layer parameter NZP-CSI-RS-ResourceSet set without the higher layer parameter trs-Info and the higher layer parameter repetition , the UE should assume that the TCI state indicates one of the following QCL type(s). :

-'QCL-TypeA' for the CSI-RS resource in the upper layer parameter NZP-CSI-RS-ResourceSet in which the upper layer parameter trs-Info is set, and (QCL-TypeD) for the same CSI-RS resource if applicable 'QCL-TypeD', or

-'QCL-TypeA' for the CSI-RS resource in the upper layer parameter NZP-CSI-RS-ResourceSet in which the higher layer parameter trs-Info is set, and'QCL-TypeD' for the SS/PBCH block if applicable QCL-TypeD', or

-'QCL-TypeA' for the CSI-RS resource in the upper layer parameter NZP-CSI-RS-ResourceSet in which the upper layer parameter trs-Info is set, and if applicable (QCL-TypeD), the upper layer parameter repetition is set 'QCL-TypeD' for periodic CSI-RS resources in the layer parameter NZP-CSI-RS-ResourceSet , or

-When'QCL-TypeB'and'QCL-TypeD' for CSI-RS resources in the upper layer parameter NZP-CSI-RS-ResourceSet in which the upper layer parameter trs-Info is set are not applicable

For the CSI-RS resource in the higher layer parameter NZP-CSI-RS-ResourceSet in which the higher layer parameter repetition is configured, the UE should assume that the TCI state indicates one of the following QCL type(s):

-'QCL-TypeA' for the CSI-RS resource in the upper layer parameter NZP-CSI-RS-ResourceSet in which the upper layer parameter trs-Info is set, and (QCL-TypeD) for the same CSI-RS resource if applicable 'QCL-TypeD', or,

-'QCL-TypeA' for the CSI-RS resource in the upper layer parameter NZP-CSI-RS-ResourceSet in which the upper layer parameter trs-Info is set, and if applicable (QCL-TypeD), the upper layer parameter repetition is set 'QCL-TypeD' for CSI-RS resources in the layer parameter NZP-CSI-RS-ResourceSet , or,

-'QCL-TypeC' for the SS/PBCH block and'QCL-TypeD' for the same SS/PBCH block if applicable (QCL-TypeD)

For the DMRS of the PDCCH, the UE should assume that the TCI state indicates one of the following QCL type(s):

-'QCL-TypeA' for the CSI-RS resource in the upper layer parameter NZP-CSI-RS-ResourceSet set without the upper layer parameter trs-Info and the upper layer parameter repetition , and (QCL-TypeD), if applicable, the same CSI 'QCL-TypeD' for -RS resource

For the DMRS of the PDSCH, the UE should assume that the TCI state indicates one of the following QCL type(s):

In this document, QCL signaling may include all signaling configurations described in the table below.

In the following tables, when there are rows including the same RS type, it can be assumed that the same RS ID is applied.

As an example, when there is a CSI-RS resource set by the upper layer parameter NZP-CSI-RS-ResourceSet together with the upper layer parameter trs-Info , the UE is capable of the following two of the upper layer parameter TCI-State You can only expect settings.

In the above table, * may mean that if QCL type-D is applicable, DL RS 2 and QCL type-2 may be configured for the terminal.

As another example, if there is a CSI-RS resource set by the upper layer parameter NZP-CSI-RS-ResourceSet without the upper layer parameter trs-Info and the higher layer parameter repetition , the UE is the upper layer parameter TCI-State Only the following three possible settings can be expected.

In the above table, * may mean that QCL type-D is not applicable.

In the above table, ** may mean that if QCL type-D is applicable, DL RS 2 and QCL type-2 may be configured for the terminal.

As another example, when there is a CSI-RS resource set by a higher layer parameter NZP-CSI-RS-ResourceSet together with a higher layer parameter repetition , the UE can configure the following three possible settings of the higher layer parameter TCI-State You can only expect them.

In the following two tables, when QCL type-D is applicable, DL RS 2 and QCL type-2 are to be set for the terminal except for the default case (the fourth row of the two tables below). I can. If the TRS for downlink is used for QCL type-D, the TRS may have a reference signal (eg, SSB or CSI-RS) for beam management (BM) as a source RS for QCL type-D. .

For the DMRS of the PDCCH, the UE has only the following three possible settings of the upper layer parameter TCI-State while the fourth setting (the fourth row of the two tables below) is valid as the default setting before the TRS is configured. Can be expected.

In the above table, * may mean a setting that can be applied before the TRS is set. Accordingly, the setting is not a TCI state, but rather can be interpreted as a valid QCL assumption.

In the above table, ** may mean that QCL parameters are not directly derived from CSI-RS (or CSI).

For the DMRS of the PDCCH, the UE has only three possible settings of the upper layer parameter TCI-State while the fourth setting (the fourth row of the two tables below) is valid (by default) before the TRS is configured. Can be expected.

In the above table, * may mean a setting that can be applied before the TRS is set. Accordingly, the setting may be interpreted as a valid QCL assumption rather than a TCI state.

4.6. DMRS (Demodulation Reference Signal)4.6. DMRS (Demodulation Reference Signal)

In the NR system according to the present disclosure, the DMRS may be transmitted and received in a frozen load structure. Alternatively, additional DMRS (Additional DMRS) may be additionally transmitted and received in addition to the first loaded DMRS.

Front loaded DMRS can support fast decoding. The first OFDM symbol on which the front loaded DMRS is loaded may be determined as a third (eg, l=2) or a fourth OFDM symbol (eg, l=3). The position of the first FODM symbol may be indicated by a PBCH (Physical Broadcast Channel).

The number of OFDM symbols occupied by the front loaded DMRS may be indicated by a combination of Downlink Control Information (DCI) and Radio Resource Control (RRC) signaling.

Additional DMRS may be configured for a high speed terminal. Additional DMRS may be located in the middle/last symbol(s) in the slot. When one front loaded DMRS symbol is set, the additional DMRS may be allocated to 0 to 3 OFDM symbols. When two front loaded DMRS symbols are configured, the additional DMRS may be allocated to 0 to 2 OFDM symbols.

The front loaded DMRS is composed of two types, and one of the two types may be indicated through higher layer signaling (eg, RRC signaling).

In the present disclosure, two types of DMRS configuration can be applied. Among the two DMRS configuration types, a DMRS configuration type that is substantially configured for the terminal may be indicated by higher layer signaling (eg, RRC).

In the case of the first DMRS configuration type 1, it can be classified as follows according to the number of OFDM symbols to which the front loaded DMRS is allocated.

The first DMRS configuration type (DMRS configuration type 1) and the number of OFDM symbols to which the front loaded DMRS is allocated = 1

Up to four ports (eg, P0 to P3) may be multiplexed based on length-2 frequency-code division multiplexing (F-CDM) and frequency division multiplexing (FDM) methods. The RS density may be set to 6 REs per port in the RB (Resource Block).

1st DMRS configuration type (DMRS configuration type 1) and the number of OFDM symbols to which the front loaded DMRS is allocated = 2

Up to 8 ports (eg, P0 to P7) may be multiplexed based on length-2 F-CDM, length-2 T-CDM (Time-Code Division Multiplexing) and FDM methods. Here, when the presence of the PT-RS is set by higher layer signaling, the T-CDM may be fixed to [1 1]. The RS density can be set to 12 RE per port in the RB.

In the case of the second DMRS configuration type 2, it may be classified as follows according to the number of OFDM symbols to which the front loaded DMRS is allocated.

The number of OFDM symbols to which the second DMRS configuration type 2 and front loaded DMRS are allocated = 1

Up to 6 ports (eg, P0 to P5) can be multiplexed based on length-2 F-CDM and FDM methods. RS density may be set to 4 RE per port in RB (Resource Block).

The number of OFDM symbols to which the second DMRS configuration type 2 and front loaded DMRS are allocated = 2

Up to 12 ports (eg, P0 to P11) can be multiplexed based on length-2 F-CDM, length-2 T-CDM, and FDM methods. Here, when the presence of the PT-RS is set by higher layer signaling, the T-CDM may be fixed to [1 1]. The RS density can be set to 8 RE per port in the RB.

More specifically, FIG. 11(a) shows a structure in which the DMRS is first loaded on one symbol (front loaded DMRS with one symbol), and in FIG. 11(b), a structure in which the DMRS is loaded first on two symbols (front loaded) DMRS with two symbols).

In FIG. 11, Δ means a DMRS offset value in the frequency axis. At this time, DMRS ports having the same Δ may be code division multiplexing in frequency domain (CDM-F) or code division multiplexing in time domain (CDM-T) in the frequency domain. . In addition, DMRS ports having different Δ may be CDM-F with each other.

According to the present disclosure, CDM-F in the table below

Can be applied based on, and CDM-T in the table below

Can be applied based on In this case, k'and l'are parameter values that determine the subcarrier index to which the corresponding DMRS is mapped, and may have a value of 0 or 1. And, according to the DMRS configuration type, the DMRS corresponding to each DMRS port may be divided into CDM groups as shown in the following table.

Table 12 below shows parameters for a first DMRS configuration type for a PDSCH, and Table 13 shows parameters for a second DMRS configuration type for a PDSCH.

The terminal may obtain DMRS port configuration information set by the base station through DCI. As an example, the DMRS configuration type set to the terminal (e.g., the first DMRS configuration type (dmrs-Type=1), the second DMRS configuration type (dmrs-Type=2)), the maximum number of OFDM symbols for the DL front loaded DMRSfmf (example : maxLength=1 or maxLength=2), the terminal may acquire DMRS port configuration information through an antenna ports field of DCI format 1_1. More specifically, Table 14 shows the DMRS port setting information according to the value of the antenna port field when (dmrs-Type=1 and maxLength=1) is set to the terminal, and Table 15 shows (dmrs-Type=1 and maxLength) to the terminal. When =2) is set, it indicates DMRS port configuration information according to the value of the antenna port field. Table 16 shows the DMRS port setting information according to the value of the antenna port field when (dmrs-Type=2 and maxLength=1) is set to the terminal, and Table 17 shows (dmrs-Type=2 and maxLength=2) to the terminal. If set, indicates DMRS port configuration information according to the value of the antenna port field.

In this case, the terminal may perform DMRS reception as follows according to conditions.

In DMRS configuration type 1,

-One codeword is scheduled for the terminal and indicates to the terminal one of {2, 9, 10, 11, 30} as an index value related to antenna port mapping (eg, an index value in Table 14 or Table 15) DCI is assigned, or

-When two codewords are scheduled to the terminal,

The UE may receive the DMRS on the assumption that all remaining orthogonal antenna ports are not associated with PDSCH transmission to other UEs.

In DMRS configuration type 2,

-One codeword is scheduled for the terminal, and DCI indicating one of {2, 10, 23} is allocated to the terminal as an index value related to antenna port mapping (eg, the index value in Table 15 or Table 16) Or

-When two codewords are scheduled to the terminal,

4.7. 코드워드 (codeword)4.7. Codeword

In the present disclosure, the base station may set the maximum number of codewords scheduled through one DCI to the terminal through higher layer signaling. For example, the base station may set the maximum number of codewords scheduled through one DCI to the terminal to 1 or 2 based on the upper layer parameter maxNrofCodeWordsScheduledByDCI (having a value of n1 or n2). In this case, the upper layer parameter maxNrofCodeWordsScheduledByDCI may be included in the higher layer parameter PDSCH-Config .

Referring to the Rel-15 TS 38.212 standard document, DCI format 1_1 may be configured as shown in the following table according to the upper layer parameter maxNrofCodeWordsScheduledByDCI .

Accordingly, the NDI, MCS, and RV of CW#0 may be set/instructed based on the NDI, MCS, and RV corresponding to Transport block 1 in DCI. Similarly, NDI, MCS, and RV of CW#1 may be set/instructed based on NDI, MCS, and RV corresponding to Transport block 2 in the DCI.

In addition, (i) a bandwidth part indicator field indicates a bandwidth part other than an active bandwidth part, and (ii) a value of the upper layer parameter maxNrofCodeWordsScheduledByDCI for the indicated bandwidth part is 2 , (iii) When the value of the upper layer parameter maxNrofCodeWordsScheduledByDCI for the active bandwidth part is 1, the UE can assume that the corresponding fields are padded with zeros in interpreting the MCS, NDI, and RV fields of transport block 2 have. Subsequently, in the above case, the UE may ignore the MCS, NDI, and RV fields of transport block 2 for the indicated bandwidth part.

In addition, when the upper layer parameter maxNrofCodeWordsScheduledByDCI indicates that transmission of two codewords is enabled, one of the two transport blocks (or codewords) (or codeword) is activated based on the following method. Or it can be disabled.

More specifically, when the upper layer parameter maxNrofCodeWordsScheduledByDCI indicates that transmission of two codewords is enabled, one of the two transport blocks is the (i) MCS value for the corresponding transport block in DCI format 1_1 If is 26 (ie, I _MCS = 26), and (ii) the RV value is 1 (ie, rv _id = 1), it can be deactivated. If both transport blocks are activated, transport block 1 and transport block 2 may be mapped to codeword 0 and codeword 1, respectively. If only one transport block is activated, the activated transport block can always be mapped to the first codeword (ie, codeword 0).

4.8. 본 개시에 적용 가능한 시간/주파수 자원 할당 케이스4.8. Time/frequency resource allocation case applicable to the present disclosure

In the present disclosure, T/F resources of each PDSCH (eg, PDSCH #0 and PDSCH #1) transmitted from different TRP (Transmission and Reception Point) (or beam or panel) may be variously overlapped. In this case, the case in which T/F resources overlap may include all five cases shown in FIG. 12.

As shown in FIG. 12, the two PDSCHs may be partially overlapped (eg, case #1 to #3) or may be overlapped on one of the time domain or frequency domain of the two PDSCHs (eg, case #4. , #5). Case #1/#2/#3 of FIG. 12 indicates that two PDSCHs are (partially) overlapped in both time and frequency. Case #4 of FIG. 12 indicates that two PDSCHs do not overlap only in the time axis. Case #5 of FIG. 12 indicates that two PDSCHs overlap on the time axis but not on the frequency axis.

4.9. 단일 PDCCH (Single PDCCH) 시스템4.9. Single PDCCH (Single PDCCH) system

In FIG. 13, it is assumed that each of two TRP#1/#2 transmits PDSCH#1/#2 to one terminal. In the following description, as shown in FIG. 13, an operation in which a plurality of PDSCHs are scheduled by one PDCCH is referred to as a single PDCCH system or a single PDCCH operation. In other words, a single PDCCH may mean a PDCCH for scheduling a plurality of (for different TRPs) PDSCHs.

For convenience of explanation, in the following description, two TRPs are exemplified as examples of a plurality of TRPs, but the corresponding operation may be equally applied to examples of three or more TRPs according to embodiments. In other words, in this disclosure, a single PDCCH may include a PDCCH for scheduling PDSCHs for three or more TRPs.

According to the single PDCCH system, even if the UE receives each PDSCH from different TRPs, the UE may obtain scheduling information of the plurality of PDSCHs by receiving one PDCCH. Accordingly, the PDCCH reception complexity of the terminal may be lowered.

In contrast, according to a multi-PDCCH (Multi PDCCH) system or multi-PDCCH operation in which two TRPs each transmit a PDCCH, and each of the PDCCHs schedules PDSCH #1/#2, the UE successfully receives two PDCCHs. Only the two PDSCHs can be received. On the other hand, in the case of a single PDCCH system or a single PDCCH operation, since the UE can receive two PDSCHs by successfully receiving only one PDCCH, performance degradation due to PDCCH miss detection can be minimized.

In FIG. 13, a PDCCH scheduling PDSCH #1/#2 may be transmitted from TRP #1 and/or TRP #2 to a terminal.

4.10. Non-Coherent Joint Transmission (NC-JT)4.10. Non-Coherent Joint Transmission (NC-JT)

In this document, time resources of PDSCHs transmitted by different TRPs (or beams) are (partially) overlapped (Case #5 in FIG. 12) or time and frequency resources (partially) overlapped (eg: In the case of CASE #1, #2, #3) of FIG. 12), a signal transmission method based on this is referred to as NC-JT.

In this document, a single DCI based NC-JT (Single DCI based NC-JT) means an NC-JT operation when PDSCHs transmitted from different TRPs (or beams) are scheduled by one DCI. I can. For example, a single DCI-based NC-JT may include an NC-JT operation when PDSCH#1/#2 is simultaneously scheduled by DCI#1.

In this document, Multi DCI based NC-JT (Multi DCI based NC-JT) means an NC-JT operation when PDSCHs transmitted from different TRPs (or beams) are scheduled by each DCI. I can. As an example, the multi-DCI-based NC-JT may include an NC-JT operation when PDSCH #1/#2 are respectively scheduled simultaneously by DCI#1/#2.

In this document, NC-JT can be classified into two types depending on whether a layer transmitted by different TRPs is independent or common.

In this document, "layers are independent" means that when TRP#A transmits signals through 3 layers and TRP#B transmits signals through 4 layers, the terminal covers a total of 7 layers. It may mean to expect to receive a signal through.

On the other hand, in this document,'layers are common' means that when TRP#A transmits signals through three layers and TRP#B transmits signals through three layers, a total of three terminals This may mean expecting signal reception through the layer.

In this document, in order to distinguish the two operations, NC-JT based on the former operation is referred to as'NC-JT with IL (Independent Layer)', and NC-JT based on the latter operation is referred to as'NC-JT. It is named'with CL (Common Layer)'.

In this document, various operation examples are described based on the'NC-JT with IL' operation (or mode), but the corresponding operation examples can be extended and applied to operation examples based on the'NC-JT with CL' operation (or mode). have.

4.11. HARQ 프로세스4.11. HARQ process

The DCI transmitted from the base station to the terminal may include a'HARQ process number' field configured with a 4-bit size. Based on the HARQ process number indicated by the'HARQ process number' field in the DCI, the UE may distinguish/recognize for which PDSCH the PDSCH scheduled by the DCI is retransmission among previously transmitted PDSCHs.

4.12. 변조 차수 (modulation order) 및 타겟 코드 레이트 (target code rate) 결정4.12. Determination of modulation order and target code rate

In this document, PDSCH is C-RNTI (cell radio network temporary identifier (RNTI)), MCS-C-RNTI (modulation coding scheme cell RNTI), TC-RNTI (temporary cell RNTI), CS-RNTI (configured scheduling RNTI) ), SI-RNTI (system information RNTI), RA-RNTI (random access RNTI), or P-RNTI (paging RNTI) by CRC (cyclic redundancy check) scrambled PDCCH (e.g., DCI format 1_0 or DCI format 1_1) Can be scheduled by Alternatively, the PDSCH may be scheduled based on a PDSCH configuration ( SPS-config ) provided from an upper layer without transmitting a corresponding PDCCH. The modulation order and target code rate for such PDSCHs may be determined/set as follows.

(1) (i) the upper layer parameter mcs-Table provided by the PDSCH-Config is set to'qam256', and (ii) the PDSCH is CRC scrambled by C-RNTI, DCI format 1_1 (or the DCI format 1_1) If scheduled by the included PDCCH),

-The terminal may determine a modulation order (Q _m ) and a target code rate (R) for the PDSCH based on the MCS value (eg, I _MCS ) and Table 20.

(2) Or, (i) MCS-C-RNTI is not set to the terminal, (ii) the upper layer parameter mcs-Table provided by PDSCH-Config is set to'qam64LowSE', (iii) PDSCH is C -When scheduled by PDCCH in a UE-specific search space CRC scrambled by RNTI,

-The UE may determine a modulation order (Q _m ) and a target code rate (R) for the PDSCH based on the MCS value (eg, I _MCS ) and Table 21.

(3) Or, (i) MCS-C-RNTI is set to the UE, and (ii) PDSCH is scheduled by PDCCH CRC scrambled by MCS-C-RNTI,

(4) Or, (i) the upper layer parameter mcs-Table provided by SPS-Config to the terminal is not set, and (ii) the upper layer parameter mcs-Table provided by PDSCH-Config is set to'qam256' If it becomes,

-When the PDSCH is scheduled by DCI format 1_1 CRC scrambled by CS-RNTI (or PDCCH including the DCI format 1_1), or,

-When the PDSCH is scheduled using SPS-config without transmitting a corresponding PDCCH,

--The UE may determine a modulation order (Q _m ) and a target code rate (R) for the PDSCH based on the MCS value (eg, I _MCS ) and Table 20.

(5) Or, (i) when the upper layer parameter mcs-Table provided by SPS-Config is set to'qam64LowSE',

-When the PDSCH is scheduled by a PDCCH CRC scrambled by CS-RNTI, or,

--The terminal may determine a modulation order (Q _m ) and a target code rate (R) for the PDSCH based on the MCS value (eg, I _MCS ) and Table 21.

(6) Alternatively, the UE may determine a modulation order (Q _m ) and a target code rate (R) for the PDSCH based on an MCS value (eg, I _MCS ) and Table 19.

4.13. 전송 블록 크기 결정 방법 (Transport block size determination)4.13. Transport block size determination

5.1.3.2. in 3GPP TS 38.214 standard spec. Based on the clause, the size of a transport block between the terminal and the base station according to the present disclosure may be determined. More specifically, the transport block size may be determined as follows.

When the upper layer parameter maxNrofCodeWordsScheduledByDCI indicates that two codeword transmissions are active, (i) I _MCS value for the corresponding transport block is 26 and (ii) rv _id value is 1, the corresponding transport block is in DCI format. Can be disabled by 1_1. If both transport blocks are activated, transport block 1 and transport block 2 may be mapped to codeword 0 and codeword 1, respectively. If only one transport block is activated, the activated transport block may always be mapped to a first codeword (eg, codeword 0).

For FDSCH allocated by DCI format 1_0 or DCI format 1_1 (or PDCCH including this) CRC scrambled by C-RNTI, MCS-C-RNTI, TC-RNTI, CS-RNTI or SI-RNTI, (i) Table 19 is used, and if the I _MCS value is greater than or equal to 0 and less than or equal to 27, or (ii) Table 18 or Table 20 is used and the I _MCS value is greater than or equal to 0 and less than or equal to 27, the terminal , Except when the transport block on DCI format 1_1 is deactivated, TBS (Transport Block Size) may be determined as follows.

(1) The terminal first determines the number of REs in the slot (eg, N _RE ).

-The terminal first, based on the following equation, determines the number of REs allocated for the PDSCH in the PRB (eg, _N'RE ).

In the above equation,

Represents the number of subcarriers in the physical resource block,

Represents the number of symbols included in the PDSCH allocation in the slot,

Denotes the number of REs for DMRS for each PRB in the scheduled interval including the overhead of the DMRS CDM group without data, indicated by DCI format 1_1 or determined according to DCI format 1_0 characteristics,

Denotes the overhead set by the upper layer parameter xOverhead in the upper layer parameter PDSCH-ServingCellConfig . If the upper layer parameter ServingCellConfig-PDSCH in the upper layer xOverhead parameter is not set (indicating that the value may be set to 0, 6, 12 or 18 values),

Is set to 0. When the PDSCH is scheduled by the PDCCH CRC scrambled by SI-RNTI, RA-RNTI or P-RNTI,

Can be assumed to be zero.

-The terminal may determine the total number of REs (N _RE ) allocated for the PDSCH based on the following equation.

In the above equation, n _PRB represents the total number of PRBs allocated for the terminal.

(2) The intermediate number (N _info ) of the information bit may be obtained based on the following equation.

In the above equation, R represents a target code rate determined by the MCS field, Qm represents a modulation order determined by the MCS field, and υ represents the number of layers. .

If the size of N _info is 3824 or less, step 3 may be used as the next step of TBS determination. Conversely, if the size of N _info exceeds 3824, step 4 may be used as the next step of TBS determination.

(3) When the size of N _info is 3824 or less, the TBS can be determined as follows:

- the N _'info is to the intermediate number of information bits quantized values (quantized intermediate number of information bits) may be set to satisfy the following formula.

In the above equation, n is

Can be satisfied.

- based on the following table, N 'Find Nearest TBS that is not less than _info.

(4) If the size of N _info exceeds 3824, the TBS can be determined as follows:

In the above equation, n is

Can be satisfied.

--When the R value is 1/4 or less, the TBS may be determined to satisfy the following equation.

In the above equation, the C value is

It can be set to satisfy.

- or, if the R value is greater than 1/4 and N _'info value is greater than 8424, TBS may be determined so as to satisfy the following equation.

In the above equation, the C value is

It can be set to satisfy.

--Or, TBS may be determined to satisfy the following equation.

Unlike previously described above, when Table 19 is used and the I _MCS value is greater than or equal to 28 and less than or equal to 31, TBS may be determined as follows.

-More specifically, in the above case, it may be assumed that the TBS is determined from the DCI transmitted in the latest PDCCH for the same transport block using the I _MCS having a value of 0 to 27. If, (i) there is no same transport block using I _MCS having values 0 to 27, and (ii) the initial PDSCH for the same transport block is semi-persistently scheduled, the TBS is the most recent It may be determined from a semi-persistent scheduling (SPS) allocation PDCCH.

Alternatively, it may be assumed that the TBS is determined from the DCI transmitted in the latest PDCCH for the same transport block using the I _MCS having a value of 0 to 28. If, (i) there is no same transport block using I _MCS having values 0 to 28, and (ii) the initial PDSCH for the same transport block is semi-persistently scheduled, the TBS is the most recent It may be determined from a semi-persistent scheduling (SPS) allocation PDCCH.

The UE may not expect that the PDSCH allocated by the PDCCH CRC scrambled by SI-RNTI has a TBS exceeding the 2976 bit size.

For PDSCH allocated by DCI format 1_0 (or PDCCH including the same) CRC scrambled by P-RNTI or RA-RNTI, TBS determination follows steps 1 to 4 above, but the following items are corrected in step 2 the first step in the state-can follow the 4: for when calculating N _info, N _info must be scaled to satisfy the following formula. Here, the scaling factor is determined based on the TB scaling field in DCI disclosed in the following table.

In addition to the NDI and HARQ process ID signaled on the PDCCH, the TBS determined as described above may be reported to a higher layer (in the terminal).

4.14. 자원 할당 (resource allocation) 방법4.14. Resource allocation method

In the present disclosure, two downlink resource allocation schemes (eg, resource allocation type 0 and resource allocation type 1) may be supported. When the scheduling grant is received together with the DCI format 1_0, the UE may assume that downlink resource allocation type 1 is used.

If the upper layer parameter resourceAllocation in the pdsch-Config is set to'dynamicswitch ', when the scheduling DCI is configured to indicate a downlink resource allocation type as part of a frequency domain resource assignment (FRA) field, the terminal is configured to be based on the DCI field. The determined/defined downlink resource allocation type 0 or type 1 may be used.

When the bandwidth part (BWP) indicator field in the scheduling DCI is not set or the terminal does not support active BWP change through DCI, downlink resource allocation type 0 and RB indexing for type 1 May be determined within the activated BWP of the terminal. Conversely, when the BWP indicator field in the scheduling DCI is set and the terminal supports active BWP change through DCI, RB indexing for downlink resource allocation type 0 and type 1 is the bandwidth part indicator in the DCI. It may be determined within the bandwidth part of the terminal indicated by the field value. When the UE detects a PDCCH intended for the UE, the UE may first determine a downlink carrier bandwidth part, and then determine resource allocation within the bandwidth part.

For the PDSCH scheduled by DCI format 1_0 in all types of PDCCH common search regions, RB numbering may start from the lowest RB of the CORESET in which the DCI is received, regardless of which bandwidth part is the active bandwidth part. In other cases, RB numbering may start from the lowest RB in the determined downlink bandwidth part.

4.14.1. Resource allocation type 0

In the present disclosure, resource allocation type 0 may mean a resource allocation method based on a resource block group (RBG).

In order to support resource allocation type 0, higher layer parameters for RBG as shown in the following table may be set to the terminal.

In the above table, the upper layer parameter rbg-Size may be selected as'config1' or'config2' as the RBG size for the PDSCH. Only when the upper layer parameter resourceAllocation is set to'resourceAllocationType0' or'dynamicSwitch', the network (or base station) may set the upper layer parameter rbg-Size to'config2'. The higher layer parameter may correspond to the L1 parameter'RBG-size-PDSCH'.

In downlink resource allocation type 0 according to the present disclosure, the resource block allocation information may include a bitmap indicating RBG(s) allocated to the scheduled terminal. The RBG(s) may be a set of consecutive virtual resource blocks defined by a higher layer parameter rbg-Size set by PDSCH-Config and a size of a carrier bandwidth part defined as shown in the following table.

here,

The total number (N _RBG ) of _RBGs for downlink bandwidth part i of the size of PRBs may be set to satisfy the following equation.

In the above equation, the size of the first RBG may be set to satisfy the following equation (11). In addition, in the above equation,

If is satisfied, the size of the last RBG is set to satisfy Equation 12 below, otherwise, the size of the last RBG may be set to P. In addition, in the above equation, the size of another RBG may be set to P.

Since the bitmap is composed of N _RBG bit sizes, one bit may be allocated for each RBG. Through this, each RBG can be addressable. The RBG is indexed in the order of increasing frequency, and may start from the lowest frequency of the carrier bandwidth part. RBG bitmaps including RBG 0 to RBG N _RBG -1 may be mapped from MSB (Most Significant Bit) to LSB (Least Significant Bit) in order. If the value of the corresponding bit in the bitmap is 1, the corresponding RBG may be allocated to the terminal, and in the opposite case, the corresponding RBG may not be allocated to the terminal.

4.14.2. Resource allocation type 1

In the downlink resource allocation type 1 according to the present disclosure, the resource block allocation information is (i) continuously allocated non-interleaved virtual resource blocks or (ii) continuously allocated to the scheduled terminal. Interleaved (interleaved) virtual resource blocks can be indicated. In this case, the non-interleaved/interleaved virtual resource block, except for a case in which DCI format 1_0 in the common search region in which the size of CORESET 0 is used is decoded,

It may be included in the active bandwidth part of the PRB size.

The downlink type 1 resource allocation field includes (i) a starting virtual resource block (eg, RB _start ) and (ii) a resource indication value corresponding to the length of a continuously allocated resource block unit (eg, L _RBs ). ; RIV) may be included. The resource indication value may be defined based on the following equation.

Although the DCI size for DCI format 1_0 in USS (User-specific Search Space) is derived from the size of CORESET 0 (derived from)

When applied to an activation BWP of another size, the downlink type 1 resource block allocation field is (i) a starting virtual resource block (e.g.

) And (ii) the length of a virtually consecutively allocated resource block unit (eg:

) May include a corresponding resource indication value (RIV).

remind

The value may be determined as the size of the CORESET when (i) CORESET 0 is set for the cell, or (ii) the size of the initial DL bandwidth part when CORESET 0 is not set for the cell.

The resource indication value may be defined based on the following equation.

In the above equation, the K value may be set to satisfy the following equation.

4.15. PRG (Precoding Resource Block Group, PRB group)4.15. PRG (Precoding Resource Block Group, PRB group)

In the present disclosure, bundling for PRG may be set based on higher layer parameters according to the following table.

In the above table, prb-bundlingType may be related (or may be indicated) with PRB bundle type and bundle size(s). When dynamic is selected, the actual bundleSizeSet1 or bundleSizeSet2 to be used can be indicated through DCI. Constraints for the bundleSize(Set) setting may be based on the vrb-ToPRB-Interleaver and rbg-Size settings. If the bundleSize(Set) value is absent (absent), the terminal can apply an n2 value (eg, 2).

Based on the upper layer parameters, the terminal may perform an operation based on the following tables.

More specifically, the terminal has precoding granularity in the frequency domain.

It can be assumed that there are four consecutive resource blocks.

May be the same as one of {2, 4, wideband}.

When the value is determined to be'wideband', the UE may not expect that non-contiguous PRB(s) are scheduled, and the UE may assume that the same precoding is applied to the allocated resources. to be.

If the value is determined to be one of {2, 4}, the PRG is the bandwidth part i.

It can be divided into four consecutive PRBs (partition). The actual number of consecutive PRBs in each PRG may be 1 or more.

The first PRG size is

Can be

, The last PRG size is

Can be or,

, The last PRG size is

Can be

The UE may assume that the same precoding is applied for any downlink consecutive allocation of PRBs in the PRG.

For the PDSCH scheduled by the PDCCH CRC scrambled by SI-RNTI and carrying SIB1, the PRG may be divided from the lowest numbered resource block of the CORESET signaled in the PBCH (partitioned).

When the UE is scheduled for PDSCH according to DCI format 1_0, the UE

It can be assumed that these 2 PRB(s) are the same.

When the UE receives the PDSCH scheduled by the PDCCH of DCI format 1_1 CRC scrambled by C-RNTI, MCS-C-RNTI or CS-RNTI, if the upper layer parameter prb-BundlingType is set to'dynamicBundling', ( i) The upper layer parameters bundleSizeSet1 and bundleSizeSet2 are

Set two sets of values, (ii) the first set is one or more of {2, 4, wideband}

Can take values (take), (iii) the second set is one of {2, 4, wideband}

Can take a value.

When the PRB bundling size indicator signaled through DCI format 1_1 is set to '0', the terminal receives the PDSCH scheduled by the same DCI

In the second set of values

You can use values. PRB bundling size indicator signaled through DCI format 1_1 is set to '1',

When one value is set for the first set of values, the UE receives the PDSCH scheduled by the same DCI.

The two values for the first set of values are'n2-wideband' (two

Values correspond to 2 and wideband) or'n4-wideband' (both

Values correspond to 4 and wideband), the UE may use the value as follows when receiving the PDSCH scheduled by the same DCI: (i) The scheduled PRBs are continuous and the size of the scheduled PRBs is

In excess,

May be equal to the scheduled bandwidth, or, (ii) otherwise,

May be set to 2 or 4, which are the remaining set values.

When the terminal receives the PDSCH scheduled by the PDCCH of DCI format 1_1 CRC scrambled by C-RNTI, MCS-C-RNTI or CS-RNTI, when the upper layer parameter prb-BundlingType is set to'staticBundling',

The value can be set as a single value indicated by the upper layer parameter bundleSize .

(i) To the terminal, the nominal RBG size for a specific bandwidth part (BWP) is set to P=2, or (ii) to the terminal in the upper layer parameter vrb-ToPRB-Interleaver in the PDSCH-Config for a specific bandwidth part (BWP). When the interleaving unit for VRB-to-PRB mapping is set to 2, the terminal

You might not expect the value to be set to 4.

5. 본 문서에서 개시하는 단말 및 기지국의 동작 예5. Examples of operations of terminals and base stations disclosed in this document

In the present disclosure, the term terminal may be replaced with a user equipment (UE).

In the present disclosure, the higher layer signaling may include radio resource control (RRC) signaling, MAC CE, and the like.

In the present disclosure, a transmission reception point (TRP) may be extended and applied to a beam.

In the present disclosure, a beam may be replaced with a resource.

According to the present disclosure, unlike the LTE system, the UE may transmit a scheduling request (SR) to the base station in both cases where there is no UL data to be transmitted (eg, case 1) and when there is UL data to be transmitted (eg, case 2). To this end, the terminal may transmit different SR information according to case 1 and case 2. For example, in case 1, the SR may have a value of'-1', and in case 2, the SR may have a value of'+1'.

Hereinafter, a detailed method of determining the PRG size between multiple PDSCHs will be described in detail.

14 is a diagram briefly illustrating an operation of a UE receiving different PDSCHs from different TRPs according to the present disclosure. As shown in FIG. 14, PDSCH#0/#1 received from respective TRPs may be received through the same or partially overlapping time/frequency resources.

At this time, as shown in FIG. 14, the two PDSCHs are entirely overlapped in the frequency domain (fully overlapped), but the PRG size for each PDSCH may be different.

As shown in FIG. 14, the PRG sizes of PDSCH #0 and PDSCH #1 may be set to 4 (RBs) and 2 (RBs), respectively. In this case, the UE may group DMRSs for PDSCH#0 in units of 4RBs and perform channel estimation in units of the group. On the other hand, the UE may group DMRSs for PDSCH#1 in units of 2RBs, and perform channel estimation in units of the group. In addition, when designing an IRC (Interference Rejection Combining) receiver filter for data detection of PDSCH#0, the terminal is a desired channel (e.g., a channel using DMRS for PDSCH#0) and an interference channel (e.g., for PDSCH#1). A channel using DMRS) can be used. In this case, the receiver filter may be calculated/determined in RE units.

For the above configuration, the base station may transmit two DCIs each scheduling the two PDSCHs to the terminal. At this time, if the terminal fails to detect one of the two DCIs, a problem may occur.

As an example, when the terminal fails to detect the DCI scheduling PDSCH #1 (e.g., fails to detect the DCI due to channel interference or an operation error of the terminal), the terminal may receive only PDSCH #0. . In this case, as illustrated in FIG. 14, even if different interferences occur within the same PRG, the UE cannot know this.

As shown in FIG. 14, A and B of FIG. 14(b) are included in the same PRG from the viewpoint of PDSCH#0, but A and B of FIG. 14(b) are included in two different PRGs from the viewpoint of PDSCH#1. It corresponds. If the terminal can know this, the terminal can cope with it through a separate implementation. On the other hand, when the terminal does not detect some DCI (e.g., when the DCI scheduling PDSCH #1 cannot be detected and the existence of PDSCH #1 is not known), the terminal implements a blind method for A and B It can be very difficult to know that the interfering channels are completely different. In addition, it may be very difficult for the terminal to find out such a difference in implementation.

As shown in FIG. 15, if it can be assumed that the PRG sizes of the two PDSCHs are always the same, the UE can assume that at least the interference channel within a specific PRG does not change. Therefore, even if the terminal loses some DCI, it may be very advantageous in estimating an interference channel.

As an example, as shown in FIG. 15, the DMRS port group (or CDM group) for PDSCH #0 and PDSCH #1 is called {DMRS port #0/#1} and {DMRS port #2/#3}, respectively. I assume. At this time, it is assumed that the terminal has lost the DCI scheduling PDSCH#1 (missing). In this case, the UE may estimate a requested channel of PDSCH#0 in 4RB units using DMRS port #0/#1. And, based on the assumption (e.g., the PRGs of two different PDSCHs are the same), the terminal can check whether there is a signal transmitted from the DMRS port #2 or #3 in PRG units of PDSCH #0 have. In this case, if the test is performed in units of PRG, more samples can be obtained, and the terminal can improve blind detection performance. As a result, even if the terminal loses the DCI scheduling PDSCH #1, the terminal can effectively estimate the interference channel due to PDSCH #1 in regions A and B of FIG. 15, and as a result, detection of PDSCH #0 Can improve performance.

Alternatively, as in the case of FIG. 14, it may not be assumed that the PRG sizes of the two PDSCHs are always the same. In this case, when the UE loses the DCI scheduling PDSCH #1, the UE must blindly detect PDSCH #1 in RB units. This is because no assumptions can be made about the interference channel. In this case, since the unit used for the interference channel estimation is 2RB, the interference channel estimation performance may be deteriorated when compared to the above case (eg, the unit used for the interference channel estimation is 4RB).

16 is a diagram illustrating a case in which different PDSCHs partially overlap according to the present disclosure. As shown in Figure 16, A region can be completely overlapped (fully overlap) at least in units of PRG. In this case, even if the terminal loses the DCI scheduling PDSCH#1, the terminal can estimate the interference channel in units of PRG. Accordingly, the UE can detect with a high probability that the PDSCH #1 channel exists as an interference channel in region A and that the PDSCH #1 channel does not exist in region B.

5.1. Example 1

When PDSCHs transmitted by different TRPs overlap (partially) on time/frequency resources, the UE can expect that the PRGs (or PRG sizes) of the PDSCHs are the same.

In other words, when PDSCHs scheduled by different DCIs overlap (partially) on time/frequency resources, the UE can expect that the PRGs (or PRG sizes) of the PDSCHs are the same. This configuration can be extended and applied to all the operation examples described later.

5.2. Second operation example

In the first operation example, the UE may expect that different PDSCHs are totally overlapped or not overlapped in PRG units.

As an example, assuming that the RBG unit is 2RB and the PRG unit is 4RB, the base station may allocate resources as shown in FIG. 17. In this case, when the terminal loses the DCI scheduling PDSCH #1, even if the terminal assumes that the PRGs of the PDSCHs are the same, a problem may occur that only part of PDSCH #1 overlaps in region A. In this case, the UE may experience difficulty in estimating the presence or absence of PDSCH#1 in region A and an interference channel.

On the other hand, according to the second operation example, the base station may only set resources as shown in (a) or (b) of FIG. 18, instead of setting resources as shown in FIG. 17. In this case, the UE may not suffer from the above-described difficulties even if the PDSCH#1 is present and the interference channel estimation is performed in units of PRG.

The second operation example according to the present disclosure may be extended and applied as follows when the PRGs of the two PDSCHs are different. More specifically, when PDSCHs transmitted from different TRPs are (partially) overlapped on time/frequency resources and it is expected that the PRGs of the PDSCHs are different, the UE may overlap the PDSCHs entirely based on the minimum value among the PRG values Or, you can expect not to overlap.

As a specific example, it is assumed that the PRG of PDSCH #0 is 4, and the terminal loses the DCI scheduling PDSCH #1. In this case, when the UE expects the PRG size of PDSCH#1 to be 2, the UE may expect that the two PDSCHs are entirely overlapped or not overlapped in units of at least 2 PRGs (eg, FIG. 19 ). In this case, the UE may estimate the presence or absence of PDSCH#1 and an interference channel in units of two PRGs.

5.3. Third operation example

In the first operation example, the terminal may expect that the RBG size is always greater than or equal to the PRG size (excluding wideband).

The problem according to FIG. 17 occurs because the RBG size is larger than the PRG size. Therefore, as in the third operation example, when the terminal expects that the RBG size is always greater than or equal to the PRG size (excluding wideband), the above problem may no longer occur. For example, when the RBG size is 4, the base station cannot support resource configuration as shown in FIG. 17 and may only support resource configuration as illustrated in FIG. 18.

5.4. 4th operation example

When PDSCHs transmitted by different TRPs overlap (partially) on time/frequency resources and the PRG of one PDSCH is wideband, the UE can expect that the PRG of the other PDSCH is 2 (or 4). In addition, the UE may expect that different PDSCHs are entirely overlapped in a PRG unit of the 2 size (or 4 size).

In FIG. 20, it is assumed that the PRGs of PDSCH#0 and PDSCH#1 are set to'wideband' and '4', respectively. According to the above-described first and second operation examples, the PRGs of the two PDSCHs should be the same, which may be excessive restriction on the PRG from the perspective of PDSCH#1. Also, this may affect the throughput.

Meanwhile, in the case of FIG. 21, the first operation example described above is satisfied, but the second operation example is not. Accordingly, when the UE performs blind detection of PDSCH#1 in region B of FIG. 21, the performance of the UE cannot be guaranteed. In order to satisfy this, the frequency domains of PDSCH#0 and PDSCH#1 must be entirely overlapped.

In a fourth operation example according to the present disclosure, a scheme for relaxing the above restrictions on the PRG and the frequency domain is disclosed.

As a first example, if the PRG of PDSCH #0 in FIG. 20 is set to'wideband' and the terminal loses the DCI scheduling PDSCH #1, the terminal may expect the PRG of PDSCH #1 to be 4.

As a second example, when the PRG of PDSCH #0 in FIG. 21 is set to'wideband' and the terminal loses the DCI for scheduling PDSCH #1, the terminal may expect the PRG of PDSCH #1 to be 4.

Meanwhile, FIG. 21 shows that the two PDSCs are entirely overlapped in the frequency domain with at least 4 units of PRG. Accordingly, the terminal may not expect resource allocation as shown in FIG. 22.

5.5. 5th operation example

When PDSCHs transmitted by different TRPs overlap (partially) on time/frequency resources and the PRG of one PDSCH is set to'wideband', the UE entirely overlaps the PDSCHs in the frequency domain, and the PRG of the PDSCHs Is expected to be the same as'wideband'.

5.6. 6th operation example

When PDSCHs transmitted by different TRPs overlap (partially) on time/frequency resources, the UE may expect that different PDSCHs are entirely overlapped in units of 2 PRBs (or 4 PRBs).

In the present disclosure, the PRG size may have a minimum of 2 (size). Therefore, even when the terminal loses the DCI scheduling PDSCH #1, the terminal can expect the PRG of PDSCH #1 to be 2. In the case of FIG. 23, the assumption of the UE as described above may be useful in finding the presence or absence of PDSCH#1 and an interference channel.

In particular, according to the'resource allocation type 0'defined in the NR Rel-15 standard document, the minimum unit of RBG is 2, so the assumption can always be valid.

On the other hand, according to'resource allocation type 1'defined in the NR Rel-15 standard document, resource allocation as shown in FIG. 24 may be possible. In this case, the aforementioned assumption of the terminal may be rather harmful in the A/D (Analog to Digital) domain.

Accordingly, according to the sixth operation example, the base station may support resource allocation as shown in FIG. 23 (eg, (a) or (b) of FIG. 23) instead of resource allocation as illustrated in FIG. 24.

5.7. 7th operation example

When PDSCHs transmitted by different TRPs are (partially) overlapped on time/frequency resources and resources are allocated based on'resource allocation type 0', if the RBG size is equal to or greater than 4, the UE has a PRG size of 2 Can not expect. On the other hand, in the case of the above, if the RBG size is equal to 2, the UE can expect that different PDSCHs are entirely overlapped in PRG units in the frequency domain. In the case of the above, if the RBG size is equal to or greater than 4, the UE can expect that different PDSCHs are entirely overlapped or not overlapped in units of 4PRGs in the frequency domain.

According to the above-described operation example, the PRG size available according to the RBG size is as follows.

(If RBG size = 2) PRG size = 2, 4, wideband

(If RBG size = 4) PRG size = 4, wideband

(If RBG size> 4) PRG size = 4, wideband

In the present disclosure, when the RBG size is equal to or greater than 4, the UE may expect that different PDSCHs are entirely overlapped in units of 4PRGs in the frequency domain. Accordingly, even when the terminal loses the DCI scheduling PDSCH#1, in the case of FIGS. 15 and 16, the terminal can always expect the PRG of PDSCH#1 to be 4.

5.8. Additional Example 1

In the present disclosure, specific methods of a PRB bundling size and resource allocation between a plurality of PDSCHs are disclosed. In this case, the plurality of PDSCHs may be defined as follows. As an example, in the plurality of PDSCHs, time/frequency resources of PDSCHs scheduled by each of DCIs included in two or more different search regions (or CORESETs) serviced to one terminal may partially/fully overlap.

If the time/frequency resources of the two PDSCHs partially/fully overlap, the UE may assume that the precoding of the other PDSCH does not differ within the PRG of one PDSCH. In this case, the UE can estimate the interference channel in PRG units, thereby improving the interference channel estimation performance and reducing UE complexity. To this end, as previously disclosed, the first to seventh operation examples may be considered.

In the present disclosure, in a multi-TRP transmission scheme, a method of implementing interference channel estimation of a terminal through a PRB bundling size and resource allocation limitation between a plurality of PDSCHs may be more simply defined. As a method for this, a plurality of operation examples (eg, first and second operation examples) among the aforementioned operation examples may be simultaneously applied.

In the present disclosure, the above-described operation examples are applied only when the PRG size is set to 2 or 4 RB, and may not be applied when the PRG is set to WB (wideband).

When the PRG is set to WB, all RBs through which the PDSCH is transmitted may be defined as one PRG. At this time, according to the second operation example, the two PDSCHs should be allocated to exactly the same RB (ie, fully overlapped) or be allocated to different RBs without intersection (ie, non-overlapped). If the two TRPs are non-ideal backhaul and dynamic coordination is difficult, such resource allocation may not be possible.

Accordingly, when the PRG is WB, considering that the PRGs of the two TRPs may be different, it may be preferable that a separate limitation is not applied to the resource allocation method. Alternatively, in the case of multi-TRP transmission, the terminal may not expect the PRG to be set to WB, and the base station may not set the PRG to WB.

In the present disclosure, the example of the first and second operations described above may be redefined as follows. In the following, although it is limited to the case of PRG = 2 or 4, the configuration can be extended and applied even when PRG = WB.

1) The UE may not expect that the precoding of one PDSCH has a PRG-level grid different from other PDSCHs having a PRG size of 2 or 4 (The UE does not expect the precoding of one PDSCH to be different in the PRG-level grid of another PDSCH with PRG =2 or 4).

2) The UE may not expect that the resource allocation of one PDSCH is not aligned on the PRG-level grid with another PDSCH having a PRG size of 2 or 4 (The UE does not expect the resource allocation of one PDSCH to be misaligned in the PRG-level grid of another PDSCH with PRG =2 or 4).

3) In the present disclosure, the prb-BundlingType IE included in the PDSCH-Config IE may be configured as shown in the following table. In this case, in consideration of the case in which the PRG size of the different PDSCHs described above is 2 or 4, the following configuration may be considered.

For example, in the case of staticBundling, the plurality of PDSCHs may always have the same bundling size. Therefore, the previously considered problem may not occur.

As another example, in the case of dynamicBundling, since bundleSizeSet1 includes n2-wideband, the previously considered problem may occur. Therefore, in the case of a terminal supporting multiple DCIs (or PDSCHs transmitted in different TRPs are (partially) overlapped in T/F resource), the terminal may not expect n2-wideband to be configured in bundleSizeSet1. Alternatively, in the above case, the terminal may not expect that n2-wideband in bundleSizeSet1 and n4 in bundleSizeSet2 are simultaneously set.

According to this configuration, it is possible to prevent PRG=2 and PRG=4 from being set for each of the plurality of PDSCHs.

5.9. Additional Example 2

In the present disclosure, the PRG bundling size of the two TRPs may be set differently.

25 is a diagram briefly showing an example in which different PRGs are set between two TRPs. In FIG. 25, it is assumed that the PRG for the first TRP is 4 and the PRG for the second TRP is set to 2.

In FIG. 25, in the case of allocating PDSCH 1 allocated within one PRG (eg, 4 RBs), the UE has two different interference covariance matrices to determine a minimum mean square error (MMSE) RX filter. Need to calculate This is because the precoder of PDSCH 2 for RB1 and RB2 and the precoder of PDSCH 2 for RB3 and RB4 are different. In this case, when the UE calculates a single co-shared matrix for the PRG, the inter-layer interference may not be sufficiently mitigated because the Rx filter is not optimized.

As shown in FIG. 25, when the PRG is set to a value of 2 or 4, the complexity of the terminal may increase in order to calculate a multiple interference co-shared matrix within each PRG. On the other hand, when the PRG is WB, the UE may need a plurality of interference co-shared matrices for one PRG for IRC performance. When the PRG size is 2 or 4, in order for the UE to calculate a single interference covariance matrix within each PRG, the precoding of PDSCH 2 must be the same as each PRG of PDSCH 1. In order to ensure the above conditions, the following alternatives can be considered.

Alt 1: When the PRG of the PDSCH is 2 or 4, the precoding of the PDSCH that overlaps with other whole/partially should be the same within each PRG (when PRG of a PDSCH is 2 or 4, the precoding of another fully/partially overlapped PDSCH should be the same in each PRG)

Alt 2: When the PRG of the PDSCH is 2 or 4, it should be the same as the PRG of the other fully/partially overlapping PDSCH (when PRG of a PDSCH is 2 or 4, PRG of another fully/partially overlapped PDSCH should be the same )

The difference between Alt 1 and Alt 2 is the scheduling flexibility. For Alt 1, the combinations of PRGs available for the two PDSCHs are (2,2), (2,WB), (4,4), (4,WB) and (WB, WB). On the other hand, for Alt 2, the combinations of PRGs available for the two PDSCHs are (2,2), (4,4) and (WB, WB).

In addition, in Alt 1, dynamic switching of the PRG value may be possible in a non-ideal backhaul scenario. For example, when the first TRP dynamically sets PRG={4, WB}, the second TRP may dynamically set PRG={4, WB}. On the other hand, dynamic switching of the PRG value for Alt 2 may not be possible in a non-ideal backhaul scenario.

In the present disclosure, the code point 0 of the PRG bundling size indicator having a size of 1 bit in the DCI may be semi-statically set to 4 or WB, and the code point 1 of the PRG bundling size indicator is semi-statically 4 and WB , 2/WB or 4/WB can be set. Thus, the 1-bit PRG bundling size indicator may be selected as one of the following: (4, WB), (4, 2/WB), (4, 4/WB), (WB, 4), or (WB , 2/WB). If the network semi-statically sets 4 by code point 0 and does not set 2/WB for code point 1, Alt 1 can be satisfied.

26 is a diagram briefly showing another example in which different PRGs are set between two TRPs. In FIG. 26, it is assumed that the PRG for the first TRP is 4 and the PRG for the second TRP is set to 4.

Even if Alt 1 or Alt 2 is satisfied, as shown in FIG. 26, in the case of'resource allocation type 1', the UE needs to calculate a multiple co-shared matrix. In FIG. 26, even if the precoder of PDSCH 2 is the same for RB2, RB3, and RB4, PDSCH 2 may not be transmitted for RB 1. As a result, when decoding PDSCH 1 allocated in one PRG (eg, 4 RBs), the UE needs to calculate two different interference covariance matrices to determine the MMSE RX filter. So, when PRG is 2 or 4, additional conditions other than Alt1 or Alt2 must be satisfied in order to calculate a single interference covariance matrix in each PRG. The additional condition is that when the PRG of the PDSCH is 2 or 4, the allocated resources of the PDSCH that are wholly/partially overlapped must be entirely overlapped or non-overlapping within each PRG. In the case of resource allocation type 0, if the PRG is 2 or 4, the RBG is always greater than or equal to the PRG, so the above problem may not occur.

Based on these items, in the case of partial/overlapping resource allocation, if the PRG of the PDSCH is 2 or 4, the precoding of other PDSCHs that are fully/partially overlapped should be the same in each PRG, and the overlapped PDSCH The allocated resources of each PRG must be entirely overlapped or non-overlapping (In case of partially/fully overlapped resource allocation, when PRG of a PDSCH is 2 or 4, the precoding of another fully/partially overlapped PDSCH should be the same in each PRG and allocated resource of the overlapped PDSCH should be either fully overlapped or non-overlapped in each PRG).

27 and 28 illustrate a network side (eg, TRP) in the context of multiple TRPs (eg, M-TRP, or multiple cells, hereinafter all TRPs may be replaced by cells) to which methods according to the present disclosure can be applied. 1, TRP 2) is a diagram showing a signaling method between a terminal.

In FIGS. 27 and 28, signaling between two TRPs and a UE is considered for convenience of description, but it goes without saying that the corresponding signaling scheme can be extended and applied to signaling between a plurality of TRPs and a plurality of terminals. In the following description, the network side may be one base station including a plurality of TRPs, and may be one cell including a plurality of TRPs.

Specifically, FIG. 27 shows a signaling configuration when a terminal receives multiple DCI in an M-TRP (or cell, hereinafter all TRP can be replaced by a cell) (e.g., when each TRP transmits DCI to the UE) Represents.

The UE may perform an initial access operation (eg, SS/PBCH block reception, RACH preamble transmission, etc.) for initial access.

The terminal may receive configuration information for transmission/reception based on multiple TRP from TRP 1 (and/or TRP 2) (M105). The configuration information may include information related to network side configuration (eg, TRP configuration), multiple TRP-based transmission/reception related resource information (resource allocation), and the like. In this case, the configuration information may be delivered through higher layer signaling (eg, RRC signaling, MAC-CE, etc.). In addition, when the setting information is predefined or set, the corresponding step may be omitted.

Thereafter, the UE may receive DCI 1 from TRP 1 and Data 1 scheduled by the DCI 1 (M110-1). In addition, the terminal may receive DCI 2 from TRP 2 and Data 2 scheduled by the DCI 2 (M110-2). For example, each TRP can apply the method (section B / C / D) described in the present invention in the process of transmitting DCI / Data, and the terminal is based on the above-described method (section B / C / D). Thus, DCI/Data can be received.

In addition, DCI (eg, DCI 1, DCI 2) and Data (eg, Data 1, Data 2) may be transmitted through a control channel (eg, PDCCH, etc.) and a data channel (eg, PDSCH, etc.), respectively. In addition, steps M110-1 and M110-2 may be performed simultaneously, or one may be performed earlier than the other.

Thereafter, the UE may decode Data 1 and Data 2 received from TRP 1 and TRP 2 (M115). For example, the UE may decode Data 1 and Data 2 based on the above-described method (section B / C / D).

Thereafter, the UE may transmit HARQ-ACK information (eg, ACK information, NACK information, etc.) for Data 1 and/or Data 2 to TRP 1 and/or TRP 2 (M120-1, M120-2). In this case, HARQ-ACK information for Data 1 and Data 2 may be combined into one. In addition, the terminal is configured to transmit only HARQ-ACK information to a representative TRP (eg, TRP 1), and transmission of HARQ-ACK information to another TRP (eg, TRP 2) may be omitted.

In this regard, the operation of the TRP and/or the terminal may be implemented by an apparatus to be described below. For example, TRP may correspond to a transmitting device, a terminal may correspond to a receiving device, and vice versa may also be considered.

Specifically, FIG. 28 is a case where the UE receives a single DCI in an M-TRP (or M-cell, hereinafter all TRP can be replaced by a cell) (e.g., when one TRP transmits DCI to the UE) Shows the signaling configuration of In FIG. 28, it is assumed that TRP 1 is a representative TRP for transmitting DCI.

The terminal may perform an initial access operation for initial access.

The terminal may receive configuration information for transmission/reception based on multiple TRP from TRP 1 (and/or TRP 2) (M205). The configuration information may include information related to network side configuration (eg, TRP configuration), multiple TRP-based transmission/reception related resource information (resource allocation), and the like. In this case, the configuration information may be delivered through higher layer signaling (eg, RRC signaling, MAC-CE, etc.). In addition, when the setting information is predefined or set, the corresponding step may be omitted.

Thereafter, the terminal may receive DCI from TRP 1 and Data 1 scheduled by the DCI (M210-1). In addition, the terminal may receive Data 2 from TRP 2 (M210-2). Here, DCI may be set to be used for scheduling for both Data 1 and Data 2. For example, each TRP can apply the method (section B / C / D) described in the present invention in the process of transmitting DCI / Data, and the terminal is based on the above-described method (section B / C / D). Thus, DCI/Data can be received.

In addition, DCI and Data (eg, Data 1, Data 2) may be transmitted through a control channel (eg, PDCCH, etc.) and a data channel (eg, PDSCH, etc.), respectively. In addition, steps M210-1 and M210-2 may be performed simultaneously, or one may be performed earlier than the other.

Thereafter, the UE may decode Data 1 and Data 2 received from TRP 1 and TRP 2 (M215). For example, the UE may decode Data 1 and Data 2 based on the above-described method (section B / C / D).

Thereafter, the UE may transmit HARQ-ACK information (eg, ACK information, NACK information, etc.) for Data 1 and/or Data 2 to TRP 1 and/or TRP 2 (M220-1, M220-2). In this case, depending on the number of codewords, HARQ-ACK information for Data 1 and/or Data 2 may be combined or separated into one. In addition, the terminal is configured to transmit only HARQ-ACK information to a representative TRP (eg, TRP 1), and transmission of HARQ-ACK information to another TRP (eg, TRP 2) may be omitted.

The terminal may perform a network access procedure to perform the procedures and/or methods described/suggested above. For example, while accessing a network (eg, a base station), the terminal may receive system information and configuration information necessary to perform the procedures and/or methods described/suggested above and store them in a memory. Configuration information required for the present disclosure may be received through higher layer (eg, RRC layer; Medium Access Control, MAC, layer, etc.) signaling.

In an NR system, a physical channel and a reference signal may be transmitted using beam-forming. When beam-forming-based signal transmission is supported, a beam-management process may be involved in order to align beams between the base station and the terminal. In addition, the signal proposed in the present disclosure may be transmitted/received using beam-forming. In the Radio Resource Control (RRC) IDLE mode, beam alignment may be performed based on a Sync Signal Block (SSB). On the other hand, in the RRC CONNECTED mode, beam alignment may be performed based on CSI-RS (in DL) and SRS (in UL). Meanwhile, when beam-forming-based signal transmission is not supported, an operation related to a beam may be omitted in the following description.

Referring to FIG. 29, a base station (eg, BS) may periodically transmit an SSB (S2902). Here, SSB includes PSS/SSS/PBCH. SSB can be transmitted using beam sweeping. Thereafter, the base station may transmit Remaining Minimum System Information (RMSI) and Other System Information (OSI) (S2904). The RMSI may include information (eg, PRACH configuration information) necessary for the terminal to initially access the base station. Meanwhile, after performing SSB detection, the UE identifies the best SSB. Thereafter, the terminal may transmit the RACH preamble (Message 1, Msg1) to the base station using the PRACH resource linked/corresponding to the index (ie, the beam) of the best SSB (S2906). The beam direction of the RACH preamble is associated with the PRACH resource. The association between the PRACH resource (and/or the RACH preamble) and the SSB (index) may be set through system information (eg, RMSI). Thereafter, as part of the RACH process, the base station transmits a RAR (Random Access Response) (Msg2) in response to the RACH preamble (S2908), and the UE uses the UL grant in the RAR to send Msg3 (e.g., RRC Connection Request). After transmitting (S2910), the base station may transmit a contention resolution message (Msg4) (S2912). Msg4 may include RRC Connection Setup.

When an RRC connection is established between the base station and the terminal through the RACH process, subsequent beam alignment may be performed based on SSB/CSI-RS (in DL) and SRS (in UL). For example, the terminal may receive an SSB/CSI-RS (S2914). SSB/CSI-RS may be used by the UE to generate a beam/CSI report. Meanwhile, the base station may request a beam/CSI report from the terminal through DCI (S2916). In this case, the UE may generate a beam/CSI report based on the SSB/CSI-RS, and transmit the generated beam/CSI report to the base station through PUSCH/PUCCH (S2918). The beam/CSI report may include a beam measurement result, information on a preferred beam, and the like. The base station and the terminal may switch the beam based on the beam/CSI report (S2920a and S2920b).

Thereafter, the terminal and the base station may perform the procedures and/or methods described/suggested above. For example, the UE and the base station process the information in the memory according to the proposal in the present disclosure based on the configuration information obtained in the network access process (e.g., system information acquisition process, RRC connection process through RACH, etc.) Or may process the received radio signal and store it in a memory. Here, the radio signal may include at least one of a PDCCH, a PDSCH, and a reference signal (RS) in case of a downlink, and may include at least one of a PUCCH, a PUSCH, and an SRS in case of an uplink.

In an example applicable to the present disclosure, the terminal receives a synchronization signal / physical broadcast channel (SS/PBCH) block including a synchronization signal (SS) and a physical broadcast channel (PBCH) from the base station. Can (S3010, S3110). In response, the base station may transmit an SS/PBCH block to the terminal (S3010 and S3210).

Based on the received SS/PBCH block, the UE may perform an access procedure to the base station including transmission of a random access channel (RACH) preamble (S3020 and S3120). In response to this, the base station may also establish a connection with the terminal (S3020 and S3220).

In addition, the terminal and the base station for which the connection is established based on the above procedure may operate as follows.

More specifically, the UE may receive configuration information related to dynamic bundling for a precoding resource block (PRB) from the base station (S3030, S3130). In response to this, the base station may transmit configuration information related to PRB dynamic bundling to the terminal (S3030 and S3230).

-First bundling size setting information indicating that the size of dynamic bundling is 2 PRB

-Second bundling size setting information indicating that the size of dynamic bundling is 4 PRB

-3rd bundling size setting information indicating that the size of dynamic bundling is wideband

The UE may receive a control signal (eg, first downlink control information (DCI)) for scheduling a first physical downlink shared channel (PDSCH) from the base station ( S3040, S3140). In response, the base station may transmit the control signal to the terminal (S3040 and S3240).

The terminal, based on the configuration information and the control signal (eg, first DCI), (i) no other PDSCH overlapping the first PDSCH in the time domain and the frequency domain, or (ii) the time domain And a second PDSCH overlapping the first PDSCH in the frequency domain, the first PDSCH and the second PDSCH in the frequency domain are in units of a precoding resource block group (PRB group; PRG) having the same size. It can be assumed that they overlap (S3050, S3150).

The terminal may receive a data signal from the base station through the first PDSCH based on the assumption (S3060 and S3160). In response to this, the base station may transmit the data signal to the terminal through the first PDSCH (S3060 and S3250).

Additionally, the base station may transmit a (additional) control signal (eg, a second DCI) for scheduling a second PDSCH to the terminal or another terminal. In this case, based on the setting information, the first DCI and the second DCI, (i) the first PDSCH and the second PDSCH are set so as not to overlap in the time domain and the frequency domain, or (ii) When the first PDSC and the second PDSCH in the time domain and the frequency domain overlap, the first PDSCH and the second PDSCH in the frequency domain are a precoding resource block group (PRB group; PRG) having the same size. It can be set to overlap in units.

In the present disclosure, when the terminal receives the data signal through the first PDSCH based on the assumption, the terminal receives the data signal through the first PDSCH based on the assumption-based interference channel estimation. It may include receiving.

In the present disclosure, the terminal may perform at least one or more of additional operations as follows.

-Receiving a second DCI scheduling a second PDSCH from the base station

-The terminal receives the (additional) data signal through the second PDSCH based on the configuration information and the assumption based on the second DCI

-Transmit acknowledgment information related to the received data signal to the base station

In the present disclosure, the UE may expect that the size of a resource block group (RBG) for the first PDSCH is greater than or equal to the size of the PRG for the first PDSCH.

In this case, based on the RGB size for the first PDSCH such as 2, the terminal may expect that candidate values of the PRG size for the first PDSCH include 2 PRBs, 4PRBs, and wideband.

As another example, based on the RGB size for the first PDSCH equal to or greater than 4, the terminal may expect that candidate values of the PRG size for the first PDSCH include 4PRB and wideband.

It is obvious that examples of the above-described proposed method may also be included as one of the implementation methods of the present disclosure, and thus may be considered as a kind of proposed method. In addition, the above-described proposed schemes may be implemented independently, but may be implemented in the form of a combination (or merge) of some proposed schemes. As for the information on whether to apply the proposed methods (or information on the rules of the proposed methods), a rule can be defined so that the base station informs the UE through a predefined signal (eg, a physical layer signal or a higher layer signal) have.

The present disclosure may be embodied in other specific forms without departing from the technical idea and essential features described in the present disclosure. Therefore, the detailed description above should not be construed as restrictive in all respects and should be considered as illustrative. The scope of the present disclosure should be determined by reasonable interpretation of the appended claims, and all changes within the equivalent scope of the present disclosure are included in the scope of the present disclosure. In addition, the embodiments may be configured by combining claims that do not have an explicit citation relationship in the claims, or may be included as new claims by amendment after filing.

Embodiments of the present disclosure can be applied to various wireless access systems. As an example of various wireless access systems, there is a 3rd Generation Partnership Project (3GPP) or a 3GPP2 system. Embodiments of the present disclosure can be applied not only to the various wireless access systems, but also to all technical fields to which the various wireless access systems are applied. Furthermore, the proposed method can be applied to a mmWave communication system using an ultra-high frequency band.

Additionally, embodiments of the present disclosure may be applied to various applications such as free-running vehicles and drones.

Claims

In a method for a terminal to receive a data signal in a wireless communication system,

Receiving a synchronization signal/physical broadcast channel (SS/PBCH) block including a sync signal (SS) and a physical broadcast channel (PBCH) from the base station;

Performing an access procedure to the base station including transmission of a random access channel (RACH) preamble based on the received SS/PBCH block;

Receiving, from the base station, configuration information related to dynamic bundling for a precoding resource block (PRB);

Receiving, from the base station, first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH);

Based on the configuration information and the first DCI, (i) there is no other PDSCH overlapping the first PDSCH in the time domain and the frequency domain, or (ii) the first PDSCH in the time domain and the frequency domain If there is a second PDSCH overlapping with, it is assumed that the first PDSCH and the second PDSCH in the frequency domain overlap in units of a precoding resource block group (PRB group) having the same size; And

And receiving the data signal through the first PDSCH based on the assumption.
The method of claim 1,

When the terminal receives the data signal through the first PDSCH based on the assumption,

And receiving, by the terminal, the data signal through the first PDSCH based on the estimation of an interference channel based on the assumption.
The method of claim 1,

The above setting information,

First bundling size setting information indicating that the size of the dynamic bundling is 2 PRB,

Second bundling size setting information indicating that the size of the dynamic bundling is 4 PRB,

3rd bundling size setting information indicating that the size of the dynamic bundling is a wideband, including one of.
The method of claim 1,

The second PDSCH is scheduled for (i) the terminal or (ii) another terminal, a method of receiving a data signal of a terminal.
The method of claim 1,

The method of receiving a data signal of the terminal,

Receiving a second DCI scheduling the second PDSCH from the base station; And

The method further comprising receiving the data signal through the second PDSCH based on the configuration information and the assumption based on the second DCI.
The method of claim 5,

The first PDSCH and the second PDSCH,

A method of receiving a data signal of a terminal, each received from different transmission reception points (TRPs).
The method of claim 1,

The UE expects that the size of the resource block group (RBG) for the first PDSCH is greater than or equal to the size of the PRG for the first PDSCH.
The method of claim 1,

Based on the size of a resource block group (RBG) for the first PDSCH, the UE expects candidate values of the PRG size for the first PDSCH.
The method of claim 8,

Based on the RGB size for the first PDSCH such as 2, the terminal expects that the candidate values of the PRG size for the first PDSCH include 2 PRB, 4PRB, and wideband, the data of the terminal How to receive signals.
The method of claim 8,

Based on the RGB size for the first PDSCH equal to or greater than 4, the terminal expects that the candidate values of the PRG size for the first PDSCH include 4PRB and a wideband, the data signal of the terminal How to receive.
The method of claim 1,

The method of receiving a data signal of the terminal,

The method further comprising transmitting acknowledgment information related to the data signal to the base station.
In a terminal receiving a data signal in a wireless communication system,

At least one transmitter;

At least one receiver;

At least one processor; And

And at least one memory that is operatively connected to the at least one processor and stores instructions for causing the at least one processor to perform a specific operation when executed,

The specific action is:

Receiving a synchronization signal/physical broadcast channel (SS/PBCH) block including a sync signal (SS) and a physical broadcast channel (PBCH) from the base station;

Performing an access procedure to the base station including transmission of a random access channel (RACH) preamble based on the received SS/PBCH block;

Receiving, from the base station, configuration information related to dynamic bundling for a precoding resource block (PRB);

Receiving, from the base station, first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH);

Based on the configuration information and the first DCI, (i) there is no other PDSCH overlapping the first PDSCH in the time domain and the frequency domain, or (ii) the first PDSCH in the time domain and the frequency domain If there is a second PDSCH overlapping with, it is assumed that the first PDSCH and the second PDSCH in the frequency domain overlap in units of a precoding resource block group (PRB group) having the same size; And

And receiving the data signal through the first PDSCH based on the assumption.
The method of claim 12,

The terminal communicates with at least one of a mobile terminal, a network, and an autonomous vehicle other than a vehicle including the terminal.
In a base station for transmitting a data signal in a wireless communication system,

At least one transmitter;

At least one receiver;

At least one processor; And

And at least one memory that is operatively connected to the at least one processor and stores instructions for causing the at least one processor to perform a specific operation when executed,

The specific action is:

Transmitting a synchronization signal/physical broadcast channel (SS/PBCH) block including a sync signal (SS) and a physical broadcast channel (PBCH) to the terminal;

Performing a connection establishment procedure with the terminal based on the transmitted SS/PBCH block;

Transmitting configuration information related to dynamic bundling for a precoding resource block (PRB) to the terminal;

To the terminal, (i) first downlink control information (DCI) for scheduling a first physical downlink shared channel (PDSCH) and (ii) a second for scheduling a second PDSCH Transmit DCI; And

Including transmitting the first PDSCH and the second PDSCH to the terminal,

Based on the setting information, the first DCI and the second DCI:

The first PDSCH and the second PDSCH are set so as not to overlap on the time domain and the frequency domain, or,

When the first PDSC and the second PDSCH in the time domain and the frequency domain overlap, the first PDSCH and the second PDSCH in the frequency domain are a precoding resource block group (PRB group; PRG) having the same size. The base station is set to overlap in units.