Method and apparatus for downlink control information interpretation in wireless communication system

By introducing multiple antenna port tables and PTRS-DMRS association fields in the DCI format, the problem of processing multiple mapping types of antenna port fields and PTRS association fields in the 5G mobile communication system is solved, and the efficiency of resource allocation and channel utilization is improved, and the efficiency of resource allocation and channel utilization is improved. System performance and reliability.

CN118985161APending Publication Date: 2024-11-19SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380032941.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-11-11
Filing Date
2023-04-07
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

In 5G mobile communication systems, it is difficult for the prior art to effectively interpret and process antenna port fields and PTRS association fields of multiple mapping types, resulting in inefficient channel scheduling and resource allocation.

Method used

By introducing multiple antenna port tables and PTRS-DMRS association fields in the DCI format, the terminal and base station can identify and process scheduling information of different mapping types, thereby optimizing the interpretation of the antenna port table and the association of PTRS, and improving the scheduling of PDSCH and PUSCH efficiency.

Benefits of technology

It realizes more efficient resource allocation and channel utilization in 5G mobile communication systems, and improves the performance and reliability of the system, especially in multi-PDSCH and multi-PUSCH scheduling scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118985161A_ABST
    Figure CN118985161A_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system supporting a higher data transmission rate. The present disclosure provides a method performed by a terminal in a wireless communication system. The method includes receiving a high layer signal including time domain resource allocation (TDRA) information from a base station; receiving downlink control information (DCI) including an antenna port field from the base station; and identifying an antenna port table of a first mapping type and an antenna port table of a second mapping type based on the antenna port field in a case where the DCI includes a plurality of pieces of scheduling information of different mapping types.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure generally relates to the operation of a terminal and a base station in a wireless communication system. More specifically, the present disclosure relates to a method for interpreting an antenna port field of a downlink control information (DCI) format by a terminal, an apparatus for performing the method, and a method for interpreting a phase tracking reference signal (PTRS) associated field of a DCI format by a terminal and an apparatus capable of performing the method. Background Art

[0002] The fifth generation (5G) mobile communication technology defines a wider frequency band, making high transmission rates and new services possible, and can be realized not only in the "below 6GHz" frequency band such as 3.5GHz, but also in the "above 6GHz" frequency band called millimeter wave (mmWave) including 28GHz and 39GHz. In addition, the implementation of the sixth generation (6G) mobile communication technology (called Beyond 5G system) in the terahertz (THz) frequency band (for example, the 95GHz to 3THz frequency band) is being considered to achieve a transmission rate 50 times faster than 5G mobile communication technology and an ultra-low latency of one-tenth of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support related services such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC) and massive machine type communication (mMTC) and meet performance requirements, standardization of beamforming and massive multiple-input multiple-output (MIMO) has been ongoing to reduce the radio wave path loss of mmWave and increase the radio wave transmission distance. In addition, parameter sets that support dynamic operations for efficient use of mmWave resources and time slot formats (for example, operating multiple subcarrier spacings), initial access technologies that support multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods (such as low-density parity check (LDPC) codes for large amounts of data transmission and polar codes for high-reliability transmission of control information), layer 2 (L2) preprocessing, and network slicing for providing dedicated networks for specific services are also used to support services and meet performance requirements.

[0004] Currently, improvements and performance enhancements to the initial 5G mobile communication technologies are being discussed for the services that they will support, and physical layer standardization has been carried out for the following technologies: vehicle-to-everything (V2X) technology for helping autonomous vehicles determine driving and improving user convenience based on information about the location and status of vehicles transmitted by vehicles; new radio unlicensed (NR-U) technology designed to make system operations comply with various relevant regulatory requirements for unlicensed frequency bands; new radio (NR) user equipment (UE) power saving technology; non-terrestrial network (NTN) technology, that is, UE directly communicates with satellites to provide coverage in areas where communication with terrestrial networks is impossible; and positioning technology.

[0005] In addition, the standardization of air interface architecture / protocols is also in progress, such as the Industrial Internet of Things (IIoT) that supports new services through interworking and integration with other industries, Integrated Access and Backhaul (IAB) that provides nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancement including conditional switching and dual-active protocol stack (DAPS) switching, and two-step random access for simplifying the random access process (e.g., two-step random access channel (RACH) for NR). Standardization of the following items has also been ongoing in terms of system architecture / services: 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software-defined network (SDN) technologies, and mobile edge computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, connected devices will be connected to communication networks, and therefore, it is expected that it will be necessary to enhance the functions and performance of 5G mobile communication systems and the integrated operations of connected devices. To this end, new research related to extended reality (XR) is planned to effectively support augmented reality (AR), virtual reality (VR), and mixed reality (MR). 5G performance improvement and complexity reduction can be achieved by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, virtual service support, and drone communication.

[0007] In addition, this development of 5G mobile communication systems will serve as the basis for the development of the following technologies: new waveforms for providing coverage in the terahertz band of 6G mobile communication technology; multi-antenna transmission technologies such as full-dimensional multiple-input multiple-output (FD-MIMO), array antennas, and massive antennas; metamaterial-based lenses and antennas for improving the coverage of terahertz band signals; high-dimensional spatial multiplexing technology using orbital angular momentum (OAM), and reconfigurable smart surface (RIS) technology; full-duplex technology for increasing the frequency efficiency of 6G mobile communication technology and improving system networks; AI-based communication technology that achieves system optimization by leveraging satellites and AI from the design stage and internalizing end-to-end AI support functions; and next-generation distributed computing technology that enables services with complexity that exceed the limits of UE operating capabilities by utilizing ultra-high performance communication and computing resources. Summary of the invention

[0008] Technical issues

[0009] The present disclosure provides an apparatus and method capable of effectively providing a service in a mobile communication system.

[0010] In addition, the present disclosure provides a method for interpreting an antenna port field of a DCI format and a device for performing the method.

[0011] Additionally, the present disclosure provides a method for interpreting a PTRS association field in a DCI format by a terminal and a device capable of executing the method.

[0012] Technical Solution

[0013] The present disclosure is directed to solving the above-mentioned problems and disadvantages and to providing at least the advantages described below.

[0014] According to one aspect of the present disclosure, a method performed by a terminal in a wireless communication system is provided. The method includes: receiving high-layer signaling including time domain resource allocation (TDRA) information from a base station, receiving DCI including an antenna port field from the base station, and identifying an antenna port table of a first mapping type and an antenna port table of a second mapping type based on the antenna port field when the DCI includes multiple scheduling information of different mapping types.

[0015] According to another aspect of the present disclosure, a method performed by a base station in a wireless communication system is provided. The method includes: sending a high-layer signal including TDRA information to a terminal, and sending a DCI including an antenna port field to the terminal, wherein, when the DCI includes multiple scheduling information of different mapping types, based on the antenna port field, an antenna port table of a first mapping type and an antenna port table of a second mapping type are identified.

[0016] According to another aspect of the present disclosure, a terminal in a wireless communication system is provided. The terminal includes a transceiver and a controller. The controller is configured to: receive a high-layer signal including TDRA information from a base station, receive a DCI including an antenna port field from the base station, and identify an antenna port table of a first mapping type and an antenna port table of a second mapping type based on the antenna port field when the DCI includes multiple scheduling information of different mapping types.

[0017] According to another aspect of the present disclosure, a base station in a wireless communication system is provided. The base station includes a transceiver and a controller. The controller is configured to: send a high-layer signal including TDRA information to a terminal, and send a DCI including an antenna port field to the terminal, wherein, in the case where the DCI includes multiple scheduling information of different mapping types, based on the antenna port field, an antenna port table of a first mapping type and an antenna port table of a second mapping type are identified.

[0018] Beneficial Effects

[0019] According to various embodiments of the present disclosure, an apparatus and method capable of effectively providing a service in a mobile communication system may be provided.

[0020] In addition, a method for interpreting an antenna port field of a DCI format by a terminal and an apparatus for performing the method may be provided.

[0021] In addition, a method for interpreting a PTRS association field of a DCI format by a terminal and a device capable of executing the method may be provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent through the following description in conjunction with the accompanying drawings, in which:

[0023] Figure 1 The basic structure of the time-frequency domain in the wireless communication system according to the embodiment is shown;

[0024] Figure 2 The structure of frames, subframes and time slots in a wireless communication system according to an embodiment is shown;

[0025] Figure 3 shows a configuration of a BWP in a wireless communication system according to an embodiment;

[0026] Figure 4 The configuration of a control resource set of a downlink control channel in a wireless communication system according to an embodiment is shown;

[0027] Figure 5The structure of a downlink control channel in a wireless communication system according to an embodiment is shown;

[0028] Figure 6 A method for transmitting and receiving data by a base station and a terminal by considering a downlink data channel and a rate matching resource in a wireless communication system according to an embodiment is shown;

[0029] Figure 7 shows frequency-axis resource allocation of a physical downlink shared channel (PDSCH) in a wireless communication system according to an embodiment;

[0030] Figure 8 FIG. 1 shows time axis resource allocation of a PDSCH in a wireless communication system according to an embodiment;

[0031] Fig. 9 1. illustrating time axis resource allocation according to subcarrier spacing of a data channel and a control channel according to an embodiment;

[0032] Fig.10 The wireless protocol structures of a base station and a terminal in a single cell case, a carrier aggregation case, and a dual connectivity case in a wireless communication system according to an embodiment are shown;

[0033] Fig.11 A PDSCH scheduling scheme according to an embodiment is shown;

[0034] Fig.12 shows DCI for single PDSCH scheduling and multi-PDSCH scheduling according to an embodiment;

[0035] Fig.13 shows a hybrid automatic repeat request (HARQ) acknowledgement (ACK) transmission of one or more PDSCHs scheduled by a DCI when the DCI indicates multiple PDSCH scheduling according to an embodiment;

[0036] Fig.14 The structure of a terminal in a wireless communication system according to an embodiment is shown;

[0037] Fig.15 A structure of a base station in a wireless communication system according to an embodiment is shown. DETAILED DESCRIPTION

[0038] Various embodiments of the present disclosure are described with reference to the accompanying drawings. However, the various embodiments of the present disclosure are not limited to specific embodiments, and it should be understood that modifications, equivalents and / or alternatives to the embodiments described herein may be varied. With respect to the description of the accompanying drawings, similar components may be marked with similar reference numerals.

[0039] Various embodiments of the present disclosure provide a method for interpreting an antenna port field by a terminal configured with multiple PDSCH scheduling and multiple physical uplink shared channel (PUSCH) scheduling in a wireless communication system.

[0040] According to the multi-PDSCH scheduling and multi-PUSCH scheduling configuration, the terminal can receive multiple pieces of scheduling information configured in one TDRA line, and each of the multiple pieces of scheduling information may include a start and length indication value (SLIV) and a mapping type. Therefore, the terminal can be configured to receive an indication of a TDRA line through one DCI, and the TDRA line includes multiple pieces of scheduling information with different mapping types.

[0041] Different pieces of DMRS configuration information may be configured for different mapping types. In the case where the DMRS configuration information is different, different antenna port tables for DMRS port indication may be configured. The DCI format for scheduling PDSCH as PUSCH may include an antenna port field for indicating a row in the antenna port table.

[0042] In case that a TDRA row including multiple pieces of scheduling information having different mapping types is indicated through one DCI, the one DCI should indicate one row in multiple tables. The present disclosure provides a method for designing and interpreting an antenna port field included in a DCI format so as to indicate each row of multiple antenna ports.

[0043] Different pieces of DMRS configuration information may be configured for different mapping types. In the case where the DMRS configuration information is different, different antenna port tables indicated by the DMRS information may be configured. Therefore, different DMRS ports may be allocated based on different mapping types.

[0044] In case that an indication of a TDRA row including a plurality of pieces of scheduling information having different mapping types is received through one DCI, the PTRS-DMRS association field may indicate DMRS ports of two mapping types. To this end, the present disclosure provides various methods for indicating the PTRS-DMRS association field.

[0045] When describing the embodiments of the present disclosure, descriptions related to technical contents that are well known in the art and not directly related to the present disclosure will be omitted. Omission of unnecessary descriptions is to prevent the main purpose of the present disclosure from being obscured.

[0046] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted or schematically shown. In addition, the size of each element does not fully reflect the actual size. In the accompanying drawings, the same or corresponding elements are represented by the same reference numerals.

[0047] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the methods for achieving these advantages and features will be clear. However, the present disclosure is not limited to the embodiments described below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose the present disclosure and inform those skilled in the art of the scope of the present disclosure, as defined by the scope of the appended claims. Throughout the specification, the same or similar reference numerals represent the same or similar elements. In addition, when describing the present disclosure, when it is determined that a detailed description of a known function or configuration may make the subject matter of the present disclosure unnecessary and unclear, a detailed description of the known functions or configurations incorporated into the present disclosure will be omitted. The terms to be described below are terms defined in view of the functions in the present disclosure and may vary according to the user, the user's intention or custom. Therefore, the definition of the terms should be made based on the content of the entire specification.

[0048] Here, it is understood that each block in the flowchart diagram and the combination of blocks in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a method for implementing the specified function in the flowchart block. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can instruct the computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-usable or computer-readable memory produce a product, which includes an instruction device that implements the specified function in the flowchart block. The computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the specified function in the flowchart block.

[0049] In addition, each block in the flowchart diagram may represent a module, a code segment or a partial code, including one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative embodiments, the functions marked in the block may not appear in order. For example, two blocks displayed in succession may actually be executed substantially simultaneously, or blocks may sometimes be executed in reverse order, depending on the functions involved.

[0050] As used in the embodiments of the present disclosure, the term "unit" refers to a software element or a hardware element that performs a predetermined function, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, the meaning of the term "unit" is not always limited to software or hardware. The term "unit" can be configured to be stored in an addressable storage medium, or it can be running one or more processors. Therefore, the term "unit" includes, for example, software elements, object-oriented software elements, class or task elements, processes, functions, attributes, processes, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by the term "unit" can be combined into a smaller number of elements or "units", or can be divided into a larger number of elements or "units". In addition, these elements and "units" can be used to reproduce one or more CPUs in a device or a secure multimedia card. In addition, a "unit" can include one or more processors.

[0051] Provided is a broadband wireless communication system that provides high-speed and high-quality packet data services using communication standards, including High Speed ​​Packet Access (HSPA) of the 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-Advanced (LTE-A), LTE-pro, High Speed ​​Packet Data (HRPD) of 3GPP two (3GPP2), Ultra Mobile Broadband (UMB), 802.16e of the Institute of Electrical and Electronics Engineers (IEEE), and typical voice-based services.

[0052] As a typical example of a broadband wireless communication system, the LTE system adopts an orthogonal frequency division multiplexing (OFDM) scheme in the downlink (DL) and a single carrier frequency division multiple access (SC-FDMA) scheme in the uplink (UL). UL represents a wireless link for transmitting data or control signals from a UE or mobile station (MS) to a base station (e.g., eNodeB), and DL represents a wireless link for transmitting data or control signals from a base station to a UE. The above-mentioned multiple access scheme can separate the data or control information of each user by allocating and operating time-frequency resources for transmitting the data or control information of each user to avoid mutual overlap, thereby establishing orthogonality.

[0053] Since the 5G communication system is a post-LTE communication system, it must freely reflect the various needs of users and service providers, and therefore must support services that meet various needs. The services considered in the 5G communication system include eMBB communication, mMTC, and URLLC.

[0054] eMBB is designed to provide data rates higher than those supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, eMBB must provide a DL peak data rate of 20 Gbps and a UL peak data rate of 10 Gbps for a single base station. In addition, the 5G communication system must provide the UE with an increased user-perceived data rate as well as a maximum data rate. In order to meet these requirements, the transmission / reception technology should be improved, including further enhanced multiple-input multiple-output (MIMO) transmission technology. In addition, the data rate required by the 5G communication system can be obtained using a frequency bandwidth of more than 20 MHz in the 3 to 6 GHz or 6 GHz or higher frequency bands, instead of using a transmission bandwidth of up to 20 MHz in the 2 GHz band used in LTE to transmit signals.

[0055] In addition, mMTC can be used to support application services such as the Internet of Things (IoT) in 5G communication systems. mMTC may need to support the connection of a large number of UEs in a cell, enhance the coverage of UEs, improve battery life, and reduce the cost of UEs in order to effectively provide IoT. Since IoT provides various sensors and various devices while providing communication functions, it is necessary to support a large number of UEs in a cell (for example, 1,000,000 UEs / kilometer (km) 2 )). In addition, compared with other services provided by 5G communication systems, UEs supporting mMTC may require wider coverage because the UE is likely to be located in a shadow area, such as a basement of a building, which is not within the cell coverage due to the nature of the service. UEs supporting mMTC must be inexpensive to configure and may require a long battery life, for example, 10 to 16 years, because it is difficult to frequently replace the UE's battery.

[0056] URLLC is a cellular-based mission-critical wireless communication service that can be used for remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, and emergency alerts. Therefore, URLLC must provide ultra-low latency and ultra-high reliability communications. For example, URLLC-enabled services must meet air interface latency of less than 0.5 milliseconds (ms) and also require 10 -5 Or a smaller packet error rate. Therefore, for services supporting URLLC, the 5G system must provide a shorter transmission time interval (TTI) than other services, and may also need to allocate a large amount of resources within the frequency band to ensure the reliability of the communication link.

[0057] The three 5G services (i.e., eMBB, URLLC, and mMTC) can be multiplexed and transmitted in a single system. In this case, different transmission / reception technologies and transmission / reception parameters can be used between services to meet the different requirements of each service. 5G is not limited to the above three services.

[0058] Now we will introduce an NR time-frequency resource.

[0059] Figure 1 The basic structure of the time-frequency domain according to the embodiment is shown, and the time-frequency domain is a radio resource domain for transmitting data or control channels in the 5G system.

[0060] refer to Figure 1 , the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time-frequency domain may be a resource element 101. The resource element 101 may be defined by one orthogonal frequency division multiplexing (OFDM) symbol 102 in the time domain and one subcarrier 103 in the frequency domain. In the frequency domain, (For example, 12) consecutive REs may configure one resource block (RB) 104. One subframe 110 may be configured by a plurality of OFDM symbols. For example, the length of the subframe 110 may be 1 ms.

[0061] Figure 2 Frame, subframe, and time slot structures in a wireless communication system according to an embodiment are shown.

[0062] refer to Figure 2 , shows an example of the structure of a frame 200, a subframe 201, and a time slot 202. One frame 200 may be defined as 10 ms. One subframe 201 may be defined as 1 ms, and thus one frame 200 may be configured by a total of 10 subframes 201. One time slot 202 or 203 may be defined as 14 OFDM symbols (i.e., the number of symbols of one time slot). ). A subframe 201 may include one or more time slots 202 and 203, and the number of time slots 202 and 203 in each subframe 201 is different according to the configured value μ 204 or 205 of the subcarrier spacing. Figure 2 , the case where the subcarrier spacing configuration value is μ=0 (indicated by reference numeral 204) and μ=1 (indicated by reference numeral 205) is shown. In the case where μ=0 (indicated by reference numeral 204), one subframe 201 may include one time slot 202, and in the case where μ=1 (indicated by reference numeral 205), one subframe 201 may include two time slots 203. That is, the number of time slots per subframe is The number of time slots per frame may vary depending on the subcarrier spacing configuration value μ and, therefore, Can be different. According to each subcarrier spacing configuration μ, it can be defined in the following Table 1 and

[0063] Table 1

[0064]

[0065] Next, the BWP configuration in the 5G communication system will be described in detail with reference to the accompanying drawings.

[0066] Figure 3 A configuration of a BWP in a wireless communication system according to an embodiment is shown.

