CN111801975A

CN111801975A - Grant based uplink transmission

Info

Publication number: CN111801975A
Application number: CN201980011306.8A
Authority: CN
Inventors: 柳光
Original assignee: Jiekai Communications Shenzhen Co Ltd
Current assignee: Jiekai Communications Shenzhen Co Ltd
Priority date: 2018-02-08
Filing date: 2019-01-25
Publication date: 2020-10-20
Anticipated expiration: 2039-01-25
Also published as: CN111801975B; GB201802058D0; GB2570899A; GB2570899B; WO2019154106A1

Abstract

A method and system for uplink data transmission from a user equipment UE to a base station, wherein transmissions from other UEs may be interrupted. The indication transmitted from the base station to the UE is used to indicate that the operation is interrupted.

Description

Grant based uplink transmission

Technical Field

The present application relates to grant based uplink transmission systems in cellular radio systems, and in particular to resource sharing in such systems.

Background

Wireless communication systems, such as third generation (3G) mobile telephone standards and techniques are well known. The 3G standards and technologies were developed by the Third Generation Partnership Project (3 GPP). Third generation wireless communications were developed to support macro cellular mobile telephone communications. Communication systems and networks are evolving towards broadband mobile systems.

In a cellular Radio communication system, a User Equipment (UE) is connected to a Radio Access Network (RAN) via a Radio link. The RAN includes: a set of base stations providing radio links to UEs located in cells covered by the set of base stations; and an interface to a Core Network (CN) that provides over Network control. It should be noted that the RAN and the CN perform their respective functions on the entire network. For convenience, the term "cellular network" refers to the combined RAN and CN, and as will be appreciated, refers to the various systems that perform the disclosed functions.

The third generation partnership project has developed a so-called Long Term Evolution (LTE) system, i.e., an Evolved Universal terrestrial Radio Access Network (E-UTRAN), in which one or more macrocells are supported by a base station eNodeB or eNB (Evolved NodeB). Recently, LTE has further evolved towards so-called 5G or NR (New Radio) systems, where one or more macrocells are supported by a base station gN. NR proposes the use of an Orthogonal Frequency Division Multiplexing (OFDM) physical transmission format.

A cellular radio network may provide a series of services to a UE in order to select a service that is appropriate for the type of data being transmitted. For example, Ultra-Reliable Low Latency Communication (URLLC) services and some large-scale machine type Communication (mtc) services may require very small Latency (less than 1ms) and high reliability (packet loss rate less than 10)^-5). A typical feature of transmitting data over these services is that small packets arrive in an infrequent (infrequent), sporadic (sporadic) manner.

Fig. 1 shows an example of (a) grant-free uplink transmission based on a grant (b) between a UE and a base station (gNB). In a grant-based system, when a UE wants to transmit data, a Scheduling Request (SR) message is transmitted (step 100). In step 101, the base station allocates uplink resources for the data and transmits an indication of these resources. The UE then transmits the data to the base station using the resources in step 102. In this system, there must be a delay of at least one Round Trip Time (RTT) before transmission begins.

As shown in fig. 1(b), round-trip delay can be avoided by using a grant-free (grant-free) system. In this system, upstream resources are pre-allocated so that when a packet arrives at step 103, it can be transmitted at step 104 using the next available resource.

Although the unlicensed transmission reduces latency, the resource requirements may increase. Resources are allocated to each UE, but since there is little data to transmit, the allocated resources are likely to be unused. Since the reserved resources are not used, the resource efficiency is low. Resources may be allocated on a shared basis, but this inevitably leads to potential conflicts between UEs sharing resources. The greater the degree of sharing (giving greater efficiency), the greater the probability of collision. The probability of collision is 10-3 and the corresponding channel usage is 4.5%, meaning that 95.5% of the resources are unused.

Therefore, there is a need for a system that can reduce latency while ensuring high reliability and high resource usage.

Disclosure of Invention

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

The application provides an uplink data transmission method from User Equipment (UE) to a base station in a cellular wireless network, which comprises the following steps: transmitting a scheduling request from the UE to the base station over the wireless link to transmit data; receiving the request at a base station and allocating uplink resources for the transmission, wherein the allocated uplink resources overlap with resources used by other UEs; and transmitting a downlink indication from the base station over a wireless link, the downlink indication comprising: at least one resource indication field, each resource indication field comprising an indication of resources used by the received scheduling request; and/or at least one interruption indication field, each interruption indication field comprising an indication of a UE using overlapping resources to interrupt transmission.

