Patent Description:
Therefore, the <NUM> or pre-<NUM> communication system is also called a "Beyond <NUM> Network" or a "Post LTE System". In the <NUM> system, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as an advanced coding modulation (ACM), and filter bank multi carrier (FBMC), non-orthogonal multiple access(NOMA), and sparse code multiple access (SCMA) as an advanced access technology have also been developed.

In a <NUM> communication system, coordinated transmission using a plurality of cells, transmission and reception points (TRP), or beams may be performed, and various service requirements may be satisfied via the coordinated transmission. In particular, joint transmission (JT) is a representative transmission technology for the coordinated transmission, and the technology enables enhancement of the intensity of a signal received by a terminal, by supporting one terminal via different cells, TRPs, and/or beams. <CIT> relates to detecting downlink control information, a terminal device, and a network device, which is an Art. <NUM>(<NUM>) EPC document for the invention. <NPL>, discusses DL multi-TRP/panel operation. <NPL>), discusses on timing between DCI indicating active BWP switching and active BWP switching.

There is a need to provide a method and device for efficiently transmitting control information for multiple pieces of data transmitted to a terminal, in order to efficiently support coordinated transmission.

Aspects of the present invention are provided in the independent claims. Preferred embodiments are provided in the dependent claims. The scope of the present invention is determined by the scope of the appended claims.

According to the disclosure, by proposing a method and device for efficiently designing a configuration of downlink control information supporting coordinated transmission, and authenticating the control information by a terminal receiving the control information, control information that efficiently supports coordinated transmission in a wireless communication system can be transmitted and received.

As used herein, the "unit" refers to a software element or a hardware element, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), which performs a predetermined function. However, the "unit" does not always have a meaning limited to software or hardware. The "unit" may be constructed either to be stored in an addressable storage medium or to execute one or more processors. Therefore, the "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, properties, procedures, sub-routines, segments of a program code, drivers, firmware, micro-codes, circuits, data, database, data structures, tables, arrays, and parameters. The elements and functions provided by the "unit" may be either combined into a smaller number of elements, or a "unit", or divided into a larger number of elements, or a "unit". Moreover, the elements and "units" or may be implemented to reproduce one or more CPUs within a device or a security multimedia card. Further, the "unit" in the embodiments may include one or more processors.

Hereinafter, the operation principle of the disclosure will be described in detail in conjunction with the accompanying drawings. In the following description of the disclosure, a detailed description of known functions or configurations incorporated herein will be omitted when it may make the subject matter of the disclosure unnecessarily unclear. The terms which will be described below are terms defined in consideration of the functions in the disclosure, and may be different according to users, intentions of the users, or customs. Therefore, the definitions of the terms should be made based on the contents throughout the specification. In the following description, a base station is an entity that allocates resources to terminals, and may be at least one of a gNode B, an eNode B, a Node B, a base station (BS), a wireless access unit, a base station controller, and a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. Examples of the base station and the terminal are not limited thereto. Further, the disclosure is applicable to FDD and TDD systems.

The disclosure relates to a communication technique for converging IoT technologies with a <NUM> communication system designed to support a higher data transfer rate beyond the <NUM> system, and a system therefor. The disclosure may be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail business, security and safety-related services, etc.) on the basis of <NUM> communication technologies and IoT-related technologies.

In the following description, terms referring to broadcast information, terms related to communication coverage, terms referring to state changes (as an example, event), terms referring to network entities, terms referring to messages, terms referring to device elements, and the like are illustratively used for the sake of convenience. Therefore, the disclosure is not limited by the terms as used below, and other terms referring to subjects having equivalent technical meanings may be used.

In the following description, the disclosure will be described using terms and names defined in the 3rd generation partnership project long term evolution (3GPP LTE) standards for the convenience of description. However, the disclosure is not limited by these terms and names, and may be applied in the same way to systems that conform other standards.

A wireless communication system is evolving from providing early voice-oriented services, to broadband wireless communication systems that provide high-speed and high-quality packet data services, such as communication standards, for example, 3GPP's high speed packet access (HSPA), long term evolution (LTE) or evolved universal terrestrial radio access (E-UTRA), LTE-advanced (LTE-A), LTE-Pro, 3GPP2's high rate packet data (HRPD), ultra-mobile broadband (UMB), IEEE's <NUM>. 16e, and the like.

An LTE system, which is a representative example of the broadband wireless communication system, employs an orthogonal frequency division multiplexing (OFDM) scheme in a downlink (DL), and employs a single carrier frequency division multiple access (SC-FDMA) scheme in an uplink (UL). The uplink refers to a radio link via which a terminal transmits data or a control signal to a base station, and the downlink refers to a radio link via which a base station transmits data or a control signal to a terminal. In a multiple access scheme, data or control information of each user is distinguished by assigning and operating time-frequency resources, in which data or control information for each user is carried, so as not to overlap each other, that is, to establish orthogonality.

A <NUM> communication system (hereinafter, a new radio or next radio (NR) system may be interchangeably used), which is a future communication system after LTE, should be able to freely reflect various requirements of users and service providers, and therefore services that satisfy various requirements should be supported in the <NUM> communication system. For example, services considered for the <NUM> communication system may include an enhanced mobile broadband (eMBB) communication, massive machine type communication (mMTC), ultra-reliability low latency communication (URLLC), and the like.

The eMBB aims to provide a data transmission rate that is further improved than a data transmission rate supported by existing LTE, LTE-A, or LTE-Pro. For example, in the <NUM> communication system, an eMBB should be able to provide a peak data rate of <NUM> Gbps in a downlink and a peak data rate of <NUM> Gbps in an uplink, from the perspective of a base station. The eMBB should provide an increased user perceived data rate of the terminal at the same time. In order to satisfy these requirements, improvement of transmission/reception technologies including a more advanced multi-input multi-output (MIMO) transmission technology is required. In addition, a data transmission rate required by the <NUM> communication system may be satisfied by using a frequency bandwidth wider than <NUM> in a frequency band of <NUM> to <NUM> or a frequency band of <NUM> or higher, instead of a frequency band of <NUM> used by the current LTE.

At the same time, mMTC is being considered to support application services, such as the Internet of Things (IoT), in the <NUM> communication system. In order to efficiently provide the Internet of Things, mMTC may require support for large-scale terminal access in a cell, improved coverage of a terminal, an improved battery time, and a reduced cost of a terminal. The IoT is attached to various sensors and various devices to provide communication functions, so that the IoT should be able to support a large number of terminals (for example, <NUM>,<NUM>,<NUM> terminals/km<NUM>) within a cell. Further, a terminal supporting mMTC is highly likely to be located in a shaded area that is not covered by the cell, such as the basement of a building, due to the nature of the service, so that it may require wider coverage compared to other services provided in the <NUM> communication system. Since a terminal supporting mMTC should be a low-cost terminal, and it is difficult to frequently exchange a battery of the terminal, a very long battery life time may be required.

Finally, URLLC, which is a cellular-based wireless communication service used for mission-critical purposes, is used for a remote control for a robot or machinery, industrial automation, an unmanned aerial vehicle, remote health care, an emergency alert, etc., and should provide communication that provides ultra-low latency and ultra-reliability. For example, a service that supports URLLC has requirements of an air interface latency less than <NUM> milliseconds and a packet error rate of <NUM>-<NUM> or less. Therefore, for the service that supports URLLC, the <NUM> system should provide a transmission time interval (TTI) smaller than that of other services, and at the same time, a design requirement that a wide resource should be allocated in a frequency band is required in the <NUM> system. However, the above-described mMTC, URLLC, and eMBB are merely examples of different service types, and service types, to which the disclosure is applied, are not limited to the above-described examples.