[0067] refer to Figure 3 , the figure shows an example in which the UE bandwidth 300 is configured by two BWPs (ie, BWP#1 301 and BWP#2 302). The base station can configure one or more BWPs for the UE, and can configure multiple pieces of information shown in Table 2 below for each BWP.

[0068] Table 2

[0069]

[0070] The present disclosure is not limited to the above examples, and in addition to the configuration information, various parameters related to the BWP may be configured in the UE. Such information may be transmitted to the UE by the base station through high-layer signaling (e.g., radio resource control (RRC) signaling). At least one of the configured one or more BWPs may be activated. Whether to activate the configured BWP may be semi-statically transmitted from the base station to the UE through RRC signaling, or may be dynamically transmitted through DCI.

[0071] The UE before RRC connection can be configured with an initial BWP for initial access from the base station through a master information block (MIB). More specifically, the UE can receive configuration information about the search space and control resource set (CORESET), and in the initial access operation, through this configuration information, the PDCCH for receiving the system information required for initial access (which can correspond to the remaining system information (RMSI) or the system information block (SIB) 1) can be transmitted through the MIB. The CORESET and search space configured through the MIB can be regarded as identification (ID) 0, respectively. The base station can notify the UE of configuration information through the MIB, for example, frequency allocation information, time allocation information, and parameter set of CORESET#0. In addition, the base station can also notify the UE of configuration information about the monitoring period and timing of CORESET#0, that is, configuration information about search space#0, through the MIB. The UE can regard the frequency domain configured as CORESET#0 obtained from the MIB as the initial BWP for initial access. Here, the ID of the initial BWP can be regarded as zero.

[0072] The configuration of 5G-supported BWP can be used for various purposes.

[0073] The BWP configuration can be used to support the situation where the bandwidth supported by the UE is smaller than the system bandwidth. For example, the base station configures the frequency position of the BWP in the UE to enable the UE to send or receive data at a specific frequency position within the system bandwidth (configuration information 2).

[0074] In addition, the base station can also configure multiple BWPs in the UE to support different parameter sets. For example, in order to support sending data to / receiving data from a predetermined UE by using a subcarrier spacing of 15kHz and a subcarrier spacing of 30kHz, two BWPs can be configured, using a subcarrier spacing of 15kHz and a subcarrier spacing of 30kHz respectively. Different BWPs can be frequency-division multiplexed, and when trying to send or receive data at a specific subcarrier spacing, the BWP configured with the corresponding subcarrier spacing can be activated.

[0075] In addition, the base station can configure a BWP with different bandwidth sizes in the UE to reduce the power consumption of the UE. For example, when the UE supports a very large bandwidth (for example, a 100 MHz bandwidth) and always sends or receives data with the corresponding bandwidth, the transmission or reception may cause the UE's power consumption to be very high. In particular, when the UE performs monitoring of unnecessary DL control channels with a large bandwidth of 100 MHz when there is no business, the power consumption of the monitoring may be very inefficient. Therefore, in order to reduce the power consumption of the UE, the base station can configure a BWP with a relatively small bandwidth for the UE, for example, a BWP of 20 MHz. In the absence of business, the UE can perform monitoring operations on a BWP of 20 MHz. According to the instructions of the base station, the UE can send or receive data on a BWP of 100 MHz.

[0076] In the method for configuring BWP, before RRC connection, the UE may receive configuration information about the initial BWP through the MIB in the initial connection operation. More specifically, the UE may be configured with a CORESET for a DL control channel, and the DCI for scheduling SIBs may be transmitted from the MIB of the physical broadcast channel (PBCH) through the CORESET. The bandwidth of the CORESET configured through the MIB may be regarded as the initial BWP. The UE may receive the PDSCH through the configured initial BWP, and the SIB is transmitted through the PDSCH. The initial BWP may be used for other system information (OSI), paging and random access, and reception of SIBs.

[0077] BWP switching is described below.

[0078] When one or more BWPs have been configured for the UE, the base station can instruct the UE to change (switch or convert) the BWP by using the BWP indicator field in the DCI. Figure 3In the present invention, when the currently activated BWP of the UE is BWP#1 301, the base station may indicate BWP#2 302 to the UE by using the BWP indicator in the DCI, and the UE may perform BWP switching to BWP#2 302 indicated by the BWP indicator in the received DCI.

[0079] As described above, since the DCI-based BWP change can be indicated by the DCI that schedules PDSCH or PUSCH, when a request to switch BWP is received, the UE should smoothly receive or send the PDSCH or PUSCH scheduled by DCI in the switched BWP. To this end, the delay time (TBWP) requirement required when switching BWP can be determined, for example, it can be defined as shown in Table 3 below.

[0080] Table 3

[0081]

[0082] The requirement for BWP switching delay time to support type 1 or type 2 depends on the UE capability. The UE can report the supported BWP delay time type to the base station.

[0083] If the UE receives a DCI including a BWP switching indicator in time slot n according to the BWP switching delay time requirement, the UE may switch the BWP indicator to the same time slot no later than time slot n+T BWP The base station completes the switching to the new BWP indicated by the BWP switching indicator at the time of , and can perform transmission and reception related to the data channel scheduled by the corresponding DCI in the switched new BWP. When the base station intends to schedule the data channel to the new BWP, the base station can consider the BWP switching delay time (T BWP ) to determine the time domain resource allocation of the data channel. That is, when the base station schedules the data channel to the new BWP, the base station may schedule the corresponding data channel after the BWP switching delay time according to the method for determining the time domain resource allocation of the data channel. Therefore, the UE may not expect the DCI indicating the BWP switching to indicate that the time slot offset (K0 or K2) value is less than the BWP switching delay time (T BWP ).

[0084] If the UE has received a DCI indicating a BWP switch (e.g., DCI format 1_1 or 0_1), the UE may not perform transmission or reception during the time interval from the 3rd symbol of the time slot in which the PDCCH including the DCI is received to the start time of the time slot indicated by the time slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the DCI. For example, if the UE has received a DCI indicating a BWP switch in time slot n, and the time slot offset value indicated by the DCI is K, the UE may be configured not to perform transmission or reception from the 3rd symbol of time slot n to the symbol before time slot n+K (e.g., the last symbol of time slot n+K-1).

[0085] The synchronization signal (SS) / PBCH block will now be introduced.

[0086] SS / PBCH block refers to the physical layer channel block, which includes the primary SS (PSS), secondary SS (SSS) and PBCH. Specifically, the SS / PBCH block is as follows:

[0087] The PSS is a signal that serves as a DL time / frequency synchronization reference and provides some information of a cell ID.

[0088] The SSS is a signal used as a reference for DL ​​time / frequency synchronization and provides the remaining cell ID information not provided by the PSS. In addition, the SSS can also be used as a reference signal for demodulating the PBCH.

[0089] PBCH is a channel that provides basic system information required for the transmission or reception of data channels and control channels of UEs. The basic system information may include control information related to search spaces, which indicates radio resource mapping information of control channels, and scheduling control information of independent data channels used to transmit system information.

[0090] The SS / PBCH block includes a combination of PSS, SSS and PBCH. One or more SS / PBCH blocks can be transmitted within 5 milliseconds, and each transmitted SS / PBCH block can be distinguished by an index.

[0091] The UE can detect the PSS and SSS in the initial access operation and decode the PBCH. The UE can obtain the MIB from the PBCH and can configure CORESET#0 (which can correspond to the CORESET with a CORESET index of 0) from it. The UE can monitor CORESET#0 under the assumption that the DMRS transmitted in the selected SS / PBCH block is quasi-co-located (QCLed) with CORESET#0. The UE can receive system information based on the DCI sent from CORESET#0. The UE can obtain configuration information related to the RACH required for initial access from the received system information. The UE can send a physical RACH (PRACH) to the base station by considering the selected SS / PBCH index, and the base station that has received the PRACH can obtain information about the SS / PBCH block index selected by the UE. The base station can know which block the UE has selected in the SS / PBCH block, and can know that the CORESET#0 associated with it has been monitored.

[0092] Next, we will introduce DCI in the 5G system.

[0093] In the 5G system, scheduling information about UL data (PUSCH) or DL ​​data (PDSCH) is transmitted from the base station to the UE via DCI. For PUSCH or PDSCH, the UE can monitor the fallback DCI format and the non-fallback DCI format. The fallback DCI format may include fixed fields predefined between the base station and the UE, while the non-fallback DCI format may include configurable fields.

[0094] DCI can be transmitted over PDCCH, which is a physical DL control channel after channel coding and modulation. A cyclic redundancy check (CRC) can be attached to the DCI information payload, and the CRC can be scrambled by the radio network temporary identifier (RNTI) corresponding to the UE's identification information. Different RNTIs can be used according to the purpose of the DCI message, for example, UE-specific data transmission, power control commands, or random access responses. That is, the RNTI is not explicitly transmitted, but is included in the CRC calculation process before transmission. When receiving DCI information transmitted over PDCCH, the UE can check the CRC by using the assigned RNTI. When the CRC check result is correct, the UE can know that the corresponding message has been transmitted to the UE.

[0095] For example, the DCI for scheduling PDSCH for system information (SI) may be scrambled by SI-RNTI. The DCI for scheduling PDSCH for random access response (RAR) message may be scrambled by random access (RA)-RNTI. The DCI for scheduling PDSCH for paging information may be scrambled by paging RNTI (P-RNTI). The DCI for notifying the slot format indicator (SFI) may be scrambled by SFI-RNTI. The DCI for notifying transmit power control (TPC) may be scrambled by TPC-RNTI. The DCI for scheduling UE-specific PDSCH or PUSCH may be scrambled by cell RNTI (C-RNTI).

[0096] DCI format 0_0 may be used as a fallback DCI for scheduling a PUSCH. Here, the CRC may be scrambled by the C-RNTI. The DCI format 0_0 in which the CRC is scrambled by the C-RNTI may include, for example, a plurality of pieces of information included in the following Table 4.

[0097] Table 4

[0098]

[0099] DCI format 0_1 ​​may be used as a non-fallback DCI for scheduling a PUSCH. Here, the CRC may be scrambled by the C-RNTI. For example, the DCI format 0_1 ​​in which the CRC is scrambled by the C-RNTI may include multiple pieces of information included in the following Table 5.

[0100] Table 5

[0101]

[0102]

[0103] DCI format 1_0 may be used as a fallback DCI for scheduling PDSCH. Here, CRC may be scrambled by C-RNTI. For example, DCI format 1_0 in which CRC is scrambled by C-RNTI may include the following pieces of information in Table 6 below.

[0104] Table 6

[0105]

[0106] DCI format 1_1 may be used as a non-fallback DCI for scheduling a PDSCH. Here, the CRC may be scrambled by the C-RNTI. For example, the DCI format 1_1 in which the CRC is scrambled by the C-RNTI may include the information included in the following Table 7.

[0107] Table 7

[0108]

[0109]

[0110] The following will introduce the DL control channel in the 5G communication system in more detail with reference to the accompanying drawings.

[0111] Figure 4 A configuration of a CORESET of a DL control channel in a wireless communication system according to an embodiment is shown.

[0112] Figure 4 An example is shown where a UE BWP 410 is configured in the frequency domain and two CORESETs (CORESET #1 401 and CORESET #2 402) are configured in one time slot 420 in the time domain. CORESETs 401 and 402 may be configured in a specific frequency resource 403 within the entire UE BWP 410 in the frequency domain. A CORESET may be configured with one or more OFDM symbols in the time domain and this may be defined as a CORESET duration 404. Figure 4 , CORESET#1 401 may be configured with a CORESET duration of two symbols, and CORESET#2 402 may be configured with a CORESET duration of one symbol.

[0113] The base station can configure the CORESET in the above 5G for the UE through high-level signaling (e.g., system information, MIB, RRC signaling). The configuration of the CORESET for the UE can be understood as providing information such as the CORESET identifier, the frequency position of the CORESET, and the symbol length of the CORESET. For example, the configuration information may include multiple pieces of information included in Table 8 below.

[0114] Table 8

[0115]

[0116] In Table 8, the tci-StatesPDCCH (simply referred to as the transmission configuration indication (TCI) state) configuration information may include information of one or more SS / PBCH block (i.e., SSB) indices that have a quasi-co-sited (QCLed) relationship with the DMRS or channel state information reference signal (CSI-RS) index transmitted in the corresponding CORESET.

[0117] Figure 5 An example of configuring a basic unit of time and frequency resources for a DL control channel that can be used in 5G according to an embodiment is shown.

[0118] refer to Figure 5, the basic unit for configuring the time and frequency resources of the control channel may be referred to as a resource element group (REG) 503. The REG 503 may be defined by one OFDM symbol 501 in the time domain and one PRB 502 (ie, 12 subcarriers) in the frequency domain. The base station may connect the REG 503 to configure the DL control channel allocation unit.

[0119] like Figure 5 As shown in FIG. 1 , when the basic unit for allocating a DL control channel in 5G is called a control channel element (CCE) 504, one CCE 504 may include a plurality of REGs 503. Figure 5 As an example, REG 503 shown in FIG. 5A , REG 503 may include 12 resource elements (REs), and when one CCE 504 includes 6 REGs 503, one CCE 504 may include 72 REs. When a DL CORESET is configured, the corresponding area may include multiple CCEs 504. A specific DL control channel may be transmitted after being mapped to one or more CCEs 504 according to an aggregation level (AL) in the CORESET. The CCEs 504 in the CORESET are distinguished by numbers. Here, the numbers of the CCEs 504 may be allocated according to a logical mapping scheme.

[0120] Figure 5 The basic unit of the DL control channel shown in FIG. 5 , namely, REG 503, may include an RE to which DCI is mapped and an area to which DMRS 505 is mapped. DMRS 505 is a reference signal for decoding DCI. Figure 5 As shown, 3 DMRS 505 can be transmitted in one REG 503. Depending on the AL, the number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8 or 16. Different numbers of CCEs can be used to achieve link adaptation of the DL control channel. For example, if AL=L, one DL control channel can be transmitted via L CCEs. The UE needs to detect the signal without knowing the information about the DL control channel, and a search space representing a set of CCEs has been defined for blind decoding. The search space is a set of DL control channel candidates, which includes the CCEs that the UE must attempt to decode under a given AL. Since there are various ALs that constitute a bundle of 1, 2, 4, 8 or 16 CCEs, the UE may have multiple search spaces. A search space set can be defined as a search space set for all configured ALs.

[0121] The search space can be divided into a common search space and a UE-specific search space. A predetermined group of UEs or all UEs can check the common search space of the PDCCH in order to receive cell common control information, such as system information or dynamic scheduling of paging messages. For example, PDSCH scheduling allocation information for transmitting SIB (including cell operator information) can be received by checking the common search space of the PDCCH. In the case of a common search space, since a predetermined group of UEs or all UEs need to receive the PDCCH, the common search space can be defined as a set of previously specified CCEs. Scheduling allocation information about UE-specific PDSCH or PUSCH can be received by checking the UE-specific search space of the PDCCH. The UE-specific search space can be a function of the UE identity and various system parameters defined specifically for the UE.

[0122] In 5G, the base station can configure the parameters of the search space of the PDCCH for the UE through high-level signaling (e.g., SIB, MIB, or RRC signaling). For example, the base station can configure the number of PDCCH candidates for each aggregation level L, the monitoring period of the search space, the monitoring timing of the symbol unit in the time slot of the search space, the search space type (common search space or UE-specific search space), the combination of RNTI and DCI format to be monitored in the search space, and the CORESET index used to monitor the search space. For example, the configuration information of the search space of the PDCCH may include the following information included in Table 9 below.

[0123] Table 9

[0124]

[0125] The base station may configure one or more search space sets for the UE according to the configuration information. According to certain embodiments, the base station may configure search space set 1 and search space set 2 in the UE. The base station may configure search space set 1 in the UE to monitor DCI format A scrambled by X-RNTI in the common search space. The base station may configure search space set 2 in the UE to monitor DCI format B scrambled by Y-RNTI in the UE-specific search space.

[0126] According to the configuration information, one or more search space sets may exist in the common search space or the UE-specific search space. For example, search space set #1 and search space set #2 may be configured as common search spaces, and search space set #3 and search space set #4 may be configured as UE-specific search spaces.

[0127] In the common search space, the following combinations of DCI formats and RNTIs may be monitored. However, the present disclosure is not limited thereto.

[0128] -DCI format 0_0 / 1_0, CRC is scrambled by: C-RNTI, configured scheduling RNTI (CS-RNTI), semi-persistent RNTI (SP-CSI-RNTI), RA-RNTI, temporary cell RNTI (TC-RNTI), paging RNTI (P-RNTI), system information (SI-RNTI),

[0129] -DCI format 2_0, CRC scrambled by SFI-RNTI

[0130] -DCI format 2_1, CRC is scrambled by interrupt RNTI (INT-RNTI)

[0131] -DCI format 2_2, CRC is scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI

[0132] -DCI format 2_3, CRC scrambled by TPC-SRS-RNTI

[0133] In the UE-specific search space, the following combinations of DCI formats and RNTIs may be monitored. However, the present disclosure is not limited thereto.

[0134] -DCI format 0_0 / 1_0, CRC is scrambled by C-RNTI, CS-RNTI, TC-RNTI

[0135] -DCI format 1_0 / 1_1, CRC is scrambled by C-RNTI, CS-RNTI, TC-RNTI. The specified RNTI can follow the following definition and usage.

[0136] C-RNTI: used for UE-specific PDSCH scheduling

[0137] TC-RNTI: used for UE-specific PDSCH scheduling

[0138] CS-RNTI: UE-specific PDSCH scheduling for semi-static configuration

[0139] RA-RNTI: used for PDSCH scheduling in random access operation

[0140] P-RNTI: used to schedule PDSCH, through which PDSCH paging is transmitted

[0141] SI-RNTI: used for PDSCH scheduling, in which system information is transmitted

[0142] INT-RNTI: used to notify whether to puncture PDSCH

[0143] TPC-PUSCH-RNTI: used to indicate the power control command of PUSCH

[0144] TPC-PUCCH-RNTI: used to indicate the power control command of PUCCH

[0145] TPC-SRS-RNTI: used to indicate the power control command of SRS

[0146] The above specified DCI format may follow the definition shown in Table 10 below.

[0147] Table 10

[0148]

[0149] In 5G, the search space of aggregation level L in CORESET p and the search space set s can be expressed by Formula 1.

[0150]

[0151] -L: aggregation level

[0152] -n CI : Carrier index

[0153] -N CCE,p : The total number of CCEs present in CORESET p

[0154] - Time slot index

[0155] - Number of PDCCH candidates at aggregation level L

[0156] - PDCCH candidate group index for aggregation level L

[0157] -i=0,…,L- 1

[0158] For pmod3 = 0, A p =39827, for pmod3 = 1, A p =39829, for pmod3 = 2, A p =39839. D = 65537

[0159] -n RNTI : UE identifier

[0160] In the public search space, The value of may correspond to zero. In the case of a UE-specific search space, The value of may correspond to a value that varies according to the UE identity (C-RNTI or ID configured by the base station for the UE) and the time index.

[0161] In 5G, multiple search space sets may be configured with different parameters (e.g., the parameters shown in Table 9), and accordingly, the search space sets monitored by the UE at each time point may be different. For example, if search space set #1 is configured with an X time slot period, search space set #2 is configured with a Y time slot period, and X and Y are different, the UE may monitor both search space set #1 and search space set #2 in a specific time slot, and may also monitor one of search space set #1 and search space set #2 in a specific time slot.

[0162] The frequency resource allocation related to PDSCH will be introduced below.

[0163] Figure 6 A method for transmitting and receiving data by a base station and a terminal by considering a downlink data channel and a rate matching resource in a wireless communication system according to an embodiment is shown.

[0164] Figure 6 A downlink data channel 601 and a rate matching resource 602 are shown. The BS can configure one or more rate matching resources 602 in the UE through high-layer signaling (e.g., RRC signaling). The configuration information of the rate matching resource 602 may include time domain resource allocation information 603, frequency domain resource allocation information 604, and period information 605. If part or all of the time and frequency resources of the scheduled data channel 601 overlap with the configured rate matching resource 602, the BS can rate match the data channel 601 in the rate matching resource 602 portion and transmit. The UE can perform reception and decoding, assuming that the data channel 601 has been rate matched in the rate matching resource 602 portion.

[0165] The BS can dynamically inform the UE whether the data channel will be rate matched in the configured rate matching resource part through DCI through additional configuration. Specifically, the BS can select some of the configured rate matching resources, group the selected resources into rate matching resource groups, and use a bitmap method to indicate to the UE through DCI whether the data channel has been rate matched with each rate matching resource group. For example, if 4 rate matching resources RMR#1, RMR#2, RMR#3 and RMR#4 have been configured, the BS can configure RMG#1={RMR#1,RMR#2} and RMG#2={RMR#3,RMR#4} as rate matching groups, and can use 2 bits of the DCI field in the form of a bitmap to indicate to the UE whether each of RMG#1 and RMG#2 has performed rate matching. For example, if rate matching needs to be performed, the BS can indicate "1"; if rate matching does not need to be performed, the BS can indicate "0".

[0166] Figure 7 FIG. 4 shows frequency domain resource allocation of PDSCH in a wireless communication system according to an embodiment. More specifically, Figure 7 Three frequency domain resource allocation methods of type 0 7-00, type 1 7-05, and dynamic switching 7-10 that can be configured by high layers in the NR wireless communication system are shown.

[0167] refer to Figure 7 In the case where the UE is configured to use only resource type 0 through high-level signaling (indicated by reference numeral 7-00), some DCIs for allocating PDSCH to the corresponding UE include RBG The relevant conditions will be introduced later. In this case, N RBG Indicates the number of resource block groups (RBGs) determined according to the BWP size allocated by the BWP indicator and the high-level parameter rbg-Size, as shown in Table 11 below, and data is transmitted to the RBG represented as "1" in the bitmap.

[0168] Table 11

[0169] BWP size Configuration 1 Configuration 2 1-36 2 4 37-72 4 8 73-144 8 16 145-275 16 16

[0170] If the UE is configured to use only resource type 1 through high-level signaling (indicated by reference numeral 7-05), some DCI for allocating PDSCH to the UE includes The base station may configure the frequency domain resource allocation information of the starting VRB 7-20 and the length of the frequency domain resources 7-25 continuously allocated therefrom through the information.

[0171] If the UE is configured to use both resource type 0 and resource type 1 through high-level signaling (indicated by reference numeral 7-10), some DCI for allocating PDSCH to the UE includes frequency domain resource allocation information, which is configured by a bit with a larger value 7-35 among payloads 7-15 for configuring resource type 0 and payloads 7-20 and 7-25 for configuring resource type 1, and its conditions will be described later. Here, one bit is added to the most significant bit (MSB) of the frequency domain resource allocation information in the DCI, and if the value of the corresponding bit is "0", 0 indicates that resource type 0 is used, and if the value of the corresponding bit is "1", 1 indicates that resource type 1 is used.

[0172] The following describes a method for allocating time domain resources for a data channel in a next-generation mobile communication system (5G or NR system).

[0173] The base station can configure the time domain resource allocation information table for the DL data channel (PDSCH) and the UL data channel (PUSCH) for the UE through high-level signaling (e.g., RRC signaling). For PDSCH, a table including maxNrofDL-Allocations=16 entries can be configured, and for PUSCH, a table including maxNrofUL-Allocations=16 entries can be configured. In an embodiment, the time domain resource allocation information may include PDCCH to PDSCH time slot timing (corresponding to the time point of receiving the PDCCH and the time point of sending the PDSCH scheduled by the received PDCCH in time slots, represented by K0), PDCCH to PUSCH time slot timing (corresponding to the time point of receiving the PDCCH and the time point of sending the PUSCH scheduled by the received PDCCH in time slots, represented by K2), information about the position and length of the starting symbol of scheduling PDSCH or PUSCH in the time slot, and the mapping type of PDSCH or PUSCH. For example, the information included in the following Table 12 or Table 13 may be transmitted from the base station to the UE.

[0174] Table 12

[0175]

[0176] Table 13

[0177]

[0178] The base station may notify the UE of one of the entries representing the time domain resource allocation information in Tables 12-13 through L1 signaling (e.g., DCI) (e.g., it may be represented by the "time domain resource allocation" field in the DCI). The UE may acquire the time domain resource allocation information of the PDSCH or PUSCH based on the DCI received from the base station.

[0179] Figure 8 Time domain resource allocation of a PDSCH in a wireless communication system according to an embodiment is shown.

[0180] refer to Figure 8 The base station can indicate the time domain position of the PDSCH resource according to the starting position 8-00 and the length 8-05 of the OFDM symbol in the time slot, wherein the starting position 8-00 and the length 8-05 are SCS (μ PDSCH , μ PDCCH ) Dynamically indicated, the SCS of the data channel and control channel is configured using the higher layer, scheduling offset (K0) value and DCI.

[0181] Fig. 9 Time domain resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to an embodiment is shown.

[0182] refer to Fig. 9 , the data channel and the control channel have the same subcarrier spacing (indicated by reference numeral 9-00, μ PDSCH =μ PDCCH ), since the data slot number and the control slot number are the same, the base station and the UE can generate a scheduling offset adjusted according to the predetermined slot offset K0. On the other hand, when the subcarrier spacing of the data channel and the subcarrier spacing of the control channel are different (indicated by reference numeral 9-05, μ PDSCH ≠μ PDCCH ), since the data time slot number and the control time slot number are different, the base station and the UE can generate a scheduling offset adjusted according to the predetermined time slot offset K0 based on the subcarrier spacing of the PDCCH.

[0183] Next, a method for scheduling PUSCH transmission will be introduced. PUSCH transmission can be dynamically scheduled by UL grant in DCI, or by configured grant type 1 or type 2. Dynamic scheduling indication of PUSCH transmission can use DCI format 0_0 or 0_1.

[0184] Configured grant type 1 PUSCH transmissions do not receive an UL grant in the DCI and may be semi-statically configured via higher layer signaling by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant of Table 14. Configured grant type 2 PUSCH transmissions may be semi-statically scheduled via an UL grant in the DCI after receiving configuredGrantConfig not including rrc-ConfiguredUplinkGrant of Table 14 via higher layer signaling. When a PUSCH transmission is operated by a configured grant, the parameters applied to the PUSCH transmission are applied via the higher layer signaling configuredGrantConfig of Table 14, except for the scaling of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank and UCI-OnPUSCH provided by the higher layer signaling pusch-Config of Table 15. When the UE is provided with transformPrecoder in the higher layer signaling configuredGrantConfig of Table 14, the UE shall apply tp-pi2BPSK in pusch-Config of Table 15 for PUSCH transmissions operated by the configured grant.

[0185] Table 14

[0186]

[0187] The PUSCH transmission method will be described next. The DMRS antenna port used for PUSCH transmission is the same as the antenna port used for SRS transmission. PUSCH transmission can depend on the codebook-based transmission method and the non-codebook-based transmission method, respectively, depending on whether the value of txConfig in pusch-Config of Table 14 is "codebook" or "non-codebook".

[0188] As described above, PUSCH transmissions may be dynamically scheduled via DCI format 0_0 or 0_1, or semi-statically configured via a configured grant. If the UE receives an indication that PUSCH transmissions are scheduled via DCI format 0_0, the UE performs beam configuration for the PUSCH transmission using the pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the smallest ID in the UL BWP activated in the serving cell, where the PUSCH transmission is based on a single antenna port. The UE does not expect PUSCH transmissions to be scheduled via DCI format 0_0 within a BWP where a PUCCH resource including pucch-spatialRelationInfo is not configured. If the UE is not configured with txConfig in pusch-Config of Table 15, the UE does not expect scheduling with DCI format 0_1.

[0189] Table 15

[0190]

[0191] Next, the codebook-based PUSCH transmission will be described. Codebook-based PUSCH transmission can be dynamically scheduled through DCI format 0_0 or 0_1, or it can be semi-statically operated through a configured grant. When codebook-based PUSCH is dynamically scheduled through DCI format 0_1 ​​or semi-statically configured through a configured grant, the UE determines the precoder for PUSCH transmission based on the SRS resource indicator (SRI), the transmit precoding matrix indicator (TPMI), and the transmission level (the number of PUSCH transmission layers).

[0192] Here, the SRI can be given by the SRS resource indicator in the DCI, or it can be configured by the high-level signaling srs-ResourceIndicator. When transmitting a codebook-based PUSCH, the UE is configured with at least one SRS resource and can be configured with up to two SRS resources. When the SRI is provided to the UE through the DCI, the SRS resource indicated by the corresponding SRI represents the SRS resource corresponding to the SRI in the SRS resource transmitted before the PDCCH including the corresponding SRI. In addition, the TPMI and the transmission level can be given by the field precoding information and the number of layers in the DCI, or can be configured by high-level signaling (precodingAndNumberOfLayers). TPMI is used to indicate the precoder applied to PUSCH transmission. If the UE is configured with one SRS resource, the TPMI is used to indicate the precoder applied in one configured SRS resource. If the UE is configured with multiple SRS resources, the TPMI is used to indicate the precoder applied in the SRS resource indicated by the SRI.

[0193] The precoder used for PUSCH transmission is selected from the UL codebook whose number of antenna ports is the same as the value of SRS-Ports in the higher layer signaling SRS-Config. In codebook-based PUSCH transmission, the UE determines the codebook subset based on the TPMI and the codebookSubset in the higher layer signaling pusch-Config. The codebookSubset in the higher layer signaling pusch-Config can be configured with one of "fullyAndPartialAndNonCoherent", "partialAndNonCoherent" or "nonCoherent" based on the UE capabilities reported by the UE to the base station. If the UE reports the UE capability "partialAndNonCoherent", the UE does not expect the value of the higher layer signaling codebookSubset to be configured as "fullyAndPartialAndNonCoherent". In addition, if the UE reports the UE capability "nonCoherent", the UE does not expect the value of the higher layer signaling codebookSubset to be configured as "fullyAndPartialAndNonCoherent" or "partialAndNonCoherent". When nrofSRS-Ports in the higher layer signaling SRS-ResourceSet indicates two SRS antenna ports, the UE does not expect to configure the value of the higher layer signaling codebookSubset to "partialAndNonCoherent".

[0194] The UE may be configured with an SRS resource set, where the usage value in the higher layer signaling SRS-ResourceSet is configured as "codebook", and one SRS resource in the corresponding SRS resource set may be indicated by SRI. If multiple SRS resources are configured in the SRS resource set, where the usage value in the higher layer signaling SRS-ResourceSet is configured as "codebook", the UE expects the value of nrofSRS-Ports in the higher layer signaling SRS-Resource to be configured to be the same for all SRS resources.

[0195] The UE transmits one or more SRS resources contained in the SRS resource set to the base station, where the usage value is configured as "codebook" according to the high-level signaling, and the base station instructs the UE to perform PUSCH transmission by selecting one of the SRS resources transmitted by the UE and using the transmission beam information of the corresponding SRS resource. Here, in the codebook-based PUSCH transmission, SRI is used as information for selecting an index of an SRS resource and is included in the DCI. In addition, the base station also includes information for indicating the rank and TPMI of the UE for PUSCH transmission in the DCI. The UE performs PUSCH transmission by using the SRS resource indicated by the SRI and applying the precoder indicated by the rank and TPMI based on the transmission beam indication of the SRS resource.

[0196] Next, non-codebook based PUSCH transmissions will be described. Non-codebook based PUSCH transmissions can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically operated via a configured grant. When at least one SRS resource is configured in an SRS resource set, and the usage value in the higher-layer signaling SRS-ResourceSet in the SRS resource set is configured as "nonCodebook", the UE can schedule non-codebook based PUSCH transmissions via DCI format 0_1.

[0197] For an SRS resource set whose usage value in the higher layer signaling SRS-ResourceSet is configured as "nonCodebook", the UE may be configured with a connected non-zero power (NZP) CSI-RS resource. The UE may calculate the precoder for SRS transmission by measuring the NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the 1st symbol of the aperiodic SRS transmission in the UE is less than 42 symbols, the UE does not expect the information about the precoder for SRS transmission to be updated.

[0198] When the value of resourceType in the high-level signaling SRS-ResourceSet is configured as "non-periodic", the connected NZP CSI-RS will be represented by the SRS request (field of DCI format 0_1 ​​or 1_1). Here, if the connected NZP CSI-RS resource is a non-periodic NZP CSI-RS resource, when the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not "00", the connected NZP CSI-RS exists. In this case, the DCI should not indicate cross-carrier or cross-BWP scheduling. In addition, when the value of the SRS request indicates the presence of NZP CSI-RS, the corresponding NZP CSI-RS is located in the time slot of the PDCCH that transmits the SRS request field. Here, the TCI state configured by the scheduled subcarrier is not configured as QCL-TypeD.

[0199] If a periodic or semi-persistent SRS resource set is configured, the connected NZP CSI-RS may be indicated by the associated CSI-RS in the higher layer signaling SRS-ResourceSet.For non-codebook based transmission, the UE does not expect the higher layer signaling spatialRelationInfo for SRS resources and the associated CSI-RS in the higher layer signaling SRS-ResourceSet to be configured together.

[0200] When the UE is configured with multiple SRS resources, the UE can determine the precoder and transmission level applied to the PUSCH transmission based on the SRI indicated by the base station. Here, the SRI can be indicated by the field SRS resource indicator in the DCI, or can be configured by the high-level signaling srs-ResourceIndicator. As with the above-mentioned codebook-based PUSCH transmission, when the UE is provided with SRI through DCI, the SRS resource indicated by the SRI represents the SRS resource corresponding to the SRI in the SRS resource transmitted before the PDCCH including the SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be transmitted simultaneously in the same symbol in an SRS resource set is determined by the UE capability reported by the UE to the base station. Here, the SRS resources transmitted simultaneously by the UE occupy the same RB. The UE configures an SRS port for each SRS resource. Only one SRS resource set in which the usage value in the high-level signaling SRS-ResourceSet is configured as "nonCodebook" can be configured, and up to four SRS resources can be configured for non-codebook-based PUSCH transmission.

[0201] The base station sends an NZP-CSI-RS connected to the SRS resource set to the UE, and the UE performs calculation of a precoder for transmitting one or more SRS resources in the corresponding SRS resource set based on the measurement result when receiving the NZP-CSI-RS. When transmitting one or more SRS resources in the SRS resource set, the UE applies the calculated precoder to the base station, in which the usage is configured as "nonCodebook", and the base station selects one or more SRS resources from the received one or more SRS resources. In this case, in non-codebook based PUSCH transmission, the SRI indicates an index that can express a combination of one SRS resource or multiple SRS resources, and the SRI is included in the DCI. Here, the number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers of the PUSCH, and the UE performs PUSCH transmission by applying the precoder applied to the SRS resource transmission to each layer.

[0202] Fig.10 Radio protocol structures of a base station and a UE in a single cell case, a carrier aggregation case, and a dual connectivity case in a wireless communication system according to an embodiment are shown.

[0203] refer to Fig.10 The radio protocol of the next generation mobile communication system includes NR service data adaptation protocol (NR SDAP) S25 and S70, NR packet data convergence protocol (NR PDCP) S30 and S65, NR radio link control (NR RLC) S35 and S60, and NR medium access control (NR MAC) S40 and S55 for each UE and NR base station.

[0204] The functions of NR SPAP S25 and S70 may include one or more of the following:

[0205] -Transmit user plane data

[0206] - Mapping between Quality of Service (QoS) flows and data bearers (DRBs) for both DL and UL

[0207] - Marking of QoS flow ID in both DL and UL packets

[0208] -UL SDAP PDU reflects the mapping of QoS flows to DRBs.

[0209] Regarding SDAP layer devices, the UE can receive a configuration associated with whether to use a header of the SDAP layer device or whether to use a function of the SDAP layer device through an RRC message for each PDCP layer device, each bearer, and each logical channel. If the SDAP header is configured, the UE is instructed to update or reconfigure the mapping information between the data bearer and the QoS flow of UL and DL through a one-bit non-access stratum (NAS) reflected QoS indicator (NAS reflected QoS) and a one-bit access stratum (AS) reflected QoS indicator (AS reflected QoS) in the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used as data processing priority or scheduling information for supporting smooth services.

[0210] The functions of NR PDCP S30 and S65 may include one or more of the following functions:

[0211] -Header compression and decompression: Robust Header Compression (ROHC) only

[0212] -Transfer user data

[0213] - Sequential delivery of higher-level PDUs

[0214] - Out-of-order delivery of higher-level PDUs

[0215] - Reordering of PDCP PDUs for reception

[0216] - Duplicate detection of lower layer SDUs

[0217] –PDCP SDU retransmission

[0218] -Encryption and decryption

[0219] -Timer-based SDU discard in UL

[0220] In the above embodiment, the reordering function of the NR PDCP device refers to a function of reordering the PDCP PDUs received from the lower layer in sequence based on the PDCP sequence number (SN), and may include a function of transmitting data to the upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP device may include: a function of transmitting data regardless of the order, a function of reordering and recording lost PDCP PDUs, a function of providing a status report on lost PDCP PDUs to the transmission side, and a function of requesting retransmission of lost PDCP PDUs.

[0221] The functions of NR RLC S35 and S60 may include one or more of the following functions:

[0222] -Transmitting higher layer PDU

[0223] - Sequential delivery of higher-level PDUs

[0224] - Out-of-order delivery of higher-level PDUs

[0225] Error correction via ARQ

[0226] - Connection, segmentation and reassembly of RLC SDU

[0227] - Re-segmentation of RLC data PDUs

[0228] - Reorder RLC data PDUs

[0229] - Duplicate detection

[0230] -Protocol error detection

[0231] -RLC SDU discarded

[0232] -RLC re-establishment

[0233] The sequential delivery function of the NR RLC device refers to a function of transmitting the RLC SDU received from the lower layer to the upper layer in the order of reception. The sequential delivery function of the NR RLC device may include: a function of reassembling and transmitting multiple RLC SDUs in the case where one RLC SDU is initially divided into multiple RLC SDUs and is received; a function of reordering the received RLC PDUs based on the RLC SN or PDCP SN; a function of reordering and recording the lost RLC PDUs; a function of providing a status report on the lost RLC PDUs to the transmission side; and a function of requesting retransmission of the lost RLC PDUs. In the event of RLC SDU loss, the sequential delivery function of the NR RLC device may include: transmitting only the RLC SDUs before the lost RLC SDU in sequence to the upper layer; or, in the case where a predetermined timer expires but there is still RLC SDU loss, transmitting all RLC SDUs received before the start of the timer in sequence to the upper layer. Alternatively, the sequential delivery function of the NR RLC device may include a function of transmitting all RLC SDUs received so far in sequence to the upper layer in the case where a predetermined timer expires but there is still RLC SDU loss. In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival, regardless of the order of sequence numbers and sequence numbers), and may be transmitted to the PDCP device out of order. In the case of segmentation, the sequential delivery function may include the function of receiving segments stored in a buffer or segments received later, reconfiguring the segments into a complete RLC PDU, processing the RLC PDU, and transmitting the RLC PDU to the PDCP device. The NR RLC layer may not include a connection function, which may be performed by the NR MAC layer or may be replaced by a multiplexing function of the NR MAC layer.

[0234] In the above-mentioned embodiment, the out-of-order delivery function of the NR RLC device refers to a function of directly transmitting the RLC SDU received from the lower layer to the upper layer without considering the order, and may include: when one RLC SDU has been initially divided into multiple RLC SDUs and is received, a function of reassembling multiple RLC SDUs and transmitting them, and a function of storing the RLC SN or PDCP SN of the received RLC PDU, reordering and recording lost RLC PDUs.

[0235] NR MAC S40 and S55 may be connected to multiple NR RLC layer devices configured in one UE. The functions of NR MAC may include one or more of the following functions:

[0236] - Mapping between logical channels and transport channels

[0237] -Multiplexing / demultiplexing of MAC SDU

[0238] -Dispatch information report

[0239] - Error correction through HARQ

[0240] - Priority handling between logical channels of a UE

[0241] -Handle priority between UEs through dynamic scheduling

[0242] -MBMS service identification

[0243] -Transmission format selection

[0244] -filling

[0245] The NR physical (PHY) layers S45 and S50 may perform the following operations: channel coding and modulating high-layer data, generating OFDM symbols from high-layer data, transmitting the OFDM symbols through a radio channel, demodulating and channel decoding OFDM symbols received through a radio channel, and / or transmitting the OFDM symbols to a high layer.

[0246] The detailed structure of the radio protocol structure can be changed differently according to the carrier (or cell) operation method. For example, when the base station performs data transmission based on a single carrier (or cell) to the UE, the base station and the UE use a protocol structure, as shown in the figure mark S00, which has a single structure for each layer. On the other hand, when the base station transmits data to the UE based on carrier aggregation (CA) using multiple carriers in a single TRP, the base station and the UE have a single structure up to the RLC, but use a protocol structure that multiplexes the PHY layer through the MAC layer, as shown in the figure mark S10. For another example, when the base station transmits data to the UE based on a dual connection using multiple carriers in multiple TRPs, the base station and the terminal have a single structure up to the RLC, but use a protocol structure that multiplexes the PHY layer through the MAC layer, as shown in the figure mark S20.

[0247] Meanwhile, referring to the above description related to PDCCH and beam configuration, since the current Rel-15 and Rel-16NR do not support PDCCH retransmission, it is difficult to achieve the required reliability in scenarios requiring high reliability (such as URLLC). The present disclosure proposes a method for improving the PDCCH reception reliability of a UE by providing a PDCCH retransmission method through multiple transmission points (TRPs). The specific method will be described in detail in the following embodiments.

[0248] The content of the present disclosure is applicable to frequency division duplex (FDD) and time division duplex (TDD) systems. Hereinafter, high-layer signaling is a signal transmission method in which a signal is transmitted from a base station to a UE by using a DL data channel of a PHY layer, or from a UE to a base station by using a UL data channel of a PHY layer, and may be referred to as RRC signaling, PDCP signaling, or a MAC control element (MAC CE).

[0249] When determining whether to apply cooperative communication, the UE may use various methods, for example, the PDCCH for allocating the PDSCH to which cooperative communication is applied has a specific format, the PDCCH for allocating the PDSCH to which cooperative communication is applied includes a specific indicator indicating whether cooperative communication is applied, the PDCCH for allocating the PDSCH to which cooperative communication is applied is scrambled by a specific RNTI, or it is assumed that cooperative communication is applied within a specific interval indicated by a higher layer. For ease of description, the case where the UE receives the PDSCH to which cooperative communication is applied based on conditions similar to those described above will be referred to as a non-coherent joint transmission (NC-JT) case.

[0250] There are many ways to determine the priority between A and B, such as selecting the one with a higher priority and executing the corresponding operation according to a predetermined priority rule, or omitting or abandoning the operation corresponding to the one with a lower priority.

[0251] The above examples are described through multiple embodiments, but these embodiments are not independent, and one or more embodiments may be applied simultaneously or in combination.

[0252] The base station is the subject that performs resource allocation for the UE, and may be at least one of a gNodeB, a gNB, an eNodeB, a NodeB, a base station, a wireless access unit, a base station controller, or a node on a network. The UE may include a UE, a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. The embodiments of the present disclosure will be described using a 5G system as an example, but the embodiments of the present disclosure may also be applied to other communication systems with similar technical backgrounds or channel types. For example, LTE or LTE-A mobile communications and mobile communication technologies developed after 5G may be included. Therefore, the embodiments of the present disclosure may be applied to other communication systems with some modifications within the scope determined by a person of ordinary skill in the art that does not significantly deviate from the scope of the present disclosure. The contents of the present disclosure are applicable to FDD and TDD systems.

[0253] In addition, in the description of the content of the present disclosure, if it is determined that a detailed description of a related function or configuration may unnecessarily obscure the subject matter of the present disclosure, the detailed description thereof will be omitted. In addition, the terms to be described later are terms defined in consideration of the functions in the present disclosure, which may vary depending on the intentions or habits of users and operators. Therefore, they should be defined according to the content of this specification.

[0254] The high-layer signaling may be signaling corresponding to at least one or a combination of the following one or more signalings.

[0255] -MIB

[0256] -SIB or SIBX (X = 1, 2, ...)

[0257] -RRC

[0258] -MAC CE

[0259] In addition, the L1 signaling may be signaling corresponding to at least one or a combination of one or more signaling methods using the following PHY layer channels or signaling.

[0260] -PDCCH

[0261] -DCI

[0262] -UE-specific DCI

[0263] -Group Common DCI

[0264] - Public DCI

[0265] - Scheduling DCI (e.g., DCI for scheduling DL or UL data)

[0266] - Non-scheduled DCI (e.g., DCI not used for scheduling DL or UL data)

[0267] -PUCCH

[0268] -UL Control Information (UCI)

[0269] Hereinafter, in the present disclosure, determining the priority between A and B is referred to as selecting the one with a higher priority and performing an operation corresponding thereto according to a predetermined priority rule, or omitting or abandoning an operation corresponding to the one with a lower priority.

[0270] The above examples are described through multiple embodiments, but these embodiments are not independent, and one or more embodiments may be applied simultaneously or in combination.

[0271] According to the 3GPP NR system, the UE can use two PDSCH mapping types to determine the position of the DMRS for PDSCH reception. For convenience, the two PDSCH mapping types may be referred to as PDSCH mapping type A or PDSCH mapping type B.

[0272] According to PDSCH mapping type A, the 1st DMRS (1st DMRS or frontload DMRS) of PDSCH can start from the Kth symbol of the time slot. Here, the value of K is 2 or 3 and is represented in the PBCH. For reference, the symbol corresponding to K=0 (the 0th symbol) is the 1st symbol of the time slot. In order for the UE to receive the PDSCH of PDSCH mapping type A, the time domain of PDSCH should include the Kth symbol. That is, with respect to the PDSCH time domain allocation of PDSCH mapping type A, the start symbol (S) should have one of 0, 1, 2, and 3 symbols, and the length (L) should be 3, 4, 14. Table 16 below shows possible combinations of starting symbol (S) and length (L) when PDSCH mapping type A is used.

[0273] According to PDSCH mapping type B, the first DMRS of PDSCH (first DMRS or front-loaded DMRS) can be located in the first symbol of the scheduled PDSCH. Unlike PDSCH mapping type A, in PDSCH mapping type B, the position of the first DMRS can be determined according to the time resource allocation of the scheduled PDSCH. Regarding the PDSCH time domain allocation of PDSCH mapping type B, the starting symbol (S) can be 0, 1, One of the 12 symbols, the length (L) can be 2, 3, Table 16 shows possible combinations of starting symbol (S) and length (L) when PDSCH mapping type B is used.

[0274] Table 16

[0275] Effective S and L combinations

[0276]

[0277] Although PDSCH mapping types are described here, two PUSCH mapping types (PUSCH mapping type A and PUSCH mapping type B) can also be used for PUSCH. In the following description, for convenience, the mapping type of PDSCH to PUSCH is omitted.

[0278] The UE may receive the time domain information and an indication of the mapping type through a time domain resource allocation (TDRA) field in the DCI format.

[0279] The base station may configure a TDRA table for a DCI format for the UE. The TDRA table has multiple rows. Each row may include an index of a TDRA row, time domain information (S, L) included in the TDRA row, a mapping type of the TDRA row, and / or one or more of a time slot offset value (K0 value) for receiving a PDSCH or a time slot offset value (K2 value) for sending a PUSCH according to the time domain information of the TDRA row.

[0280] The UE may receive the index of the TDRA row in the TDRA field of the DCI format, and thus, may obtain the time domain information of the TDRA row corresponding to the index of the TDRA row, information on the mapping type, and the like.

[0281] In the case of mapping type A and mapping type B, they may have different use cases. For example, in the case of PDSCH (or PUSCH) of mapping type A, the 1st DMRS always starts from the Kth symbol of the time slot regardless of the time domain resource allocation of PDSCH (or PUSCH). Therefore, although different UEs receive the scheduling of PDSCH (or PUSCH) with different time domain resource allocation, the position of the 1st DMRS of PDSCH (or PUSCH) is the same. Therefore, mapping type A is suitable for multiplexing between different UEs, that is, multi-user MIMO (MU-MIMO). In the case of mapping type B, when different UEs receive (transmit) PDSCH (or PUSCH) with different starting positions, the position of the 1st DMRS of PDSCH (or PUSCH) of different UEs may be different. In the case of mapping type B, since the DMRS is always located in the 1st symbol of the scheduled PDSCH (or PUSCH), the UE is able to receive the DMRS and perform channel estimation or PDSCH decoding the fastest (the base station is able to receive the DMRS and perform channel estimation or PUSCH decoding the fastest). Therefore, mapping type B may be applicable to an environment that requires fast reception (transmission) and decoding of the PDSCH (or PUSCH). Therefore, different mapping types may have different DMRS configurations.

[0282] For each mapping type, the UE may have a different DMRS configuration.

[0283] The DMRS configuration may include one or more of the following three pieces of information.

[0284] -dmrs-Type: Configured as one of DMRS configuration types 1 and 2

[0285] -maxLength: Configure the maximum number of symbols that DMRS can occupy

[0286] -dmrs-AdditionalPosition: Configures additional DMRS in addition to the first DMRS (first DMRS or frontload DMRS).

[0287] These three pieces of information of DMRS configuration can be configured differently for each mapping type. For example, in the case of mapping type A, dmrs-Type can be configured as 1, and in the case of mapping type B, dmrs-Type can be configured as 2. For example, in the case of mapping type A, maxLength can be configured as 2, and in the case of mapping type B, maxLength can be configured as 1. For example, dmrs-AdditionalPosition of mapping type A and dmrs-AdditionlaPosition of mapping type B may be different.

[0288] The Antenna Port field is described below.

[0289] The UE needs information about the DMRS port to receive PDSCH or send PUSCH. This information can be indicated in the antenna port field of the DCI format used to schedule PDSCH or PUSCH.

[0290] The Antenna Port field may indicate a row of the antenna port table. Here, a row of the antenna port table may include one or more of the following: an index of a row in the antenna port table, an index (or multiple indexes) of a DMRS port corresponding to the row of the antenna port table, a number of DMRS symbols corresponding to the row of the antenna port table (present when maxLength is equal to or greater than 2), and / or a number of code division multiplexing (CDM) groups without data corresponding to the row of the antenna port table.

[0291] The UE can receive different DMRS configurations for each mapping type. For example, mapping type A can be configured as a first DMRS configuration, and mapping type B can be configured as a second DMRS configuration. Therefore, the first antenna port table for PDSCH (or PUSCH) scheduled with mapping type A may be different from the second antenna port table for PDSCH (or PUSCH) scheduled with mapping type B. In addition, the number of rows in the two antenna port tables may be different. In the same row index of the two antenna port tables, an index (or multiple indexes) of different DMRS ports, different numbers of DMRS symbols, or different numbers of CDM groups without data may be included.

[0292] The UE may receive a row of one of the indicated two antenna port tables in the DCI format. More specifically, the UE may determine the length of the antenna port field in the DCI format based on the maximum number of rows in each of the two antenna port tables. For example, assume that the first antenna port table includes 32 rows in total and the second antenna port table includes 64 rows. In this case, the UE may determine the length of the antenna port field based on the maximum value of 64. That is, it may be determined as ceil(log2(64))=6 bits.

[0293] The UE can determine the mapping type of the PDSCH (or PUSCH) scheduled through the TDRA field of the DCI format. The UE can determine the antenna port table based on the DMRS configuration of the mapping type. In addition, the required number of bits can be determined based on the number of rows of the determined antenna port table. The required number of bits may be equal to or less than the number of bits of the antenna port. The UE can obtain the row index of the antenna port table from some bits (e.g., the least significant bit (LSB)) of the required number of bits in the antenna port field. Through a series of processes, the UE can obtain the mapping type and DMRS-associated information (index of the DMRS port, number of DMRS symbols, number of CDM groups without data, etc.) of the scheduled PDSCH (or PUSCH).

[0294] For reference, in the case of PUSCH, the antenna port table may be determined according to the DMRS configuration of the mapping type of the scheduled PUSCH and the level of the PUSCH.

[0295] Table 17 is the antenna port field of DCI format 0_1 ​​for PUSCH scheduling, and Tables 18 to 37 are the corresponding antenna port tables.

[0296] Table 17

[0297]

[0298]

[0299] Table 18 (Table 7.3.1.1.2-6): Antenna port, transform precoder enabled, dmrs-Type = 1, maxLength = 1, but both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured and used modulation.

[0300]

[0301] Table 19 (Table 7.3.1.1.2-6A): Antenna port, transform precoder enabled, both dmrs-UplinkTransformPrecoding and tp-pi2BPSK configured, and e / 2-BPSK modulation used, dmrs-Type = 1, maxLength = 1

[0302]

[0303] Table 20 (Table 7.3.1.1.2-7): Antenna port, transform precoder enabled, dmrs-Type = 1, maxLength = 2, but both dmrs-UplinkTransformPrecoding and tp-pi2BPSK are configured and used modulation.

[0304] value Number of DMRS CDM groups without data DMRS Port Number of front-loaded symbols 0 2 0 1 1 2 1 1 2 2 2 1 3 2 3 1 4 2 0 2 5 2 1 2 6 2 2 2 7 2 3 2 8 2 4 2 9 2 5 2 10 2 6 2 11 2 7 2 12-15 Reserve Reserve Reserve

[0305] Table 21 (Table 7.3.1.1.2-7A): Antenna port, transform precoder enabled, both dmrs-UplinkTransformPrecoding and tp-pi2BPSK configured, used Modulation, dmrs-Type = 1, maxLength = 2

[0306] value Number of DMRS CDM groups without data DMRS Port Number of front-loaded symbols 0 2 0,nSCID=0 1 1 2 0,nSCID=1 1 2 2 2, nSCID=0 1 3 2 2, nSCID=1 1 4 2 0,nSCID=0 2 5 2 0,nSCID=1 2 6 2 2, nSCID=0 2 7 2 2, nSCID=1 2 8 2 4, nSCID=0 2 9 2 4, nSCID=1 2 10 2 6, nSCID=0 2 11 2 6,nSCID=1 2 12-15 Reserve Reserve Reserve

[0307] Table 22 (Table 7.3.1.1.2-8): Antenna port, transform precoder disabled, DMRS-Type = 1, maxLength = 1, rank = 1

[0308] value Number of DMRS CDM groups without data DMRS Port 0 1 0 1 1 1 2 2 0 3 2 1 4 2 2 5 2 3 6-7 Reserve Reserve

[0309] Table 23 (Table 7.3.1.1.2-9): Antenna port, transform precoder disabled, DMRS-Type = 1, maxLength = 1, rank = 2

[0310] value Number of DMRS CDM groups without data DMRS Port 0 1 0,1 1 2 0,1 2 2 2,3 3 2 0,2 4-7 Reserve Reserve

[0311] Table 24 (Table 7.3.1.1.2-10): Antenna port, transform precoder disabled, DMRS-Type = 1, maxLength = 1, rank = 3

[0312]

[0313] Table 25 (Table 7.3.1.1.2-11): Antenna port, transform precoder disabled, DMRS-Type = 1, maxLength = 1, rank = 4

[0314]

[0315] Table 26 (Table 7.3.1.1.2-12): Antenna port, transform precoder disabled, dmrs-Type=1, maxLength=2, rank=1

[0316] value Number of DMRS CDM groups without data DMRS Port Number of front-loaded symbols 0 1 0 1 1 1 1 1 2 2 0 1 3 2 1 1 4 2 2 1 5 2 3 1 6 2 0 2 7 2 1 2 8 2 2 2 9 2 3 2 10 2 4 2 11 2 5 2 12 2 6 2 13 2 7 2 14-15 Reserve Reserve Reserve

[0317] Table 27 (Table 7.3.1.1.2-13): Antenna port, transform precoder disabled, DMRS-Type = 1, maxLength = 2, rank = 2

[0318]

[0319]

[0320] Table 28 (Table 7.3.1.1.2-14): Antenna port, transform precoder disabled, DMRS-Type = 1, maxLength = 2, rank = 3

[0321] value Number of DMRS CDM groups without data DMRS Port Number of front-loaded symbols 0 2 0-2 1 1 2 0,1,4 2 2 2 2,3,6 2 3-15 Reserve Reserve Reserve

[0322] Table 29 (Table 7.3.1.1.2-15): Antenna port, transform precoder disabled, DMRS-Type = 1, maxLength = 2, rank = 4

[0323] value Number of DMRS CDM groups without data DMRS Port Number of front-loaded symbols 0 2 0-3 1 1 2 0,1,4,5 2 2 2 2,3,6,7 2 3 2 0,2,4,6 2 4-15 Reserve Reserve Reserve

[0324] Table 30 (Table 7.3.1.1.2-16): Antenna port, transform precoder disabled, DMRS-Type = 2, maxLength = 1, rank = 1

[0325]

[0326]

[0327] Table 31 (Table 7.3.1.1.2-17): Antenna port, transform precoder disabled, DMRS-Type = 2, maxLength = 1, rank = 2

[0328] value Number of DMRS CDM groups without data DMRS Port 0 1 0,1 1 2 0,1 2 2 2,3 3 3 0,1 4 3 2,3 5 3 4,5 6 2 0,2 7-15 Reserve Reserve

[0329] Table 32 (Table 7.3.1.1.2-18): Antenna port, transform precoder disabled, DMRS-Type = 2, maxLength = 1, rank = 3

[0330] value Number of DMRS CDM groups without data DMRS Port 0 2 0-2 1 3 0-2 2 3 3-5 3-15 Reserve Reserve

[0331] Table 33 (Table 7.3.1.1.2-19): Antenna port, transform precoder disabled, DMRS-Type = 2, maxLength = 1, rank = 4

[0332] value Number of DMRS CDM groups without data DMRS Port 0 2 0-3 1 3 0-3 2-15 Reserve Reserve

[0333] Table 34 (Table 7.3.1.1.2-20): Antenna port, transform precoder disabled, DMRS-Type = 2, maxLength = 2, rank = 1

[0334]

[0335]

[0336] Table 35 (Table 7.3.1.1.2-21): Antenna port, transform precoder disabled, DMRS-Type = 2, maxLength = 2, rank = 2

[0337]

[0338]

[0339] Table 36 (Table 7.3.1.1.2-22): Antenna port, transform precoder disabled, dmrs-Type=2, maxLength=2, rank=3

[0340] value Number of DMRS CDM groups without data DMRS Port Number of front-loaded symbols 0 2 0-2 1 1 3 0-2 1 2 3 3-5 1 3 3 0,1,6 2 4 3 2,3,8 2 5 3 4,5,10 2 6-31 Reserve Reserve Reserve

[0341] Table 37 (Table 7.3.1.1.2-23): Antenna port, transform precoder disabled, DMRS-Type = 2, maxLength = 2, rank = 4

[0342] value Number of DMRS CDM groups without data DMRS Port Number of front-loaded symbols 0 2 0-3 1 1 3 0-3 1 2 3 0,1,6,7 2 3 3 2,3,8,9 2 4 3 4,5,10,11 2 5-31 Reserve Reserve Reserve

[0343] Table 38 is the antenna port field of DCI format 1_1 for PDSCH scheduling, and Tables 39 to 46 are the corresponding antenna port tables.

[0344] Table 38

[0345]

[0346]

[0347] Table 39 (Table 7.3.1.2.2-1): Antenna port (1000+DMRS port), dmrs-Type=1, maxLength=1

[0348]

[0349]

[0350] Table 40 (Table 7.3.1.2.2-1A): Antenna port (1000+DMRS port), dmrs-Type=1, maxLength=1

[0351]

[0352] Table 41 (Table 7.3.1.2.2-2): Antenna port (1000+DMRS port), dmrs-Type=1, maxLength=2

[0353]

[0354] Table 42 (Table 7.3.1.2.2-2A): Antenna port (1000+DMRS port), dmrs-Type=1, maxLength=2

[0355]

[0356] Table 43 (Table 7.3.1.2.2-3): Antenna port (1000+DMRS port), dmrs-Type=2, maxLength=1

[0357]

[0358] Table 44 (Table 7.3.1.2.2-3A): Antenna port (1000+DMRS port), dmrs-Type=2, maxLength=1

[0359]

[0360] Table 45 (Table 7.3.1.2.2-4): Antenna port (1000+DMRS port), dmrs-Type=2, maxLength=2

[0361]

[0362]

[0363] Table 46 (Table 7.3.1.2.2-4A): Antenna port (1000+DMRS port), dmrs-Type=2, maxLength=2

[0364]

[0365]

[0366] Assume that dmrs-Type=1 and maxLength=2 are configured as the DMRS configuration for any PDSCH mapping type for the UE. In this case, the corresponding antenna port table is Table 42. The UE may receive a DCI format for a PDSCH that schedules a PDSCH mapping type, and the DCI format may include an antenna port field. The antenna port field may represent one of the 32 rows (value 0 to value 31) of Table 42. For reference, referring to Table 42, when only one codeword is enabled in the PDSCH, one of all 32 rows (value 0 to value 31) may be indicated. If two codewords are enabled in the PDSCH at the same time, one of 4 rows (value 0 to value 3) of the 32 rows may be indicated. In addition, other rows (value 3 to value 31) may not be indicated.

[0367] Assume that dmrs-Type=2 and maxLength=2 are configured as DMRS configurations for any PUSCH mapping type for the UE. In this case, the corresponding antenna port table is one of Tables 34 to 37. Here, an antenna port table is determined according to the level. Assume that the level is 3. In this case, Table 36 can be used as an antenna port table. The UE can receive a DCI format for scheduling a PUSCH of a PUSCH mapping type, and the DCI format can include an antenna port field. The antenna port field can indicate one of the 32 rows (value 0 to value 31) of Table 36. For reference, referring to Table 36, one of the 32 rows (value 0 to value 5) can be indicated. In addition, other rows (value 6 to value 31) may not be indicated.

[0368] In a subsequent embodiment, at least one TDRA row of the TDRA table of the UE includes multiple pieces of scheduling information, one piece of scheduling information among the multiple pieces of scheduling information of the TDRA row includes mapping type A, and the other scheduling information includes mapping type B. That is, when receiving an indication of the TDRA row, the UE may receive (or send) a PDSCH (or PUSCH) of mapping type A according to one piece of scheduling information, and may receive (or send) a PDSCH (or PUSCH) of mapping type B according to the other scheduling information.

[0369] In subsequent embodiments, for ease of description, “a TDRA row including different mapping types” means that the TDRA row includes multiple pieces of scheduling information, one piece of scheduling information among the multiple pieces of scheduling information includes mapping type A, and the other pieces of scheduling information include mapping type A and mapping type B.

[0370] The following describes the process of using UL PTRS.

[0371] The UE may configure the higher-level parameter phaseTrackingRS of PTRS on the higher-level parameter DMRS-UplinkConfig. When transmitting PUSCH to the base station, the UE may transmit PTRS for phase tracking of the UL channel. The process of UE transmitting UL PTRS may be determined based on whether transform precoding is performed during PUSCH transmission. When transform precoding is performed and the transformPrecoderEnabled area is configured in the higher-level parameter PTRS-UplinkConfig, the sampleDensity in the transformPrecoderEnabled area may indicate N in Table 47 below. RB0 To N RB4 When transform precoding is performed and the transformPrecoderEnabled area is configured in the high-level parameter PTRS-UplinkConfig, the UE can determine the scheduled resource N according to Table 47. RB In addition, if the transform precoder is applied to PUSCH transmission, the number of bits of the PTRS-DMRS association field used to indicate the association between the PTRS and the DMRS of DCI format 0_1 ​​or 0_2 may be 0.

[0372] Table 47

[0373] Scheduled bandwidth Number of PT-RS groups The number of samples per PT-RS group <![CDATA[N RB0 ≤N RB <N RB1 ]]> 2 2 <![CDATA[N RB1 ≤N RB <N RB2 ]]> 2 4 <![CDATA[N RB2 ≤N RB <N RB3 ]]> 4 2 <![CDATA[N RB3 ≤N RB <N RB4 ]]> 4 4 <![CDATA[N RB4 ≤N RB ]]> 8 4

[0374] When transform precoding is not applied to PUSCH transmission and the higher-level parameter phaseTrackingRS is configured, the UE may set N in the transformPrecoderDisabled field of the higher-level parameter PTRS-UplinkConfig. RB0 To N RB1 Indicates frequencyDensity, ptrs-MCS 1 To ptrs-MCS 3 Indicated as timeDensity. As described in Table 48-1 and Table 48-2, according to the MCS (l MCS ) and RB(N RB), the UE can determine the PTRS density in the time domain (L PT-RS ) and PTRS density in the frequency domain (K PT-RS ). In the following Table 48-1, ptrs-MCS 4 It is not specified as a high-level parameter, but the base station and UE can know the ptrs-MCS based on the configured MCS table. 4 It's 29 or 28.

[0375] Table 48-1

[0376] Scheduling MCS <![CDATA[Time density (L PT-RS )]]> <![CDATA[I MCS <ptrs-MCS 1 ]]> No PT-RS <![CDATA[ptrs-MCS 1 ≤I MCS <ptrs-MCS 2 ]]> 4 <![CDATA[ptrs-MCS 2 ≤I MCS <ptrs-MCS 3 ]]> 2 <![CDATA[ptrs-MCS 3 ≤I MCS <ptrs-MCS 4 ]]> 1

[0377] Table 48-2

[0378] Scheduled bandwidth <![CDATA[Frequency density (K PT-RS )]]> <![CDATA[N RB <N RB0 ]]> No PT-RS <![CDATA[N RB0 ≤N RB <N RB1 ]]> 2 <![CDATA[N RB1 ≤N RB ]]> 4

[0379] If the transform precoder is not applied to PUSCH transmission and PTRS-UplinkConfig is configured, the base station may indicate a 2-bit "PTRS-DMRS association" area to the UE to indicate the association between the DMRS and PTRS of DCI format 0_1 ​​or 0_2. According to the maximum number of PTRS ports configured as maxNrofPorts in the high-level parameter PTRS-UplinkConfig, the indicated 2-bit PTRS-DMRS association field may be applied to Table 49-1 or Table 49-2 below. If the maximum number of PTRS ports is 1, the UE may determine the association between PTRS and DMRS as the 2-bit and PTRS-DMRS association field indicated in Table 49-1, and transmit PTRS according to the determined association. If the maximum number of PTRS ports is 2, the UE may determine the association between PTRS and DMRS as the 2-bit and PTRS-DMRS association field indicated in Table 49-2, and may transmit PTRS according to the determined association.

[0380] Table 49-1

[0381]

[0382]

[0383] Table 49-2

[0384]

[0385] The DMRS ports in Tables 49-1 and 49-2 can be determined by the table determined by the "antenna port field" indicated by the DCI indicating the PTRS-DMRS association and the high-level parameter configuration. If the transform precoder is not configured as the high-level configuration of the PUSCH, the dmrs-Type is configured as 1, the maxLength is configured as 2 for the DMRS, and the rank of the PUSCH is 2, the UE can determine the DMRS port by the "antenna port" table shown in Table 50 below and the bits indicated by the antenna port area. In the case of supporting non-codebook based PUSCH, the UE can determine the rank value by referring to the SRI area indicated by the DCI including the "antenna port" field (for example, if the SRI area does not exist, the rank can be regarded as 1). If the rank supports codebook based PUSCH, the UE can determine the rank value by referring to the TPMI area indicated by the DCI including the "antenna port" field. Table 50 is an example of an antenna port table for reference when configuring the above-mentioned PUSCH, but is not limited to this, and when PUSCH is configured with other parameters, the DMRS port can be determined according to the configuration and bit of the "antenna port" field indicated by the DCI according to the "antenna port" table.

[0386] Table 50

[0387] value Number of DMRS CDM groups without data DMRS Port Number of front-loaded symbols 0 1 0,1 1 1 2 0,1 1 2 2 2,3 1 3 2 0,2 1 4 2 0,1 2 5 2 2,3 2 6 2 4,5 2 7 2 6,7 2 8 2 0,4 2 9 2 2,6 2 10-15 Reserve Reserve Reserve

[0388] The first scheduled DMRS to the fourth scheduled DMRS in Table 49-1 may be defined as the values ​​obtained by sequentially mapping the bits of the "antenna port" field of the DCI with the DMRS ports indicated by the "antenna port" table according to the high-level configuration. For example, if the bits of the "antenna port" field of the DCI are 0001, and the DMRS port is determined with reference to Table 50, the scheduled DMRS ports may be 0 and 1, DMRS port 0 may be defined as the first scheduled DMRS, and DMRS port 1 may be defined as the second scheduled DMRS. The DMRS port determined with reference to the "antenna port" table according to another high-level configuration and the bits of another "antenna port" field may also apply. The UE may determine a DMRS port among the DMRS ports defined above, which is associated with the PTRS port by referring to the bits of the PTRS-DMRS association indication in the DCI, and may transmit the PTRS according to the determined DMRS port.

[0389] In Table 49-2, the DMRS ports sharing PTRS port 0 and the DMRS ports sharing PTRS port 1 may be defined according to codebook-based PUSCH transmission or non-codebook-based PUSCH transmission. When the UE transmits PUSCH based on a partially coherent or non-coherent codebook, the UL layer transmitted through PUSCH antenna ports 1000 and 1002 may be associated with PTRS port 0, and the UL layer transmitted through PUSCH antenna ports 1001 and 1003 may be associated with PTRS port 1. More specifically, when layer 3: TPMI=2 is selected for codebook-based PUSCH transmission, the first layer may be associated with PTRS port 0 because the first layer is transmitted to PUSCH antenna ports 1000 and 1002, the second layer may be transmitted through PUSCH antenna port 1001, the third layer may be transmitted through PUSCH antenna port 1002, and thus the second layer and the third layer may be associated with PTRS port 1. Each of the three layers may mean a DMRS port. The DMRS port of the first layer may correspond to the "first DMRS port of shared PTRS port 0" in Table 49-2, the DMRS port of the second layer may correspond to the "first DMRS port of shared PTRS port 1" in Table 49-2, and the DMRS port of the third layer may correspond to the "second DMRS port of shared PTRS port 1" in Table 49-2. Similarly, the DMRS port associated with PTRS port 0 and the DMRS port associated with PTRS port 1 may be determined according to different numbers of layers and TPMIs. In the case where the UE transmits PUSCH based on non-codebook, the DMRS port associated with PTRS port 0 and the DMRS port associated with PTRS port 1 may be distinguished according to the antenna port and SRI indicated by the DCI. More specifically, whether the SRS resource (included in the SRS resource set, whose purpose is "nonCodebook") is associated with PTRS port 0 or PTRS port 1 may be configured by the high-level parameter ptrs-PortIndex. The base station may use SRI to indicate the SRS resource for non-codebook-based PUSCH transmission. The ports of the indicated SRS resources can be mapped one-to-one to each PUSCH DMRS port. The association between the PUSCH DMRS port and the PTRS port can be determined based on the high-level parameter ptrs-PortIndex of the SRS resource mapped to the DMRS port. More specifically, if the ptrs-PortIndex of SRS resources 1 to 4 included in the SRS resource set whose purpose is nonCodebook is configured as n0, n0, n1, n1 respectively, SRI is used, indicating that PUSCH is transmitted through SRS resources 1, 2 and 4, and DMRS ports 0, 1 and 2 are indicated as antenna port fields, then the ports of SRS resources 1, 2 and 4 can be mapped to DMRS ports 0, 1 and 2 respectively.In addition, according to the ptrs-PortIndex in the SRS resource, DMRS ports 0 and 1 can be associated with PTRS port 0, and DMRS port 2 can be associated with PTRS port 1. Therefore, in Table 49-2, DMRS port 0 can correspond to "the first DMRS port of shared PTRS port 0", DMRS port 1 can correspond to "the second DMRS port of shared PTRS port 0", and DMRS port 2 can correspond to "the first DMRS port of shared PTRS port 1". Similarly, the DMRS port associated with PTRS port 0 and the DMRS port associated with PTRS port 1 can be determined according to different SRI values ​​and methods of configuring ptrs-PortIndex in SRS resources of different modes. For two PTRS ports, the UE can determine the association between the DMRS port and the PTRS port as described above. The UE can determine the DMRS port associated with PTRS port 0 by referring to the MSB bit in the PTRS-DMRS association among the multiple DMRS ports associated with each PTRS port. The UE can determine the DMRS port associated with PTRS port 1 by referring to the LSB bit to transmit PTRS.

[0390] Multiple PDSCH / PUSCH scheduling will now be introduced.

[0391] 3GPP's Rel-17 NR introduces a new scheduling method. The present disclosure is related to the new scheduling method. The new scheduling methods introduced in Rel-17NR are "multi-PDSCH scheduling" and "multi-PUSCH scheduling". Through "multi-PDSCH scheduling", one DCI can schedule one or more PDSCHs, and through "multi-PUSCH scheduling", one DCI can schedule one or more PUSCHs. Here, in multiple PDSCHs or multiple PUSCHs, each PDSCH or PUSCH transmits a different transport block (TB). Since the base station does not schedule multiple DCIs for each of the multiple PDSCHs or multiple PUSCHs in the scheduling UE, the overhead of the DL control channel can be reduced by using multi-PDSCH scheduling and multi-PUSCH scheduling. However, since one DCI for multi-PDSCH scheduling and multi-PUSCH scheduling should include scheduling information of multiple PDSCHs or multiple PUSCHs, the size of the DCI may increase. To this end, a method is needed for the UE to preferentially interpret the DCI when configuring multi-PDSCH scheduling and multi-PUSCH scheduling for the UE.

[0392] Although multiple PDSCH scheduling is described in this disclosure, embodiments using the techniques proposed in this disclosure may also be used for multiple PUSCH scheduling.

[0393] The base station may configure multiple PDSCH scheduling for the UE. The base station may explicitly configure multiple PDSCH scheduling for the UE through a higher layer signal (e.g., an RRC signal). In addition, the base station may implicitly configure multiple PDSCH scheduling through a higher layer signal (e.g., an RRC signal) in the UE.

[0394] The base station can configure the TDRA table as follows through a high-level signal (e.g., an RRC signal) to perform multi-PDSCH scheduling to the UE. The TDRA table may include one or more rows. The number of rows can be configured to be N_row at most, and each row can be assigned an inherent index. The value of the inherent index can be one of 1, 2, ..., N_row. Here, N_row can be 64, but is not limited to this. One or more scheduling information can be configured for each row. Here, when a piece of scheduling information is configured in a row, the row schedules one PDSCH. That is, when the row is indicated, this may indicate that a single PDSCH scheduling has been indicated. If multiple pieces of scheduling information are configured in a row, the multiple pieces of scheduling information schedule multiple PDSCHs in sequence. That is, when the row is indicated, this may indicate that multiple PDSCH scheduling has been indicated.

[0395] The scheduling information may include at least one of K0, SLIV, and PDSCH mapping type. That is, when multiple PDSCH scheduling is indicated, a row may include multiple pieces of scheduling information (K0, SLIV, PDSCH mapping type). Among the multiple pieces of scheduling information, the Nth scheduling information (K0, SLIV, PDSCH mapping type) is the scheduling information of the Nth PDSCH. For reference, a row may include at most N_pdsch pieces of scheduling information (K0, SLIV, PDSCH mapping type). Here, N_pdsch may be 8, but is not limited thereto. For example, a row may schedule at most 8 PDSCHs.

[0396] Here, K0 indicates the time slot for scheduling PDSCH, and represents the time slot difference between the time slot of PDCCH in which DCI for transmission scheduling PDSCH is received and the time slot for scheduling PDSCH. That is, if K0=0, PDSCH and PDCCH are the same time slot. The start and length indicator value (SLIV) indicates the symbol index at which PDSCH starts within a time slot, and the number of consecutive symbols to which PDSCH is allocated. The PDSCH mapping type indicates information related to the position of the 1st DMRS (frontload DMRS) of PDSCH. In the case of PDSCH mapping type A, the 1st DMRS (frontload DMRS) of PDSCH starts from the 3rd symbol to the 4th symbol of the time slot; and in the case of PDSCH mapping type B, the 1st DMRS (frontload DMRS) of PDSCH starts from the 1st symbol of the symbol of scheduled PDSCH.

[0397] When configuring a row of the TDRA table through a high-level signal, some of K0, SLIV, and PDSCH mapping types of the scheduling information may be omitted. In this case, the omitted information may be interpreted as a default value or a preconfigured value. For example, when K0 is omitted, the value of K0 may be interpreted as 0. In addition, when configuring a row of the TDRA table, information other than K0, SLIV, and PDSCH mapping type may be additionally configured.

[0398] In the following description, multi-PDSCH scheduling is configured for the UE. Here, multi-PDSCH scheduling configuration means that multiple scheduling information is configured in at least one row of the TDRA table. For reference, one piece of scheduling information can be configured in another row of the TDRA table. Therefore, even if multi-PDSCH scheduling is configured for the UE, the UE can still be instructed to perform single PDSCH scheduling or multi-PDSCH scheduling according to the TDRA field of the received DCI. In other words, the multi-PDSCH scheduling indication corresponds to the case where one row of the TDRA table received by the UE via DCI includes multiple scheduling information, while the single PDSCH scheduling indication corresponds to the case where one row of the TDRA table received by the UE via DCI includes one piece of scheduling information.

[0399] In the case of a single PDSCH scheduling indication, one PDSCH is scheduled, and the one PDSCH requires information such as MCS, new data indicator (NDI), redundancy version (RV), and HARQ process number (HPN). To this end, the DCI indicating single PDSCH scheduling should include information such as MCS, NDI, RV, and HPN of one PDSCH. More specifically, the following DCI is recommended:

[0400] - A DCI indicating single PDSCH scheduling may include one MCS field. The MCS (ie, the modulation scheme and code rate of channel coding) indicated in the MCS field may be applied to one PDSCH scheduled by the DCI.

[0401] - The DCI indicating single PDSCH scheduling may include a 1-bit NDI field. An NDI value may be obtained from the 1-bit NDI field, and based on the NDI value, it may be determined whether one PDSCH transmits a new transport block or retransmits a previous transport block.

[0402] - The DCI indicating single PDSCH scheduling may include a 2-bit RV field. The RV value may be obtained from the 2-bit RV field, and the redundancy version of one PDSCH may be determined based on the RV value.

[0403] -The DCI for scheduling a single PDSCH may include one HPN field. One HPN field may be 4 bits. (For reference, when the UE supports up to 32 HARQ processes, the HPN field is extended to 5 bits, but for the convenience of explaining the present disclosure, it is assumed that the HPN field is 4 bits). One HARQ process ID may be indicated by one HPN field. One HARQ process ID may be the HARQ process ID of one scheduled PDSCH.

[0404] When multiple PDSCH scheduling is indicated, since multiple PDSCHs are to be scheduled, each PDSCH requires information such as MCS, NDI, RV, and HPN. To this end, the DCI indicating multiple PDSCH scheduling should include information such as MCS, NDI, RV, and HPN of each scheduled PDSCH. More specifically, the following DCI is recommended:

[0405] -DCI indicating multiple PDSCH scheduling may include an MCS field. The MCS indicated in the MCS field (e.g., modulation scheme and code rate of channel coding) may be equally applicable to all PDSCHs scheduled by the DCI. That is, the DCI for multiple PDSCH scheduling cannot schedule different PDSCHs by using different MCSs.

[0406] -The DCI indicating multi-PDSCH scheduling may include a K-bit NDI field. Here, K may be the maximum value of the number of scheduling information included in each row of the TDRA table. For example, if the TDRA table includes two rows, row 1 includes 4 pieces of scheduling information, and row 2 includes 8 pieces of scheduling information, the value of K (e.g., K=8) may be obtained. The kth bit of the K-bit NDI field may indicate the NDI value of the PDSCH corresponding to the kth scheduling information. That is, the kth PDSCH may obtain the NDI value from the kth bit of the K-bit NDI field, and determine whether the kth PDSCH transmits a new transport block or retransmits a previous transport block based on the NDI value.

[0407] -The DCI indicating multi-PDSCH scheduling may include a K-bit RV field. The k-th bit of the K-bit RV field may indicate the RV value of the PDSCH corresponding to the k-th scheduling information. That is, the k-th PDSCH may obtain the RV value from the k-th bit of the K-bit RV field, and the redundancy version of the k-th PDSCH may be determined based on the RV value.

[0408] -The DCI indicating multiple PDSCH scheduling may include an HPN field. An HPN field may be 4 bits. (For reference, if the UE supports up to 32 HARQ processes, the HPN field may be extended to 5 bits, but as described herein, 4 bits are assumed for ease of explanation). An HARQ process ID may be represented by an HPN field. An HARQ process ID may be the HARQ process ID of the 1st PDSCH among the PDSCHs scheduled by the DCI indicating multiple PDSCH scheduling. Here, the 1st PDSCH corresponds to the 1st scheduling information. That is, in the case of the 2nd PDSCH (corresponding to the 2nd scheduling information), the HPN is a value obtained by adding 1 to the HARQ process ID of the 1st PDSCH. For reference, if the HARQ process ID exceeds the maximum number of HARQ process IDs (numOfHARQProcessID) configured in the UE, a modulo calculation is performed. In other words, when the HARQ process ID indicated by the DCI is "x", the HARQ process ID of the kth PDSCH will be determined according to the following formula 2.

[0409] HPN of the kth PDSCH = (x+k-1) modulo numOfHARQProcessID

[0410] ...Formula 2

[0411] As described above, when indicating single PDSCH scheduling, the DCI includes a 1-bit NDI field or a 2-bit RV field; and when indicating multiple PDSCH scheduling, the DCI includes a K-bit NDI field or includes a K-bit RV field. For reference, a single PDSCH scheduling indication or a multiple PDSCH scheduling indication is indicated in the TDRA field of the DCI (i.e., whether it is a single PDSCH scheduling indication or a multiple PDSCH scheduling indication is determined according to the number of scheduling information included in the row of the indicated TDRA field). Therefore, one DCI should support both single PDSCH scheduling and multiple PDSCH scheduling. If the length of the DCI for the single PDSCH scheduling indication and the length of the DCI for the multiple PDSCH scheduling indication are different, "0" can be filled in the shorter DCI to make them have the same length.

[0412] The DCI interpretation process of the UE is as follows. The UE receives the DCI. In this case, the length of the DCI can be assumed to be the larger value of the length of the DCI for the single PDSCH scheduling indication and the length of the DCI for the multi-PDSCH scheduling indication. The UE can know the position of the TDRA field in the DCI. The position of the TDRA field can be the same in the DCI for the single PDSCH scheduling indication and the DCI for the multi-PDSCH scheduling indication. The UE can determine whether the received DCI is a DCI for a single PDSCH scheduling indication or a DCI for a multi-PDSCH scheduling indication through the TDRA field. When the number of scheduling information included in the indicated row of the TDRA field is one, the UE can determine the DCI for the single PDSCH scheduling indication, and if the number of scheduling information included in the row of the TDRA field is two or more, the UE can determine the DCI for the multi-PDSCH scheduling indication. When the UE determines the DCI as a single PDSCH scheduling indication, the DCI can be interpreted according to the determination result. That is, the DCI can be interpreted as the NDI field being 1 bit and the RV field being 2 bits. When the UE determines the DCI as a multi-PDSCH scheduling indication, the DCI can be interpreted according to the determination result. That is, the DCI can be interpreted as the NDI field being K bits and the RV field being K bits. For reference, the position of other fields in the DCI may vary depending on the length of the NDI field or the RV field. Therefore, the bit length of other fields may be the same, but the position in the DCI may be different depending on whether it is a single PDSCH scheduling indication or a multi-PDSCH scheduling indication.

[0413] Fig.11 A PDSCH scheduling scheme according to an embodiment is shown.

[0414] The first row (row 0) of the TDRA table includes four scheduling information (e.g., K0, SLIV and / or PDSCH mapping type). Here, the first SLIV is called SLIV00, the second SLIV is called SLIV01, the third SLIV is called SLIV02, and the fourth SLIV is SLIV03. Therefore, when receiving the indication of the first row (row 0) of the TDRA table, the UE can determine that multi-PDSCH scheduling is indicated.

[0415] The second row (row 1) of the TDRA table includes two scheduling information (eg, K0, SLIV and / or PDSCH mapping type). Here, the first SLIV is referred to as SLIV 1 0 , the second SLIV is called SLIV 1 1 Therefore, when the UE receives the indication of the second row (row 1) of the TDRA table, it can be determined that multiple PDSCH scheduling is indicated.

[0416] The third row (row 2) of the TDRA table includes a piece of scheduling information (e.g., K0, SLIV and / or PDSCH mapping type). Here, SLIV is referred to as SLIV 2 0 Therefore, when the UE receives the indication of the third row (row 2) of the TDRA table, it can be determined that single PDSCH scheduling is indicated.

[0417] Fig.11 (a) shows a case where the UE receives an indication of the first row (row 0) of the TDRA table. The TDRA field of the DCI received by the UE on the PDCCH 1100 may indicate the first row (row 0) of the TDRA table. Therefore, the UE may receive four PDSCHs based on the four scheduling information (e.g., K0, SLIV, and / or PDSCH mapping type) of the first row (row 0). The UE may receive four PDSCHs based on the four scheduling information (e.g., K0, SLIV, and / or PDSCH mapping type) according to the SLIV. 0 0 (i.e., the first SLIV) determines the symbol of the first PDSCH 1101 to be received, which can be based on the SLIV 0 1 (i.e., the second SLIV) determines the symbol of the second PDSCH 1102 to be received, which can be based on the SLIV 0 2 (i.e., the third SLIV) determines the symbol of the third PDSCH 1103 to be received, which can be based on the SLIV 0 3 (ie, the fourth SLIV) determines the symbol of the fourth PDSCH 1104. Each of the four PDSCHs has an inherent HARQ process ID. That is, the first PDSCH can be received with HPN 0 As the HARQ process ID, the second PDSCH can be HPN 1 As the HARQ process ID, the third PDSCH can be HPN 2 As the HARQ process ID, the fourth PDSCH can be HPN 3 As the HARQ process ID. Here, the HPN field of the DCI may indicate the HARQ process ID of the first PDSCH, and the HARQ process IDs of the remaining PDSCHs may be determined based on the HARQ process ID of the first PDSCH. 0 = 0 can be indicated by DCI as the HARQ process ID of the first PDSCH. In this case, HPN 1 =1 can indicate the HARQ process ID of the second PDSCH, HPN 1 =2 can indicate the HARQ process ID of the third PDSCH, HPN 1=3 may indicate the HARQ process ID of the 4th PDSCH.

[0418] Fig.11 (b) shows a situation where the UE receives an indication of the second row (row 1) of the TDRA table. The TDRA field of the DCI received by the UE on PDCCH 1110 may indicate the second row (row 1) of the TDRA table. Therefore, the UE may receive two PDSCHs based on the two scheduling information (e.g., K0, SLIV and / or PDSCH mapping type) of the second row (row 1). The UE may determine the symbol for receiving the first PDSCH 1111 based on SLIV10 as the first SLIV, and may determine the symbol for receiving the second PDSCH 1112 based on SLIV11 as the second SLIV. Each of the two PDSCHs has an inherent HARQ process ID. That is, the HARQ process ID of the first PDSCH may be HPN0, and the HARQ process ID of the second PDSCH may be HPN1. Here, the HPN field of the DCI may indicate the HARQ process ID of the first PDSCH, and the HARQ process IDs of the remaining PDSCHs may be determined based on the HARQ process ID of the first PDSCH. For example, HPN0=0 may be indicated as the HARQ process ID of the first PDSCH through the DCI. In this case, HPN1=1 may be indicated as the HARQ process ID of the second PDSCH.

[0419] Fig.11 (c) shows a case where the UE receives an indication of row 2 (row 1) of the TDRA table. The TDRA field of the DCI received by the UE on PDCCH 1120 may indicate row 3 (row 2) of the TDRA table. Therefore, the UE may receive a PDSCH based on the scheduling information (e.g., K0, SLIV, and / or PDSCH mapping type) of row 3 (row 2). The UE may receive a PDSCH based on the SLIV. 2 0 (Single SLIV) determines the symbol used to receive a PDSCH 1121. The HARQ process ID of a PDSCH (i.e., HPN 0 ) is indicated by DCI. For example, the HPN field of the DCI may indicate the HPN 0 =0 as the HARQ process ID of the first PDSCH.

[0420] Fig.12 DCI for single PDSCH scheduling and multi-PDSCH scheduling according to an embodiment are shown.

[0421] refer to Fig.12(a) and (b), the UE can determine the position of the TDRA field 1200 in the received DCI. The position of the TDRA field of the DCI scheduled by a single PDSCH is the same as the position of the DCI scheduled by multiple PDSCHs. The UE can determine whether the received DCI indicates a DCI scheduled by a single PDSCH or a DCI scheduled by multiple PDSCHs based on the value of the TDRA field.

[0422] If the row corresponding to the value of the TDRA field of the received DCI (e.g., row 3 (row 2) of the TDRA table) includes a piece of scheduling information (e.g., K0, SLIV and / or PDSCH mapping type), the UE interprets this as a DCI scheduled with a single PDSCH, such as Fig.12 As shown in (a).

[0423] refer to Fig.12 (a), the DCI for single PDSCH scheduling may include a 5-bit MCS field 1205, a 1-bit NDI field 1210, a 2-bit RV field 1215, and a 4-bit HARQ field 1220. In addition, the DCI for single PDSCH scheduling may also include other fields in addition to the above fields. For example, the DCI may also include an antenna port field 1225 or a DMRS sequence initialization field 1230. In addition, when the DCI for single PDSCH scheduling is shorter than the DCI for multi-PDSCH scheduling, a padding bit 1235 may also be included therein.

[0424] If the row corresponding to the TDRA field value of the received DCI (e.g., row 1 (row 0) to row 2 (row 1) of the TDRA table) includes two or more scheduling information (e.g., K0, SLIV and / or PDSCH mapping type), the UE understands the situation as a DCI with multiple PDSCH scheduling, such as Fig.12 As shown in (b). Fig.12 (b), the DCI for multi-PDSCH scheduling may include a 5-bit MCS field 1255, a K-bit NDI field 1260 and 1261, a K-bit RV field 1262 and 1263, and a 4-bit HARQ field 1270. In addition, the DCI for multi-PDSCH scheduling also includes other fields in addition to the above fields. For example, the DCI may also include an antenna port field 1275 and a DMRS sequence initialization field 1280. For reference, Fig.12 (b) shows a DCI that schedules up to two PDSCHs. Here, the 2-bit NDI fields 1260 and 1261 are shown separately, but can also be integrated into one 2-bit NDI field. Fig.12 In (b), the 2-bit RV fields 1262 and 1263 are shown separately, but can also be integrated into one 2-bit RV field.

[0425] refer to Fig.12 (a) and (b), assuming that the length of the DCI indicating single PDSCH scheduling is shorter than the length of the DCI indicating multiple PDSCH scheduling, padding bits 1235 are added to the DCI indicating single PDSCH scheduling. If the length of the DCI indicating single PDSCH scheduling is longer than the length of the DCI indicating multiple PDSCH scheduling, padding bits may be added to the DCI indicating multiple PDSCH scheduling.

[0426] Hereafter, unless otherwise specified, PDSCH assumes transmission of a single codeword. If two codewords are configured for the UE, the DCI field is used for the first codeword unless otherwise specified.

[0427] Fig.13 HARQ-ACK transmission of one or more PDSCHs scheduled by DCI when the DCI indicates multiple PDSCH scheduling according to an embodiment is shown.

[0428] The base station may configure one or more K1 values ​​for the UE. One or more K1 values ​​may be referred to as a K1 set. The DCI indicating multi-PDSCH scheduling may include an indicator indicating a K1 value in the K1 set. More specifically, the DCI may include a PDSCH-to-HARQ_feedback timing indicator field of up to 3 bits. This field may indicate a K1 value in the K1 set.

[0429] The UE can determine the time slot for transmitting HARQ-ACK of multiple PDSCHs based on a K1 value and the time slot of the last PDSCH scheduled among multiple PDSCHs. For reference, HARQ-ACK of all PDSCHs scheduled by one DCI can be transmitted through one PUCCH in the time slot for transmitting HARQ-ACK. The time slot after K1 time slots from the time slot of the last PDSCH scheduled is the time slot for transmitting HARQ-ACK of multiple PDSCHs. That is, the PUCCH including HARQ-ACK of multiple PDSCHs can be transmitted in the time slot after K1 time slots from the time slot of the last PDSCH scheduled.

[0430] refer to Fig.13 , assuming that the DCI received by the UE on PDCCH 1300 indicates row 0 of the TDRA table, such as Fig.12As shown, and according to row 0 of the TDRA table, PDSCH is scheduled in time slot n-5, time slot n-4, time slot n-3, and time slot n-2. In addition, assuming that the UE receives an indication that the value of K1 is 2, the UE can determine time slot n located two time slots later as the time slot for transmitting HARQ-ACK, and the value of K1 is counted from time slot n-2, which is the last time slot for scheduling PDSCH. That is, the UE can transmit HARQ-ACK information of PDSCH 1301 of time slot n-5, PDSCH 1302 of time slot n-4, PDSCH 1303 of time slot n-3, and PDSCH 1304 of time slot n-2 through PUCCH 1305 of time slot n.

[0431] Multi-cell multi-PDSCH / PUSCH scheduling will now be described.

[0432] A new scheduling method is introduced in Rel-18 NR of 3GPP. In the above-mentioned multi-PDSCH / PUSCH scheduling, one DCI schedules one or more PDSCHs or PUSCHs in one cell. As a new scheduling method of Rel-18 NR, one DCI can schedule PDSCH or PUSCH in one cell among multiple cells or in each cell among multiple cells. This scheduling method can be called multi-cell multi-PDSCH / PUSCH scheduling.

[0433] The UE may receive an indication of a cell that schedules a PDSCH or a PUSCH through one DCI. For example, one DCI may include an indication of cell A and cell B. In addition, the UE may receive an indication of scheduling information of cell A (e.g., K0 / SLIV / PDSCH mapping type in the case of PDSCH or K2 / SLIV / PUSCH mapping type in the case of PUSCH) and an indication of scheduling information of cell B. The UE may receive PDSCH or send PUSCH based on the scheduling information indicated by cell A and cell B.

[0434] Here, the scheduling information of each cell may include indications of different mapping types.

[0435] The present disclosure will be described below based on multi-PDSCH / PUSCH scheduling, but the present disclosure is also applicable to multi-cell multi-PDSCH / PUSCH scheduling.

[0436] Hereinafter, in the present disclosure, it will be described that multiple PDSCHs or PUSCHs of multi-PDSCH / PUSCH scheduling may have different mapping types and different antenna port tables are applicable to the respective mapping types. Similarly, in multi-cell multi-PDSCH / PUSCH scheduling, the PDSCH or PUSCH of multiple cells may have different mapping types. Therefore, the problem of applying different antenna port tables to each mapping type may arise. In addition, in multi-cell multi-PDSCH / PUSCH scheduling, even if the PDSCH to PUSCH of different cells has the same mapping type, different antenna port tables may be applied according to the scheduled cells. Therefore, although the problem of different antenna port tables according to different mapping types will be described later, this can also be extended to the problem of different antenna port tables according to different cells.

[0437] According to the multi-PDSCH scheduling and multi-PUSCH scheduling configuration, the UE may receive multiple pieces of scheduling information configured in one TDRA row, and each of the multiple pieces of scheduling information may include a SLIV and a mapping type. Therefore, the UE may be configured to receive an indication of a TDRA row including scheduling information with different mapping types through one DCI.

[0438] Different DMRS configuration information can be configured for different mapping types. If the DMRS configuration information is different, different antenna port tables indicated by the DMRS port can be configured. The DCI format for scheduling PDSCH as PUSCH includes an antenna port field for indicating a row in the antenna port table. However, as described above, the antenna port field of the DCI format can be used to indicate a row in one antenna port table. However, when a TDRA row with multiple scheduling information of different mapping types is indicated to the UE, the UE should receive an indication of a row in each of the two antenna port tables. The method for achieving this goal is described below.

[0439] The following describes the restrictions on DMRS configuration.

[0440] According to an embodiment of the present disclosure, the UE may expect mapping type A and mapping type B to use the same antenna port table. Here, in order to use the same antenna port table, the UE may receive the same DMRS type (dmrs-Type) and DMRS maximum length (maxLength) configured by a higher layer. The base station may configure the same DMRS type (dmrs-Type) and DMRS maximum length (maxLength) for the UE.

[0441] When a TDRA table including TDRA rows of different mapping types is configured, the UE may expect mapping type A and mapping type B to use the same antenna port table. That is, when a TDRA table including TDRA rows of different mapping types is configured, the UE may expect the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B to be the same.

[0442] When the base station is to configure a TDRA table including TDRA rows of different mapping types for the UE, the base station should configure the TDRA table for the UE so that mapping type A and mapping type B use the same antenna port table. That is, when the base station is to configure a TDRA table including TDRA rows of different mapping types for the UE, the base station should configure the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B for the UE to be the same.

[0443] When a TDRA table that does not include a TDRA row containing different mapping types is configured, the UE can have the same or different antenna port tables for mapping type A and mapping type B. That is, when a TDRA table that does not include a TDRA row containing different mapping types is configured, the UE can expect the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B to be the same or different. In other words, when a TDRA table that does not include a TDRA row containing different mapping types is configured in the UE, there is no configuration restriction on the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B.

[0444] When the base station is to configure a TDRA table that does not include TDRA rows containing different mapping types for the UE, the base station can configure the TDRA table for the UE so that mapping type A and mapping type B use the same or different antenna port tables. That is, when the base station is to configure a TDRA table that does not include TDRA rows containing different mapping types for the UE, the base station can configure the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B for the UE to be the same or different. In other words, when the base station is to configure a TDRA table that does not include TDRA rows containing different mapping types for the UE, the base station can configure the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B for the UE without any configuration restrictions.

[0445] Therefore, when at least one row in the TDRA table configured for the UE corresponds to a TDRA row including different mapping types, the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B should be the same. This also affects other TDRA rows in the TDRA table.

[0446] For example, assume that in the TDRA table, the first TDRA row includes scheduling information for mapping type A, and the second TDRA row includes scheduling information for mapping type B. In existing operations (when the operation is not performed), the base station can configure different DMRS types (dmrs-Type) or DMRS maximum lengths (maxLength) for mapping type A and mapping type B in the UE. Therefore, the PDSCH (or PUSCH) scheduled in the first TDRA row and the PDSCH (or PUSCH) scheduled in the second TDRA row can have DMRSs with different DMRS types (dmrs-Type) or DMRS maximum lengths (maxLength). However, in the above embodiment, the PDSCH (or PUSCH) scheduled in the first TDRA row and the PDSCH (or PUSCH) scheduled in the second TDRA row always have DMRSs with the same DMRS type (dmrs-Type) or DMRS maximum length (maxLength). This may make it difficult for the base station to configure a DMRS suitable for the mapping type.

[0447] To solve this problem, the following embodiments may be considered.

[0448] The UE may additionally receive a DMRS configuration only for TDRA rows including different mapping types through a higher layer signal (e.g., an RRC signal). The DMRS configuration may include at least a DMRS type (dmrs-Type) and a DMRS maximum length (maxLength). The UE may receive the following three DMRS configurations.

[0449] - DMRS configuration type 1: The DMRS configuration of the TDRA row only includes the scheduling information of mapping type A

[0450] - Second DMRS configuration: The DMRS configuration of the TDRA row only includes the scheduling information of mapping type B

[0451] - DMRS configuration type 3: The DMRS configuration of the TDRA row includes scheduling information of mapping type A and scheduling information of mapping type B

[0452] For reference, the first DMRS configuration may be a DMRS configuration configured in mapping type A ("dmrs-DownlinkForPDSCH-MappingTypeA" in the case of PDSCH mapping type A, and "dmrs-UplinkForPUSCH-MappingTypeA" in the case of PUSCH mapping type A), the second DMRS configuration may be a DMRS configuration configured in mapping type B ("dmrs-DownlinkForPDSCH-MappingTypeB" in the case of PDSCH mapping type B, and "dmrs-UplinkForPUSCH-MappingTypeB" in the case of PUSCH mapping type B), and the third DMRS configuration may be a newly configured DMRS configuration.

[0453] After receiving the DCI format, the UE may perform the following operations.

[0454] The UE may obtain the index of the TDRA row from the TDRA field of the received DCI format. The UE may obtain the scheduling information and the mapping type of the scheduling information included in the TDRA row.

[0455] If the TDRA row includes only scheduling information of mapping type A, the UE may assume the first DMRS configuration. Therefore, the UE may determine the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength) according to the first DMRS configuration, and may use the antenna port table according to the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength).