The resource indication field may also include an indication of the allocated uplink resources.

The method may further comprise a configuration phase comprising: the base station allocates at least one scheduling request resource and/or at least one uplink resource for data transmission to the UE, wherein each scheduling request resource has a corresponding resource index.

The method may also include transmitting, from the base station to the UE, an indication of scheduling request resources and/or uplink resources allocated to the UE.

Each allocated scheduling request resource may be allocated a scheduling request resource index, the indication of scheduling request resources comprising the scheduling request resource index.

Each scheduling request resource may include a unique combination of time, frequency, and sequence resources.

The at least one allocated scheduling request resource may also be allocated to more UEs communicating with the base station.

At least one allocated scheduling request resource may be allocated only to the UE.

The indication of the allocated uplink resources may include an offset before the UE starts uplink data transmission using the allocated resources for data transmission.

The indication of allocated resources may comprise a number of repetitions of data to be transmitted.

The downlink indication may include a plurality of resource or outage fields, each resource or outage field being associated with a different UE.

The method may further comprise: before transmitting the downlink indication, the base station distributes interruption indication to at least one UE which is communicated with the base station, and sends the interruption indication to the at least one UE.

The interruption indication may include an interruption ID, wherein an interruption indication field of the UE using the overlapping resources includes the interruption ID.

The interruption indication may comprise an uninterrupted indicator.

The interruption indication may be selected from a set comprising at least one interruption ID and an interruption free indicator, wherein the interruption indication field of the UE using the overlapping resources comprises the interruption ID.

Each interrupt ID may be assigned to one UE using overlapping resources.

Each resource indication field may be used for a UE transmitting a URLLC/MTC channel.

Each outage indication field may be used for one or more UEs transmitting an eMBB channel.

The method may further comprise: an existing resource allocation that overlaps with the allocated uplink resource is identified at the base station.

The present application also provides a method for uplink data transmission from a user equipment UE to a base station in a cellular wireless network, the method being performed by the UE, the method comprising: transmitting a scheduling request from the UE to the base station over the wireless link to transmit data; receiving, at the UE, a downlink indication, the downlink indication comprising: at least one resource indication field, each resource indication field comprising an indication of resources used by the received scheduling request; and/or at least one interruption indication field, each interruption indication field comprising an indication of a UE using overlapping resources to interrupt transmission.

The method may further comprise: in a configuration phase, receiving an indication of at least one scheduling request resource available for the UE to transmit a scheduling request, each scheduling request resource having a corresponding resource index, and/or an indication of at least one uplink resource allocated to the UE for data transmission.

The indication of the allocated uplink resources may include an indication of an offset before the UE starts uplink data transmission using the allocated resources for data transmission.

The indication of allocated uplink resources may comprise an indication of a number of repetitions of data to be transmitted.

The downlink indication may include a plurality of downlink indication fields, each downlink indication field being associated with a different UE and including an indication of allocated resources and an indication of the UE to discontinue transmission.

The method may further comprise: receiving an indication of outage from the base station.

The interruption indication may include an interruption ID, wherein an interruption indication field of a UE using overlapping resources includes the interruption ID.

The interruption indication may comprise an uninterrupted indicator.

The interruption indication may be selected from a set comprising at least one interruption ID and an interruption free indicator, wherein the interruption indication field of a UE using overlapping resources comprises the interruption ID.

The interruption indication field may include at least one interruption ID allocated to a UE using overlapping resources.

The UE using the overlapping resources may be a UE transmitting an eMBB channel.

The present application also provides a method for uplink data transmission from a user equipment UE to a base station in a cellular wireless network, the method being performed by the UE, the method comprising: receiving an interruption indication from a base station over a wireless link, the interruption indication selected from a set comprising at least one interruption ID and an interruption free indicator; if the interruption indication is an interruption ID, monitoring downlink indication transmission from the base station, and if the received downlink indication comprises the interruption ID, interrupting the uplink transmission during the resource period indicated by the downlink indication; and if the interruption indication is an interruption-free indicator, configuring the UE not to monitor the downlink indication.

The application also provides a UE configured to perform the above method.

The present application also provides a method for uplink data transmission from a user equipment UE to a base station in a cellular wireless network, the method being performed by the base station, the method comprising: receiving a request from a UE at a base station to transmit data and allocating uplink resources for the transmission, wherein the allocated uplink resources overlap with resources used by other UEs; transmitting a downlink indication from the base station over a wireless link, the downlink indication comprising: at least one resource indication field, each resource indication field comprising an indication of resources used by the received scheduling request; and/or at least one interruption indication field, each interruption indication field comprising an indication of a UE using overlapping resources to interrupt transmission.

