WO2020032852A1 - Facteurs bêta pour informations de commande de liaison montante - Google Patents

Facteurs bêta pour informations de commande de liaison montante Download PDF

Info

Publication number
WO2020032852A1
WO2020032852A1 PCT/SE2019/050673 SE2019050673W WO2020032852A1 WO 2020032852 A1 WO2020032852 A1 WO 2020032852A1 SE 2019050673 W SE2019050673 W SE 2019050673W WO 2020032852 A1 WO2020032852 A1 WO 2020032852A1
Authority
WO
WIPO (PCT)
Prior art keywords
indication
uci
offset value
beta offset
network node
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/SE2019/050673
Other languages
English (en)
Inventor
Jonas FRÖBERG OLSSON
Alexey SHAPIN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2020032852A1 publication Critical patent/WO2020032852A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1664—Details of the supervisory signal the supervisory signal being transmitted together with payload signals; piggybacking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]

Definitions

  • UCI Uplink Control Information
  • SR Service Call
  • UCI is transmitted either on physical uplink control channel (PUCCH) when the wireless device has no physical uplink shared channel (PUSCH) transmission or multiplexed on the PUSCH resource when the wireless device is granted a PUSCH transmission.
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • 3GPP third generation partnership project
  • URLLC ultra-reliable low latency communication
  • PDSCH physical downlink shared channel
  • PUSCH data physical downlink shared channel
  • HARQ hybrid automatic repeat request
  • ACK acknowledgement
  • eMBB enhanced mobile broadband
  • CSI channel state information
  • the preferred beam changes for a wireless device and the wireless device may need to inform network node such as a gNB about the change via CSI feedback.
  • network node such as a gNB
  • MCS modulation coding scheme
  • uplink control information (UCI) is multiplexed with PUSCH there are coding offsets also known as beta- factors for HARQ-ACK and CSI that define a coding offset for HARQ-ACK bits and CSI bits relative to the coding of PUSCH data bits.
  • coding offset values that can be used is given by the tables below.
  • Table 1 Mapping of beta_offset values for HARQ-ACK information and the index signalled by higher layers.
  • controlling UCI prioritization may relate to controlling whether a wireless device is to omit at least a portion of information in or from the UCI, and/or may relate to controlling the type of information the wireless device is to provide via the UCI.
  • the disclosure advantageously extends the beta-offset tables with an entry indicating that wireless device may omit HARQ-ACK/CSI from UCI.
  • a method implemented in a wireless device, WD includes receiving an indication of at least one beta offset value for Uplink Control Information, UCI, the indication of the at least one beta offset value indicating whether to transmit at least one of hybrid automatic repeat request-acknowledgement, HARQ-ACK, and channel state information, CSI, in the UCI.
  • the method includes transmitting an encoded physical uplink channel, the physical uplink channel being encoded based at least in part on the indication.
  • receiving the indication of the at least one beta offset value further includes receiving at least one index value corresponding an entry in a table of beta offset values.
  • the at least one beta offset value defines at least one coding offset for at least one UCI bit relative to a coding of at least one Physical Uplink Shared Channel, PUSCH, data bit.
  • the transmitting the physical uplink channel further comprises transmitting PUSCH based at least in part on the indication.
  • the received indication of the at least one beta offset value is based at least in part on whether at least one of the PUSCH, the HARQ-ACK and the CSI corresponds to one of ultra-reliable low latency communications,
  • the at least one beta offset value is to be used for encoding UCI if UCI is multiplexed with the PUSCH.
  • the indication of the at least one beta offset value indicates whether to transmit the at least one of the HARQ-ACK and CSI in the UCI by indicating whether to omit the at least one of the HARQ-ACK and CSI in the UCI.
  • receiving the indication further includes receiving the indication of the at least one beta offset value in at least one of downlink control information, DCI, and radio resource control,
  • a method implemented in a network node includes transmitting an indication of at least one beta offset value for Uplink Control Information, UCI, the indication of the at least one beta offset value indicating whether to transmit at least one of hybrid automatic repeat request-acknowledgement, HARQ-ACK, and channel state information, CSI, in the UCI.
  • the method includes receiving a physical uplink channel, the physical uplink channel encoded based at least in part on the indication.
  • receiving the indication of the at least one beta offset value further comprises receiving at least one index value corresponding to an entry in a table of beta offset values.
  • the at least one beta offset value defines at least one coding offset for at least one UCI bit relative to a coding of at least one Physical Uplink Shared Channel, PUSCH, data bit.
  • the receiving the physical uplink channel further comprises receiving PUSCH based at least in part on the indication.
  • the transmitted indication of the at least one beta offset value is based at least in part on whether at least one of the PUSCH, the HARQ-ACK and the CSI corresponds to one of ultra-reliable low latency communications,
  • the at least one beta offset value is to be used for encoding UCI if UCI is multiplexed with the PUSCH.
  • the indication of the at least one beta offset value indicates whether to transmit the at least one of the HARQ-ACK and CSI in the UCI by indicating whether to omit the at least one of the HARQ-ACK and CSI in the UCI.
  • transmitting the indication further comprises transmitting the indication of the at least one beta offset value in at least one of downlink control information, DCI, and radio resource control, RRC, signalling.
  • a wireless device configured to communicate with a network node.
  • the WD includes processing circuitry.
  • the processing circuitry is configured to cause the WD to receive an indication of at least one beta offset value for Uplink Control Information, UCI, the indication of the at least one beta offset value indicating whether to transmit at least one of hybrid automatic repeat request-acknowledgement, HARQ-ACK, and channel state information, CSI, in the UCI.
  • the processing circuitry is further configured to cause the WD to transmit an encoded physical uplink channel, the physical uplink channel being encoded based at least in part on the indication.
  • the processing circuitry is further configured to cause the WD to receive the indication of the at least one beta offset value by being configured to cause the WD to receive at least one index value corresponding to at least one entry in a table of beta offset values.
  • the at least one beta offset value defines at least one coding offset for at least one UCI bit relative to a coding of at least one Physical Uplink Shared Channel, PUSCH, data bit.
  • the processing circuitry is further configured to cause the WD to transmit the physical uplink channel by being configured to cause the WD to transmit PUSCH based at least in part on the indication.
  • the received indication of the at least one beta offset value is based at least in part on whether at least one of the PUSCH, the HARQ-ACK and the CSI corresponds to one of ultra reliable low latency communications, URLLC, and mobile broadband
  • the at least one beta offset value is to be used for encoding UCI if UCI is multiplexed with the PUSCH.
  • the indication of the at least one beta offset value indicates whether to transmit the at least one of the HARQ-ACK and CSI in the UCI by indicating whether to omit the at least one of the HARQ-ACK and CSI in the UCI.
  • the processing circuitry is further configured to cause the WD to receive the indication by being configured to cause the WD to receive the indication of the at least one beta offset value in at least one of downlink control information, DCI, and radio resource control, RRC, signalling.
  • a network node configured to communicate with a wireless device, WD.
  • the network node includes processing circuitry.
  • the processing circuitry is configured to cause the network node to transmit an indication of at least one beta offset value for Uplink Control Information, UCI, the indication of the at least one beta offset value indicating whether to transmit at least one of hybrid automatic repeat request- acknowledgement, HARQ-ACK, and channel state information, CSI, in the UCI.
  • the processing circuitry is further configured to cause the network node to receive a physical uplink channel, the physical uplink channel encoded based at least in part on the indication.
  • the processing circuitry is further configured to cause the network node to receive the indication of the at least one beta offset value by being configured to cause the network node to receive at least one index value corresponding to at least one entry in a table of beta offset values.
  • the at least one beta offset value defines at least one coding offset for at least one UCI bit relative to a coding of at least one Physical Uplink Shared Channel, PUSCH, data bit.
  • the processing circuitry is further configured to cause the network node to receive the physical uplink channel by being configured to receive PUSCH based at least in part on the indication.
  • the transmitted indication of the at least one beta offset value is based at least in part on whether at least one of the PUSCH, the HARQ-ACK and the CSI corresponds to one of ultra-reliable low latency communications, URLLC, and mobile broadband communications.
  • the at least one beta offset value is to be used for encoding UCI if UCI is multiplexed with the PUSCH.
  • the indication of the at least one beta offset value indicates whether to transmit the at least one of the HARQ-ACK and CSI in the UCI by indicating whether to omit the at least one of the HARQ-ACK and CSI in the UCI.
  • the processing circuitry is further configured to cause the network node to transmit the indication by being configured to cause the network node to transmit the indication of the at least one beta offset value in at least one of downlink control information, DCI, and radio resource control, RRC, signalling.
  • FIG. 1 is a schematic diagram of an exemplary network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure
  • FIG. 2 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure
  • FIG. 3 is a flow chart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure
  • FIG. 4 is a flow chart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure
  • FIG. 5 is a flow chart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure
  • FIG. 6 is a flow chart illustrating exemplary methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure
  • FIG. 7 is a flowchart of an exemplary process of indication unit in a network node for controlling the type of information the wireless device is to provide via the UCI according to some embodiments of the present disclosure.
  • FIG. 8 is a flowchart of an exemplary process of beta unit in a wireless device for controlling the type of information the wireless device is to provide via the UCI according to some embodiments of the present disclosure.
  • the PUSCH can be either eMBB or URLLC.
  • BLER block error rate
  • the encoding of UCI is relative to the encoding of, for example, CSI
  • a targeting BLER for CSI that is fixed, for example at 10 L -2
  • one would need two beta- offsets for CSI where one would be used when PUSCH is eMBB and the other when PUSCH is URLLC.
  • the HARQ-ACK could be either associated with eMBB or URLLC which would mean that potentially 4 beta-factors for HARQ-ACK would be needed if PUSCH could be either eMBB or URLLC.
  • NR 3 GPP Rel-l5 supports both semi- static and dynamic signalling of beta- factors where for dynamic signalling there is a 2-bit field in the Pormat 0_l downlink control information (DCI) that can indicate one out of four semi- static sets of beta- factors.
  • DCI downlink control information
  • the disclosure solves at least a portion of the problems with existing system by extending the beta-offset tables with an entry indicating that the wireless device may omit HARQ-ACK/CSI from UCI.
  • the disclosure provides for the network or network node to control UCI prioritization in the wireless device where the wireless device may receive an indication that HARQ-ACK and/or CSI should not be transmitted in UCI.
  • relational terms such as“first” and“second,”“top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.
  • the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein.
  • the singular forms“a”,“an” and“the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the joining term,“in communication with” and the like may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • electrical or data communication may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example.
  • Implicit indication may for example be based on position and/or resource used for transmission.
  • Explicit indication may for example be based on a parametrization with one or more parameters, and/or one or more index or indices, and/or one or more bit patterns representing the information. It may in particular be considered that control signaling as described herein, based on the utilized resource sequence, implicitly indicates the control signaling type.
  • At least one uplink (UL) connection and/or channel and/or carrier and at least one downlink (DL) connection and/or channel and/or carrier e.g., via and/or defining a cell, which may be provided by a network node, in particular a base station, gNB or eNodeB.
  • An uplink direction may refer to a data transfer direction from a terminal to a network node, e.g., base station and/or relay station.
  • a downlink direction may refer to a data transfer direction from a network node, e.g., base station and/or relay node, to a terminal.
  • UL and DL may be associated to different frequency resources, e.g., carriers and/or spectral bands.
  • a cell may comprise at least one uplink carrier and at least one downlink carrier, which may have different frequency bands.
  • a network node e.g., a base station, gNB or eNodeB, may be adapted to provide and/or define and/or control one or more cells, e.g., a PCell and/or a LA cell.
  • Transmitting in downlink may pertain to transmission from the network or network node to the wireless device. Transmitting in uplink may pertain to
  • Uplink, downlink and sidelink may be considered communication directions.
  • uplink and downlink may also be used to described wireless communication between network nodes, e.g. for wireless backhaul and/or relay communication and/or (wireless) network
  • backhaul and/or relay communication and/or network communication is implemented as a form of sidelink or uplink communication or similar thereto.
  • Configuring a terminal or wireless device or node may involve instructing and/or causing the wireless device or node to change its configuration, e.g., at least one setting and/or register entry and/or operational mode.
  • a terminal or wireless device or node may be adapted to configure itself, e.g., according to information or data in a memory of the terminal or wireless device.
  • Configuring a node or terminal or wireless device by another device or node or a network may refer to and/or comprise transmitting information and/or data and/or instructions to the wireless device or node by the other device or node or the network, e.g., allocation data (which may also be and/or comprise configuration data) and/or scheduling data and/or scheduling grants.
  • Configuring a terminal may include sending allocation/configuration data to the terminal indicating which modulation and/or encoding to use.
  • a terminal may be configured with and/or for scheduling data and/or to use, e.g., for transmission, scheduled and/or allocated uplink resources, and/or, e.g., for reception, scheduled and/or allocated downlink resources.
  • Uplink resources and/or downlink resources may be scheduled and/or provided with allocation or configuration data.
  • Signaling may comprise one or more signals and/or symbols.
  • Reference signaling may comprise one or more reference signals and/or symbols.
  • Data signaling may pertain to signals and/or symbols containing data, in particular user data and/or payload data and/or data from a communication layer above the radio and/or physical layer/s. It may be considered that demodulation reference signaling comprises one or more demodulation signals and/or symbols.
  • Demodulation reference signaling may in particular comprise demodulation reference signals (DMRS) according to 3 GPP, NR and/or LTE technologies.
  • DMRS demodulation reference signals
  • Demodulation reference signaling may generally be considered to represent signaling providing reference for a receiving device like a terminal to decode and/or demodulate associated data signaling or data.
  • Demodulation reference signaling may be associated to data or data signaling, in particular to specific data or data signaling. It may be considered that data signaling and demodulation reference signaling are interlaced and/or multiplexed, e.g. arranged in the same time interval covering e.g. a subframe or slot or symbol, and/or in the same time-frequency resource structure like a resource block.
  • a resource element may represent a smallest time-frequency resource, e.g. representing the time and frequency range covered by one symbol or a number of bits represented in a common
  • a resource element may e.g. cover a symbol time length and a subcarrier, in particular in 3GPP, NR and/or LTE standards.
  • a data transmission may represent and/or pertain to transmission of specific data, e.g. a specific block of data and/or transport block.
  • demodulation reference signaling may comprise and/or represent a sequence of signals and/or symbols, which may identify and/or define the demodulation reference signaling.
  • the term“coupled,”“connected,” and the like may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
  • the term“network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi- standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.
  • MME mobile management
  • wireless device or a user equipment (UE) are used interchangeably.
  • the WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD).
  • the WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer
  • CPE Premises Equipment
  • IoT Internet of Things
  • NB-IOT Narrowband IoT
  • the generic term“radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).
  • RNC evolved Node B
  • MCE Multi-cell/multicast Coordination Entity
  • RRU Remote Radio Unit
  • RRH Remote Radio Head
  • the terms“beta factor,”“beta offset,”“beta offset value” and“offset value” may be used herein interchangeably and may relate to the coding rate for PUSCH.
  • the beta offset value may be defined for a WD and/or a UE to determine a number of resources for multiplexing HARQ- ACK information and for multiplexing CSI reports in a PUSCH.
  • the offset values may be signalled to a WD and/or UE either by a DCI format scheduling the PUSCH transmission or by higher layers.
  • the beta offset value influences the UCI and the PUSCH coding rate, and may have a direct impact on the number of resource elements reserved for UCI.
  • the beta offset value can be used for encoding control information when the control information (e.g., UCI, HARQ, CSI) is multiplexed with PUSCH data.
  • a beta offset value of 1.0 may indicate that the code rate of UCI is the same as the code rate for PUSCH data when UCI is to be multiplexed with PUSCH data.
  • WCDMA Wide Band Code Division Multiple Access
  • WiMax Worldwide Interoperability for Microwave Access
  • UMB Ultra Mobile Broadband
  • GSM Global System for Mobile Communications
  • functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes.
  • the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
  • Embodiments provide for control of UCI prioritization, for example, controlling of whether a wireless device is to transmit and/or omit at least a portion of information in or from the UCI.
  • FIG. 1 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14.
  • the access network 12 comprises a plurality of network nodes l6a, l6b, l6c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area l8a, l8b, l8c (referred to collectively as coverage areas 18).
  • Each network node l6a, l6b, l6c is connectable to the core network 14 over a wired or wireless connection 20.
  • a first wireless device (WD) 22a located in coverage area l8a is configured to wirelessly connect to, or be paged by, the corresponding network node l6c.
  • a second WD 22b in coverage area l8b is wirelessly connectable to the corresponding network node l6a. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.
  • a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16.
  • a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR.
  • WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.
  • the communication system 10 may itself be connected to a host computer 24, 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.
  • the host computer 24 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.
  • the connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30.
  • the intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network.
  • the intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).
  • the communication system of FIG. 1 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24.
  • the connectivity may be described as an over-the-top (OTT) connection.
  • the host computer 24 and the connected WDs 22a, 22b are configured to communicate data and/or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications.
  • a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.
  • a network node 16 is configured to include an indication unit 32 which is configured to cause the network node 16 to transmit an indication of at least one beta offset value for Uplink Control Information, UCI, the indication of the at least one beta offset value indicating whether to transmit at least one of hybrid automatic repeat request-acknowledgement, HARQ-ACK, and channel state information, CSI, in the UCI; and receive a physical uplink channel, the physical uplink channel encoded based at least in part on the indication.
  • UCI Uplink Control Information
  • HARQ-ACK channel state information
  • CSI channel state information
  • a wireless device 22 is configured to include a beta unit 34 which is configured to cause the wireless device 22 receive an indication of at least one beta offset value for Uplink Control Information, UCI, the indication of the at least one beta offset value indicating whether to transmit at least one of hybrid automatic repeat request-acknowledgement, HARQ-ACK, and channel state information, CSI, in the UCI; and transmit an encoded physical uplink channel, the physical uplink channel being encoded based at least in part on the indication.
  • controlling UCI prioritization may include configuring the wireless device 22 according to the indication described herein.
  • a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10.
  • the host computer 24 further comprises processing circuitry 42, which may have storage and/or processing capabilities.
  • the processing circuitry 42 may include a processor 44 and memory 46.
  • the processing circuitry 42 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • processors and/or processor cores and/or FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 44 may be configured to access (e.g., write to and/or read from) memory 46, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 46 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read- Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • Processing circuitry 42 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by host computer 24.
  • Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein.
  • the host computer 24 includes memory 46 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 48 and/or the host application 50 may include instructions that, when executed by the processor 44 and/or processing circuitry 42, causes the processor 44 and/or processing circuitry 42 to perform the processes described herein with respect to host computer 24.
  • the instructions may be software associated with the host computer 24.
  • the software 48 may be executable by the processing circuitry 42.
  • the software 48 includes a host application 50.
  • the host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24.
  • the host application 50 may provide user data which is transmitted using the OTT connection 52.
  • The“user data” may be data and information described herein as implementing the described functionality.
  • the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider.
  • the processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and/or receive from the network node 16 and or the wireless device 22.
  • the processing circuitry 42 of the host computer 24 may include an information unit 54 configured to enable the service provider to provide and/or receive information for controlling UCI prioritization that is described herein.
  • the communication system 10 further includes a network node 16 provided in a communication system 10 and comprising hardware 58 enabling it to communicate with the host computer 24 and with the WD 22.
  • the hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the
  • the radio interface 62 may be formed as or may include, for example, one or more radio frequency (RF) transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the communication interface 60 may be configured to facilitate a connection 66 to the host computer 24.
  • the connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.
  • the hardware 58 of the network node 16 further includes processing circuitry 68.
  • the processing circuitry 68 may include a processor 70 and a memory 72.
  • the processing circuitry 68 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • FPGAs Field Programmable Gate Array
  • ASICs Application Specific Integrated Circuitry
  • the processor 70 may be configured to access (e.g., write to and/or read from) the memory 72, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • volatile and/or nonvolatile memory e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection.
  • the software 74 may be executable by the processing circuitry 68.
  • the processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node 16.
  • Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein.
  • the memory 72 is configured to store data, programmatic software code and/or other information described herein.
  • the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16.
  • processing circuitry 68 of the network node 16 may include indication unit 32 configured to perform the network node methods (such as those described with respect to the flowchart of FIG. 7, for example) as described herein.
  • the communication system 10 further includes the WD 22 already referred to.
  • the WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located.
  • the radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
  • the hardware 80 of the WD 22 further includes processing circuitry 84.
  • the processing circuitry 84 may include a processor 86 and memory 88.
  • the processing circuitry 84 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions.
  • the processor 86 may be configured to access (e.g., write to and/or read from) memory 88, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • memory 88 may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
  • the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22.
  • the software 90 may be executable by the processing circuitry 84.
  • the software 90 may include a client application 92.
  • the client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24.
  • an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24.
  • the client application 92 may receive request data from the host application 50 and provide user data in response to the request data.
  • the OTT connection 52 may transfer both the request data and the user data.
  • the client application 92 may interact with the user to generate the user data that it provides.
  • the processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD 22.
  • the processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein.
  • the WD 22 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein.
  • the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to WD 22.
  • the processing circuitry 84 of the wireless device 22 may include a beta unit 34 configured to perform the WD methods (such as those described with reference to FIG. 8, for example) as described herein.
  • the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 1.
  • the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, 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 the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 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
  • the wireless connection 64 between the WD 22 and the network node 16 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 the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.
  • 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.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 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 48, 90 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors etc.
  • the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22.
  • the cellular network also includes the network node 16 with a radio interface 62.
  • the network node 16 is configured to, and/or the network node’s 16 processing circuitry 68 is configured to perform the functions and/or methods described herein for
  • the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16.
  • the WD 22 is configured to, and/or comprises a radio interface 82 and/or processing circuitry 84 configured to perform the functions and/or methods described herein for
  • FIGS. 1 and 2 show various“units” such as indication unit 32, and beta unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be
  • FIG. 3 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 1 and 2, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 2.
  • the host computer 24 provides user data (Block S100).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 74 (Block S102).
  • the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block S104).
  • the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block S106).
  • the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 74 executed by the host computer 24 (Block s 108).
  • FIG. 4 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 1, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 1 and 2.
  • the host computer 24 provides user data (Block S110).
  • the host computer 24 provides the user data by executing a host application, such as, for example, the host application 74.
  • the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block S 112).
  • the transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the WD 22 receives the user data carried in the transmission (Block S 114).
  • FIG. 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 1, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 1 and 2.
  • the WD 22 receives input data provided by the host computer 24 (Block S 116).
  • the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block S 118).
  • the WD 22 provides user data (Block S120).
  • the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122).
  • client application 92 may further consider user input received from the user.
  • the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124).
  • the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).
  • FIG. 6 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 1, in accordance with one embodiment.
  • the communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 1 and 2.
  • the network node 16 receives user data from the WD 22 (Block S128).
  • the network node 16 initiates transmission of the received user data to the host computer 24 (Block S130).
  • the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block S132).
  • FIG. 7 is a flowchart of an exemplary process of e.g., indication unit 32 in a network node 16 according to some embodiments of the present disclosure.
  • One or more Blocks and/or functions and/or methods performed by the network node 16 may be performed by one or more elements of network node 16 such as by indication unit 32 in processing circuitry 68, processor 70, radio interface 62, etc. according to the example method.
  • the example method includes transmitting (Block S134), such as via indication unit 32, processing circuitry 68, processor 70, and/or radio interface 62, an indication of at least one beta offset value for Uplink Control Information, UCI, the indication of the at least one beta offset value indicating whether to transmit at least one of hybrid automatic repeat request-acknowledgement, HARQ-ACK, and channel state information, CSI, in the UCI.
  • the method includes receiving (Block S136), such as via indication unit 32, processing circuitry 68, processor 70, and/or radio interface 62, a physical uplink channel, the physical uplink channel encoded based at least in part on the indication.
  • receiving the indication of the at least one beta offset value further comprises receiving, such as via indication unit 32, processing circuitry 68, processor 70, and/or radio interface 62, at least one index value corresponding to an entry in a table of beta offset values.
  • the at least one beta offset value defines at least one coding offset for at least one UCI bit relative to a coding of at least one Physical Uplink Shared Channel, PUSCH, data bit.
  • receiving the physical uplink channel further comprises receiving, such as via indication unit 32, processing circuitry 68, processor 70, and/or radio interface 62, PUSCH based at least in part on the indication.
  • the transmitted indication of the at least one beta offset value is based at least in part on whether at least one of the PUSCH, the HARQ-ACK and the CSI corresponds to one of ultra-reliable low latency communications, URLLC, and mobile broadband communications.
  • the at least one beta offset value is to be used for encoding UCI if UCI is multiplexed with the PUSCH.
  • the indication of the at least one beta offset value indicates whether to transmit the at least one of the HARQ-ACK and CSI in the UCI by indicating whether to omit the at least one of the HARQ-ACK and CSI in the UCI.
  • transmitting the indication further comprises transmitting, such as via indication unit 32, processing circuitry 68, processor 70, and/or radio interface 62, the indication of the at least one beta offset value in at least one of downlink control information, DCI, and radio resource control, RRC, signalling.
  • processing circuitry 68 is configured to transmit an indication for controlling uplink control information (UCI) prioritization at the wireless device where the indication indicating whether to omit at least a portion of information in the UCI. In some embodiments, processing circuitry 68 is configured to perform communications with the wireless device based on the indication.
  • UCI uplink control information
  • the indication is an indication of a beta offset for one of hybrid automatic repeat request-acknowledgement (HARQ- ACK) and channel state information (CSI).
  • the information includes hybrid automatic repeat request (HARQ) feedback and channel state information (CSI).
  • FIG. 8 is a flowchart of an exemplary process of e.g., beta unit 34 in a wireless device 22 according to some embodiments of the present disclosure.
  • One or more Blocks and/or functions and/or methods performed by WD 22 may be performed by one or more elements of WD 22 such as by beta unit 34 in processing circuitry 84, processor 86, radio interface 82, etc.
  • the example method includes receiving (Block S134), such as via beta unit 34, processing circuitry 84, processor 86 and/or radio interface 82, an indication of at least one beta offset value for Uplink Control Information, UCI, the indication of the at least one beta offset value indicating whether to transmit at least one of hybrid automatic repeat request-acknowledgement, HARQ-ACK, and channel state information, CSI, in the UCI.
  • the method includes transmitting (Block S136), such as via beta unit 34, processing circuitry 84, processor 86 and/or radio interface 82, an encoded physical uplink channel, the physical uplink channel being encoded based at least in part on the indication.
  • receiving the indication of the at least one beta offset value further comprises receiving, such as via beta unit 34, processing circuitry 84, processor 86 and/or radio interface 82, at least one index value corresponding an entry in a table of beta offset values.
  • the at least one beta offset value defines at least one coding offset for at least one UCI bit relative to a coding of at least one Physical Uplink Shared Channel, PUSCH, data bit.
  • the transmitting the physical uplink channel further comprises transmitting, such as via beta unit 34, processing circuitry 84, processor 86 and/or radio interface 82, PUSCH based at least in part on the indication.
  • the received indication of the at least one beta offset value is based at least in part on whether at least one of the PUSCH, the HARQ-ACK and the CSI corresponds to one of ultra-reliable low latency communications, URLLC, and mobile broadband communications.
  • the at least one beta offset value is to be used for encoding UCI if UCI is multiplexed with the PUSCH.
  • the indication of the at least one beta offset value indicates whether to transmit the at least one of the HARQ-ACK and CSI in the UCI by indicating whether to omit the at least one of the HARQ-ACK and CSI in the UCI.
  • receiving the indication further comprises receiving, such as via beta unit 34, processing circuitry 84, processor 86 and/or radio interface 82, the indication of the at least one beta offset value in at least one of downlink control information, DCI, and radio resource control, RRC, signalling.
  • processing circuitry 84 is configured to receive an indication for controlling uplink control information (UCI) prioritization at the wireless device where the indication indicating whether to omit at least a portion of information in the UCI. In some embodiments, processing circuitry 84 is configured to perform communications with the network node based on the indication.
  • UCI uplink control information
  • the indication is an indication of a beta offset for one of hybrid automatic repeat request-acknowledgement (HARQ- ACK) and channel state information (CSI).
  • the information includes hybrid automatic repeat request (HARQ) feedback and channel state information (CSI).
  • beta-offset indices 16-31 are unused (reserved) for HARQ-ACK while beta-offset indices 19-31 are unused (reserved) for CSI.
  • One of the unused indices may be used or configured to define an “omit” beta-offset value indicating that HARQ-ACK/CSI may not be included in the UCI.
  • index 31 is unused (reserved) in 3GPP Rel-l5 for both and could advantageously be used for this purpose.
  • the wireless device 22 operates using both eMBB and URLLC in UL, while only eMBB in UL.
  • the network or network node 16 may, in this example, configure the wireless device for dynamic indication of beta- factors where the 2-bit beta-offset indicator could be configured to indicate according to Table 3.
  • the beta offset is a beta factor.
  • Table 3 Example of beta-offset indicator configuration where CSI is omitted when URLLC PUSCH is scheduled.
  • the network/network node 16 When the network or network node 16 sends a grant to wireless device 22, the network/network node 16 knows whether the wireless device 22 has a CSI and/or HARQ-ACK pending to be transmitted. If the grant is intended for URLLC data, the PUSCH transmission is scheduled more robustly than if the PUSCH is eMBB. Since all HARQ-ACKs are associated with eMBB, it is desirable that the same reliability holds for the HARQ-ACK irrespectively if PUSCH is eMBB or URLLC. Therefore, a lower beta-offset for HARQ-ACK is indicated when the scheduled PUSCH is for URLLC. In this example, no extra encoding offset is needed for the HARQ-ACK relative to the encoding of PUSCH when PUSCH is intended for URLLC (PUSCH is already targeting a low BLER). However, when CSI is pending and the
  • network/network node 16 schedules PUSCH for URLLC it indicates“1” for the beta- offset indicator that indicate that the CSI beta-offset is“omit”.
  • The“omit” value will be interpreted by the wireless device 22 such that CSI may not be included in UCI.
  • UCI is only sent if there is pending HARQ- ACK.
  • the network or network node 16 may in this example configure the wireless device 22 for dynamic indication of beta- factors where the 2-bit beta-offset indicator could be configured to indicate according to Table 4.
  • Table 4 Example of beta-offset indicator configuration where UCI only contains URLLC HARQ-AKC if URLLC PUSCH is scheduled.
  • a higher beta- offset for the HARQ-ACK is indicated if the HARQ-ACK is URLLC. This means that the HARQ-ACK associated with URLLC may be sent more reliably than if it is associated with eMBB.
  • URLLC PUSCH is scheduled, CSI may not be included in UCI since the CSI beta-offset has value“omit”.
  • the UCI may include HARQ-ACK only if is associated with URLLC where in value“3” for the beta-offset indicator is indicated in the DCI including the grant for the URLLC transmission, but the URLLC HARQ-ACK is however not given extra protection compared to the URLLC PUSCH data.
  • the disclosure describes mechanisms of multiplexing Uplink Control
  • UCI Uplink Information
  • RRC radio resource control
  • beta factor for HARQ- ACK, CSI parts or other possible parts of UCI, as described herein.
  • This new value of beta factor indicates to the wireless device 22 not to multiplex (omit) certain parts of UCI with uplink data.
  • the disclosure also covers cases when UCI belongs to certain type of services or when plurality of UCI instances exist in the system, therefore, the “omit” value of beta- factor can be applied to different parts of any UCI type/instance.
  • a network node configured to communicate with a wireless device (WD), the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to:
  • UCI uplink control information
  • Embodiment A2 The network node of Embodiment Al, wherein the indication is an indication of a beta offset for one of hybrid automatic repeat request- acknowledgement (HARQ-ACK) and channel state information (CSI).
  • HARQ-ACK hybrid automatic repeat request- acknowledgement
  • CSI channel state information
  • Embodiment A3 The network node of Embodiment Al, wherein the information includes hybrid automatic repeat request (HARQ) feedback and channel state information (CSI).
  • HARQ hybrid automatic repeat request
  • CSI channel state information
  • Embodiment B A method implemented in a network node, the method comprising:
  • Embodiment B2 The method of Embodiment B 1, wherein the indication is an indication of a beta offset for one of hybrid automatic repeat request- acknowledgement (HARQ-ACK) and channel state information (CSI).
  • HARQ-ACK hybrid automatic repeat request- acknowledgement
  • CSI channel state information
  • Embodiment B3 The method of Embodiment B 1, wherein the information includes hybrid automatic repeat request (HARQ) feedback and channel state information (CSI).
  • HARQ hybrid automatic repeat request
  • CSI channel state information
  • a wireless device configured to communicate with a network node, the WD configured to, and/or comprising a radio interface and/or processing circuitry configured to:
  • UCI uplink control information
  • Embodiment C2 perform communications with the network node based on the indication.
  • Embodiment C2. The WD of Embodiment Cl, wherein the indication is an indication of a beta offset for one of hybrid automatic repeat request- acknowledgement (HARQ-ACK) and channel state information (CSI).
  • HARQ-ACK hybrid automatic repeat request- acknowledgement
  • CSI channel state information
  • Embodiment C3 The WD of Embodiment Cl, wherein the information includes hybrid automatic repeat request (HARQ) feedback and channel state information (CSI).
  • HARQ hybrid automatic repeat request
  • CSI channel state information
  • Embodiment Dl A method implemented in a wireless device (WD), the method comprising:
  • UCI uplink control information
  • Embodiment D2 The method of Embodiment Dl, wherein the indication is an indication of a beta offset for one of hybrid automatic repeat request- acknowledgement (HARQ-ACK) and channel state information (CSI).
  • HARQ-ACK hybrid automatic repeat request- acknowledgement
  • CSI channel state information
  • Embodiment D3 The method of Embodiment Dl, wherein the information includes hybrid automatic repeat request (HARQ) feedback and channel state information (CSI).
  • HARQ hybrid automatic repeat request
  • CSI channel state information
  • the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a“circuit” or“module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware.
  • the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer.
  • Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
  • These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Java® or C++.
  • the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer.
  • the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.

