阅读说明：本技术 无线通信系统中基于优先级的控制和数据信息传输的方法和设备 (Method and apparatus for priority-based control and data information transmission in a wireless communication system ) 是由 朴成珍 吴振荣 柳贤锡 方钟弦 申哲圭 吕贞镐 于 2020-03-16 设计创作，主要内容包括：一种用于融合用于支持超越4G系统的更高数据传输速率的5G通信系统和IoT技术的通信技术及其系统。本公开可以应用于基于5G通信技术和IoT相关技术的智能服务。提供了一种无线通信系统的终端的方法。该方法包括从基站接收用于调度数据发送/接收的下行链路控制信息(DCI),检查与DCI相关的优先级信息,基于优先级信息,确定是否执行根据DCI调度的数据发送/接收,并且如果确定要执行数据发送/接收,则执行数据发送/接收,其中,优先级信息由DCI中的优先级信息字段指示、是由高层信令配置的值、或者与DCI的格式相关。(A communication technology for fusing a 5G communication system and an IoT technology for supporting a higher data transmission rate beyond a 4G system and a system thereof. The present disclosure may be applied to intelligent services based on 5G communication technologies and IoT related technologies. A method of 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 associated with the DCI, the priority information being indicated by a priority information field in the DCI, being a value configured by higher layer signaling, or being associated with a format of the DCI, determining whether to perform data transmission/reception according to the DCI scheduling based on the priority information, and performing the data transmission/reception if it is determined that the data transmission/reception is to be performed.)

1. A method performed by a terminal of a wireless communication system, the method comprising:

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 the data transmission/reception in a case where it is determined that the 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 higher layer signaling, or is related to a format of the DCI.

2. The method of claim 1, further comprising:

transmitting at least one piece of terminal capability information (user equipment (UE) capability information) related to services that the terminal is capable of performing to the base station,

wherein the priority information is configured based on the UE capability information.

3. The method of claim 1, wherein the priority information is included in the DCI in a case where the format of the DCI is a non-fallback DCI format, and

wherein the priority information is indicated by a higher layer signaling in case that the format of the DCI is a fallback DCI format.

4. The method of claim 1, further comprising:

-receiving preemption indication information from the base station,

wherein whether to perform the data transmission/reception is determined based on the preemption indication and a priority associated with the DCI.

5. A method performed by a base station of a wireless communication system, the method comprising:

checking priority information related to downlink control information, DCI;

transmitting 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

performing the data transmission/reception with the terminal in a case where it is determined that the 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 higher layer signaling, or is related to a format of the DCI.

6. The method of claim 5, further comprising:

receiving at least one piece of terminal capability information (user equipment (UE) capability information) related to services that the terminal is capable of performing from the terminal,

wherein the priority information is determined based on the UE capability information.

7. The method of claim 5, further comprising:

sending a preemption indication information to the terminal,

wherein whether to perform the data transmission/reception is determined based on the preemption indication and a priority associated with the DCI.

8. A terminal of a wireless communication system, the terminal comprising:

a transceiver; and

at least one processor configured to:

receiving downlink control information DCI for scheduling data transmission/reception from a base station via the transceiver,

checking priority information associated with the DCI,

determining whether to perform data transmission/reception scheduled according to the DCI based on the priority information, and

performing the data transmission/reception via the transceiver in a case where it is determined that the 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 higher layer signaling, or is related to a format of the DCI.

9. The terminal according to claim 8, wherein,

wherein the at least one processor is further configured to transmit at least one piece of terminal capability information (user equipment, UE, capability information) related to services that the terminal is capable of performing to the base station via the transceiver, and

wherein the priority information is determined based on the UE capability information.

10. The terminal according to claim 8, wherein,

wherein the priority information is included in the DCI in case that the format of the DCI is a non-fallback DCI format, and

wherein the priority information is indicated by a higher layer signaling in case that the format of the DCI is a fallback DCI format.

11. The terminal according to claim 8, wherein,

wherein the at least one processor is further configured to receive preemption indication information from the base station via the transceiver, and

wherein whether to perform the data transmission/reception is determined based on the preemption indication and a priority associated with the DCI.

12. A base station of a wireless communication system, the base station comprising:

a transceiver; and

at least one processor configured to:

priority information associated with the downlink control information is checked,

transmitting downlink control information DCI for scheduling data transmission/reception to a terminal via the transceiver,

determining whether to perform data transmission/reception scheduled according to the DCI based on the priority information, and

performing the data transmission/reception with the terminal via the transceiver in a case where it is determined that the 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 higher layer signaling, or is related to a format of the DCI.

13. The base station as set forth in claim 12,

wherein the at least one processor is further configured to receive at least one piece of terminal capability information (user equipment, UE, capability information) related to services that the terminal is capable of performing from the terminal via the transceiver, and

wherein the priority information is determined based on the UE capability information.

14. The base station of claim 12, wherein in case the format of the DCI is a non-fallback DCI format, the priority information is included in the DCI, and

wherein the priority information is transmitted to the terminal through higher layer signaling in case that the format of the DCI is a fallback DCI format.

15. The base station as set forth in claim 12,

wherein the at least one processor is further configured to transmit preemption indication information to the terminal via the transceiver, and

wherein whether to perform the data transmission/reception is determined based on the preemption indication and a priority associated with the DCI.

Technical Field

The present disclosure relates to wireless communication systems. More particularly, the present disclosure relates to a method for priority-based control and data information transmission.

Background

To meet the increasing demand for wireless data traffic since the deployment of fourth generation (4G) communication systems, efforts have been made to develop improved fifth generation (5G) or pre-5G communication systems. Accordingly, the 5G or pre-5G communication system is also referred to as a "super 4G network" or a "post Long Term Evolution (LTE) system". The 5G communication system is considered to be implemented in a higher frequency (millimeter wave) band (e.g., 60GHz band), thereby achieving a higher data rate. In order to reduce propagation loss of radio waves and increase transmission distance, beamforming, massive-input-multiple-output (MIMO), Full-Dimensional MIMO (FD-MIMO), array antenna, analog beamforming, and massive antenna techniques are discussed in the 5G communication system. In addition, in the 5G communication system, development of system Network improvement is being performed based on an advanced small cell, a cloud Access Network (RAN), an ultra-dense Network, device-to-device (D2D) communication, a wireless backhaul, a mobile Network, cooperative communication, Coordinated Multi-point (CoMP), reception side interference cancellation, and the like. In the 5G system, hybrid FSK and QAM modulation (FQAM) and Sliding Window Superposition Coding (SWSC) have been developed as Advanced Coding Modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and Sparse Code Multiple Access (SCMA) have been developed as advanced access technologies.

The Internet, which is a human-centric network-connected Internet 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. Internet of Everything (IoE) has emerged as an IoT technology and a big data processing technology through a combination of connection with a cloud server. As IoT implementations require 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 recently been studied. Such IoT environments can provide intelligent internet technology services that create new value for human life by collecting and analyzing data generated between networked things. Through the fusion and integration of existing Information Technology (IT) with various industrial applications, IoT may be applied in a variety of fields, including smart homes, smart buildings, smart cities, smart cars or networked cars, smart grids, healthcare, smart appliances, and advanced medical services.

In line with this, various attempts have been made to apply the 5G communication system to the IoT network. For example, technologies such as sensor networks, Machine Type Communication (MTC), and machine-to-machine (M2M) communication may be implemented through beamforming, MIMO, and array antennas. The application of cloud Radio Access Network (RAN) as the big data processing technology described above can also be considered as an example of the convergence of 5G technology and IoT technology.

The 5G communication system is evolving to provide various services, and thus a scheme for efficiently providing these services is required.

The above information is provided as background information only to aid in understanding the present disclosure. No determination is made as to whether any of the above is applicable as prior art with respect to the present disclosure, nor is an assertion made.

Disclosure of Invention

Technical problem

Aspects of the present disclosure are directed to solving at least the above problems and/or disadvantages and to providing at least the advantages described below. Accordingly, an 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 transmitting or receiving data and control information according to a priority if there is a priority between each service.

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.

Solution to the problem

According to an aspect of the present disclosure, a method of a terminal of a wireless communication system is provided. The method comprises the following steps: 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 higher layer signaling, or is related to a format of the DCI.

The method also includes transmitting at least one piece of terminal capability information (user equipment (UE) capability information) related to services that the terminal is capable of performing 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, 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 higher layer signaling.

