CN111543023B

CN111543023B - Method and apparatus for transmitting uplink data

Info

Publication number: CN111543023B
Application number: CN201980007401.0A
Authority: CN
Inventors: 朴奎镇
Original assignee: KT Corp
Current assignee: KT Corp
Priority date: 2018-02-14
Filing date: 2019-02-13
Publication date: 2023-09-26
Anticipated expiration: 2039-02-13
Also published as: KR20190098708A; KR102320416B1; CN111543023A

Abstract

Disclosed in this embodiment is a method and apparatus for transmitting uplink data according to uplink cancellation indication information in a next generation wireless network, and in one embodiment, a method for transmitting uplink data by a terminal is provided, comprising the steps of: transmitting uplink data based on the uplink data resource allocation information; monitoring uplink cancellation indication information based on the monitoring configuration information on the uplink cancellation indication information; receiving uplink cancellation indication information; and suspending ongoing transmission of uplink data according to the uplink cancellation indication information.

Description

Method and apparatus for transmitting uplink data

Technical Field

The present disclosure relates to methods and apparatus for transmitting uplink data in a next generation/5G radio access network (hereinafter, referred to as new radio "NR").

Background

Recently, the third generation partnership project (3 GPP) has approved "research on new radio access technologies", which is one research project for researching next generation/5G radio access technologies (hereinafter referred to as "new radio" or "NR"). Based on the research on the new radio access technology, the radio access network working group 1 (RAN WG 1) has discussed a frame structure, channel coding and modulation, waveforms, multiple access methods, etc. for the New Radio (NR). There is a need for NR designs that not only provide improved data transmission rates compared to Long Term Evolution (LTE)/LTE-advanced, but also meet various requirements in specific and specific usage scenarios.

Enhanced mobile broadband (emmbb), mass machine type communication (mctc), and Ultra Reliable Low Latency Communication (URLLC) are proposed as typical usage scenarios for NR. To meet the needs of each scenario, it is required to design NR so as to have a flexible frame structure compared to LTE/LTE-advanced.

Since demands for data rates, time delays, reliability, coverage, and the like are different from each other, it is necessary to provide a method of efficiently multiplexing radio resource units based on mutually different parameter sets (numerology), for example, subcarrier spacing, subframes, transmission Time Intervals (TTI), and the like, as a method for efficiently satisfying each usage scenario demand by constituting a frequency band of an arbitrary NR system.

Disclosure of Invention

Technical problem

At least one object of the present disclosure is to provide a method of transmitting uplink data according to uplink cancellation indication information in NR.

Technical proposal

According to one aspect of the present disclosure, a method for a user equipment or terminal (hereinafter referred to as "user equipment" or "UE") to transmit uplink ("UL") data is provided. The method may include: transmitting UL data based on UL data resource allocation information; monitoring UL cancellation indication information based on the monitoring configuration information on the UL cancellation indication information; receiving UL cancellation indication information; and suspending ongoing UL data transmission based on the UL cancellation indication information.

According to another aspect of the present disclosure, there is provided a method of a base station for controlling UL data transmission of a UE. The method may include: configuring monitoring configuration information regarding UL cancellation indication information; transmitting the monitoring configuration information to the UE transmitting UL data; and transmitting UL cancellation indication information based on the monitoring configuration information.

According to another aspect of the present disclosure, there is provided a UE for transmitting UL data. The UE may include: a transmitter that transmits UL data based on UL data resource allocation information; a controller that monitors UL cancellation indication information based on the monitoring configuration information regarding the UL cancellation indication information and suspends ongoing UL data transmission based on the UL cancellation indication information; and a receiver that receives the UL cancellation indication information.

Effects of the invention

Embodiments of the present disclosure provide a method of transmitting UL data according to UL cancellation indication information in NR.

Drawings

Fig. 1 schematically illustrates an NR wireless communication system according to an embodiment of the present disclosure.

Fig. 2 schematically illustrates a frame structure in an NR system according to an embodiment of the present disclosure.

Fig. 3 illustrates a resource grid supported by a radio access technology according to an embodiment of the present disclosure.

Fig. 4 illustrates portions of bandwidth supported by a radio access technology according to an embodiment of the present disclosure.

Fig. 5 illustrates an example of a synchronization signal block in a radio access technology according to an embodiment of the present disclosure.

Fig. 6 is a signal diagram for explaining a random access procedure in a radio access technology according to an embodiment of the present disclosure.

Fig. 7 shows CORESET.

Fig. 8 illustrates an example of symbol-level alignment in different subcarrier spacings (SCS) in accordance with an embodiment of the disclosure.

Fig. 9 schematically illustrates a bandwidth portion according to an embodiment of the present disclosure.

Fig. 10 illustrates one example of UL cancellation according to an embodiment of the present disclosure.

Fig. 11 illustrates another example of UL cancellation according to an embodiment of the present disclosure.

Fig. 12 illustrates another example of UL cancellation according to an embodiment of the present disclosure.

Fig. 13 illustrates yet another example of UL cancellation according to an embodiment of the present disclosure.

Fig. 14 is a flowchart illustrating a procedure in which a UE suspends UL data transmission according to UL cancellation indication information according to an embodiment of the present disclosure.

Fig. 15 is a flowchart illustrating a procedure in which a base station controls UL data transmission of a UE according to UL cancellation indication information according to an embodiment of the present disclosure.

Fig. 16 is a block diagram illustrating a base station according to an embodiment of the present disclosure.

Fig. 17 is a block diagram illustrating a UE according to an embodiment of the present disclosure.

Detailed Description

Some embodiments of the present disclosure will be described in detail below with reference to the exemplary drawings. In the drawings, like reference numerals are used to refer to like elements throughout the drawings even though they are shown on different drawings. Furthermore, in the following description of the present disclosure, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present disclosure unclear. When the expressions "comprising," "having," "including," and the like are used herein, any other portion may also be added unless the expression "only" is used. When an element is referred to in the singular, the plural is intended to cover the plural unless specifically stated to the element.

Further, terms such as first, second, A, B, (a), (B) and the like may be used herein in describing components of the present disclosure. Each of these terms is not intended to define the essence, sequence, or order of the corresponding components, but is merely used to distinguish the corresponding components from other components. When describing the positional relationship between components, if two or more components are described as being "connected," "combined," or "coupled" to each other, it is to be understood that the two or more components may be directly "connected," "combined," or "coupled" to each other, or may be "connected," "combined," or "coupled" to each other with another component "interposed" therebetween. In this case, the other component may be included in at least one of the two or more components that are "connected", "combined", or "coupled" with each other.

In describing the sequence of operations or manufacturing methods, for example, the use of expressions "after," "subsequent," "following," "preceding," etc. may also cover instances where the operations or processes are not performed continuously, unless "immediate" or "direct" is used in the expressions. The numerical values referred to herein for components or information corresponding thereto (e.g., levels, etc.) may be construed as including ranges of error due to various factors (e.g., process factors, internal or external influences, noise, etc.), even if no explicit description is provided of this.

The wireless communication system in this specification refers to a system for providing various communication services such as a voice service and a data service using radio resources. A wireless communication system may include User Equipment (UE), base stations, core networks, and so forth.

The embodiments disclosed below may be applied to wireless communication systems using various radio access technologies. For example, embodiments may be applied to various radio access technologies such as Code Division Multiple Access (CDMA), frequency Division Multiple Access (FDMA), time Division Multiple Access (TDMA), orthogonal Frequency Division Multiple Access (OFDMA), single carrier frequency division multiple access (SC-FDMA), non-orthogonal multiple access (NOMA), and so forth. In addition, radio access technologies may refer to corresponding generation communication technologies established by various communication organizations, such as third generation partnership project (3 GPP), 3GPP2, wifi, bluetooth, institute of Electrical and Electronics Engineers (IEEE) or International Telecommunications Union (ITU), etc., as well as specific access technologies. For example, CDMA may be implemented as a wireless technology such as Universal Terrestrial Radio Access (UTRA) or CDMA 2000. TDMA may be implemented as a wireless technology such as global system for mobile communications (GSM)/General Packet Radio Service (GPRS)/enhanced data rates for GSM evolution (EDGE). OFDMA may be implemented as a wireless technology such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, evolved UTRA (E-UTRA). IEEE 802.16m is an evolution of IEEE 802.16e that provides backward compatibility with IEEE 802.16 e-based systems. UTRA is part of Universal Mobile Telecommunications System (UMTS). 3GPP (third Generation partnership project) LTE (Long term evolution) is a part of E-UMTS (evolved UMTS) that uses evolved-UMTS terrestrial radio Access (E-UTRA), which employs OFDMA in the downlink and SC-FDMA in the uplink. As described above, embodiments may be applied to radio access technologies that have been enabled or commercialized. Furthermore, embodiments may also be applied to radio access technologies being developed or to be developed in the future.

