Method and device for priority-based control and data information transmission in wireless communication system

Abstract

A communication technology and system thereof for integrating a 5G communication system and IoT technology for supporting a higher data transmission rate beyond a 4G system. The present disclosure can be applied to intelligent services based on 5G communication technology and IoT-related technologies. A method for a terminal of a wireless communication system is provided. The method includes receiving downlink control information (DCI) for scheduling data transmission / reception from a base station, checking priority information related to the DCI, determining whether to perform data transmission / reception scheduled according to the DCI based on the priority information, and performing data transmission / reception if it is determined that data transmission / reception is to be performed, wherein the priority information is indicated by a priority information field in the DCI, is a value configured by high-level signaling, or is related to the format of the DCI.

Description

Technical Field

[0001] The present disclosure relates to wireless communication systems and more particularly to a method for priority-based control and data information transmission. Background Art

[0002] In order to meet the demand for increased wireless data traffic since the deployment of the fourth generation (4G) communication system, efforts have been made to develop improved fifth generation (5G) or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "super 4G networks" or "post-long term evolution (LTE) systems". 5G communication systems are considered to be implemented in higher frequency (millimeter wave (mmWave)) bands (e.g., 60 GHz bands) to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G communication systems. In addition, in the 5G communication system, system network improvements are being developed based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, cooperative communications, coordinated multi-points (CoMP), receiving-end interference elimination, etc. In the 5G system, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM) have been developed, as well as filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The Internet, which is a human-centered connected network in which humans generate and consume information, is now evolving into the Internet of Things (IoT) in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE), which is a combination of IoT technology and big data processing technology through connection with cloud servers, has emerged. As IoT implementation requires technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology", sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been studied recently. This IoT environment can provide intelligent Internet technology services that create new value for human life by collecting and analyzing data generated between networked things. Through the integration and combination of existing information technology (IT) with various industrial applications, IoT can be applied to multiple fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart appliances and advanced medical services.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. Cloud radio access networks (RANs) as an application of the above-mentioned big data processing technologies can also be considered as an example of the fusion of 5G technologies and IoT technologies.

[0005] 5G communication systems are evolving to provide various services, and thus schemes for efficiently providing these services are required.

[0006] The above information is provided as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the invention

[0007] Technical issues

[0008] Various aspects of the present disclosure are intended to at least solve the above-mentioned problems and / or disadvantages, and to provide at least the following advantages. Therefore, one aspect of the present disclosure is to provide a method and apparatus for efficiently providing various services. Specifically, the present disclosure provides a method and apparatus for sending or receiving data and control information according to the priority if there is a priority between each service.

[0009] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.

[0010] Solution to the problem

[0011] According to one aspect of the present disclosure, a method for a terminal of a wireless communication system is provided. The method includes: receiving downlink control information (DCI) for scheduling data transmission / reception from a base station; checking priority information related to the DCI; determining whether to perform data transmission / reception scheduled according to the DCI based on the priority information; and performing data transmission / reception if it is determined that data transmission / reception is to be performed, wherein the priority information is indicated by a priority information field in the DCI, is a value configured by high-layer signaling, or is related to the format of the DCI.

[0012] The method also includes sending at least one piece of terminal capability information (user equipment (UE) capability information) related to the service that the terminal can perform to the base station, wherein the priority information is configured based on the UE capability information. If the format of the DCI is a non-fallback DCI format, the priority information is included in the DCI, and if the format of the DCI is a fallback DCI format, the priority information is indicated by high-layer signaling.

[0013] The method also includes receiving preemption indication information from the base station, wherein whether to perform data transmission / reception is determined based on the preemption indication and a priority associated with the DCI. The method also includes receiving configured scheduling information from the base station, wherein whether to perform data transmission / reception is determined based on the configured scheduling and a priority associated with the DCI.

[0014] According to another aspect of the present disclosure, a method of a base station of a wireless communication system is provided. The method includes: checking priority information related to downlink control information (DCI); sending downlink control information (DCI) for scheduling data transmission / reception to a terminal; determining whether to perform data transmission / reception scheduled according to the DCI based on the priority information; and if it is determined that data transmission / reception is to be performed, performing data transmission / reception with the terminal, wherein the priority information is indicated by a priority information field in the DCI, is a value configured by high-layer signaling, or is related to the format of the DCI.

[0015] According to another aspect of the present disclosure, a terminal of a wireless communication system is provided. The terminal includes a transceiver and at least one processor, the at least one processor being configured to perform control to: receive downlink control information (DCI) for scheduling data transmission / reception from a base station; check priority information related to the DCI; determine whether to perform data transmission / reception scheduled according to the DCI based on the priority information; and perform data transmission / reception if it is determined that data transmission / reception is to be performed, wherein the priority information is indicated by a priority information field in the DCI, is a value configured by high-layer signaling, or is related to the format of the DCI.

[0016] According to another aspect of the present disclosure, a base station of a wireless communication system is provided. The base station includes a transceiver and at least one processor, the at least one processor being configured to perform control to: check priority information related to downlink control information; send downlink control information (DCI) for scheduling data transmission / reception to a terminal; determine whether to perform data transmission / reception scheduled according to the DCI based on the priority information; and if it is determined that data transmission / reception is to be performed, perform data transmission / reception with the terminal, wherein the priority information is indicated by a priority information field in the DCI, is a value configured by high-layer signaling, or is related to the format of the DCI.

[0017] Advantageous Effects of the Invention

[0018] According to the disclosed embodiments of the present disclosure, radio resources can be efficiently used, and various devices can be efficiently provided to users according to priorities.

[0019] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0021] Figure 1 is a diagram showing a transmission structure in a time-frequency domain (i.e., a radio resource region of a 5G or New Radio (NR) system) according to an embodiment of the present disclosure;

[0022] Figure 2is a diagram showing a process of allocating data for enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine type communication (mMTC) in a time-frequency resource region in a 5G or NR system according to an embodiment of the present disclosure;

[0023] Figure 3 is a diagram showing a process of reporting UE capabilities of a terminal to a base station after the terminal initially accesses the base station according to an embodiment of the present disclosure;

[0024] Figure 4 is a diagram illustrating a method for transmitting data information or control information of a terminal based on priority according to an embodiment of the present disclosure;

[0025] Figure 5a is a diagram showing the priority relationship of fallback downlink control information (DCI) and non-fallback DCI according to an embodiment of the present disclosure;

[0026] Figure 5b is a diagram illustrating a method for checking a priority by a terminal via a first DCI and a second DCI according to an embodiment of the present disclosure;

[0027] Figure 6a is a diagram showing a relationship between a DCI including priority information and a DCI including preemption information according to an embodiment of the present disclosure;

[0028] Figure 6b is a diagram illustrating an operation of a terminal receiving DCI and preemption information according to an embodiment of the present disclosure;

[0029] Figure 7a is a diagram showing a priority relationship between a configured grant resource and a dynamic grant resource according to an embodiment of the present disclosure;

[0030] Figure 7b is a diagram illustrating an operation of a terminal in a case where an overlap (or conflict) occurs between a configuration authorization resource and a dynamic authorization resource according to an embodiment of the present disclosure;

[0031] Figure 8 is a diagram illustrating a method of dynamically selecting modulation coding scheme (MCS) table information according to a DCI including priority information according to an embodiment of the present disclosure;

[0032] Fig. 9 is a block diagram showing a structure of a terminal capable of performing according to an embodiment of the present disclosure; and

[0033] Fig.10 is a block diagram showing the structure of a base station that can be performed according to an embodiment of the present disclosure.

[0034] Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures. DETAILED DESCRIPTION

[0035] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details that aid in understanding, but these are considered to be exemplary only. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, for the sake of clarity and conciseness, descriptions of well-known functions and structures may be omitted.

[0036] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0037] It will be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0038] When describing the embodiments of the present disclosure, descriptions related to technical contents known in the art and not directly related to the present disclosure will be omitted. The omission of such unnecessary descriptions is intended to prevent the main idea of ​​the present disclosure from being obscured and to convey the main idea more clearly.

[0039] 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 have the same reference numerals.

[0040] By referring to the embodiments described below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the ways to achieve them will become apparent. However, the present disclosure is not limited to the embodiments set forth 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, and the present disclosure is limited only by the scope of the attached claims. Throughout the specification, the same or similar reference numerals represent the same or similar elements.

[0041] Here, it will be understood that each block of the flowchart illustration and the combination of blocks in the flowchart illustration 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 create a device for implementing the functions specified in the (multiple) flowchart blocks. 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 an article of instruction device including the functions specified in the (multiple) flowchart blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operations are performed on the computer or other programmable data processing device, thereby generating a computer-implemented process, so that the instructions executed on the computer or other programmable data processing device provide operations for implementing the functions specified in the (multiple) flowchart blocks.

[0042] In addition, each block of the flowchart diagram may represent a module, code segment or part, which includes one or more executable instructions for implementing (multiple) specified logical functions. It should also be noted that in some alternative embodiments, the functions mentioned in the blocks may not occur in a given order. For example, depending on the functions involved, two blocks shown in succession may actually be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order.

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

[0044] Wireless communication systems have moved away from providing early voice-oriented services and have made progress in broadband wireless communication systems that provide high-speed and high-quality packet data services, such as communication standards such as High Speed ​​Packet Access (HSPA) of 3GPP, Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access (E-UTRA), Advanced LTE (LTE-A), High Speed ​​Packet Data (HRPD) of 3GPP2, Ultra Mobile Broadband (UMB), 802.16e of IEEE, etc. In addition, communication standards for 5G or New Radio (NR) are generated based on the fifth generation wireless communication system.

[0045] In a 5G or NR system, which is a typical example of a broadband wireless communication system, an orthogonal frequency division multiplexing (OFDM) scheme is adopted in a downlink (DL) and an uplink (UL). More specifically, a cyclic prefix OFDM (CP-OFDM) scheme is adopted in the downlink, and a discrete Fourier transform spread OFDM (DFT-S-OFDM) scheme is adopted in addition to CP-OFDM in the uplink. An uplink refers to a radio link through which a terminal sends data or a control signal to a base station, and a downlink refers to a radio link through which a base station sends data or a control signal to a terminal. In such a multiple access scheme, generally, the data or control information of each user can be distinguished by allocating and operating the time-frequency resources on which the data or control information of each user is sent so as not to overlap with each other, that is, to establish orthogonality.