Services considered in the <NUM> communication system, which are described above, should be combined with each other and provided on the basis of one framework. That is, for efficient resource management and control, it is desirable that each of services is integrated into one system so as to be controlled and transmitted, rather than operated independently.

Hereinafter, an embodiment will be described using an LTE, LTE-A, LTE-A Pro, or NR system as an example, but the embodiment may also be applied to other communication systems having a similar technical background or channel type. Further, the embodiment may also be applied to other communication systems via some modifications without departing from the scope of the disclosure, according to determination by those skilled in the art. Hereinafter, frame structures of LTE, LTE-A, and <NUM> systems will be described with reference to the drawings, and a design direction of the <NUM> system will be described.

<FIG> is a diagram illustrating a time-frequency domain transmission structure of an LTE, LTE-A, NR, or similar wireless communication system.

<FIG> illustrates a basic structure of a time-frequency resource area that is a radio resource area in which data or control information of LTE, LTE-A, and NR systems based on a single carrier-frequency division multiple access (SC-FDMA) waveform or cyclic prefix (CP) OFDM (CP-OFDM) is transmitted.

In <FIG>, the horizontal axis represents a time domain and the vertical axis represents a frequency domain. A minimum transmission unit in the time domain of LTE, LTE-A, and <NUM> systems is an OFDM symbol or an SC-FDMA symbol, and Nsymb symbols <NUM> may be gathered and constitute one slot <NUM>. In the case of LTE and LTE-A, two slots including Nsymb symbols (where Nsymb=<NUM>) may be gathered and constitute one subframe <NUM>. According to some embodiments, in the case of a <NUM> communication system, two types of slot structures, which are a slot and a mini-slot (mini-slot or non-slot) may be supported. In the case of a <NUM> slot, Nsymb may have a value of <NUM> or <NUM>, and in the case of a <NUM> mini-slot, Nsymb may be configured to a value of <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM>. In LTE and LTE-A, a length of the slot is <NUM>, a length of the subframe is fixed at <NUM>, but in the case of the <NUM> communication system, the length of the slot or mini-slot may be changed flexibly according to a subcarrier spacing. In LTE and LTE-A, a radio frame <NUM> is a time domain unit including <NUM> subframes.

In LTE and LTE-A, the minimum transmission unit in the frequency domain is a subcarrier in units of <NUM> (where, a subcarrier spacing is fixed to <NUM>), and a bandwidth of the entire system transmission bandwidth includes a total of NBW subcarriers <NUM>. The flexible and scalable frame structure of the <NUM> system will be described later.

A basic unit of the time-frequency resource domain is a resource element (RE) <NUM> and may be represented by an OFDM symbol or SC-FDMA symbol index and a subcarrier index. A resource block (RB or physical resource block (PRB)) <NUM> may be defined by Nsymb consecutive OFDM symbols <NUM> in the time domain or NRB consecutive subcarriers <NUM> in the frequency domain and SC-FDMA symbols. Therefore, one RB <NUM> includes Nsymb x NRB REs <NUM>. In the LTE and LTE-A systems, data is mapped in units of RBs, and the base station performs scheduling for a predetermined UE in units of RB-pairs constituting one subframe. The number of SC-FDMA symbols or the number Nsymb of OFDM symbols is determined according to the length of a cyclic prefix added for each symbol to prevent interference between symbols. For example, when a general CP is applied, Nsymb = <NUM>, and when a scalable CP is applied, Nsymb = <NUM>. The scalable CP is applied to a system having a relatively larger radio transmission distance compared to the general CP, so as to enable orthogonality between symbols to be maintained. Values, such as a subcarrier spacing, a CP length, etc., are essential information for OFDM transmission or reception, and smooth transmission or reception may be possible only when the base station and the UE recognize the values as common values.

The frame structures of the LTE and LTE-A systems are designed in consideration of conventional voice and data communication, and are subject to limitations in scalability to satisfy various services and requirements, such as a <NUM> communication system. Therefore, in the <NUM> system, it is necessary to flexibly define and operate a frame structure in consideration of various services and requirements.

<FIG>, <FIG>, and <FIG> illustrate a scalable frame structure of the <NUM> system. The examples illustrated in <FIG>, <FIG>, and <FIG> are based on an essential parameter set defining a scalable frame structure, and the essential parameter set may include a subcarrier spacing, a CP length, a slot length, and the like.

In the early days when the <NUM> system is introduced, coexistence or dual mode operation with at least existing LTE and LTE-A systems (hereinafter, LTE/LTE-A) is expected. Based on this, the existing LTE/LTE-A may provide a stable system operation, and the <NUM> system may function to provide an improved service. Therefore, the scalable frame structure of the <NUM> system needs to include at least the frame structure of LTE/LTE-A or the essential parameter set. In <FIG>, an essential parameter set or a <NUM> frame structure, such as the frame structure of LTE/LTE-A, is illustrated. In the case of frame structure type A <NUM> illustrated in <FIG>, a subcarrier spacing is <NUM>, <NUM> symbols constitute a <NUM> slot, and a physical resource block (PRB) includes <NUM> subcarriers (= <NUM> = <NUM> x <NUM>).

Referring to <FIG>, in the case of frame structure type B <NUM> illustrated in <FIG>, a subcarrier spacing is <NUM>, <NUM> symbols constitute a <NUM> slot, and a PRB includes <NUM> subcarriers (= <NUM> = <NUM> x <NUM>). That is, compared to frame structure type A, the subcarrier spacing and PRB size are doubled, and the slot length and symbol length are cut in half.

Referring to <FIG>, in frame structure type C <NUM> illustrated in <FIG>, a subcarrier spacing is <NUM>, <NUM> symbols constitute a <NUM> subframe, and a PRB includes <NUM> subcarriers (= <NUM> = <NUM> x <NUM>). That is, compared to frame structure type A, the subcarrier spacing and PRB size are increased by <NUM> times, and the slot length and symbol length are decreased by <NUM> times.

That is, if the frame structure types are generalized, high scalability can be provided by making a subcarrier spacing, a CP length, a slot length, etc., which are included in the essential parameter set, have a relationship of an integer multiple to each other for each frame structure type. Further, a subframe having a fixed length of <NUM> may be defined to indicate a reference time unit irrelevant to the frame structure type. Therefore, one subframe includes one slot in the case of frame structure type A, one subframe includes two slots in the case of frame structure type B, and one subframe includes four slots in the case of frame structure type C. Of course, a scalable frame structure is not limited to the above-described frame structure type A, B, or C, and other subcarrier spacings, such as <NUM> and <NUM>, may also be applied, and in this case, it is obvious that different structures are possible.

The frame structure types described above may be applied by corresponding to various scenarios. In terms of a cell size, since a longer CP length is capable of supporting a larger cell, frame structure type A may support a relatively larger cell compared to frame structure types B and C. In terms of an operation frequency band, the larger a subcarrier spacing is, the more advantageous it is to recover phase noise in a high-frequency band, so that frame structure type C may support a relatively higher operation frequency compared to frame structure types A and B. In terms of a service point of view, a shorter subframe length is more advantageous to support an ultra-low latency service such as URLLC, so that frame structure type C is relatively suitable for a URLLC service, compared to frame structure types A and B. Multiple frame structure types may be multiplexed in one system so as to be operated in an integrated manner.