The method further 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 further includes receiving configuration scheduling (configured scheduling) information from the base station, wherein whether to perform data transmission/reception is determined based on the configuration scheduling and the priority associated with the DCI.

According to another aspect of the present disclosure, a method of a base station of a wireless communication system is provided. The method comprises the following steps: checking priority information related to Downlink Control Information (DCI); transmitting 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 performing data transmission/reception with the terminal 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 higher layer signaling, or is related to a format of the DCI.

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 configured to perform control to: 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 higher layer signaling, or is related to a format of the DCI.

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 configured to perform control to: checking priority information related to downlink control information; transmitting 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 performing data transmission/reception with the terminal 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 higher layer signaling, or is related to a format of the DCI.

Advantageous effects of the invention

According to the disclosed embodiments of the present disclosure, radio resources can be efficiently used, and various devices can be efficiently provided to a user according to priorities.

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.

Drawings

The above and other aspects, features and advantages of particular embodiments of the present disclosure will become more apparent from the following description when taken in conjunction with the accompanying drawings, in which:

fig. 1 is a diagram illustrating 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;

fig. 2 is a diagram illustrating a process of allocating data for enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and large-scale machine type communication (mtc) in a time-frequency resource region in a 5G or NR system according to an embodiment of the present disclosure;

fig. 3 is a diagram illustrating a process of reporting UE capability of a terminal to a base station after the terminal initially accesses the base station according to an embodiment of the present disclosure;

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

fig. 5A is a diagram illustrating a priority relationship of fallback Downlink Control Information (DCI) and non-fallback DCI according to an embodiment of the present disclosure;

fig. 5B is a diagram illustrating a method of checking priority by a terminal via first DCI and second DCI according to an embodiment of the present disclosure;

fig. 6A is a diagram illustrating a relationship between DCI including priority information and DCI including preemption information according to an embodiment of the present disclosure;

fig. 6B is a diagram illustrating an operation of a terminal that receives DCI and preemption information in accordance with an embodiment of the present disclosure;

FIG. 7A is a diagram illustrating a priority relationship between a configuration granted (configured granted) resource and a dynamic granted resource according to an embodiment of the present disclosure;

fig. 7B is a diagram illustrating an operation of a terminal in a case where an overlap (or collision) occurs between a configuration granted resource and a dynamic granted resource according to an embodiment of the present disclosure;

fig. 8 is a diagram illustrating a method of dynamically selecting Modulation Coding Scheme (MCS) table information according to DCI including priority information according to an embodiment of the present disclosure;

fig. 9 is a block diagram illustrating a structure of a terminal capable of performing according to an embodiment of the present disclosure; and is

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

Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures.

Detailed Description

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details that are helpful for understanding, but these are to be considered merely illustrative. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are not limited to bibliographic meanings, but are used only by the inventors to enable a clear and consistent understanding of the disclosure. Accordingly, it will be apparent to those skilled in the art that the following descriptions of the various embodiments of the present disclosure are provided for illustration only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

It should 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.

In describing the embodiments of the present disclosure, descriptions related to technical contents well known in the art and not directly related to the present disclosure will be omitted. Such omission of unnecessary description is intended to prevent the main ideas of the present disclosure from being obscured, and to more clearly convey the main ideas.

In the drawings, some elements may be exaggerated, omitted, or schematically shown for the same reason. Further, the size of each element does not completely reflect the actual size. In the drawings, the same or corresponding elements have the same reference numerals.

Advantages and features of the present disclosure and the manner of attaining them will become apparent by reference to the following embodiments described in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments set forth below, but may be embodied in various different forms. The following examples are provided solely for the purpose of complete disclosure and to inform those skilled in the art of the scope of the disclosure, and the disclosure is to be limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals denote the same or similar elements.

Here, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block(s). These computer program instructions may also be stored in a computer usable or computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer usable or computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the flowchart block(s). The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart block(s).

Furthermore, each block of the flowchart illustrations may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

As used herein, a "unit" refers to a software element or a hardware element, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), which performs a predetermined function. However, the "unit" does not always have a meaning limited to software or hardware. A "unit" may be configured to be stored in an addressable storage medium or to execute one or more processors. Thus, a "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by a "unit" may be combined into a smaller number of elements or "units" or divided into a larger number of elements or "units". Further, the elements and "units" may be implemented as one or more CPUs within a rendering device or secure multimedia card. Furthermore, a "unit" in an embodiment may include one or more processors.

Wireless communication systems have moved away from providing early voice-oriented services and have advanced in broadband wireless communication systems providing high-speed and high-quality packet data services, such as communication standards, e.g., 3GPP High Speed Packet Access (HSPA), Long Term Evolution (LTE) or evolved universal terrestrial radio access (E-UTRA), LTE-advanced (LTE-a), 3GPP2 High Rate Packet Data (HRPD), Ultra Mobile Broadband (UMB), IEEE's 802.16E, etc. Further, a communication standard for a 5G or New Radio (NR) is generated based on the fifth generation wireless communication system.

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 Downlink (DL) and Uplink (UL). More specifically, a cyclic prefix OFDM (CP-OFDM) scheme is employed in the downlink, and a discrete Fourier transform spread OFDM (DFT-S-OFDM) scheme is employed in addition to CP-OFDM in the uplink. The uplink refers to a radio link through which a terminal transmits data or control signals to a base station, and the downlink refers to a radio link through which a base station transmits data or control signals to a terminal. In such a multiple access scheme, in general, data or control information of each user can be distinguished by allocating and operating time-frequency resources on which the data or control information of each user is transmitted so as not to overlap each other, i.e., to establish orthogonality.

The 5G or NR system employs a hybrid automatic repeat request (HARQ) scheme in which corresponding data is retransmitted in a physical layer when a decoding failure occurs in an initial transmission. In the HARQ scheme, when the receiver fails to correctly decode data, the receiver transmits a Negative Acknowledgement (NACK) informing the transmitter of the decoding failure, thereby enabling the transmitter to retransmit the data in the physical layer. The receiver improves data reception performance by combining data retransmitted by the transmitter with data that previously failed in decoding. Further, when the receiver correctly decodes data, the receiver may transmit information indicating that the decoding is successful (acknowledgement (ACK)) to the transmitter to allow the transmitter to transmit new data.

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

In the present disclosure, terms are defined based on respective functions, and may vary depending on the intention or use of a user or operator. Therefore, the definitions should be based on the contents of the entire specification. Hereinafter, the base station is a subject performing resource allocation to the terminal, and may be at least one of a eNode 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. A 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 communication functions. Hereinafter, in the present disclosure, the NR system is described as an example, but the present disclosure is not limited thereto. The embodiments can be applied to various communication systems having similar technical background or channel forms. Further, the present disclosure may be applied to other communication systems via some modifications, as determined by those skilled in the art, without departing from the scope of the present disclosure.

In this disclosure, the terms physical channel and signal may be used interchangeably with data or control signals. For example, although a Physical Downlink Shared Channel (PDSCH) is a physical channel for transmitting data, the PDSCH may be referred to as data in the present disclosure. For example, PDSCH transmission or reception may be understood as data transmission and reception.