[0046] The 5G or NR system adopts a hybrid automatic repeat request (HARQ) scheme, in which the corresponding data is retransmitted in the physical layer when a decoding failure occurs in the initial transmission. In the HARQ scheme, when the receiver fails to correctly decode the data, the receiver sends a negative acknowledgment (NACK) to inform the transmitter of the decoding failure, thereby enabling the transmitter to retransmit the data in the physical layer. The receiver improves the data reception performance by combining the data retransmitted by the transmitter with the data that previously failed to be decoded. In addition, when the receiver correctly decodes the data, the receiver can send information indicating successful decoding (acknowledgement (ACK)) to the transmitter to allow the transmitter to send new data.

[0047] The new radio (NR) access technology system, i.e., the new 5G communication, is designed so that various services are freely multiplexed on time and frequency resources, and accordingly, waveforms, parameter sets, reference signals, etc. can be dynamically or freely allocated according to the needs of the corresponding services. In the 5G or NR system, the supported service types can be divided into several categories, such as enhanced mobile broadband (eMBB), massive machine type communication (MMTC), and ultra-reliable and low-latency communication (URLLC). eMBB is a service designed to transmit large-capacity data at high speed, mMTC is a service designed to minimize terminal power and access multiple terminals, and URLLC is a service designed for high reliability and low latency. Different requirements may apply depending on the type of service applied to the terminal.

[0048] In the present disclosure, terms are defined based on corresponding functions and may vary depending on the intention or use of the user or operator. Therefore, the definition should be based on the content of the entire specification. In the following, a base station is a subject that performs resource allocation on a terminal, and may be at least one of a gNode B (gNB), an eNode B (eNB), a Node B, a base station (BS), a radio access unit, a base station controller, or a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In the following, in the present disclosure, an NR system is described as an example, but the present disclosure is not limited thereto. The embodiments may be applied to various communication systems having similar technical backgrounds or channel forms. In addition, according to the determination of those skilled in the art, the present disclosure may be applied to other communication systems via some modifications without departing from the scope of the present disclosure.

[0049] In the present disclosure, the terms physical channel and signal may be used interchangeably with data or control signal. For example, although the physical downlink shared channel (PDSCH) is a physical channel for transmitting data, in the present disclosure, the PDSCH may be referred to as data. For example, PDSCH transmission or reception may be understood as data transmission and reception.

[0050] In the present disclosure, higher signaling (which can be used interchangeably with higher signal, higher layer signal or higher layer signaling) is a method of transmitting a signal from a base station to a terminal through a physical downlink data channel, or a method of transmitting a signal from a terminal to a base station through a physical uplink data channel, and may also be referred to as radio resource control (RRC) signaling or a media access control (MAC) control element (CE).

[0051] Recently, as research on 5G communication systems progresses, various methods of scheduling communications with terminals have been discussed. Therefore, an efficient scheduling and data transmission / reception method based on the characteristics of the 5G communication system is required. Therefore, in order to provide a variety of services to users in a communication system, a method capable of providing each service to users according to the characteristics of the service within the same time interval, and a device using the method are required.

[0052] The terminal shall receive separate control information from the base station in order to send data to the base station or receive data from the base station. However, in the case of a service type that requires periodic traffic or low latency and / or high reliability, data can be sent or received without separate control information. In the present disclosure, this transmission scheme is referred to as a data transmission method based on configuration authorization (which can be used interchangeably with configuration authorization, authorization-free or configuration scheduling). The method of receiving or sending data after receiving the data transmission resource configuration and related information configured via control information can be referred to as the first signal transmission / reception type, and the method of sending or receiving data without control information based on the previously configured information can be referred to as the second signal transmission / reception type. For the second signal transmission / reception type, pre-configured resource areas exist periodically, and for these areas, there is an uplink type 1 authorization (UL type 1 authorization) configured only by a higher signal, and an uplink type 2 authorization (UL type 2 authorization) (or semi-persistent scheduling (SPS)) as a method configured by a combination of a higher signal and a signal L1 (ie, downlink control information (DCI)). In the case of UL Type 2 grant (or SPS), part of the information is a higher signal, and whether to send actual data is determined by signal L1. Here, signal L1 can be broadly classified into a signal indicating resource activation (which is configured as a higher level) and a signal indicating release of activated resources.

[0053] Figure 1 is a diagram showing a transmission structure in the time-frequency domain (i.e., a radio resource region of a 5G or NR system) according to an embodiment of the present disclosure.

[0054] refer to Figure 1 , the horizontal axis represents the time domain in the radio resource region, and the vertical axis represents the frequency domain in the radio resource region. The minimum transmission unit in the time domain is an OFDM symbol, and N symb OFDM symbols 102 are aggregated to form a time slot 106. The length of a subframe may be defined as 1.0 ms, and a radio frame 114 may be defined as 10 ms. The minimum transmission unit in the frequency domain is a subcarrier, and the bandwidth of the entire system transmission bandwidth may include a total of N BW subcarriers 104. Such specific value may be applied variably depending on the system.

[0055] The basic unit of the time-frequency resource region is a resource element (RE) 112 and can be represented by an OFDM symbol index and a subcarrier index. A resource block (RB) 108 can be defined as N in the frequency domain. RB There are 110 consecutive subcarriers.

[0056] Generally, the minimum transmission unit of data is RB. In 5G or NR system, N symb =14, N RB =12, and N BW It may be proportional to the bandwidth of the system transmission band. The data rate increases in proportion to the number of RBs scheduled to the terminal. In a 5G or NR system, in the case of an FDD system that operates by dividing the downlink and uplink by frequency, the downlink transmission bandwidth and the uplink transmission bandwidth may be different. The channel bandwidth represents the RF bandwidth corresponding to the system transmission bandwidth. Table 1 below shows the correspondence between the channel bandwidth and the system transmission bandwidth defined in the LTE system, which is the fourth generation of wireless communication before the 5G or NR system. For example, in an LTE system with a channel bandwidth of 10MHz, the transmission bandwidth includes 50 RBs.

[0057] [Table 1]

[0058]

[0059] In a 5G or NR system, a channel bandwidth wider than that of LTE shown in Table 1 may be used. Table 2 shows the correspondence between system transmission bandwidth, channel bandwidth, and subcarrier spacing (SCS) in a 5G or NR system.

[0060] [Table 2]

[0061]

[0062] Scheduling information about downlink data or uplink data in a 5G or NR system is transmitted from a base station to a terminal based on downlink control information (DCI). DCI is defined according to various formats, and according to each format, DCI may indicate whether the scheduling information is for uplink data (UL authorization) or for downlink data (DL authorization), whether the DCI is a compact DCI with small-size control information, whether spatial multiplexing using multiple antennas is applied, whether the DCI is used to control power, and the like. For example, DCI format 1_1, which is scheduling control information (DL authorization) for downlink data, may include at least one of the following control information.

[0063] - Carrier indicator: Indicates on which frequency carrier the transmission is performed

[0064] -DCI format indicator: an indicator that identifies whether the corresponding DCI is for downlink or uplink

[0065] - Bandwidth Part (BWP) indicator: Indicates in which BWP the downlink data is sent

[0066] - Frequency domain resource allocation: Indicates RBs in the frequency domain allocated for data transmission. The resources to be indicated are determined according to the system bandwidth and the resource allocation scheme.

[0067] -Time domain resource allocation: indicates in which OFDM symbol in which time slot the data related channel will be sent

[0068] - VRB to PRB mapping: Indicates the scheme by which virtual RB (hereinafter referred to as VRB) index and physical RB (hereinafter referred to as PRB) index will be mapped

[0069] - Modulation and Coding Scheme (MCS): Indicates the coding rate and modulation scheme used for data transmission. For example, in addition to information indicating whether the modulation scheme is quadrature phase shift keying (QPSK), quadrature amplitude modulation (16QAM), 64QAM, or 256QAM, a coding rate value capable of notifying a transport block size (TBS) and channel coding information may also be indicated.

[0070] - Code Block Group (CBG) transmission information: When retransmission of a CBG is configured, information related to which CBG is sent

[0071] -HARQ process number: indicates the HARQ process number

[0072] - New data indicator: indicates whether the transmission is a HARQ initial transmission or a retransmission

[0073] - Redundancy version: indicates the redundancy version of HARQ

[0074] - Physical Uplink Control Channel (PUCCH) resource indicator: Indicates the PUCCH resource used to transmit ACK / NACK information for downlink data

[0075] -PDSCH to HARQ_Feedback Timing Indicator: Indicates the time slot for sending ACK / NACK information for downlink data

[0076] - Transmission Power Control (TPC) Command for PUCCH: Indicates the transmission power control command for PUCCH (i.e., uplink control channel)

[0077] In the case of PUSCH transmission, time domain resource allocation may be transmitted according to information related to the time slot in which the PUSCH is transmitted, the starting OFDM symbol position S at the time slot, and the number of OFDM symbols to which the PUSCH is mapped, L. The above S may be a relative position from the start of the time slot, L may be the number of consecutive OFDM symbols, and S and L may be determined based on a start and length indicator value (SLIV) defined as follows.

[0078] If(L-1)≤7then

[0079] SLIV 14·(L-1)+S

[0080] else

[0081] SLIV=14·(14-L+1)+(14-1-S)

[0082] Where 0 <L≤14-S

[0083] In a 5G or NR system, generally, a table including SLIV, PUSCH mapping type, and information about the time slot in which PUSCH is transmitted in one row can be configured via RRC configuration. Subsequently, in the time domain resource allocation of DCI, the base station can transmit information about SLIV, PUSCH mapping type, and the time slot in which PUSCH is transmitted to the terminal by indicating the index value in the configured table. This method is also applicable to PDSCH.

[0084] Specifically, if the base station indicates to the terminal the time resource allocation field index m included in the DCI for scheduling the PDSCH, the indication notifies a combination of DRMS ​​type A position information, PDSCH mapping type information, time slot index KO, data resource start symbol S, and data resource allocation length L, which correspond to m+1 in the table showing the time domain resource allocation information. For example, Table 3 below is a table including PDSCH time domain resource allocation information based on a normal cyclic prefix.

