CN111543023A

CN111543023A - Method and apparatus for transmitting uplink data

Info

Publication number: CN111543023A
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: 2020-08-14
Anticipated expiration: 2039-02-13
Also published as: KR20190098708A; CN111543023B; KR102320416B1

Abstract

The embodiment discloses a method and equipment for transmitting uplink data according to uplink cancellation indication information in a next generation wireless network, and provides a method for transmitting the uplink data by a terminal in one embodiment, and the method comprises the following steps: transmitting uplink data based on the uplink data resource allocation information; monitoring the uplink cancellation indication information based on the monitoring configuration information on the uplink cancellation indication information; receiving uplink cancellation indication information; and suspends the 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 a method and apparatus for transmitting uplink data in a next generation/5G radio access network (hereinafter, referred to as a new radio "NR").

Background

Recently, the third generation partnership project (3GPP) has approved "research on new radio access technologies", which is a research project that studies the 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 WG1) has discussed a frame structure, channel coding and modulation, waveforms, multiple access method, and the like for the New Radio (NR). NR needs to be designed not only to provide an improved data transmission rate compared to Long Term Evolution (LTE)/LTE-advanced, but also to meet various requirements in specific and specific usage scenarios.

Enhanced mobile broadband (eMBB), mass machine type communication (mtc), and ultra-reliable low latency communication (URLLC) are proposed as typical usage scenarios for NRs. In order to meet the requirements of each scenario, it is required to design NR so as to have a flexible frame structure compared to LTE/LTE-advanced.

Since requirements for data rate, delay, reliability, coverage, etc. are different, it is required to provide a method of efficiently multiplexing radio resource units based on mutually different parameter sets (numerology), such as subcarrier spacing, subframe, Transmission Time Interval (TTI), etc., as a method for efficiently satisfying each usage scenario requirement through a frequency band constituting 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 scheme

According to an aspect of the present disclosure, there is provided a method for a user equipment or terminal (hereinafter referred to as "user equipment" or "UE") to transmit uplink ("UL") data. The method can comprise the following steps: transmitting UL data based on the UL data resource allocation information; monitoring the 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 for a base station to control UL data transmission of a UE. The method can comprise the following steps: configuring monitoring configuration information regarding UL cancel indication information; transmitting the monitoring configuration information to a UE that is 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 which transmits UL data based on the UL data resource allocation information; a controller that monitors the UL cancellation indication information based on monitoring configuration information on the UL cancellation indication information and suspends ongoing UL data transmission based on the UL cancellation indication information; and a receiver which 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 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.

Figure 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 even though they are shown on different drawings. In addition, 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", "containing", etc. are used as mentioned herein, any other part may also be added, unless the expression "only" is used. When an element is referred to in the singular, it can also be in the plural unless specifically stated to the element.

Further, terms such as first, second, A, B, (a), (B) may be used herein when describing components of the present disclosure. Each of these terms is not intended to define the nature, order, or sequence of the corresponding components, but rather is merely intended to distinguish the corresponding components from other components. In describing positional relationships 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 which are "connected", "combined", or "coupled" to each other.

In describing the order of operations or methods of manufacture, for example, the use of "after", "subsequently", "next", "before", and the like, is also intended to encompass instances in which the operations or processes are not performed in the singular, unless the context clearly dictates otherwise. Reference herein to digital values for components or information corresponding thereto (e.g., levels, etc.) may be interpreted as including a range of errors due to various factors (e.g., process factors, internal or external influences, noise, etc.), even if an explicit description is not provided.

A wireless communication system in the present specification refers to a system for providing various communication services such as a voice service and a data service using radio resources. The wireless communication system may include a User Equipment (UE), a base station, a core network, and so on.

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. Further, the radio access technology may refer to respective generation communication technologies established by various communication organizations, such as third generation partnership project (3GPP), 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. The 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, which provides backward compatibility with IEEE 802.16e based systems. UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3GPP (third generation partnership project) LTE (long term evolution) is part of E-UMTS (evolved UMTS) using evolved-UMTS terrestrial radio access (E-UTRA) with OFDMA in the downlink and SC-FDMA in the uplink. As described above, the embodiments may be applied to radio access technologies that have been enabled or commercialized. Furthermore, the embodiments may also be applied to radio access technologies being developed or to be developed in the future.

