WO2020201388A1

WO2020201388A1 - Methods and apparatuses for uplink transmission preemption

Info

Publication number: WO2020201388A1
Application number: PCT/EP2020/059314
Authority: WO
Inventors: Alexey SHAPIN; Jonas FRÖBERG OLSSON; Ali Behravan; Yufei Blankenship; Mattias Andersson; David Sandberg
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2019-04-02
Filing date: 2020-04-01
Publication date: 2020-10-08

Abstract

Methods (2000) and devices (101, 103) for uplink transmission preemption. In one aspect, an uplink preemption message is generated (s220) and transmitted (s230) to a device, where the uplink preemption message is a Downlink Control Information (DCI) message that comprises an indicator for the device to refrain from transmitting on a resource.

Description

METHODS AND APPARATUSES FOR UPLINK TRANSMISSION PREEMPTION

TECHNICAL FIELD

[0001] Disclosed are embodiments related to preemption of transmissions using control signaling.

BACKGROUND

[0002] Ultra-reliable and low latency communication (URLLC) is one of the main use cases of 5G new radio (NR). URLLC can have strict requirements on transmission reliability and latency, sometimes as strict as 99.9999% reliability within 1 ms one-way latency. In NR Rel-15, several new features and enhancements were introduced to support these requirements. Power controls for release 15 UEs are specified in 3GPP TS 38.213, V15.0.0, clause 7.1.1. Rel- 16 may include further enhancements in URLLC system performance, as well as ensuring reliable and efficient coexistent of URLLC and other NR use cases. For instance, both enhanced mobile broadband (eMBB) and URLLC user equipment (UEs) may need to co-exist in the same cell.

SUMMARY

[0003] According to embodiments, a method is provided that comprises: generating an uplink preemption message; and transmitting the message to a first device, where the uplink preemption message is a Downlink Control Information (DCI) message that comprises an indicator for the first device to refrain from transmitting on a preempted resource. The first device may have been previously scheduled for uplink transmission on the preempted resource (e.g., a time-frequency resource). In certain aspects, the message is a DCI format 2 4 message transmitted on a control channel.

[0004] According to some embodiments, a method is provide that comprises: receiving an uplink preemption message, where the uplink preemption message is a DCI message that comprises an indicator to refrain from transmitting on a preempted resource; and in response to the uplink preemption message, refraining from transmitting on the preempted resource. Before receiving the uplink preemption message, the device receiving the message may have previously received authorization to transmit on the preempted resource. In certain aspects, the indicator is a pointer (e.g., a pointer to information regarding scheduled resources). Additionally, a device (e.g., a UE receiving the message) may identify the preempted resource in a bitmap of time- frequency resources based at least in part on the pointer.

[0005] According to some embodiments, apparatuses (e.g., a network node or UE) are provided that are configured to perform one or more of the foregoing methods. For instance, a node may generate an uplink preemption message, and transmit the message to a first device, where the uplink preemption message is a DCI message that comprises an indicator for the first device to refrain from transmitting on a preempted resource. A UE may receive an uplink preemption message, where the uplink preemption message is a DCI message that comprises an indicator to refrain from transmitting on a preempted resource, and in response to the uplink preemption message, refraining from transmitting on the preempted resource.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments.

[0007] FIG. 1 illustrates a system according to embodiments.

[0008] FIGs. 2A, 2B, and 2C are flow charts illustrating processes according to embodiments.

[0009] FIG. 3 A is a schematic block diagram illustrating a telecommunication network connected via an intermediate network to a host computer.

[0010] FIG. 3B is a schematic block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection.

[0011] FIG. 3C is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment.

[0012] FIG. 3D is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment.

[0013] FIG. 3E is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment.

[0014] FIG. 3F is a flowchart depicting embodiments of a method in a communications system including a host computer, a base station and a user equipment.

[0015] FIG. 4 illustrates a configuration according to some embodiments.

[0016] FIG. 5A is a schematic drawing illustrating an example of a UE.

[0017] FIG. 5B is a schematic drawing illustrating an example of a UE.

[0018] FIG. 6A is a schematic drawing illustrating an example of a network node.

[0019] FIG. 6B is a schematic drawing illustrating an example of a network node.

DETAILED DESCRIPTION

[0020] According to embodiments, two approaches can be used to support

multiplexing/prioritization of UE’s within a cell. This can include a combination of the two approaches.

[0021] A first approach is based on power control to increase the power of at least one

UE (e.g., a URLLC UE) to make it more resilient to interference from other users, such as one or more eMBB users. Power controls for release 15 UEs are specified in 3GPP TS 38.213,

V15.0.0, clause 7.1.1. An advantage to this approach is that it does not require any changes in the behavior of the preempted device (e.g., an eMBB UE). Thus, it can work with Release 15 UEs. To guarantee the performance of the URLLC UE even while being interfered with by eMBB traffic, the URLLC UE’s transmit power spectral density (PSD) may need to be increased significantly. However, and for example, UEs not in the close vicinity of a network node (e.g., base station) may not have the power budget for such an increase and will therefore experience much lower Signal to Interference and Noise Ratio (SINR) than is required.

[0022] In a second approach, a technical solution is provided for notifying UEs in a cell about uplink (UL) preemption. According to embodiments a current group common DCI format can be used and/or a new format can be used. In this case, existing DCI messages regarding downlink preemption are distinguished from those with a preemption indication for UL.

Alternatively, and according to aspects of the disclosure, a new format is provided.

[0023] According to embodiments, the second approach is based on a preemption indicator being transmitted from a node (e.g., base station) to one or more interfering UEs (e.g., an eMBB UE). When a higher priority UE (e.g., a URLLC UE) is scheduled on time/frequency resources that are already scheduled to a lower priority UE (e.g., an eMBB UE), the node can transmit a preemption indicator to the lower priority EE using the DCI format. Upon reception of this indicator, the lower priority UE will avoid transmitting on a set of preconfigured resources.

[0024] An example of a use case for this scenario is when eMBB traffic is scheduled in a whole slot and all PRBs, and time sensitive URLLC data needs to be transmitted. Here, time sensitive may mean that reliability standards require instant access to the channel, and waiting until the next slot before transmission will introduce unacceptable delay. In NR, URLLC traffic maybe be scheduled on one or a few OFDM symbols and with a significantly shorter time from the uplink grant to when the uplink transmission takes place. This means that eMBB users may already have been scheduled on all available time/frequency resources. With a preemption indicator, the node (e.g., gNB) can choose to preempt the eMBB traffic and hence reduce the interference to the URLLC UE.

[0025] While priority in terms of use-case or service type (e.g., URLLC vs. eMBB) are used as examples, priority may be determined by a node based on other requirements or features. Additionally, priority or preemption requirements may be signaled to the node from other network elements, for instance, as illustrated with respect to FIGs. 3 A-3F.

[0026] According to some embodiments (e.g., in a node), a method comprises generating an uplink preemption message, wherein the uplink preemption message comprises an indicator to refrain from transmitting on a resource (e.g., time/frequency resource). The method further comprises transmitting the message. For instance, an uplink preemption message may be sent from a node to a UE on a control channel. According to some embodiments (e.g., in a UE), a method comprises receiving an uplink preemption message, wherein the uplink preemption message comprises an indicator to refrain from transmitting on a resource, and in in response to said uplink preemption message, refraining from transmitting on the resource. According to some embodiments (e.g., in a node), a method comprises generating a preemption message, wherein the preemption message indicates one or more of uplink and downlink preemption. The method further comprises transmitting the message.

[0027] Referring now to FIG. 1, a communication system 1000 is shown according to some embodiments. The system may, for instance, implement 5G new radio (NR) and include a first node 103, a second node 105, a first UE 101, and a second UE 102. In some embodiments, the first UE 101 is an eMBB device and the second UE 102 URLLC device, where each is in communication with first node 103. The nodes may be, for instance, base stations, such as NBs, eNBs, gNBs or other types of wireless access points.

[0028] FIG. 2A is a flowchart illustrating a process 2000 according to some

embodiments. The process may begin with step s220. The process may be performed, for instance by a node 103.

[0029] Step s220 comprises generating an uplink preemption message. According to embodiments, the uplink preemption message is a Downlink Control Information, DCI, message that comprises an indicator for a device to refrain from transmitting on a resource, such as a time-frequency resource. The message may be, for example a DCI message having a 2 1 or 2 4 format according to embodiments. Step s230 comprises transmitting the message. According to some embodiments, the message may be sent over a control channel from node 103 to UE 101. This may be after UE 101 was already authorized to transmit on the now-preempted resource, for instance, in step s210. For instance, UE 101 may have been previously scheduled for uplink transmissions on a given resource; however, such transmissions may be preempted for a second UE 102. For example, UE 102 may have a higher priority than UE 101.

[0030] In some embodiments, the indicator may be a pointer. The indicator can correspond to a resource bitmap for the UE (e.g., UE 101), where the bitmap describes a set of time-frequency resources. If there is overlap between the indicated resources and previously scheduled resources, those resources will be preempted.

[0031] In some embodiments, the generating or transmitting the uplink preemption message comprises using an RNTI, and in some cases, the RNTI indicates that the message carries information about uplink preemption. In some embodiments, the RNTI is an uplink cancellation indication RNTI. In some embodiments, process 2000 may include sending a configuration message for the first device to monitor the Physical Downlink Control Channel (PDCCH) for an uplink cancelation indication RNTI.

[0032] According to some embodiments, before step s220, a node (e.g., node 103) transmits a Radio Resource Control (RRC) configuration to the first device, where the configuration indicates a message position for the indicator to refrain from transmitting on the preempted resource.

[0033] In some embodiments, the process 2000 may be based on a determination that a second device is scheduled for transmission on the resource. With the first device preempted, the node may receive traffic from the second device on the preempted resource or transmit to the second device on the preempted resource. In some embodiments, the second device may have a higher priority than the first device. For instance, the second device may be a URLLC device.

[0034] FIG. 2B is a flowchart illustrating a process 2400 according to some

embodiments. The process may begin with step s260. The process may be performed, for instance by a UE 101 or 102.