In NR, one component carrier (CC) or serving cell may include up to <NUM> RBs or more. Therefore, when a UE always receives a signal over the entire serving cell bandwidth, such as in the LTE system, power consumption of the UE may be extreme, and in order to solve this problem, it is possible for a base station to configure one or more bandwidth parts (BWPs) to the UE so as to support the UE to change a reception area within a cell. In the NR system, the base station may configure an "initial bandwidth part (initial BWP)" which is a bandwidth of a control resource set (hereinafter, referred to as CORESET) #<NUM> (or common search space (CSS)), to the UE via a master information block (MIB). Thereafter, the base station may configure an initial BWP (first BWP) of the UE via RRC signaling, and may notify the UE of at least one BWP configuration information via downlink control information (DCI) in the future. Thereafter, the base station may indicate which band the UE will use, by notifying of a BWP ID via DCI. If the UE fails to receive DCI in a currently allocated BWP for a certain time period or longer, the UE returns to a "default bandwidth part" and attempts to receive DCI.

<FIG> is a diagram illustrating an example of a bandwidth part configuration in the <NUM> communication system. <FIG> illustrates an example in which a UE bandwidth <NUM> is configured to two bandwidth parts, that is, a first bandwidth part <NUM> and a second bandwidth part <NUM>. A base station may configure one or more bandwidth parts to a UE, and may configure the following information for each bandwidth part.

In addition to the configuration information, various parameters related to a bandwidth part may be configured to the UE. The base station may transfer the information to the UE via higher layer signaling, for example, RRC signaling. At least one bandwidth part among the configured one or multiple bandwidth parts may be activated. Whether or not to activate the configured bandwidth part may be transferred from the base station to the UE in a semi-static manner via RRC signaling, or may be dynamically transferred via a MAC control element (CE) or DCI.

The configuration of a bandwidth part supported by the <NUM> communication system may be used for various purposes. For example, when a bandwidth supported by the UE is smaller than a system bandwidth, this may be supported via the bandwidth part configuration. For example, by configuring, for the UE, a frequency position (configuration information <NUM>) of the bandwidth part in Table <NUM>, the UE may transmit or receive data at a specific frequency position within the system bandwidth. As another example, for the purpose of supporting different numerologies, the base station may configure multiple bandwidth parts for the UE. For example, in order to support both data transmission and reception using a subcarrier spacing of <NUM> and a subcarrier spacing of <NUM> for the UE, two bandwidth parts may be configured to use the subcarrier spacings of <NUM> and <NUM>, respectively. Different bandwidth parts may be frequency division multiplexed (FDM), and when the base station and the UE are to transmit or receive data at a specific subcarrier spacing, a bandwidth part configured at the subcarrier spacing may be activated.

As another example, for the purpose of reducing power consumption of the UE, the base station may configure, for the UE, a bandwidth part having a different bandwidth size. For example, if the UE supports a very large bandwidth, for example, <NUM>, and always transmits or receives data via the corresponding bandwidth, very large power consumption may occur. In particular, in a situation where there is no traffic, it is very inefficient, in terms of power consumption, for the UE to monitor an unnecessary downlink control channel for a large bandwidth of <NUM>. Therefore, for the purpose of reducing the power consumption of the UE, the base station may configure, for the UE, a bandwidth part of a relatively small bandwidth, for example, a bandwidth part of <NUM>. In the situation where there is no traffic, the UE may perform monitoring in the bandwidth part of <NUM>, and if data is generated, the UE may transmit or receive the data by using the bandwidth part of <NUM> according to an indication of the base station.

<FIG> is a diagram illustrating a method of changing a dynamic configuration for a bandwidth part.