The interruption indication may comprise an uninterrupted indicator.

Each interrupt ID may be assigned to one UE using overlapping resources.

The present application also provides a base station configured to perform the above method.

The non-transitory computer readable storage medium may include at least one of a hard disk, a Compact disc Read Only Memory (CD-ROM), an optical Memory, a magnetic Memory, a Read Only Memory (ROM), a Programmable Read Only Memory (PROM), an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), and a Flash Memory.

Drawings

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Elements in the figures have been simplified and are not necessarily drawn to scale. For ease of understanding, reference numerals have been included in the various figures.

FIG. 1 is a schematic diagram of an authorization-based and authorization-free communication process;

FIG. 2 is a schematic diagram of an authorization-based protocol;

FIG. 3 is an exemplary diagram of SR resource allocation;

fig. 4 is an exemplary diagram of downlink indication transmission;

fig. 5 is an exemplary diagram of a format of a downstream indication;

FIG. 6 is a schematic diagram of a transmission from a UE;

FIG. 7 is a diagram of an example of the format of an interrupt ID;

fig. 8 is a diagram of an example of communication exchange using interrupt IDs.

Detailed Description

The embodiments described herein are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Figure 2 illustrates an authorization-based communication system that provides for efficient use of resources while managing system latency. The following description considers low latency (particularly URLLC) data and services in particular, but the principles, methods and systems are equally applicable to any type of data and services.

In step 200, the UE configures at least one defined set of resources for transmitting SR messages related to low latency data transmission. The resources may be time, frequency, and/or sequence resources (sequences) that may be used for the UE to transmit the SR message. Each unique combination (unique combination) of time, frequency and/or sequence is assigned an SR resource index (index). A cyclic shift (cyclic shift) of one sequence is a different sequence to other cyclic shifts.

In step 201, the UE also configures resources for transmitting low latency data, which may include, for example, detailed information (details) of time and frequency resources, redundancy versions, coding and modulation schemes, periods, and demodulation reference signals DMRSs. In

steps

200 and 201, the configuration information may be considered pre-configuration information, as the configuration is set before the need for resources used by the service is known.

The UE selects resources for transmitting the SR message from among the allocated SR resources upon receiving a data packet for transmission (e.g., from an upper layer of the UE) in step 202, and transmits the SR message using the resources in step 203. The SR resources may be selected randomly or according to a predefined method. The SR message may include an SR resource index, or other indication of the use of SR resources.

After receiving the SR message, the base station allocates appropriate uplink resources for uplink data transmission, and transmits a downlink indication in step 204. The downlink indication uses the SR resource index to address (addresses) a particular UE, or may implicitly (implicitly) indicate the SR resource index, e.g., by indicating time, frequency, resource block RB, or sequence. The downlink indication may also include a description (description) of resources for uplink transmission, which may be a subset of resources allocated to the UE.

The downlink indication may also include an indication to the UE and/or other UEs to interrupt (suspend) transmission on resources used for low latency data transmission associated with the SR message. The information (inclusion) contained in the interruption information allows the resources allocated to the UE to be reused for other transmissions, which are interrupted when the resources are needed for low latency data. As mentioned above, low latency data is typically characterized by infrequent transmission of small packets, and therefore these resources are only used on an infrequent basis for low latency data transmission. Thus, the information contained in the interrupt information allows these resources to be used for most of the time not used for low latency data transmission. A typical application of these resources is the transmission of eMBB data on the PDSCH. Such transmissions may take the entire time of a slot and therefore are likely to have begun before the resources are allocated for low latency data.

In step 205, the UE transmits uplink data using the indicated resources. Although these resources may be used by another UE or a different service, these other UEs or services may be interrupted so that the UE may use these resources without any risk of collision.

Specific flow aspects of fig. 2 will be described in more detail below. It is noted that aspects are described sequentially for convenience, but are disclosed equally when used in combination with all or part of them, or alone.

As described above, the UE is allocated a set of SR resources or pool of SR resources (pool). Each SR resource may be allocated one index of #0 to # K-1. Each resource is a unique combination of time, frequency, and/or sequence resources. The number of resources # K is selected by the system (especially, the base station (gNB)) according to a target collision rate of SR messages. The collision rate also depends on the number of UEs using the resource pool and the rate at which data packets arrive at the UEs for uplink transmission.