Landscapes

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

Abstract

L'invention concerne un procédé, un système et un appareil pour des facteurs bêta pour informations de commande de liaison montante (UCI) pour les communications sans fil. Un procédé mis en œuvre dans un dispositif sans fil (WD) comprend la réception d'une indication d'au moins une valeur de décalage bêta pour UCI, l'indication de la ou des valeurs de décalage bêta indiquant s'il faut transmettre un accusé de réception de demande automatique de répétition hybride (HARQ-ACK) et/ou des informations d'état de canal (CSI) dans les UCI ; et l'émission d'un canal de liaison montante physique codé, le canal de liaison montante physique étant codé sur la base, au moins en partie, de l'indication. Un procédé mis en œuvre dans un nœud de réseau comprend l'émission d'une indication d'au moins une valeur de décalage bêta pour UCI ; et la réception d'un canal de liaison montante physique, le canal de liaison montante physique étant codé sur la base, au moins en partie, de l'indication.
PCT/SE2019/050673 2018-08-10 2019-07-05 Facteurs bêta pour informations de commande de liaison montante Ceased WO2020032852A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862717442P 2018-08-10 2018-08-10
US62/717,442 2018-08-10

Publications (1)

Publication Number Publication Date
WO2020032852A1 true WO2020032852A1 (fr) 2020-02-13