As described in Table <NUM>, a base station may configure one or more bandwidth parts for a UE, and information on a bandwidth of a bandwidth part, a frequency position of the bandwidth part, and the numerology of the bandwidth part, may be informed as a configuration for each bandwidth part. <FIG> illustrates an example in which two bandwidth parts are configured within a UE bandwidth <NUM> for one UE, wherein the two bandwidth parts include a first bandwidth part (BWP#<NUM>) <NUM> and a second bandwidth part (BWP#<NUM>) <NUM>. One or multiple bandwidth parts in the configured bandwidth may be activated, and a case where one bandwidth part is activated is considered in <FIG>. In <FIG>, BWP#<NUM><NUM> among bandwidth parts configured in slot #<NUM><NUM> is activated, the UE may monitor PDCCH in in a first control area (first CORESET, <NUM>) configured in BWP#<NUM><NUM>, and data <NUM> may be transmitted or received in BWP#<NUM><NUM>. A control area in which the UE receives PDCCH may be different according to a bandwidth part, which is activated, among the configured bandwidth parts, and a bandwidth in which the UE monitors the PDCCH may vary accordingly.

The base station may additionally transmit, to the UE, an indicator for switching the configuration of the bandwidth part. Here, switching of the configuration of the bandwidth part may be considered to be the same as an operation of activating a specific bandwidth part (for example, changing of activation from bandwidth part A to bandwidth part B). The base station may transmit a configuration switching indicator to the UE in a specific slot, and the UE may receive the configuration switching indicator from the base station, may determine a bandwidth part to be activated, by applying a switched configuration according to the configuration switching indicator from a specific time point, and then may monitor PDCCH in a control area configured in the activated bandwidth part.

In <FIG>, the base station may transmit, to the UE, a configuration switching indicator <NUM> that indicates switching of the activated bandwidth part from existing BWP #<NUM><NUM> to BWP #<NUM><NUM>, in slot #<NUM><NUM>. After receiving the corresponding indicator, the UE may activate BWP#<NUM><NUM> according to the content of the indicator. At this time, a transition time <NUM> for switching the bandwidth part may be required, and accordingly, a point in time when the active bandwidth part is switched and applied may be determined. <FIG> illustrates a case in which the transition time <NUM> of one slot is taken after the configuration switching indicator <NUM> is received. Data transmission or reception may not be performed during the transition time (that is, it may be understood as a guard period (GP) <NUM>). Accordingly, bandwidth part #<NUM><NUM> is activated in slot #<NUM><NUM> so that the UE may transmit or receive control information and data via the corresponding bandwidth part. The UE may monitor PDCCH in a second CORESET <NUM> of BWP#<NUM><NUM>.

The base station may preconfigure one or multiple bandwidth parts for the UE via higher layer signaling (e.g., RRC signaling), and the configuration switching indicator <NUM> may indicate activation, by mapping with one of the bandwidth part configurations preconfigured by the base station. For example, an indicator of log<NUM>N bits may select and indicate one of N preconfigured bandwidth parts. Table <NUM> below is an example of indicating configuration information for a bandwidth part by using a <NUM>-bit indicator.

The configuration switching indicator <NUM> for the bandwidth part described above may be transferred from the base station to the UE in the form of medium access control (MAC) control element (CE) signaling or L1 signaling (e.g., common DCI, group-common DCI, and UE-specific DCI).

A point in time, at which bandwidth part activation is to be applied according to the configuration switching indicator <NUM> for the bandwidth part described above, is as follows. The point in time, at which a configuration switch is to be applied, may be based on a predefined value (for example, applied from the back of N(=<NUM>) slot after the configuration switching indicator is received), may be configured by the base station for the UE via higher layer signaling (e.g., RRC signaling), or may be partially included in the content of the configuration switching indicator <NUM> and transmitted. Alternatively, the point in time may be determined by a combination of the above methods. After receiving the configuration switching indicator <NUM> for the bandwidth part, the UE may apply the switching configuration from the time point obtained by the above method.

In the NR system, the following detailed frequency axis resource allocation methods (frequency domain resource allocation (FD-RA)) are provided in addition to frequency axis resource candidate allocation via the bandwidth part indication. <FIG> is a diagram illustrating a frequency axis resource allocation method used in the NR system. This method may be configured via a higher layer, and there are three methods, such as type <NUM><NUM>, type <NUM><NUM>, and a dynamic switch <NUM>.

If a UE is configured to use only resource allocation (RA) type <NUM>, via higher layer signaling <NUM>, a part of DCI for allocation of PDSCH to the UE includes a bitmap including NRBG bits. Conditions for this will be described later. In this case, NRBG refers to the number of resource block groups (RBGs), which is determined as shown in Table <NUM> below according to the size of BWP allocated by the BWP indicator and a higher layer parameter of rbg-Size, and data is transmitted to an RBG indicated by <NUM> by the bitmap.

If the UE is configured to use only RA type <NUM>, via the higher layer signaling <NUM>, a part of the DCI for allocation of PDSCH to the UE includes frequency axis resource allocation information including <MAT> bits. Conditions for this will be described later. Based on this, a base station is able to configure a starting VRB <NUM> and a length <NUM> of a frequency axis resource continuously allocated therefrom. If the UE is configured to use both RA type <NUM> and RA type <NUM>, via the higher layer signaling <NUM>, a part of the DCI for allocation of PDSCH to the UE includes frequency axis resource allocation information including bits of a larger value <NUM> among a payload <NUM> for RA type <NUM> and a payload <NUM>, <NUM> for RA type <NUM>. Conditions for this will be described later. In the case of <NUM> due to addition of one bit to a most significant bit (MSB) of the frequency axis resource allocation information in the DCI, RA type <NUM> is indicated to be used, and in the case of <NUM>, RA type <NUM> is indicated to be used.

<FIG> is a diagram illustrating an example of time axis resource allocation in the NR system. Referring to <FIG>, a base station may indicate a time axis position of a PDSCH resource according to µPDSCH and µPDCCH which are subcarrier spacings of a control channel (physical downlink control channel, PDCCH) and a data channel (physical downlink shared channel, PDSCH) that are configured via a higher layer, a scheduling offset (K<NUM>) value, and an OFDM symbol starting position <NUM> and a length <NUM> within one slot (slot <MAT>, <NUM>) dynamically indicated via DCI.

<FIG> is a diagram illustrating an example of time axis resource allocation according to subcarrier spacings of a control channel and a data channel. Referring to <FIG>, if subcarrier spacings of a data channel and a control channel are the same (<NUM>, µPDSCH=µPDCCH), each slot number of the data channel and control channel is the same, so that a base station and a UE may check a scheduling offset on the basis of a predetermined slot offset of K<NUM>. On the other hand, if the subcarrier spacings of the data channel and the control channel are different (<NUM>, µPDSCH≠µPDCCH), each slot number of the data channel and the control channel is different, so that the base station and the UE may check a scheduling offset on the basis of the predetermined slot offset of K<NUM> according to the subcarrier spacing of the data channel.

The NR system provides various types of DCI formats as shown in Table <NUM> below according to the purpose, for efficient control channel reception by the UE.

For example, the base station may use DCI format 1_0 or DCI format 1_1 to allocate (schedule) PDSCH to one cell.

DCI format 1_0 includes at least the following information when transmitted with a CRC scrambled with a new RNTI, a configured scheduling RNTI (CS-RNTI), or a cell radio network temporary identifier (C-RNTI):.

DCI format 1_1 includes at least the following information when transmitted with a CRC scrambled with a new-RNTI, a CS-RNTI, or a C-RNTI:.

The maximum number of DCI of different sizes, which the UE can receive per slot in a corresponding cell, is <NUM>, and the maximum number of DCI of different sizes scrambled with a C-RNTI, which the UE can receive per slot in the cell, is <NUM>.

Referring to the DCI structure, in release <NUM>, NR DCI formats 1_0 and 1_1 are focused on allocating PDSCH transmitted at a single transmission point, and additional standard support is required in the case of coordinated transmission in which a single UE receives PDSCH transmitted at multiple points. For example, the control information includes information related to HARQ, such as frequency axis and time axis resource allocation information, antenna allocation information, MCS, etc., each of which corresponds to one PDSCH, and therefore a method of extending the information is required to allocate two or more PDSCHs.

In the disclosure, a DCI design method for efficiently allocating the multiple PDSCHs to one UE and a method for the UE to check the effectiveness of receiving multiple pieces of DCI may be provided to improve the efficiency of coordinated transmission.

Hereinafter, in the disclosure, higher layer signaling is a signal transferring method, in which a signal is transferred from a base station to a UE by using a downlink data channel of a physical layer or a signal is transferred from a UE to a base station by using an uplink data channel of a physical layer, wherein the higher layer signaling may be referred to as RRC signaling, packet data convergence protocol (PDCP) signaling, or a medium access control (MAC) control element (CE) (MAC CE). The configuration via a higher layer may be understood as the configuration based on information transferred using the higher layer signaling. PDCCH transmission/reception or control channel transmission/reception may be understood as DCI transmission/reception via PDCCH, and likewise, PDSCH transmission/reception or data channel transmission/reception may be understood as transmission/reception of DL data via PDSCH. This technique may also be applied to an uplink channel.

Hereinafter, in the disclosure, the examples are described via a plurality of embodiments. However, these are not independent, and one or more embodiments may be applied simultaneously or in combination.

Unlike the conventional system, the <NUM> wireless communication system can support not only a service requiring a high transmission rate, but also a service having a very short transmission delay and a service requiring a high connection density. In a wireless communication network including multiple cells, transmission and reception points (TRPs), or beams, coordinated transmission between respective cells, TRPs, or/and beams is one of element techniques capable of satisfying various service requirements by increasing the intensity of a signal received by a UE or efficiently performing TRP or/and inter-beam interference control.

Joint transmission (JT) is a representative transmission technology for the coordinated transmission, and the technology enables enhancement of the intensity of a signal received by a UE, by supporting one UE via different cells, TRPs, and/or beams. Characteristics of each cell, TRP, or/and beam-to-UE channel may differ greatly, and therefore different precoding, MCS, resource allocation, etc. need to be applied to each cell, TRP, or/and beam-to-UE link.

In particular, in the case of non-coherent joint transmission (NC-JT) supporting non-coherent precoding between each cell, TRP, or/and beam, an individual DL transmission information configuration for the each cell, TRP, or/and beam becomes important. However, the individual DL transmission information configuration for the each cell, TRP, or/and beam becomes a major factor in increasing a payload required for DL DCI transmission, and this may adversely affect reception performance of PDCCH transmitting DCI. Therefore, it is necessary to carefully design a tradeoff between the amount of DCI information and the PDCCH reception performance, for JT support.

<FIG> is a diagram illustrating each joint transmission scheme. Reference numeral <NUM> is a diagram illustrating coherent joint transmission (C-JT) supporting coherent precoding between each cell, TRP, or/and beam. In the C-JT, TRP A <NUM> and TRP B <NUM> transmit the same data (PDSCH), and joint precoding is performed in multiple TRPs. This indicates that TRP A <NUM> and TRP B <NUM> transmit data by using the same DMRS ports (e.g., DMRS ports A and B in both TRPs) for reception of the same PDSCH. In this case, a UE <NUM> will receive one piece of DCI information for reception of one PDSCH demodulated by DMRS ports A and B.

Reference numeral <NUM> is a diagram illustrating non-coherent joint transmission supporting non-coherent precoding between each cell, TRP, or/and beam. In the case of the NC-JT, different PDSCHs are transmitted in each cell, TRP, or/and beam, and individual precoding may be applied to each PDSCH. This indicates that TRP A <NUM> and TRP B <NUM> transmit data by using different DMRS ports (e.g., DMRS port A in TRP A and DMRS port B in TRP B) for reception of the different PDSCHs. In this case, a UE <NUM> will receive two types of DCI information for reception of PDSCH A demodulated by DMRS port A and PDSCH B demodulated by DMRS port B.

<FIG> is a diagram illustrating an example of radio resource allocation according to a situation in the case of joint transmission. For example, in the case of the NC-JT, according to <FIG>, various radio resource allocations can be considered, wherein the various radio resource allocations includes a case <NUM> where frequency and time resources used by multiple TRPs are the same, a case <NUM> where the frequency and time resources used by multiple TRPs do not overlap at all, and a case <NUM> where some of the frequency and time resources used by multiple TRPs overlap. In particular, in the case as reference numeral <NUM>, it may be seen that a DCI payload required for resource allocation information increases linearly according to the number of TRPs. Such an increase in a DL DCI payload may adversely affect reception performance of PDCCH transmitting DCI or may significantly increase complexity of DCI blind decoding of the UE. Therefore, the disclosure provides a DCI design method for efficiently supporting NC-JT.

<FIG> is a diagram illustrating four examples of a DCI design for NC-JT support.

In <FIG>, case #<NUM><NUM> is a case in which, in a situation where (N-<NUM>) different PDSCHs are transmitted in (N-<NUM>) additional TRPs (TRP#<NUM> to TRP#(N-<NUM>)) other than a serving TRP (TRP#<NUM>) used at single PDSCH transmission, control information for the PDSCH transmitted in the additional TRPs is transmitted in the form (the same DCI format) as that of control information for the PDSCH transmitted in the serving TRP. That is, a UE acquires control information on PDSCHs transmitted in different TRPs (coordinated TRPs, TRP#<NUM> to TRP#(N-<NUM>)) via all DCI (DCI#<NUM> to DCI#(N-<NUM>)) having the same DCI format and the same payload. Case #<NUM><NUM> has an advantage that the degree of freedom (i.e., the degree of freedom in PDSCH allocation such as resource allocation) to control each PDSCH is fully guaranteed, but if each piece of DCI is transmitted in a different TRP, there is a disadvantage that a difference in coverage for each piece of DCI occurs and therefore the reception performance may be deteriorated. That is, when the DCI is transmitted in a TRP other than the serving TPR, there may be a disadvantage that the PDCCH reception performance may be deteriorated.

Case #<NUM><NUM> is a case in which, in a situation where (N-<NUM>) different PDSCHs are transmitted in (N-<NUM>) additional TRPs (TRP#<NUM> to TRP#(N-<NUM>)) other than a serving TRP (TRP#<NUM>) used at single PDSCH transmission, control information for the PDSCH transmitted in the additional TRPs is transmitted via different DCI (payload) or in a format (different DCI format) different from that that of control information for the PDSCH transmitted in the serving TRP.

For example, in a case of DCI#<NUM> for transmission of control information for PDSCH transmitted in the serving TRP (TRP#<NUM>), all information elements of DCI format 1_0 to DCI format 1_1 are included. However, in a case of "shortened" DCI (sDCI#<NUM> to sDCI#(N-<NUM>)) for transmission of control information for PDSCHs transmitted in coordinated TRPs (TRP#<NUM> to TRP#(N-<NUM>)), only a part of information elements of DCI format 1_0 to DCI format 1_1 may be included. Therefore, in a case of sDCI for transmission of the control information for PDSCHs transmitted in the coordinated TRPs, it may be possible that the sDCI has a smaller payload compared to normal DCI (nDCI) for transmission of the control information related to PDSCH transmitted in the serving TRP, or includes as many reserved bits as the number of bits fewer than that of nDCI. Case #<NUM> has a disadvantage that the degree of freedom for controlling (allocation) of each PDSCH may be restricted depending on the contents of information elements included in the sDCI. However, since the reception performance of sDCI becomes superior to that of nDCI, there is an advantage that a probability of occurrence of a coverage difference per DCI decreases. That is, even if sDCI is transmitted in the coordinated TRPs, the reception performance of sDCI becomes excellent, so that the coverage may not differ from that of nDCI.

Case #<NUM><NUM> is a case in which, in a situation where (N-<NUM>) different PDSCHs are transmitted in (N-<NUM>) additional TRPs (TRP#<NUM> to TRP#(N-<NUM>)) other than a serving TRP (TRP#<NUM>) used at single PDSCH transmission, control information for the PDSCH transmitted in the additional TRPs is transmitted via different DCI (payload) or in a format (different DCI format) different from that that of control information for the PDSCH transmitted in the serving TRP. For example, in the case of DCI#<NUM> for transmission of the control information for PDSCH transmitted in the serving TRP (TRP#<NUM>), all information elements of DCI format 1_0 to DCI format 1_1 are included. Further, in the case of the control information for PDSCHs transmitted in the coordinated TRPs (TRP#<NUM> to TRP#(N-<NUM>)), it may be possible to collect only some of information elements of DCI format 1_0 to DCI format 1_1 in "secondary" DCI (hereinafter, sDCI) so as to transmit the same.

For example, the sDCI may include at least one piece of information in HARQ related information, such as frequency axis resource allocation, time axis resource allocation, and MCS of coordinated TRPs. In addition, in the case of information that is not included in sDCI, such as a BWP indicator or a carrier indicator, it is possible for the UE to follow the information of nDCI (DCI#<NUM>) of the serving TRP. Case #<NUM><NUM> has a disadvantage that the degree of freedom for controlling (allocation) of each PDSCH may be restricted depending on the contents of the information element included in sDCI. However, there is an advantage that the reception performance of sDCI can be adjusted, and the complexity of DCI blind decoding of the UE is reduced compared to case #<NUM> or #<NUM>.

Case #<NUM><NUM> is a case where, in a situation where (N-<NUM>) additional TRPs (TRP#<NUM> to TRP#(N-<NUM>)) other than the serving TRP (TRP#<NUM>) used at single PDSCH transmission are transmitted in (N-<NUM>) different PDSCHs, the control information for the PDSCH transmitted in the additional TRPs and the control information for PDSCH transmitted in the serving TRP are transmitted via the same DCI (long DCI or lDCI). That is, the UE acquires the control information for PDSCHs transmitted in different TRPs (TRP#<NUM> to TRP#(N-<NUM>)) via a single piece of DCI. Case #<NUM><NUM> has an advantage that a DCI blind decoding complexity of the UE does not increase, but has a disadvantage that the degree of freedom for PDSCH controlling (allocation) is low, for example, the number of coordinated TRPs is restricted according to long DCI payload restriction.

In the following descriptions and embodiments, sDCI may refer to various auxiliary DCI, such as shortened DCI, secondary DCI, normal DCI (DCI formats 1_0 to 1_1 described above) including PDSCH control information transmitted in the coordinated TRP, or long DCI, and the descriptions may be applied to the various auxiliary DCI if no special restriction is specified.

The following descriptions and embodiments provide a method for a detailed configuration of sDCI for cases #<NUM>, #<NUM>, and #<NUM> and methods of determining validity (validation, which may be interchangeably used with authentication, verification, etc.) when the UE receives sDCI.

In embodiments, "coordinated TRP" may be replaced with various terms, such as "coordinated panel" or "coordinated beam" when actually applied. In embodiments, "a case where NC-JT is applied" can be interpreted in various ways according to a situation, but one expression is used for the convenience of explanation, wherein the case may be interpreted as "a case where the UE receives PDSCH on the basis of two or more TCI indications simultaneously in one Bandwidth part (that is, it may be understood as a case where the UE simultaneously receives downlink data corresponding to each of two or more TCIs indicated via one or more pieces of DCI in one BWP)", "a case where PDSCH received by the UE is associated with one or more DMRS port groups (that is, when one PDSCH allocated by one piece of DCI is associated with multiple DMRS port groups, different QCL signaling or a different TCI indication may be applied to each of the DMRS port groups)", and the like.

In the embodiment, detailed configuration methods of sDCI according to cases #<NUM><NUM>, #<NUM><NUM>, and #<NUM><NUM> of the first embodiment will be described.

In Case #<NUM>, as described in the first embodiment, the control information for PDSCH transmitted in both the serving TRP and the coordinated TRP can be transmitted via the same DCI format, for example, DCI format 1_1. The UE can assume that the some restrictions are applied to control information of an additional PDSCH other than the PDSCH transmitted in the serving TRP.

The control information of the PDSCH transmitted in the serving TRP may be referred to as various expressions and is referred to as nDCI for the convenience in this description, wherein the various expressions includes "first DCI for data allocation to a corresponding PDSCH transmission time point", "first detected DCI in DCI for data allocation to a the PDSCH transmission time point", "DCI transmitted in a position of a PDCCH candidate group of a lowest index, a (UE-specific) search space of a lowest (or highest) ID, or a (UE-specific) CORESET of a lowest (or highest) ID, in the DCI for data allocation to the PDSCH transmission time point".

The control information of the additional PDSCH may be referred to as various expressions, and is referred to as sDCI for the convenience in this description, wherein the various expressions includes "second or subsequent DCI for data allocation to a corresponding PDSCH transmission point", "DCI detected after the second DCI in the DCI for data allocation to the PDSCH transmission point", or "DCI transmitted outside a search space or CORESET of a lowest ID (excluding a common CORESET) in the DCI for data allocation to the PDSCH transmission point". In the following embodiments, nDCI and sDCI for allocation of PDSCH transmitted in at least one same OFDM symbol to the UE are referred to as associated DCI (associated nDCI and sDCI).

In case #<NUM>, the UE may assume at least one of the following restrictions upon reception of sDCI for NC-JT:.

In case #<NUM>, as described in the first embodiment, the control information sDCI for PDSCH transmitted in the coordinated TRPs can be transmitted in an abbreviated form compared to nDCI. For example, sDCI can be transmitted via the same type DCI format as that of nDCI, for example, DCI format 1_1, but may include only a part of nDCI information. The UE can apply the same value as that transmitted in nDCI, to information, which is not included in sDCI, in information required for reception of an additional PDSCH transmitted in the coordinated TRPs. For detailed descriptions of the nDCI and sDCI, refer to the description in case #<NUM>.

In case #<NUM>, it may be assumed that the UE receives at least one piece of the following information when receiving sDCI for NC-JT:.

In case #<NUM>, as described in the first embodiment, control information for multiple PDSCHs transmitted in multiple coordinated TRPs may be aggregated in one piece of sDCI so as to be transmitted. For example, sDCI may include pairs (or a set including a part of multiple information) of some information of nDCI information in a DCI format separate from nDCI, and each pair refers to a part of the control information for PDSCH transmitted in each coordinated TRP. The UE can apply the same value as that transmitted in nDCI, to information, which is not included in sDCI, in information required for reception of an additional PDSCH transmitted in the coordinated TRPs. For detailed descriptions of the nDCI and sDCI, refer to the description in case #<NUM>.

In case #<NUM>, if one serving TRP and (N-<NUM>) coordinated TRPs separately transmit PDSCH for NC-JT, it may be assumed that the UE receives at least one piece of the following information upon reception of sDCI:.

In the following embodiments, methods for determining sDCI reception validity by the UE are provided. The following embodiments are not limited to one of cases #<NUM>, #<NUM>, or #<NUM>, and can be commonly applied by similar methods.

The embodiment provides a first sDCI validation method for a case in which a CRC of sDCI received by the UE is scrambled with a CS-RNTI.

When NC-JT via sDCI is supported, a false alarm or miss detection for sDCI reception causes the UE to assume erroneous interference, causes loss of data transmitted in the coordinated TRPs, and therefore may adversely affect network throughput. Therefore, it is important to provide a device that allows the UE to determine the validity of sDCI reception (sDCI validation).

Procedures of determining the validity of sDCI reception mainly include two procedures of: <NUM>) determining an sDCI validity determination initiation condition (or a starting condition); and <NUM>) performing the sDCI validity determination.