For example, the system may use 14 OFDM symbols per millisecond (ms), with one mini-slot defined as 2 OFDM symbols. If SR and data resources are allocated at each mini-slot, there are 7000 SR and data transmission opportunities (opportunities) per second. If 100 UEs use this resource pool and each UE has a packet arrival rate of 0.001 (7 packets per second ready for transmission), the target collision rate is 10-5 and the corresponding channel usage is 0.43%. From this, it can be calculated that K.gtoreq.23, as shown in Table 1 below.

TABLE 1

The required collision rate can therefore reach 23 resources per 100 UEs, which is a significant improvement compared to the 100 resources required for each UE-specific allocation.

However, if the packet arrival rate is increased to 0.01 (70 packets per second per UE), then under all other assumptions above, 223 SR resources are needed, and therefore the dedicated allocation is more efficient.

Thus, the system may allocate different resources for each UE depending on the expected behavior of the UE. The resources may be shared between fewer UEs with higher data packet rates and between more UEs with lower data packet rates, or UEs with higher data packet rates may be allocated dedicated resources.

Fig. 3 shows an example of resource allocation for a group of 20 UEs. The 5 sequences may be used across 2 RBs, providing 10 unique resources, each resource assigned a unique SR resource index. The UEs #0- #3 are determined to have a higher packet arrival rate and are therefore allocated dedicated SR resources (SR resource indices #0- # 3). The UEs #4- #19 have lower packet arrival rates and thus share the SR resource pool (SR resource indices #4- # 19).

The high and low packet arrival rates are related to the target collision rate, and the high target collision rate can accept the high packet arrival rate, so the threshold value between the high and low packet arrival rates is relatively high. Knowing the packet arrival rate of the UE can derive the configuration of the intended UE to report to the gNB at connection setup or based on the historical behavior of the UE. For example, the gNB may configure a point (dot) to monitor packet arrival rates to determine future possible rates. This is reasonable because URLLC is mainly used for plant control, and its service mode is almost static.

Fig. 4 shows an example of a timing diagram for the downlink indication.

To address a particular UE (or group of UEs), the downlink indication may include one or more SR resource indices, or a combination of parameters, e.g., a combination of RB index and sequence number, mapped to the desired UE. The downlink indication may further comprise a resource description indicating the resources, in particular the subset of resources allocated at step 201 of fig. 2 described above. The downlink indication may also include an offset (offset) and a repetition parameter.

In fig. 4, SR messages are transmitted at 400 and corresponding downlink indications are transmitted at 401. In this example, the downlink indication includes an offset 402 of 2 and a repetition number of 2. Thus, the uplink data is first transmitted at the second opportunity 403 and repeated once at 404. The minimum or default offset is 1, and the use of a higher value allows flexibility in scheduling. The number of repetitions may be set according to the particular reliability requirements of the data.

The downlink indication message may be structured into a set of downlink indication fields, such that one message may address more than one UE, as shown in fig. 5. Each downlink indication field corresponds to one UE, and includes an SR resource index and optionally also includes a data resource description. The UE identifies the SR resource index in the downlink indication field used for the SR message, and the UE uses the corresponding resource for uplink transmission.

As described above, the downlink indication may be used to allow a UE with low latency data to use resources by interrupting transmissions of other UEs (or the same UE). In particular, an ongoing eMBB transmission may be interrupted.

The following description uses fig. 6 to assist in the explanation. In the example of fig. 6, 5 PDSCHs 600 and 604 are scheduled by 5 DCIs 610-614 to 5 eMBB UEs. At step 201 of fig. 2, 4 low latency data transmission resources 620 and 623 are allocated to one or more UEs for low latency data transmission. As described above, the low latency resources 620-623 are only used occasionally, and therefore these resources may often be used for

PDSCH transmissions

601, 602, 603 that overlap with them.

The gNB knows which PDSCHs 600 & 604 and low latency data transmission resources 620 & 623 overlap and therefore knows which PDSCHs may be interrupted. The DCI transmitted to each UE includes an interruption indication to indicate how the UE should behave (behavior). The interrupt indication may be an interrupt ID or a "no interrupt" indication.

"uninterrupted" indicates transmission to UEs over PDSCH that does not overlap with low latency data transmission resources, since these UEs do not need to interrupt transmission even if low latency resources are used. In the example of fig. 6, this applies to UEs 0 and 4. Thus,