The UE used in this specification must be interpreted in a broad sense, which indicates a device including a wireless communication module that communicates with a base station in a wireless communication system. For example, UEs include User Equipment (UE) in WCDMA, LTE, NR, HSPA, IMT-2020(5G or new radio), etc., mobile stations in GSM, User Terminals (UT), Subscriber Stations (SS), wireless devices, etc. Further, the UE may be a portable user equipment, such as a smartphone, or the UE may be a vehicle in a V2X communication system, a device in a vehicle that includes a wireless communication module, etc. (depending on its type of use). 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 that communicates with a UE through a network, and covers various coverage areas such as a node B, an evolved node B (enb), a enode B, a Low Power Node (LPN), a sector, a site, various types of antennas, a Base Transceiver System (BTS), an access point, a point (e.g., a transmission point, a reception point, or a transmission/reception point), a relay node, a macrocell, a microcell, a picocell, a femtocell, a Radio Remote Head (RRH), a radio frequency unit (RU), a small cell, and so on. 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 the 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 ways. The base station may be 1) a device for providing a macrocell, microcell, picocell, femtocell, or small cell 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 interacting with each other and configuring a wireless area in cooperation. For example, the base station may be a point, a transmission/reception point, a transmission point, a reception point, and the like, depending on the configuration method of the wireless area. In the above description 2), the base station may be a wireless area that may support a User Equipment (UE) to transmit and receive data to and 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.

Uplink (UL) refers to data transmission and reception from the UE to the base station, and Downlink (DL) refers to data transmission and reception from the base station to the UE. The downlink may refer to a communication or communication path from a plurality of transmission/reception points to the UE, and the uplink may refer to a communication or communication path from the UE to a plurality of transmission/reception points. In the downlink, the transmitter may be part of a plurality of transmission/reception points, and the 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 the plurality of transmission/reception points.

The 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 signals on channels such as PUCCH, PUSCH, PDCCH, PDSCH, etc. may be expressed as "transmission and reception of PUCCH, PUSCH, PDCCH, PDSCH, etc.

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

After studying 4G (fourth generation) communication technology, 3GPP is developing 5G (fifth generation) communication technology in order to meet the demand of the next generation radio access technology 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 needs of ITU-R and a new NR communication technology 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, the 5G communication technology will be described on the basis of NR.

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

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

< overview of NR System >

Fig. 1 schematically shows an NR system.

Referring to fig. 1, the NR system is divided into a 5G core network (5GC) and NG-RAN parts. The NG-RAN includes a gNB and NG-eNB, which provide user plane (SDAP/PDCP/RLC/MAC/PHY) and User Equipment (UE) control plane (RRC) protocol ends. Multiple gNBs or gNBs and ng-eNBs are interconnected 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 UE connection and mobility control functions, and a User Plane Function (UPF) for controlling user data. NR supports a frequency band below 6GHz (frequency range 1: FR1 FR1) and a frequency band equal to or greater than 6GHz (frequency range 2: FR2 FR 2).

