WO2020201388A1 - Procédés et appareils de préemption de la transmission en liaison montante - Google Patents

Procédés et appareils de préemption de la transmission en liaison montante Download PDF

Info

Publication number
WO2020201388A1
WO2020201388A1 PCT/EP2020/059314 EP2020059314W WO2020201388A1 WO 2020201388 A1 WO2020201388 A1 WO 2020201388A1 EP 2020059314 W EP2020059314 W EP 2020059314W WO 2020201388 A1 WO2020201388 A1 WO 2020201388A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
preemption
uplink
resource
transmitting
Prior art date
Application number
PCT/EP2020/059314
Other languages
English (en)
Inventor
Alexey SHAPIN
Jonas FRÖBERG OLSSON
Ali Behravan
Yufei Blankenship
Mattias Andersson
David Sandberg
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2020201388A1 publication Critical patent/WO2020201388A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path

Definitions

  • Ultra-reliable and low latency communication 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.
  • 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.
  • eMBB enhanced mobile broadband
  • UEs URLLC user equipment
  • a method 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).
  • the message is a DCI format 2 4 message transmitted on a control channel.
  • a method 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.
  • the device receiving the message Before receiving the uplink preemption message, the device receiving the message may have previously received authorization to transmit on the preempted resource.
  • the indicator is a pointer (e.g., a pointer to information regarding scheduled resources).
  • a device e.g., a UE receiving the message
  • apparatuses e.g., a network node or UE
  • 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.
  • FIG. 1 illustrates a system according to embodiments.
  • FIGs. 2A, 2B, and 2C are flow charts illustrating processes according to embodiments.
  • FIG. 3 A is a schematic block diagram illustrating a telecommunication network connected via an intermediate network to a host computer.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 4 illustrates a configuration according to some embodiments.
  • FIG. 5A is a schematic drawing illustrating an example of a UE.
  • FIG. 5B is a schematic drawing illustrating an example of a UE.
  • FIG. 6A is a schematic drawing illustrating an example of a network node.
  • FIG. 6B is a schematic drawing illustrating an example of a network node.
  • multiplexing/prioritization of UE’s within a cell This can include a combination of the two approaches.
  • a first approach is based on power control to increase the power of at least one
  • UE e.g., a URLLC UE
  • Power controls for release 15 UEs are specified in 3GPP TS 38.213,
  • a technical solution for notifying UEs in a cell about uplink (UL) preemption.
  • UL uplink
  • a current group common DCI format can be used and/or a new format can be used.
  • existing DCI messages regarding downlink preemption are distinguished from those with a preemption indication for UL.
  • 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).
  • a node e.g., base station
  • interfering UEs e.g., an eMBB UE
  • the node can transmit a preemption indicator to the lower priority EE using the DCI format.
  • the lower priority UE will avoid transmitting on a set of preconfigured resources.
  • 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.
  • 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.
  • 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.
  • the node e.g., gNB
  • the node can choose to preempt the eMBB traffic and hence reduce the interference to the URLLC UE.
  • 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.
  • URLLC vs. eMBB URLLC vs. eMBB
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • Step s220 comprises generating an uplink preemption message.
  • 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.
  • 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.
  • 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.
  • 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.
  • the RNTI is an uplink cancellation indication RNTI.
  • 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.
  • PDCCH Physical Downlink Control Channel
  • a node 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.
  • RRC Radio Resource Control
  • the process 2000 may be based on a determination that a second device is scheduled for transmission on the resource.
  • the node may receive traffic from the second device on the preempted resource or transmit to the second device on the preempted resource.
  • the second device may have a higher priority than the first device.
  • the second device may be a URLLC device.
  • FIG. 2B is a flowchart illustrating a process 2400 according to some
  • the process may begin with step s260.
  • the process may be performed, for instance by a UE 101 or 102.
  • Step s260 comprises receiving an uplink preemption message.
  • 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.
  • the device receiving the message e.g., UE 101
  • 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.
  • the indicator may be a pointer.
  • the device e.g., UE 101
  • 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.
  • the size of the message can indicate that the message relates to uplink preemption.
  • FIG. 2C is a flowchart illustrating a process 2750 according to some
  • 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.
  • the message may comprise a first plurality of bits relating to downlink preemption and a second plurality of bits relating to uplink preemption.
  • FIGs. 3A-3F 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.
  • 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.
  • existing formats may be used.
  • the existing formats may be used. For instance, the existing
  • DCI format may be used to communicate downlink and/or uplink preemption.
  • DCI formats 2_X there are several DCI formats 2_X that are dedicated for group signaling.
  • 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.
  • PI downlink preemption indication
  • 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 new RNTI e.g. INT-UL-RNTI
  • a successful decode with the uplink cancellation indication RNTI can indicate to the UE that the preemption relates to the uplink.
  • 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.
  • one part of size 14*N bits carries information about DL preemption and another part 14*M bits carries information about UL preemption.
  • 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.
  • the position in the DCI of preemption information can be signaled.
  • 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.
  • 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.
  • 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.
  • OFDM orthogonal frequency-division multiplexing
  • 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.
  • DCI format 2 1 (e.g., for DL preemption) is monitored in common search space.
  • 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.
  • 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.
  • 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.
  • a search space serving DCI format 2 1 is configured for
  • 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.
  • the search space configuration parameter is a monitor ingSymbolsWithinSlot IE.
  • monitoringSymbolsWithinSlot of the search space does not specify more than 1 monitoring occasions within a slot.
  • 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.
  • a separate parameter such as nrofCandidates-UL-PI , is provided to replace an existing the existing parameter nrofCandidates.
  • DCI format 2 1 may be used as DL preemption DCI.
  • a new DCI format may be used for uplink preemption.
  • “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.
  • a new DCI format within the formats dedicated for group signaling for example 2 4, is used.
  • the new DCI format is for group common communication preemption.
  • a common format with a configurable payload is used.
  • 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.
  • a UE e.g., UE 101
  • a new RNTI int-UL-RNTI
  • a successful decode with an uplink cancellation indication RNTI can indicate to the UE that the preemption relates to the uplink.
  • the UE can be configured with more than one PDCCH monitoring occasion for DCI format 2 4.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a separate parameter e.g.
  • nrofCandidates-UL-PI is provided to replace an existing parameter, such as nrofCandidates.
  • uplink signaling content examples are provided below. This content may be, for instance, with respect to a new DCI format used for uplink preemption.
  • the signaling of UL preemption/interruption includes a pointer to a future slot or symbol where the UL preemption starts.
  • the signaling of UL preemption/interruption can include a pointer to a future slot or symbol where the UL preemption ends.
  • 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.
  • 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.
  • the specified time is the end of the slot which contains the specific OFDM symbol.
  • the specified time is the end of the Physical Uplink Share Channel (PUSCH) transmission that is being preempted.
  • 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.
  • PUSCH Physical Uplink Share Channel
  • 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.
  • CP cyclic prefix
  • TUL.PI T proc,2 , where the following parameter values:
  • variable di,2 set to 0
  • 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;
  • 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.
  • CP cyclic prefix
  • 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.
  • 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 0 ⁇ set , where n 0 ⁇ set is a fixed value or semi-static value, and the end symbol of the referenced future symbols may be n + P + n 0 ⁇ set .
  • 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.
  • the referenced symbols are in a reference numerology other than the numerology in which the UL preemption occurs.
  • a UE determines which symbols in its transmission numerology are subject for preemption based on its transmission numerology and the reference numerology.
  • the signaling of UL preemption/interruption includes soft power control parameters.
  • 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.
  • 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).
  • HARQ-ACK hybrid automated request acknowledgment
  • SR scheduling request
  • PUSCH PUCCH carrying CSI (channel state information) only
  • SRS sounding reference signal
  • 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.
  • a processor may perform any of the methods described with respect to FIGs. 2A, 2B, and 2C.
  • 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.
  • FIGs. 5A and 5B two different examples are depicted, respectively, comprising the arrangement of a UE, such as UE 101.
  • UE 101 is used in these examples, similar descriptions and arrangements may apply to UE 102.
  • 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.
  • 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.
  • 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.
  • the first receiving port 504 may be, for example, connected to one or more antennas in UE 101.
  • 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.
  • 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.
  • the UE 101 may comprise a determining unit 515, an obtaining unit 518, a providing unit 528, etc.
  • 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.
  • processors 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).
  • SoC System-on-a-Chip
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the UE 101 may comprise the arrangement depicted in
  • 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.
  • inventions 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.
  • 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.
  • the first network node 103 may comprise arrangement depicted in FIG. 6A.
  • 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.
  • 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.
  • 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.
  • the second receiving port 604 may be, for example, connected to one or more antennas in first network node 103.
  • 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.
  • 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.
  • the first network node 103 may comprise a determining unit 613, a creating unit
  • determining unit 613 the creating unit 615, the providing unit 618 described above may refer to a
  • 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.
  • processors 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).
  • SoC System-on-a-Chip
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • inventions 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.
  • a telecommunication network connected via an intermediate network to a host computer is provided in accordance with some embodiments.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • the base station may be considered an example of the first network node 103.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the host computer provides user data.
  • substep 3411 (which may be optional) of step 3410, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 3430 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.
  • step 3440 the UE executes a client application associated with the host application executed by the host computer.
  • 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.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • 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.
  • the UE receives the user data carried in the transmission.
  • 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.
  • 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.
  • substep 3621 (which may be optional) of step 3620, the UE provides the user data by executing a client application.
  • 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.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in substep 3630 (which may be optional), transmission of the user data to the host computer.
  • 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.
  • 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.
  • the base station receives user data from the UE.
  • step 3720 (which may be optional)
  • the base station initiates transmission of the received user data to the host computer.
  • step 3730 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • 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.
  • 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
  • the UE 101 comprises processing circuitry configured to execute a client application associated with the host application.
  • 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.
  • a method implemented in a communication system 1000 including a host computer, a base station and a UE 101 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.
  • 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.
  • 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.
  • 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.
  • 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: at the UE 101, receiving the user data from the first network node 103.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a method comprising:
  • said uplink preemption message comprises an indicator to refrain from transmitting on a resource.
  • said generating or transmitting the uplink preemption message comprises using an RNTI (e.g., INT-UL-RNTI), and
  • N number of downlink carriers for which the DCI is signaled for and M is number of uplink carriers the DCI is signaled for
  • one part of size 14*N bits carries information about downlink preemption and another part 14*M bits carries information about uplink preemption.
  • a method comprising:
  • said preemption message indicates one or more of uplink and downlink preemption.
  • a UE is configured with more than one PDCCH monitoring occasion for
  • 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.
  • a UE is configured with more than one PDCCH monitoring occasion for
  • 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.
  • 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
  • a preemption indicator 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.
  • a DCI e.g., format 2 1
  • 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.
  • 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.
  • 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.
  • 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:
  • monitoringSymbolsWithinSlot IE specifies more than 1 monitoring occasions within a slot, the corresponding preemption DCI format is for UL preemption;
  • the corresponding preemption DCI format is for DL preemption.
  • search space set is a CSS set s
  • the UE is configured with an INT-RNTI provided by a new RNTI, int-UL-RNTI, for monitoring PDCCH conveying DCI format 2 1;
  • the UE can be configured with more than one PDCCH monitoring occasion for
  • 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.
  • 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.
  • 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.
  • uplink preemption signaling comprises any of the following content:
  • the specified time is the end of the slot which contains the specific OFDM symbol
  • the specified time is the end of the PUSCH transmission that is being preempted
  • 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.
  • 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.
  • the future symbols are referenced using bitmap where each bit reference a group of consecutive symbols.
  • the referenced symbols are in a reference numerology other than the numerology in which the UL preemption occurs.
  • a UE determines which symbols in its transmission numerology are subject for preemption based on its transmission numerology and the reference numerology.
  • TUL,PI where the UL preemption starts is provided without explicit signaling.
  • m is set to pDL, the subcarrier spacing of the downlink carrier where the PDCCH of UL PI DCI is transmitted and
  • N2 corresponds to the N2 value of the UE processing capability 2.
  • PUSCH PUCCH carrying CSI (channel state information) only, SRS (sounding reference signal).
  • 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.
  • An apparatus e.g., node
  • a apparatus comprising:
  • processing circuitry adapted to perform any of examples 1-6.
  • a method comprising:
  • An apparatus e.g., UE, comprising:
  • processing circuitry adapted to perform any of examples 8a-8c.
  • 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.
  • 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.
  • 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.
  • EIRLLC EE Dynamic change of power control parameters, e.g. P0, alpha without SRI configured; Enhanced TPC, e.g. increased TPC range, finer granularity.
  • 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.
  • Other power control enhancements are not precluded; No change of eMBB UE power control scheme is assumed.
  • 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.
  • the UE processing time for UL cancelation indication should be equal or shorter than N2 defined in Rel-15 UE capability#2.
  • UE cancels 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.
  • 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.
  • 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).
  • the gNB needs to re-schedule those resources for the prioritized URLLC transmissions.
  • 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.
  • 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
  • PDCCH Physical Downlink Control Channel
  • the gNB For a latency critical UL transmission, the gNB has to allocate suitable resources.
  • mini-slot type of resource i.e. short duration in time
  • 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.
  • 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.
  • 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.
  • 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).
  • 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).
  • 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.
  • 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.
  • the specified SFI table for Rel-15 i.e. Table 11.1.1-1 in TS 38.213 should be used.
  • 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.
  • 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.
  • 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.
  • a smaller DCI format disallow the possibility to have its size aligned to for example DCI format 2 1.
  • 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).
  • 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
  • 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.
  • 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.
  • a UL transmission e.g. PUSCH
  • 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.
  • DCI format 2 0 dynamic SFI
  • UL pre-emption indication design similar to DCI format 2 1 Group common DL pre-emption indication
  • a and B are any parameter, number, indication used herein etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des procédés (2000) et des dispositifs (101, 103) pour une préemption de transmission en liaison montante. Selon un aspect, un message de préemption de liaison montante est généré (s220) et transmis (s230) à un dispositif, où le message de préemption de liaison montante est un message d'information de contrôle de liaison descendante (DCI) qui comprend un indicateur pour que le dispositif s'abstienne de transmettre sur une ressource.