[0085] [Table 3]

[0086]

[0087] In Table 3, dmrs-typeA-Position is a field indicating the symbol position of DMRS transmitted in a time slot indicated by the system information block (SIB), where the system information block is a terminal common control information. The possible values ​​of this field are 2 or 3. When the total number of symbols constituting a time slot is 14 and the first symbol index is 0, 2 represents the third symbol and 3 represents the fourth symbol. In Table 3, the PDSCH mapping type is information indicating the position of DMRS in the scheduled data resource area. If the PDSCH mapping type is A, the DMRS is always transmitted or received at the symbol position determined by dmrs-typeA-Position, regardless of the allocated data time domain resources. If the PDSCH mapping type is B, the position of the DMRS used for transmission / reception is always the first symbol of the allocated data time domain resources. In other words, PDSCH mapping type B does not use dmrs-typeA-Position information.

[0088] In Table 1, K 0 Refers to the offset between the time slot index of the PDCCH that sends the DCI and the time slot index of the PUSCH or PDSCH scheduled in the DCI. For example, if the time slot index of the PDCCH is n, the time slot index of the PUSCH or PDSCH scheduled by the DCI of the PDCCH is n+K 0 In Table 3, S refers to the starting symbol index of the data time domain resource in a time slot. Based on the normal cyclic prefix, the possible S values ​​range from 0 to 13. In Table 1, L refers to the data time domain resource interval length in a time slot. The possible L values ​​range from 1 to 14.

[0089] In 5G or NR systems, the PUSCH mapping type is defined by type A and type B. In PUSCH mapping type A, the first OFDM symbol of the DMRS OFDM symbol is located in the second or third OFDM symbol of the time slot. In PUSCH mapping type B, the first OFDM symbol of the DMRS OFDM symbol is located in the first OFDM symbol in the time domain resources allocated for PUSCH transmission. The above method for PUSCH time domain resource allocation can also be applied to PDSCH time domain resource allocation.

[0090] DCI can be sent on a physical downlink control channel (PDCCH) (or control information, hereinafter, PDCCH and control information can be used interchangeably), which is a downlink physical control channel via channel coding and modulation. Generally, DCI is independently scrambled with a specific radio network temporary identifier (RNTI) (or terminal identifier) ​​of each terminal, a cyclic redundancy check (CRC) is added, channel coded, and then configured to each independent PDCCH for transmission. PDCCH is mapped to a control resource set (CORESET) configured in the terminal and then transmitted.

[0091] Downlink data can be sent on the physical downlink shared channel (PDSCH), which is a physical channel for downlink data transmission. PDSCH can be sent after the control channel transmission interval, and scheduling information in the frequency domain, such as specific mapping position, modulation scheme, etc., is determined based on the DCI sent through PDCCH.

[0092] The base station notifies the terminal of the modulation scheme applied to the PDSCH for transmission and the size of the data to be transmitted (transport block size, TBS) through the modulation and coding scheme (MCS) in the control information constituting the DCI. In the embodiment of the present disclosure, the MCS may include 5 bits or more, or less than 5 bits.

[0093] TBS corresponds to the size of a transport block before channel coding for error correction is applied to a data transport block (TB) to be transmitted by the base station.

[0094] In the present disclosure, a transport block (TB) may include a media access control (MAC) header, a MAC CE, one or more MAC service data units (SDUs), and padding bits. Alternatively, a TB may represent a MAC protocol data unit (PDU) or a data unit for conversion from a MAC layer to a physical layer.

[0095] Modulation schemes supported by the 5G or NR system are Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation (QAM), 64QAM, and 256QAM, which respectively correspond to modulation orders of 2, 4, 6, and 8. For example, in the case of QPSK modulation, 2 bits per symbol may be transmitted, in the case of 16QAM modulation, 4 bits per OFDM symbol may be transmitted, in the case of 64QAM modulation, 6 bits per symbol may be transmitted, and in the case of 256QAM modulation, 8 bits per symbol may be transmitted.

[0096] If PDSCH is scheduled according to DCI, HARQ-ACK information indicating the success or failure of decoding PDSCH is sent from the base station to the terminal via PUCCH. HARQ-ACK information is sent in the time slot indicated by the PDSCH to HARQ feedback timing indicator included in the DCI for scheduling PDSCH, and the values ​​of the PDSCH to HARQ feedback timing indicator mapped to 1 to 3 bits respectively are configured by a high-level signal, as shown in Table 4. If the PDSCH to HARQ feedback timing indicator indicates k, the terminal sends HARQ-ACK information after k time slots of time slot n where PDSCH has been sent (ie, in time slot n+k).

[0097] [Table 4]

[0098]

[0099]

[0100] If the PDSCH to HARQ feedback timing indicator is not included in the DCI format 1_1 for scheduling the PDSCH, the terminal sends HARQ-ACK information in time slot n+k according to the value k configured based on the high-level signaling. When sending HARQ-ACK information on the PUCCH, the terminal sends the HARQ-ACK information to the base station by using the PUCCH resource determined based on the PUCCH resource indicator included in the DCI for scheduling the PDSCH. Here, the ID of the PUCCH resource mapped to the PUCCH resource indicator can be configured via high-level signaling.

[0101] Figure 2 2 is a diagram showing a process of allocating data for eMBB, URLLC, and mMTC in a time-frequency resource region in a 5G or NR system according to an embodiment of the present disclosure.

[0102] refer to Figure 2, data for eMBB, URLLC, and mMTC may be allocated in the entire system frequency band 200. If URLLC data 203, 205, and 207 are generated and need to be sent when eMBB data 201 and mMTC data 209 are being allocated and sent in a specific frequency band, the transmitter may clear a portion of the allocated eMBB data 201 and mMTC data 209, or may send URLLC data 203, 205, and 207 without sending eMBB data 201 and mMTC data 209. In the above service, URLLC needs to reduce latency, so URLLC data may be allocated to a portion of the resources to which eMBB data or mMTC has been allocated so as to be sent. If URLLC data is further allocated to and sent in resources to which eMBB data has been allocated, eMBB data may not be sent in overlapping time-frequency resources, so the transmission performance of eMBB data may be reduced. For example, eMBB data transmission failure may occur due to URLLC allocation.

[0103] Figure 3 is a diagram illustrating a process of reporting UE capabilities of a terminal to a base station after the terminal initially accesses the base station according to an embodiment of the present disclosure.

[0104] refer to Figure 3 , for uplink synchronization or cell access, the terminal 302 sends 306 random access information to the base station 304 via a random access channel (RACH). The base station successfully receives the random access information sent from the terminal, and finally successfully performs the random access procedure by exchanging messages corresponding to the received random access information, and sends 308 a signal to the terminal indicating that the access to the cell has been completed. Thereafter, the base station sends 310 UE capability query request information to the terminal to determine what UE capabilities the terminal accessing the cell has. After receiving the corresponding UE capability query, the terminal sends 312 UE capability information stored by the terminal to the base station via the uplink resources allocated by the base station. Then, the base station sends 314 UE capability information confirmation information to the terminal indicating that the base station has correctly received the UE capability information. The types of the above-mentioned UE capabilities can be as follows.

[0105] -General parameters

[0106] -Service Data Adaptation Protocol (SDAP) parameters

[0107] - Packet Data Convergence Protocol (PDCP) parameters

[0108] - Radio Link Control (RLC) parameters

[0109] -Media Access Control (MAC) parameters

[0110] -Physical layer (PHY) parameters

[0111] For example, the PHY parameters may include at least part of the following items.

[0112] -Whether carrier aggregation (CA) is supported

[0113] -Whether 60kHz subcarrier spacing is supported

[0114] - Whether to support extended cyclic prefix

[0115] -Whether to support code block group retransmission

[0116] -The maximum number of PDSCH or PUSCH that can be received in one time slot

[0117] - Whether to support scheduling / HARQ processing time capability 2

[0118] - Number of supported services (e.g., eMBB, URLLC, or mMTC)

[0119] -The number of supported services expected by the terminal

[0120] The base station can support optimal scheduling for each terminal via UE capability information. More specifically, after the base station receives the UE capability information sent from the terminal, the base station can send additional DCI configuration information to the terminal via a higher signal (such as RRC signaling). For example, if the terminal reports to the base station that the terminal supports code block group (CBG) retransmission, the base station may be able to notify the terminal via a higher signal that the DCI information searched includes a code block group related field. The terminal may be able to determine which code block group is retransmitted based on data scheduled via the corresponding DCI.

[0121] If a terminal can support one or more services, the base station may be able to include priority information in the DCI in order to efficiently schedule control information or data information to the corresponding terminal. Priority information may be associated with each service. In order to include priority information in the DCI, the base station may be able to consider one of the following. The above-mentioned services refer to services that are given specific requirements. An example of a specific requirement may include criteria such as transmission reliability, transmission delay, transmission capacity, etc. Different services mean that at least one requirement value is different, and if all requirements are the same, then two services can be considered to be the same service. The following describes the information used to confirm the number of services that the terminal can support and indicate priority information.

[0122] - Method 1: In the UE capability information, the processing time capability 2, the MCS table 3, the number of PDSCH / PUSCH that can be received through TDM per time slot, the PDCCH monitoring conditions, the maximum number of PDSCHs that can be received simultaneously, the presence or absence of CA resources, etc.

[0123] -Method 2: In the UE capability information, the number of services that the terminal can support

[0124] - Method 3: In the UE capability information, the number of services that the terminal is expected to support.

[0125] In the above method, method 1 is a method in which the base station indirectly determines the number of services that the terminal can support based on the UE capability information reported by the terminal. Method 2 is a method in which the terminal directly reports the number of services that the terminal can support, and therefore the base station directly determines the number of services that the terminal can support. Method 3 is similar to method 2. However, in method 2, the priority-related information configured by the base station via the final higher signal may be different from the number of services reported by the terminal, while in method 3, based on the number of services reported by the terminal, the base station unconditionally indicates to the terminal via a higher signal the priority-related information corresponding to the number. For example, according to method 2, if the terminal reports that the number of supportable services is 5, the base station can configure the priority-related information by assuming that the number of services is 4, while according to method 3, if the terminal reports that the number of supportable services is 5, the base station should configure the priority-related information based on the situation that the number of services is 5.