[0035] Step s260 comprises receiving an uplink preemption message. According to embodiments, the uplink preemption message is a Downlink Control Information, DCI, message that comprises an indicator to refrain from transmitting on a resource, such as a time-frequency resource. The message may be, for example a DCI message having a 2 1 or 2 4 format according to embodiments. Step s270 comprises, in response to the uplink preemption message, refraining from transmitting on the resource. According to some embodiments, before step 260, the device receiving the message (e.g., UE 101) was previously authorized (s250) to transmit on the now-preempted resource.

[0036] According to some embodiments, process 2400 includes an intermediate step s265, in which the device determines one or more preempted resources indicated by the message. As described herein, and in accordance with certain embodiments, this could be accomplished, for instance, based on one or more of use of a pointer, determination of future slots or symbols based on offsets and/or periodicity, and use of prior signaling from the network.

[0037] In some embodiments, the indicator may be a pointer. The device (e.g., UE 101) may identify the preempted resource in a bitmap of time-frequency resources based at least in part on the pointer.

[0038] In some embodiments, the device (e.g., UE 101) performs a blind decode of at least a portion of the message and determines that the decoding was successful, which indicates that the message relates to uplink preemption. This could be, for instance, based on one or more of a Radio Network Temporary Identifier, RNTI, and check-sum. The RNTI may be, for example, an uplink cancellation indication RNTI. Additionally, and in some instance, the size of the message can indicate that the message relates to uplink preemption.

[0039] FIG. 2C is a flowchart illustrating a process 2750 according to some

embodiments. The process may begin with step s280. The process may be performed, for instance, by a node 103. Step s280 comprises a node (e.g., node 103) generating a preemption message, wherein the preemption message indicates one or more of uplink and downlink preemption. Step s290 comprises transmitting the message. For instance, the message may comprise a first plurality of bits relating to downlink preemption and a second plurality of bits relating to uplink preemption.

[0040] Some example of interactions between network elements, such as between one or more of UE 101, UE 102, node 103, and node 105, as well as structures of communication system 1000, are illustrated with respect to FIGs. 3A-3F.

[0041] According to embodiments, reuse of existing formats and/or a new DCI format may be used. Such embodiments may describe one or more uplink (or downlink) preemption messages used with respect to the processes of FIGs. 2A, 2B, and 2C.

[0042] In some embodiments, existing formats may be used. For instance, the existing

DCI format may be used to communicate downlink and/or uplink preemption. In the current specifications there are several DCI formats 2_X that are dedicated for group signaling.

According to some embodiments, a suitable format for reuse is DCI 2 1, which is dedicated for preemption indication in the downlink (DL). It is scrambled by an interruption RNTI (INT- RNTI) and the format size is configurable and can be 14 bits * N, where N is number of carriers for which the DCI is signaled for. Disclosed embodiments describe some methods of distinguishing between DCI 2 1 for downlink preemption indication (PI) and uplink preemption indication.

[0043] In one embodiment, the DCI 2 1 carries information about UL preemption if a new RNTI (e.g. INT-UL-RNTI) is used for scrambling of DCI format 2 1. A successful decode with the uplink cancellation indication RNTI can indicate to the UE that the preemption relates to the uplink.

[0044] In one embodiment, the DCI 2_1 size is configured as 14*N +14*M bits, where N is number of DL carriers for which the DCI is signaled for and N is number of UL carriers the DCI is signaled for. In this embodiment, one part of size 14*N bits carries information about DL preemption and another part 14*M bits carries information about UL preemption.

[0045] According to embodiments, a starting position of bits for UL preemption signaling can be configured RRC. An example of an RRC configuration 4000 is provided in FIG. 4, which describes, for example, RNTI values, a time-frequency set, payload size, interruption configurations for the serving cell, and identifiers. As shown in FIG. 4, the position in the DCI of preemption information can be signaled. According to some embodiments, RRC signaling may be provided, for instance, from node 103 to UE 101. This may occur, for instance, before one or more steps of process 2000 shown in FIG. 2 A or process 2400 shown in FIG. 2B.

[0046] In one embodiment, the UE can be configured with more than one PDCCH monitoring occasion for DCI format 2 1 per slot or within a given periodicity. If the UE is configured with more than one PDCCH monitoring occasion for DCI format 2 1, the first occasion within the slot or within a given periodicity is for DL preemption indication and other occasions are for UL preemption. The embodiment is not limited to this order; thus, another ordered rule can be used, including UL preemption signaling first and DL preemption signaling second, etc.

[0047] In one embodiment for Time Division Duplexing (TDD), the contents of the DCI format 2 1 are reinterpreted based on whether the resources that are indicated are part of DL,

UL, or flexible orthogonal frequency-division multiplexing (OFDM) symbols. If they are downlink or flexible symbols and the UE is scheduled to receive DL transmission on these resources, the UE interprets it as a DL preemption indicator. If they are UL or flexible symbols, and the UE is scheduled to transmit UL transmission on these resources, the UE interprets it as an UL preemption indicator.

[0048] In one embodiment, the DCI format 2 1 is monitored in a first and second search space where the DCI format is interpreted as DL if detected in first (or second) search space while interpreted as UL if detected on second (or first). The search spaces may be associated with same or different CORESET. When defined for same CORESET, the search spaces may have different start symbols.

[0049] In Rel-15, DCI format 2 1 (e.g., for DL preemption) is monitored in common search space. In one embodiment, DCI format 2 1 is configured to be monitored in UE-specific search space, wherein a detected DCI format 2 1 on UE-specific search indicates to a UE that the bits shall be interpreted as UL preemption.

[0050] In further other embodiments, DL and UL preemption is distinguished by search space candidates. For example, for an even number n of search space candidates for DCI format 2 1 for aggregation level L, then the first n/2 of the candidates are associated with DL while the last n/2 of the candidates are associated with UL. In such embodiment, Rel-15 UEs are configured with n/2 search space candidates while Rel-16 UEs are configured with n search space candidates for aggregation level L.

[0051] In a further embodiment, a search space serving DCI format 2 1 is configured for

UL preemption DCI, wherein when more than 1 monitoring occasion is specified within a slot the corresponding preemption DCI format is for UL preemption and when no more than 1 monitoring occasion within a slot is specified, the corresponding preemption DCI format is for DL preemption. In some examples the search space serving DCI format 2 1 is configured by a configuration parameter which has a plurality of bits. In some examples when a bit is set to‘ 1’ to identify the first OFDM symbol(s) of a control resource set within a slot, having multiple bits of value‘ 1’ indicates multiple monitoring occasions within a slot. In some examples the search space configuration parameter is a monitor ingSymbolsWithinSlot IE. This can be (re) used to differentiate the UL preemption DCI format from DL preemption DCI format. That is, if monitoringSymbolsWithinSlot of the search space specifies more than 1 monitoring occasions within a slot, the corresponding preemption DCI format is for UL preemption. Otherwise, the corresponding preemption DCI format is for DL preemption. This would be where

monitoringSymbolsWithinSlot of the search space does not specify more than 1 monitoring occasions within a slot.

[0052] In a further embodiment, a search space serving DCI format 2 1 is configured for

UL preemption DCI when a number of PDCCH candidates per aggregation level is specifically defined for DCI format 2 1. For example, a separate parameter, such as nrofCandidates-UL-PI , is provided to replace an existing the existing parameter nrofCandidates. When the number of PDCCH candidates per aggregation level (e.g. nrofCandidates) is not specifically defined for DCI format 2 1, DCI format 2 1 may be used as DL preemption DCI.

[0053] According to some embodiments, a new DCI format may be used for uplink preemption. Although“2 4” is used as an example identity, other DCI format identities/naming conventions may be used for a new DCI format for uplink preemption.

[0054] In one embodiment, a new DCI format within the formats dedicated for group signaling, for example 2 4, is used. In certain aspects, the new DCI format is for group common communication preemption. According to embodiments, a common format with a configurable payload is used.

[0055] In one embodiment, if a search space set is a common search space (CSS) set, an indication by field dci-Format2-4 to monitor PDCCH candidates for DCI format 2 4 is provided.

[0056] In one embodiment, a UE (e.g., UE 101) may be provided or otherwise configured with a new RNTI, int-UL-RNTI, for monitoring PDCCH conveying DCI format 2 1 or 2 4. A successful decode with an uplink cancellation indication RNTI can indicate to the UE that the preemption relates to the uplink.

[0057] In one embodiment, the UE can be configured with more than one PDCCH monitoring occasion for DCI format 2 4.

[0058] In one embodiment, DCI format 2 1 is reused for both UL and DL preemption, but with an extra bit indicating if the DCI is for DL or UL preemption.

[0059] In a further embodiment, a search space serving DCI format 2 4 is configured for

UL preemption DCI, wherein more than 1 monitoring occasion is specified within a slot. In some examples a configuration parameter comprising a plurality of bits, wherein a bit is set to ‘ 1’ to identify the first OFDM symbol(s) of a control resource set within a slot and having multiple bits of value‘ 1’ indicates multiple monitoring occasions within a slot. In some examples the search space configuration parameter is a monitoringSymbolsWithinSlot IE. When configuring the search space for the UL preemption DCI format, monitoringSymbolsWithinSlot of the search space specifies more than 1 monitoring occasions within a slot. This can be used to differentiate the UL preemption DCI format from DL preemption DCI format. That is, if monitoringSymbolsWithinSlot of the search space specifies more than 1 monitoring occasions within a slot, the corresponding preemption DCI format is for UL preemption. Otherwise, where monitoringSymbolsWithinSlot of the search space does not specify more than 1 monitoring occasions within a slot, the corresponding preemption DCI format is for DL preemption.

[0060] In a further embodiment, a search space serving DCI format 2 4 is configured for

UL preemption DCI, wherein a number of PDCCH candidates per aggregation level is specifically defined for DCI format 2 4. For example, a separate parameter (e.g.

nrofCandidates-UL-PI) is provided to replace an existing parameter, such as nrofCandidates.

[0061] Examples of uplink signaling content are provided below. This content may be, for instance, with respect to a new DCI format used for uplink preemption.