A UE as used in this specification must be construed in a broad sense indicating a device comprising a wireless communication module in communication with a base station in a wireless communication system. For example, the UE includes a User Equipment (UE) in WCDMA, LTE, NR, HSPA, IMT-2020 (5G or new radio) or the like, a mobile station in GSM, a User Terminal (UT), a Subscriber Station (SS), a wireless device or the like. Further, the UE may be a portable user equipment such as a smart phone, or the UE may be a vehicle in a V2X communication system, a device containing a wireless communication module in the vehicle, etc. (depending on the type of use thereof). In the case of a Machine Type Communication (MTC) system, a UE may refer to an MTC terminal, an M2M terminal, or a URLLC terminal, which employs a communication module capable of performing machine type communication.

A base station or cell in this specification refers to an end communicating with UEs through a network that encompasses various coverage areas such as node bs, evolved node bs (enbs), gnode bs, low Power Nodes (LPNs), sectors, sites, various types of antennas, base Transceiver Systems (BTSs), access points, points (e.g., transmission points, reception points, or transmission/reception points), relay nodes, megacells, macrocells, microcells, picocells, femtocells, remote Radio Heads (RRHs), radio frequency units (RUs), small cells, and so forth. In addition, a cell may be used as a meaning including a bandwidth part (BWP) in a frequency domain. For example, the serving cell may refer to active BWP of the UE.

The various cells listed above are provided with a base station controlling one or more cells, which can be interpreted in two meanings. The base station may be 1) a device for providing a megacell, macrocell, microcell, picocell, femtocell, or microcell in conjunction with the wireless region, or the base station may be 2) the wireless region itself. In the above description 1), the base station may be a plurality of devices controlled by the same entity and providing a predetermined wireless area, or all devices that interact with each other and cooperatively configure the wireless area. For example, the base station may be one point, a transmission/reception point, a transmission point, a reception point, etc., depending on the configuration method of the wireless area. In the above description 2), a base station may be a wireless area that may support a User Equipment (UE) to transmit data to and receive data from other UEs or neighboring base stations.

In this specification, a cell may refer to a coverage of a signal transmitted from a transmission/reception point, a component carrier having a coverage of a signal transmitted from a transmission/reception point (or a transmission point), or a transmission/reception point itself.

The Uplink (UL) refers to data transmission and reception from the UE to the base station, and the Downlink (DL) refers to data transmission and reception from the base station to the UE. The downlink may refer to communication or communication paths from the plurality of transmission/reception points to the UE, and the uplink may refer to communication or communication paths from the UE to the plurality of transmission/reception points. In the downlink, a transmitter may be part of a plurality of transmission/reception points, and a receiver may be part of a UE. Further, in the uplink, the transmitter may be part of the UE and the receiver may be part of a plurality of transmission/reception points.

Uplink and downlink transmit and receive control information on control channels, such as a Physical Downlink Control Channel (PDCCH) and a Physical Uplink Control Channel (PUCCH). The uplink and downlink transmit and receive data on data channels, such as a Physical Downlink Shared Channel (PDSCH) and a Physical Uplink Shared Channel (PUSCH). Hereinafter, transmission and reception of a signal on a channel such as PUCCH, PUSCH, PDCCH, PDSCH may be denoted as "transmission and reception PUCCH, PUSCH, PDCCH, PDSCH and the like".

For clarity, the following description will focus on a 3GPP LTE/LET-A/NR (New radio) communication system, but technical features of the present disclosure are not limited to the corresponding communication system.

After researching 4G (fourth generation) communication technologies, 3GPP is developing 5G (fifth generation) communication technologies in order to meet the needs of the next generation radio access technologies of ITU-R. In particular, 3GPP is developing LTE-A pro as a 5G communication technology by improving LTE-advanced technology to conform to the requirements of ITU-R and a new NR communication technology that is completely different from 4G communication technology. LTE-a pro and NR both refer to 5G communication technologies. Hereinafter, unless a specific communication technology is specified, a 5G communication technology will be described on the basis of NR.

Considering the various operating scenarios defined in NR in view of satellites, automobiles, new industries, etc. in a typical 4G LTE scenario, in order to support an enhanced mobile broadband (eMBB) scenario in terms of services, a mass machine type communication (emtc) scenario in which UEs span a wide area with high UE density and thus require low data rates and asynchronous connections, and an ultra-reliability low latency (URLLC) scenario, which requires high responsiveness and reliability and supports high-speed mobility.

To meet these scenarios, NR introduces a wireless communication system employing a new waveform and frame structure technique, a low latency technique, an ultra-high band (millimeter wave) support technique, and a forward compatibility providing technique. In particular, NR systems have various technical variations in terms of flexibility in order to provide forward compatibility. The main technical features of NR will be described below with reference to the drawings.

< NR System overview >

Fig. 1 schematically shows an NR system.

Referring to fig. 1, the nr system is divided into a 5G core network (5 GC) and NG-RAN part. The NG-RAN includes a gNB and a NG-eNB that provide a user plane (SDAP/PDCP/RLC/MAC/PHY) and a User Equipment (UE) control plane (RRC) protocol side. Multiple gNBs or gNBs are interconnected with the ng-eNB through an Xn interface. The gNB and NG-eNB are connected to the 5GC via NG interfaces, respectively. The 5GC may be configured to include an access and mobility management function (AMF) for managing a control plane such as a UE connection and mobility control function, and a User Plane Function (UPF) for controlling user data. NR supports a frequency band below 6GHz (frequency range 1: FR1) and a frequency band equal to or greater than 6GHz (frequency range 2: FR2).

The gNB represents a base station providing NR user plane and control plane protocol ends to the UE. The ng-eNB represents a base station providing the UE with the E-UTRA user plane and control plane protocol ends. The base stations described in this specification should be understood to cover both gNB and ng-eNB. However, base stations may also be used to refer to gNB or ng-NB separately from each other, as desired.

< NR waveform, parameter set (numerology) and frame Structure >

NR uses a Cyclic Prefix (CP) -OFDM waveform with a cyclic prefix for downlink transmission and CP-OFDM or discrete fourier transform spread spectrum (DFT-s) -OFDM for uplink transmission. OFDM technology is easily combined with multiple-input multiple-output (MIMO) schemes and allows the use of low complexity receivers and has high frequency efficiency.

Since the above three scenarios have mutually different demands in NR for data rate, delay rate, coverage, and the like, it is necessary to efficiently satisfy the demands of each scenario on the frequency band constituting the NR system. For this reason, a technique for efficiently multiplexing radio resources based on a plurality of different parameter sets is proposed.

Specifically, the NR transmission parameter set is determined based on the subcarrier spacing and the Cyclic Prefix (CP), and as shown in table 1 below, "μ" is used as an index value of 2, which varies exponentially based on 15 kHz.

TABLE 1

As shown in table 1 above, NR may have five parameter sets according to subcarrier spacing. This is different from LTE, which is one of 4G communication technologies, in which the subcarrier spacing is fixed to 15kHz. Specifically, in NR, the subcarrier spacing for data transmission is 15, 30, 60, or 120kHz, and the subcarrier spacing for synchronization signal transmission is 15, 30, 120, or 240kHz. Further, the extended CP is applied only to a subcarrier spacing of 60 kHz. In NR, a frame is defined to include 10 subframes and have a length of 10ms, and each subframe has the same length of 1 ms. One frame may be divided into 5ms half frames, each half frame including 5 subframes. In case of a subcarrier spacing of 15kHz, one subframe includes one slot, each slot including 14 OFDM symbols. Fig. 2 shows a frame structure in the NR system. Referring to fig. 2, one slot includes 14 OFDM symbols, which are fixed in the case of a normal CP, but the length of the slot in the time domain may vary according to the subcarrier spacing. For example, in the case of a parameter set with a subcarrier spacing of 15kHz, the slots are configured to have the same 1ms length as the subframes. On the other hand, in the case of a parameter set having a subcarrier spacing of 30kHz, a slot includes 14 OFDM symbols, but one subframe may include two slots each having a length of 0.5 ms. That is, subframes and frames may be defined using a fixed time length, and slots may be defined according to the number of symbols such that the time length thereof varies with the subcarrier spacing.