[0126] Methods 1 and 2 can make it possible to determine the number of services that will be provided directly to the terminal by the base station. For example, if the base station determines to provide a total of four services to the terminal, the base station can allocate two-bit field information indicating the priority to the DCI field via a higher signal. In the case of method 3, the terminal directly reports the number of services that the terminal wants to receive. For example, if the terminal reports to the base station that the terminal wants to receive a total of four services, the base station can allocate two-bit field information indicating the priority to the DCI field via a higher signal. More generally, if the number of services determined by methods 1 to 3 is N, the DCI field including the priority information can have ceil (log 2 [N]) bits in size.

[0127] As another example, if the number of services determined by methods 1 to 3 is N, the priority of the DCI field and the HARQ process ID may be implicitly mapped. More specifically, when the priority is higher, there may be a smaller HARQ process ID or a larger HARQ process ID. Alternatively, the base station may be able to map a priority value separately for each HARQ process ID, and in this case, the HARQ process ID and priority mapping relationship may be configured via a high-level signal. In addition to the HARQ process ID, the priority information may also be implicitly notified to another DCI field among the DCI fields, such as MCS index information.

[0128] According to the above priorities, if there is a conflict in time or frequency resources regarding data or control information scheduled from the base station, the terminal can use the above priorities to determine which data or control resource should be given priority. Figure 4 Provides a detailed description of how to use priorities. Figure 3 In the method of notifying the terminal of information based on priority based on the UE capability by the base station, it is mainly described. Although part of the above description is made, the priority information can be indicated by at least one of the following methods.

[0129] 1. A DCI field directly indicating priority information: For example, two bits may indicate priority information of a total of four pieces of scheduling information.

[0130] 2. Implicitly include priority information in an existing DCI field: For example, the HARQ process ID is determined to be mapped to a priority, and if there are more HARQ process IDs than the priority information size, the priority can be mapped to the HARQ process ID via a modulo operation. Specifically, the mod(HARQ process ID / N) value can be the priority of the corresponding scheduling information. Here, N is the size of the priority information (i.e., the maximum value that the priority information can indicate). As another example, the base station may be able to map each HARQ process ID and the associated priority information value via a higher signal.

[0131] 3. DCI format: The priority information or priority of each DCI format may be different.

[0132] 4. RNTI: Priority information or priority may be changed by the scrambled RNTI in the DCI.

[0133] 5. CORESET information: Priority information or priorities may change according to the CORESET configuration information.

[0134] 6. Combination of the above methods: For example, two priority groups may be divided according to the DCI format, and the priority may be divided by a DCI field indicating priority information within the DCI format. For example, DCI format A may have a higher priority than DCI format B, and the priority within DCI format A may be further determined by the value indicating the priority information in the DCI field. This combination is only an example, and the priority may be determined by the above combination.

[0135] Figure 4 is a diagram illustrating a method of transmitting data information or control information of a terminal based on a priority according to an embodiment of the present disclosure.

[0136] refer to Figure 4, reference numeral 400 shows a case where DCI 1 402 and DCI 2 404 transmitted from a base station schedule PDSCH 1 408 and PDSCH 2 406 (or PUSCH 1 and PUSCH 2), respectively. Figure 4 An example is shown in which the base station transmits DCI 1 first and DCI 2 later in terms of time, but the present disclosure is applicable not only to the case where DCI 2 is transmitted after DCI 1 is transmitted, but also to the case where the start symbol of DCI 1 is earlier than that of DCI 2. In this case, DCI 1 transmission and DCI 2 transmission may partially overlap in time. Figure 4 A case is shown where PDSCH 1 (or PUSCH 1) scheduled in DCI 1 is transmitted after PDSCH 2 (or PUSCH 2) scheduled in DCI 2. The present disclosure is applicable not only to the case where PDSCH 2 is transmitted before PDSCH 1, but also to the case where the start symbol of PDSCH 2 is earlier than the start symbol of PDSCH 1, and in this case, the transmission of PDSCH 1 and PDSCH 2 may partially overlap in time.

[0137] refer to Figure 4 , the case of reference numeral 410 is similar to the case of reference numeral 400, but reference numeral 410 shows an example in which PDSCH 2 418 (or PUSCH 2) scheduled in DCI 2 414 collides (or overlaps) with a portion of the resource region of PDSCH 1 416 (or PUSCH 1) scheduled in DCI 1 412. In reference numeral 410, although it is a case in which both the time and frequency resource regions overlap, it may also be a case in which only the time resource region overlaps. In addition, the case in which the start symbol of PDSCH 2 is the same as the start symbol of PDSCH 1 or the start symbol of PDSCH 2 is located after the start symbol of PDSCH 1 may also correspond to the case of reference numeral 410.

[0138] The criteria for determining the overlap of the time and frequency resource areas of each terminal may be different. For example, if the terminal is able to receive two or more PDSCHs or send PUSCHs in one symbol, the terminal may not make an overlapping determination when the two PDSCHs or PUSCHs overlap each other only in some time resource areas. When both the time and frequency resource areas overlap, the terminal may make an overlapping determination. On the other hand, if the terminal cannot receive two or more PDSCHs or send PUSCHs in one symbol, the terminal may make an overlapping determination when the two PDSCH or PUSCH resources overlap at least in the time resource area. In other words, the criteria for determining whether the PDSCHs or PUSCHs overlapping in the time and frequency resource areas overlap may vary according to the UE capabilities of the terminal.

[0139] refer to Figure 4 , reference numeral 420 shows an example in which PDSCH 1 424 and HARQ-ACK 1 432 for PDSCH 1 424 are scheduled in DCI 1 422, and PDSCH 2 428 and HARQ-ACK 2 430 for PDSCH 2 428 are scheduled in DCI 2 426. Although reference numeral 420 shows a case where DCI 1 and PDSCH 1 precede DCI 2 and PDSCH 2 in time, it is also possible that DCI 2 precedes PDSCH 1 in time or is transmitted (overlapped) in one or more of the same symbols. Although a case where HARQ-ACK 2 precedes HARQ-ACK 1 in time is shown, a case where the start symbol of HARQ-ACK 2 is earlier than the start symbol of HARQ-ACK 1 can also be sufficiently included in reference numeral 420.

[0140] refer to Figure 4 , reference numeral 440 is similar to reference numeral 420, but reference numeral 440 shows an example in which, in terms of time or frequency resource domain, HARQ-ACK 1 450 information for PDSCH 1 444 scheduled by DCI 1 442 overlaps HARQ-ACK 2 452 information for PDSCH 2 448 scheduled by DCI 2 446. If the two PDSCHs are PDSCHs scheduled with the same priority, the HARQ-ACK information can be multiplexed and sent to the base station in one HARQ-ACK codebook. However, if the two PDSCHs have different priorities (or reliabilities), since the HARQ-ACK information may also have different requirements, operations different from the aforementioned case may be required.

[0141] The above-mentioned PDSCH may be a PDSCH requesting HARQ-ACK information. Alternatively, the PDSCH may be a PDSCH scheduled with a DCI including a CRC scrambled with a C-RNTI and an MCS-RNTI. Reference numerals 400 and 420 indicate an out-of-order HARQ, i.e., a terminal does not receive a PDSCH or send a PUSCH or HARQ-ACK in a scheduling order (or an order in which the DCI is sent), but receives a PDSCH or sends a PDSCH or HARQ-ACK in an order different from that in which the DCI is received. These operations are not supported in Release 15 (Rel-15) NR.

[0142] The operation of reference numeral 410 is an operation not defined in Rel-15 NR, and the terminal does not prioritize any DCI, PDSCH, or PUSCH, and considers these operations to be error conditions. In the case of reference numeral 440, in Rel-15 NR, an operation is defined in which if the HARQ-ACK information overlaps, the HARQ-ACK information is multiplexed and one HARQ-ACK information is sent to the PUCCH or PUSCH. However, if two pieces of HARQ-ACK information correspond to PDSCHs with different priorities, the requirements for each HARQ-ACK information may vary. This may lead to a situation where priority sorting is required.

[0143] In this disclosure, Figure 3 In the embodiment, the condition for supporting the operations of 400, 410, 420 and 440 based on the above-mentioned priority corresponds to the case where DCI 2 has a higher priority than DCI 1, and specifically, such a condition may be the same as at least one of the following cases.

[0144] - DCI field including priority information: High priority means that if the priority information is explicitly present in the DCI field, the value of the corresponding field is greater. For example, when the priority field value is greater, the priority can be determined to be high. In other words, if the priority field value of DCI 2 is greater than the priority field value of DCI 1, DCI 2 can have a higher priority than DCI 1. (Also applies to the opposite case)

[0145] - HARQ process ID: If priority information is associated with the HARQ process ID, DCI 2 including a HARQ process ID associated with a high priority information value may have a higher priority than DCI 1 including a HARQ process ID associated with a relatively lower priority information value.

[0146] -DCI format: If the DCI format of DCI 2 has a higher priority than the DCI format of DCI 1, the priority of DCI 2 may be higher than the priority of DCI 1.

[0147] -RNTI: If the RNTI scrambled in the CRC of DCI 2 has a higher priority than the RNTI scrambled in the CRC of DCI 1, the priority of DCI 2 can be higher than that of DCI 1.

[0148] In other words, the above conditions indicate the conditions for supporting the corresponding scheduling scheme (unordered HARQ) in the case of reference numerals 400 and 420, and indicate the conditions for supporting the operation of canceling the pre-scheduled PDSCH 1 reception or canceling the PUSCH 1 or HARQ ACK 1 transmission when conditions permit, in the case of reference numerals 410 and 440.