[0062] In one embodiment, the signaling of UL preemption/interruption includes a pointer to a future slot or symbol where the UL preemption starts. As another example, the signaling of UL preemption/interruption can include a pointer to a future slot or symbol where the UL preemption ends. As another example, the signaling of UL preemption/interruption can include a pointer to a future slot or symbol where the UL preemption starts and pointer to a future slot or symbol where the UL preemption ends. As another example, the signaling of UL preemption/interruption includes a pointer to a specific OFDM symbol where the UL preemption starts and there is no indicator where the preemption ends. The UE may then assume that the preemption continues until a specified time.

[0063] In some embodiments, the specified time is the end of the slot which contains the specific OFDM symbol. In another variation, the specified time is the end of the Physical Uplink Share Channel (PUSCH) transmission that is being preempted. In another version, the specified time is the end of the last PUSCH transmission in a set of repeated PUSCH transmissions, where the set of repeated PUSCH transmissions are either scheduled by the same DCI or is one period of an UL cell group (CG) transmission.

[0064] In some embodiments, regardless of the processing capability of the UE receiving the preemption indicator, the specific time TUL.PI where the UL preemption starts is provided without explicit signaling. In one example, TUL.PI provides a specific symbol that follows the PDCCH carrying the UL preemption DCI. The specific symbol is the next symbol with its cyclic prefix (CP) which starts TUL.PI after the end of reception of the last symbols of the PDCCH carrying the UL preemption DCI. The same TUL.PI is used for both normal and extended cyclic prefix. For instance, TUL.PI =T_proc,2 , where

the following parameter values:

• variable ch, i set to 0

• variable di,2 set to 0

• // is set to WDL, i.e., the subcarrier spacing of the downlink carrier where the PDCCH of UL PI DCI is transmitted.

• Ni corresponds to the Ni value of the UE processing capability 2;

[0065] In another example, TUL.PI additionally takes into account the non-uplink symbols as indicated by the TDD-UL-DL-ConfigurationCommon in the serving cell where the PDCCH is sent. That is, TUL.PI provides a specific uplink symbol that follows the PDCCH carrying the UL preemption DCI. The specific symbol is the next uplink symbol with its cyclic prefix (CP) which starts TUL.PI after the end of reception of the last symbols of the PDCCH carrying the UL preemption DCI. In this example, a symbol refers to an OFDM symbol for DL as well as UL when transform precoding is not enabled. When transform precoding is enabled for UL, the symbol is sometimes referred to as a DFT-s-OFDM symbol.

[0066] In one embodiment, the referenced symbols are future symbols with a start and end symbol determined by the UE based on the start or end of PDCCH comprising the UL preemption indicator and the monitoring periodicity P symbols of UL preemption indicator. For example, if the DCI was received on a PDCCH with start/end symbol n, then the start symbol of the referenced future symbols would be n + n₀^_set , where n₀^_set is a fixed value or semi-static value, and the end symbol of the referenced future symbols may be n + P + n₀^_{set .} In some embodiments, the future symbols are referenced using a bitmap where each bit references a group of consecutive symbols. This could be, for instance, part of step s265.

[0067] In one embodiment, the referenced symbols are in a reference numerology other than the numerology in which the UL preemption occurs. When symbols in the reference numerology are indicated as preempted, then a UE determines which symbols in its transmission numerology are subject for preemption based on its transmission numerology and the reference numerology.

[0068] In one embodiment, the signaling of UL preemption/interruption includes soft power control parameters.

[0069] In any of the embodiments and examples disclosed herein, the impact to preempted UE UL transmission may be adapted or preconfigured. For example, for the UE being preempted, all UL transmissions otherwise scheduled for transmission in the preempted time-frequency resources may be dropped. In other examples, for the UE being preempted, certain types of UL transmission otherwise scheduled for transmission in the preempted time- frequency resources are dropped, but other types are not dropped. For example, the not-dropped UL transmission may include: PUCCH carrying hybrid automated request acknowledgment (HARQ-ACK) and/or SR (scheduling request) and the dropped UL transmission may include: PUSCH, PUCCH carrying CSI (channel state information) only, and SRS (sounding reference signal).

[0070] A computer program may comprise instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any one of embodiments herein. For instance, a processor may perform any of the methods described with respect to FIGs. 2A, 2B, and 2C. In some embodiments, a carrier may comprise the computer program, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0071] Referring now to FIGs. 5A and 5B, two different examples are depicted, respectively, comprising the arrangement of a UE, such as UE 101. Although UE 101 is used in these examples, similar descriptions and arrangements may apply to UE 102.

[0072] In some embodiments, the UE 101 may comprise the arrangement depicted in

FIG. 5 A. The embodiments of UE 101 may be implemented through one or more processors, such as a first processor 501 in the UE 101 depicted in FIG. 5 A, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the UE 101. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the UE 101.

[0073] The UE 101 may further comprise a first memory 503 comprising one or more memory units. The memory 503 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the UE 101.

[0074] In some embodiments, the UE 101 may receive information from, for instance, the first network node 103 and/or the second network node 105, through a first receiving port 504. This may include, for instance, information communicated as described with respect to FIGs. 2A, 2B, and 2C. In some embodiments, the first receiving port 504 may be, for example, connected to one or more antennas in UE 101. In other embodiments, the UE 101 may receive information from another structure in the communications system 1000 through the first receiving port 504. Since the first receiving port 504 may be in communication with the first processor 501, the first receiving port 504 may then send the received information to the first processor 501. The first receiving port 504 may also be configured to receive other information.

[0075] The first processor 501 in the UE 101 may be further configured to transmit or send information to, for example, first network node 103 and/or the second network node 105 and, or another structure in the communications system 1000, through a first sending port 505, which may be in communication with the first processor 510, and the first memory 503.

[0076] The UE 101 may comprise a determining unit 515, an obtaining unit 518, a providing unit 528, etc. Those skilled in the art will also appreciate that the determining unit 515, obtaining unit 518, a providing unit 528 described above may refer to a combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the first processor 501, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC). Also, in some embodiments, the different units 515-528 described above may be implemented as one or more applications running on one or more processors such as the first processor 501.

[0077] Thus, the methods according to the embodiments described herein for the UE 101 may be respectively implemented by means of a first computer program 510 product, comprising instructions, i.e., software code portions, which, when executed on at least one first processor 501, cause the at least one first processor 501 to carry out the actions described herein, as performed by the UE 101. The first computer program 510 product may be stored on a first computer-readable storage medium 508. The first computer-readable storage medium 609, having stored thereon the first computer program 510, may comprise instructions which, when executed on at least one first processor 501, cause the at least one first processor 501 to carry out the actions described herein, as performed by the UE 101. In some embodiments, the first computer-readable storage medium 508 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the first computer program 510 product may be stored on a carrier containing the first computer program 510 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the first computer-readable storage medium 508, as described above.

[0078] The UE 101 may comprise a communication interface configured to facilitate communications between the UE 101 and other nodes or devices, e.g., the first network node 103 and/or the second network node 105 and/, or another structure. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard. For instance, a UE 101 may receive messages indicating uplink preemption via one or more communication interfaces and the related structures.

[0079] In other embodiments, the UE 101 may comprise the arrangement depicted in

FIG. 5B. The UE 101 may comprise a first processing circuitry 511, e.g., one or more processors such as the first processor 510, in the UE 101 and the first memory 503. The UE 101 may also comprise a first radio circuitry 513, which may comprise, for instance, the first receiving port 504 and the first sending port 505. The first processing circuitry 511 may be configured to, or operable to, perform the method actions according to FIG. 2B, in a similar manner as that described in relation to FIG. 5 A. The first radio circuitry 513 may be configured to set up and maintain at least a wireless connection with the node 103. Circuitry may be understood herein as a hardware component.

[0080] Hence, embodiments herein also relate to the UE 101 operative to operate in the communications system 1000. The UE 101 may comprise the first processing circuitry 511 and the first memory 503, said first memory 503 containing instructions executable by said first processing circuitry 511, whereby the UE 101 is further operative to perform the actions described herein in relation to the UE 101, e.g., in FIG. 2B.

[0081] FIGs. 6A and FIG. 6B depict two different examples, respectively, of an arrangement that the first network node 103 may comprise. Although node 103 is used in these examples, similar descriptions and arrangements may apply to node 105.

[0082] In some embodiments, the first network node 103 may comprise arrangement depicted in FIG. 6A. For instance, the first network node 103 may be implemented through one or more processors, such as a second processor 601 in the first network node 103 depicted in FIG. 6A, together with computer program code for performing the functions and actions of the embodiments herein. A processor, as used herein, may be understood to be a hardware component. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first network node 103. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first network node 103.

[0083] The first network node 103 may further comprise a second memory 603 comprising one or more memory units. The second memory 603 is arranged to be used to store obtained information, store data, configurations, schedulings, and applications etc. to perform the methods herein when being executed in the first network node 103.

[0084] In some embodiments, the first network node 103 may receive information from, e.g., the UE 101 and/or the second network node 105, through a second receiving port 604. In some embodiments, the second receiving port 604 may be, for example, connected to one or more antennas in first network node 103. In other embodiments, the first network node 103 may receive information from another structure in the communications system 1000 through the second receiving port 604. Since the second receiving port 604 may be in communication with the second processor 601, the second receiving port 604 may then send the received information to the second processor 601. The second receiving port 604 may also be configured to receive other information.

[0085] The second processor 601 in the first network node 103 may be further configured to transmit or send information to, for instance, the UE 101 and/or the second network node 105, or another structure in the communications system 1000, through a second sending port 605, which may be in communication with the second processor 601, and the second memory 603.

[0086] The first network node 103 may comprise a determining unit 613, a creating unit

615, a providing unit 618, etc. Those skilled in the art will also appreciate that the determining unit 613, the creating unit 615, the providing unit 618 described above may refer to a