NR defines the basic unit of scheduling as a slot and also introduces mini-slots (or sub-slots or non-slot based scheduling) in order to reduce the transmission delay of a radio sector. If a wide subcarrier spacing is used, the length of one slot is reduced in inverse proportion, thereby reducing transmission delay in the radio sector. Mini-slots (or sub-slots) are intended to efficiently support the URLLC scenario, and mini-slots may be scheduled in 2, 4, or 7 symbol units.

Furthermore, unlike LTE, NR defines uplink and downlink resource allocation as symbol level in one slot. In order to reduce the HARQ delay, a slot structure capable of directly transmitting HARQ ACK/NACK in a transmission slot has been defined. This slot structure is referred to as a "self-contained structure" to be described.

NR is designed to support a total of 256 slot formats, and 62 slot formats are used in 3GPP Rel-15. In addition, NR supports a common frame structure constituting an FDD or TDD frame by a combination of various slots. For example, NR supports i) a slot structure in which all symbols of a slot are configured for downlink, ii) a slot structure in which all symbols are configured for uplink, and iii) a slot structure in which downlink symbols and uplink symbols are mixed. In addition, NR supports data transmission scheduled to be distributed over one or more time slots. Accordingly, the base station may use a Slot Format Indicator (SFI) to inform the UE whether the slot is a downlink slot, an uplink slot, or a flexible slot. The base station may inform the slot format by indicating an index of a table configured through UE-specific RRC signaling using the SFI. Further, the base station may dynamically indicate the slot format using Downlink Control Information (DCI), or may statically or quasi-statically indicate the slot format through RRC signaling.

< physical resources of NR >

Regarding physical resources in NR, antenna ports, resource grids, resource elements, resource blocks, bandwidth parts, etc. are considered.

An antenna port is defined as a channel carrying another symbol on the same antenna port inferred from the channel carrying the symbol on the antenna port. If the massive nature of the channel carrying the symbol on one antenna port can be inferred from another channel carrying the symbol on another antenna port, then the two antenna ports may have a quasi co-located or quasi co-located (QC/QCL) relationship. The large scale characteristics include at least one of delay spread, doppler spread, frequency shift, average received power, and received timing.

Referring to fig. 3, a resource grid may exist according to respective parameter sets because NRs support multiple parameter sets in the same carrier. Furthermore, the existence of the resource grid depends on the antenna ports, subcarrier spacing and transmission direction.

The resource block includes 12 subcarriers and is defined only in the frequency domain. Further, the resource elements include one OFDM symbol and one subcarrier. Thus, as shown in fig. 3, the size of one resource block may vary according to the subcarrier spacing. Also, "point a", a common resource block, and a virtual resource block, which serve as a common reference point of the resource block grid, are defined in NR.

Unlike in LTE, where the carrier bandwidth is fixed at 20MHz, in NR, the maximum carrier bandwidth is configured to be 50MHz to 400MHz depending on the subcarrier spacing. Therefore, it is not assumed that all UEs use the entire carrier bandwidth. Accordingly, as shown in fig. 4, in NR, bandwidth parts (BWP) may be designated within a carrier bandwidth so that the UE can use the bandwidth parts. Further, the bandwidth portion may be associated with one parameter set, may comprise a subset of consecutive common resource blocks, and may be dynamically activated over time. The UE has up to four bandwidth parts in each of the uplink and downlink, and the UE transmits and receives data using the active bandwidth parts in a given time.

In the case of paired spectrum, the uplink and downlink bandwidth portions are independently configured. In the case of unpaired spectrum, the downlink bandwidth portion and the uplink bandwidth portion are paired so as to share the center frequency in order to prevent unnecessary frequency retuning between downlink and uplink operations.

< initial Access in NR >

In NR, the UE performs cell search and random access procedures to access and communicate with a base station.

The cell search is: a process of synchronizing a UE with a cell of a corresponding base station by using a Synchronization Signal Block (SSB) transmitted from the base station and acquiring a physical layer cell ID and system information.

Referring to fig. 5, the ssb includes a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) occupying one symbol and 127 subcarriers, and a PBCH spanning three OFDM symbols and 240 subcarriers.

The UE monitors the SSB in the time and frequency domains, thereby receiving the SSB.

SSBs may be sent up to 64 times in 5 ms. Multiple SSBs are transmitted over different transmit beams in 5ms time, and the UE assumes detection based on the particular beam used for transmission transmitting SSBs once every 20 ms. The number of beams that can be used for SSB transmission within 5ms can increase with increasing frequency band. For example, up to 4 SSB beams may be transmitted on a frequency band of 3GHz or less, and up to 8 SSB beams may be transmitted on a frequency band of 3 to 6 GHz. Furthermore, up to 64 different beams may be used to transmit SSBs on a frequency band of 6GHz or higher.

One slot includes two SSBs, and the start symbol and the number of repetitions in the slot are determined according to the subcarrier spacing as follows.

Unlike SSs in a typical LTE system, SSBs are not transmitted at the center frequency of the carrier bandwidth. That is, SSBs may also be transmitted at frequencies other than the center of the system band, and multiple SSBs may be transmitted in the frequency domain with wideband operation supported. Accordingly, the UE monitors the SSB using a synchronization grid, which is a candidate frequency location for monitoring the SSB. The carrier grid and the synchronization grid are center frequency location information of a channel for initial connection newly defined in NR, and the synchronization grid can support fast SSB search of the UE because its frequency spacing is configured wider than that of the carrier grid.

The UE may acquire MIB on PBCH of SSB. MIB (master information block) includes minimum information of Remaining Minimum System Information (RMSI) for a UE to receive network broadcasting. In addition, the PBCH may include information about the first DM-RS symbol position in the time domain, information for the UE to monitor SIB1 (e.g., SIB1 parameter set information, SIB1 CORESET related information, search space information, PDCCH related parameter information, etc.), offset information between the common resource block and the SSB (absolute SSB position in the carrier is transmitted through SIB 1), and so on. The SIB1 parameter set information is also applied to some messages used in a random access procedure for the UE to access the base station after the cell search procedure is completed. For example, the parameter set information of SIB1 may be applied in at least one of messages 1 to 4 for the random access procedure.

The RMSI described above may refer to SIB1 (system information block 1), and SIB1 is periodically (e.g., 160 ms) broadcast in a cell. SIB1 includes information required for the UE to perform an initial random access procedure, and SIB1 is periodically transmitted on the PDSCH. In order to receive SIB1, the UE must receive parameter set information for SIB1 transmission and CORESET information for scheduling SIB1 on the PBCH. The UE uses the SI-RNTI in CORESET to identify scheduling information for SIB1. And the UE acquires SIB1 on the PDSCH according to the scheduling information. The remaining SIBs other than SIB1 may be periodically transmitted, or the remaining SIBs may be transmitted according to a request of the UE.

Fig. 6 shows a random access procedure in a radio access technology.

Referring to fig. 6, if cell search is completed, the UE transmits a random access preamble for random access to the base station. The random access preamble is transmitted on the PRACH. In particular, the random access preamble is periodically transmitted to the base station on a PRACH comprising consecutive radio resources in repeated specific time slots. In general, when a UE initially accesses a cell, a contention-based random access procedure is performed, and when the UE performs random access for Beam Failure Recovery (BFR), a non-contention-based random access procedure is performed.

The UE receives a random access response to the transmitted random access preamble. The random access response may include a random access preamble Identifier (ID), UL grant (uplink radio resource), temporary C-RNTI (temporary cell-radio network temporary identifier), and TAC (time alignment command). Since one random access response may include random access response information for one or more UEs, a random access preamble identifier may be included to indicate which UE the included UL grant, temporary C-RNTI, and TAC are valid for. The random access preamble identifier may be an identifier of a random access preamble received by the base station. The TAC may include information as means for the UE to adjust uplink synchronization. The random access response may be indicated by a random access identifier on the PDCCH, that is, a random access-radio network temporary identifier (RA-RNTI).

In response to receiving the valid random access response, the UE processes information included in the random access response and performs scheduled transmission to the base station. For example, the UE applies TAC and stores temporary C-RNTI. In addition, the UE transmits data stored in a buffer of the UE or newly generated data to the base station using UL grant. In this case, information identifying the UE must be included in the data.

Finally, the UE receives the downlink message to resolve the contention.

The downlink control channel in NR is transmitted in CORESET (control resource set) of 1 to 3 symbols in length, and the downlink control channel transmits uplink/downlink scheduling information, SFI (slot format index), TPC (transmit power control) information, and the like.