[0456] When the TDRA row includes only scheduling information of mapping type B, the UE may assume the second DMRS configuration. Therefore, the UE may determine the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength) according to the second DMRS configuration, and may use the antenna port table according to the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength).

[0457] When the TDRA row includes scheduling information for mapping type A and scheduling information for mapping type B, the UE can assume the third DMRS configuration. Therefore, the UE can determine the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength) according to the third DMRS configuration, and can use the antenna port table according to the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength). Here, the mapping type A and mapping type B scheduled in the TDRA row use the same antenna port table. Therefore, the DMRS configurations of mapping type A and mapping type B can have the same DMRS port, the same number of DMRS symbols, and the same number of CDM groups without data. However, according to mapping type A and mapping type B, the location of the actually transmitted DMRS may be determined in different ways.

[0458] The UE may interpret the antenna port field based on the antenna port table.

[0459] The method of interpreting the Antenna Port field is as follows.

[0460] When the number of rows in the antenna port table corresponding to the first DMRS configuration is N 1 When the number of digits required is X 1 (X 1 =ceil(log 2 (N 1 ))).

[0461] When the number of rows in the antenna port table corresponding to the second DMRS configuration is N 2 When the number of digits required is X 2 (X 2 =ceil(log 2 (N 2 ))).