combination of analog and digital circuits, and/or one or more processors configured with software and/or firmware, e.g., stored in memory, that, when executed by the one or more processors such as the second processor 601, perform as described above. One or more of these processors, as well as the other digital hardware, may be included in a single Application- Specific Integrated Circuit (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a System-on-a-Chip (SoC). Also, in some embodiments, the different units 613-618 described above may be implemented as one or more applications running on one or more processors such as the second processor 601.

[0087] Thus, the methods according to the embodiments described herein for the first network node 103 may be respectively implemented by means of a second computer program 610 product, comprising instructions, i.e., software code portions, which, when executed on at least one second processor 601, cause the at least one second processor 601 to carry out the actions described herein, as performed by the first network node 103. The second computer program 610 product may be stored on a second computer-readable storage medium 608. The computer-readable storage medium 608, having stored thereon the second computer program 610, may comprise instructions which, when executed on at least one second processor 601, cause the at least one second processor 601 to carry out the actions described herein, as performed by the network node 103 or 105. In some embodiments, the computer-readable storage medium 610 may be a non-transitory computer-readable storage medium, such as a CD ROM disc, or a memory stick. In other embodiments, the second computer program 610 product may be stored on a carrier containing the second computer program 610 just described, wherein the carrier is one of an electronic signal, optical signal, radio signal, or the second computer- readable storage medium 608, as described above.

[0088] The first network node 103 may comprise a communication interface configured to facilitate communications between the first network node 103 and other nodes or devices, e.g., the UE 101 and/or the second network node 105, or another structure. The interface may, for example, include a transceiver configured to transmit and receive radio signals over an air interface in accordance with a suitable standard. For instance, a node 103 may send messages indicating uplink preemption via one or more communication interfaces and the related structures.

[0089] In other embodiments, the first network node 103 may comprise the following arrangement depicted in FIG. 6B. The first network node 103 may comprise a second processing circuitry 611, e.g., one or more processors such as the second processor 601, in the first network node 103 and the second memory 603. The first network node 103 may also comprise a second radio circuitry 620, which may comprise e.g., the second receiving port 604 and the second sending port 605. The second processing circuitry 611 may be configured to, or operable to, perform the method actions according to FIG. 2A or 2C in a similar manner as that described in relation to FIG. 6A. The second radio circuitry 620 may be configured to set up and maintain at least a wireless connection with the second network node 105 and/or a UE (e.g., UE 101 and 102). Accordingly, a node as depicted in FIG. 6B may be configured to generate a message indicating uplink preemption, and transmit that message to one or more UEs. Circuitry may be understood herein as a hardware component.

[0090] Hence, embodiments herein also relate to the first network node 103 operative to operate in the communications system 1000. The first network node 103 may comprise the second processing circuitry 611 and the second memory 603, said second memory 603 containing instructions executable by said second processing circuitry 611, whereby the first network node 103 is further operative to perform the actions described herein in relation to the first network node 103, e.g., in FIG. 2A or 2C.

[0091] A telecommunication network connected via an intermediate network to a host computer is provided in accordance with some embodiments.

[0092] With reference to FIG. 3 A, in accordance with an embodiment, a communication system includes telecommunication network 3210 such as the communications system 1000, for example, a 3GPP-type cellular network, which comprises access network 3211, such as a radio access network, and core network 3214. Access network 3211 comprises a plurality of network nodes 103, 105. For example, base stations 3212a, 3212b, 3212c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 3213a, 3213b, 3213c. Each base station 3212a, 3212b, 3212c is connectable to core network 3214 over a wired or wireless connection 3215. A plurality of user equipments, such as the UE 101 or 102 may be comprised in the communications system 1000. In FIG. 3 A, a first UE 3291 located in coverage area 3213c is configured to wirelessly connect to, or be paged by, the corresponding base station 3212c. A second UE 3292 in coverage area 3213a is wirelessly connectable to the corresponding base station 3212a. According to embodiments, uplink transmissions from one or more of 3291 or 3292 may be preempted, for instance, based on signaling from one or more of the base stations 3212a, 3212b, 3212c.

[0093] While a plurality of UEs 3291, 3292 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 3212. Any of the UEs 3291, 3292 may be considered examples of the UE 101 or 102.

[0094] Telecommunication network 3210 is itself connected to host computer 3230, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server, or as processing resources in a server farm. Host computer 3230 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 3221 and 3222 between telecommunication network 3210 and host computer 3230 may extend directly from core network 3214 to host computer 3230 or may go via an optional intermediate network 3220. Intermediate network 3220 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 3220, if any, may be a backbone network or the Internet; in particular, intermediate network 3220 may comprise two or more sub-networks (not shown).

[0095] The communication system of FIG. 3 A as a whole enables connectivity between the connected UEs 3291, 3292 and host computer 3230. The connectivity may be described as an Over-The-Top (OTT) connection 3250. Host computer 3230 and the connected UEs 3291, 3292 are configured to communicate data and/or signaling via OTT connection 3250, using access network 3211, core network 3214, any intermediate network 3220 and possible further infrastructure (not shown) as intermediaries. OTT connection 3250 may be transparent in the sense that the participating communication devices through which OTT connection 3250 passes are unaware of routing of uplink and downlink communications. For example, base station 3212 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 3230 to be forwarded (e.g., handed over) to a connected UE 3291. Similarly, base station 3212 need not be aware of the future routing of an outgoing uplink communication originating from the UE 3291 towards the host computer 3230.

[0096] In relation to FIGs. 3B-3F, which are described next, it may be understood that the base station may be considered an example of the first network node 103.

[0097] FIG. 3B illustrates an example of host computer communicating via a first network node 103 with a UE 101 over a partially wireless connection in accordance with some embodiments

[0098] The UE 101 and the first network node 103, e.g., a base station and host computer discussed in the preceding paragraphs will now be described with reference to FIG. 3B. In communication system 3330, such as the communications system 1000, host computer 3310 comprises hardware 3315 including communication interface 3316 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 3300. Host computer 3310 further comprises processing circuitry 3318, which may have storage and/or processing capabilities. In particular, processing circuitry 3318 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 3310 further comprises software 3311, which is stored in or accessible by host computer 3310 and executable by processing circuitry 3318. Software 3311 includes host application 3312. Host application 3312 may be operable to provide a service to a remote user, such as UE 3330 connecting via OTT connection 3350 terminating at UE 3330 and host computer 3310. In providing the service to the remote user, host application 3312 may provide user data which is transmitted using OTT connection 3350.

[0099] Communication system 3300 further includes the first network node 103 exemplified in FIG. 3B as a base station 3320 provided in a telecommunication system and comprising hardware 3325 enabling it to communicate with host computer 3310 and with UE 3330. Hardware 3325 may include communication interface 3326 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 3300, as well as radio interface 3327 for setting up and maintaining at least wireless connection 3370 with the UE 101, exemplified in FIG. 3B as a UE 3330 located in a coverage area served by base station 3320. Communication interface 3326 may be configured to facilitate connection 3360 to host computer 3310. Connection 3360 may be direct or it may pass through a core network (not shown in FIG. 3B) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 3325 of base station 3320 further includes processing circuitry 3328, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 3320 further has software 3321 stored internally or accessible via an external connection.

[0100] Communication system 3300 further includes the UE 3330 already referred to. Its hardware 3335 may include radio interface 3337 configured to set up and maintain wireless connection 3370 with a base station serving a coverage area in which UE 3330 is currently located. Hardware 3335 of UE 3330 further includes processing circuitry 3338, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 3330 further comprises software 3331, which is stored in or accessible by UE 3330 and executable by processing circuitry 3338. Software 3331 includes client application 3332. Client application 3332 may be operable to provide a service to a human or non-human user via UE 3330, with the support of host computer 3310. In host computer 3310, an executing host application 3312 may communicate with the executing client application 3332 via OTT connection 3350 terminating at UE 3330 and host computer 3310. In providing the service to the user, client application 3332 may receive request data from host application 3312 and provide user data in response to the request data. OTT connection 3350 may transfer both the request data and the user data. Client application 3332 may interact with the user to generate the user data that it provides.

[0101] It is noted that host computer 3310, base station 3320 and UE 3330 illustrated in

FIG. 3B may be similar or identical to host computer 3230, one of base stations 3212a, 3212b, 3212c and one of UEs 3291, 3292 of FIG. 3 A, respectively. This is to say, the inner workings of these entities may be as shown in FIG. 3B and independently, the surrounding network topology may be that of FIG. 3 A.

[0102] In FIG. 3B, OTT connection 3350 has been drawn abstractly to illustrate the communication between host computer 3310 and UE 3330 via base station 3320, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 3330 or from the service provider operating host computer 3310, or both. While OTT

connection 3350 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or

reconfiguration of the network).

[0103] Wireless connection 3370 between UE 3330 and base station 3320 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 3330 using OTT connection 3350, in which wireless connection 3370 forms the last segment. More precisely, the teachings of these embodiments may improve the spectrum efficiency, and latency, and thereby provide benefits such as reduced user waiting time, better responsiveness and extended battery lifetime. [0104] A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 3350 between host computer 3310 and UE 3330, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 3350 may be implemented in software 3311 and hardware 3315 of host computer 3310 or in software 3331 and hardware 3335 of UE 3330, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 3350 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 3311, 3331 may compute or estimate the monitored quantities. The

reconfiguring of OTT connection 3350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 3320, and it may be unknown or imperceptible to base station 3320. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 3310’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 3311 and 3331 causes messages to be transmitted, in particular empty or‘dummy’ messages, using OTT connection 3350 while it monitors propagation times, errors etc.

[0105] FIG. 3C illustrates an example of methods implemented in a communication system including a host computer, a base station and a user equipment. FIG. 3C is a flowchart illustrating a method implemented in a communication system. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIG. 3A and FIG. 3B. For simplicity of the present disclosure, only drawing references to FIG. 3C will be included in this section. In step 3410, the host computer provides user data. In substep 3411 (which may be optional) of step 3410, the host computer provides the user data by executing a host application. In step 3420, the host computer initiates a transmission carrying the user data to the UE. In step 3430 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 3440 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0106] FIG. 3D illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments. FIG. 3D is a flowchart illustrating a method implemented in a communication system. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIG. 3A and FIG. 3B. For simplicity of the present disclosure, only drawing references to FIG. 3D will be included in this section. In step 3510 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 3520, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 3530 (which may be optional), the UE receives the user data carried in the transmission.