[0149] Specifically, only when DCI 2 has a higher priority than DCI 1, the terminal may expect scheduling as shown in reference numeral 400 or 420. On the other hand, if the priority of DCI 2 is equal to or lower than the priority of DCI 1, the terminal may not expect scheduling as shown in reference numeral 400 or 420. In the case where the priority of DCI 2 is equal to or lower than the priority of DCI 1, the terminal scheduled as shown in reference numeral 400 or 420 may assume this situation as an error, and may ignore the data transmission resources scheduled in 404 or 426, or ignore all data transmission resources scheduled in 404 and 402 or 422 and 426. Specifically, only when DCI 2 has a higher priority than DCI 1, the terminal may expect such a situation, such as in reference numerals 410 to 440, in which the terminal may expect to cancel PDSCH 1 reception or PUSCH 1 transmission in the case of reference numeral 410, and cancel HARQ-ACK 1 transmission in the case of reference numeral 440. Cancellation of scheduled PDSCH reception may mean that, even if the PDSCH has been scheduled, the terminal does not receive the PDSCH due to reception of another PDSCH, and as a result, a NACK including HARQ-ACK information corresponding to the PDSCH is sent. In addition, the terminal itself may not be able to send HARQ-ACK information. This situation is applicable to bits including HARQ-ACK information if only bits corresponding to the canceled PDSCH exist.

[0150] Figure 5a is a diagram showing the priority relationship between fallback DCI and non-fallback DCI according to an embodiment of the present disclosure.

[0151] refer to Figure 5a, consider the case where the priority information is included in the DCI field by default. For example, if the terminal supports multiple services and each service has a different priority, the base station can add the priority information in the DCI via a higher signal. However, the DCI that can change, add or delete the DCI field information via a higher signal is limited to non-fallback DCI. An example of non-fallback DCI may correspond to DCI format 1_1 that can schedule the PDSCH of Rel-15 NR or DCI format 0_1 ​​that can schedule PUSCH. On the other hand, DCI that has not changed due to a higher signal, etc. is called fallback DCI. For example, DCI format 1_0 that can schedule the PDSCH of Rel-15 NR or DCI format 0_0 that can schedule PUSCH may correspond to fallback DCI.

[0152] Therefore, it is necessary to define the priority relationship between the fallback DCI and the non-fallback DCI that includes priority information relative to the fallback DCI that does not include priority information. More specifically, if the PUSCH (or PDSCH or HARQ-ACK for the PDSCH (which can be used interchangeably with the PUCCH on which the HARQ-ACK is sent)) scheduled based on the non-fallback DCI overlaps at least partially with the resource area of ​​the PUSCH (or PDSCH or HARQ-ACK) scheduled based on the fallback DCI, the terminal needs to determine which PUSCH (or PDSCH or HARQ-ACK) should be given priority among the overlapping PUSCHs (or PDSCH or HARQ-ACK). It may be necessary to determine whether out-of-order scheduling using fallback DCI is allowed when the base station schedules PUSCH (or PDSCH) using a non-fallback DCI with a specific priority value. Therefore, the priority relationship between the fallback DCI and the non-fallback DCI can be configured by at least one of the following methods.

[0153] If a high-priority DCI and a DCI with a lower priority schedule a PDSCH (or PUSCH or PUCCH) in which at least some OFDM symbols overlap in terms of time resources, the terminal processes the PDSCH (or PUSCH or PUCCH) scheduled in the high-priority DCI and ignores (or discards) the PDSCH (or PUSCH or PUCCH) scheduled in the low-priority DCI. If two DCIs with the same priority schedule PDSCHs (or PUSCHs or PUCCHs) in which at least some OFDM symbols overlap in terms of time resources, the terminal processes the PDSCH (or PUSCH or PUCCH) scheduled in the DCI sent later in time and ignores (or discards) the PDSCH (or PUSCH or PUCCH) scheduled in the DCI sent first in time.

[0154] The method of determining whether the DCI is sent later in time or first can be performed based on the first symbol of the CORESET including the DCI. Specifically, in the first symbol of the first DCI and the first symbol of the second DCI, if the first symbol of the first DCI leads the first symbol of the second DCI in the time domain, it can be determined that the first DCI leads in time. Alternatively, the method of determining whether the DCI is sent later in time or first can be performed based on the last symbol of the CORESET including the DCI. For example, specifically, in the last symbol of the first DCI and the last symbol of the second DCI, if the last symbol of the first DCI leads the last symbol of the second DCI in the time domain, it can be determined that the first DCI leads in time.

[0155] - Method 1: Fallback DCI has a lower priority than non-fallback DCI. For example, regardless of the priority field value in the non-fallback DCI, the non-fallback DCI always takes precedence over the fallback DCI. Therefore, the terminal can expect that the PDSCH (or PUSCH or HARQ-ACK) scheduled based on the fallback DCI can be cancelled by the PDSCH (or PUSCH or HARQ-ACK) scheduled based on the non-fallback DCI. Non-fallback DCI can enable out-of-order HARQ scheduling for fallback DCI. Out-of-order HARQ scheduling refers to Figure 4 400 and 420. For example, Figure 4 In the reference numerals 400, 410, 420 and 440 of FIG. 1 , DCI 1 may be a fallback DCI and DCI 2 may be a non-fallback DCI.

[0156] - Method 2: Fallback DCI has a higher priority than non-fallback DCI. For example, fallback DCI always takes precedence over non-fallback DCI regardless of the priority field value in non-fallback DCI. Therefore, the terminal can expect that PDSCH (or PUSCH or HARQ-ACK) scheduled based on non-fallback DCI can be canceled by PDSCH (or PUSCH or HARQ-ACK) scheduled based on fallback DCI. Fallback DCI can enable out-of-order HARQ scheduling for non-fallback DCI. Out-of-order HARQ scheduling refers to Figure 4 400 and 420. For example, Figure 4 In the reference numerals 400, 410, 420 and 440 of FIG. 1 , DCI 1 may be a non-fallback DCI and DCI 2 may be a fallback DCI.

[0157] - Method 3: The priority relationship between fallback DCI and non-fallback DCI can be defined by a separate higher signal. In other words, according to the higher signal, the priority of fallback DCI can always be higher, lower, or in the middle of non-fallback DCI. Figure 5aAn example of a priority relationship that may be established between fallback DCI and non-fallback DCI is shown. Figure 5a The priority relationship of DCI format 0_0 500 for scheduling PUSCH in fallback DCI is shown. If the priority field indicating the priority of DCI format 0_1 ​​502 or 504 as non-fallback DCI is 1 bit, and DCI format 0_1 ​​504 with a value of 1 takes precedence over DCI format 0_1 ​​502 with a value of 0, the base station can notify the terminal of the priority of DCI format 0_0 compared to DCI format 0_1 ​​via a higher signal.

[0158] In other words, the priority of DCI format 0_0 that the base station can configure via a higher signal can be set to 506, 508, 510, 512 or 514, and the terminal can determine the priority of DCI format 0_0 via a higher signal. For example, if the priority of DCI format 0_0 is configured to 508 via a higher signal, the terminal can determine that the priority of DCI format 0_0 has the same priority relationship as the priority of DCI format 0_1 ​​having a priority value of 0. If the priority of DCI format 0_0 is configured to 512 via a higher signal, the terminal can determine that the priority of DCI format 0_0 has the same priority relationship as the priority of DCI format 0_1 ​​having a priority value of 1. If the priority of DCI format 0_0 is configured to 506 via a higher signal, the terminal can determine that DCI format 0_0 always has a lower priority than DCI format 0_1. If the priority of DCI format 0_0 is configured to 514 via a higher signal, the terminal can determine that DCI format 0_0 always has a higher priority than DCI format 0_1. If the priority of DCI format 0_0 is configured as 510 via a higher signal, the terminal may determine that DCI format 0_0 has a lower priority than DCI format 0_1 ​​having a priority value of 1, and has a higher priority than DCI format 0_1 ​​having a priority value of 0.

[0159] refer to Figure 5a , the method of configuring DCI format 0_0 is only an example, only at least one configuration information among 506, 508, 510, 512 and 514 may exist, and the terminal may receive corresponding information via a higher signal.

[0160] -Method 4: The priority of fallback DCI and non-fallback DCI may vary depending on the search space in which the DCI is received. For example, the fallback DCI detected in the common search space may have a lower priority than the non-fallback DCI and fallback DCI detected in the terminal-specific search space (UE-specific search space). As another example, the fallback DCI detected in the common search space may have a higher priority than the fallback DCI detected in the UE-specific search space. As another example, similar to method 3, the base station may separately configure the priority of the fallback DCI detected in the common search space and the priority of the fallback DCI detected in the UE-specific search space. As another example, it is possible that the fallback DCI detected in the common search space complies with method 1 or method 2, and the fallback DCI detected in the UE-specific search space complies with method 3. The above methods are merely examples, and other methods for separately configuring the fallback DCI detected for each search space are also possible.

[0161] - In addition, a combination of one or more methods described in this disclosure may be used to determine the priority relationship between fallback DCI and non-fallback DCI.

[0162] The above method may only be applicable to terminals that do not support simultaneous reception of two or more PDSCHs (or unicast PDSCHs) requesting HARQ-ACK feedback in one cell. In addition, the above method may only be applicable to terminals that do not support simultaneous transmission of two or more PUSCHs in one cell.

[0163] Figure 5b 2 is a diagram illustrating a method of checking a priority through a first DCI and a second DCI by a terminal according to an embodiment of the present disclosure.

[0164] refer to Figure 5b First, the terminal receives the first DCI in operation 520, and receives the second DCI in operation 522. If the first DCI is a fallback DCI and the second DCI is a non-fallback DCI, the terminal receives the second DCI according to the above. Figure 5b The method described in determines whether to give priority to the first DCI or the second DCI. If the first DCI is given priority, the terminal ignores (or discards) the PDSCH (or PUSCH or PUCCH) resources used for scheduling in the second DCI. Alternatively, if the second DCI is given priority, the terminal ignores (or discards) the PDSCH (or PUSCH or PUCCH) resources used for scheduling in the first DCI. In other words, the terminal operates only according to the scheduling information of the DCI with priority. In operation 524, the terminal performs the first DCI (or the second DCI) priority processing according to the priority relationship.

[0165] Figure 6a is a diagram showing a relationship between a DCI including priority information and a DCI including preemption information according to an embodiment of the present disclosure.