[0462] When the number of rows in the antenna port table corresponding to the third DMRS configuration is N 3 When the number of digits required is X 3 (X 3 =ceil(log 2 (N 3 ))).

[0463] In the DCI format monitored by the UE, the length of the antenna port field may be determined as follows.

[0464] In the case where only one of the three DMRS configurations is configured for the UE, the length of the antenna port field is X according to the configured DMRS configuration. 1 Bit, X 2 Bit and X 3That is, when only the first DMRS configuration is configured for the UE, the length of the antenna port field is X 1 When only the second DMRS configuration is configured for the UE, the length of the antenna port field is X 2 When only the third DMRS configuration is configured for the UE, the length of the antenna port field is X 3 Bit.

[0465] If only two of the three DMRS configurations are configured for the UE, the length of the antenna port field is the maximum number of bits required for the two DMRS configurations. That is, the length of the antenna port field is max{X n ,X m} bits. Here n and m are determined according to the configured DMRS configuration. That is, when the UE is configured with the first DMRS configuration and the second DMRS configuration, the length of the antenna port field is max{X1,X2} bits. When the UE is configured with the first DMRS configuration and the third DMRS configuration, the length of the antenna port field is max{X1,X2} bits. 1 ,X 3 When the UE is configured with the second and third DMRS configurations, the length of the antenna port field is max{X 2 ,X 3}Bit.