Family

ID=67297240

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2019/050673 Ceased WO2020032852A1 (fr) 2018-08-10 2019-07-05 Facteurs bêta pour informations de commande de liaison montante

Country Status (1)

Country Link
WO (1) WO2020032852A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114079967A (zh) * 2020-08-14 2022-02-22 大唐移动通信设备有限公司 上行信道的传输方法、装置、终端及网络侧设备
CN115942481A (zh) * 2021-08-09 2023-04-07 普天信息技术有限公司 一种上行信道复用上行控制信息的方法及系统

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "UCI Transmission for URLLC", vol. RAN WG1, no. Busan, Korea; 20180521 - 20180525, 20 May 2018 (2018-05-20), XP051441232, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN1/Docs/> [retrieved on 20180520] *
FUJITSU: "UCI piggyback on PUSCH with URLLC data", vol. RAN WG1, no. Sanya, China; 20180416 - 20180420, 15 April 2018 (2018-04-15), XP051426235, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN1/Docs/> [retrieved on 20180415] *
HUAWEI ET AL: "Discussion on partially overlapped PUCCH and PUSCH", vol. RAN WG1, no. Athens, Greece; 20180226 - 20180302, 17 February 2018 (2018-02-17), XP051397762, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG1%5FRL1/TSGR1%5F92/Docs/> [retrieved on 20180217] *
OPPO: "Remaining issues on grant free", vol. RAN WG1, no. Sanya, China; 20180416 - 20180420, 15 April 2018 (2018-04-15), XP051426302, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN1/Docs/> [retrieved on 20180415] *
ZTE ET AL: "UCI multiplexing for URLLC", vol. RAN WG1, no. Sanya, China; 20180416 - 20180420, 15 April 2018 (2018-04-15), XP051426461, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings%5F3GPP%5FSYNC/RAN1/Docs/> [retrieved on 20180415] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114079967A (zh) * 2020-08-14 2022-02-22 大唐移动通信设备有限公司 上行信道的传输方法、装置、终端及网络侧设备
CN115942481A (zh) * 2021-08-09 2023-04-07 普天信息技术有限公司 一种上行信道复用上行控制信息的方法及系统