[0107] FIG. 3E illustrates methods implemented in a communication system including a host computer, a base station and a user equipment. FIG. 3E is a flowchart illustrating a method implemented in a communication system. The communication system includes a host computer, a first network node 103 and a UE 101 which may be those described with reference to FIG. 3 A and FIG. 3B. For simplicity of the present disclosure, only drawing references to FIG. 3E will be included in this section. In step 3610 (which may be optional), the UE 101 receives input data provided by the host computer. Additionally or alternatively, in step 3620, the UE 101 provides user data. In substep 3621 (which may be optional) of step 3620, the UE provides the user data by executing a client application. In substep 3611 (which may be optional) of step 3610, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 3630 (which may be optional), transmission of the user data to the host computer. In step 3640 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0108] FIG. 3F illustrates methods implemented in a communication system including a host computer, a base station and a user equipment. FIG. 3F is a flowchart illustrating a method implemented in a communication system. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIG. 3 A and FIG. 3B. For simplicity of the present disclosure, only drawing references to FIG. 370 will be included in this section. In step 3710 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 3720 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 3730 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0109] Some embodiments may be summarized as follows:

[0110] A base station configured to communicate with a UE 101, the base station comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the first network node 103.

[0111] A communication system 1000 including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a UE 101, wherein the cellular network comprises a first network node 103 having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform one or more of the actions described herein as performed by the network node 103. The communication system may further include the first network node 103. The communication system may further include the UE 101, wherein the UE 101 is configured to communicate with the first network node 103. The communication system, wherein: the processing circuitry of the host computer is configured to execute a host

application, thereby providing the user data; and the UE 101 comprises processing circuitry configured to execute a client application associated with the host application.

[0112] A method implemented in a first network node 103, comprising one or more of the actions described herein as performed by the first network node 103.

[0113] A method implemented in a communication system 1000 including a host computer, a base station and a UE 101, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE 101 via a cellular network comprising the first network node 103, wherein the first network node 103 performs one or more of the actions described herein as performed by the first network node 103. The method may further comprise: at the first network node 103, transmitting the user data. The user data may be provided at the host computer by executing a host application, and the method may further comprise: at the UE 101, executing a client application associated with the host application.

[0114] A UE 101 configured to communicate with a first network node 103, the UE 101 comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the UE 101.

[0115] A communication system 1000 including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a UE 101, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform one or more of the actions described herein as performed by the UE 101. The communication system may further including the UE 101. The communication system 1000, wherein the cellular network further includes a first network node 103 configured to communicate with the UE 101.

[0116] The communication system 1000, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.

[0117] A method implemented in a UE 101, comprising one or more of the actions described herein as performed by the UE 101.

[0118] A method implemented in a communication system 1000 including a host computer, a first network node 103 and a UE 101, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE 101 via a cellular network comprising the base station, wherein the UE 101 performs one or more of the actions described herein as performed by the UE 101. The method may further comprise: at the UE 101, receiving the user data from the first network node 103.

[0119] A UE 101 configured to communicate with a first network node 103, the UE 101 comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the UE 101.

[0120] A communication system 1000 including a host computer comprising: a communication interface configured to receive user data originating from a transmission from a UE 101 to a first network node 103, wherein the UE 101 comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to: perform one or more of the actions described herein as performed by the UE 101. The communication system 1000 may further include the UE 101. The communication system 1000 may further include the first network node 103, wherein the first network node 103 comprises a radio interface configured to communicate with the UE 101 and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE 101 to the base station.

[0121] The communication system 1000, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

[0122] The communication system 1000, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

[0123] A method implemented in a UE 101, comprising one or more of the actions described herein as performed by the UE 101. The method may further comprise: providing user data; and forwarding the user data to a host computer via the transmission to the first network node 103.

[0124] A method implemented in a communication system 1000 including a host computer, a first network node 103 and a UE 101, the method comprising: at the host computer, receiving user data transmitted to the first network node 103from the UE 101, wherein the UE 101 performs one or more of the actions described herein as performed by the UE 101. The method may further comprise: at the UE 101, providing the user data to the first network node 103. The method may further comprise: at the UE 101, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application. The method may further comprise: at the UE 101, executing a client application; and at the UE 101, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

[0125] A first network node 103 configured to communicate with a UE 101, the first network node 103 comprising a radio interface and processing circuitry configured to perform one or more of the actions described herein as performed by the network node 103.

[0126] A communication system 1000 including a host computer comprising a communication interface configured to receive user data originating from a transmission from a UE 101 to a base station, wherein the first network node 103 comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform one or more of the actions described herein as performed by the first network node 103. The communication system 1000 may further include the first network node 103. The communication system 1000 may further include the UE 101, wherein the UE 101 is configured to communicate with the first network node 103.

[0127] The communication system 1000 wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE 101 is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

[0128] A method implemented in a communication system including a host computer, a first network node 103 and a UE 101, the method comprising: at the host computer, receiving, from the first network node 103, user data originating from a transmission which the base station has received from the UE 101, wherein the UE 101 performs one or more of the actions described herein as performed by the UE 101. The method may further comprise: at the first network node 103, receiving the user data from the UE 101. The method may further comprise: at the first network node 103, initiating a transmission of the received user data to the host computer. [0129] Summary of Various Examples:

[0130] la. A method, comprising:

[0131] generating an uplink preemption message; and

[0132] transmitting said message,

[0133] wherein said uplink preemption message comprises an indicator to refrain from transmitting on a resource.

[0134] lb. The method of example la, wherein said message is a DCI (e.g., DCI format

2 1) message transmitted on a control channel.

[0135] lc. The method of example, la or lb, wherein said uplink preemption message comprises information identifying a set of one or more preempted resources.

[0136] Id. The method of any of example lc, wherein said preempted resources are time-frequency resources.

[0137] le. The method of any of the preceding examples,

[0138] wherein said generating or transmitting the uplink preemption message comprises using an RNTI (e.g., INT-UL-RNTI), and

[0139] wherein use of said RNTI indicates that said message carries information about uplink preemption.

[0140] If. The method of any of the preceding examples, wherein said message comprises a first plurality of bits relating to downlink preemption and a second plurality of bits relating to uplink preemption.

[0141] lg. The method of example If, wherein an RRC configuration indicates the staring position in said message of said second plurality of bits.

[0142] lh. The method of example If or lg,

[0143] wherein the message is a DCI 2_1 message having a size configured as 14*N

+14*M bits,

[0144] where N is number of downlink carriers for which the DCI is signaled for and M is number of uplink carriers the DCI is signaled for, and

[0145] wherein one part of size 14*N bits carries information about downlink preemption and another part 14*M bits carries information about uplink preemption.

[0146] li. The method of any of the preceding examples, wherein said transmitting is to a first UE,

[0147] further comprising:

[0148] receiving traffic from a second UE on said resource; or

[0149] transmitting traffic to a second UE on said resource.

[0150] lj. The method of example li, wherein said first UE is an enhanced mobile broadband (eMBB) device and said second UE is an ultra-reliable low latency communication (URLLC) device.

[0151] 2a. A method, comprising:

[0152] generating a preemption message; and

[0153] transmitting said message,

[0154] wherein said preemption message indicates one or more of uplink and downlink preemption.

[0155] 2b. The method example 2a,

[0156] wherein a UE is configured with more than one PDCCH monitoring occasion for

DCI format 2 1 per slot or within a given periodicity, and

[0157] wherein said message is generated such that the first occasion within slot or within a given periodicity is for downlink preemption indication and other occasions are for uplink preemption.

[0158] 2c. The method of example 2a,

[0159] wherein a UE is configured with more than one PDCCH monitoring occasion for

DCI format 2 1 per slot or within a given periodicity, and

[0160] wherein said message is generated such that the first occasion within slot or within a given periodicity is for uplink preemption indication and other occasions are for downlink preemption.

[0161] 2d. The method of example 2a, wherein:

[0162] for content of a DCI (e.g., format 2 1) message are indicated as part of downlink or flexible symbols, and a UE is scheduled to receive downlink transmission on these resources, the UE interprets a preemption indicator as a downlink preemption indicator

[0163] 2e. The method of 2a or 2d, wherein:

[0164] for content of a DCI (e.g., format 2 1) indicated as part of uplink or flexible symbols, and a UE is scheduled to transmit uplink transmission on these resources, the UE interprets a preemption indicator as an uplink preemption indicator.

[0165] 2f. The method of examples 2d or 2e, wherein one or more node or UE is configured for TDD signaling.

[0166] 2g. The method of example 2a, wherein a preemption indicator of said message is interpreted as a downlink indicator if detected in a first search space by a UE and interpreted as an uplink indicator if detected in a second search space.

[0167] 2f. The method of example 2f, wherein the search spaces may be associated with same or different control resource set, CORESET, and when defined for same CORESET, the search spaces have different start symbols.

[0168] 2g. The method of example 2a, wherein DCI format 2 1 messages monitored in common search space indicate downlink preemption and DCI format 2 1 messages monitored in UE-specific search space indicate uplink preemption.

[0169] 2h. The method of example 2a, wherein downlink and uplink preemption is distinguished by search space candidates.

[0170] 2i. The method of example 2h, where for even number n of search space candidates for DCI format 2 1 for aggregation level L, the first n/2 of the candidates are associated with downlink and thee last n/2 of the candidates are associated with uplink.

[0171] 2j. The method of example 2i, wherein Rel-15 UEs are configured with n/2 search space candidates and Rel-X UEs are configured with n search space candidates for aggregation level L.

[0172] 2k. The method of example 2a, wherein a search space serving DCI format 2 1 is configured for UL preemption DCI, wherein when more than 1 monitoring occasion is specified within a slot the corresponding preemption DCI format is for UL preemption and when no more than 1 monitoring occasion within a slot is specified, the corresponding preemption DCI format is for DL preemption.