UEs

0 and 4 do not need to monitor downlink indications in the relevant time slots, and thus waste power by monitoring these indications can be avoided.

If the low latency resources do overlap with the PDSCH, the associated UE is assigned an interrupt ID. As shown in the example of fig. 6 in fig. 7, each UE 1-3 is assigned a unique interrupt ID. UEs that have been assigned the interruption ID are configured to monitor downlink indications in the relevant time slots, since these UEs may receive an indication to interrupt their PDSCH transmission. In the examples of fig. 6 and 7, each UE is assigned a unique interrupt ID. However, a common interrupt ID may be used for two or more UEs according to relative scheduling of PDSCH and low latency resources. For example, if the only low latency resource is 620, then

UEs

0, 3 and 4 would be set to no interruption and one interruption ID could be assigned to

UEs

1 and 2 since

UEs

1 and 2 would only interrupt together.

In transmitting the downlink indication, the gNB includes an interrupt ID corresponding to any UE using a resource that overlaps with the low latency resource indicated for use in the downlink indication. The UE receiving the interrupt ID is configured to extract resource details from the downlink indication and interrupt transmission during the time that the resource is used for low latency data transmission. The low latency resources may not occupy all the frequency resources used by the PDSCH of the UE, but the UE may interrupt all transmissions of the relevant channel, since reprocessing (reprocessing) signals according to the newly available resources may be difficult and must be done quickly. However, if such re-processing can be performed within the available time, then the partial transmission can continue on frequency resources to which no low latency transmission is allocated. In the example of fig. 6, some data transmissions from

UEs

1 and 3 may continue to be transmitted near low-latency resources.

Fig. 8 shows a message example of the UE and the configurations of fig. 6 and 7. In step 800, the DCI for each UE is used to indicate a non-interruption or interruption ID of the corresponding UE. In step 801, the gNB receives an SR message for short time (low latency) transmission and allocates resources 621. The downlink indication is transmitted in step 802, including the UE resource allocation transmitting the SR message, and also including the interrupt

IDs

1 and 2.

Since the UEs 1-3 are configured with the interrupt ID in step 800, each UE listens for the downlink indication to receive the message 802. The interrupt ID of UE1 is not included, so the UE continues to transmit on the PDSCH. However,

UEs

2 and 3 receive their interruption ID, and thus retrieve (retrieve) the resource details contained in the downlink indication. Then,

UEs

2 and 3 interrupt transmission on the PDSCH during the resources indicated in the downlink indication message and resume transmission once the allocated time period has elapsed.

Thus, the above disclosure provides a system in which collisions of low latency data are avoided, but are allowed to be used for other channels when low latency resources are not used for low latency data, to reduce efficiency losses (efficiency losses). With the interrupt ID, a message is transmitted in an active process (interrupt process) that is used to interrupt the transmission on the UE shared resource. In the examples of fig. 6 to 8, 2 bits are sufficient to indicate the interrupt ID, which is advantageous compared to another method using an RNTI (length of 16 bits) of the UE.

Although it is not described in detail that any device or apparatus forming part of a network may include at least one processor, memory unit, and communication interface, the processor, memory unit, and communication interface are configured to perform the methods of any aspect of the present application. Further options and choices are described below.

The signal processing functions in the embodiments of the present application, particularly the signal processing capabilities of the gNB and the UE, may be implemented by computing systems or architectures that are well known to those skilled in the art. The computing system may be a desktop, laptop or notebook computer, hand-held computing device (PDA, cell phone, palmtop, etc.), mainframe, server, client, or any other type of special or general purpose computing device as may be satisfactory or applicable to a given application or environment. The computing system may include one or more processors that may execute a general or special purpose processing engine such as, for example, a microprocessor, microcontroller or other control module.

The computing system may also include a main memory, such as a Random Access Memory (RAM) or other dynamic memory, for storing information and instructions to be executed by the processor. The main memory may also be used for storing temporary variables or other intermediate information during execution of instructions by the processor. The computing system may also include a Read Only Memory (ROM) or other static storage device for storing static information and instructions for execution by the processor.

The computing system may also include an information storage system including, for example, a media drive and a removable storage interface. The media drive may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a compact disk drive (CD) or Digital Video Drive (DVD) read-write drive (R or RW), or other fixed or removable media drive. The storage medium may include, for example, a hard disk, floppy disk, magnetic tape, optical disk, CD, DVD, or other fixed or removable medium that is read by and written to by a media drive. The storage media may include a computer-readable storage medium having stored thereon particular computer software or data.