As mentioned above, NR has introduced the concept of CORESET to ensure flexibility of the system. CORESET refers to the time-frequency resources used for the downlink control signals. The UE may decode the control channel candidates using one or more search spaces in the CORESET time-frequency resources. The CORESET specific QCL (quasi co-location) hypothesis is configured and used to provide information about the analog beam direction, as well as the characteristics of delay spread, doppler shift and average delay, which are all assumed by the existing QCL.

Fig. 7 shows CORESET.

Referring to fig. 7, CORESET may exist in various forms within a carrier bandwidth within a single slot, and CORESET may include up to 3 OFDM symbols in the time domain. Further, CORESET is defined as a multiple of 6 resource blocks up to the carrier bandwidth in the frequency domain.

A first CORESET, as part of the initial bandwidth portion, is specified (e.g., indicated, allocated) by the MIB to receive additional configuration information and system information from the network. After establishing a connection with the base station, the UE may receive and configure one or more pieces of CORESET information through RRC signaling.

In this specification, frequencies, frames, subframes, resources, resource blocks, regions, bands, sub-bands, control channels, data channels, synchronization signals, various reference signals related to NR (new radio), various signals, or various messages may be interpreted as meanings used currently or in the past, or as various meanings to be used in the future.

NR (New radio)

NR is required to be designed not only to provide an improved data transmission rate, but also to meet various QoS requirements for each specific and specific usage scenario, as compared to LTE/LTE-advanced. In particular, enhanced mobile broadband (emmbb), mass machine type communication (mctc), and ultra-reliable and low latency communication (URLLC) are defined as representative usage scenarios for NR. To meet the needs of each usage scenario, NR is required to be designed to have a more flexible frame structure than LTE/LTE-advanced.

Because each usage scenario imposes different demands on data rate, latency, coverage, etc., there is a need for a method of efficiently multiplexing mutually different radio resource units based on parameter sets (e.g., subcarrier spacing (SCS), subframes, transmission Time Intervals (TTI), etc.), as a solution to efficiently meet the demands of different usage scenarios on the frequency band provided to the NR system.

To this end, i) a method of multiplexing parameter sets having mutually different subcarrier spacing (SCS) based on TDM, FDM, or TDM/FDM on one NR carrier, and ii) a method of supporting one or more time units when scheduling units in the time domain are configured have been discussed. In this regard, in NR, the definition of a subframe has been given as a type of time domain structure. Further, as a reference parameter set for defining a corresponding subframe duration, similar to LTE, a single subframe duration is defined as 14 OFDM symbols with normal CP overhead based on 15kHz subcarrier spacing (SCS). Thus, the subframe of NR has a duration of 1 ms.

Unlike LTE, since the subframe of NR is an absolute reference duration, slots and mini-slots may be defined as time units for actual UL/DL data scheduling. In this case, the number of OFDM symbols (value of y) constituting a slot is defined as y=14, regardless of the parameter set.

Thus, a slot may be made up of 14 symbols. Depending on the transmission direction of the corresponding slot, all symbols may be used for DL or UL transmission, or the symbols may be used in the configuration of DL part + gap + UL part.

Further, mini-slots have been defined to consist of fewer symbols than slots in the parameter set (or SCS), as a result of which short time domain scheduling intervals can be configured for UL/DL data transmission or reception based on mini-slots. Also, a long time domain scheduling interval may be configured for UL/DL data transmission or reception through slot aggregation.

In particular, in the case of transmitting or receiving delay critical data, such as URLLC, when scheduling is performed on a 1ms (14 symbols) slot basis defined in a frame structure based on a parameter set having a small SCS value (e.g., 15 kHz), it may be difficult to satisfy the delay requirement. For this purpose, a mini slot consisting of fewer OFDM symbols than the slot may be defined. Scheduling for delay critical data, such as URLLC, may be performed on a mini-slot basis.

As described above, it is also considered to support parameter sets having different SCS values in one NR carrier by multiplexing in TDM and/or FDM manner, so that data is scheduled according to delay requirements based on the length of a slot (or mini-slot) defined by the parameter set. For example, as shown in FIG. 8, when the SCS is 60kHz, the symbol length is reduced to 1/4 of the symbol length when the SCS is 15 kHz. Thus, when one slot is composed of 14 OFDM symbols, the slot length based on 15kHz is 1ms, and the slot length based on 60kHz is reduced to about 0.25ms.

Thus, since SCS or TTI lengths different from each other are defined in NR, techniques for satisfying the needs of each of URLLC and eMBB have been developed.

PDCCH

In NR and LTE/LTE-a systems, L1 control information (such as DL allocation DL Control Information (DCI), and UL grant DCI, etc.) is transmitted and/or received through a PDCCH. A control channel element is defined as a resource element (CCE) used to transmit the PDCCH. In NR, a control resource set (CORESET) as a frequency/time resource for PDCCH transmission may be configured for each UE. Further, each CORESET may include one or more search spaces configured with one or more PDCCH candidates to allow the UE to monitor the PDCCH.

< wider Bandwidth operation >

A typical LTE system supports scalable bandwidth operation for any LTE CC (component carrier). That is, according to the frequency deployment scenario, the LTE provider may configure a bandwidth of minimum 1.4MHz to maximum 20MHz when configuring a single LTE CC, and the conventional LTE UE supports transmission/reception capability with a bandwidth of 20MHz for the single LTE CC.

However, NR is designed to be able to support NR UEs with different transmit/receive bandwidth capabilities on a single wideband NR CC. Accordingly, there is a need to configure one or more bandwidth parts (BWP), including sub-divided bandwidths for NR CCs as shown in fig. 9, thereby supporting flexible and wider bandwidth operation through configuration and activation of different bandwidth parts for respective UEs.

In particular, one or more bandwidth parts may be configured by a single serving cell configured for a UE in NR, and the UE is defined to activate one Downlink (DL) bandwidth part and one Uplink (UL) bandwidth part, thereby using these for uplink/downlink data transmission/reception in the corresponding serving cell. Furthermore, in the case where a plurality of serving cells are configured for the UE (that is, a UE to which CA is applied), the UE is also defined to activate one downlink bandwidth portion and/or one uplink bandwidth portion in each serving cell, thereby using these for uplink/downlink data transmission/reception by using radio resources of the corresponding serving cell.

In particular, an initial bandwidth portion for an initial access procedure of the UE may be defined in the serving cell; one or more UE-specific bandwidth portions may be configured for each UE through dedicated RRC signaling, and a default bandwidth portion for fallback operation may be defined for each UE.

It may be defined that multiple downlink and/or uplink bandwidth portions are activated and used simultaneously, depending on the capabilities of the UE and the configuration of the bandwidth portions in the serving cell. However, activation and use of only one Downlink (DL) bandwidth portion and one Uplink (UL) bandwidth portion at a time in the UE is defined in NR rel-15.

Discontinuous transmission indication for DL

A method for giving an indication of discontinuous transmission through a group common PDCCH has been defined as a multiplexing method of DL data for different transmission durations defined in NR. That is, when the UE receives the indication information for discontinuous transmission, the UE becomes able to recognize the presence or absence of data transmission preemption for any other UE of a part of time/frequency resources allocated to the PDSCH transmission resources of the corresponding UE according to the indication information.

In accordance with embodiments of the present disclosure, methods are provided for transmitting and/or receiving UL data channels based on preemption to efficiently multiplex UL data transmission resources between UEs having different latency requirements.

As a use scenario provided by NR and LTE/LTE-a systems, the importance for efficient support schemes for URLLC services requiring low latency/high reliability and eMBB services for maximizing data transmission rates is increasing,

in particular, in order to meet the latency requirement, in the case of UL data transmission for URLLC, UL data transmission may be performed by preempting a portion of UL data transmission resources that have been scheduled (or allocated) to other UEs, in a similar manner as described above for the DL case. For example, when UL data transmission needs to be performed for a URLLC UE sensitive to latency requirements while UL data transmission is performed for an eMBB UE, the URLLC UE may transmit corresponding UL data by preempting a portion of UL data transmission resources that have been scheduled or allocated to the eMBB UE.

To this end, in order to suspend UL data channel (PUSCH) transmission of a UE (e.g., an eMBB UE) currently transmitting UL data, and in order to support UL cancellation indication for enabling corresponding resources for UL data transmission of other UEs (e.g., URLLC UEs), it is necessary to define a specific operation scheme of the UE.

In the present disclosure, for convenience of description, the term "UL (uplink) cancellation indication" is used; however, the embodiments of the present disclosure are not limited to such specific terminology. The UL cancellation indication may be referred to as a UL preemption indication, a discontinuous UL transmission indication, or a suspended UL transmission indication, etc.; however, embodiments of the present disclosure are not limited to these terms.

Embodiment 1 monitoring information configuration for UL cancellation indication