Similar Documents

Publication Publication Date Title
US20240406964A1 (en) Harq handling for single-dci multi-slot scheduling
US11316611B2 (en) Compact downlink control information messages
US12207240B2 (en) Hybrid automatic repeat request (HARQ) feedback for multiple physical downlink shared channel (PDSCH) with downlink (DL) semi-persistent scheduling
EP3963780B1 (fr) Gestion d&#39;informations de commande de liaison montante pour des sous-créneaux
US12349126B2 (en) Pre-emption priority level for uplink control information (UCI) and physical uplink shared channel (PUSCH) conflict resolution
US20230284220A1 (en) Control signalling for a repeated transmission
WO2020067967A1 (fr) Saut de fréquence pour transmission avec de multiples répétitions
US11374718B2 (en) Channel state information reporting without uplink shared channel
EP4014404B1 (fr) Transmission d&#39;informations de commande de liaison montante avec pusch entrant en collision
EP3834338A1 (fr) Informations de commande de liaison descendante (dci) permettant la programmation de multiples blocs de transport (tb)
US20240305417A1 (en) Hybrid automatic repeat request (harq) feedback en-/disabling for multicast
WO2019138079A1 (fr) Autorisations configurées dans des communications en duplex à répartition dans le temps
WO2020032852A1 (fr) Facteurs bêta pour informations de commande de liaison montante
WO2020091669A1 (fr) Configuration d&#39;opportunités de demande de répétition automatique hybride (harq)
US12177020B2 (en) Method to decode uplink control channel for ultra reliable low latency applications
US11804937B2 (en) Physical uplink control channel (PUCCH) resource selection before radio resource control (RRC) configuration
EP4014382A1 (fr) Conception de livre de codes de demande de répétition automatique hybride à programmation semi-persistante

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: 19740089

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: 19740089

Country of ref document: EP

Kind code of ref document: A1