[0466] If all three DMRS configurations are configured for the UE, the length of the antenna port field is the maximum number of bits required by the three DMRS configurations. That is, the length of the antenna port field is max{X 1 ,X 2 ,X 3}Bit.

[0467] When the UE analyzes the antenna port field based on the antenna port table, all bits of the antenna port field may not be needed. For example, when all three DMRS configurations are configured for the UE, the DCI format monitored by the UE includes max{X 1 ,X 2 ,X 3 If the TDRA row indicated by the TDRA field of the DCI format only includes scheduling information of mapping type A, max{X 1 ,X 2 ,X 3} LSB of the antenna port field X 1 bit, but the MSB max{X 1 ,X 2 ,X 3}-X 1Therefore, the UE may assume that the MSB of the antenna port field is max{X 1 ,X 2 ,X 3}-X 1 The bits are filled with '0' and the Antenna Port field may be interpreted based on this assumption.

[0468] If the TDRA row indicated by the TDRA field of the DCI format includes only mapping type B scheduling information, then MSBmax{X 1 ,X 2 ,X 3} LSB of the antenna port field X 2 bit, but the MSB max{X 1 ,X 2 ,X 3}}-X 2 Therefore, the UE may assume that the MSB of the antenna port field is max{X 1 ,X 2 ,X 3}-X 2 The bits are filled with '0' and the Antenna Port field may be interpreted based on this assumption.