If the CRC of sDCI is scrambled with CS-RNTI, it is possible to use one of the following two methods as a condition for initiating sDCI validity determination:.

<FIG> is a diagram illustrating a UE operation of performing sDCI validity determination according to an NDI field value of sDCI if a CRC of sDCI is scrambled with a CS-RNTI. Referring to <FIG>, a UE receives DCI (hereinafter, DL grant DCI with C-RNTI) for scheduling (for DL grant) PDSCH scrambled with C-RNTI so as to obtain allocation information for a first PDSCH, in <NUM>. Thereafter, the UE attempts, in <NUM>, to detect DCI (hereinafter, DL grant DCI with CS-RNTI) for scheduling (for DL grant) PDSCH scrambled with CS-RNTI, receives, in <NUM>, a single PDSCH allocated by the DL grant DCI with C-RNTI if the detection fails, and checks, in <NUM>, an NDI field value in the detected DL grant DCI with CS-RNTI if the detection is successful.

If the checked NDI field value is <NUM>, the UE determines the DL grant DCI with CS-RNTI as DCI for DL SPS retransmission and receives a single PDSCH allocated according thereto, in <NUM>. If the checked NDI field value is <NUM>, the UE starts to determine UE validity for the "DL grant DCI with CS-RNTI", in <NUM>. That is, if DCI is scrambled with CS-RNTI and the value of the NDI field is <NUM>, it may be acknowledge that the validity determination initiation condition is satisfied.