The gNB represents a base station providing an NR user plane and a control plane protocol side to the UE. The ng-eNB represents the base station providing the E-UTRA user plane and control plane protocol end to the UE. The base station described in this specification should be understood to cover both the gbb and the ng-eNB. However, base stations may also be used to refer to separate gNBs or ng-NBs, 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 (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 requirements for data rate, delay rate, coverage, and the like in NR, it is necessary to efficiently satisfy the requirements of each scenario on the frequency band constituting the NR system. To this end, 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 subcarrier spacing and Cyclic Prefix (CP), 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 at 15 kHz. 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 240 kHz. In addition, the extended CP is applied only to the subcarrier spacing of 60 kHz. In NR, a frame is defined to include 10 subframes and have a length of 10ms, each subframe having the same length of 1 ms. One frame may be divided into 5ms fields, each field comprising 5 subframes. In the case where the subcarrier spacing is 15kHz, one subframe includes one slot, and each slot includes 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 subcarrier spacing. For example, in the case of a parameter set having a subcarrier spacing of 15kHz, a slot is configured to have the same 1ms length as a subframe. On the other hand, in the case of the 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, so that the time length thereof varies with 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 the radio sector. If a wide subcarrier spacing is used, the length of one slot is shortened inversely, thereby reducing transmission delay in the radio sector. The mini-slots (or sub-slots) are intended to support URLLC scenarios efficiently, and the mini-slots may be scheduled in 2, 4, or 7 symbol units.

Further, unlike LTE, NR defines uplink and downlink resource allocation as symbol levels in one slot. 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 of these are used in 3GPP Rel-15. Further, NR supports a common frame structure in which FDD or TDD frames are constructed by combination of various time 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. Furthermore, NR supports data transmission that is scheduled to be distributed over one or more time slots. Accordingly, the base station may inform the UE of whether the slot is a downlink slot, an uplink slot, or a flexible slot using a Slot Format Indicator (SFI). The base station may inform the slot format by using the SFI to indicate the index of the table configured by the UE-specific RRC signaling. 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 resource of NR >

Regarding the physical resources in NR, antenna ports, resource grid, resource elements, resource blocks, bandwidth sections, and the like are considered.

An antenna port is defined as an inference from a channel carrying a symbol on the antenna port that another channel carrying another symbol on the same antenna port. Two antenna ports may have a quasi-co-location or quasi-co-location (QC/QCL) relationship if the large scale characteristics of the channel carrying symbols on the antenna ports can be inferred from another channel carrying symbols on another antenna port. 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, the resource grid may exist according to the respective parameter sets because the NRs support multiple parameter sets in the same carrier. Furthermore, the existence of the resource grid depends on the antenna ports, the subcarrier spacing and the transmission direction.

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

Unlike LTE, in which the carrier bandwidth is fixed to 20MHz, in NR, the maximum carrier bandwidth is configured to 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, a bandwidth part (BWP) can be specified within a carrier bandwidth so that a UE can use the bandwidth part. Further, the bandwidth portion may be associated with one set of parameters, 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 transmits and receives data using the activated bandwidth parts for a given time.

In the case of paired spectrum, the uplink and downlink bandwidth portions are independently configured. In the case of unpaired spectrum, to prevent unnecessary frequency retuning between downlink and uplink operation, the downlink and uplink bandwidth portions are configured in pairs, sharing a central frequency.

< initial Access in NR >

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

The cell search is: a procedure 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 can be sent up to 64 times in 5 ms. The multiple SSBs transmit through different transmit beams in 5ms of time, and the UE assumes detection based on a particular beam used for transmission transmitting an SSB every 20 ms. The number of beams that can be used for SSB transmission in 5ms may increase as the frequency band increases. For example, up to 4 SSB beams may be transmitted on a frequency band of 3GHz or lower, while up to 8 SSB beams may be transmitted on a frequency band of 3 to 6 GHz. Furthermore, SSBs may be transmitted using up to 64 different beams over a frequency band of 6GHz or higher.

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

Unlike the SS in a typical LTE system, the SSB does not transmit at the center frequency of the carrier bandwidth. That is, the SSB may also be transmitted at a frequency different from the center of the system band, and a plurality of SSBs may be transmitted in the frequency domain if wideband operation is 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 newly defined in NR for initial connection, and the synchronization grid can support fast SSB search of the UE because its frequency spacing is configured to be wider than that of the carrier grid.

The UE may obtain the MIB on the PBCH of the SSB. The MIB (master information block) includes minimum information for the UE to receive the Remaining Minimum System Information (RMSI) broadcasted by the network. In addition, the PBCH may include information on the first DM-RS symbol position in the time domain, information for the UE to monitor the SIB1 (e.g., SIB1 parameter set information, information related to SIB1 CORESET, search space information, PDCCH related parameter information, etc.), offset information between common resource blocks and SSBs (absolute SSB position in carrier is transmitted through SIB 1), and the like. The SIB1 parameter set information also applies to some messages used in a random access procedure for accessing the base station after the UE completes the cell search procedure. 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 above-mentioned RMSI may refer to SIB1 (system information block 1), and SIB1 is periodically (e.g., 160ms) 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 (control resource set) information for scheduling SIB1 on PBCH. The UE uses the SI-RNTI in CORESET to identify the scheduling information for SIB 1. The UE acquires SIB1 on PDSCH according to the scheduling information. The remaining SIBs except for the 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. Specifically, the random access preamble is periodically transmitted to the base station on the PRACH, which includes consecutive radio resources in a specific time slot that is repeated. 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), a UL grant (uplink radio resource), a temporary C-RNTI (temporary cell-radio network temporary identifier), and a 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 in order to indicate to which UE the included UL grant, temporary C-RNTI, and TAC are valid. The random access preamble identifier may be an identifier of a random access preamble received by the base station. The TAC may be included as information 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 a valid random access response, the UE processes information included in the random access response and performs scheduled transmissions to the base station. For example, the UE applies the TAC and stores the 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 the UL grant. In this case, information identifying the UE must be included in the data.

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