[0469] If the TDRA row indicated by the TDRA field of the DCI format includes scheduling information of mapping type A and scheduling information of mapping type B, max{X 1 ,X 2 ,X 3} LSB of the antenna port field X 3 bit, the MSB max{X 1 ,X 2 ,X 3}-X 3 Therefore, the UE may assume that the MSB of the antenna port field is max{X 1 ,X 2 ,X 3}-X 3 The bits are filled with '0' and the Antenna Port field may be interpreted based on this assumption.

[0470] The third DMRS configuration may be the same as the second DMRS configuration or one of the first DMRS configurations. That is, when configuring the third DMRS configuration, the UE may configure a configuration that is the same as the first DMRS configuration or one of the second DMRS configurations, but may not configure a configuration that is different from the first DMRS configuration and the second DMRS configuration. With this restriction, the UE may configure at most two different DMRS configurations.

[0471] The third DMRS configuration may require a new higher layer signal (eg, RRC signal). This may cause the design and overhead of the higher layer signal. The following will introduce a method for improving this problem.

[0472] The UE may not receive the higher layer signal configured by the third DMRS configuration. On the contrary, the third DMRS configuration may be determined by the following three methods.

[0473] -First method: The UE may assume that the third DMRS configuration is always the same as the first DMRS configuration. For the third DMRS configuration, the UE may use the scheduling information DMRS configuration of the TDRA row that includes only mapping type A. In other words, the UE may determine the DMRS of mapping type B, which is scheduled by the TDRA row including different mapping types, by using the DMRS configuration of mapping type A (i.e., DMRS type (dmrs-Type) or DMRS maximum length (maxLength)). Therefore, for mapping type B scheduled by the TDRA row including different mapping types, the UE may use the antenna port table of mapping type A. Here, the position of the DMRS of mapping type B may follow the scheme of mapping type B.

[0474] -Second method: The UE may assume that the third DMRS configuration is always the same as the second DMRS configuration. That is, for the third DMRS configuration, the UE may use the DMRS configuration of the TDRA row that includes only the scheduling information of mapping type B. In other words, the UE may determine the DMRS of mapping type A, which is scheduled by the TDRA row including different mapping types, by using the DMRS configuration of mapping type B (i.e., the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength)). Therefore, for mapping type A scheduled by the TDRA row including different mapping types, the UE may use the antenna port table of mapping type B. Here, the DMRS position of mapping type A may follow the scheme of mapping type A.

[0475] - A third method: The UE may assume that the third DMRS configuration is the same as the first DMRS configuration or the second DMRS configuration based on the mapping type of one piece of scheduling information among a plurality of pieces of scheduling information scheduled by a TDRA row including different mapping types.

[0476] For example, the UE may assume that the third DMRS configuration is the same as the first DMRS configuration or the second DMRS configuration based on the mapping type of the earliest scheduling information among multiple pieces of scheduling information scheduled by TDRA rows including different mapping types. When the mapping type of the earliest scheduling information is mapping type A, the UE may assume that the DMRS configuration of mapping type A (i.e., the first DMRS configuration) is the same as the third DMRS configuration. When the mapping type of the earliest scheduling information is mapping type B, the UE may assume that the DMRS configuration of mapping type B (i.e., the second DMRS configuration) is the same as the third DMRS configuration.

[0477] Here, the earliest scheduling information may be replaced by the latest scheduling information. The earliest scheduling information may be the earliest scheduling information in time.

[0478] According to an embodiment, multiple PDSCH / PUSCH scheduling may introduce one or more restrictions on the same mapping type.

[0479] When the UE has an antenna port table corresponding to mapping type A (which is different from the antenna port table corresponding to mapping type B), the UE may expect the same mapping type of the scheduling information included in the TDRA row. When the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of the UE's mapping type A is different from the DMRS type (dmrs-Type) or maximum length (maxLength) of mapping type B, the UE may expect the same mapping type of the scheduling information included in the TDRA row.

[0480] In addition, when TDRA rows including different mapping types are configured in the TDRA table, the UE may assume that the antenna port table corresponding to mapping type A and the antenna port table corresponding to mapping type B are the same. When TDRA rows including different mapping types are configured in the TDRA table, the UE may assume that the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type A and the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type B are the same.

[0481] That is, the UE may be configured not to expect that the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type A and the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type B are different from each other, and TDRA rows including different mapping types are configured in the TDRA table. The UE may be configured not to expect that the antenna port table corresponding to mapping type A and the antenna port table corresponding to mapping type B are different from each other, and TDRA rows including different mapping types are configured in the TDRA table.

[0482] When the base station configures the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type A and the DMRS type (dmrs-Type) or maximum length (maxLength) of mapping type B for the UE, the base station can configure the mapping type of the scheduling information included in the TDRA row to be always the same.

[0483] When the base station configures the TDRA table for the UE with TDRA rows including different mapping types, the base station shall configure the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type A and the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type B to be the same.

[0484] That is, the base station can configure the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type A to be different from the DMRS type (dmrs-Type) or maximum length (maxLength) of mapping type B, and can configure the TDRA table to include TDRA rows of different mapping types.

[0485] Since the PDSCH (or PUSCH) scheduled in the TDRA field of the DCI format received by the UE always has the same mapping type, the position and length of the DMRS can be determined based on the DMRS configuration of the mapping type. In addition, the UE can determine an antenna port table based on the DMRS configuration of the mapping type. A row of an antenna port table can be indicated in the antenna port field.

[0486] According to an embodiment, the antenna port field indicates two antenna ports per row of the table.

[0487] When the UE receives a TDRA row including different mapping types configured in the TDRA table, the UE may assume the respective antenna port fields of the monitored DCI format mapping type A and mapping type B. Alternatively, the UE may assume that the antenna port field of the monitored DCI format includes bits for mapping type A and bits for mapping type B.

[0488] The length of the antenna port field can be determined as (X 1 +X 2 )Bit.

[0489] MSB of the Antenna Port field X 1 The bit can be used to indicate a row of the antenna port table according to the DMRS configuration of mapping type A. The LSB of the antenna port field is 2 The MSB X bit can be used to indicate a row of the antenna port table according to the DMRS configuration of mapping type B. 1 Bit can be used for mapping type B, LSB X 2 Bits can be used to map type A.

[0490] For example, when the UE receives a TDRA row including different mapping types configured in the TDRA table, the UE may obtain the X of the antenna port table indicating the mapping type A in the DCI format to be monitored. 1 bit and X for indicating the antenna port table of mapping type B 2 Since UE can use X 1 The indication of a row of the antenna port table of receive mapping type A is indicated by X 2 The bit receives an indication of a row of the antenna port table of mapping type B, and thus antenna port indication can be performed without restriction.

[0491] The DCI format monitored by the UE may not always be required (X 1 +X 2 For example, if the TDRA field of the DCI format received by the UE indicates that the TDRA row includes only scheduling information of one mapping type, then (X 1 +X 2 ) bit. To this end, in the DCI format monitored by the UE, the antenna port field can be determined as follows.

[0492] According to one method, when the TDRA table configured for the UE includes at least one TDRA row including different mapping types, the DCI format monitored by the UE may include (X 1 +X 2 That is, even if the TDRA row indicated by the TDRA field of the DCI format includes only one type of scheduling information, the UE always receives (X 1 +X2 ) bit antenna port field. Here, the UE can obtain the index value of a row of the antenna port table of a mapping type from the antenna port field, as shown below.

[0493] UE can assume that (X 1 +X 2 ) bits are binary numbers, the binary numbers are converted to decimal numbers, and then the value corresponding to the decimal number is regarded as the index of the row of the antenna port table. When the number of rows in the antenna port table is N i and the number of digits required is indicated as X ¬i (X i =ceil(log 2 (N i ))) bit, the UE may assume that the MSB of the antenna port field ((X 1 +X 2 -X i ) bit is filled with "0". Here, when one mapping type is mapping type A, i=1; and when one mapping type is mapping type B, i=2.

[0494] When one mapping type is mapping type A, the MSB of the antenna port field can be used. 1 The LSB of the antenna port field can be used to obtain the index of the row of the antenna port table of mapping type A; when a mapping type is mapping type B, the LSB of the antenna port field can be used. 2 The UE can assume that the LSB of the antenna port field is x 2 When a mapping type is mapping type B, the UE may assume that “0” is filled in the MSB of the Antenna Port field. 1 Position in the middle.

[0495] According to another method, the length of the antenna port field may be different according to the mapping type of the TDRA line indicated by the TDRA field of the DCI format received by the UE. If the TDRA line indicated by the TDRA field of the DCI format received by the UE includes only one type of scheduling information, the UE may assume that the received DCI format includes max{X 1 ,X 2 That is, when the TDRA row indicated by the TDRA field of the DCI format received by the UE includes only scheduling information of one mapping type, the UE may assume that the DCI format includes an antenna port field having the same number of bits as the existing antenna port field.

[0496] If the TDRA row indicated by the TDRA field of the DCI format received by the UE includes scheduling information of mapping type A and scheduling information of mapping type B, the UE may assume that (X 1 +X 2 )-bit antenna port field is included in the received DCI format. That is, when the TDRA row indicated by the TDRA field of the DCI format received by the UE includes scheduling information of mapping type A and scheduling information of mapping type B, the UE may assume that (X 1 +X 2 ) bits of antenna port field are included in the DCI format.

[0497] According to another method, the length of the antenna port field may be different according to the number of scheduling information included in the TDRA row indicated by the TDRA field of the DCI format received by the UE. When the TDRA row indicated by the TDRA field of the DCI format received by the UE includes only one piece of scheduling information, the UE may assume that the received DCI format includes max{X 1 ,X 2 That is, when the TDRA row indicated by the TDRA field of the DCI format received by the UE includes only one piece of scheduling information, the UE may assume that the antenna port field having the same number of bits as the existing antenna port field is included in the DCI format.

[0498] If the TDRA row indicated by the TDRA field of the DCI format received by the UE includes multiple pieces of scheduling information, the UE may assume that the received DCI format includes (X 1 +X 2 That is, if the TDRA line indicated by the TDRA field of the DCI format received by the UE includes multiple pieces of scheduling information, the UE may assume that (X 1 +X 2 )-bit antenna port field is included in the DCI format.

[0499] The UE may assume that the length of the antenna port field is determined based on the TDRA row indicated by the TDRA field of the received DCI format. When monitoring the DCI format, the UE should know the length of the DCI format in advance. Therefore, when the DCI format length varies based on the TDRA row indicated by the TDRA field, the UE may match the length of the DCI format with the longest DCI format length. That is, the UE may pad some bits for a shorter DCI format to match the longest DCI format length. The UE may pad some bits into the LSB of a shorter DCI format to match the longest DCI format length. Some bits may be "0".

[0500] According to an embodiment, the antenna port field indicates one or more rows of the antenna port combination table.

[0501] The UE may receive a configured new antenna port combination table from the base station, and the antenna port field may indicate a row in the antenna port combination table.

[0502] A new antenna port combination table can be defined as follows.

[0503] Each row of the new antenna port combination table has an inherent index.

[0504] Each row of the new antenna port combination table can be configured with a first index and a second index. Here, the first index can be the index of a row in the rows of the antenna port table of mapping type A, and the second index can be the index of a row in the rows of the antenna port table of mapping type B.

[0505] In case of receiving a configured new antenna port combination table, the UE may obtain a row of the antenna port table as follows.

[0506] The UE may obtain the index of the row of the antenna port combination table from the antenna port field. The UE may obtain the first index and the second index configured in the row of the antenna port combination table having the index. The UE may regard the first index as the index of the antenna port table of mapping type A and the second index as the index of the antenna port table of mapping type B. Therefore, the UE may consider that the row corresponding to the first index of the antenna port table of mapping type A has been indicated as the row of the antenna port table of mapping type A, and may consider that the row corresponding to the second index of the antenna port table of mapping type B has been indicated as the row of the antenna port table of mapping type B.

[0507] The antenna port combination table can be applicable to all TDRA rows or to a specific TDRA row.

[0508] When the antenna port combination table is configured, the UE can obtain information about the DMRS and antenna ports of the PDSCH (or PUSCH) of all TDRA rows from the antenna port combination table.

[0509] More specifically, when the TDRA row indicated by the TDRA field of the DCI format received by the UE includes only scheduling information of mapping type A, the UE can determine the row of the antenna port combination table from the antenna port field, and the UE can determine the row of the antenna port table of mapping type A based on the first index of the row of the antenna port combination table. In this case, the second index corresponding to the mapping type B that is not scheduled can be ignored.

[0510] In the case where the TDRA row indicated by the TDRA field of the DCI format received by the UE includes only scheduling information of mapping type B, the UE can determine the row of the antenna port combination table from the antenna port field, and the UE can determine the row of the antenna port table of mapping type B based on the second index of the row of the antenna port combination table. In this case, the first index corresponding to the mapping type B that is not scheduled can be ignored.

[0511] In a case where the TDRA row indicated by the TDRA field of the DCI format received by the UE includes scheduling information of mapping type A and scheduling information of mapping type B, the UE can determine the row of the antenna port combination table from the antenna port field, and the UE can determine the row of the antenna port table of mapping type A based on the first index of the row of the antenna port combination table, and determine the row of the antenna port table of mapping type B based on the second index.

[0512] Here, the antenna port table of mapping type A can be an antenna port table according to the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength) configured in mapping type A, and the antenna port table of mapping type B can be an antenna port table according to the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength) configured in mapping type B.

[0513] When the first method is used, the length of the antenna port field can be determined according to the number of rows configured in the antenna port combination table. comb When the antenna port field can be ceil(log2(N comb ))Bit.

[0514] When the antenna port combination table is configured, if a TDRA row including different mapping types is indicated, the UE can use the antenna port combination table; if a TDRA row including scheduling information with only one mapping type is indicated, the existing antenna port table (for example, an antenna port table configured according to a DMRS configured with mapping type A and an antenna port table configured according to a DMRS configured with mapping type B) can be used.

[0515] More specifically, when the TDRA row indicated by the TDRA field of the DCI format received by the UE includes only scheduling information of mapping type A, the UE can obtain the index of the row of the antenna port table determined according to the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type A from the antenna port field. The UE can obtain the antenna port information from the row of the antenna port table having the index.

[0516] In the case where the TDRA row indicated by the TDRA field of the DCI format received by the UE includes only scheduling information of mapping type B, the UE can obtain the index of the row of the antenna port table determined according to the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type B from the antenna port field. The UE can obtain the antenna port information from the row of the antenna port table with the index.

[0517] When the TDRA row indicated by the TDRA field of the DCI format received by the UE includes scheduling information of mapping type A and scheduling information of mapping type B, the UE can determine the row of the antenna port combination table from the antenna port field, and can determine the row of the antenna port table of mapping type A based on the first index of the row of the antenna port combination table, and determine the row of the antenna port table of mapping type B based on the second index.

[0518] The length of the antenna port field can be determined according to the number of rows in the antenna port table of mapping type A, the number of rows in the antenna port table of mapping type B, and the number of rows configured in the antenna port combination table. For example, when the number of rows configured in the antenna port combination table is N comb And the number of bits used to indicate the row of the antenna port combination table is X comb =ceil(log2(N comb )), the length of the antenna port field can be max{X 1 ,X 2 ,X comb Here, no matter what mapping type is included in the TDRA row indicated by the TDRA field of the DCI format, the length of the antenna port field is fixed. Additionally or optionally, the length of the antenna port field of the DCI format may also be max{X 1 ,X 2} or X comb If the TDRA row indicated by the TDRA field of the DCI format received by the UE includes only scheduling information of one mapping type, the length of the antenna port field is max{X 1 ,X 2} bits, and if the TDRA row indicated by the TDRA field of the DCI format received by the UE includes only scheduling information of one mapping type, the length of the antenna port field may be X comb Bit.

[0519] When the antenna port combination table is configured, if a TDRA row including multiple scheduling information is indicated, the UE can use the antenna port combination table, and if a TDRA row including multiple scheduling information is indicated, the UE can use the existing antenna port table (for example, an antenna port table configured according to a DMRS configured with mapping type A and / or an antenna port table configured according to a DMRS configured with mapping type B).

[0520] More specifically, when the TDRA row indicated by the TDRA field of the DCI format received by the UE includes only scheduling information of mapping type A, the UE can obtain the index of the row of the antenna port table determined according to the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type A from the antenna port field. The UE can obtain the antenna port information from the row of the antenna port table having the index.

[0521] In the case where the TDRA row indicated by the TDRA field of the DCI format received by the UE includes only one piece of scheduling information of mapping type B, the UE can obtain from the antenna port field the index of the row of the antenna port table determined according to the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength) of mapping type B. The UE can obtain the antenna port information from the antenna port table row having the index.

[0522] In a case where the TDRA row indicated by the TDRA field of the DCI format received by the UE includes multiple scheduling information, the UE can determine the row of the antenna port combination table from the antenna port field, and can determine the row of the antenna port table of mapping type A based on the first index of the row of the antenna port combination table, and determine the row of the antenna port table of mapping type B based on the second index.

[0523] The length of the antenna port field can be determined according to the number of rows in the antenna port table of mapping type A, the number of rows in the antenna port table of mapping type B, and the number of rows configured in the antenna port combination table. Assume that the number of rows configured in the antenna port combination table is N comb , and the number of bits used to indicate the rows of the antenna port combination table is X comb =ceil(log2(N comb )). The length of the Antenna Port field can be max{X 1 ,X 2 ,X comb Here, regardless of the number of scheduling information included in the TDRA row indicated by the TDRA field of the DCI format, the length of the antenna port field is fixed. Additionally or optionally, the length of the antenna port field of the DCI format may also be max{X 1 ,X 2} or Xcomb If the TDRA row indicated by the TDRA field of the DCI format received by the UE includes only one piece of scheduling information, the length of the antenna port field can be max{X 1 ,X 2} bits, and if the TDRA line indicated by the TDRA field of the DCI format received by the UE only includes multiple scheduling information, the length of the antenna port field can be X comb Bit.

[0524] According to an embodiment, the UE may receive an antenna port combination table indicating the configuration of the antenna port of each level of PUSCH from the base station. More specifically, the UE may receive a PUSCH antenna port combination table configured at level 1, the UE may receive a PUSCH antenna port combination table configured at level 2, the UE may receive a PUSCH antenna port combination table configured at level 3, and the UE may receive a PUSCH antenna port combination table configured at level 4. Here, the first index of the antenna port combination table of level r (r=1, 2, 3, 4) may indicate a row of the antenna port table corresponding to the DMRS configuration of level r (r=1, 2, 3, 4) and mapping type A, and the second index may indicate a row of the antenna port table corresponding to the DMRS configuration of level r (r=1, 2, 3, 4) and mapping type B.

[0525] The UE may receive a configured antenna port combination table from the base station, the antenna port combination table being used to indicate the antenna port of the PDSCH for each enabled codeword number. More specifically, the UE may receive a configured antenna port combination table for the PDSCH with the enabled codeword numbered 1 (hereinafter referred to as the first table) and a configured antenna port combination table for the PDSCH with the enabled codeword numbered 2 (hereinafter referred to as the second table). When the DCI-scheduled PDSCH received by the UE includes an enabled codeword, the first table may be used. That is, the first index of the first table may indicate a row of the antenna port table corresponding to the DMRS configuration of mapping type A, and DMRS information (DMRS port, number of DMRS symbols, and / or number of CDM groups without data) may be obtained when the number of the enabled codeword in the row is 1. The second index of the first table may indicate a row of the antenna port table corresponding to the DMRS configuration of mapping type B, and DMRS information (DMRS port, number of DMRS symbols, and / or number of CDM groups without data) may be obtained when the number of the enabled codeword in the row is 1. Similarly, when the PDSCH scheduled by the DCI received by the UE includes two enabled codewords, the second table can be used. That is, the first index of the second table can indicate the row of the antenna port table corresponding to the DMRS configuration of mapping type A, and the DMRS information (DMRS port, number of DMRS symbols and / or number of CDM groups without data) can be obtained when the number of the enabled codewords in the row is 1. The second index of the second table can indicate the row of the antenna port table corresponding to the DMRS configuration of mapping type B, and the DMRS information (DMRS port, number of DMRS symbols and / or number of CDM groups without data) can be obtained when the number of the enabled codewords in the row is 1.

[0526] According to an embodiment, an antenna port field value indicating the same DMRS information may be expected.

[0527] When the DCI format received by the UE indicates a TDRA row including different mapping types, the UE may expect the antenna port field value indicating the same DMRS information even if each mapping type uses a different antenna port table. Here, the same DMRS information includes the same DMRS port, the same number of DMRS symbols (number of front-end symbols), or the same number of DMRSCDM groups without data. If the DCI format to be transmitted indicates that the TDRA row includes different mapping types and each mapping type uses a different antenna port table, the base station does not indicate the antenna port field value representing the same DMRS information.

[0528] The same DMRS information may include at least one of the same DMRS port, the same number of DMRS symbols (front-load symbol number), or the same number of DMRS CDM groups without data. For example, the same DMRS information may correspond to the case of the same DMRS port.

[0529] In other words, when the DCI format received by the UE indicates a TDRA row including different mapping types and each mapping type uses a different antenna port table, the UE does not expect the antenna port field value indicating other DMRS information. If the DCI format to be transmitted indicates a TDRA row of different mapping types and each mapping type uses a different antenna port table, the base station does not indicate the antenna port field value representing other DMRS information.

[0530] Even if different antenna port tables are used for different mapping types, rows with the same index in the two antenna port tables can have the same DMRS port. For example, when Table 41 (in the case of dmrs-Type=1, maxLength=2) and Table 43 (in the case of dmrs-Type=2, maxLength=1) are configured for PDSCH mapping types A and B, respectively, when only one codeword is enabled, rows 0 to 10 of the two tables can be determined to have the same DMRS port, the same number of DMRS symbols (number of front-end symbols), and the same number of DMRS CDM groups without data. Therefore, when one of the rows is indicated, the UE can determine the DMRS and antenna port information for mapping type A and mapping type B.

[0531] According to an embodiment, the antenna port field value may be applied to antenna port tables of two mapping types.

[0532] When a TDRA row including different mapping types is indicated, the UE may apply the value of the antenna port field to the antenna port table of both mapping types.

[0533] The UE may expect the value of the antenna port field to indicate a valid row (non-reserved row) in the antenna port table of the two mapping types. That is, when the value of the antenna port field is indicated as an invalid value in any antenna port table of the two mapping types, the UE may determine it as an error case and ignore the DCI format including the antenna port field.

[0534] When the UE receives an indication of an invalid row (reserved row) in one of the antenna port tables of two mapping types from the value of the antenna port field, the UE may assume that scheduling information corresponding to the mapping type using the antenna port table is not scheduled.

[0535] For example, when the TDRA row indicated by the TDRA field of the DCI format received by the UE includes scheduling information of mapping type A and scheduling information of mapping type B, the UE can determine the row by applying the value indicated by the antenna port field to each antenna port table. That is, the UE can determine the DMRS information and antenna port information of mapping type A by applying the value indicated by the antenna port field to the antenna port table of mapping type A, and can determine the DMRS information and antenna port information of mapping type B by applying the value indicated by the antenna port field to the antenna port table of mapping type B. If the row selected from the antenna port table of mapping type A is a valid row (non-reserved row) and the row selected from the antenna port table of mapping type B is an invalid row (reserved row), the UE can receive (or send) the PDSCH (or PUSCH) corresponding to the scheduling information of mapping type A. However, the UE may not receive (or send) the PDSCH (or PUSCH) corresponding to the scheduling information of mapping type B.

[0536] When the UE indicates a TDRA row including different mapping types for the received DCI format, the UE may interpret the value of the antenna port field as one of the valid rows of the antenna port table for the mapping type according to a predetermined rule.

[0537] Here, the valid row in the antenna port table may be a non-reserved row.

[0538] When Table 41 (in the case of dmrs-Type=1, maxLength=2) and Table 43 (in the case of dmrs-Type=2, maxLength=1) are configured as PDSCH mapping types A and B, and only one codeword is enabled, and the antenna port field indicates a row in rows 0 to 23, the row corresponds to a valid value in the two antenna port tables. That is, the row corresponds to a non-reserved row in the two antenna port tables. However, when the antenna port field indicates a row in rows 24 to 30, the row corresponds to a valid value in one antenna port table (dmrs-Type=1, maxLength=2), but the row corresponds to an invalid value (reserved) in another antenna port table (dmrs-Type=1, maxLength=2). Therefore, when a TDRA row including different mapping types is indicated, rows 24 to 30 cannot be indicated in the antenna port field.

[0539] To solve this problem, the following method can be used.

[0540] The value indicated in the antenna port field may be reinterpreted based on the number of valid rows of the antenna port table to select a row in the antenna port table. For example, the row of the antenna port table may be selected based on a value obtained by performing a modulo calculation on the value indicated in the antenna port field and the number of valid rows of the antenna port table.

[0541] For example, when Table 41 (in the case of dmrs-Type = 1, maxLength = 2) and Table 43 (in the case of dmrs-Type = 2, maxLength = 1) are configured as PDSCH mapping types A and B, it is assumed that only one codeword is enabled. In addition, it is assumed that the value indicated in the antenna port field is 25. As described above, in the antenna port table (dmrs-Type = 2, maxLength = 1), row 25 is an invalid value (reserved). To solve this problem, the UE can obtain 25mod24=1 by performing a modular multiplication calculation on the value 25 indicated in the antenna port field and the valid row number 24 in the antenna port table, and the DMRS information and antenna port information can be obtained from row 1 of the antenna port table.

[0542] If the value indicated in the antenna port field indicates a valid value in one antenna port table but indicates an invalid value (reserved) in another antenna port table, the UE may interpret this as one of the following valid values.

[0543] The UE may interpret this situation as a specific row with valid values ​​in the antenna port table indicating invalid values ​​(reserved). Here, the specific row may be row 0. For another example, the base station may configure the specific row through a higher layer.

[0544] The UE may interpret this situation as a specific row of a valid value of the antenna port table with a valid value indicated. Here, the index of the specific row may be the value indicated in the antenna port field. For example, row 25 is an invalid value (reserved) in the antenna port table (dmrs-Type=2, maxLength=1). In this case, row 25 of the antenna port table (dmrs-Type=1, maxLength=2) may be used.

[0545] Although the above describes each embodiment separately for the sake of convenience, the present disclosure can also be implemented by combining the embodiments. In addition, in the embodiments of the present disclosure, for the sake of convenience, the operation of the UE is mainly described, but the technical features of the embodiments of the present disclosure described as the operation of the UE can also be applied to the configuration of the base station and the operation of the base station.

[0546] The UE may receive multiple pieces of scheduling information configured in one TDRA row according to the multi-PUSCH scheduling configuration, and each of the multiple pieces of scheduling information may have a SLIV and a mapping type. Therefore, the UE may receive an indication of a TDRA row including scheduling information with different mapping types through one DCI.

[0547] Different DMRS configuration information can be configured as different mapping types. In the case of different DMRS configuration information, different antenna port tables can be configured for DMRS port indication. Therefore, the UE can configure different DMRS ports for PUSCHs of different mapping types according to different antenna port tables.

[0548] For example, assume the following DMRS configuration configured as mapping type A.

[0549] -DMRS type (dmrs-Type) = 1

[0550] -DMRS maximum length (maxLength) = 1

[0551] In addition, assume the following DMRS configuration configured as mapping type B.

[0552] -DMRS type (dmrs-Type) = 1

[0553] -DMRS maximum length (maxLength) = 2

[0554] In addition, it is assumed that the rank is 2. The rank is information that the UE can obtain through the DCI format. Therefore, when determining the DMRS port to transmit the PUSCH of mapping type A, the UE can use a row in Table 23 (corresponding to the non-reserved rows of indexes 0, 1, 2, and 3), and when determining the DMRS port to transmit the PUSCH of mapping type B, the UE can use a row in Table 27 (corresponding to the non-reserved rows of indexes 0, 1,..., 9). For example, assume that the base station indicates that DMRS ports {0,1} are used to transmit the PUSCH of mapping type A, and DMRS ports {0,2} are used to transmit the PUSCH of mapping type B. In this case, the UE can recognize that different DMRS ports are mapped to different mapping types for PUSCH transmission. Therefore, the DMRS port used to transmit the PUSCH of mapping type A and the DMRS port used to transmit the PUSCH of mapping type B in the UE can be different from each other.

[0555] The index of the DMRS port used for PTRS transmission should be indicated to the UE. The DCI format for scheduling PUSCH may include a PTRS-DMRS association field for indicating the DMRS port used for PTRS transmission. As described above, the PTRS-DMRS association field may indicate one of the antenna ports of the scheduled PUSCH, and when transmitting PUSCH, PTRS may be transmitted through the indicated antenna port.

[0556] As described above, the PTRS-DMRS association field can be indicated as the 1st scheduled DMRS port, the 2nd scheduled DMRS port, the 3rd scheduled DMRS port and / or the 4th scheduled DMRS port according to Table 49-1. Assume that the 2nd scheduled DMRS port is indicated as the current PTRS-DMRS association field. In this case, according to the previous example, in the case of mapping type A, PUSCH is transmitted through DMRS port {0,1}, and therefore the PTRS antenna port is DMRS port 1, and in the case of mapping type B, PUSCH is transmitted through DMRS port {0,2}, and therefore the PTRS antenna port is DMRS port 2. Therefore, in the case of different mapping types, different DMRS ports can be used for PTRS transmission.

[0557] The base station should select the DMRS port with the largest received signal power among the DMRS ports as the PTRS antenna port to obtain the highest performance. This is why the base station indicates one DMRS port in the PTRS-DMRS association field of the DCI format. However, in the case of different mapping types, since the DMRS port may be different depending on the mapping type, the base station may not be able to simultaneously indicate to the UE the DMRS port with the largest received signal power in two different mapping types. For example, in the above example, the UE can transmit PTRS through DMRS port 1 of the PUSCH of mapping type A and transmit PTRS through DMRS port 2 of the PUSCH of mapping type B. In this case, assuming that the received signal power of each DMRS port is DMRS port 1>DMRS port 0>DMRS port 2, the base station should indicate that PTRS is transmitted through DMRS port 1 of the PUSCH of mapping type A and PTRS is transmitted through DMRS port 0 of the PUSCH of mapping type B. However, the DCI format does not have to support these indications. The following describes a method for determining PTRS antenna ports for different mapping types.

[0558] The following will introduce one or more restrictions on the same DMRS port and the same DMRS port indication.

[0559] The UE may expect mapping type A and mapping type B to use the same antenna port table. Here, in order to use the same antenna port table, the UE may receive the same DMRS type (dmrs-Type) and DMRS maximum length (maxLength) configured by the higher layer. The base station may configure the same DMRS type (dmrs-Type) and DMRS maximum length (maxLength) for the UE. In addition, the UE may expect that the DMRS ports indicating mapping type A and mapping type B are the same.

[0560] When a TDRA table including TDRA rows of different mapping types is configured, the UE may expect mapping type A and mapping type B to use the same antenna port table. That is, when a TDRA table including TDRA rows containing different mapping types is configured, the UE may expect the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B to be the same.

[0561] When the base station is to configure a TDRA table including TDRA rows containing different mapping types for the UE, the base station should configure the TDRA table for the UE so that mapping type A and mapping type B use the same antenna port table. That is, when the base station is to configure a TDRA table including TDRA rows containing different mapping types for the UE, the base station should configure the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B for the UE to be the same.

[0562] When a TDRA table that does not include a TDRA row containing different mapping types is configured, the antenna port tables of mapping type A and mapping type B of the UE can be the same or different. That is, when a TDRA table that does not include a TDRA row containing different mapping types is configured, the UE can expect the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B to be the same or different. In other words, when a TDRA table that does not include a TDRA row containing different mapping types is configured in the UE, there is no configuration restriction on the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B.

[0563] When the base station is to configure a TDRA table for the UE that does not include a TDRA row containing different mapping types, the base station can configure the TDRA table for the UE so that mapping type A and mapping type B use the same or different antenna port tables. That is, when the base station is to configure a TDRA table for the UE that does not include a TDRA row containing different mapping types, the base station can configure the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B to be the same or different for the UE. In other words, when the base station is to configure a TDRA table for the UE that does not include a TDRA row containing different mapping types, the base station can freely configure the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B for the UE without being restricted by its configuration.

[0564] When at least one row in the TDRA table configured for the UE corresponds to a TDRA row including different mapping types, the DMRS type (dmrs-Type) and DMRS maximum length (maxLength) of mapping type A and mapping type B should be the same. This also affects other TDRA rows in the TDRA table.

[0565] For example, assuming that the first TDRA row in the TDRA table includes scheduling information for mapping type A and the second TDRA row includes scheduling information for mapping type B, the base station can configure different DMRS types (dmrs-Type) or DMRS maximum lengths (maxLength) for mapping type A and mapping type B in the UE. Therefore, the PUSCH scheduled in the first TDRA row and the PUSCH scheduled in the second TDRA row can have DMRSs with different DMRS types (dmrs-Type) or DMRS maximum lengths (maxLength). However, the PUSCH scheduled in the first TDRA row and the PUSCH scheduled in the second TDRA row can always have DMRSs with the same DMRS type (dmrs-Type) or DMRS maximum length (maxLength). This may make it difficult for the base station to configure a DMRS suitable for the mapping type.

[0566] To solve this problem, the following embodiments may be considered.

[0567] The UE may additionally receive a DMRS configuration only for TDRA rows including different mapping types through a higher layer signal (e.g., an RRC signal). The DMRS configuration may include at least a DMRS type (dmrs-Type) and a DMRS maximum length (maxLength). The UE may receive the following three DMRS configurations:

[0568] - DMRS configuration type 1: DMRS configuration including only TDRA rows of scheduling information mapping type A

[0569] - Second DMRS configuration: DMRS configuration including only TDRA rows of scheduling information mapping type B

[0570] - DMRS configuration type 3: DMRS configuration of TDRA rows including scheduling information of type A and scheduling information of type B

[0571] For reference, the first DMRS configuration may be a DMRS configuration configured with mapping type A (dmrs-UplinkForPUSCH-MappingTypeA), the second DMRS configuration may be a DMRS configuration configured with mapping type B (dmrs-UplinkForPUSCH-MappingTypeB), and the third DMRS configuration may be a newly configured DMRS configuration.

[0572] After receiving the DCI format, the UE may perform the following operations.

[0573] The UE may obtain the index of the TDRA row from the TDRA field of the received DCI format. The UE may obtain the scheduling information and the mapping type of the scheduling information included in the TDRA row.

[0574] If the TDRA row includes only scheduling information of mapping type A, the UE may assume the first DMRS configuration. Therefore, the UE may determine the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength) according to the first DMRS configuration, and may use the antenna port table according to the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength).

[0575] When the TDRA row includes only scheduling information of mapping type B, the UE may assume the second DMRS configuration. Therefore, the UE may determine the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength) according to the second DMRS configuration, and may use the antenna port table according to the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength).

[0576] When the TDRA row includes scheduling information for mapping type A and scheduling information for mapping type B, the UE can assume the third DMRS configuration. Therefore, the UE can determine the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength) according to the third DMRS configuration, and can use the antenna port table according to the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength). Here, the mapping type A and mapping type B scheduled in the TDRA row use the same antenna port table. Therefore, the DMRS configurations of mapping type A and mapping type B can have the same DMRS port, the same number of DMRS symbols, and the same number of CDM groups without data. However, according to mapping type A and mapping type B, the position of the actually transmitted DMRS can be determined in different ways.