PCT/EP2020/059314 2019-04-02 2020-04-01 Procédés et appareils de préemption de la transmission en liaison montante WO2020201388A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201962828263P 2019-04-02 2019-04-02
US62/828,263 2019-04-02
US201962829510P 2019-04-04 2019-04-04
US62/829,510 2019-04-04

Publications (1)

Publication Number Publication Date
WO2020201388A1 true WO2020201388A1 (fr) 2020-10-08

Family

ID=70189940

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2020/059314 WO2020201388A1 (fr) 2019-04-02 2020-04-01 Procédés et appareils de préemption de la transmission en liaison montante

Country Status (1)

Country Link
WO (1) WO2020201388A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220086851A1 (en) * 2020-09-11 2022-03-17 Qualcomm Incorporated Limit for retransmission of dropped feedback
US11523414B2 (en) 2018-01-13 2022-12-06 Wilus Institute Of Standards And Technology Inc. Channel multiplexing method and multiplexed channel transmission method for wireless communication system and device using same
US11601966B2 (en) 2019-10-07 2023-03-07 Wilus Institute Of Standards And Technology Inc. Method, device, and system for cancelling uplink transmission in wireless communication system

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018175420A1 (fr) * 2017-03-20 2018-09-27 Convida Wireless, Llc Planification et commande dans une nouvelle radio en ayant recours à une indication de pré-emption

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018175420A1 (fr) * 2017-03-20 2018-09-27 Convida Wireless, Llc Planification et commande dans une nouvelle radio en ayant recours à une indication de pré-emption

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP TS 38.213, V15.0.0
INSTITUTE FOR INFORMATION INDUSTRY (III): "Considerations for UCI for URLLC", vol. RAN WG1, no. Reno, USA; 20171127 - 20171201, 17 November 2017 (2017-11-17), XP051369084, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG1%5FRL1/TSGR1%5F91/Docs/> [retrieved on 20171117] *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11523414B2 (en) 2018-01-13 2022-12-06 Wilus Institute Of Standards And Technology Inc. Channel multiplexing method and multiplexed channel transmission method for wireless communication system and device using same
US11950226B2 (en) 2018-01-13 2024-04-02 Wilus Institute Of Standards And Technology Inc. Channel multiplexing method and multiplexed channel transmission method for wireless communication system and device using same
US11956774B2 (en) 2018-01-13 2024-04-09 Wilus Institute Of Standards And Technology Inc. Channel multiplexing method and multiplexed channel transmission method for wireless communication system and device using same
US11601966B2 (en) 2019-10-07 2023-03-07 Wilus Institute Of Standards And Technology Inc. Method, device, and system for cancelling uplink transmission in wireless communication system
US20220086851A1 (en) * 2020-09-11 2022-03-17 Qualcomm Incorporated Limit for retransmission of dropped feedback