In the present disclosure, higher signaling (higher signaling), which may be used interchangeably with higher signal (higher signal), higher layer signal (higher layer signal), or higher layer signaling (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 Medium Access Control (MAC) Control Element (CE).

Recently, as research on the 5G communication system has progressed, various methods of scheduling communication with a terminal have been discussed. Therefore, efficient scheduling and data transmission/reception methods based on the characteristics of the 5G communication system are required. Therefore, in order to provide a plurality of services to a user in a communication system, a method capable of providing each service to the user according to characteristics of the service within the same time interval, and an apparatus using the same are required.

The terminal should receive separate control information from the base station in order to transmit data to or receive data from the base station. However, in case of a service type requiring a periodic traffic or a low latency and/or high reliability, data may be transmitted or received without separate control information. In this disclosure, such a transmission scheme is referred to as a data transmission method based on configuration grant (which may be used interchangeably with configuration grant, unlicensed, or configuration scheduling). A method of receiving or transmitting data after receiving a data transmission resource configuration configured via control information and related information may be referred to as a first signal transmission/reception type, and a method of transmitting or receiving data based on previously configured information without control information may be referred to as a second signal transmission/reception type. For the second signal transmission/reception type, preconfigured resource regions periodically exist, and for these regions, there are an uplink type 1 grant (UL type 1 grant) configured only by a higher signal, and an uplink type 2 grant (UL type 2 grant) (or semi-persistent scheduling (SPS)) which is a method configured by a combination of a higher signal and a signal L1, i.e., Downlink Control Information (DCI). In case of UL type 2 grant (or SPS), part of the information is a higher signal, and whether or not the actual data is transmitted is decided by signal L1. Here, the signal L1 can be broadly classified into a signal indicating resource activation (which is configured to a higher level) and a signal indicating release of activated resources.

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

Referring to fig. 1, the horizontal axis represents wirelessThe time domain in the electrical 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_symbThe OFDM symbols 102 are aggregated to form a slot 106. The length of the subframe may be defined as 1.0ms, and the 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 N in total_BWAnd subcarriers 104. Such specific values may be applied variably depending on the system.

The basic unit of the time-frequency resource region is a Resource Element (RE)112, and may be represented by an OFDM symbol index and a subcarrier index. Resource Blocks (RBs) 108 may be defined as N in the frequency domain_RBA number of consecutive subcarriers 110.

Generally, the minimum transmission unit of data is an RB unit. In 5G or NR systems, N_symb＝14、N_RB12 and N_BWMay 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 the 5G or NR system, in the case of an FDD system operating by dividing downlink and uplink by frequency, a downlink transmission bandwidth and an uplink transmission bandwidth may be different. The channel bandwidth denotes an RF bandwidth corresponding to a system transmission bandwidth. Table 1 below shows a correspondence relationship between a channel bandwidth and a system transmission bandwidth defined in an LTE system which is a fourth generation wireless communication preceding the 5G or NR system. For example, in an LTE system having a channel bandwidth of 10MHz, the transmission bandwidth includes 50 RBs.

[ Table 1]

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

[ Table 2]

Scheduling information regarding downlink data or uplink data in the 5G or NR system is transmitted from a base station to a terminal based on Downlink Control Information (DCI). The DCI is defined according to various formats, and according to each format, the DCI may indicate whether scheduling information is for uplink data (UL grant) or downlink data (DL grant), whether the DCI is a compact DCI having small-sized control information, whether spatial multiplexing using multiple antennas is applied, whether the DCI is for controlling power, and the like. For example, DCI format 1_1, which is scheduling control information (DL grant) for downlink data, may include at least one of the following control information.

-carrier indicator: indicating on which frequency carrier to perform transmission

-DCI format indicator: indicator identifying whether corresponding DCI is for downlink or uplink

-a bandwidth part (BWP) indicator: indicating in which BWP downlink data is sent

-frequency domain resource allocation: indicating RBs of a frequency domain allocated for data transmission. The resources to be represented are determined according to the system bandwidth and the resource allocation scheme.

-time domain resource allocation: indicating in which OFDM symbol of which slot a data-related channel is to be transmitted

-VRB to PRB mapping: indicating in which scheme a virtual RB (hereinafter, VRB) index and a physical RB (hereinafter, PRB) index are to be mapped

Modulation and Coding Scheme (MCS): indicating the coding rate and modulation scheme used for data transmission. For example, in addition to information indicating whether a modulation scheme is Quadrature Phase Shift Keying (QPSK), quadrature amplitude modulation (16QAM), 64QAM, or 256QAM, a coding rate value capable of informing a Transport Block Size (TBS) and channel coding information may be indicated.

-Code Block Group (CBG) transport information: indicating information related to which CBG to send when retransmission of CBGs is configured

-HARQ process number: indicating HARQ process number

-new data indicator: indicating whether a transmission is a HARQ initial transmission or a retransmission

-redundancy version: indicating redundancy versions for HARQ

-Physical Uplink Control Channel (PUCCH) resource indicator: indicating PUCCH resources for transmitting ACK/NACK information for downlink data

PDSCH to HARQ feedback timing indicator: indicating a slot for transmitting ACK/NACK information for downlink data

-Transmit Power Control (TPC) commands for PUCCH: indicating transmission power control commands for PUCCH (i.e., uplink control channel)

In the case of PUSCH transmission, the time domain resource allocation may be conveyed according to information related to the slot in which the PUSCH is transmitted, the starting OFDM symbol position S at the slot, and the number L of OFDM symbols to which the PUSCH is mapped. The above S may be a relative position from the start of a 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) as defined below.

If(L-1)≤7then

SLIV 14·(L-1)+S

else

SLIV＝14·(14-L+1)+(14-1-S)

Wherein 0< L ≦ 14-S

In the 5G or NR system, generally, a table including SLIV, a PUSCH mapping type, and information on a slot for transmitting PUSCH in one row may be configured via RRC configuration. Subsequently, in the time domain resource allocation of DCI, the base station may transmit information on the SLIV, the PUSCH mapping type, and the slot for transmitting the PUSCH to the terminal through an index value in a table indicating the configuration. This method is also applicable to PDSCH.

Specifically, if the base station indicates to the terminal a time resource allocation field index m included in DCI for scheduling PDSCH, the indication informs the combination of DRMS type a location information, PDSCH mapping type information, slot index KO, data resource start symbol S, and data resource allocation length L, which correspond to m +1 in the table showing 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.

[ Table 3]

In table 3, DMRS-typeA-Position is a field of a symbol Position at which a DMRS is transmitted within one slot, indicated by a System Information Block (SIB), which is a piece of terminal common control information. Possible values for this field are 2 or 3. When the total number of symbols constituting one slot is 14 and the first symbol index is 0, 2 denotes a third symbol and 3 denotes a fourth symbol. In table 3, the PDSCH mapping type is information indicating the location of the DMRS in the scheduled data resource region. If the PDSCH mapping type is a, the DMRS is always transmitted or received at a symbol Position determined by DMRS-typeA-Position, regardless of allocated data time domain resources. If the PDSCH mapping type is B, the location of the DMRS for transmission/reception is always the first symbol of the allocated data time domain resource. In other words, PDSCH mapping type B does not use dmrs-typeA-Position information.

In Table 1, K₀Refers to an offset of a slot index to which a PDCCH transmitting DCI belongs and a slot index to which a PUSCH or PDSCH scheduled in DCI belongs. For example, if the slot index of the PDCCH is n, the slot index of the PUSCH or PDSCH scheduled by the DCI of the PDCCH is n + K₀. In table 3, S refers to a starting symbol index of a data time domain resource within one slot. The possible S values range from 0 to 13 based on the normal cyclic prefix. In table 1, L refers to a data time domain resource interval length within one slot. Possible values of L range from 1 to 14.

In the 5G or NR system, 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 slot. In PUSCH mapping type B, the first OFDM symbol of a 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 may be equally applicable to PDSCH time domain resource allocation.