A UE-specific DCI format (UE-specific DCI formart) for UL cancellation indication may be defined as a method for transmitting UL cancellation indication information. In this case, UL cancellation indication information may be transmitted to each UE through a UE-specific PDCCH transmitted via a UE-specific CORESET or a UE-specific search space for each UE.

A DCI format (UE-group common DCI formart) common to a group of UEs for UL cancellation indication may be defined as another method for transmitting UL cancellation indication information. In this case, UL cancellation indication information may be transmitted to each UE through a UE group common PDCCH transmitted through a UE group common CORESET or a UE group common search space configured for the UE group.

Accordingly, when UL cancellation indication information for a UE is defined to be transmitted through a UE-specific PDCCH or a PDCCH common to a UE group, a base station/network may be configured to: the UL cancellation indication is monitored by UE-specific higher layer signaling for the UE or cell-specific/UE group-common higher layer signaling. In this case, the monitoring configuration for the UL cancellation indication may be performed regardless of whether the monitoring configuration for the DL preemption indication exists.

In another embodiment, the UL cancellation indication may be indicated based on a specific sequence in addition to being transmitted over the PDCCH in the form of DCI (UE-specific or group-common). For example, the specific sequence may be preconfigured or may be configured based on specific factors such as cell ID, UE ID, or bandwidth.

In particular, the monitoring configuration information for UL cancellation indication may include control resource set (core) and search space configuration information for monitoring corresponding UL cancellation indication information, radio Network Temporary Identifier (RNTI) configuration information, or monitoring period configuration information, etc.

Embodiment 2 operation scheme of UE when UL cancellation indication information is received

1. Scheme for suspending remaining PUSCH transmissions

The UE having received the above UL cancellation indication information may not perform PUSCH transmission in one or more remaining OFDM symbols allocated to resources of the ongoing PUSCH transmission, that is, suspend PUSCH transmission.

Specifically, as shown in fig. 10, the UE having received the UL cancel instruction suspends all PUSCH transmissions after a timing gap k corresponding to a preconfigured delay time since the time when UL cancel instruction information transmission was performed. Here, the time when UL cancellation indication information transmission is performed may mean, for example: the last symbol of the UL cancel indication information is transmitted or the UL symbol corresponding to the last symbol of the UL cancel indication is transmitted.

At this point, the K value may be set by the base station/network and then sent to the UE through explicit signaling. For example, the K value may be set by the base station/network and then sent to the UE via UE-specific higher layer signaling or cell-specific/UE group-common higher layer signaling. In another example, the K value may be dynamically set, e.g., by the base station/network, by being included in the corresponding UL cancellation indication information via L1 control signaling, and then transmitted to the UE.

In another example of defining the K value, the K value may be implicitly set by the capability of the UE. Or based thereon, the base station/network may set up it and send it to the UE by explicit signaling, as described above.

In yet another example of defining a K value, the K value may be implicitly determined. For example, the K value may be determined as a function of numerology or SCS values of DL or UL. In another example, the K value may be determined as a function of the monitoring period value of the cancel indication.

In one embodiment, fig. 10 illustrates PUSCH resource allocation performed within the slot boundary of a slot. That is, according to this case, PUSCH resource allocation based on slots or based on mini slots may be performed. The UE may perform PUSCH transmission through a slot allocated for PUSCH transmission. Upon receiving the UL cancellation indication, the UE may suspend PUSCH transmission in one or more remaining symbols within a slot boundary of a corresponding slot following a symbol corresponding to a K value (which is a timing gap).