The downlink control channel in NR is transmitted in CORESET (control resource set) having a length of 1 to 3 symbols, 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 in order to ensure the flexibility of the system. CORESET (control resource set) refers to the time-frequency resources used for downlink control signals. The UE may decode the control channel candidates using one or more search spaces in the CORESET time-frequency resources. CORESET-specific QCL (quasi co-location) assumptions are configured and used to provide information about the analog beam direction, and the characteristics of delay spread, doppler shift, and average delay, which are assumed by existing QCLs.

Figure 7 shows CORESET.

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

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 a 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 meaning used currently or in the past, or as meaning 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 satisfy various QoS requirements per specific and specific usage scenario, compared to LTE/LTE-advanced. In particular, enhanced mobile broadband (eMBB), mass machine type communication (mtc), and ultra-reliability and low latency communication (URLLC) are defined as representative usage scenarios for NRs. To meet the requirements of each usage scenario, it is required to design NR to have a more flexible frame structure than LTE/LTE-advanced.

Since each usage scenario imposes different requirements on data rate, delay, coverage, etc., there is a need for a method of efficiently multiplexing mutually different radio resource units based on a parameter set (e.g., subcarrier spacing (SCS), subframe, Transmission Time Interval (TTI), etc.) as a solution to efficiently meet the requirements of different usage scenarios on a frequency band provided to an NR system.

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

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

Thus, a slot may consist of 14 symbols. All symbols may be used for DL transmission or UL transmission, or symbols may be used in the configuration of DL part + gap + UL part, depending on the transmission direction of the corresponding slot.

Further, the mini-slots have been defined to consist of fewer symbols than the slots in the parameter set (or SCS), and as a result, a short time-domain scheduling interval can be configured for UL/DL data transmission or reception based on the 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 case of transmitting or receiving latency critical data, such as URLLC, it may be difficult to meet latency requirements 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). For this purpose, a mini-slot may be defined that is made up of fewer OFDM symbols than the slot. Scheduling for delay critical data, such as URLLC, can 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 a TDM and/or FDM manner, thereby scheduling data according to delay requirements based on the length of the slot (or mini-slot) defined by the parameter sets. For example, as shown in FIG. 8, when the SCS is 60kHz, the symbol length is reduced to 1/4 for the symbol length when the SCS is 15 kHz. Therefore, 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.25 ms.

Therefore, since SCS different from each other or TTI length different from each other is defined in NR, a technique for satisfying the requirements of each of URLLC and eMBB has 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 the PDCCH. The control channel element is defined as a resource element (CCE) for transmitting the PDCCH. In NR, a control resource set (CORESET), which is 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 >

Typical LTE systems support scalable bandwidth operation for arbitrary LTE CCs (component carriers). That is, according to a frequency deployment scenario, an LTE provider may configure a bandwidth of minimum 1.4MHz to maximum 20MHz when configuring a single LTE CC, and a conventional LTE UE supports a transmission/reception capability of a bandwidth of 20MHz for the single LTE CC.

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

Specifically, one or more bandwidth parts may be configured by a single serving cell configured for the UE in the 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. Further, 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 part and/or one uplink bandwidth part in each serving cell, so that these are used for uplink/downlink data transmission/reception by using radio resources of the corresponding serving cell.

Specifically, 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 parts may be configured for each UE through dedicated RRC signaling, and a default bandwidth part for fallback operation may be defined for each UE.

It can be defined that a plurality of downlink and/or uplink bandwidth parts are simultaneously activated and used according to the capability of the UE and the configuration of the bandwidth part in the serving cell. However, it is defined in NR rel-15 that only one Downlink (DL) bandwidth part and one Uplink (UL) bandwidth part at a time in a UE are activated and used.