The DCI may be transmitted on a Physical Downlink Control Channel (PDCCH) (or control information, hereinafter, the PDCCH and the control information may 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, added with a Cyclic Redundancy Check (CRC), channel-coded, and then configured to each independent PDCCH to be transmitted. The PDCCH is mapped to a control resource set (CORESET) configured in the terminal and then transmitted.

Downlink data may be transmitted on a Physical Downlink Shared Channel (PDSCH), which is a physical channel used for downlink data transmission. The PDSCH may be transmitted after a control channel transmission interval and scheduling information such as a specific mapping position, a modulation scheme, etc. in the frequency domain is determined based on DCI transmitted through the PDCCH.

The base station notifies the terminal of a modulation scheme applied to the PDSCH for transmission and the size of data to be transmitted (transport block size, TBS) via a Modulation Coding Scheme (MCS) in control information constituting the DCI. In embodiments of the present disclosure, the MCS may include 5 bits or more, or less than 5 bits. The TBS corresponds to a 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.

In the present disclosure, a Transport Block (TB) may include a Medium Access Control (MAC) header, a MAC CE, one or more MAC Service Data Units (SDUs), and padding bits. Alternatively, the TB may represent a MAC Protocol Data Unit (PDU) or a data unit for conversion from the MAC layer to the physical layer.

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

If the PDSCH is scheduled according to the DCI, HARQ-ACK information indicating success or failure in decoding the PDSCH is transmitted from the base station to the terminal via the PUCCH. HARQ-ACK information is transmitted in a slot indicated by a PDSCH-to-HARQ feedback timing indicator included in DCI for scheduling a PDSCH, and values of the PDSCH-to-HARQ feedback timing indicators mapped to 1 to 3 bits, respectively, are configured by a higher layer signal, as shown in table 4. If the PDSCH-to-HARQ feedback timing indicator indicates k, the terminal transmits HARQ-ACK information after k slots of slot n (i.e., in slot n + k) in which the PDSCH has been transmitted.

[ Table 4]

If the PDSCH-to-HARQ feedback timing indicator is not included in the DCI format 1_1 for scheduling the PDSCH, the terminal transmits HARQ-ACK information in a time slot n + k according to a value k configured based on higher layer signaling. When transmitting the HARQ-ACK information on the PUCCH, the terminal transmits 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 may be configured via higher layer signaling.

Fig. 2 is a diagram illustrating a procedure for allocating data for eMBB, URLLC, and mtc in a time-frequency resource region in a 5G or NR system according to an embodiment of the present disclosure.

Referring to fig. 2, data for eMBB, URLLC, and mtc may be allocated in the entire system frequency band 200. If URLLC data 203, 205, and 207 are generated and need to be transmitted while the eMBB data 201 and the mtc data 209 are being allocated and transmitted in a particular frequency band, the transmitter may flush a portion to which the eMBB data 201 and the mtc data 209 have been allocated, or may transmit the URLLC data 203, 205, and 207 without transmitting the eMBB data 201 and the mtc data 209. In the above-described service, URLLC needs to reduce the delay time, and therefore URLLC data may be allocated to a part of resources to which eMBB data or mtc has been allocated, so as to be transmitted. If URLLC data is further allocated to and transmitted in resources to which eMBB data has been allocated, the eMBB data may not be transmitted in overlapping time-frequency resources, and thus transmission performance of the eMBB data may be degraded. For example, an eMBB data transfer failure may occur due to URLLC allocation.

Fig. 3 is a diagram illustrating a procedure of reporting UE capability of a terminal to a base station after the terminal initially accesses the base station according to an embodiment of the present disclosure.

Referring to fig. 3, for uplink synchronization or cell access, a terminal 302 transmits 306 random access information to a base station 304 via a Random Access Channel (RACH). The base station successfully receives the random access information transmitted from the terminal, finally successfully performs a random access procedure by exchanging messages corresponding to the received random access information, and transmits 308 a signal indicating that access to the cell has been completed to the terminal. Thereafter, the base station sends 310UE 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 the UE capability information saved by the terminal to the base station via the uplink resources allocated by the base station. The base station then 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-described UE capabilities may be as follows.

-general parameters

-Service Data Adaptation Protocol (SDAP) parameters

-Packet Data Convergence Protocol (PDCP) parameters

-Radio Link Control (RLC) parameters

-Medium Access Control (MAC) parameters

-physical layer (PHY) parameters

For example, the PHY parameters may include at least a portion of the following.

Whether Carrier Aggregation (CA) is supported or not

Whether 60kHz subcarrier spacing is supported or not

-whether extended cyclic prefix is supported or not

-whether code block group retransmission is supported

Maximum number of PDSCH or PUSCH that can be received in one slot

-whether scheduling/HARQ process time capability is supported 2

Number of supportable services (e.g. eMBB, URLLC, or mMTC)

-number of supported services desired by the terminal

The base station may support optimal scheduling for each terminal via the UE capability information. More specifically, after the base station receives the UE capability information transmitted from the terminal, the base station may transmit 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 inform the terminal via higher signaling that the searched DCI information includes a code block group related field. The terminal may be able to determine which group of code blocks is retransmitted based on data scheduled via the corresponding DCI.

If one terminal is able to 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 for the corresponding terminal. Priority information may be associated with each service. In order to include priority information in DCI, the base station may be able to consider one of the following. The above-mentioned service refers to a service given a specific requirement. One example of a particular requirement may include criteria such as transmission reliability, transmission delay, transmission capacity, and the like. Different services means that at least one requirement value is different and two services can be considered to be the same service if all requirements are the same. Information for confirming the number of services supportable by the terminal and indicating priority information is described below.

-method 1: among the UE capability information, processing time capability 2, MCS table 3, the number of PDSCH/PUSCH receivable through TDM per slot, PDCCH monitoring conditions, the maximum number of PDSCH receivable at the same time, presence or absence of CA resources, etc.

-method 2: number of services supportable by terminal in UE capability information

-method 3: in the UE capability information, the number of services that the terminal desires to support.

Among the above methods, method 1 is a method in which a base station indirectly determines the number of services supportable by a terminal based on UE capability information reported by the terminal. Method 2 is a method in which a terminal directly reports the number of services supportable by the terminal, and thus a base station directly determines the number of services supportable by the terminal. Method 3 is similar to method 2. However, in the 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, and in the method 3, the base station unconditionally indicates the priority-related information corresponding to the number to the terminal via the higher signal according to the number of services reported by the terminal. For example, according to method 2, if the terminal reports that the number of supportable services is 5, the base station may configure the priority-related information by assuming that the number of services is 4, whereas 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 according to a case that the number of services is 5.

Methods 1 and 2 may enable determination of the number of services to 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 may allocate two-bit field information indicating priority to the DCI field via a higher signal. In case of method 3, the terminal directly reports the number of services 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 may allocate two-bit field information indicating priority to the DCI field via a higher signal. More generally, if the number of services determined by the methods 1 to 3 is N, the DCI field including the priority information may have ceil (log)₂[N]) The size of the bits.

As another example, if the number of services determined by the 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 for each HARQ process ID separately, and in this case, the HARQ process ID and priority mapping relationship may be configured via higher layer signals. In addition to the HARQ process ID, priority information may be implicitly notified to another DCI field among DCI fields, such as MCS index information.

According to the above priority, if a collision occurs in terms of time or frequency resources with respect to data or control information scheduled from the base station, the terminal can use the above priority to determine which data or control resource should be given priority. A detailed description of the method of using the priority will be provided based on fig. 4. In fig. 3, a method in which a base station notifies a terminal of priority-based information based on UE capability is mainly described. Although described in part above, the priority information may be indicated in at least one of the following ways.

1. DCI field directly indicating priority information: for example, two bits may indicate priority information for a total of four pieces of scheduling information.

2. The priority information is implicitly included in the existing DCI field: for example, the HARQ process ID is determined to be mapped to the priority, and if there are a greater number of HARQ process IDs compared to the priority information size, the priority may be mapped to the HARQ process ID via a modulo operation. Specifically, a mod (HARQ process ID/N) value may be a priority of 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 the individual HARQ process IDs and associated priority information values via a higher signal.

DCI format: the priority information or priority of each DCI format may be different.

RNTI: the priority information or priority may be changed by the scrambled RNTI in the DCI.

CORESET information: the priority information or priority may vary depending on the CORESET configuration information.

6. The combination of the above methods: for example, two priority groups may be divided according to DCI formats, and the priority may be divided by a DCI field within the DCI format indicating priority information. 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 a value in the DCI field indicating priority information. Such a combination is merely an example, and the priority may be determined by the above-described combination.

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

Referring to fig. 4, reference numeral 400 shows a case where DCI 1402 and DCI 2404 transmitted from a base station schedule PDSCH 1408 and PDSCH 2406 (or PUSCH 1 and PUSCH 2), respectively. Fig. 4 shows an example in which the base station transmits DCI 1 first and DCI 2 later in 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 DCI 2. In this case, the DCI 1 transmission and the DCI 2 transmission may partially overlap in time. Fig. 4 shows a case where PDSCH 1 (or PUSCH 1) scheduled in DCI 1 is transmitted after PDSCH2 (or PUSCH 2) scheduled in DCI 2. The present disclosure is applicable not only to the case where PDSCH2 is transmitted before PDSCH 1 but also to the case where the starting symbol of PDSCH2 is earlier than the starting symbol of PDSCH 1, and in this case, the transmission of PDSCH 1 and PDSCH2 may partially overlap in time.

Referring to fig. 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 a PDSCH 2418 (or PUSCH 2) scheduled in DCI 2414 collides with (or overlaps with) a portion of the resource region of a PDSCH 1416 (or PUSCH 1) scheduled in DCI 1412. In reference numeral 410, although the time and frequency resource regions overlap, only the time resource regions may overlap. Note that the case where the starting symbol of the PDSCH2 is the same as the starting symbol of the PDSCH 1 or the starting symbol of the PDSCH2 is located after the starting symbol of the PDSCH 1 may correspond to the case of reference numeral 410.