In another embodiment, fig. 11 illustrates PUSCH resource allocation performed based on multiple aggregated slots. In this case, the UE may suspend only the remaining PUSCH transmission within the slot boundary of the slot (#n) where the UL cancellation indication is received. Thereafter, the UE may normally perform PUSCH transmission over one or more remaining allocated slots (from #n+1).

In another embodiment, fig. 12 illustrates PUSCH resource allocation performed based on multiple aggregated slots. In this case, the UE may suspend all remaining PUSCH transmissions during the time slot (#n) where the UL cancellation indication is received and during the aggregate time slot since it (from #n+1).

2. Scheme for suspending PUSCH transmission only in a portion of the duration of the remaining PUSCH transmission

As shown in fig. 13, the UE having received the UL cancellation indication information may suspend PUSCH transmission corresponding to only an OFDM symbol corresponding to a part of the duration of the ongoing PUSCH transmission.

Specifically, as shown in fig. 13, the UE having received the UL cancellation indication may suspend PUSCH transmission corresponding to the duration M of PUSCH transmission after a preconfigured timing gap K since the time at which the corresponding UL cancellation indication information transmission was performed, and thereafter resume PUSCH transmission. Here, the time of transmitting the UL cancellation indication information transmission may refer to, for example, the last symbol of transmitting the UL cancellation indication information or a UL symbol corresponding to the last symbol of transmitting the UL cancellation indication information.

At this time, the K value may be set by the base station/network and then transmitted to the UE through explicit signaling, as shown above. For example, the K value may be set by the base station/network and then sent to the UE via UE-specific higher layer signaling or cell-specific/UE group-common higher layer signaling. In another example, the K value may be dynamically set, e.g., by the base station/network, by being included in the corresponding UL cancellation indication information via L1 control signaling, and then transmitted to the UE.

In yet another example of defining a K value, the K value may be implicitly determined. For example, the K value may be determined as a function of the numerology or SCS value of DL or UL, or as a function of the monitoring period value of the cancel indication.

Further, in a similar manner to the method of determining the K value described above, the M value, which is the duration of the suspension, may be set by the base station/network and then transmitted to the UE through explicit signaling. For example, the M value may be set by the base station/network and then sent to the UE through UE-specific higher layer signaling or cell-specific/UE group-common higher layer signaling. In another example, the M value may be dynamically set, e.g., by the base station/network, by being included in the corresponding UL cancellation indication information via L1 control signaling, and then transmitted to the UE.

In another example, the M value may be implicitly set by the capability of the UE. Alternatively, based thereon, the base station/network may set up it and send it to the UE by explicit signaling, as described above.

In yet another example of defining an M value, the M value may be implicitly determined. For example, the M value may be determined as a function of the numerology or SCS value of DL or UL, or as a function of the monitoring period value of the cancel indication.

In addition, the base station/network may perform explicit signaling for this when PUSCH transmission is resumed after a predetermined duration has elapsed.

In addition, an OFDM symbol or one symbol may be applied to a unit for defining a K value or an M value. As a numerical or SCS value for defining a symbol or slot boundary, an SCS applied to PUSCH transmission may be used, or an SCS of DL (e.g., PDCCH for UL cancellation indication transmission) may be used.

In one embodiment, transmission of UL cancellation indication information when the UE performs PUSCH transmission may be performed through DL. In another embodiment, the transmission of UL cancellation indication information may be performed by a cell adjacent to a cell in which the UE is performing PUSCH transmission. For this purpose, a multi-carrier or carrier aggregation scheme may be used. It should be noted that this is just one example; accordingly, the embodiments of the present disclosure are not limited to a specific method in the case where UL cancellation indication information can be received while the UE performs PUSCH transmission.

Accordingly, if an UL cancellation indication request for any other UE requiring low latency is invoked while the UE is transmitting the UL data channel, the latency requirement may be fulfilled because transmission of the UL channel for the any other UE may be performed with high priority. According to this, since transmission of UL channels of URLLC UEs can be performed at the same time as ebbb UEs perform UL data channel transmission, multiplexing of URLLC services and ebbb services can be efficiently performed.

Referring back to fig. 14, in step S1410, the UE may transmit UL data based on UL data resource allocation information.

The UE may transmit PUSCH to the base station according to allocation information on UL data resources. In one embodiment, the UE may be a UE using an eMBB service. However, this is merely an example and thus embodiments of the present disclosure are not limited thereto. One slot or a plurality of aggregated slots may be allocated resources for UL data transmission.

Referring back to fig. 14, in step S1420, the UE may monitor UL cancellation indication information based on the monitoring configuration information for the UL cancellation indication information.

The UE may receive monitoring configuration information regarding UL cancellation indication information from the base station. The monitoring configuration information may be received when the UE performs PUSCH transmission, or may be received independently of PUSCH transmission.

The UE may monitor whether UL cancellation indication information is transmitted based on the monitoring configuration information while transmitting PUSCH transmission. The monitoring configuration information may include control resource set (core) and search space configuration information, radio Network Temporary Identifier (RNTI) configuration information, and monitoring period configuration information, etc., to monitor UL cancellation indication information.

In one embodiment, regarding the monitoring period of UL cancellation indication information, in order to avoid interference with the ullc data requesting preemption, it is necessary for a UE currently transmitting UL data (e.g., an eMBB UE) to suspend corresponding UL data transmission before the ullc UE for transmitting ullc data starts UL data transmission. Considering the 1ms latency requirement of the URLLC traffic, if the subcarrier spacing is short, non-slot level monitoring may be performed on UL cancellation indication information so that the eMBB UE may suspend transmission in time. In one embodiment, non-slot level monitoring of the PDCCH may be supported by high-level parameters such as monitoringSymbolsWithinSlot.

In one embodiment, if a UL-specific DCI format is defined for a UL cancellation indication, the UE may monitor a UE-specific PDCCH transmitted through a UE-specific CORESET or a UE-specific search space in order to receive UL cancellation indication information. When transmitting UL cancellation indication information through the UE-specific PDCCH, the base station/network may configure (e.g., instruct) the UE to perform monitoring for UL cancellation indications through UE-specific higher layer signaling.

In another embodiment, if a UE group common DCI format is defined for the UL cancellation indication, the UE may monitor a UE group common PDCCH transmitted through a UE group common CORESET or a UE group common search space to receive UL cancellation indication information. When UL cancellation indication information is transmitted through a PDCCH common to the UE group, the base station/network may configure (e.g., instruct) the UE to perform monitoring for UL cancellation indications through higher layer signaling common to the cell specific/UE group.

In one embodiment, since the UL scheduling slot offset is greater than the time required for UL cancellation indication, a UE currently transmitting UL data may monitor UL cancellation indication information when scheduling UL transmission. Further, since the UE currently transmitting UL data requires a processing time of UL cancellation indication information, the UE may not monitor UL cancellation indication information if the last symbol of UL data transmission is earlier than the processing time.

Accordingly, the UE currently transmitting UL data may monitor UL cancellation indication information during a period from a reception time of UL grant to a completion time of processing of UL cancellation indication information before a last symbol of UL data transmission. Further, since the start time of monitoring may be later than the receive time of UL grant, the base station may provide information semi-statically or dynamically. Accordingly, power consumption required for monitoring can be reduced.

Referring back to fig. 14, the UE may receive UL cancellation indication information at step S1430 and suspend ongoing UL data transmission based on the UL cancellation indication information at step S1440.

Upon receiving the UL cancellation indication information, the UE may suspend PUSCH transmission in one or more remaining OFDM symbols in resources allocated to the ongoing PUSCH transmission that have not been used. In one embodiment, in case of successfully decoding the UL cancellation indication, the UE may suspend transmission of UL data using the resource where the transmission is cancelled. In this case, the resource where the transmission is cancelled may be allocated for transmission of UL channels for any other UE that has requested preemption.

After a preconfigured timing gap K from the transmission time of the UL cancellation indication information, the UE may suspend PUSCH transmission. For example, the UE may suspend PUSCH transmission after K corresponding to a predetermined number of symbols from the last symbol of the UL cancellation indication information is transmitted or the UL symbol corresponding to the last symbol of the UL cancellation indication information is transmitted.

In one embodiment, the K value, which is a pre-configured timing gap, may be set by the base station/network and then sent to the UE by explicit signaling. In another embodiment, the K value may be set implicitly by the UE's capability or by the UE's capability and then sent to the UE by explicit signaling. In yet another embodiment, the K value may be implicitly set as a function of numerology or SCS values of DL or UL, or as a function of the monitoring period value of the cancel indication. Accordingly, the K value may include a time taken for the base station to transmit UL cancellation indication information and a time taken for the UE to process the UL cancellation indication information.

In one embodiment, if resources for UL data transmission are allocated to one slot, the UE may suspend UL data transmission in the slot in which UL cancellation indication information is received. In this case, one or more remaining symbols within the slot may be used for UL channel transmission for any other UE that has requested UL preemption.

In one embodiment, if resources for UL data transmission are allocated to a plurality of aggregated slots, the UE may suspend UL data transmission only for a slot in which UL cancellation indication information is received. In another embodiment, the UE may suspend UL data transmission for all of the plurality of allocated slots and the slot in which the UL cancellation indication information is received.

In one embodiment, the UL cancellation indication information may further include information about an M value, which is a preconfigured suspension duration for suspending transmission of UL data. In one embodiment, the M value, which is a preconfigured duration of suspension, may be set by the base station/network and then sent to the UE by explicit signaling. In this case, the M value may be set by the base station/network and then transmitted to the UE through UE-specific higher layer signaling. In another embodiment, the M value may be sent to the UE via higher layer signaling common to the cell specific/UE group. In yet another embodiment, the M value may be dynamically set, for example, by being included in the corresponding UL cancellation indication information via L1 control signaling, and then transmitted to the UE.

In yet another embodiment, the M value may be set implicitly by the UE's capability or by the UE's capability and then sent to the UE by explicit signaling. In yet another embodiment, the M value may be implicitly set as a function of numerology or SCS values of DL or UL, or as a function of the monitoring period value of the cancel indication.

If information on the M value as the suspension duration is further included in the UL cancel indication information, the UE may suspend UL data transmission during the suspension duration and resume UL data transmission after the suspension duration has elapsed.

In one embodiment, if resources for UL data transmission are allocated to one slot, the UE may suspend UL data transmission in the slot in which UL cancellation indication information is received. If there are one or more remaining symbols after the M value has elapsed, the UE may resume UL data transmission for the one or more remaining symbols. In one embodiment, if resources for UL data transmission are allocated to a plurality of aggregated slots, the UE may transmit UL data for one or more remaining symbols after the M value has elapsed and slots since it.

Accordingly, when the UE transmits the UL data channel, if a UL cancellation indication request is given for any other UE requiring low latency, the latency requirement can be fulfilled because the UL channel for any other UE can be transmitted with high priority.

Referring back to fig. 15, in step S1510, the base station may configure monitoring configuration information for UL cancellation indication information.

In one embodiment, when the base station receives UL data from a UE (e.g., an eMBB UE), the base station may receive a Scheduling Request (SR) from any other UE (e.g., a URLLC UE) that requires low latency. The base station may configure UL cancellation indication information to be transmitted to a UE (e.g., an eMBB UE) currently transmitting UL data.

In one embodiment, after the base station has received the SR from the URLLC UE, the base station may decode the SR and prepare an UL grant for the URLLC UE. Thereafter, the base station may configure UL cancellation indication information for the UE currently transmitting UL data. In one embodiment, the transmission time of the UL cancellation indication information may be earlier than or equal to the transmission time of the UL grant.

To meet low latency requirements for URLLC UEs, the slot offset between UL grants and corresponding scheduled PUSCHs of URLLC UEs may be configured to be smaller than the slot offset between UL grants and corresponding scheduled PUSCHs, respectively, of UEs currently transmitting UL data. In another embodiment, the time taken for processing UL cancellation indication information and preparing PUSCH suspension by the UE currently transmitting UL data may be configured to be shorter than or equal to the time taken for processing UL grant and preparing PUSCH transmission by the URLLC UE.

In one embodiment, the UL cancellation indication information may include information about the cancelled UL resources. Based on this, the UE currently transmitting UL data can timely suspend the ongoing transmission that has been scheduled in the cancelled UL resource.

In one embodiment, the monitoring configuration information may include control resource set (CORESET) and search space configuration information, radio Network Temporary Identifier (RNTI) configuration information, and monitoring period configuration information, etc., to monitor UL cancellation indication information.

Referring back to fig. 15, in step S1520, the base station may transmit monitoring configuration information to the UE currently transmitting UL data.

In one embodiment, the base station may define a UE-specific DCI format for the UL cancellation indication. In this case, for the UE, the base station may configure the monitoring of the UL cancellation indication through UE-specific higher layer signaling.

In another embodiment, the base station may define a DCI format common to the UE group for the UL cancellation indication. In this case, for the UE, the base station may configure the monitoring of the UL cancellation indication through higher layer signaling common to the cell specific/UE group.

Referring back to fig. 15, in step S1530, the base station may transmit UL cancellation indication information based on the monitoring configuration information.

If an UL-specific DCI format is defined for the UL cancellation indication, the base station may transmit UL cancellation indication information through a UE-specific PDCCH transmitted via a UE-specific CORESET or a UE-specific search space.

If a UL group common DCI format is defined for the UL cancellation indication, the base station may transmit UL cancellation indication information through a UE group common PDCCH transmitted via a UE group common CORESET or a UE group common search space.

In one embodiment, the UL cancellation indication information may require higher reliability than the DL preemption indication information. This is because, before the URLLC UE transmits PUSCH, UL cancellation indication information is used to instruct a UE (e.g., an eMBB UE) currently transmitting UL data to cancel an ongoing or impending PUSCH, while DL preemption indication is used to instruct a UE (e.g., an eMBB UE) currently receiving PDSCH that has been cancelled by the base station. Therefore, in order to avoid collision with the UE currently transmitting UL data and to achieve overall reliability of URLLC, it is necessary to improve reliability of UL cancellation indication information.

To this end, in one embodiment, more time-frequency resources may be allocated for UL cancellation indication information. For example, a higher aggregation level may be applicable to a PDCCH including UL cancellation indication information. In another example, the reliability of the UL cancellation indication information may be improved by frequency repetition or time repetition.

In another embodiment, in order to improve reliability of UL cancellation indication information, the payload size of the UL cancellation indication information may be reduced. For example, even when the URLLC UE occupies only a portion of the BWP in a few symbols, one bit may be used to represent the entire BWP within one slot. If the UE currently transmitting UL data initiates PUSCH transmission in a slot in which UL cancellation indication information is received, the UE may suspend PUSCH transmission in the entire BWP in one or more remaining symbols of the slot. The scheduled PUSCH transmission may be cancelled if the UE currently transmitting UL data does not initiate PUSCH transmission.

When the UL cancellation indication information is transmitted, the UE may suspend PUSCH transmission in one or more remaining OFDM symbols in resources allocated to the ongoing PUSCH transmission that have not been used. After a preconfigured timing gap K, the UE may suspend PUSCH transmission from the time when transmission of UL cancellation indication information has been performed. For example, the UE may suspend PUSCH transmission after K corresponding to a predetermined number of symbols from the last symbol of the UL cancellation indication information is transmitted or the UL symbol corresponding to the last symbol of the UL cancellation indication information is transmitted.

When a UE that is transmitting PUSCH suspends PUSCH transmission, the base station may allocate one or more remaining resources of the resources allocated for that UE to any other UE requesting preemption (e.g., a UE using URLLC service). Thereafter, the base station may receive UL data or the like from the UE requesting preemption through the one or more allocated resources.

Accordingly, when the UE transmits the UL data channel, if the UL cancellation indication request for any other UE requiring low latency is invoked, the latency requirement may be fulfilled because transmission of the UL channel for any other UE may be performed with high priority.

Fig. 16 is a block diagram illustrating a base station 1600 according to an embodiment of the present disclosure.

Referring to fig. 16, a base station 1600 includes a controller 1610, a transmitter 1620, and a receiver 1630.

The controller 1610 controls the overall operation of the base station 1600 required to perform the method of controlling UL data transmission of the UE according to the above-described embodiments of the present disclosure.

The controller 1610 may configure monitoring configuration information for UL cancellation indication information. The monitoring configuration information may include control resource set (core) and search space configuration information, configuration information of a Radio Network Temporary Identifier (RNTI), and monitoring period configuration information, etc., to monitor UL cancellation indication information.

Controller 1610 may define a UE-specific DCI format for the UL cancellation indication. In another embodiment, controller 1610 may define a DCI format common to the UE group for the UL cancellation indication.

The transmitter 1620 is configured to transmit signals, messages and data required to perform the above-described embodiments to the UE. The receiver 1630 is configured to receive signals, messages, and data from the UE required to perform the embodiments described above.

The transmitter 1620 may transmit the monitoring configuration information to the UE currently transmitting UL data. If a UE-specific DCI format is defined for the UL cancellation indication, the transmitter 1620 may transmit the monitoring configuration information for the UL cancellation indication through UE-specific higher layer signaling for the UE. In yet another embodiment, if a DCI format common to a UE group is defined for an UL cancellation indication, the transmitter 1620 may transmit monitoring configuration information for the UL cancellation indication through higher layer signaling common to a cell specific/UE group for the UE.

The transmitter 1620 may transmit UL cancellation indication information based on the monitoring configuration information. If a UL-specific DCI format is defined for the UL cancellation indication, the transmitter 1620 may transmit UL cancellation indication information through a UE-specific PDCCH transmitted via a UE-specific CORESET or a UE-specific search space.

If a UL group common DCI format is defined for the UL cancellation indication, the transmitter 1620 may transmit the UL cancellation indication information through a UE group common PDCCH transmitted via a UE group common CORESET or a UE group common search space.

When the UL cancellation indication information is transmitted, the UE may suspend PUSCH transmission in one or more remaining OFDM symbols in resources allocated to the ongoing PUSCH transmission that have not been used. After a preconfigured timing gap K from the time when transmission of UL cancellation indication information is performed, the UE may suspend PUSCH transmission. For example, the UE may suspend PUSCH transmission after K corresponding to a predetermined number of symbols from the last symbol from which UL cancellation indication information is transmitted or the UL symbol corresponding to the last symbol from which UL cancellation indication information is transmitted.

When a UE that is transmitting PUSCH suspends PUSCH transmission, controller 1610 may allocate one or more remaining resources of the resources allocated for that UE to any other UE requesting preemption (e.g., a UE using URLLC service). Thereafter, the receiver 1630 may receive UL data and the like from the UE requesting preemption through the one or more allocated resources.

Fig. 17 is a block diagram illustrating a UE 1700 according to an embodiment of the present disclosure.

Referring to fig. 17, a UE 1700 according to another embodiment includes a receiver 1710, a controller 1720, and a transmitter 1730.

The transmitter 1730 transmits UL control information, data, and messages to the base station through corresponding channels. The transmitter 1730 may transmit UL data based on UL data resource allocation information.

The receiver 1710 receives DL control information, data, and messages from the base station through corresponding channels. The receiver 1710 may receive monitoring configuration information on UL cancellation indication information from the base station. The monitoring configuration information may be received when the UE performs PUSCH transmission, or received independently of PUSCH transmission.

The monitoring configuration information may include: control resource set (CORESET) and search space configuration information, radio Network Temporary Identifier (RNTI) configuration information, and monitoring period configuration information, etc., to monitor UL cancellation indication information.

The receiver 1710 may receive UL cancellation indication information based on the result of the monitoring from the controller 1720.

The controller 1720 controls the overall operation of the UE 1700 required to perform the method of transmitting UL data according to the above-described embodiments of the present disclosure.

The controller 1720 may monitor UL cancellation indication information based on the monitoring configuration information for UL cancellation indication information.

In one embodiment, if a UL-specific DCI format is defined for a UL cancellation indication, controller 1720 may monitor a UE-specific PDCCH transmitted over a UE-specific CORESET or UE-specific search space to receive UL cancellation indication information. When UL cancellation indication information is transmitted through the UE-specific PDCCH, the base station/network may configure the UE to perform monitoring for UL cancellation indications through UE-specific higher layer signaling.

In another embodiment, if a UE group common DCI format is defined for the UL cancellation indication, controller 1720 may monitor a UE group common PDCCH space transmitted over a UE group common CORESET or UE group common search space to receive UL cancellation indication information. When UL cancellation indication information is transmitted through a PDCCH common to the UE group, the base station/network may configure the UE to perform monitoring for UL cancellation indication through a higher layer signaling common to the cell specific/UE group.

The controller 1720 may suspend ongoing UL data transmission based on the UL cancellation indication information. Upon receiving the UL cancellation indication information, the controller 1720 may suspend PUSCH transmission in one or more remaining OFDM symbols in the resources allocated for ongoing PUSCH transmission that have not been used. After a preconfigured timing gap K from the time of transmitting the UL cancellation indication information, the controller 1720 may suspend PUSCH transmission. For example, the controller 1720 may suspend PUSCH transmission after K corresponding to a predetermined number of symbols from the last symbol of the UL cancellation indication information is transmitted or the UL symbol corresponding to the last symbol of the UL cancellation indication information is transmitted.

In one embodiment, the K value, which is a pre-configured timing gap, may be set by the base station/network and then sent to the UE1700 by explicit signaling. In another embodiment, the K value may be set implicitly by the capabilities of the UE1700 or by the capabilities of the UE1700 and then sent to the UE by explicit signaling. In yet another embodiment, the K value may be implicitly set as a function of numerology or SCS values of DL or UL, or as a function of the monitoring period value of the cancel indication. Accordingly, the K value may include the time taken for the base station to transmit UL cancellation indication information and the time taken for the UE1700 to process UL cancellation indication information.

In one embodiment, if resources for UL data transmission are allocated to one slot, the controller 1720 may suspend UL data transmission for a slot in which UL cancellation indication information is received. In this case, one or more remaining symbols within the slot may be used for UL channel transmission for any other UE that has requested UL preemption.

In one embodiment, if resources for UL data transmission are allocated to a plurality of aggregated slots, controller 1720 may suspend UL data transmission only during the slot in which UL cancellation indication information is received. In another embodiment, controller 1720 may suspend UL data transmission for all of the plurality of allocated slots and the slot in which UL cancellation indication information is received.

In one embodiment, the UL cancellation indication information may further include information about an M value, which is a preconfigured suspension duration for suspending transmission of UL data. In one embodiment, the M value, which is a preconfigured duration of suspension, may be set by the base station/network and then sent to the UE 1700 by explicit signaling. In this case, the M value may be set by the base station/network and then transmitted to the UE through UE-specific higher layer signaling. In another embodiment, the M value may be sent to the UE 1700 through higher layer signaling common to the cell specific/UE group. In yet another embodiment, the M value may be dynamically set, for example, by being included in the corresponding UL cancellation indication information via L1 control signaling, and then transmitted to the UE.

In another embodiment, the M value may be set implicitly by the capabilities of the UE1700 or by the capabilities of the UE1700 and then sent to the UE1700 by explicit signaling. In yet another embodiment, the M value may be implicitly set as a function of numerology or SCS values of DL or UL, or as a function of the monitoring period value of the cancel indication.

If information on the M value as the suspension duration is further included in the UL cancel indication information, the controller 1720 may suspend UL data transmission during the suspension duration and resume UL data transmission after the suspension duration has elapsed.

In one embodiment, if resources for UL data transmission are allocated to one slot, the controller 1720 may suspend UL data transmission for a slot in which UL cancellation indication information is received. If there are one or more remaining symbols after the value of M has elapsed, controller 1720 may resume UL data transmission for the one or more remaining symbols. In one embodiment, if resources for UL data transmission are allocated to a plurality of aggregated slots, controller 1720 may transmit UL data for one or more remaining symbols after the M value has elapsed and slots from it.

The above-described embodiments may be supported by standard documents disclosed in at least one radio access system, such as IEEE 802, 3GPP, and 3GPP 2. That is, steps, configurations, and components not described in the present embodiment can be supported by the above-described standard documents for clarifying the technical concept of the present invention. Furthermore, all terms disclosed herein can be described by the above standard documents.

The above-described embodiments may be implemented in various ways. For example, the present embodiments may be implemented as hardware, firmware, software, or a combination thereof.

In the case of implementation by hardware, the method according to the current embodiment may be implemented as at least one of: an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a processor, a controller, a microcontroller, or a microprocessor.

In the case of implementation by firmware or software, the method according to the current embodiment may be implemented in the form of a device, process or function that performs the above-described function or operation. The software codes may be stored in memory units or may be driven by processors. The memory unit may be provided internal or external to the processor and may exchange data with the processor in various well-known ways.

Furthermore, the terms "system," "processor," "controller," "component," "module," "interface," "model," "unit," and the like may generally refer to computer-related physical hardware, a combination of hardware and software, or running software. For example, the components described above may be, but are not limited to being, processor-driven processes, processors, controllers, control processors, entities, threads of execution, programs, and/or computers. For example, both an application running in a controller or processor and the controller or processor can be a component. One or more components can be provided in a process and/or thread of execution, and the components can be provided in a single device (e.g., system, computing device, etc.), or can be distributed across two or more devices.

The above-described embodiments of the present disclosure have been described for illustrative purposes only, and it will be appreciated by those of ordinary skill in the art that various modifications and changes can be made thereto without departing from the scope and spirit of the present disclosure. Further, the embodiments of the present disclosure are not intended to be limiting, but rather are intended to illustrate the technical concept of the present disclosure, and thus the scope of the technical concept of the present disclosure is not limited by these embodiments. The scope of the present disclosure should be construed based on the appended claims in such a manner that all technical ideas included in the scope equivalent to the claims belong to the present disclosure.

Cross Reference to Related Applications

The present application claims priority from patent application 10-2018-0018740 filed in korea on 14 th 2 nd 2018 and patent application 10-2019-0015479 filed in 2019 on 11 th 2 nd, according to 35USC ≡119 (a), the entire contents of which are incorporated herein by reference, if applicable. In addition, based on korean patent application, the non-provisional application requires priority in countries other than the united states for the same reason, the entire contents of which are incorporated herein by reference.

Claims

1. A method for a User Equipment (UE) to transmit Uplink (UL) data, the method comprising:

transmitting UL data based on UL data resource allocation information;

monitoring UL cancellation indication information based on monitoring configuration information regarding the UL cancellation indication information;

receiving the UL cancellation indication information; and

suspending transmission of UL data being transmitted based on the UL cancellation indication information

Wherein a suspension of transmission of the UL data is performed after a pre-configured timing gap K has elapsed since a time of receiving the UL cancellation indication information, and a suspension duration of the suspension is M,

wherein, K and M are set based on the subcarrier spacing SCS value of DL.

2. The method of claim 1, wherein the monitoring configuration information includes at least one of control resource set (CORESET) and search space configuration information, radio Network Temporary Identifier (RNTI) configuration information, and monitoring period configuration information to monitor the UL cancellation indication information.

3. The method of claim 1, wherein the UL cancellation indication information is indicated by UE-specific Downlink Control Information (DCI) or DCI common to a group of UEs.

4. The method of claim 1, wherein the suspending of the transmission of UL data is performed within a time slot in which the UL cancellation indication information is received or for all of a plurality of time slots allocated based on the UL data resource allocation information.

5. The method of claim 1, wherein the UL cancellation indication information further includes information about a preconfigured duration of suspension for suspending transmission of the UL data, and

wherein the suspension of the transmission of the UL data is performed during a suspension duration, and the transmission of the UL data is resumed after the suspension duration has elapsed.

6. A method of a base station for controlling Uplink (UL) data transmission of a User Equipment (UE), the method comprising:

Configuring monitoring configuration information for UL cancellation indication information;

transmitting the monitoring configuration information to the UE transmitting UL data; and

transmitting the UL cancellation indication information based on the monitoring configuration information,

wherein the UE suspends transmission of the UL data after a pre-configured timing gap K has elapsed since the time of receiving the UL cancellation indication information, and a suspension duration of the suspension is M,

wherein, K and M are set based on the subcarrier spacing SCS value of DL.

7. The method of claim 6, wherein the monitoring configuration information includes at least one of control resource set (CORESET) and search space configuration information, radio Network Temporary Identifier (RNTI) configuration information, and monitoring period configuration information to monitor the UL cancellation indication information.

8. The method of claim 6, wherein the UL cancellation indication information is indicated by UE-specific Downlink Control Information (DCI) or DCI common to a group of UEs.

9. The method of claim 6, wherein the UE suspends transmission of UL data within a time slot in which the UL cancellation indication information is received or for all of a plurality of time slots allocated based on UL data resource allocation information.

10. The method of claim 6, wherein the UL cancellation indication information further includes information about a preconfigured duration of suspension for suspending transmission of the UL data, and

wherein the UE suspends transmission of UL data for a suspension duration and resumes transmission of UL data after the suspension duration has elapsed.

11. A User Equipment (UE) for transmitting Uplink (UL) data, the UE comprising:

a transmitter that transmits UL data based on UL data resource allocation information;

a controller that monitors UL cancellation indication information based on monitoring configuration information regarding the UL cancellation indication information, and suspends transmission of UL data being transmitted based on the UL cancellation indication information; and

a receiver that receives the UL cancellation indication information,

wherein the controller suspends transmission of the UL data after a pre-configured timing gap K has elapsed since the time of receiving the UL cancellation indication information, and a suspension duration of the suspension is M,

wherein, K and M are set based on the subcarrier spacing SCS value of DL.

12. The user equipment of claim 11, wherein the monitoring configuration information comprises at least one of control resource set (CORESET) and search space configuration information, radio Network Temporary Identifier (RNTI) configuration information, and monitoring period configuration information to monitor the UL cancellation indication information.

13. The user equipment of claim 11, wherein the UL cancellation indication information is indicated by UE-specific Downlink Control Information (DCI) or DCI common to a group of UEs.

14. The user equipment of claim 11, wherein the controller suspends transmission of the UL data within a time slot in which the UL cancellation indication information is received or for all of a plurality of time slots allocated based on the UL data resource allocation information.

15. The user equipment of claim 11, wherein the UL cancellation indication information further includes information on a pre-configured suspension duration for suspending transmission of the UL data, and

wherein the controller pauses transmission of the UL data for a pause duration and resumes transmission of the UL data after the pause duration has elapsed.