If some information in the DL grant DCI with CS-RNTI satisfies conditions in Table <NUM> or Table <NUM>, the UE confirms, in <NUM>, that the DL grant DCI with CS-RNTI is DCI for activation/release of DL SPS or UL grant type <NUM>. On the other hand, if some information in the DL grant DCI with CS-RNTI satisfies the condition in Table <NUM>, the UE confirms that the DL grant DCI with CS-RNTI is sDCI for NC-JT, and receives multiple PDSCHs according to the sDCI, in <NUM>. If all of the above validity determinations fail (if validation is not achieved), the UE determines that the sDCI is detected with a non-matching CRC (that is, the sDCI is disregarded).

Table <NUM> above is an example for description of the embodiment, and when actually applied, the contents of Table <NUM> do not overlap with the validity determination for activation and release of DL SPS or UL grant type <NUM>, and it is obvious that the contents of Table <NUM> can be appropriately replaced with other padding values or other information that can be omitted from sDCI. In the specification, in order not to obscure the gist of the disclosure, listing all information combinations and padding values that can be used for sDCI validity determination, other than those in Table <NUM>, is omitted.

<FIG> is a diagram illustrating a UE operation of performing sDCI validity determination according to a time axis resource allocation value of sDCI if a CRC of sDCI is scrambled with a CS-RNTI. Referring to <FIG>, a UE receives a DL grant DCI with C-RNTI and obtains allocation information for a first PDSCH, in <NUM>. Thereafter, the UE attempts to detect, in <NUM>, the DL grant DCI with CS-RNTI, and if the detection fails, the UE receives, in <NUM>, a single PDSCH allocated by the DL grant DCI with C-RNTI. If the UE succeeds in the detection, the UE checks a time axis resource allocation value in the detected DL grant DCI with CS-RNTI, and determines, in <NUM>, whether a condition for starting sDCI validity determination is satisfied.