The criteria for determining the overlap of the time and frequency resource regions for each terminal may be different. For example, if a terminal is capable of receiving two or more PDSCHs or transmitting a PUSCH in one symbol, the terminal may not make a determination of overlap when two PDSCHs or PUSCHs overlap with each other only in some time resource regions. When both the time and frequency resource regions overlap, the terminal may make a determination of overlap. On the other hand, if the terminal cannot receive two or more PDSCHs or transmit a PUSCH in one symbol, the terminal may make a determination of overlap when two PDSCH or PUSCH resources overlap at least in a time resource region. In other words, the criterion for determining whether PDSCH or PUSCH overlapping in the time and frequency resource region overlap may vary according to the UE capability of the terminal.

Referring to fig. 4, reference numeral 420 shows an example in which PDSCH 1424 and HARQ-ACK 1432 for PDSCH 1424 are scheduled in DCI 1422, and PDSCH 2428 and HARQ-ACK 2430 for PDSCH 2428 are scheduled in DCI 2426. Although reference numeral 420 shows the case where DCI 1 and PDSCH 1 precede DCI 2 and PDSCH2 in time, it is also fully possible that DCI 2 precedes PDSCH 1 in time or is transmitted (overlapped) in one or more of the same symbols. Although the case where HARQ-ACK 2 precedes HARQ-ACK 1 in time is shown, the case where the start symbol of HARQ-ACK 2 is earlier than the start symbol of HARQ-ACK 1 may be sufficiently included in reference numeral 420.

Referring to fig. 4, reference numeral 440 is similar to reference numeral 420, but reference numeral 440 shows an example in which HARQ-ACK 1450 information for a PDSCH 1444 scheduled by DCI 1442 overlaps with HARQ-ACK 2452 information for a PDSCH 2448 scheduled by DCI 2446 in terms of time or frequency resource domain. If the two PDSCHs are PDSCHs scheduled with the same priority, HARQ-ACK information may be multiplexed in one HARQ-ACK codebook and transmitted to the base station. However, if the two PDSCHs have different priorities (or reliabilities), since HARQ-ACK information may also have different requirements, an operation different from the foregoing case may be required.

The PDSCH may be a PDSCH requesting HARQ-ACK information. Alternatively, the PDSCH may be a PDSCH scheduled with DCI including a CRC scrambled with a C-RNTI and a MCS-RNTI. Reference numerals 400 and 420 indicate out-of-order HARQ, i.e., a case where a terminal does not receive a PDSCH or transmit a PUSCH or HARQ-ACK in a scheduling order (or an order in which DCI is transmitted), but receives a PDSCH or transmits a PDSCH or HARQ-ACK in an order different from that in which DCI is received. None of these operations is supported in Release 15(Rel-15) NR.

The operation of reference numeral 410 is an operation not defined in Rel-15NR, and the terminal does not prioritize any DCI, PDSCH or PUSCH, and considers these operations as an error case. In Rel-15NR, an operation of multiplexing HARQ-ACK information and transmitting one piece of HARQ-ACK information to a PUCCH or a PUSCH if the HARQ-ACK information overlaps is defined with reference numeral 440. However, if the two pieces of HARQ-ACK information correspond to PDSCHs having different priorities, the requirement for each piece of HARQ-ACK information may vary. This may lead to situations where prioritization is required.

In the present disclosure, in fig. 3, the condition based on the above-described operation of priority support 400, 410, 420, and 440 corresponds to a case where DCI 2 has higher priority than DCI 1, and in particular, such condition may be the same as at least one of the following cases.

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

-HARQ process ID: if the priority information is associated with a 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.

-a DCI format: if the DCI format of DCI 2 has higher priority than the DCI format of DCI 1, the priority of DCI 2 may be higher than the priority of DCI 1.

-RNTI: the priority of DCI 2 may be higher than that of DCI 1 if RNTI scrambled in the CRC of DCI 2 has higher priority than RNTI scrambled in the CRC of DCI 1.

In other words, the above-mentioned condition indicates a condition for supporting a corresponding scheduling scheme (out-of-order HARQ) in the case of reference numerals 400 and 420, and indicates a condition for supporting an operation of canceling reception of a previously scheduled PDSCH 1 or canceling transmission of a PUSCH 1 or HARQ ACK 1 when the condition permits in the case of reference numerals 410 and 440.

Specifically, the terminal may expect scheduling as shown by reference numeral 400 or 420 only when DCI 2 has higher priority than DCI 1. 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 by 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 by reference numeral 400 or 420 may assume this case as an error and may ignore the data transmission resources scheduled in 404 or 426 or ignore all the 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 the case, such as in reference numerals 410 to 440, where 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. The cancellation of the scheduled PDSCH reception may mean that the terminal does not receive the PDSCH due to the reception of another PDSCH even though the PDSCH has been scheduled, and as a result, a NACK including HARQ-ACK information corresponding to the PDSCH is transmitted. Furthermore, the terminal itself may not be able to transmit HARQ-ACK information. This case is applicable for bits including HARQ-ACK information if only bits corresponding to the cancelled PDSCH exist.

Fig. 5A is a diagram illustrating a priority relationship of fallback DCI and non-fallback DCI according to an embodiment of the present disclosure.

Referring to fig. 5A, consider the case where priority information is included in a DCI field by default. For example, if the terminal supports a plurality of services, and each service has a different priority, the base station may add priority information in DCI via a higher signal. However, DCI capable of changing, adding, or deleting DCI field information via higher signals is limited to non-fallback DCI. Examples of the non-fallback DCI may correspond to DCI format 1_1 capable of scheduling Rel-15NR PDSCH or DCI format 0_1 capable of scheduling PUSCH. On the other hand, DCI which is not changed due to a higher signal or the like is referred to as fallback DCI. For example, DCI format 1_0 of PDSCH capable of scheduling Rel-15NR or DCI format 0_0 of PUSCH capable of scheduling PUSCH may correspond to fallback DCI.

Therefore, there is a need to define a priority relationship between fallback DCI and non-fallback DCI including priority information relative to fallback DCI not including priority information. More specifically, if the resource region of the PUSCH (or PDSCH or HARQ-ACK for the PDSCH, which may be used interchangeably with the PUCCH on which the HARQ-ACK is transmitted) based on the non-fallback DCI scheduling at least partially overlaps with the resource region of the PUSCH (or PDSCH or HARQ-ACK) based on the fallback DCI scheduling, the terminal needs to determine which PUSCH (or PDSCH or HARQ-ACK) should be given priority among the PUSCHs (or PDSCH or HARQ-ACK) overlapping each other. It may be necessary to determine whether to allow out-of-order scheduling with fallback DCI in case the base station schedules PUSCH (or PDSCH) with non-fallback DCI with a specific priority value. Accordingly, the priority relationship between the fallback DCI and the non-fallback DCI may be configured by at least one of the following methods.

If the high-priority DCI and the DCI with 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 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 a DCI transmitted later in time and ignores (or discards) the PDSCH (or PUSCH or PUCCH) scheduled in a DCI transmitted first in time.

The method of determining whether the DCI is transmitted later in time or first may be performed based on a first symbol of the CORESET including the DCI. Specifically, of the first symbol of the first DCI and the first symbol of the second DCI, if the first symbol of the first DCI precedes the first symbol of the second DCI in the time domain, it may be determined that the first DCI precedes in time. Alternatively, the method of determining whether the DCI is transmitted later or first in time may be performed based on the last symbol of the CORESET including the DCI. For example, in particular, of the last symbol of the first DCI and the last symbol of the second DCI, if the last symbol of the first DCI precedes the last symbol of the second DCI in the time domain, it may be determined that the first DCI precedes in time.

-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. Thus, the terminal may expect that the PDSCH (or PUSCH or HARQ-ACK) scheduled based on the fallback DCI may be cancelled by the PDSCH (or PUSCH or HARQ-ACK) scheduled based on the non-fallback DCI. The non-fallback DCI may enable out-of-order HARQ scheduling for the fallback DCI. Out-of-order HARQ scheduling refers to reference numerals 400 and 420 of fig. 4. For example, in reference numerals 400, 410, 420 and 440 of fig. 4, DCI 1 may be a fallback DCI, and DCI 2 may be a non-fallback DCI.