In alternative embodiments, the information storage system may include other similar components for allowing computer programs or other instructions or data to be loaded into the computing system. These components may include, for example, a removable storage unit and interface, such as a program cartridge and cartridge interface, a removable memory (e.g., a flash memory or other removable memory module) and memory slot, and other removable storage units and interfaces that allow software and data to be transferred from the removable storage unit to the computing system.

The computing system may also include a communication interface. The communication interface may be used to allow software and data to be transferred between the computing system and external devices. For example, the communication interfaces can include a modem, a network interface (such as an Ethernet or other network card), a communication port (such as a Universal Serial Bus (USB) port), a PCMCIA slot and card, and the like. Software and data transferred via the communications interface are in the form of signals which may be electronic, electromagnetic, optical or other signals capable of being received by the communications interface medium.

In this application, the terms "computer program product," "computer-readable medium," and the like are used generally to refer to tangible media, such as memory, storage devices, or storage units. These and other forms of computer-readable media may store one or more instructions for use by a processor, including a computer system, to cause the processor to perform specified operations. These instructions, which are generally referred to as "computer program code" (which may be grouped in the form of computer programs or other groupings), when executed, enable the computer system to perform functions of embodiments of the present application. It is noted that the code may directly cause the processor to perform specified operations, may be compiled to do so, and/or may be combined with other software, hardware, and/or firmware elements (e.g., libraries for performing standard functions) to do so.

The non-computer readable medium may comprise at least one from the group of: hard disks, Compact disk Read Only memories (CD-ROMs), optical storage devices, magnetic storage devices, Read Only Memories (ROMs), Programmable Read Only Memories (PROMs), Erasable Programmable Read Only Memories (EPROMs), Electrically Erasable Programmable Read Only Memories (EEPROMs), and flash memories (flashmemories).

In embodiments implemented by software, the software may be stored in a computer-readable medium and loaded into the computing system using, for example, a removable storage drive. A control module (e.g., software instructions or executable computer program code) executed by a processor in a computer system causes the processor to perform functions as described herein.

Further, the present application may be applied in any circuit for performing signal processing functions in a network element. For example, it is further contemplated that a semiconductor manufacturer may employ the innovative concepts in the design of a stand-alone device, which may be a microcontroller (DSP) of a digital signal processor, an Application Specific Integrated Circuit (ASIC), and/or any other subsystem element.

For clarity of description, the foregoing description has described embodiments of the present application with reference to a single processing logic. However, the present application may equally well implement signal processing functions by means of a plurality of different functional units and processors. Thus, references to specific functional units are only to be seen as references to suitable means for providing the described functionality rather than indicative of a strict logical, physical structure or organization.

Aspects of the present application may be implemented in any suitable form including hardware, software, firmware or any combination of these. The present application may optionally be implemented, at least partly, as computer software, a computer software component, such as an FPGA device, running on one or more data processors and/or digital signal processors or configurable modules. Thus, the elements and components of an embodiment of the application may be physically, functionally and logically implemented in any suitable way. Indeed the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units.

Although the present application has been described with reference to the preferred embodiments, the above-described preferred embodiments are not intended to limit the present application, and the scope of the present application is defined by the following claims. Furthermore, while descriptions of features related to particular embodiments may appear, one skilled in the art may, in light of the present disclosure, appreciate various features of such embodiments. In the claims, the term "comprising" does not exclude the presence of other elements or steps.

Further, although individually listed, a plurality of means, elements or method steps may be implemented by e.g. a single unit or processor. Furthermore, although different features may comprise different claims, these may possibly advantageously be combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Likewise, the inclusion of a feature in one set of claims does not imply a limitation to this set of claims, but rather indicates that the feature is equally applicable to other claim categories, as appropriate.

Further, the ordering of features in the claims does not imply that the features must be performed in a particular order, and in particular the order of individual steps in a method claim does not imply that the steps must be performed in this order. Rather, the steps may be performed in any suitable order. Furthermore, singular references do not exclude a plurality. Thus, the singular forms "a", "an", "first", "second", etc. do not exclude the plural forms.

Although the present application has been described with reference to the preferred embodiments, the above-described preferred embodiments are not intended to limit the present application, and the scope of the present application is defined by the following claims. Furthermore, while descriptions of features related to particular embodiments may appear, one skilled in the art may, in light of the present disclosure, appreciate various features of such embodiments. In the claims, the term "comprising" or "including" does not exclude the presence of other elements.