[0173] 21. The method of example 2k, wherein the search space serving DCI format 2 1 is configured by a configuration parameter which has a plurality of bits, wherein, when a bit is set to‘ 1’ to identify the first OFDM symbol(s) of a control resource set within a slot and having multiple bits of value‘ 1’ indicates multiple monitoring occasions within a slot. [0174] 2m. The method of examples 21 or 21, wherein the search space configuration parameter is a monitoringSymbolsWithinSlot IE, wherein the monitoringSymbolsWithinSlot IE is used to differentiate the UL preemption DCI format from DL preemption DCI format:

[0175] if monitoringSymbolsWithinSlot IE specifies more than 1 monitoring occasions within a slot, the corresponding preemption DCI format is for UL preemption; and

[0176] if monitoringSymbolsWithinSlot IE does not specify more than 1 monitoring occasions within the slot, the corresponding preemption DCI format is for DL preemption.

[0177] 2k. The method of example 2a, wherein a search space serving DCI format 2 1 is configured for UL preemption DCI, when a number of PDCCH candidates per aggregation level is specifically defined for DCI format 2 1 and when the number of PDCCH candidates per aggregation level is not specifically defined for DCI format 2 1, DCI format 2 1 is used as DL preemption DCI.

[0178] 3a. The method of example la or 2a, wherein said message is DCI 2 4 format message.

[0179] 3b. The method of example 3a, wherein:

[0180] if search space set is a CSS set s, an indication by dci-Format2-4 to monitor

PDCCH candidates for DCI format 2 4 is provided;

[0181] the UE is configured with an INT-RNTI provided by a new RNTI, int-UL-RNTI, for monitoring PDCCH conveying DCI format 2 1;

[0182] the UE can be configured with more than one PDCCH monitoring occasion for

DCI format 2 4; and/or

[0183] DCI format 2 1 is reused for both UL and DL preemption but with an extra bit indicating if the DCI is for DL or UL preemption.

[0184] 3c. The method of example 3a, wherein a search space serving DCI format 2 4 is configured for UL preemption DCI, when more than 1 monitoring occasion is specified within a slot.

[0185] 3d. The method of example 3c, wherein a configuration parameter comprises a plurality of bits wherein a bit is set to‘ 1’ to identify the first OFDM symbol(s) of a control resource set within a slot and having multiple bits set to the value‘ 1’ indicates multiple monitoring occasions within a slot. [0186] 3e. The method of example 3d, wherein the search space configuration parameter is a monitoringSymbolsWithinSlot IE and configuring the search space for the UL preemption DCI format comprises monitoringSymbolsWithinSlot IE specifies more than 1 monitoring occasions within a slot.

[0187] 3f. The method of example 3a, wherein a search space serving DCI format 2 4 is configured for UL preemption DCI, wherein a number of PDCCH candidates per aggregation level is specifically defined for DCI format 2 4.

[0188] 3g. The method of example 3f, wherein the number of PDCCH candidates per aggregation level is defined by a separate parameter, nrofCandidates-UL-PI, and is provided to replace an existing parameter, nrofCandidates.

[0189] 4a. The method of any of the preceding examples, wherein uplink preemption signaling comprises any of the following content:

[0190] a pointer to a future slot or symbol where the UL preemption starts;

[0191] a pointer to a future slot or symbol where the UL preemption ends;

[0192] a pointer to a future slot or symbol where the UL preemption starts and pointer to a future slot or symbol where the UL preemption ends;

[0193] soft power control parameters;

[0194] a pointer to a specific OFDM symbol where the UL preemption starts and there is no indicator where the preemption ends, such that the UE then assumes that the preemption continues until a specified time;

[0195] in one version of the example, the specified time is the end of the slot which contains the specific OFDM symbol;

[0196] in one version of the example, the specified time is the end of the PUSCH transmission that is being preempted;

[0197] in one version of the example, the specified time is the end of the last PUSCH transmission in a set of repeated PUSCH transmissions, where the set of repeated PUSCH transmissions are either scheduled by the same DCI or is one period of an UL CG transmission.

[0198] in one version of the example, the referenced symbols are future symbols with start and end symbol determined by UE based on start or end of PDCCH comprising the UL preemption indicator and the monitoring periodicity P symbols of UL preemption indicator (e.g., if the DCI was received on a PDCCH with start/end symbol n, then the start symbol of the referenced future symbols is n + n offset where n offset is a fixed value or semi-static value, and the end symbol of the referenced future symbols may be n + P + n offset.

[0199] in one version, the future symbols are referenced using bitmap where each bit reference a group of consecutive symbols.

[0200] the referenced symbols are in a reference numerology other than the numerology in which the UL preemption occurs. When symbols in the reference numerology are indicated as pre-empted, then a UE determines which symbols in its transmission numerology are subject for preemption based on its transmission numerology and the reference numerology.

[0201] 5a. The method of any of the preceding examples, wherein the specific time

TUL,PI where the UL preemption starts is provided without explicit signaling.

[0202] 5b. The method of example 5a, wherein TUL,PI provides a specific symbol that follows the PDCCH carrying the UL preemption DCI.

[0203] 5c. The method of example 5b, wherein he specific symbol is the next symbol with its cyclic prefix (CP) which starts TUL,PI after the end of reception of the last symbols of the PDCCH carrying the UL preemption DCI.

[0204] 5d. The method of example 5b or 5c, wherein TUL,PI =Tproc,2, where , with the following parameter values:

[0205] Variable d2,l set to 0

[0206] Variable d2,2 set to 0

[0207] m is set to pDL, the subcarrier spacing of the downlink carrier where the PDCCH of UL PI DCI is transmitted and

[0208] N2 corresponds to the N2 value of the UE processing capability 2.

[0209] 5e. The method of any of examples 5a to 5d, wherein TUL,PI corresponds to non uplink symbols indicated by a TDD-UL-DL-ConfigurationCommon in a serving cell where the PDCCH is sent.

[0210] 5f. The method of example 5e, wherein TUL,PI provides a specific uplink symbol that follows the PDCCH carrying the UL preemption DCI.

[0211] 5g. The example of 5f, wherein the specific symbol is the next uplink symbol with its cyclic prefix (CP) which starts TUL,PI after the end of reception of the last symbols of the PDCCH carrying the UL preemption DCI, wherein a symbol refers to an OFDM symbol for DL as well as UL when transform precoding is not enabled and when transform precoding is enabled for UL, the symbol is referred to as a DFT-s-OFDM symbol.

[0212] 6a. The method of any of the preceding examples, wherein the impact to preempted UE UL transmission is adapted or preconfigured.

[0213] 6b. The method of example 6a, wherein, for the UE being preempted, all UL transmissions otherwise scheduled for transmission in the preempted time-frequency resources are dropped.

[0214] 6c. The method of example 6a, wherein, for the UE being preempted, certain types of UL transmission otherwise scheduled for transmission in the preempted time-frequency resources are dropped, and other types are not dropped.

[0215] 6d. The method of example 6c, wherein the not-dropped UL transmission includes:

[0216] PUCCH carrying HARQ-ACK and/or SR (scheduling request); and the dropped

UL transmission includeS:

[0217] PUSCH, PUCCH carrying CSI (channel state information) only, SRS (sounding reference signal).

[0218] 7a. An apparatus (e.g., node) adapted to perform any of examples 1-6.

[0219] 7b. A computer program comprising instructions which when executed by processing circuitry of an apparatus causes the apparatus to perform the method of any one of examples 1-6.

[0220] 7c. A carrier containing the computer program of example 7b, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.

[0221] 7d. An apparatus (e.g., node), comprising:

[0222] a transmitter; and

[0223] processing circuitry adapted to perform any of examples 1-6.

[0224] 8a. A method, comprising:

[0225] receiving an uplink preemption message, wherein said uplink preemption message comprises an indicator to refrain from transmitting on a resource; and [0226] in response to said uplink preemption message, refraining from transmitting on said resource.

[0227] 8b. The method of example 6a, further comprising:

[0228] before receiving said uplink preemption message, receiving authorization to transmit on said resource.

[0229] 8c. The method of example 6a or 6b, wherein said message is configured as set forth in any of examples 1-6.

[0230] 9a. An apparatus (e.g., UE) adapted to perform any of examples 8a-8c.

[0231] 9b. A computer program comprising instructions which when executed by processing circuitry of an apparatus causes the apparatus to perform the method of any one of examples 8a-8c.

[0232] 9c. A carrier containing the computer program of example 9b, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.

[0233] 9d. An apparatus (e.g., UE), comprising:

[0234] a receiver; and

[0235] processing circuitry adapted to perform any of examples 8a-8c.

[0236]

[0237] Inter-UE prioritization and multiplexing for UL transmission was identified as an area that may need to be addressed to achieve the objectives for URLLC use cases. This topic was discussed during Rel-15 as well. Currently for Rel-16 two solutions have been agreed: the pre-emption based solutions and power control based solutions. RANI to study the potential enhancements for UL inter UE Tx prioritization/multiplexing. Performance study of the enhanced UL inter UE Tx prioritization/multiplexing mechanisms using Re-15 mechanisms as the performance benchmark. The use cases and scenarios adopted in LI enhancements for URLLC are considered for the evaluation of UL inter UE Tx prioritization/multiplexing. Other factors to be considered such as overhead, capability, etc. Study the UE UL cancelation mechanisms, including at least the potential mechanisms may include UE UL

cancelation/pausing indication, UL continuation indication, UL re-scheduling indication;

Physical channel/signal used for the UL cancelation indication; UE Processing timeline for the UL cancelation indication; UE monitoring behaviors for the UL cancelation indication; UE PDCCH monitoring capability, if the EIL cancelation indication is by PDCCH; methods to ensure the reliability of the indication for EE EIL cancelation; the EE power control enhancements; other enhancements for the multiplexing between a grant-based EE transmission from a EE and a grant-free EE transmission from another EE.

[0238] Potential EE power control enhancements: enhanced dynamic power boost for

EIRLLC EE; Dynamic change of power control parameters, e.g. P0, alpha without SRI configured; Enhanced TPC, e.g. increased TPC range, finer granularity. The need of URLLC UE power change during one transmission instance might not be envisioned. Enhanced dynamic power boost for URLLC UE, including at least: feasibility of boosting UE power in power limited or interference limited scenarios; Physical channel/signal used for the signaling; UE Processing timeline for the signaling; UE monitoring behaviours for the signaling; UE PDCCH monitoring capability, if the signalling is by PDCCH; methods to ensure the reliability of the signaling; Type of gNB receiver should be reported. Note: Other power control enhancements are not precluded; No change of eMBB UE power control scheme is assumed.

[0239] The following should be included in TR 38.824 section 7.2.1“UE UL cancelation mechanisms”: UE UL cancelation mechanism is considered as one potential enhancement for UL inter-UE Tx prioritization/multiplexing. Either PDCCH or sequence can be considered as potential options for the UL cancelation indication. If PDCCH is used, either group common DCI or UE-specific DCI can be considered as potential options. If sequence is used, either group common sequence or UE-specific sequence can be considered. The monitoring periodicity for the UL cancelation indication should be configurable by the gNB and UE supporting UL cancelation indication should be able to support more than one monitoring occasions for the UL cancelation indication in a slot. If PDCCH is used, whether the UE PDCCH monitoring capability (number of CCEs/BDs per slot) should be increased is to be further investigated. The UE processing time for UL cancelation indication should be equal or shorter than N2 defined in Rel-15 UE capability#2. Upon detecting an UL cancelation indication, UE cancels the corresponding UL transmission. The corresponding UL transmission may include an on-going UL transmission, or an UL transmission that has not been started. After cancelation, the UE may resume the transmission afterwards as one option, or may not resume the transmission afterwards as another option.

[0240] Enhanced UL power control is considered as one potential enhancement for UL inter-UE Tx prioritization/multiplexing. The potential enhanced EIL power control may include UE determining the power control parameter set (e.g. P0, alpha) based on scheduling DCI indication without using SRI, or based on group-common DCI indication. Increased TPC range compared to Rel-15 may also be considered. Power boosting is not applicable to power limited UEs.

[0241] It is recommended that both UL cancelation scheme and enhanced UL power control scheme to be specified.

[0242] UL inter-UE multiplexing by pre-emption or power control - the two options that have been discussed for enabling dynamic resource sharing, when needed, between traffic with different priorities such as eMBB and URLLC. The choice should serve the purpose with reasonable limits on the complexity incurred. The idea behind inter-UE multiplexing is the following. Based on the request from some UEs for urgent transmission of high priority UL traffic (URLLC traffic), the gNB needs to provide resources to accommodate transmissions as soon as possible to meet the delay requirements. It can happen that the gNB has already assigned the suitable UL resources to one or multiple other UEs for UL transmissions with less stringent requirements in terms of delay (eMBB traffic). Hence, the gNB needs to re-schedule those resources for the prioritized URLLC transmissions. In section 2.2 we go through some of the design choices a little bit more in detail. Irrespective of the enabling mechanism (muting or power control) this goal would be achieved at the cost of 1) additional signalling and complexity both at UE and gNB due to changing ongoing or planned UL transmissions and 2) impact to the performance of eMBB traffic. For the cost to be worth investing, it is important to adopt a mechanism that ensures best the required quality of the URLLC transmissions. The fundamental drawback with power control-based schemes is that the URLLC transmissions would suffer from the interference originating from transmissions controlled by the serving gNB where in fact those transmissions could have been de-prioritized. To study further possible negative impact on URLLC transmission a simulation work has been done on link level. It has been shown that using power control only very robust MCSs can ensure URLLC reliability, otherwise there is a high chance of BLER floor appearing. Moreover, power boosting of URLLC transmissions, is firstly only possible for non-power-limited UE, and secondly would not only increase the interference for neighbouring cells, but also impact the performance of eMBB traffic. One of the advantages of using power control based schemes is that it can be effective also when the interfering UE cannot be pre-empted in time, for example when the non-URLLC UE does not support uplink pre-emption or when it is not monitoring PDCCH frequently enough. Also, it can be seen that there are situations where it would be enough from a URLLC perspective to just reduce the transmit power for the interfering eMBB UE. This would however require the eMBB UE to frequently monitor PDCCH. There will be situations when one scheme is more effective than the other and that the design should allow for a dynamic selection between the two schemes.