[0577] The UE may interpret the antenna port field based on the antenna port table.

[0578] The UE may obtain the DMRS port from the antenna port table according to the value of the antenna port field. For a PUSCH of mapping type A and a PUSCH of mapping type B, the DMRS port may be the same.

[0579] The UE may receive an indication of using one of the DMRS ports as a PTRS antenna port from the PTRS-DMRS association field of the received DCI format. Since the DMRS ports of the PUSCH of mapping type A and the PUSCH of mapping type B are the same, the PTRS antenna ports are also the same.

[0580] The third DMRS configuration may be the same as the second DMRS configuration or one of the first DMRS configurations. That is, after configuring the third DMRS configuration, the UE may configure a configuration that is the same as the first DMRS configuration or one of the second DMRS configurations, but may not configure a configuration that is different from the first DMRS configuration and the second DMRS configuration. With this restriction, the UE may configure at most two different DMRS configurations.

[0581] The third DMRS configuration requires a new higher layer signal (eg, RRC signal). This may cause the design and overhead of the higher layer signal. The following will introduce a method to improve this problem.

[0582] The UE may not receive a higher layer signal configured for the third DMRS configuration. Instead, the third DMRS configuration may be determined.

[0583] The UE may assume that the third DMRS configuration is always the same as the first DMRS configuration. That is, the UE may use the DMRS configuration for the TDRA row including only scheduling information of mapping type A as the third DMRS configuration. In other words, the UE may determine the DMRS of the PUSCH of mapping type B, which is scheduled by the TDRA rows including different mapping types, by using the DMRS configuration of mapping type A, i.e., the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength). Therefore, for the PUSCH of mapping type B scheduled by the TDRA rows including different mapping types, the UE may use the antenna port table of mapping type A. Here, the position of the DMRS of mapping type B may be according to the scheme of mapping type B.

[0584] The UE may assume that the third DMRS configuration is always the same as the second DMRS configuration. That is, the UE may use the DMRS configuration for the TDRA row including only scheduling information of mapping type B as the third DMRS configuration. In other words, the UE may determine the DMRS of the PUSCH of mapping type A by using the DMRS configuration of mapping type B (i.e., DMRS type (dmrs-Type) or DMRS maximum length (maxLength)), which is scheduled by TDRA rows including different mapping types. Therefore, for the PUSCH of mapping type A scheduled by TDRA rows including different mapping types, the UE may use the antenna port table of mapping type B. Here, the position of the DMRS of mapping type A may follow the scheme of mapping type A.

[0585] The UE may assume that the third DMRS configuration is the same as the first DMRS configuration or the second DMRS configuration based on the mapping type of one piece of scheduling information in the scheduling information scheduled by the TDRA row including different mapping types.

[0586] For example, the UE may assume that the third DMRS configuration is the same as the first DMRS configuration or the second DMRS configuration based on the mapping type of the earliest scheduling information among multiple pieces of scheduling information including TDRA row scheduling of different mapping types. When the mapping type of the earliest scheduling information is mapping type A, the UE may assume that the DMRS configuration of mapping type A (i.e., the first DMRS configuration) is the same as the third DMRS configuration. When the mapping type of the earliest scheduling information is mapping type B, the UE may assume that the DMRS configuration of mapping type B (i.e., the second DMRS configuration) is the same as the third DMRS configuration.

[0587] Here, the earliest scheduling information may be replaced by the latest scheduling information. The earliest scheduling information may be the earliest scheduling information in time.

[0588] It can be assumed that the UE receives the same DMRS type (dmrs-Type) or the same configured DMRS maximum length (maxLength). However, the above conditions may be modified and applied as follows.

[0589] The UE may expect to receive the same DMRS type (dmrs-Type) configured for different mapping types. Here, different DMRS maximum lengths (maxLength) may be configured for different mapping types. According to this condition change, the UE may use different DMRS maximum lengths in different mapping types. Therefore, the base station may indicate to the UE the DMRS length suitable for the mapping type. However, the UE may expect to receive indications of the same DMRS port for mapping type A and mapping type B.

[0590] The UE may expect to receive the same DMRS maximum length (maxLength) configured for different mapping types. Here, different DMRS types (dmrs-Type) may be set for different mapping types. According to this condition change, the UE may use different DMRS types (dmrs-Type) in different mapping types. Therefore, the base station may configure the DMRS type suitable for the mapping type for the UE. However, the UE may expect to receive an indication of the same DMRS port for mapping type A and mapping type B.

[0591] The conditions of the DMRS type (dmrs-Type) and the DMRS maximum length (maxLength) of the UE have been described, but the following conditions may be added.

[0592] In different mapping types, in addition to the same first DMRS (first DMRS or frontload DMRS), the UE may also expect to configure additional DMRS (dmrs-AdditionalPosition).

[0593] There may be restrictions on the DMRS configuration of mapping type A and mapping type B. For example, the same DMRS type (dmrs-Type) or the same DMRS maximum length (maxLength) should be configured for mapping type A and mapping type B. However, if there are no such restrictions, the UE can always expect to indicate the same DMRS port.

[0594] The UE may expect mapping type A and mapping type B to be indicated by the same DMRS port. Here, the antenna port table for the PUSCH of mapping type A and the antenna port table for the PUSCH of mapping type B may be the same or different. That is, the DMRS type (dmrs-Type) and the DMRS maximum length (maxLength) configured by the base station to the UE may be the same or different. Therefore, the antenna port table corresponding to mapping type A and the antenna port table corresponding to mapping type B may be the same or different. However, when a TDRA row including different mapping types is indicated in the received DCI format, the UE may expect that the DMRS port of mapping type A and the DMRS port of mapping type B determined according to the antenna port field of the DCI format are always the same.

[0595] The base station can freely configure the DMRS configuration of mapping type A and mapping type B for the UE. The DMRS configuration may include a DMRS type (dmrs-Type) or a DMRS maximum length (maxLength). Here, free configuration can be understood as the DMRS configuration of mapping type A can be independent of the DMRS configuration of mapping type B. When the base station provides an indication of a TDRA row of different mapping types including a DCI format to the UE, the base station shall indicate the value of the antenna port field so that the DMRS port of mapping type A and the DMRS port of mapping type B indicated in the antenna port field of the DCI format are the same.

[0596] Multiple PUSCH scheduling will impose restrictions on the same mapping type.

[0597] When the UE has an antenna port table corresponding to mapping type A that is different from the antenna port table corresponding to mapping type B, the UE may expect the same mapping type of the scheduling information included in the TDRA row. When the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type A of the UE is different from the DMRS type (dmrs-Type) or maximum length (maxLength) of mapping type B, the UE may expect the same mapping type of the scheduling information included in the TDRA row.

[0598] In addition, when TDRA rows including different mapping types are configured in the TDRA table, the UE may assume that the antenna port table corresponding to mapping type A and the antenna port table corresponding to mapping type B are the same. When TDRA rows including different mapping types are configured in the TDRA table, the UE may assume that the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type A and the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type B are the same as each other.

[0599] That is, the UE may be configured not to expect that the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength) of mapping type A is different from the DMRS type (dmrs-Type) or the DMRS maximum length (maxLength) of mapping type B and that TDRA rows including different mapping types are configured in the TDRA table. The UE may be configured not to expect that the antenna port table corresponding to mapping type A and the antenna port table corresponding to mapping type B are different from each other and that TDRA rows including different mapping types are configured in the TDRA table.

[0600] When the base station configures the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type A and the DMRS type (dmrs-Type) or maximum length (maxLength) of mapping type B for the UE, the base station can configure the mapping type of the scheduling information included in the TDRA row to be always the same.

[0601] When the base station configures a TDRA table including TDRA rows of different mapping types for the UE, the base station shall configure the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type A and the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type B to be the same.

[0602] That is, the base station can configure the DMRS type (dmrs-Type) or DMRS maximum length (maxLength) of mapping type A to be different from the DMRS type (dmrs-Type) or maximum length (maxLength) of mapping type B, and can be configured to include TDRA rows including different mapping types in the TDRA table.

[0603] Since the PUSCH scheduled in the TDRA field of the DCI format received by the UE always has the same mapping type, the position and length of the DMRS can be determined based on the DMRS configuration of the mapping type. In addition, the UE can determine an antenna port table based on the DMRS configuration of the mapping type. A row of an antenna port table can be indicated in the antenna port field.

[0604] Two mapping types of PTRS antenna ports may be indicated in the PTRS-DMRS association field.

[0605] A DCI format for scheduling a PUSCH received by a UE may include a DCI field for indicating a PTRS antenna port for each mapping type.

[0606] More specifically, certain bits of the PTRS-DMRS association field may indicate one of the DMRS ports of mapping type A as a PTRS antenna port, and the remaining bits of the PTRS-DMRS association field may indicate one of the DMRS ports of mapping type B as a PTRS antenna port.

[0607] When indicating to the UE a TDRA row including different mapping types, the PTRS-DMRS association field of the DCI format may be configured as 4 bits. Here, the 2 MSB bits may indicate one of the DMRS ports of mapping type A as a PTRS antenna port, and the 2 LSB bits may indicate one of the DMRS ports of mapping type B as a PTRS antenna port.

[0608] When indicating a TDRA row of a mapping type to the UE, the PTRS-DMRS association field of the DCI format may be configured with 2 bits. These 2 bits may indicate one of the DMRS ports of the mapping type included in the TDRA row as a PTRS antenna port.

[0609] For reference, in the above example, when the UE schedules PUSCHs of different mapping types for the TDRA row of the DCI format and when scheduling PUSCHs of one mapping type, the number of bits of the PTRS-DMRS association field required by the UE in the DCI format may be different. Therefore, the following operations may be performed to match the number of bits.

[0610] If at least one TDRA row in the TDRA table configured for the UE includes different mapping types, the UE may always expect 4 bits as the PTRS-DMRS association in the DCI format. When a TDRA row of one mapping type is indicated to the UE, 2 bits in the 4-bit PTRS-DMRS association field of the DCI format may indicate that one of the DMRS ports of the mapping type included in the TDRA row is a PTRS antenna port. 2 of the 4 bits may be selected as follows.

[0611] One of the DMRS ports of one mapping type included in the TDRA row may use the 2 MSB bits as a PTRS antenna port. In addition, the 2 LSB bits may not be used.

[0612] One of the DMRS ports of one mapping type included in the TDRA row may use the 2 LSB bits as a PTRS antenna port. In addition, the 2 MSB bits may not be used.

[0613] 2 MSB bits or 2 LSB bits may be used according to a mapping type included in the TDRA row. If a mapping type included in the TDRA row is mapping type A, one of the DMRS ports of the mapping type may be used as a PTRS antenna port by using 2 MSB bits. If a mapping type included in the TDRA row is mapping type B, one of the DMRS ports of the mapping type may be used as a PTRS antenna port by using 2 LSB bits.

[0614] If the UE is indicated that the TDRA row includes different mapping types and the DMRS ports of different mapping types are different, the PTRS-DMRS association field of the DCI format can be configured as 4 bits. Here, the 2 MSB bits can indicate that one of the DMRS ports of mapping type A is a PTRS antenna port, and the 2 LSB bits can indicate that one of the DMRS ports of mapping type B is a PTRS antenna port.