Claims

1. A method for uplink data transmission from a user equipment, UE, to a base station in a cellular wireless network, the method comprising:

transmitting a scheduling request from the UE to the base station over the wireless link to transmit data;

receiving the request at a base station and allocating uplink resources for the transmission, wherein the allocated uplink resources overlap with resources used by other UEs; and the number of the first and second groups,

transmitting a downlink indication from the base station over a wireless link, the downlink indication comprising:

at least one resource indication field, each resource indication field comprising an indication of resources used by the received scheduling request; and/or

At least one interruption indication field, each interruption indication field comprising an indication of an interruption transmission by a UE using overlapping resources.

2. The method of claim 1, wherein the resource indication field further comprises an indication of the allocated uplink resources.

3. The method according to claim 1 or 2, further comprising a configuration phase comprising: the base station allocates at least one scheduling request resource and/or at least one uplink resource for data transmission to the UE, wherein each scheduling request resource has a corresponding resource index.

4. The method of claim 3, further comprising: transmitting, from the base station to the UE, an indication of scheduling request resources and/or uplink resources allocated to the UE.

5. The method according to claim 3 or 4, wherein each allocated scheduling request resource is allocated a scheduling request resource index, and wherein the indication of scheduling request resources comprises the scheduling request resource index.

6. The method of any of claims 3 to 5, wherein each scheduling request resource comprises a unique combination of time, frequency and sequence resources.

7. The method according to any of claims 3 to 6, characterized in that at least one allocated scheduling request resource is also allocated to more UEs communicating with the base station.

8. The method according to any of claims 3 to 6, characterized in that at least one allocated scheduling request resource is allocated only to the UE.

9. The method of claim 4, wherein the indication of the allocated uplink resources comprises an offset before the UE starts uplink data transmission using the allocated resources for data transmission.

10. The method of claim 4, wherein the indication of the allocated resources comprises a number of repetitions of data to be transmitted.

11. The method according to any of claims 1 to 10, wherein the downlink indication comprises a plurality of resource or interrupt fields, each resource or interrupt field being associated with a different UE.

12. The method of any one of claims 1 to 11, further comprising: before transmitting the downlink indication, the base station distributes interruption indication to at least one UE which is communicated with the base station, and sends the interruption indication to the at least one UE.

13. The method of claim 12, wherein the outage indication comprises an outage ID, and wherein an outage indication field of the UE using the overlapping resources comprises the outage ID.

14. The method of claim 11, wherein the indication of interruption comprises an uninterrupted indicator.

15. The method of claim 12, wherein the interruption indication is selected from a group consisting of at least one interruption ID and an interruption-free indicator, and wherein the interruption indication field of the UE using the overlapping resources comprises an interruption ID.

16. The method of claim 12, wherein each interrupt ID is assigned to a UE using overlapping resources.

17. The method according to any of claims 1 to 16, wherein each resource indication field is used for a UE transmitting a URLLC/MTC channel.

18. The method of any one of claims 1 to 17, wherein each outage indication field is used for one or more UEs transmitting an eMBB channel.

19. The method of claim 1, further comprising: an existing resource allocation that overlaps with the allocated uplink resource is identified at the base station.

20. A method of uplink data transmission from a user equipment, UE, to a base station in a cellular wireless network, the method being performed by the UE, characterized in that the method comprises:

receiving, at the UE, a downlink indication, the downlink indication comprising:

21. The method of claim 20, wherein the resource indication field further comprises an indication of the allocated uplink resource.

22. The method of claim 20 or 21, further comprising: in a configuration phase, receiving an indication of at least one scheduling request resource available for the UE to transmit a scheduling request, each scheduling request resource having a corresponding resource index, and/or an indication of at least one uplink resource allocated to the UE for data transmission.

23. The method of claim 22, wherein each scheduling request resource comprises a unique combination of time, frequency, and sequence resources.

24. The method according to claim 22 or 23, characterized in that at least one allocated scheduling request resource is also allocated to more UEs communicating with the base station.

25. The method according to claim 22 or 23, characterized in that at least one allocated scheduling request resource is allocated only to the UE.

26. The method of claim 21, wherein the indication of the allocated uplink resources comprises an indication of an offset before the UE starts uplink data transmission using the allocated resources for data transmission.

27. The method of claim 21, wherein the indication of the allocated uplink resources comprises an indication of a number of repetitions of data to be transmitted.