Discontinuous transmission indication for DL

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

According to 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 usage scenarios provided by NR and LTE/LTE-a systems, the importance of 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 requirements, in case of UL data transmission for URLLC, UL data transmission may be performed by preempting a portion of the 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 that is sensitive to latency requirements while performing UL data transmission for an eMBB UE, the URLLC UE may transmit corresponding UL data by preempting a portion of the UL data transmission resources that have been scheduled or allocated to the embbe.

To this end, in order to suspend UL data channel (PUSCH) transmission of a UE currently transmitting UL data (e.g., an eMBB UE) and 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) cancel indication" is used; however, the disclosed embodiments are not limited to such specific terms. 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, the disclosed embodiments are not limited to these terms.

Embodiment 1 monitoring information configuration for UL cancel indication

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

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

Thus, when defining UL cancellation indication information for a UE to be transmitted via a UE-specific PDCCH or a PDCCH common to a group of UEs, the 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 cancel indication may be performed regardless of whether there is a monitoring configuration for the DL preemption indication.

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

Specifically, the monitoring configuration information for the UL cancellation indication may include control resource set (CORESET) and search space configuration information for monitoring the 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 receiving UL cancel indication information

1. Scheme for suspending remaining PUSCH transmission

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

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

At this time, the K value may be set by the base station/network and then sent to the UE through explicit signaling. For example, the value of K 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 value of K 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 sent to the UE.

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

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

In one embodiment, fig. 10 illustrates performing PUSCH resource allocation within a slot boundary of a slot. That is, according to this case, slot-based or mini-slot-based PUSCH resource allocation may be performed. The UE may perform PUSCH transmission through the allocated slots 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 the value of K (as a timing gap).