Similar Documents

Publication Publication Date Title
US11510217B2 (en) Method and apparatus for transmission/reception of signals between wireless devices
US9894654B2 (en) Defining sub-subchannels for data communication using separately provided frequency and time resources and related wireless terminals and network nodes
US11277858B2 (en) Uplink transmission scheme
KR20220016047A (ko) 뉴 라디오(nr) 통신에서의 업링크(ul) 멀티플렉싱 및 우선순위화를 위한 방법 및 장치
KR20190070918A (ko) 유연한 라디오 서비스를 위한 5g nr 데이터 전달
CN114080773B (zh) 具有不同服务类型的harq-ack码本的sr传输的优先级区分
CN107113145B (zh) 用于上行链路无线电资源分配的方法和系统
WO2020069111A1 (fr) Sélection et réservation de ressources associées à un véhicule sur toute liaison latérale
WO2021191874A1 (fr) Dci et multi-dci de signaux mixtes pour la planification de pdsch
WO2020201388A1 (fr) Procédés et appareils de préemption de la transmission en liaison montante
WO2018027918A1 (fr) Procédé et appareil de transmision de canal de liaison montante
EP2829137A1 (fr) Appareil et procédé de gestion de brouillage entre des réseaux cellulaires et locaux
US20240089978A1 (en) Methods and Apparatuses for Handling Configured and Dynamic Downlink Transmissions in a Wireless Communication Network
WO2020146645A1 (fr) Schémas d&#39;attribution de ressources sans fil dans une communication de véhicule à tout (v2x)
CN116349346A (zh) 无线通信系统中用于设备到设备通信的部分感测方法和设备
EP4101238A1 (fr) Ressource de référence pour annulation de liaison montante dans des ressources nr-u
US20240090023A1 (en) Technique For Using Channel Occupancy Time
WO2021089881A1 (fr) Mise en correspondance de priorité de canal logique (lch) dynamique
EP3949628A1 (fr) Attribution de ressources sur la base d&#39;un regroupement de dispositifs sans fil
EP3949553A2 (fr) Ue et premier n?ud de réseau pour gérer des ajustements de puissance
US20240057072A1 (en) Methods of uplink transmission cancellation
JP7416206B2 (ja) 上りリンク信号の送受信方法及び装置
US20230300859A1 (en) Terminal and sidelink communication control method
EP4336922A1 (fr) Procédé et appareil de détermination d&#39;une ressource non préférée dans un système de communication sans fil
WO2022240343A1 (fr) Technique d&#39;utilisation de temps d&#39;occupation de canal

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20717147

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20717147

Country of ref document: EP

Kind code of ref document: A1