[0243] Details of the UL pre-emption signalling method include: whether PDCCH or sequence is used to indicate a pre-emption. In either of the two cases, whether it is group common signaling or UE specific signaling should be used; if PDCCH is used, whether UE PDCCH monitoring capability should be increased; and whether the UE should resume the eMBB transmission afterward or cancel the eMBB transmission

[0244] Regarding the medium for sending the indication, it may be better to use an existing channel rather than introducing a new signal for UE-specific or group signalling. One reason is that introducing a new signal, causes more overhead and from a resource efficiency point of view it is not preferred. In our understanding, reusability has been a general

consideration in designing the physical channels in NR, and unless a physical channel reuse is not possible a new signal can be introduced. In some examples it is proposed to use PDCCH to indicate UL pre-emption.

[0245] For a latency critical UL transmission, the gNB has to allocate suitable resources.

For this purpose, mini-slot type of resource (i.e. short duration in time) are best suited. Achieving other performance requirements, such as required reliability, can be assisted by, for example, suitable allocation in frequency domain up to the entire UL active BWP. These suitable resources may have already been assigned specifically to one or multiple UEs that therefore need to be pre-empted. This implies that although the UL pre-emption indication is in fact effective in a UE-specific manner, it is a better design choice to consider a group common UL pre-emption indication with the flexibility to adjust the group size depending on the scenario, from a single UE to multiple UEs, as needed. This approach preserves the properties for the single UE case while reducing signalling overhead and blocking probability in case multiple UEs need to be pre empted. In some examples for UE-specific or group signaling, in Rel-16, consider group common signalling for UL pre-emption indication is proposed.

[0246] As discussed above, with the arrival of delay critical UL transmissions, the gNB has to inform the affected UEs, as soon as possible. This requires that the UE should be able to monitor the UL pre-emption indication as frequently as possible to be able to react in case of sudden arrival of delay critical UL traffic. Rel-15 already supports CORESET monitoring to enable mini-slot transmissions which are essential for supporting URLLC traffic. To balance the need of frequent monitoring with the increased UE processing burden, it should be studied how frequently the group common signalling for pre-emption indication should be monitored.

[0247] The appropriate monitoring periodicity of group-common signalling for indicating

UL pre-emption is to be studied.

[0248] Candidates for group common signaling include aiming to reuse the already existing mechanism, when possible, the two following options are mainly considered for group common signalling of UL pre-emption: one option is UL pre-emption indication based on DCI format 2 0 (dynamic SFI); another option is UL pre-emption indication design similar to DCI format 2 1 (DL pre-emption indication). In the first option, it is proposed to use the existing dynamic SFI and define a new (or extended) UE behavior. For example, when a UE detects an assignment flexible (or DL) for the symbols that have already scheduled by UE specific signalling for UL transmissions, the UE completely cancels the UL transmissions. This design choice is based on two assumptions, i.e., for the purpose of UL pre-emption, 1) dynamic SFI overrides UE specific signalling and 2) the pre-empted UL transmission is not delayed and resumed but simply cancelled. This approach is simple and requires less processing time at the UE due to the need for only cancelling UL transmissions. However, it requires to define a new behaviour which is based on the assumption that a later SFI over-riding a prior UE-specific DCI which by itself is contradictory with the design philosophy used in Rel-15. Moreover, relying on the existing SFI regime for the simplicity reasons implies that the specified SFI table for Rel-15 (i.e. Table 11.1.1-1 in TS 38.213) should be used. With careful examining the entries of this table, one can observe limitations on where the UL transmission cancellation can occur as compared to a bit map pattern that provide full flexibility. [0249] In the second option, the DL pre-emption mechanism can be adopted for the UL pre-emption indication. This approach enables a gNB to indicate to a UE with finer granularity which resources are needed to be pre-empted by using a bit map pattern. This mechanism is flexible in the sense that depending on how the UE behaviour is defined or its capability, the bit map pattern can be used to indicate when the UL transmission should be stopped without resuming transmission afterwards. Or alternatively, it can be used to indicate to the UE when to stop and then resume the UL transmission if the UE is capable of such operation in reasonable time. Since the reception of the pre-emption indication at the UE side may be crucial to maintain URLLC reliability we also see a need to keep the DCI size small. We note that the bit map pattern used for DCI 2 1 may not be needed for UL pre-emption and a more compact representation could be advantageous. On the other hand would a smaller DCI format disallow the possibility to have its size aligned to for example DCI format 2 1. In some examples the decision on the type of group common signalling for UL pre-emption depends on resolving the key design issue of UE behaviour when detecting an UL pre-emption indication (simply stop or stop and resume depending on the capability).

[0250] In some examples, in Rel-16, the following options may be considered as baseline candidates for the design of group common signaling for UL pre-emption: UL pre-emption indication based on DCI format 2 0 (dynamic SFI) or UL pre-emption indication design similar to DCI format 2 1 (Group common DL pre-emption indication). Whether the UE simply stops or stops and resumes a UL transmission that is indicated to be pre-empted may be based on its capability

[0251] As mentioned previously, with the arrival of delay critical UL transmissions, the gNB has to inform the affected UEs as soon as possible. The feature discussed here would be meaningful if the UE is capable of reacting to the commands transmitted by gNB fast enough, including the UEs intended to interrupt their corresponding UL transmissions and the UEs intended to transmit the delay critical UL traffic. Moreover, if based on the further study, the ongoing transmission is decided to be simply stopped and not resumed when UL pre-emption indication is detected, processing time of less than N2 symbols is expected to be feasible. The UE in such situation only needs to mute the transmission and is not required to prepare a UL transmission (e.g. PUSCH) which requires encoding and mapping to physical resources. However, if the UL transmission is going to be resumed after muting, further study is needed to determine the minimum required processing time. Supporting more advanced UEs in Rel-16 with shorter processing time is crucial for proper NR operations to serve delay critical services. In Rel-16, supporting new UE capability with shorter processing time than Rel-15 is proposed. For example, use PDCCH to indicate UL pre-emption; consider group-common signalling for UL pre-emption indication; study the appropriate monitoring periodicity of group-common signalling for indicating UL pre-emption; consider the following options as baseline candidates for the design of group common signaling for UL pre-emption: UL pre-emption indication based on DCI format 2 0 (dynamic SFI) or UL pre-emption indication design similar to DCI format 2 1 (Group common DL pre-emption indication); study whether the UE simply stops or stops and resumes a UL transmission that is indicated to be pre-empted based on its capability; new UE capability with shorter processing time than Rel-15 should be considered.