In another embodiment, fig. 11 illustrates performing PUSCH resource allocation 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 perform PUSCH transmission normally through one or more remaining allocated slots (from # n + 1).

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

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

As shown in fig. 13, a UE that has received UL cancellation indication information may suspend PUSCH transmission corresponding to only OFDM symbols corresponding to a portion of the duration of an ongoing PUSCH transmission.

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

At this time, as shown above, the K value may be set by the base station/network and then sent to the UE through explicit signaling. For example, the value of K 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 value of K 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 sent to the UE.

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

Further, in a similar manner to the above-described method of determining the value of K, the value of M, 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 value of M 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 value of M 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 sent to the UE.

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

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

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

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

In one embodiment, the transmission of the UL cancellation indication information when the UE performs PUSCH transmission may be performed through DL. In another embodiment, the transmission of the UL cancellation indication information may be performed by a cell adjacent to a cell where 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 only an example; accordingly, the present disclosure embodiments are not limited to a specific method in a case where the UL cancellation indication information may be received while the UE performs PUSCH transmission.

Accordingly, if a UL cancel indication request is invoked for any other UE requiring low latency while the UE is transmitting a UL data channel, the latency requirement may be fulfilled since transmission of the UL channel for that any other UE may be performed with high priority. According to this, since transmission of the UL channel of the URLLC UE can be performed while the eMBB UE performs UL data channel transmission, multiplexing of the URLLC service and the eMBB service can be performed efficiently.

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

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

Referring back to fig. 14, in step S1420, the UE may monitor the 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 while the UE performs PUSCH transmission, or may be received independently of PUSCH transmission.

The UE may monitor whether the UL cancellation indication information is transmitted based on the monitoring configuration information while transmitting the 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 the UL cancellation indication information.

In one embodiment, with respect to the monitoring period of the UL cancellation indication information, in order to avoid interference with URLLC data requesting preemption, it is necessary for a UE currently transmitting UL data (e.g., an eMBB UE) to suspend a corresponding UL data transmission before a URLLC UE for transmitting URLLC data starts UL data transmission. Considering the 1ms delay requirement of URLLC traffic, if the subcarrier spacing is short, non-slot level monitoring may be performed on the 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 a higher layer parameter such as monitorngsymbols within the slot.

In one embodiment, if a UL-specific DCI format is defined for the UL cancellation indication, the UE may monitor a UE-specific PDCCH transmitted through a UE-specific CORESET or UE-specific search space in order to receive UL cancellation indication information. When the UL cancellation indication information is sent over the UE-specific PDCCH, the base station/network may configure (e.g., indicate) the UE to monitor for UL cancellation indications over 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 transmitting UL cancellation indication information over a PDCCH common to a UE group, the base station/network may configure (e.g., indicate) the UE to monitor for UL cancellation indications over cell-specific/UE group-common higher layer signaling.

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 the UL cancellation indication information when scheduling UL transmissions. Further, since the UE currently transmitting UL data requires a processing time of UL cancellation indication information, the UE may not monitor the UL cancellation indication information if the last symbol of UL data transmission is earlier than the processing time.

Accordingly, a UE currently transmitting UL data may monitor the UL cancellation indication information during a time period from a reception time of the UL grant to a completion time of processing of the UL cancellation indication information before a last symbol of the UL data transmission. Further, since the start time of monitoring may be later than the reception time of the UL grant, the base station may provide the 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 ongoing PUSCH transmission that have not been used. In one embodiment, the UE may suspend transmission of UL data using the resource on which the transmission was cancelled, in the event that the UL cancellation indication was successfully decoded. In this case, the resource on which the transmission is cancelled may be allocated for transmission of the UL channel for any other UE that has requested preemption.

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

In one embodiment, the value of K may be set by the base station/network as a preconfigured timing gap and then sent to the UE through explicit signaling. In another embodiment, the value of K may be set implicitly by the UE's capabilities or by the UE's capabilities and then sent to the UE through explicit signaling. In yet another embodiment, the value of K may be set implicitly as a function of numerology or SCS value of DL or UL, or as a function of the monitoring period value of the cancellation indication. Therefore, the K value may include the time taken for the base station to transmit the UL cancellation indication information and the 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 within a slot in which the UL cancel 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 within a slot in which the 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 on an M value, which is a preconfigured pause duration for pausing transmission of UL data. In one embodiment, the value of M, which is a preconfigured suspension duration, may be set by the base station/network and then sent to the UE by explicit signaling. In this case, the value of M may be set by the base station/network and then sent to the UE through UE-specific higher layer signaling. In another embodiment, the value of M 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, e.g., by being included in corresponding UL cancellation indication information via L1 control signaling, and then transmitted to the UE.

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

If information on the value of M as the pause duration is further included in the UL cancellation indication information, the UE may pause UL data transmission during the pause duration and resume UL data transmission after the pause duration elapses.

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

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

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

In one embodiment, when a 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 requiring low latency (e.g., a URLLC UE). The base station may configure the UL cancellation indication information to send to a UE currently sending UL data (e.g., an eMBB UE).

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 the low latency requirements for URLLC UEs, the slot offset between the UL grant of a URLLC UE and the corresponding scheduled PUSCH may be configured to be smaller than the slot offset between the UL grant of the UE currently transmitting UL data and the corresponding scheduled PUSCH, respectively. In another embodiment, the time taken for processing the 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 the UL grant and preparing PUSCH transmission by the URLLC UE.

In one embodiment, the UL cancellation indication information may include information on the cancelled UL resource. Based on this, the UE currently transmitting UL data can timely suspend 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 the UL cancellation indication information.

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

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 monitoring for UL cancellation indications through UE-specific higher layer signaling.

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

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

If a UL-specific DCI format is defined for the UL cancellation indication, the base station may transmit the 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 a higher reliability than the DL preemption indication information. This is because, before the URLLC UE transmits PUSCH, UL cancellation indication information is used to indicate that a UE currently transmitting UL data (e.g., an eMBB UE) cancels an ongoing or upcoming PUSCH, while DL preemption indications are used to indicate to a UE currently receiving PDSCH that has been cancelled by the base station (e.g., an eMBB UE). Therefore, in order to avoid collision with the UE currently transmitting UL data and achieve the overall reliability of URLLC, it is necessary to improve the reliability of UL cancellation indication information.

To this end, in one embodiment, more time-frequency resources may be allocated for the 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, to improve the reliability of the UL cancellation indication information, the payload size of the UL cancellation indication information may be reduced. For example, even when a URLLC UE occupies only a portion of BWP in a few symbols, one bit may be used to represent the entire BWP within one slot. If a UE currently transmitting UL data initiates a PUSCH transmission in a slot in which UL cancellation indication information is received, the UE may suspend the PUSCH transmission for 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 a PUSCH transmission.

When the UL cancellation indication information is transmitted, the UE may suspend PUSCH transmission in one or more remaining OFDM symbols, which have not been used, in resources allocated to ongoing PUSCH transmission. The UE may suspend PUSCH transmission after a preconfigured timing gap K 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 or corresponding to the last symbol in which UL cancellation indication information is transmitted.

In one embodiment, the value of K may be set by the base station/network as a preconfigured timing gap and then sent to the UE through explicit signaling. In another embodiment, the value of K may be set implicitly by the UE's capabilities or set by the UE's capabilities and then sent to the UE through explicit signaling. In yet another embodiment, the value of K may be set implicitly as a function of numerology or SCS value of DL or UL, or as a function of the monitoring period value of the cancellation indication. Therefore, the K value may include the time taken for the base station to transmit the UL cancellation indication information and the time taken for the UE to process the UL cancellation indication information.

In one embodiment, the UL cancellation indication information may further include information on an M value, which is a preconfigured pause duration for pausing transmission of UL data. In one embodiment, the value of M, which is a preconfigured suspension duration, may be set by the base station/network and then sent to the UE through explicit signaling. In this case, the value of M may be set by the base station/network and then sent to the UE through UE-specific higher layer signaling. In another embodiment, the value of M 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, e.g., by being included in corresponding UL cancellation indication information via L1 control signaling, and then transmitted to the UE.

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 over the one or more allocated resources.

Accordingly, when a UE transmits a UL data channel, if a UL cancellation indication request for any other UE requiring low latency is invoked, the latency requirement may be fulfilled, since 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 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 a UE according to the embodiment of the present disclosure described above.

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

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

The transmitter 1620 is used to transmit signals, messages and data required to perform the above-described embodiments to the UE. The receiver 1630 is used for receiving signals, messages and data required for performing the above-described embodiments from the UE.

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 monitoring configuration information for the UL cancellation indication through UE-specific higher layer signaling for the UE. In yet another embodiment, if a UE group common DCI format is defined for the UL cancellation indication, the transmitter 1620 may transmit the monitoring configuration information for the UL cancellation indication through cell-specific/UE group common higher layer signaling 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 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, which have not been used, in resources allocated to ongoing PUSCH transmission. The UE may suspend PUSCH transmission after a pre-configured timing gap K from the time when transmission of UL cancellation indication information is performed. For example, the UE may suspend PUSCH transmission after K corresponding to a predetermined number of symbols from the last symbol in which UL cancellation indication information is transmitted or the UL symbol corresponding to the last symbol in which UL cancellation indication information is transmitted.

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

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

Referring to fig. 17, a UE1700 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 a corresponding channel. The transmitter 1730 may transmit UL data based on the UL data resource allocation information.

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

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 the UL cancellation indication information.

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

The controller 1720 controls the overall operation of the UE1700 required to perform the method of transmitting UL data according to the embodiment of the present disclosure described above.

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

In one embodiment, if a UL-specific DCI format is defined for the UL cancellation indication, the controller 1720 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 the UL cancellation indication information is sent over the UE-specific PDCCH, the base station/network may configure the UE to monitor for UL cancellation indications over UE-specific higher layer signaling.

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

The controller 1720 may suspend the 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, which have not been used, in resources allocated to ongoing PUSCH transmission. The controller 1720 may suspend PUSCH transmission after the preconfigured timing gap K from the time the UL cancellation indication information is transmitted. For example, the controller 1720 may suspend PUSCH transmission after K corresponding to a predetermined symbol number from the last symbol in which UL cancellation indication information is transmitted or an UL symbol corresponding to the last symbol in which UL cancellation indication information is transmitted.

In one embodiment, the value of K may be set by the base station/network as a preconfigured timing gap and then sent to the UE1700 through explicit signaling. In another embodiment, the value of K may be set implicitly by the capabilities of the UE1700 or by the capabilities of the UE1700 and then sent to the UE through explicit signaling. In yet another embodiment, the value of K may be set implicitly as a function of numerology or SCS value of DL or UL, or as a function of the monitoring period value of the cancellation indication. Accordingly, the K value may include the time taken for the base station to transmit the UL cancellation indication information and the time taken for the UE1700 to process the 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 within a slot in which the UL cancel 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 aggregation slots, the controller 1720 may suspend UL data transmission only within a slot in which the UL cancellation indication information is received. In another embodiment, the controller 1720 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 on an M value, which is a preconfigured pause duration for pausing transmission of UL data. In one embodiment, the value of M, which is a preconfigured suspension duration, may be set by the base station/network and then sent to the UE1700 through explicit signaling. In this case, the value of M may be set by the base station/network and then sent to the UE through UE-specific higher layer signaling. In another embodiment, the value of M may be sent to UE1700 through cell-specific/UE group-common higher layer signaling. In yet another embodiment, the M value may be dynamically set, e.g., by being included in corresponding UL cancellation indication information via L1 control signaling, and then transmitted to the UE.

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

If information on the value of M, which is a pause duration, is further included in the UL cancel indication information, the controller 1720 may pause UL data transmission during the pause duration and resume the UL data transmission after the pause duration elapses.

In one embodiment, if resources for UL data transmission are allocated to one slot, the controller 1720 may suspend UL data transmission within the slot in which the UL cancel indication information is received. If there are one or more remaining symbols after the M value has passed, controller 1720 may recover 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 passed and the slots therefrom.

The above 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. Further, all terms disclosed herein may 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 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, a process, or a function that performs the above-described functions or operations. The software codes may be stored in memory units or may be driven by processors. The memory unit may be provided inside or outside 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 a computer-related entity, either hardware, a combination of hardware and software, or software in execution. For example, the aforementioned components 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, an application running in a controller or processor and the controller or processor can both be a component. One or more components may be provided within a process and/or thread of execution and these components may be provided within a single device (e.g., a system, computing device, etc.) or may be distributed over two or more devices.

The above-described embodiments of the present disclosure have been described for illustrative purposes only, and it will be understood by those of ordinary skill in the art that various modifications and changes may be made thereto without departing from the scope and spirit of the present disclosure. Furthermore, the embodiments of the present disclosure are not intended to be limiting, but 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 the embodiments. The scope of the present disclosure should be construed based on the appended claims, and all technical concepts included within the scope equivalent to the claims should be interpreted as belonging to the present disclosure.

Cross Reference to Related Applications

If applicable, the present application claims priority from patent application 10-2018 § 0018740, filed on 14.2018 in Korea, and from patent application 10-2019 § 0015479, filed on 11.2019 in 2.2018, all of which are incorporated herein by reference, according to 35USC § 119 (a). In addition, based on korean patent application, the non-provisional application requires priority in countries other than the united states for the same reason, and the entire contents thereof 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 the 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 the UL data being transmitted based on the UL cancellation indication information.

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 UE group-common DCI.

4. The method of claim 1, wherein the suspension of the transmission of the UL data is performed after a pre-configured timing gap has elapsed since the time the UL cancellation indication information was received.

5. The method of claim 1, wherein the suspension of the transmission of the 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.

6. The method of claim 1, wherein the UL cancellation indication information further comprises information on a preconfigured pause duration for pausing 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.

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

configuring monitoring configuration information for the UL cancellation indication information;

transmitting the monitoring configuration information to a UE that is transmitting UL data; and

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

8. The method of claim 7, 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.

9. The method of claim 7, wherein the UL cancellation indication information is indicated by UE-specific Downlink Control Information (DCI) or UE group-common DCI.

10. The method of claim 7, wherein the UE suspends transmission of the UL data after a preconfigured timing gap has elapsed since the time the UL cancellation indication information was received.

11. The method of claim 7, 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.

12. The method of claim 7, wherein the UL cancellation indication information further includes information on a preconfigured pause duration for pausing 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.

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

a transmitter which transmits UL data based on the 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.

14. The user equipment of claim 13, 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.

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

16. The user equipment of claim 13, wherein the controller suspends transmission of the UL data after a preconfigured timing gap has elapsed since the time the UL cancellation indication information was received.

17. The user equipment of claim 13, 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.

18. The user equipment of claim 13, wherein the UL cancellation indication information further comprises information on a preconfigured pause duration for pausing transmission of the UL data, and

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