-method 2: fallback DCI has a higher priority than non-fallback DCI. For example, regardless of the priority field value in the non-fallback DCI, the fallback DCI always takes precedence over the non-fallback DCI. Thus, the terminal may expect that the PDSCH (or PUSCH or HARQ-ACK) scheduled based on the non-fallback DCI may be cancelled by the PDSCH (or PUSCH or HARQ-ACK) scheduled based on the fallback DCI. The fallback DCI may enable out-of-order HARQ scheduling for the non-fallback DCI. Out-of-order HARQ scheduling refers to reference numerals 400 and 420 of fig. 4. For example, in reference numerals 400, 410, 420 and 440 of fig. 4, DCI 1 may be a non-fallback DCI, and DCI 2 may be a fallback DCI.

-method 3: the priority relationship between the fallback DCI and the non-fallback DCI may be defined by a separate higher signal. In other words, the priority of the fallback DCI may always be higher, lower or in the middle of the non-fallback DCI according to the higher signal. Fig. 5A illustrates an example of a priority relationship that may be established between fallback DCI and non-fallback DCI. Fig. 5A shows the priority relationship of DCI format 0_ 0500 for scheduling PUSCH in fallback DCI. If the priority field indicating the priority of DCI format 0_ 1502 or 504, which is non-fallback DCI, is 1 bit and DCI format 0_ 1504 having a value of 1 is prioritized over DCI format 0_ 1502 having a value of 0, the base station may signal via a higher signal that terminal DCI format 0_0 has priority over DCI format 0_ 1.

In other words, the priority at which the base station can configure DCI format 0_0 via a higher signal may be set to 506, 508, 510, 512, or 514, and the terminal may 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 may determine that the priority of DCI format 0_0 has the same priority relationship with the priority of DCI format 0_1 having a priority value of 0. If the priority of the DCI format 0_0 is configured to 512 via a higher signal, the terminal may determine that the priority of the DCI format 0_0 has the same priority relationship with the priority of the DCI format 0_1 having the priority value 1. If the priority of DCI format 0_0 is configured to 506 via a higher signal, the terminal may 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 may determine that DCI format 0_0 always has a higher priority than DCI format 0_ 1. If the priority of the DCI format 0_0 is configured to 510 via a higher signal, the terminal may determine that the DCI format 0_0 has a lower priority than the DCI format 0_1 having the priority value 1 and has a higher priority than the DCI format 0_1 having the priority value 0.

Referring to fig. 5A, a method of configuring DCI format 0_0 is merely an example, only at least one piece of configuration information of 506, 508, 510, 512, and 514 may exist, and a terminal may receive corresponding information via a higher signal.

-method 4: the priority of the fallback DCI and the non-fallback DCI may vary according to the search space in which the DCI is received. For example, fallback DCI detected in a common search space may have a lower priority than non-fallback DCI and fallback DCI detected in a terminal-specific search space (UE-specific search space). As another example, fallback DCI detected in a common search space may have a higher priority than fallback DCI detected in a UE-specific search space. As yet another example, similar to method 3, the base station may separately configure the priority of fallback DCI detected in the common search space and the priority of fallback DCI detected in the UE-specific search space. As yet another example, it is possible that fallback DCI detected in a common search space conforms to method 1 or method 2, and fallback DCI detected in a UE-specific search space conforms to method 3. The above-described method is merely an example, and other methods for individually configuring fallback DCI detected for each search space are possible.

Furthermore, a combination of one or more methods described in this disclosure may be used to determine a priority relationship between fallback DCI and non-fallback DCI.

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

Fig. 5B is a diagram illustrating a method of checking a priority by a terminal via first DCI and second DCI according to an embodiment of the present disclosure.

Referring to fig. 5B, first, the terminal receives first DCI in operation 520 and receives second DCI in operation 522. If the first DCI is a fallback DCI and the second DCI is a non-fallback DCI, the terminal determines whether to give priority to the first DCI or the second DCI according to the method described in fig. 5B above. If the first DCI is given priority, the terminal ignores (or discards) the PDSCH (or PUSCH or PUCCH) resource 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) resource used for scheduling in the first DCI. In other words, the terminal operates only according to the scheduling information of the DCI having the priority. In operation 524, the terminal performs first DCI (or second DCI) priority processing according to the priority relationship.

Fig. 6A is a diagram illustrating a relationship between DCI including priority information and DCI including preemption information according to an embodiment of the present disclosure.

Specifically, referring to fig. 6A, (a) of fig. 6A shows the case of DL preemption. In Rel-15NR, preemption means that a portion of the resource region of the previously scheduled PDSCH is not actually transmitted (or a portion of the resource region of the PDSCH is not actually used for transmission). Specifically, although the base station has scheduled PDSCH for the eMBB terminal, the base station may allocate PDSCH for the URLLC terminal in a portion or all of the resource region if a portion of the corresponding PDSCH resource region is used for URLLC terminals that require emergency services. However, since the eMBB terminal does not know that all or a part of the scheduled PDSCH resource region 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 inform the information, the eBB terminal may determine the PDSCH scheduled by the base station for the URLLC terminal as data of the eBB terminal and may perform demodulation and/or decoding, thereby reducing the efficiency of the demodulation and decoding.

In Rel-15NR, the preemption indication may indicate, in terms of time and frequency, where preemption occurs in the (2 to 4) slots or one slot immediately preceding the transmission of the indicator. Specifically, the time information indicates the positions of the symbols or symbol groups to be preempted as 14 bit maps, and the frequency information indicates the preempted frequency equalization by dividing an active band part (BWP) configured to the terminal. Such preemption indication information may be sent simultaneously to one or more groups of terminals as terminal common control information for DCI format 2_ 1.

This example is shown in fig. 6A. The terminal receives PDSCH 606 scheduled via DCI format in PDCCH 604 and confirms that PDSCH has been scheduled. DCI format 2_ 1612 as a preemption indication may indicate 610 in which resource region in the immediately preceding slot portion 600 and active bandwidth portion 602 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 transmit DCI format 2_1 to the terminals of the corresponding group.

In the above case, depending on the priority value of the DCI format in the PDCCH 604 for scheduling the PDSCH 606, DCI format 2_ 1612 as the preemption indication may not be applied to the PDSCH 606. For example, if the PDSCH 606 corresponds to a service having the highest priority, even if the terminal receives DCI format 2_ 1612 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.

Since DCI format 2_ 1612 is terminal group common information, from the viewpoint of the base station, a case may occur in which a terminal of a group receiving DCI format 2_1 receives services having different priorities at the same time. In this case, higher signal reconfiguration is required to configure the monitoring deactivation of DCI format 2_1 for a particular terminal, and since this configuration is not dynamic (i.e., not immediate in time), additional operations are required so that the preemption region indicated by DCI format 2_1 is not applied to terminals receiving PDSCH with high actual priority, as described above. Since preemption itself means that a part of the resource region of the PDSCH with low priority can be used for the PDSCH with high priority, an additional operation is required to prevent a part of the PDSCH with high priority from being used for the PDSCH with low priority on the contrary. Accordingly, the terminal may perform an operation of using or not using the preemption indication according to a priority included in a DCI format for scheduling the PDSCH. Specifically, the following method may be performed for this operation.

The method comprises the following steps: regardless of the priority, the preemption region indicated by the preemption indication for DCI format 0_0 or 0_1 used to schedule PDSCH may be considered valid. In this case, regardless of the priority of DCI, the terminal considers that the PDSCH is not transmitted in the preemption region indicated by the indication.

The method 2 comprises the following steps: the base station may separately configure, via a higher signal, whether the preemption region indicated by the preemption indication is valid for a PDSCH scheduled based on DCI format 0_1 or DCI format 0_0 having a particular priority value.

Method 2 may be performed specifically as follows. If four values in total indicate priority, the base station can inform 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 a field indicating a priority of non-fallback DCI for scheduling a PDSCH is 2 bits, preemption may be configured to be applied to a PDSCH scheduled based on non-fallback DCI including a value of "00" or "01". Accordingly, the terminal may monitor the preemption indication and may determine that the indicated preemption indication is valid for the PDSCH (scheduled by the DCI including priority values 00 or 01). Preemption cannot be applied to PDSCH scheduled based on non-fallback DCI that includes a value of "10" or "11". Thus, the terminal may monitor for the preemption indication and may determine that the indicated preemption indication is not valid for the PDSCH.

This configuration may be performed via higher layer signals. For example, the higher layer signal may indicate information on a priority to which the preemption indication is applied or not applied, and the information on 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 higher signals whether the preemption region indicated by the preemption indication is also valid for the fallback DCI scheduling based PDSCH.