[0252] While various embodiments or examples of the present disclosure are described herein, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments. Moreover, any combination of the above- described elements in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context.

[0253] Additionally, while the processes described above and illustrated in the drawings are shown as a sequence of steps, this was done solely for the sake of illustration. Accordingly, it is contemplated that some steps may be added, some steps may be omitted, the order of the steps may be re-arranged, and some steps may be performed in parallel.

[0254] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. [0255] Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0256] In general, the usage of“first”,“second”,“third”,“fourth”, and/or“fifth” herein may be understood to be an arbitrary way to denote different elements or entities, and may be understood to not confer a cumulative or chronological character to the nouns they modify, unless otherwise noted, based on context.

[0257] Several embodiments are comprised herein. It should be noted that the examples herein are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present in another embodiment and it will be obvious to a person skilled in the art how those components may be used in the other exemplary embodiments

[0258] The embodiments herein are not limited to the above described embodiments.

Various alternatives, modifications and equivalents may be used. Therefore, the above embodiments should not be taken as limiting the scope of the embodiments. A feature from one embodiment may be combined with one or more features of any other embodiment.

[0259] The term“at least one of A and B” should be understood to mean“only A, only

B, or both A and B.”, where A and B are any parameter, number, indication used herein etc.

[0260] It should be emphasized that the term“comprises/comprising” when used in this specification is taken to specify the presence of stated features, integers, steps or components, but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof. It should also be noted that the words“a” or“an” preceding an element do not exclude the presence of a plurality of such elements.

[0261] The term“configured to” used herein may also be referred to as“arranged to”,

“adapted to”,“capable of’ or“operative to”.

[0262] It should also be emphasized that the steps of the methods may, without departing from the embodiments herein, be performed in another order than the order in which they appear herein.

Claims

CLAIMS:

1. A method performed by a network node, comprising:

generating an uplink preemption message; and

transmitting the message to a first device,

wherein the uplink preemption message is a Downlink Control Information, DCI, message that comprises an indicator for the first device to refrain from transmitting on a preempted resource.

2. The method of claim 1, wherein the message comprises a DCI format for group common uplink preemption message transmitted on a control channel.

3. The method of claim 1 or 2, wherein the first device was previously scheduled for uplink transmission on the preempted resource.

4. The method of any of claims 1-3, wherein the preempted resource is a time-frequency resource.

5. The method of any of claims 1-4, wherein the indicator is a pointer.

6. The method of any of claims 1-5, wherein the indicator corresponds to a resource bitmap for the first UE.

7. The method of claim 6, wherein the bitmap describes a set of time-frequency resources and the set includes the preempted resource.

8. The method of any of claims 1-7,

wherein the generating or transmitting the uplink preemption message comprises using a Radio Network Temporary Identifier, RNTI, and

wherein use of the RNTI indicates that the message carries information about uplink preemption.

9. The method of claim 8, wherein the RNTI is an uplink cancellation indication RNTI.

10. The method of any of claims 1-9, wherein the message comprises a first plurality of bits relating to downlink preemption and a second plurality of bits relating to uplink preemption.

11. The method of any of claims 1-10, further comprising:

transmitting a Radio Resource Control, RRC, configuration to the first device, wherein the configuration indicates a message position for the indicator to refrain from transmitting on the preempted resource.

12. The method of any of claims 1-11, wherein a size of the message indicates that the message relates to uplink preemption.

13. The method of any of claims 1-12, further comprising:

determining that a second device is scheduled for transmission on the preempted resource; and

receiving traffic from the second device on the preempted resource or transmitting traffic to the second device on the preempted resource.

14. The method of claim 13, wherein the second device has a higher priority than the first device.

15. The method of claim 13 or 14, wherein and the second device is an ultra-reliable low latency communication, URLLC, device and the first device is not a URLLC device.

16. The method of claim 15, wherein the first device is an enhanced mobile broadband, eMBB, device

17. The method of any of claims 1-16,

wherein the first device is configured with more than one Physical Downlink Control Channel, PDCCH, monitoring occasion for DCI format messages per slot or within a given periodicity, and

wherein the message is generated such that a first occasion within a slot or within a given periodicity is for downlink preemption indication and a second occasion within a slot or within a given periodicity is for uplink preemption.

18. The method of any of claims 1-17, wherein the message indicates one or more of a future slot or symbol where uplink preemption starts or where uplink preemption ends.

19. The method of any of claims 1-18, wherein all uplink transmissions otherwise scheduled for transmission in the preempted resource are dropped.

20. The method of any of claims 1-18, wherein one or more of a first type of uplink transmission otherwise scheduled for transmission in the preempted resource are dropped, and one or more of a second type of uplink transmission are not dropped.

21. The method of claim 20, wherein

the first type comprises one or more of the type Physical Uplink Shared Channel, PUSCH; PUCCH carrying Channel State Information, CSI, only; and Sounding Reference Signal, SRS; and

the second type comprises one or more of the type Physical Uplink Control Channel, PUCCH, carrying hybrid automatic repeat request acknowledge HARQ-ACK; and a scheduling request, SR.

22. The method of any of claims 1-21, further comprising:

sending a configuration message for the first device to monitor PDCCH for an uplink cancelation indication RNTI

23. The method of any of claims 1-22, further comprising:

sending to the first device, before transmitting the message that comprises an indicator for the first device to refrain from transmitting on a preempted resource, an authorization to transmit on the preempted resource.

24. The method of any of claims 1-23, wherein the message is a DCI format 2 4 message.

25. A network node adapted to perform any of claims 1-24.

26. A computer program comprising instructions that when executed by processing circuitry of an apparatus causes the apparatus to perform the method of any one of claims 1-24.

27. A carrier containing the computer program of claim 26, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.

28. An apparatus, comprising:

processing circuitry adapted to generate an uplink preemption message; and a transmitter adapted to transmit the message to a device,

wherein the uplink preemption message is a Downlink Control Information, DCI, message that comprises an indicator for the device to refrain from transmitting on a preempted resource.

29. A method performed by a device, comprising:

receiving an uplink preemption message, wherein the uplink preemption message is a Downlink Control Information, DCI, message that comprises an indicator to refrain from transmitting on a preempted resource; and

in response to the uplink preemption message, refraining from transmitting on the preempted resource.

30. The method of claim 29, further comprising:

before receiving the uplink preemption message, receiving authorization to transmit on the preempted resource.

31. The method of 29 or 30, wherein the indicator is a pointer to information regarding scheduled resources.

32. The method of claim 31, further comprising:

identifying the preempted resource in a bitmap of time-frequency resources based at least in part on the pointer.

33. The method of any of claims 29-32, further comprising:

performing a blind decode of at least a portion of the message,

determining that the decode was successful based on one or more of a Radio Network Temporary Identifier, RNTI, and check-sum, wherein the determining indicates that the message relates to uplink preemption.

34. The method of claim 33, wherein the RNTI is an uplink cancellation indication RNTI.

35. The method of any of claims 29-34, wherein a size of the message indicates that the message relates to uplink preemption.

36. The method of any of claims 29-35, further comprising:

receiving a Radio Resource Control, RRC, configuration, wherein the configuration indicates a message location of the indicator to refrain from transmitting on the preempted resource.

37. The method of any of claims 29-36, wherein the message indicates one or more of a future slot or symbol where uplink preemption starts or where uplink preemption ends.

38. The method of any of claims 29-37, wherein all uplink transmissions otherwise scheduled for transmission in the preempted resource are dropped.

39. The method of any of claims 29-37, wherein one or more of a first type of uplink transmission otherwise scheduled for transmission in the preempted resource are dropped, and one or more of a second type of uplink transmission are not dropped.

40. The method of claim 39, wherein

the first type comprises one or more of the type Physical Uplink Control Channel, PUCCH, carrying hybrid automatic repeat request acknowledge HARQ-ACK; and a scheduling request, SR; and

the second type comprises one or more of the type Physical Uplink Shared Channel, PUSCH; PUCCH carrying Channel State Information, CSI, only; and Sounding Reference Signal, SRS.

41. The method of any of claims 29-40, further comprising:

monitoring a Physical Control Downlink Channel, PDCCH, for an uplink cancelation indication RNTI.

42. The method of any of claims 29-42, further comprising:

determining a future start or end symbol for preemption.

43. The method of 42, wherein the determining is based on a start or end of PDCCH comprising the indicator and a periodicity.

44. The method of claim 42 or 43, wherein a start or end symbol is determined based at least in part on an offset value, and wherein the offset value is a fixed or semi-static value.

45. The method of claim 32, wherein a bit in the bitmap of time-frequency resources is a reference to a group of consecutive symbols.

46. The method of any of claims 29-45, wherein the message comprises a DCI format for group common uplink preemption message received on a control channel.

47. The method of any of claims 29-46, wherein the message comprises a DCI format 2 4 message.

48. An apparatus adapted to perform any of claims 29-47.

49. The apparatus of claim 48, wherein the apparatus is a User Equipment, UE.

50. A computer program comprising instructions which when executed by processing circuitry of an apparatus causes the apparatus to perform the method of any one of claims 29-47.

51. A carrier containing the computer program of claim 50, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, and a computer readable storage medium.

52. An apparatus comprising:

a receiver adapted to receive an uplink preemption message, wherein the uplink preemption message is a Downlink Control Information, DCI, message that comprises an indicator to refrain from transmitting on a preempted resource; and

processing circuitry adapted to, in response to the uplink preemption message, cause the apparatus to refrain from transmitting on the preempted resource.

53. The apparatus of claim 52, wherein the indicator is a pointer, and the processing circuitry is further adapted to identify the preempted resource in a bitmap of time-frequency resources based at least in part on the pointer.