[0166] Specifically, refer to Figure 6a , Figure 6a (a) shows the case of DL preemption. In Rel-15 NR, preemption means that part of the resource area of ​​the previously scheduled PDSCH is not actually sent (or part of the resource area of ​​the PDSCH is not actually used for transmission). Specifically, although the base station has scheduled the PDSCH for the eMBB terminal, if part of the corresponding PDSCH resource area is used for a URLLC terminal that requires emergency service, the base station can allocate PDSCH to the URLLC terminal in part or all of the resource area. However, since the eMBB terminal does not know that all or part of the scheduled PDSCH resource area is used for the URLLC terminal, the base station needs to notify the eMBB terminal of the corresponding information. This information is a preemption indication. If the base station does not notify the information, the eMBB terminal may determine the PDSCH scheduled by the base station for the URLLC terminal as the data of the eMBB terminal, and may perform demodulation and / or decoding, thereby reducing the efficiency of demodulation and decoding.

[0167] In Rel-15 NR, the preemption indication can indicate the position where the preemption occurred in the (2 to 4) time slots or one time slot immediately before the indicator was sent in terms of time and frequency. Specifically, the time information indicates the position of the preempted symbol or symbol group as a 14-bit map, and the frequency information indicates the preempted frequency balance by dividing the active band part (BWP) configured to the terminal. This preemption indication information can be sent to one or more groups of terminals at the same time as the terminal common control information of DCI format 2_1.

[0168] This example is Figure 6a As shown. The terminal receives the PDSCH 606 ​​scheduled via the DCI format in the PDCCH 604, and confirms that the PDSCH has been scheduled. The DCI format 2_1 612 as a preemption indication can indicate 610 in which resource area in the immediately preceding time slot part 600 and the active bandwidth part 602 the preemption occurred. In order to receive the corresponding DCI format 2_1, the terminal periodically performs monitoring according to the base station configuration. However, if no preemption occurs, the base station may not actually send the DCI format 2_1 to the terminal of the corresponding group.

[0169] In the above case, according to the priority value of the DCI format in the PDCCH 604 for scheduling the PDSCH 606, the DCI format 2_1 612 as the preemption indication may not be applied to the PDSCH 606. For example, if the PDSCH 606 ​​corresponds to the service with the highest priority, even if the terminal receives the DCI format 2_1 612 and the preemption indication indicates a part of the region of the PDSCH 606, the terminal can determine that the information does not correspond to the terminal itself.

[0170] Since DCI format 2_1 612 is terminal group public information, from the point of view of the base station, it may happen that the terminal of the group receiving DCI format 2_1 receives services with different priorities at the same time. In this case, a higher signal reconfiguration is required to configure the monitoring deactivation of DCI format 2_1 of a specific terminal, and since this configuration is not dynamic (i.e., not immediate in time), additional operations are required so that the preemption area indicated by DCI format 2_1 is not applied to the terminal receiving the PDSCH with a high actual priority, as described above. Since preemption itself means that a part of the resource area of ​​the PDSCH with a low priority can be used for the PDSCH with a high priority, additional operations are required to prevent a part of the PDSCH with a high priority from being used for the PDSCH with a low priority on the contrary. Therefore, the terminal can perform an operation of using or not using the preemption indication according to the priority included in the DCI format for scheduling PDSCH. Specifically, the following method can be performed on this operation.

[0171] Method 1: Regardless of the priority, the preemption region indicated by the preemption indication of DCI format 0_0 or 0_1 for scheduling PDSCH can be considered valid. In this case, regardless of the priority of DCI, the terminal considers that no PDSCH is sent in the preemption region indicated by the indication.

[0172] Method 2: The base station may separately configure via a higher signal whether the preemption region indicated by the preemption indication is valid for the PDSCH scheduled based on the DCI format 0_1 ​​or DCI format 0_0 having a specific priority value.

[0173] Method 2 can be specifically performed as follows. If there are a total of four values ​​indicating priority, the base station is able to notify whether the preemption indication is valid for the PDSCH indicated by the DCI corresponding to a specific value among the four priority indication values. For example, if the field indicating the priority of the non-fallback DCI used to schedule the PDSCH is 2 bits, the preemption can be configured to be applied to the PDSCH scheduled based on the non-fallback DCI including the value "00" or "01". Therefore, the terminal can monitor the preemption indication, and can determine that the indicated preemption indication is valid for the PDSCH (scheduled by the DCI including the priority value 00 or 01). Preemption cannot be applied to the PDSCH scheduled based on the non-fallback DCI including the value "10" or "11". Therefore, the terminal can monitor the preemption indication, and can determine that the indicated preemption indication is invalid for the PDSCH.

[0174] This configuration may be performed via a higher layer signal. For example, the higher layer signal may indicate information about the priority of applying or not applying the preemption indication, and the information about the priority may be a priority included in the DCI, or may be information related to another priority (e.g., DCI format, RNTI, etc.). The base station is able to configure via a higher signal whether the preemption region indicated by the preemption indication is also valid for the PDSCH scheduled based on the fallback DCI.

[0175] If the terminal receives a DCI to which a DL preemption indication is not applied, a separate search for the preemption indication may be skipped. For example, the terminal may not monitor the DCI format 2_1 including the preemption indication and the CRC scrambled with the interrupt RNTI (INT-RNTI) via blind decoding. This is because, even if the terminal receives a preemption indication, since the preemption indication is not applicable to the PDSCH scheduled by the corresponding DCI, it is more efficient to skip the preemption indication to reduce power consumption from the perspective of terminal operation.

[0176] A similar method applies to UL preemption similar to DL preemption. DL preemption is information indicating that a portion of the resource region of the PDSCH received by the terminal corresponds to no transmission, while UL preemption is information indicating that a portion of the resource region of the PUSCH to be sent by the terminal should not be used for actual transmission. Therefore, DL preemption is information sent from the base station after the terminal receives the actual PDSCH, while UL preemption is information that the terminal should check before or during the sending of the actual PUSCH. Similar to DL preemption, UL preemption can be used as information indicating that a specific resource region corresponds to no transmission. A terminal that has received UL preemption can perform the following three possible operations.

[0177] 1. If at least a portion of the PUSCH resources overlaps with the resource region indicated in the UL preemption, the terminal cancels the corresponding PUSCH transmission.

[0178] 2. If the scheduled PUSCH resource region overlaps with the resource region indicated in UL preemption at least in terms of time resources, the terminal performs PUSCH transmission only on the resources remaining after excluding the overlapping resource region.

[0179] 3. If the scheduled PUSCH resource region overlaps with the resource region indicated in UL preemption at least in terms of time resources, the terminal cancels PUSCH transmission in the overlapping resource region and all subsequent corresponding resource regions. For example, the terminal performs PUSCH transmission only in the PUSCH resource region immediately before the overlapping resource region.

[0180] Figure 6a (b) shows the UL preemption operation. After receiving the UL grant for scheduling PUSCH 624 in PDCCH 620, the terminal receives information indicating UL preemption in another PDCCH 622. If the resource region indicated by the UL preemption information is a prohibited transmission region, the region may include a time and frequency resource region, such as Figure 6a As shown in the reference numeral 626. If the resource regions of 626 and 624 overlap at least in terms of time resources, the terminal may perform at least one of the above three operations.

[0181] If the terminal supports multiple services, when the terminal receives a UL grant (DCI) including specific priority information, the terminal can ignore the preemption information in the PUSCH transmission even if the terminal obtains the UL preemption information. For example, when the terminal receives a UL grant including the highest priority information and sends its PUSCH, the terminal can receive the UL preemption in another PDCCH, and even if the resource region indicated by the preemption overlaps with the PUSCH resource region, the terminal can ignore the overlap and can send data in the scheduled PUSCH resources.

[0182] For example, similar to the method of configuring the relationship between DL preemption and DCI information with priority information, in the case of UL preemption, the base station may also pre-configure the priority level to which UL preemption can be applied. For example, if UL preemption is only applicable to the priority information "00" present in the DCI field, and the PUSCH scheduled based on the DCI including the priority information "00" overlaps at least partially with the resource region indicated by the UL preemption, the terminal may be expected to perform at least one of the above three methods. If the terminal receives a PUSCH scheduled based on a DCI including priority information other than the priority information "00", and the corresponding PUSCH resource region overlaps at least partially with the resource region indicated by the UL preemption, the terminal may ignore the overlap and may perform PUSCH transmission. Another possible method is that if the terminal sends a PUSCH scheduled based on a DCI including priority information different from the priority information "00", it may not detect the UL preemption indication information corresponding to the corresponding resource region. (For example, monitoring for receiving the UL preemption indication information may not be performed). This is because, even if the terminal obtains the UL preemption information, the UL preemption information is not applied, so that power consumption can be reduced by avoiding reception in the first place.

[0183] Figure 6b is a diagram illustrating an operation of a terminal receiving DCI and preemption information according to an embodiment of the present disclosure.

[0184] refer to Figure 6b , the preemption information may be the DL or UP preemption information described above. In operation 630, the terminal first receives a first DCI. The first DCI may be control information for controlling the PDSCH or the PUSCH. In operation 632, the terminal then receives a second DCI. The second DCI may be DL preemption information indicating that a portion of the resource region of the PDSCH corresponds to no transmission, or may be UL preemption information indicating that a portion of the resource region of the PUSCH corresponds to prohibiting (or stopping) transmission. Figure 6b An example is shown in which the UL preemption information is received after receiving the DCI for scheduling the PUSCH, but it is possible to receive the UL preemption information first.

[0185] The first DCI does not include a separate field containing priority information, nor does it have priority information, such as a fallback DCI, but a priority relationship with a non-fallback DCI including a priority information field can be pre-configured directly or indirectly. If the base station pre-configures via a higher signal that the second DCI indicating DL or UL preemption information is only applicable to the first DCI with a specific priority value, then in operation 634, the terminal can process the PDSCH or PUSCH scheduled in the first DCI based on the information determined via the second DCI. The processing method is consistent with the above method. It can also include information indicating a priority value, based on which the preemption indication can be applied to higher-level information that can enable the configuration of the second DCI.

[0186] Figure 7a is a diagram showing a priority relationship between a configuration authorization resource and a dynamic authorization resource according to an embodiment of the present disclosure.