For the condition of starting sDCI validity determination, one of the following examples can be used. <NUM>) If a time axis resource allocation of sDCI and a time axis resource allocation of nDCI indicate at least one identical OFDM symbol, and <NUM>) If OFDM symbol positions indicated by both the time axis resource allocation of sDCI and the time axis resource allocation of nDCI match. If the time axis resource allocation in the DL grant DCI with CS-RNTI does not satisfy the above condition, the UE determines that there is no valid sDCI and receives a single PDSCH allocated by nDCI in <NUM>.

If the time axis resource allocation in the DL grant DCI with CS-RNTI satisfies the condition, the UE determines, in <NUM>, whether other information in the DL grant DCI with CS-RNTI satisfies the defined validity determination condition. For example, if some information in the DL grant DCI with CS-RNTI satisfies conditions in Table <NUM>, the UE confirms that the DL grant DCI with CS-RNTI is sDCI for NC-JT and receives multiple PDSCHs in <NUM>. If the above validity determinations fail (if validation is not achieved), the UE determines that the sDCI is detected with a non-matching CRC (that is, the sDCI is disregarded).

Table <NUM> is an example for description of the embodiment, and when actually applied, it is obvious that the contents of Table <NUM> can be appropriately replaced with other padding values or other information that can be omitted from sDCI, for example, as shown in Table <NUM>. In the specification, in order not to obscure the gist of the disclosure, listing all information combinations and padding values that can be used for sDCI validity determination, other than those in Table <NUM>, is omitted. In particular, a method based on frequency axis resource allocation other than the described time axis resource allocation-based sDCI validity determination time condition (in this case, as an example, if the frequency axis resource allocations of nDCI and sDCI indicate at least one identical RB, or indicate identical RBs, the UE may perform validity determination for sDCI), a method based on both the time axis and frequency axis resource allocations, or the like can be applied in a manner similar to the above description.

The embodiment provides a method for sDCI validity determination for a case in which CRC of sDCI received by the UE is scrambled with C-RNTI.

If the CRC of sDCI for NC-JT is scrambled with C-RNTI, the UE may determine nDCI for allocation of a first PDSCH transmitted in the serving TRP, according to one of the following conditions. <NUM>) A case where DCI (hereinafter, DL grant DCI with C-RNTI) scrambled with multiple C-RNTIs allocating multiple PDSCHs to one OFDM symbol is detected, DCI detected in a PDCCH candidate position of a lowest index, an earliest (UE-specific) search space within a corresponding slot, a (UE-specific) search space of a lowest (or highest) search space ID, or CORESET (excluding common CORESET) of a lowest (or highest) CORESET ID, and <NUM>) a case where an indicator indicating serving TRP DCI, primary DCI, first DCI, or the like is included in DCI and designated as nDCI.

<FIG> is a diagram illustrating a procedure of PDSCH reception by a UE when a CRC of sDCI for NC-JT is scrambled with a C-RNTI and multiple pieces of DL grant DCI with C-RNTI allocating multiple PDSCHs to one OFDM symbol is detected. Referring to <FIG>, a UE attempts, in <NUM>, to detect DL grant DCI with C-RNTI, and determines, in <NUM>, whether the number of pieces of DL grant DCI with C-RNTI allocating PDSCH within one slot is more than <NUM>. If there is one piece of DL grant DCI with C-RNTI allocating PDSCH in one slot, the UE receives, in <NUM>, a single PDSCH allocated by corresponding DCI. On the other hand, if there is more than one piece of DL grant DCI with C-RNTI allocating PDSCH in one slot, the UE determines, in <NUM>, whether a condition for sDCI validity determination is satisfied. For example, if nDCI is determined according to the described nDCI determination criteria, the UE may determine starting of sDCI validity determination according to whether time axis resource allocation of sDCI (DL grant DCI with C-RNTI other than nDCI) indicates the same OFDM symbol (at least one) as that of time axis resource allocation of nDCI. If the sDCI validity determination start condition is not satisfied, the UE receives, in <NUM>, a single PDSCH allocated by nDCI.

On the other hand, if the sDCI validity determination start condition is satisfied, the UE determines, in <NUM>, whether other information in corresponding "DL grant DCI with C-RNTI" satisfies the defined validity determination condition. For example, if some information in the DL grant DCI with C-RNTI other than nDCI satisfies the conditions in Table <NUM>, the UE confirms that the DL grant DCI with C-RNTI is sDCI for NC-JT and receives multiple PDSCHs in <NUM>. If the above validity determinations fail (if validation is not achieved), the UE determines that the sDCI is detected with a non-matching CRC (that is, the sDCI is disregarded).

Table <NUM> is an example for description of the embodiment, and when actually applied, it is obvious that the contents of Table <NUM> can be appropriately replaced with other padding values or other information that can be omitted from sDCI, for example, as shown in Table <NUM>. In the specification, in order not to obscure the gist of the disclosure, listing all information combinations and padding values that can be used for sDCI validity determination, other than those in Table <NUM>, is omitted. In particular, a method based on frequency axis resource allocation other than the described time axis resource allocation-based sDCI validity determination, a method based on both the time axis and frequency axis resource allocations, or the like can be applied in a manner similar to the above description.

The embodiment provides a method for sDCI validity determination for a case in which a CRC of sDCI received by the UE is scrambled with a new RNTI (hereinafter, newRNTI).

If the CRC of sDCI for NC-JT is scrambled with newRNTI, the UE may determine nDCI for allocation of a first PDSCH transmitted in the serving TRP, according to one of the following conditions. <NUM>) DL grant DCI with C-RNTI allocating an OFDM symbol to the same position as an OFDM symbol (at least one) allocated by sDCI, and <NUM>) a case where an indicator indicating the serving TRP DCI, primary DCI, first DCI, or the like is included in DCI and designated.

The newRNTI is an example of an RNTI name for sDCI scrambling, and may be referred to as various names, such as NCJT-RNTI, CoMP-RNTI, and multiple (MP) PDSCH-RNTI, when actually applied.