28. The method of claim 21, wherein the downlink indication comprises a plurality of downlink indication fields, each downlink indication field being associated with a different UE and comprising an indication of allocated resources and an indication of the UE to discontinue transmission.

29. The method of any one of claims 20 to 28, further comprising: receiving an indication of outage from the base station.

30. The method of claim 29, wherein the outage indication comprises an outage ID, and wherein an outage indication field for UEs using overlapping resources comprises the outage ID.

31. The method of claim 29 or 30, wherein the indication of interruption comprises an uninterrupted indicator.

32. The method of claim 23, wherein the interruption indication is selected from a group consisting of at least one interruption ID and an interruption-free indicator, and wherein the interruption indication field of the UE using the overlapping resources comprises the interruption ID.

33. The method of claim 20, wherein the outage indication field comprises at least one outage ID assigned to UEs using overlapping resources.

34. The method of any of claims 20 to 33, the UE using overlapping resources being a UE transmitting an eMBB channel.

35. A method of uplink data transmission from a user equipment, UE, to a base station in a cellular wireless network, the method being performed by the UE, characterized in that the method comprises:

receiving an interruption indication from a base station over a wireless link, the interruption indication selected from a set comprising at least one interruption ID and an interruption free indicator;

if the interruption indication is an interruption ID, monitoring downlink indication transmission from the base station, and if the received downlink indication comprises the interruption ID, interrupting the uplink transmission during the resource period indicated by the downlink indication; and the number of the first and second groups,

and if the interruption indication is an interruption-free indicator, configuring the UE not to monitor the downlink indication.

36. A UE configured to perform the method of any of claims 20 to 35.

37. A method of uplink data transmission from a user equipment, UE, to a base station in a cellular wireless network, the method being performed by the base station, characterized in that the method comprises:

receiving a request from a UE at a base station to transmit data and allocating uplink resources for the transmission, wherein the allocated uplink resources overlap with resources used by other UEs;

38. The method of claim 37, wherein the resource indication field further comprises an indication of the allocated uplink resources.

39. The method according to claim 37 or 38, further comprising a configuration phase comprising: the base station allocates at least one scheduling request resource and/or at least one uplink resource for data transmission to the UE, wherein each scheduling request resource has a corresponding resource index.

40. The method of claim 39, further comprising transmitting an indication of scheduling request resources and/or uplink resources allocated to the UE from the base station to the UE.

41. The method according to claim 39 or 40, wherein each allocated scheduling request resource is allocated a scheduling request resource index, and wherein the indication of scheduling request resources comprises the scheduling request resource index.

42. The method of any of claims 39 to 41, wherein each scheduling request resource comprises a unique combination of time, frequency and sequence resources.

43. The method according to any of claims 39 to 42, wherein at least one allocated scheduling request resource is also allocated to more UEs communicating with the base station.

44. The method according to any of claims 39 to 42, wherein at least one allocated scheduling request resource is allocated only to said UE.

45. The method of claim 40, wherein the indication of the allocated uplink resources comprises an offset before the UE starts uplink data transmission using the allocated resources for data transmission.

46. The method of claim 40, wherein the indication of the allocated resources comprises a number of repetitions of data to be transmitted.

47. The method according to any of claims 37 to 46, wherein the downlink indication comprises a plurality of resource or interrupt fields, each resource or interrupt field being associated with a different UE.

48. The method of any one of claims 37 to 47, further comprising: before transmitting the downlink indication, the base station distributes interruption indication to at least one UE which is communicated with the base station, and sends the interruption indication to the at least one UE.

49. The method of claim 48, wherein the outage indication comprises an outage ID, and wherein an outage indication field for UEs using overlapping resources comprises the outage ID.

50. The method of claim 47, wherein the indication of interruption comprises an uninterrupted indicator.

51. The method of claim 48, wherein the interruption indication is selected from a group consisting of at least one interruption ID and no interruption indicator, and wherein the interruption indication field of the UE using overlapping resources comprises the interruption ID.

52. The method of claim 48, wherein each interruption ID is assigned to a UE using overlapping resources.

53. The method according to any of claims 37 to 52, wherein each resource indication field is used for UEs transmitting URLLC/MTC channels.

54. The method of any one of claims 37 to 53, wherein each outage indication field is used for one or more UEs transmitting an eMBB channel.

55. The method of claim 37, further comprising: an existing resource allocation that overlaps with the allocated uplink resource is identified at the base station.

56. A base station configured to perform the method of any of claims 37 to 55.