[0187] refer to Figure 7a In the case of periodically configuring configuration grant (CG) resources 700, 702, 704, and 706 that support uplink data transmission or downlink data reception without a separate DCI, if the PDSCH or PUSCH 710 scheduled based on a specific DCI 708 (i.e., dynamic grant) overlaps in at least some time and frequency, the terminal needs to determine the resource that needs to be given priority. First, the priority of the PDSCH or PUSCH scheduled based on the specific DCI 708 (i.e., dynamic grant) can be determined according to the DCI. Figure 4 , Figure 5a , Figure 5b , Figure 6a and Figure 6b As shown, a method for determining priority is described. In the case where PDSCH reception or PUSCH transmission is possible without the configuration grant of DCI, the priority of data that can be sent or received via the configuration grant resource can be determined by the following two methods.

[0188] Method 1: The priority of the configured authorized data can be determined via a higher signal. Specifically, in the case of Rel-15 NR, there are configured authorized resources (type 1 configured authorization) that can be configured and activated only based on a higher signal, and in this case, the priority configuration performed by the higher layer signal can be applied. For example, when the base station configures the configured authorized resources via a higher signal, information including data priority information for data transmission or data reception via the configured authorized resources can be further included in the higher signal so as to be sent to the terminal. After receiving the priority information configured for each specific configured authorized resource, the terminal can send or receive data in the corresponding configured authorized resource only for data that meets the corresponding priority (i.e., data having the same priority as the priority of the configured authorized resource configured via a higher signal, or data having the same or higher priority as the priority of the configured authorized resource configured via a higher signal).

[0189] Method 2: Priority information may be included in the DCI for activating the configuration grant. Specifically, in the case of Rel-15 NR, the base station sends basic configuration grant configuration information to the terminal via an upper layer signal, and the terminal shall receive the DCI including the additional activation information in order to send or receive actual data. This is called type 2 configuration grant. If priority-related information is included in the DCI information, the terminal can determine the priority of the data through the configuration grant activated via the priority information.

[0190] As shown in Table 5, the type 2 configuration grant can be activated by DCI format 0_0 or DCI format 0_1. Specifically, in the case of type 2 configuration grant, in DCI format 0_1 ​​as non-fallback DCI, the priority information of the type 2 configuration grant is indicated by the priority field included in the DCI, and since DCI format 0_0 as fallback DCI does not have a separate priority field, it can be activated by Figure 5a and Figure 5b The priority is determined by at least one of the methods described in .

[0191] [Table 5]

[0192] DCI format 0_0 DCI format 0_1 HARQ process number Set to all '0' Set to all '0' Redundant version Set to '00' Set to '00' Priority Not applicable (default priority) XXX

[0193] The priority of the PDSCH received via the configuration authorization or the priority of the PUSCH sent via the configuration authorization can be determined according to the above method. Therefore, if the PDSCH (or PUSCH) 710 scheduled based on the dynamic authorization 708 overlaps with the PDSCH 700, 702, 704 and 706 (or the PUSCH sent) received according to the configuration authorization 706 (for example, in the case of 704 and 706), the terminal can compare their respective priorities so that only the PDSCH with a higher priority can be received (or only the PUSCH with a higher priority can be sent). For example, the terminal does not receive (or send) a PDSCH (or PUSCH) with a low priority. Here, the situation of receiving the PDSCH indicates that the ACK or NACK information is sent via the HARQ-ACK resources corresponding to the ACK or NACK information. In addition, the fact that the PDSCH is not received can indicate that if the HARQ-ACK information corresponding to the PDSCH is indicated as NACK, or if there are only HARQ-ACK resources for the PDSCH, the HARQ-ACK information itself may not be sent.

[0194] The specifically described situation can be applied to the case where the terminal cannot receive two or more PDSCHs (or send PUSCHs) at the same time. If the terminal is able to receive two or more PDSCHs (or send PUSCHs), for each priority, a PDSCH (or PUSCH) that can be processed simultaneously can be received (or sent). For example, in the case where the terminal is able to receive two PDSCHs at the same time, if a total of three PDSCH resource areas (including two PDSCH resource areas scheduled via dynamic grants and one PDSCH resource area configured via configuration grants) overlap each other on at least one symbol, the terminal can receive two PDSCHs with high priority without receiving one PDSCH with the lowest priority. Therefore, the terminal receives two PDSCHs with high priority and reports to the base station whether its HARQ-ACK information is ACK or NACK. In addition, the terminal may not receive a PDSCH with the lowest priority, and indicate the HARQ-ACK information corresponding to the PDSCH as NACK, and send it to the base station, or the terminal itself does not perform HARQ-ACK transmission.

[0195] The terminal may perform retransmission on the PUSCH sent via the configuration grant, which is possible by the base station sending a DCI including a CRC scrambled with a configuration scheduling RNTI (CS-RNTI) to the terminal. If the configuration grant includes priority information, the base station may send a retransmission request for the PUSCH to the terminal based on the DCI including a CRC scrambled with the CS-RNTI, where the DCI may or may not include priority information. In this case, there may be a question as to whether the priority value of the DCI for scheduling data retransmission should be equal to the priority of the configuration grant. In order to solve this problem, the configuration grant including priority information can be retransmission scheduled by the following method.

[0196] Method 1: Retransmission scheduling can be based on all DCIs regardless of the priority value associated with the configuration grant.

[0197] According to method 1, based on a DCI having a priority value (or priority information) that is the same as or different from the priority value associated with the configuration grant, the terminal can be expected to be scheduled for retransmission. For example, if the priority value associated with the configuration grant is 1, the DCI for scheduling retransmission for the configuration grant may have a priority value of 1 or a priority value different from 1. The DCI for scheduling retransmission is determined by the HARQ process value corresponding to the configuration grant and the value for NDI to indicate retransmission for the configuration grant. In the case of a fallback DCI, in which, according to this method, the priority information field is not included in the DCI, but the priority is configured via a higher signal, the fallback DCI including a CRC scrambled with a CS-RNTI regardless of the pre-configured priority information value can schedule retransmissions for configuration grants corresponding to all priority values.

[0198] Method 2: Retransmission scheduling is possible only based on the DCI corresponding to the priority value associated with the configuration grant.

[0199] According to method 2, based on a DCI having the same priority value (or priority information) as the priority value associated with the configuration grant, the terminal can be expected to be scheduled for retransmission. For example, if the priority value associated with the configuration grant is 1, the DCI for scheduling retransmission for the configuration grant needs to have a priority value of 1. In the case of a fallback DCI, in which the priority information field is not included in the DCI, but the priority is configured via a higher signal, the base station can schedule only retransmission for the configuration grant corresponding to the preconfigured priority information value based on the fallback DCI.

[0200] Figure 7b is a diagram illustrating an operation of a terminal in a case where an overlap (or conflict) occurs between a configuration authorization resource and a dynamic authorization resource according to an embodiment of the present disclosure.

[0201] refer to Figure 7b , in operation 720, the terminal receives the configuration of the configuration grant through a higher signal from the base station. In the case of type 2 configuration grant or semi-persistent scheduling (SPS), the terminal also receives L1 information (i.e., DCI for activating configuration scheduling). Then, if uplink data is generated, the terminal performs transmission via the configuration grant resources, and in the case of SPS, the terminal periodically receives downlink data. When the base station sends a dynamic grant via signal L1, and the terminal receives information in its operation 722, the terminal confirms in operation 724 that the resources indicated by the corresponding dynamic grant overlap with at least a portion of the preconfigured configuration grant or SPS resources.

[0202] If the terminal supports only one PUSCH transmission or one (for unicast) PDSCH reception, the problem of which one of the two should be selected for transmission / reception may occur. On the contrary, if the terminal supports two or more PUSCH transmissions or two or more PDSCH receptions, all transmissions and receptions can be performed without selecting the data to be sent or received. However, if the PUSCH resources configured and scheduled by the configuration grant and dynamic grant are more than the number of PUSCHs capable of multiple simultaneous transmissions that the terminal can support, the above selection problem may occur. Similarly, if the PDSCH resources configured and scheduled by SPS and dynamic grant are more than the number of PUSCHs capable of multiple simultaneous transmissions that the terminal can support, the above selection problem may occur.

[0203] according to Figure 7b According to the priority information value described in , in operation 726, the terminal sends data via the PUSCH resources configured with the configuration grant or the PUSCH resources scheduled with the dynamic grant. If the priority information between the PUSCHs configured via the configuration grant and the dynamic grant is the same, the terminal sends uplink data via the PUSCH scheduled with the dynamic grant. In other words, the transmission is canceled (or discarded) by the PUSCH with the configuration grant or the dynamic grant having low priority information.

[0204] In the case where the PUCCH resources previously configured to the terminal via a higher signal or scheduled to the terminal via the signal L1 (DCI) overlap with the PUSCH configured via the configuration grant and the PUSCH resources scheduled via the dynamic grant in at least one OFDM symbol, if the PDSCH associated with the PUCCH has the same priority information value as that of the PUSCH, the uplink control information (UCI) may be carried on the PUSCH and transmitted. Alternatively, if the terminal has the ability to perform transmission of only one PUCCH or PUSCH, the terminal may transmit only the PUCCH or PUSCH with a high priority, and may discard the PUCCH or PUSCH with a low priority.

[0205] For example, if the PUCCH resources in which the HARQ-ACK information for the PDSCH with a priority information value of 1 is to be transmitted and the PUSCH resources previously configured via a configuration grant with a priority information value of 2 based on a higher signal or signal L1 (or scheduled via a dynamic grant) overlap in at least one OFDM symbol, then in the case of the configuration grant, if there is data to be sent via the configuration grant, the terminal discards the HARQ-ACK information and transmits the PUSCH. As another example, if the PUCCH resources in which the HARQ-ACK information for the PDSCH with a priority information value of 1 is to be transmitted and the PUSCH resources previously configured via a configuration grant with a priority information value of 1 based on a higher signal or signal L1 (or scheduled via a dynamic grant) overlap in at least one OFDM symbol, then in the case of the configuration grant, if there is data to be sent via the configuration grant, the terminal piggybacks the HARQ-ACK information onto the PUSCH so as to transmit it. For reference, the example is applied when it is assumed that a higher priority value leads to a higher priority, and the opposite is also possible.