<FIG> is a diagram illustrating a PDSCH reception operation of a UE when a CRC of sDCI for NC-JT is scrambled with newRNTI. Referring to <FIG>, a UE attempts, in <NUM>, to detect DL grant DCI with C-RNTI, and if the detection is successful, the UE attempts, in <NUM>, to detect DCI(hereinafter, DL grant DCI with newRNTI) for scheduling (for DL grant) of PDSCH scrambled with newRNTI. If DL grant DCI with newRNTI is not detected, the UE receives, in <NUM>, a single PDSCH allocated by the DL grant DCI with C-RNTI (or nDCI). If DL grant DCI with newRNTI is detected, the UE determines, in <NUM>, whether a condition for sDCI validity determination is satisfied. For example, if nDCI is determined according to the described nDCI determination criteria, the UE may determine starting of sDCI validity determination according to whether time axis resource allocation of sDCI (DL grant DCI with newRNTI) indicates the same OFDM symbol (at least one) as that of time axis resource allocation of nDCI. If the sDCI validity determination start condition is not satisfied, the UE receives, in <NUM>, a single PDSCH allocated by nDCI.

On the other hand, if the sDCI validity determination start condition is satisfied, the UE determines, in <NUM>, whether other information in the "DL grant DCI with newRNTI" satisfies the defined validity determination condition. For example, if some information in the DL grant DCI with newRNTI satisfies conditions in Table <NUM>, the UE confirms that the DL grant DCI with newRNTI is sDCI for NC-JT and receives multiple PDSCHs in <NUM>. If the above validity determinations fail (if validation is not achieved), the UE determines that the sDCI is detected with a non-matching CRC (that is, the sDCI is disregarded).

Table <NUM> is an example for description of the embodiment, and when actually applied, it is obvious that the contents of Table <NUM> can be appropriately replaced with other padding values or other information that can be omitted from sDCI, for example, as shown in Table <NUM>. In the specification, in order not to obscure the gist of the disclosure, listing all information combinations and padding values that can be used for sDCI validity determination, other than those in Table <NUM>, is omitted. In particular, a method based on frequency axis resource allocation other than the described time axis resource allocation-based sDCI validity determination, a method based on both the time domain(axis) and frequency axis resource allocations, or the like can be applied in a manner similar to the above description.

<FIG> is a block diagram illustrating a structure of a UE according to the disclosure.

Referring to <FIG>, the UE may include transceivers <NUM> and <NUM>, a memory, and a processing unit <NUM> including a processor. According to the embodiment described above, the transceivers <NUM> and <NUM> and the processing unit <NUM> of the UE may operate. However, the elements of the UE are not limited to the above examples. For example, the UE may include more or fewer elements compared to the above-described elements. In addition, the transceivers <NUM> and <NUM> and the processing unit <NUM> may be implemented in the form of a single chip.

The transceivers <NUM> and <NUM> may transmit a signal to or receive a signal from a base station. Here, the signal may include control information and data. To this end, the transceiver <NUM>, <NUM> may include an RF transmitter configured to perform up-conversion and amplification of a frequency of a transmitted signal, an RF receiver configured to perform low-noise amplification of a received signal and perform down-conversion of a frequency, and the like. However, this is merely an embodiment of the transceiver <NUM> and <NUM>, and elements of the transceiver <NUM> and <NUM> are not limited to the RF transmitter and the RF receiver. Further, the transceiver <NUM> and <NUM> may receive a signal via a radio channel, may output the signal to the processor <NUM>, and may transmit the signal output from the processor <NUM>, via the radio channel.

The processing unit <NUM> may store programs and data necessary for an operation of the UE. The processing unit <NUM> may store control information or data included in a signal obtained by the UE. The processing unit <NUM> may include a storage medium, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a memory including a combination of storage media.

The processing unit <NUM> may control a series of procedures so that the UE can operate according to the above-described embodiment. According to an embodiment, the processing unit <NUM> may receive multiple pieces of DCIs to concurrently receive multiple PDSCHs, and in particular, may control an element of the UE so as to perform a validity check on a part of DCI.

<FIG> is a block diagram illustrating a structure of a base station according to the disclosure.

Referring to <FIG>, the base station may include transceivers <NUM> and <NUM>, a memory, and a processing unit <NUM> including a processor. According to the above-described communication method of the base station, the transceivers <NUM> and <NUM> and the processing unit <NUM> of the base station may operate. However, elements of the base station are not limited to the above examples. For example, the base station may include more or fewer elements compared to the above-described elements. In addition, the transceivers <NUM> and <NUM> and the processing unit <NUM> may be implemented in the form of a single chip.

The transceivers <NUM> and <NUM> may transmit a signal to or receive a signal from a UE. Here, the signal may include control information and data. To this end, the transceiver <NUM>, <NUM> may include an RF transmitter configured to perform up-conversion and amplification of a frequency of a transmitted signal, an RF receiver configured to perform low-noise amplification of a received signal and perform down-conversion of a frequency, and the like. However, this is merely an embodiment of the transceiver <NUM> and <NUM>, and elements of the transceiver <NUM> and <NUM> are not limited to the RF transmitter and the RF receiver. Further, the transceiver <NUM> and <NUM> may receive a signal via a radio channel, may output the signal to the processor <NUM>, and may transmit the signal output from the processor <NUM>, via the radio channel.

The processing unit <NUM> may store programs and data necessary for an operation of the base station. The processing unit <NUM> may store control information or data included in a signal obtained by the base station. The processing unit <NUM> may include a storage medium, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a memory including a combination of storage media.

The processing unit <NUM> may control a series of procedures so that the base station can operate according to the above-described embodiment. According to the disclosure, the processing unit <NUM> may generate DCI including at least one of nDCI or sDCI in order to configure data transmission using multiple TRPs to a UE, may transmit the generated DCI to the UE by using the transceivers <NUM> and <NUM>, and may control each element of the base station to transmit PDSCH to the UE by using multiple TRPs.

The embodiments of the disclosure described and shown in the specification and the drawings have been presented to easily explain the technical contents of the disclosure and help understanding of the disclosure, and are not intended to limit the scope of the disclosure. That is, it will be apparent to those skilled in the art that other modifications and changes may be made thereto on the basis of the technical idea of the disclosure. Further, the above respective embodiments may be employed in combination, as necessary. For example, embodiments <NUM> to <NUM> of the disclosure may be partially combined to operate a base station and a terminal. In addition, embodiments <NUM>, <NUM>-<NUM> of the disclosure are not covered by the claimed invention, but facilitate understanding of the invention.

Claim 1:
A method performed by a terminal in a wireless communication system, the method comprising:
receiving, from a base station, configuration information on identifiers on control resource sets, CORESETs;
receiving, from the base station, first downlink control information, DCI, for scheduling of a first physical downlink shared channel, PDSCH, wherein the first DCI is associated with a first identifier of a CORESET, and the CORESET of the first identifier is for a first transmission and reception point, TRP;
receiving, from the base station, second DCI for scheduling of a second PDSCH, wherein the second DCI is associated with a second identifier of the CORESET, and the CORESET of the second identifier is for a second TRP;
identifying whether a first bandwidth part, BWP indicator included in the first DCI and a second BWP indicator included in the second DCI indicate the same value or not; and
receiving, from the base station, the first PDSCH and the second PDSCH, in case that the first BWP indicator and the second BWP indicator indicate the same value.