The individual search preemption indication may be skipped if the terminal receives DCI without applying a DL preemption indication. For example, the terminal may not monitor DCI format 2_1 including the preemption indication and CRC scrambled with an interrupt RNTI (INT-RNTI) by blind decoding. This is because, even if the terminal receives the preemption indication, it is more efficient to skip the preemption indication to reduce power consumption from the viewpoint of terminal operation because the preemption indication is not applicable to the PDSCH scheduled by the corresponding DCI.

A similar approach applies to UL preemption similar to DL preemption. DL preemption is information indicating that a part of the resource region of PDSCH received by the terminal corresponds to no transmission, while UL preemption is information indicating that a part of the resource region of PUSCH to be transmitted by the terminal should not be used for actual transmission. Thus, 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 transmission of the actual PUSCH. Similar to DL preemption, UL preemption can be used as information indicating that a particular resource region corresponds to no transmission. A terminal that has received UL preemption can perform the following three possible operations.

1. And if at least one part of the PUSCH resources is overlapped with the resource region indicated in the UL preemption, the terminal cancels the corresponding PUSCH transmission.

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

3. And if the scheduled PUSCH resource region is at least overlapped with the resource region indicated in the UL preemption in terms of time resources, the terminal cancels the PUSCH transmission of the overlapped resource region and all subsequent corresponding resource regions. For example, the terminal performs PUSCH transmission only in a PUSCH resource region immediately before the overlapping resource region.

Fig. 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 transmission prohibited region, the region may include a time and frequency resource region, as shown at reference numeral 626 of fig. 6A. 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 three operations described above.

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 PUSCH transmission even if the terminal acquires the UL preemption information. For example, when the terminal receives an UL grant including the highest priority information and transmits its PUSCH, the terminal may receive UL preemption in another PDCCH, and even if a resource region indicated by the preemption overlaps with a PUSCH resource region, the terminal may ignore the overlap and may transmit data in the scheduled PUSCH resource.

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 a priority level to which UL preemption can be applied. For example, if UL preemption is only applied to priority information "00" present in the DCI field, and the PUSCH scheduled based on the DCI including priority information "00" at least partially overlaps with the resource region indicated by UL preemption, the terminal may be expected to perform at least one of the three methods described above. If the terminal receives a PUSCH scheduled based on DCI including priority information other than priority information "00" and the corresponding PUSCH resource region at least partially overlaps with the resource region indicated by UL preemption, the terminal may ignore the overlap and may perform PUSCH transmission. Another possible method is that if the terminal transmits a PUSCH scheduled based on a DCI including priority information different from priority information "00", it may not detect UL preemption indication information corresponding to a corresponding resource region. (e.g., no monitoring for receiving UL preemption indication information may be performed). This is because, even if the terminal acquires the UL preemption information, the UL preemption information is not applied, so that it is possible to reduce power consumption by avoiding reception first.

Fig. 6B is a diagram illustrating an operation of a terminal that receives DCI and preemption information according to an embodiment of the present disclosure.

Referring to fig. 6B, the preemption information may be DL or UP preemption information as described above. In operation 630, the terminal first receives first DCI. The first DCI may be control information for controlling a PDSCH or a PUSCH. The terminal then receives the second DCI in operation 632. The second DCI may be DL preemption information indicating that a portion of a resource region of a PDSCH corresponds to no transmission or may be UL preemption information indicating that a portion of a resource region of a PUSCH corresponds to prohibited (or stopped) transmissions. Fig. 6B shows an example of receiving UL preemption information after receiving DCI for scheduling PUSCH, but it is possible to receive UL preemption information first.

The first DCI includes neither a separate field containing priority information nor priority information such as fallback DCI, but may configure a priority relationship with non-fallback DCI including a priority information field directly or indirectly in advance. If the base station preconfigures, via a higher signal, the second DCI indicating DL or UL preemption information only applicable to the first DCI having a specific priority value, the terminal may process the PDSCH or PUSCH scheduled in the first DCI based on information determined via the second DCI in operation 634. The processing method is consistent with the method. Information indicating a priority value may also be included, based on which the preemption indication may be applied to higher level information that enables configuration of the second DCI.

Fig. 7A is a diagram illustrating a priority relationship between a configuration granted resource and a dynamic granted resource according to an embodiment of the present disclosure.

Referring to fig. 7A, in case of periodically configuring Configuration Grant (CG) resources 700, 702, 704, and 706 supporting uplink data transmission or downlink data reception without a separate DCI, if PDSCH or PUSCH 710 scheduled based on a specific DCI 708 (i.e., dynamic grant) overlaps in at least some time and frequency, a terminal needs to determine resources that need to be given priority. First, the priority of the PDSCH or PUSCH scheduled based on a specific DCI 708 (i.e., dynamic grant) may be determined according to the DCI. As shown in fig. 4, 5A, 5B, 6A, and 6B, a method for determining priority is described. In the case where PDSCH reception or PUSCH transmission is enabled without configuration grant of DCI, the priority of data that can be transmitted or received via the configuration grant resources can be determined by the following two methods.

The method comprises the following steps: the priority of the data configuring the authorization may be determined via a higher signal. Specifically, in the case of Rel-15NR, there is a configuration grant resource (type 1 configuration grant) that can be configured and activated based on only a higher signal, and in this case, priority configuration by a higher layer signal can be applied. For example, when the base station configures the grant resources via a higher signal, information including data priority information for data transmission or data reception via the configured grant resources may be further included in the higher signal to be transmitted to the terminal. After receiving the priority information configured for each specific configuration granted resource, the terminal may transmit or receive data in the corresponding configuration granted resource only for data satisfying the corresponding priority (i.e., data having the same priority as the priority of the configuration granted resource configured via a higher signal or data having the same or higher priority as the priority of the configuration granted resource configured via a higher signal).

The method 2 comprises the following steps: the priority information may be included in DCI for activating a configuration grant. Specifically, in the case of Rel-15NR, the base station transmits basic configuration authorization configuration information to the terminal via an upper layer signal, and the terminal should receive DCI including additional activation information in order to transmit or receive actual data. This is referred to as type 2 configuration authorization. If the priority-related information is included in the DCI information, the terminal may determine the priority of the data through a configuration grant activated through the priority information.

As shown in table 5, the type 2 configuration grant may be activated by DCI format 0_0 or DCI format 0_ 1. Specifically, in case of the type 2 configuration grant, in DCI format 0_1 which is a non-fallback DCI, priority information of the type 2 configuration grant is indicated by a priority field included in the DCI, and since DCI format 0_0 which is a fallback DCI does not have a separate priority field, priority may be determined by at least one of the methods described in fig. 5A and 5B.

[ Table 5]

	DCI format 0_0	DCI format 0_1
			HARQ process number	Is set to be all '0'	Is set to be all '0'
Redundancy version	Is provided to '00'	Is provided to '00'
			Priority level	Not applicable (Default priority)	XXX

The priority of the PDSCH received via the configuration grant or the priority of the PUSCH transmitted via the configuration grant may be determined according to the above-described method. Thus, if PDSCH (or PUSCH)710 scheduled based on dynamic grant 708 overlaps PDSCH 700, 702, 704, and 706 (or transmitted PUSCH) received according to configured grant 706 (e.g., in the case of 704 and 706), the terminal may compare the respective priorities to be able to receive only PDSCH with higher priority (or transmit only PUSCH with higher priority). For example, the terminal does not receive (or transmit) the PDSCH (or PUSCH) having a low priority. Here, the case of receiving the PDSCH means that ACK or NACK information is transmitted via HARQ-ACK resources corresponding to the ACK or NACK information. Further, the failure to receive the PDSCH may indicate that HARQ-ACK information itself may not be transmitted if HARQ-ACK information corresponding to the PDSCH is indicated as NACK, or if there are only HARQ-ACK resources for the PDSCH.

The specifically described case may be applied to a case where the terminal cannot simultaneously receive two or more PDSCHs (or transmit PUSCHs). If the terminal is capable of receiving two or more PDSCHs (or transmitting PUSCHs), PDSCHs (or PUSCHs) that can be simultaneously processed may be received (or transmitted) for each priority. For example, in case that the terminal is capable of simultaneously receiving two PDSCHs, if a total of three PDSCH resource regions (including two PDSCH resource regions scheduled via dynamic grant and one PDSCH resource region configured via configuration grant) overlap each other on at least one symbol, the terminal may receive two PDSCHs having high priority without receiving one PDSCH having lowest priority. Therefore, the terminal receives two PDSCHs of high priority and reports whether its HARQ-ACK information is ACK or NACK to the base station. Further, the terminal may not receive one PDSCH with the lowest priority and indicate HARQ-ACK information corresponding to the PDSCH as NACK and transmit it to the base station, or the terminal itself does not perform HARQ-ACK transmission.