[0206] Similarly, according to Figure 7b According to the priority information value described in , the terminal receives 726 data in descending order of priority information via PDSCH resources configured based on SPS or PDSCH resources scheduled based on dynamic grant. If the priority information between the PDSCHs configured via SPS and dynamic grant is the same, the terminal receives downlink data via the PDSCH scheduled based on dynamic grant. In other words, for the PDSCH with low priority information according to SPS or dynamic grant, the terminal cancels (or discards) PDSCH reception. For example, in a case where three unicast PDSCHs can be received at the same time, the terminal schedules each PDSCH via an SPS with a priority value of 2 and a dynamic grant with a priority value of 1, 2 or 3, and if the four PDSCH resources overlap in at least one OFDM symbol, the terminal discards the PDSCH scheduled via the dynamic grant with the lowest priority value of 1.

[0207] Figure 7b PUSCH transmission is shown, but as mentioned above, this can also apply to PDSCH reception.

[0208] Figure 8 is a diagram illustrating a method of dynamically selecting MCS table information according to a DCI including priority information according to an embodiment of the present disclosure.

[0209] refer to Figure 8, the MCS table is a table that describes the modulation order, target code rate, and spectrum efficiency according to the MCS index indicated by the DCI, as shown in Table 6 below. Table 6 below is an example of an MCS table for PDSCH, and there may be multiple MCS tables. If different MCS tables are used, the indicated modulation order, target code rate, and spectrum efficiency may be different even if the same MCS index is indicated.

[0210] [Table 6]

[0211]

[0212]

[0213] There are two methods to select the MCS table in Rel-15 NR. The first method is to configure the MCS table for use via a higher signal, and the other method is to select the MCS table based on the RNTI that scrambles the CRC of the DCI. If the MCS table is associated with a specific service, the terminal can determine the specific MCS table to be used based on the priority information in the DCI field.

[0214] Specifically, when the base station pre-configures the priority information of the DCI field, the MCS table implicitly associated with each priority information can be configured via a higher layer. For example, if a total of 2 bits of priority information are included in the DCI, the base station can perform configuration via a higher signal, where priority information "00" and "01" are associated with MCS table A, "10" is associated with MCS table B, and "11" is associated with MCS table C. In this case, the terminal can determine the MCS table to be used according to the value indicated by the priority information in the DCI field via DCI decoding, and additionally, the terminal can implicitly determine that the MCS index value of the DCI field is indicated based on the corresponding MCS table.

[0215] refer to Figure 8 , the terminal receives 800 DCI and determines which condition of A and B is satisfied. If the DCI sent by the base station satisfies 802 condition A (i.e., a case where one of the sets of priority values ​​associated with MCS table A is included in the corresponding DCI priority information), the terminal determines 806 that the MCS index is configured based on MCS table A. If 804 condition B is satisfied (i.e., a case where one of the sets of priority values ​​associated with MCS table B is included in the corresponding DCI priority information), the terminal determines 808 that the MCS index is configured based on MCS table B.

[0216] Fig. 9 is a block diagram showing a structure of a terminal capable of performing according to an embodiment of the present disclosure.

[0217] refer to Fig. 9, the terminal of the present disclosure may include a terminal receiver 900, a terminal transmitter 904 and a terminal processor 902. The terminal receiver 900 and the terminal transmitter 904 may be collectively referred to as a transceiver. The transceiver may send a signal to a base station or receive a signal from a base station. The signal may include control information and data. To this end, the transceiver may include an RF transmitter configured to perform up-conversion and amplification of the frequency of the transmitted signal, an RF receiver configured to perform low-noise amplification of the received signal and down-conversion of the frequency of the received signal, etc. In addition, the transceiver may receive a signal via a wireless channel, may output a signal to the terminal processor 902, and may send a signal output from the terminal processor 902 via a wireless channel. The terminal processor 902 may control a series of processes so that the terminal may operate according to the above-mentioned embodiments.

[0218] Fig.10 is a block diagram showing the structure of a base station that can be performed according to an embodiment of the present disclosure.

[0219] refer to Fig.10 In an embodiment of the present disclosure, the base station may include at least one of a base station receiver 1001, a base station transmitter 1005, and a base station processor 1003. The terminal receiver 1001 and the terminal transmitter 1005 may be collectively referred to as a transceiver. The transceiver may send a signal to a terminal or receive a signal from a terminal. The signal may include control information and data. To this end, the transceiver may include an RF transmitter configured to perform up-conversion and amplification of the frequency of the transmitted signal, an RF receiver configured to perform low-noise amplification of the received signal and down-conversion of the frequency of the received signal, and the like. In addition, the transceiver may receive a signal via a wireless channel, may output a signal to the base station processor 1003, and may send a signal output from the base station processor 1003 via a wireless channel. The base station processor 1003 may control a series of processes so that the base station operates according to the above-mentioned embodiment of the present disclosure.

[0220] The embodiments of the present disclosure described and shown in the specification and the drawings are presented to easily explain the technical content of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. For example, it is obvious to those skilled in the art that, based on the technical spirit of the present disclosure, other modifications and changes may be made to it. In addition, the above-mentioned various embodiments may be used in combination as needed. For example, the embodiments of the present disclosure may be partially combined to operate a base station and a terminal. In addition, although the above-mentioned embodiments have been described by an NR system, other variations based on the technical ideas of the embodiments may be implemented in other systems, such as an FDD or TDD LTE system.

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

Claims

1. A method performed by a terminal of a wireless communication system, the method comprising: receiving downlink control information DCI for cancellation of uplink transmission from a base station, wherein the DCI includes resource information indicating a time and frequency resource region for cancellation; identifying whether cancellation is applied to transmission of a physical uplink shared channel PUSCH based on a priority associated with the PUSCH and a time and frequency resource region for cancellation; and In case resources of the PUSCH overlap with the time and frequency resource region indicated by the resource information and the priority associated with the PUSCH corresponds to 0, transmission of the PUSCH is canceled.

2. The method according to claim 1, further comprising: In case the priority associated with the PUSCH corresponds to non-0, transmission of the PUSCH to the base station is performed.

3. The method according to claim 1, further comprising: Information for configuring cancellation of uplink transmission based on a priority associated with a PUSCH is received from a base station via higher layer signaling.

4. The method according to claim 1, wherein: PUSCH transmission is cancelled in the time domain from the earliest overlapping resources between the resources of the PUSCH and the time and frequency resource region indicated by the resource information.

5. The method according to claim 4, wherein: The priority of PUSCH is based on the DCI configuration that schedules PUSCH, and The DCI includes priority information indicating the priority of the PUSCH.

6. A method performed by a base station of a wireless communication system, the method comprising: Sending downlink control information DCI for scheduling a physical uplink shared channel PUSCH to the terminal; Sending a DCI for cancellation of uplink reception to a terminal, wherein the DCI for cancellation of uplink reception includes resource information indicating a time and frequency resource region for cancellation; as well as In case that resources of the PUSCH overlap with the time and frequency resource region indicated by the resource information and the priority associated with the PUSCH corresponds to 0, it is recognized that reception of the PUSCH is canceled.

7. The method according to claim 6, further comprising: In case the priority associated with the PUSCH corresponds to non-0, reception of the PUSCH is received from the terminal.

8. The method according to claim 6, further comprising: Information for configuring cancellation of uplink reception based on the priority associated with the PUSCH is transmitted to the terminal via higher layer signaling.

9. The method according to claim 8, wherein: PUSCH transmission is cancelled in the time domain from the earliest overlapping resources between the resources of the PUSCH and the time and frequency resource region indicated by the resource information.

10. The method according to claim 6, in, The DCI scheduling the PUSCH includes priority information indicating the priority of the PUSCH.

11. A terminal of a wireless communication system, the terminal comprising: Transceiver; and At least one processor configured to: receiving downlink control information DCI for cancellation of uplink transmission from a base station, wherein the DCI includes resource information indicating a time and frequency resource region for cancellation, identifying whether cancellation is applied to the transmission of a physical uplink shared channel PUSCH based on a priority associated with the PUSCH and a time and frequency resource region for cancellation, and In case resources of the PUSCH overlap with the time and frequency resource region indicated by the resource information and the priority associated with the PUSCH corresponds to 0, transmission of the PUSCH is canceled.

12. The terminal according to claim 11, in, The at least one processor is further configured to perform transmission of the PUSCH to the base station if the priority associated with the PUSCH corresponds to non-zero.

13. The terminal according to claim 11, wherein: The at least one processor is further configured to receive, from a base station via higher layer signaling, information for configuring cancellation of uplink transmission based on a priority associated with the PUSCH.

14. The terminal according to claim 11, in, PUSCH transmission is cancelled in the time domain from the earliest overlapping resources between the resources of the PUSCH and the time and frequency resource region indicated by the resource information.

15. The terminal according to claim 11, wherein: The priority of PUSCH is based on the DCI configuration that schedules PUSCH, and The DCI includes priority information indicating the priority of the PUSCH.

16. A base station of a wireless communication system, the base station comprising: Transceiver; and At least one processor configured to: Sending downlink control information DCI for scheduling the physical uplink shared channel PUSCH to the terminal, sending a DCI for cancellation of uplink reception to a terminal, wherein the DCI for cancellation of uplink reception includes resource information indicating a time and frequency resource region for cancellation, and In case that resources of the PUSCH overlap with the time and frequency resource region indicated by the resource information and the priority associated with the PUSCH corresponds to 0, it is recognized that reception of the PUSCH is canceled.

17. The base station according to claim 16, in, The at least one processor is further configured to receive, via the transceiver, reception of the PUSCH from the terminal if the priority associated with the PUSCH corresponds to non-0.

18. The base station according to claim 16, in, The at least one processor is further configured to transmit, via higher layer signaling, information for configuring cancellation of uplink reception based on a priority associated with the PUSCH to the terminal via the transceiver.

19. The base station according to claim 16, wherein: PUSCH transmission is cancelled in the time domain from the earliest overlapping resources between the resources of the PUSCH and the time and frequency resource region indicated by the resource information.

20. The base station according to claim 16, in, The DCI scheduling the PUSCH includes priority information indicating the priority of the PUSCH.

Images