[0615] When indicating a TDRA row as a mapping type to the UE or when the DMRS ports of different mapping types are the same, even if a TDRA row including different mapping types is indicated, the PTRS-DMRS association field of the DCI format can be configured as 2 bits. These 2 bits can indicate that one of the DMRS ports of the mapping type included in the TDRA row is a PTRS antenna port.

[0616] For reference, in the above example, when the UE schedules PUSCHs of different mapping types for the TDRA row of the DCI format and when scheduling PUSCHs of one mapping type, the number of bits of the PTRS-DMRS association field required by the UE in the DCI format may be different. Therefore, the following operations may be performed to match the number of bits.

[0617] If at least one TDRA row in the TDRA table configured for the UE includes different mapping types and the DMRS ports of different mapping types can be indicated in different ways, the UE can always expect 4 bits as the PTRS-DMRS association in the DCI format. When a TDRA row of one mapping type is indicated to the UE or when the DMRS ports of different mapping types are the same, even if a TDRA row including different mapping types is indicated, 2 of the 4 bits of the PTRS-DMRS association field in the DCI format can indicate one of the DMRS ports of the mapping type included in the TDRA row as a PTRS antenna port. 2 bits can be selected from the 4 bits based on the above method.

[0618] That is, the conditions for the presence of a 4-bit PTRS-DMRS association field in the DCI format are as follows:

[0619] - Condition 1: At least one row in the TDRA table includes different mapping types, or

[0620] - Condition 2: At least one row in the TDRA table includes different mapping types and different DMRS ports may indicate different mapping types.

[0621] For reference, if the UE wishes to always indicate the same DMRS port, there is a 4-bit PTRS-DMRS association field in the DCI format when using condition 1. However, when using condition 2, there is a 2-bit PTRS-DMRS association field in the DCI format.

[0622] Different bits for indicating PTRS antenna ports of different mapping types may be included in one PTRS-DMRS association field, but a new DCI field may be defined. That is, the 4-bit PTRS-DMRS association field may be represented by the first 2-bit PTRS-DMRS association field and the second 2-bit PTRS-DMRS association field. Preferably, the first 2-bit PTRS-DMRS association field may be the 2 MSB bits of the above-mentioned 4-bit PTRS-DMRS association field, and the second 2-bit PTRS-DMRS association field may be the 2 LSB bits of the above-mentioned 4-bit PTRS-DMRS association field.

[0623] The PTRS-DMRS association field may indicate one or more DMRS ports that are co-scheduled for both mapping types.

[0624] The UE may receive an indication of one or more commonly selected DMRS ports from the PTRS-DMRS association field among DMRS ports of different mapping types. Here, the PTRS-DMRS association field may be 2 bits.

[0625] For example, assume that the UE has received {3, 4, 5} as the DMRS port of mapping type A, and {2, 3, 5} as the DMRS port of mapping type B. Here, mapping type A corresponds to the case where the DMRS type (dmrs-Type) is 2, the DMRS maximum length (maxLength) is 2, the level is 3, and the row corresponding to the value 2 in the antenna port table is indicated. Mapping type B corresponds to the case where the DMRS type (dmrs-Type) is 1, the DMRS maximum length (maxLength) is 2, the level is 3, and the row corresponding to the value 2 in the antenna port table is indicated.

[0626] The UE may generate a co-scheduled DMRS port by collecting the DMRS ports commonly included between the DMRS ports of mapping type A and the DMRS ports of mapping type B. That is, between the DMRS ports {3, 4, 5} in mapping type A and the DMRS ports {2, 3, 5} in mapping type B, the commonly included DMRS ports {3, 5} may be generated as co-scheduled DMRS ports.

[0627] The UE may receive an indication of one of the co-scheduled DMRS ports in the PTRS-DMRS association field, and may perform PTRS transmission using the DMRS port. The PTRS-DMRS association field may indicate a value of one of "the 1st co-scheduled DMRS port", "the 2nd co-scheduled DMRS port", "the 3rd co-scheduled DMRS port", and "the 4th co-scheduled DMRS port". Here, the DMRS ports used for PTRS transmission may be used in ascending order of the values ​​indicated by the PTRS-DMRS association field. For example, when the co-scheduled DMRS ports are {3,5} and the PTRS-DMRS association field indicates "the 1st co-scheduled DMRS port", the UE may use DMRS port 3 as the antenna port for PTRS transmission. When the PTRS-DMRS association field indicates "the 2nd co-scheduled DMRS port", the UE may use DMRS port 5 as the antenna port for PTRS transmission.

[0628] Therefore, the DMRS port with the highest received signal power may be included in two different mapping types. That is, when the base station schedules a PUSCH of mapping type A and a PUSCH of mapping type B to the UE, it may not be a correct operation to schedule the DMRS port with the highest received power for one mapping type and not schedule the DMRS port with the highest received power for other mapping types. Therefore, at least one DMRS port co-scheduled for two different mapping types may have the maximum received signal power, and one DMRS port of the at least one DMRS port may be used as an antenna port for PTRS transmission.

[0629] However, the above assumption may not always be valid. Therefore, as described below, the DMRS port with the maximum received power may belong to only one mapping type.

[0630] The PTRS-DMRS association field may indicate one or more DMRS ports scheduled for both mapping types.

[0631] The UE may receive an indication of one or more DMRS ports obtained by collecting all DMRS ports of different mapping types from the PTRS-DMRS association field. Here, the PTRS-DMRS association field may be greater than 2 bits. For example, the PTRS-DMRS association field may be 3 bits.

[0632] For example, it is assumed that the UE has received {3, 4, 5} as the DMRS port of mapping type A, and {2, 3, 6} as the DMRS port of mapping type B. Here, mapping type A corresponds to a DMRS type (dmrs-Type) of 2, a DMRS maximum length (maxLength) of 2, a level of 3, and indicates a row corresponding to a value of 2 in the antenna port table. Mapping type B corresponds to a DMRS type (dmrs-Type) of 1, a DMRS maximum length (maxLength) of 2, a level of 3, and indicates a row corresponding to a value of 2 in the antenna port table.

[0633] The UE may generate all scheduled DMRS ports by collecting both DMRS ports of mapping type A and DMRS ports of mapping type B. That is, the UE may simultaneously collect DMRS ports {3, 4, 5} of mapping type A and DMRS ports {2, 3, 6} of mapping type B, and generate all DMRS ports {3, 4, 5, 6} as all scheduled DMRS ports.

[0634] The UE may receive an indication of one DMRS port among all scheduled DMRS ports in the PTRS-DMRS association field, and may use the DMRS port to perform PTRS transmission. The PTRS-DMRS association field may indicate a value of "the 1st all scheduled DMRS port", "the 2nd all scheduled DMRS port", "the 3rd all scheduled DMRS port", "the 4th all scheduled DMRS port", "the 5th all scheduled DMRS port", "the 6th all scheduled DMRS port", "the 7th all scheduled DMRS port", and "the 8th all scheduled DMRS port". Here, the DMRS ports used for PTRS transmission may be used in ascending order of the value indicated by the PTRS-DMRS association field. For example, when all scheduled DMRS ports are {3, 4, 5, 6} and the PTRS-DMRS association field indicates "the 1st all scheduled DMRS port", the UE may use DMRS port 3 as the antenna port for PTRS transmission. When the PTRS-DMRS Association field indicates "2nd all scheduled DMRS ports", the UE may use DMRS port 4 as the antenna port for PTRS transmission. When the PTRS-DMRS Association field indicates "3rd all scheduled DMRS ports", the UE may use DMRS port 5 as the antenna port for PTRS transmission. When the PTRS-DMRS Association field indicates "4th all scheduled DMRS ports", the UE may use DMRS port 6 as the antenna port for PTRS transmission.

[0635] The PTRS-DMRS association field may directly indicate the index of the DMRS antenna port.

[0636] The UE may have received an indication of one of the DMRS ports scheduled for different mapping types from the PTRS-DMRS association field, and may have used a DMRS port to perform PTRS transmission based on the indication. Regardless of the scheduling, the UE may be instructed to use one of the possible DMRS ports. That is, the PTRS-DMRS association field may indicate the index of a DMRS port.

[0637] Here, the DMRS ports that can be indicated may be all DMRS ports available according to the DMRS type (dmrs-Type). For example, when 1 is configured as the DMRS type (dmrs-type), the available DMRS ports may be DMRS ports 0 to 7. When 2 is configured as the DMRS type (dmrs-type), the available DMRS ports may be DMRS ports 0 to 11. When DMRS ports 1 and 2 are simultaneously configured as DMRS types (dmrs-type) of different mapping types, the available DMRS ports may be DMRS ports 0 to 11. The PTRS-DMRS association field may indicate the index of one of the available DMRS ports.

[0638] Here, the DMRS ports that can be indicated may be all DMRS ports available according to the DMRS type (dmrs-Type) and the DMRS maximum length (maxLength). When 1 is configured as the DMRS type (dmrs-type) and the DMRS maximum length is 1, the available DMRS ports may be DMRS ports 0 to 3. When 1 is configured as the DMRS type (dmrs-type) and the DMRS maximum length is 2, the available DMRS ports may be DMRS ports 0 to 7. When 2 is configured as the DMRS type (dmrs-type) and the DMRS maximum length is 1, the available DMRS ports may be DMRS ports 0 to 5. When 2 is configured as the DMRS type (dmrs-type) and the DMRS maximum length is 2, the available DMRS ports may be DMRS ports 0 to 11. When the DMRS type (dmrs-type) or the DMRS maximum length is configured for different mapping types, each configured maximum DMRS port may be an available DMRS port.

[0639] Here, the DMRS port that can be indicated may be a DMRS port that is part of the DMRS configuration. A part of the DMRS ports may be configured through a separate higher layer signal.

[0640] The UE may receive an indication of one of the available DMRS ports from the PTRS-DMRS association field and may perform PTRS transmission using the DMRS port. The PTRS-DMRS association field may indicate a value of one of "DMRS port 0", "DMRS port 1" and / or "DMRS port 2". Here, the order of DMRS ports used for PTRS transmission may be used in ascending order. For example, when the PTRS-DMRS association field indicates "DMRS port 3", the UE may use DMRS port 3 as the antenna port for PTRS transmission.

[0641] The length of the PTRS-DMRS association field may be determined according to the number of available DMRS ports. For example, the length of the PTRS-DMRS association field may be determined as ceil(log2(the number of available DMRS ports)).

[0642] The PTRS-DMRS association field may indicate a mapping type of PTRS antenna port, and the PTRS antenna port may be used for all PUSCHs.

[0643] The UE may receive an indication of one of the DMRS ports scheduled for different mapping types from the PTRS-DMRS association field, and perform PTRS transmission using one DMRS port based on the indication. However, the UE may receive an indication of one of the DMRS ports scheduled for one mapping type from the PTRS-DMRS association field, and may transmit the PTRS through the antenna port obtained by means of the indication. The UE may transmit the PTRS of another mapping type through the same antenna port as the antenna port obtained by the above indication.

[0644] When the UE receives an indication including TDRA rows of different mapping types, the UE may select one of mapping type A and mapping type B to apply the PTRS-DMRS association field. For example, the selection may be based on at least one of the following:

[0645] - The UE may always select mapping type A. That is, the PTRS-DMRS association field may indicate one of the DMRS ports of mapping type A.

[0646] - The UE may always select mapping type B. That is, the PTRS-DMRS association field may indicate one of the DMRS ports of mapping type B.

[0647] -The UE may select the mapping type of the 1st scheduled PUSCH. That is, the PTRS-DMRS association field may indicate one of the DMRS ports of the 1st scheduled PUSCH mapping type. Here, the 1st scheduled PUSCH may be the PUSCH scheduled at the earliest time position. Here, the 1st scheduled PUSCH may be the PUSCH corresponding to the scheduling information first configured by the higher layer in the indicated TDRA row.

[0648] For example, it is assumed that the UE has received {3, 4, 5} as the DMRS port of mapping type A, and {2, 3, 6} as the DMRS port of mapping type B. Here, mapping type A corresponds to the case where the DMRS type (dmrs-Type) is 2, the DMRS maximum length (maxLength) is 2, the level is 3, and the row corresponding to the value 2 in the antenna port table is indicated. Mapping type B corresponds to the case where the DMRS type (dmrs-Type) is 1, the DMRS maximum length (maxLength) is 2, the level is 3, and the row corresponding to the value 2 in the antenna port table is indicated.

[0649] The UE may receive an indication of one of the DMRS ports selected from the DMRS ports in the PTRS-DMRS association field and perform PTRS transmission using the DMRS port. The PTRS-DMRS association field may indicate a value of one of "the 1st co-scheduled DMRS port", "the 2nd co-scheduled DMRS port", "the 3rd co-scheduled DMRS port" and "the 4th co-scheduled DMRS port". Here, the DMRS ports used for PTRS transmission may be used in ascending order of the value indicated by the PTRS-DMRS association field. For example, when the selected mapping type is mapping type A, the scheduled DMRS ports are {3, 4, 5}, and when the PTRS-DMRS association field indicates "the 1st co-scheduled DMRS port", the UE may use DMRS port 3 as the antenna port for PTRS transmission. When the PTRS-DMRS association field indicates "the 2nd co-scheduled DMRS port", the UE may use DMRS port 4 as the antenna port for PTRS transmission. When the PTRS-DMRS association field indicates "3rd co-scheduled DMRS port", the UE may use DMRS port 5 as the antenna port for PTRS transmission.

[0650] When all antenna ports are included in the scheduled DMRS ports of two different mapping types, PTRS can be transmitted through the antenna ports. However, a certain antenna port can be included in the scheduled DMRS ports of one mapping type but not included in the scheduled DMRS ports of another mapping type. In this case, the UE can perform the following operations.

[0651] As a first operation, when the determined antenna port is not included in the scheduled DMRS port of another mapping type, the PTRS may not be transmitted through the PUSCH of the mapping type. That is, the PTRS may be transmitted only in the case of one mapping type.

[0652] As a second operation, when the determined antenna port is not included in the scheduled DMRS port of another mapping type, the PTRS may be transmitted through a specific DMRS port in the PUSCH of the mapping type. Here, the specific DMRS port may be the DMRS port with the smallest index among the scheduled DMRS ports.

[0653] Although the above describes each embodiment separately, this is only for the convenience of explanation, and a combination of the embodiments may also be implemented. In addition, in the embodiments of the present disclosure, for the convenience of explanation, the operation of the UE is mainly described, but the technical features of the embodiments of the present disclosure described as the operation of the UE may also be applied to the configuration of the base station and the operation of the base station.

[0654] As described above, the specific embodiments of the antenna port association field and the specific embodiments of the PTRS association field have been introduced separately, but this is only for the convenience of explanation, and the embodiments related to the antenna port association field and the PTRS association field can be implemented in combination. In addition, it should be pointed out that the term "embodiment" is also for the convenience of explanation, and the embodiments can be selectively combined and implemented within a non-contradictory range.

[0655] Fig.14 A structure of a UE in a wireless communication system according to an embodiment is shown.

[0656] refer to Fig.14 , the UE may include a transceiver (referring to a UE receiver 1400 and a UE transmitter 1410), a memory, and a UE processor 1405 (or a UE controller or processor). According to the communication method of the UE described above, the transceiver (receiver 1400 and transmitter 1410), the memory, and the UE processor 1405 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 than the above elements. In addition, the transceiver, the memory, and the processor may be implemented in a single chip.

[0657] The transceiver may send / receive signals to / from the base station. Here, the signals may include control information and data. To this end, the transceiver may include a radio frequency (RF) transmitter and an RF receiver, the RF transmitter being configured to up-convert and amplify the frequency of the transmitted signal, and the RF receiver being configured to perform low-noise amplification on the received signal and down-convert its frequency. However, this is only one embodiment of the transceiver, and the elements of the transceiver are not limited to the RF transmitter and the RF receiver.

[0658] In addition, the transceiver may also receive a signal through a wireless channel, output the signal to the processor, and transmit a signal output from the processor through a wireless channel.

[0659] The memory may store programs and data required for the UE to run. In addition, the memory may also store control information or data included in the signals sent and received by the UE. The memory may include a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a compact disc (CD)-ROM, a digital versatile disc (DVD), or a combination of storage media. In addition, there may be multiple memories.

[0660] In addition, the processor may also control a series of processes so that the UE can operate according to the above-mentioned embodiments. For example, the processor may control the elements of the UE to receive DCI configured by two layers and simultaneously receive multiple PDSCHs. There may be multiple processors, and the processor may perform operations to control the elements of the UE by executing a program stored in a memory.

[0661] Fig.15 A structure of a base station in a wireless communication system according to an embodiment is shown.

[0662] refer to Fig.15 , the base station may include a transceiver (referring to a base station receiver 1500 and a base station transmitter 1510), a memory, and a base station processor 1505 (or a base station controller or processor). According to the communication method of the above-mentioned base station, the transceiver (receiver 1500 and transmitter 1510), the memory, and the base station processor 1505 of the base station may operate. However, the elements of the base station are not limited to the above-mentioned examples. For example, the base station may include more or fewer elements than the above-mentioned elements. In addition, the transceiver, the memory, and the processor may be implemented in a single chip.

[0663] The transceiver may send / receive signals to / from the UE. Here, the signals may include control information and data. To this end, the transceiver may include an RF transmitter and an RF receiver, the RF transmitter being configured to up-convert and amplify the frequency of the transmitted signal, and the RF receiver being configured to perform low-noise amplification on the received signal and down-convert its frequency. However, this is only one embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and the RF receiver.

[0664] In addition, the transceiver may also receive a signal through a wireless channel, output the signal to the processor, and transmit a signal output from the processor through a wireless channel.

[0665] The memory may store programs and data required for the base station to operate. In addition, the memory may also store control information or data included in the signals sent and received by the base station. The memory may include a storage medium such as ROM, RAM, hard disk, CD-ROM and DVD, or a combination of storage media. In addition, there may be multiple memories.

[0666] The processor may control a series of processes so that the base station operates according to the above-mentioned embodiments of the present disclosure. For example, the processor may control each element of the base station to configure and transmit two layers of DCI including allocation information of multiple PDSCHs. There may be multiple processors, and the processor may perform operations to control the elements of the base station by executing a program stored in a memory.

[0667] The methods according to various embodiments described in the claims or specification of the present disclosure may be implemented by hardware, software, or a combination of hardware and software.

[0668] When the method is implemented by software, a computer-readable storage medium for storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors in the electronic device. At least one program may include instructions for causing the electronic device to perform the method according to the various embodiments of the present disclosure defined in the attached claims and / or herein.

[0669] The program (software module or software) can be stored in a non-volatile memory, including random access memory and flash memory, ROM, electrically erasable programmable read-only memory (EEPROM), magnetic disk storage devices, CD-ROM, DVD, other types of optical storage devices or magnetic tapes. Alternatively, any combination of some or all of the memories can also constitute a memory for storing programs. In addition, the electronic device can also include multiple such memories.

[0670] In addition, the program can be stored in a connectable storage device that can access the electronic device through a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device can access the electronic device through an external port. In addition, a separate storage device on a communication network can access the portable electronic device.

[0671] In the above detailed embodiments of the present disclosure, the elements included in the present disclosure are expressed in singular or plural form according to the proposed detailed embodiments. However, the singular form or plural form is selected for convenience of description, and the present disclosure is not limited to the elements expressed in singular or plural form. Therefore, the elements expressed in plural form may also include a single element, or the elements expressed in singular form may also include multiple elements.

[0672] The embodiments of the present disclosure described and shown in the specification and the drawings are merely specific examples proposed for the convenience of explaining the technical content of the present disclosure and helping to understand the present disclosure, and are not intended to limit the scope of the present disclosure. That is to say, it is obvious to those skilled in the art that other variants based on the technical ideas of the present disclosure can also be implemented. In addition, the above-mentioned embodiments can be used in combination as needed. For example, a part of an embodiment of the present disclosure can be used in combination with a part of another embodiment to operate a base station and a terminal. In addition, although the above-mentioned embodiments are described based on an FDD LTE system, other variants based on the technical ideas of the embodiments can also be implemented in other systems, such as TDD LTE, 5G, and NR systems.

[0673] In the drawings describing the methods of the present disclosure, the order of description does not always correspond to the order of executing the steps of each method, and the sequential relationship between the steps may be changed, or the steps may be executed in parallel.

[0674] In addition, in the drawings describing the method of the present disclosure, some elements may be omitted and some elements may be included without departing from the basic spirit and scope of the present disclosure.

[0675] Furthermore, in the method of the present disclosure, part or all of the content of each embodiment may be implemented in combination without departing from the basic spirit and scope of the present disclosure.

[0676] While the present disclosure has been particularly shown and described with reference to certain embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined in the appended claims and their equivalents.

Claims

1. A method performed by a terminal in a wireless communication system, the method include: receiving a high-layer signal including time domain resource allocation TDRA information from a base station; receiving downlink control information DCI including an antenna port field from the base station; as well as In a case where the DCI includes a plurality of scheduling information of different mapping types, an antenna port table of a first mapping type and an antenna port table of a second mapping type are identified based on the antenna port field.

2. The method according to claim 1, in, The antenna port field consists of a first bit field of the antenna port table of the first mapping type and a second bit field of the antenna port table of the second mapping type.

3. The method according to claim 1, in, The antenna port field consists of a single bit field for indicating the antenna port table of the first mapping type and the antenna port table of the second mapping type.

4. The method according to claim 1, in, The DCI includes a phase tracking reference signal PTRS and a demodulation reference signal DMRS related field, and The PTRSDMRS related field is composed of the first bit field of the antenna port table of the first mapping type and the second bit field of the antenna port table of the second mapping type.

5. A method performed by a base station in a wireless communication system, the method include: Sending a high-layer signal including time domain resource allocation TDRA information to the terminal; as well as Sending downlink control information DCI including an antenna port field to the terminal, Wherein, in a case where the DCI includes a plurality of scheduling information of different mapping types, based on the antenna port field, an antenna port table of a first mapping type and an antenna port table of a second mapping type are identified.

6. The method according to claim 5, in, The antenna port field consists of a first bit field of the antenna port table of the first mapping type and a second bit field of the antenna port table of the second mapping type.

7. The method according to claim 5, in, The antenna port field consists of a single bit field for indicating the antenna port table of the first mapping type and the antenna port table of the second mapping type.

8. The method according to claim 5, in, The DCI includes a phase tracking reference signal PTRS demodulation reference signal DMRS related field, The PTRSDMRS related field is composed of the first bit field of the antenna port table of the first mapping type and the second bit field of the antenna port table of the second mapping type.

9. A terminal in a wireless communication system, the terminal include: Transceiver; as well as A controller, the controller being configured to: Receive a high-level signal including time domain resource allocation TDRA information from a base station, receiving downlink control information DCI including an antenna port field from the base station, and In a case where the DCI includes a plurality of scheduling information of different mapping types, an antenna port table of a first mapping type and an antenna port table of a second mapping type are identified based on the antenna port field.

10. The terminal according to claim 9, in, The antenna port field consists of a first bit field of the antenna port table of the first mapping type and a second bit field of the antenna port table of the second mapping type.

11. The terminal according to claim 9, in, The antenna port field consists of a single bit field for indicating the antenna port table of the first mapping type and the antenna port table of the second mapping type.

12. The terminal according to claim 9, in, The DCI includes a phase tracking reference signal PTRS and a demodulation reference signal DMRS related field, and The PTRSDMRS related field is composed of the first bit field of the antenna port table of the first mapping type and the second bit field of the antenna port table of the second mapping type.

13. A base station in a wireless communication system, the base station include: Transceiver; as well as A controller, the controller being configured to: Sending a high-layer signal including time domain resource allocation TDRA information to the terminal, and Sending downlink control information DCI including an antenna port field to the terminal, Wherein, in a case where the DCI includes a plurality of scheduling information of different mapping types, based on the antenna port field, an antenna port table of a first mapping type and an antenna port table of a second mapping type are identified.

14. The base station according to claim 13, in, The antenna port field consists of a first bit field of the antenna port table of the first mapping type and a second bit field of the antenna port table of the second mapping type.

15. The base station according to claim 13, in, The antenna port field consists of a single bit field for indicating the antenna port table of the first mapping type and the antenna port table of the second mapping type, The DCI includes a phase tracking reference signal PTRS demodulation reference signal DMRS related field, and The PTRSDMRS related field is composed of the first bit field of the antenna port table of the first mapping type and the second bit field of the antenna port table of the second mapping type.