The terminal may perform retransmission on the PUSCH transmitted via the configuration grant, which is possible by the base station transmitting DCI including CRC scrambled with configuration scheduling RNTI (CS-RNTI) to the terminal. If the configuration grant includes priority information, the base station may transmit a retransmission request for a PUSCH to the terminal based on DCI including CRC scrambled with CS-RNTI, wherein the DCI may or may not include the priority information. In this case, there may be a problem as to whether the priority value of DCI for scheduling data retransmission should be equal to the priority of the configuration grant. To solve this problem, the configuration grant including the priority information may be subjected to retransmission scheduling by the following method.

The method comprises the following steps: the retransmission scheduling may be based on all DCIs, regardless of the priority value associated with the configuration grant.

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

The method 2 comprises the following steps: retransmission scheduling is possible based only on DCI corresponding to a priority value associated with a configuration grant.

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

Fig. 7B is a diagram illustrating an operation of a terminal in a case where an overlap (or collision) occurs between a configuration granted resource and a dynamic granted resource according to an embodiment of the present disclosure.

Referring to fig. 7B, the terminal receives a configuration of the configuration grant through a higher signal from the base station in operation 720. In 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 resource, and in case of SPS, the terminal periodically receives downlink data. When the base station transmits a dynamic grant via signal L1 and the terminal receives information in its operation 722, the terminal confirms in operation 724 that the resource indicated by the corresponding dynamic grant overlaps with at least a portion of the preconfigured configuration grant or SPS resource.

If the terminal supports only one PUSCH transmission or one (for unicast) PDSCH reception, a problem may occur that one of the two should be selected for transmission/reception. In contrast, if the terminal supports two or more PUSCH transmissions or two or more PDSCH receptions, all transmission and reception may be performed without selecting data to be transmitted or received. However, the above selection problem may occur if the configured grant and the dynamically granted configured and scheduled PUSCH resources are more than the number of PUSCHs capable of multiple transmissions simultaneously that the terminal can support. Similarly, the above selection problem may occur if the PDSCH resources configured and scheduled by SPS and dynamic grant are more than the number of PUSCH capable of multiple simultaneous transmissions that the terminal may support.

According to the priority information values described in fig. 7B, the terminal transmits data via the PUSCH resources configured with the configuration grant or the PUSCH resources scheduled with the dynamic grant in operation 726. If priority information between the PUSCHs configured via the configuration grant and the dynamic grant is the same, the terminal transmits uplink data via the PUSCH scheduled with the dynamic grant. In other words, the transmission is cancelled (or dropped) by the PUSCH with the configuration grant or the dynamic grant of the low priority information.

In case that PUCCH resources previously configured to the terminal via a higher signal or scheduled to the terminal via a signal L1(DCI) overlap with PUSCH resources configured via a configuration grant and PUSCH resources scheduled via a dynamic grant in at least one OFDM symbol, Uplink Control Information (UCI) may be piggybacked on a PUSCH and transmitted if a PDSCH associated with the PUCCH has the same priority information value as that of the PUSCH. Alternatively, if the terminal has a capability of performing transmission of only one PUCCH or PUSCH, the terminal may transmit only the PUCCH or PUSCH having a high priority and may drop the PUCCH or PUSCH having a low priority.

For example, if a PUCCH resource in which HARQ-ACK information having a priority information value of 1 for a PDSCH is to be transmitted and a PUSCH resource previously configured (or scheduled via a dynamic grant) based on a higher signal or signal L1 via a configuration grant having a priority information value of 2 overlap in at least one OFDM symbol, in case of the configuration grant, if there is data to be transmitted via the configuration grant, the terminal discards the HARQ-ACK information and transmits a PUSCH. As another example, if a PUCCH resource in which HARQ-ACK information having a priority information value of 1 for a PDSCH is to be transmitted overlaps a PUSCH resource previously configured (or scheduled via a dynamic grant) based on a higher signal or signal L1 via a configuration grant having a priority information value of 1 in at least one OFDM symbol, in case of the configuration grant, if there is data to be transmitted via the configuration grant, the terminal piggybacks the HARQ-ACK information to the PUSCH so as to transmit it. For reference, the example is applied when it is assumed that a higher priority value results in a higher priority, and vice versa.

Also, according to the priority information values described in fig. 7B, the terminal receives 726 data in descending order of priority information via PDSCH resources based on SPS configuration or PDSCH resources based on dynamic grant scheduling. If priority information between the PDSCH configured via the SPS and the dynamic grant is the same, the terminal receives downlink data via the PDSCH scheduled based on the dynamic grant. In other words, for PDSCH with low priority information according to SPS or dynamic grant, the terminal cancels (or drops) PDSCH reception. For example, in case three unicast PDSCHs can be received simultaneously, the terminal schedules each PDSCH via one SPS having a priority value of 2 and a dynamic grant having a priority value of 1, 2 or 3, and if four PDSCH resources overlap in at least one OFDM symbol, the terminal discards the PDSCH scheduled via the dynamic grant having the lowest priority value of 1.

Fig. 7B shows PUSCH transmission, but as described above, this may also apply to PDSCH reception.

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

Referring to fig. 8, the MCS table is a table describing a modulation order, a target code rate, and spectral efficiency according to an MCS index indicated by DCI, as shown in the following table 6. Table 6 below is an example of an MCS table for PDSCH, and there may be a plurality of MCS tables. If different MCS tables are used, the indicated modulation order, target code rate and spectral efficiency may be different even if the same MCS index is indicated.

[ Table 6]

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 particular service, the terminal can determine the particular MCS table to use based on the priority information in the DCI field.

Specifically, when the base station configures priority information of a DCI field in advance, an MCS table implicitly associated with each piece of priority information may be configured via a higher layer. For example, if priority information of a total of 2 bits is included in the DCI, the base station may perform configuration via a higher signal, wherein the 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 may 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.

Referring to fig. 8, a terminal receives 800DCI and determines which condition of a and B is satisfied. If the DCI transmitted by the base station satisfies 802 condition a (i.e., the 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 the MCS index to be configured based on MCS table a. If condition B is satisfied 804 (i.e., 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.

Fig. 9 is a block diagram illustrating a structure of a terminal capable of performing according to an embodiment of the present disclosure.

Referring to fig. 9, a terminal of the present disclosure may include a terminal receiver 900, a terminal transmitter 904, and a terminal processor 902. Terminal receiver 900 and terminal transmitter 904 may be collectively referred to as a transceiver. The transceiver may transmit signals to or receive signals from a base station. The signals may include control information and data. To this end, the transceiver may include an RF transmitter configured to perform up-conversion and amplification of a frequency of a transmission signal, an RF receiver configured to perform low-noise amplification of a reception signal and down-conversion of a frequency of a reception signal, and the like. Further, the transceiver may receive signals via a wireless channel, may output signals to the terminal processor 902, and may transmit signals output from the terminal processor 902 via the wireless channel. The terminal processor 902 may control a series of processes so that the terminal may operate according to the above-described embodiments.

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

Referring to fig. 10, in an embodiment of the present disclosure, a 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 transmit signals to or receive signals from the terminal. The signals may include control information and data. To this end, the transceiver may include an RF transmitter configured to perform up-conversion and amplification of a frequency of a transmission signal, an RF receiver configured to perform low-noise amplification of a reception signal and down-conversion of a frequency of a reception signal, and the like. Further, the transceiver may receive a signal via a wireless channel, may output a signal to the base station processor 1003, and may transmit a signal output from the base station processor 1003 via the wireless channel. The base station processor 1003 may control a series of processes so that the base station operates according to the above-described embodiments of the present disclosure.

The embodiments of the present disclosure described and illustrated in the specification and drawings are presented to easily explain technical contents of the present disclosure and to assist understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. For example, it is apparent to those skilled in the art that other modifications and variations can be made thereto based on the technical spirit of the present disclosure. Further, the above-described respective embodiments may be used in combination as necessary. For example, embodiments of the present disclosure may be combined in part to operate a base station and a terminal. Further, although the above embodiments have been described by the NR system, other variations based on the technical idea of the embodiments may be implemented in other systems, such as the FDD or TDD LTE system.

While the 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 therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.