EP3906743A1

EP3906743A1 - Uci on configured grant

Info

Publication number: EP3906743A1
Application number: EP19907588.8A
Authority: EP
Inventors: Jonas FRÖBERG OLSSON; Ying Sun; Alexey SHAPIN; Yufei Blankenship; Majid GERAMI
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2019-01-04
Filing date: 2019-12-30
Publication date: 2021-11-10
Also published as: WO2020141996A1; EP3906743A4

Abstract

A method performed by a wireless device (110) includes receiving at least one configured grant, CG for transmitting on a physical uplink shared channel, PUSCH. The wireless device transmits uplink control information, UCI, on the PUSCH though the wireless device does not have uplink-shared channel, UL-SCH, data to transmit.

Description

UCI ON CONFIGURED GRANT

BACKGROUND

In NR Rel-15, semi-persistent scheduling (SPS) for uplink (UL) comes in two flavors, namely Configured grant Type 1 and Type2. For Type 1, the configured grant is fully Radio Resource Control (RRC) configured. By contrast, Type 2 is partly RRC configured and partly dynamically indicated. The RRC information element for configuration of Configured grant look as follows, see 38.331 Section 6.3.2:

— ASN1START

— TAG-CONFIGUREDGRANTCONFIG-START

ConfiguredGrantConfig ::= SEQUENCE {

frequencyHopping ENUMERATED {model, mode2}

OPTIONAL, — Need S,

eg-DMRS-Configuration DMRS-UplinkConfig,

mcs-Table ENUMERATED {qam256, sparel}

OPTIONAL, -- Need S

mcs-TableTransformPrecoder ENUMERATED {qam256, sparel } OPTIONAL, — Need S

uci-OnPUSCH SetupRelease { CG-UCI-

OnPUSCH } ,

resourceAllocation ENUMERATED {

resourceAllocationTypeO , resourceAllocationTypel ,

dynamicSwitch } ,

rbg-Size ENUMERATED {config2}

OPTIONAL, — Need S

powerControlLoopToUse ENUMERATED {n0, nl}, pO-PUSCH-Alpha PO-PUSCH-AlphaSetld, transformPrecoder ENUMERATED {enabled}

OPTIONAL, — Need S

nrofHARQ-Processes INTEGER (1..16) ,

repK ENUMERATED {nl, n2 , n4, n8}, repK-RV ENUMERATED {sl-0231, s2-0303,

S3-0000} OPTIONAL, — Cond RepK

periodicity ENUMERATED {

sym2, sym7, symlxl4, sym2xl4, sym4xl4, sym5xl4, sym8xl4, syml0xl4, syml6xl4, sym20xl4,

sym32xl4, sym40xl4, sym64xl4, sym80xl4, syml28xl4, syml60xl4, sym256xl4, sym320xl4,

sym512x14,

sym640xl4, syml024xl4,

syml280xl4, sym2560xl4, sym5120xl4,

sym6, symlxl2, sym2xl2, sym4xl2, sym5xl2, sym8xl2, syml0xl2, syml6xl2, sym20xl2, sym32x12, sym40xl2, sym64xl2, sym80xl2, syml28xl2, syml60xl2, sym256xl2, sym320xl2, sym512xl2,

sym640xl2 ,

syml280xl2, sym2560xl2

},

configuredGrantTimer INTEGER (1..64)

OPTIONAL, — Need R

rrc-ConfiguredUplinkGrant SEQUENCE {

timeDomainOffset INTEGER (0..5119), timeDomainAllocation INTEGER (0..15), frequencyDomainAllocation BIT STRING (SIZE(18)), antennaPort INTEGER (0..31), dmrs-Seqlnitialization INTEGER (0..1)

OPTIONAL, -- Cond NoTransformPrecoder precodingAndNumberOfLayers INTEGER

(0..63) ,

srs-Resourcelndicator INTEGER (0..15), mcsAndTBS INTEGER (0..31),

frequencyHoppingOffset INTEGER (1..

maxNrofPhysicalResourceBlocks-1 ) OPTIONAL, -- Need M pathlossReferencelndex INTEGER

(0.. maxNrofPUSCH-Pathlos sReferenceRSs-1 ) ,

}

OPTIONAL — Need R

}

CG-UCI-OnPUSCH ::= CHOICE {

dynamic SEQUENCE (SIZE (1..4)) OF

BetaOffsets ,

semiStatic BetaOffsets

}

— TAG-CONFIGUREDGRANTCONFIG-STOP

— ASN1STOP

The information in rrc-ConfiguredUplinkGrant is Type 1 -specific. For Type 2, corresponding information is provided by configured grant activation Downlink Control Information (DCI). The activation DCI for configured grant is scrambled with Configured Scheduling-Radio Network Temporary Identifier (CS-RNTI). The CG-UCI-OnPUSCH indicate if Uplink Control Information (UCI) coding offsets relative to data for configured grant, which may include beta-offsets, are dynamically indicated or semi-static. For Type 1, beta-offsets shall be semi-static.

UCI such as Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) and Channel State Information (CSI) can be transmitted together with data on the configured grant if higher layers (i.e., Medium Access Control (MAC)_ layer) deliver (to Physical (PHY)) a transport block to be transmitted. Section 6.1.2.3 of 3GPP TS 38.214 states:

The UE shall not transmit anything on the resources configured by

ConfiguredGrantConfig if the higher layers did not deliver a transport block to transmit on the resources allocated for uplink transmission without grant.

In NR Rel-15, a Scheduling Request (SR) is not allowed to be transmitted in UCI on Physical Uplink Shared Channel (PUSCH). In fact, if UE has a PUSCH transmission that overlaps with a Physical Uplink Control Channel (PUCCH) transmission that includes positive SR information, the UE will only send the SR on the PUCCH if the PUSCH transmission is without Uplink-Shared Channel (UL-SCH) (i.e., without data) (See, Section 9 in 3GPP TS 38.213):

If a UE would transmit on a serving cell a PUSCH without UL-SCH that overlaps with a PUCCH transmission on the serving cell that includes positive SR information, the UE does not transmit the PUSCH.

MAC does not deliver a transport block for a configured grant to PHY if there is no data available. More precisely, Section 5.4.3.1.3 of 3GPP TS 38.321 specifies:

The MAC entity shall not generate a MAC PDU for the HARQ entity if the following conditions are satisfied:

the MAC entity is configured with skipUplinkTxDynamic and the grant indicated to the HARQ entity was addressed to a C-RNTI, or the grant indicated to the HARQ entity is a configured uplink grant; and

- there is no aperiodic CSI requested for this PUSCH transmission as

specified in TS 38.212 [9]; and

- the MAC PDU includes zero MAC SDUs; and

- the MAC PDU includes only the periodic BSR and there is no data

available for any LCG, or the MAC PDU includes only the padding BSR. When a transport block for a configured grant is delivered to PHY, HARQ-ACK and/or CSI may be transmitted as UCI on the configured grant resource if timing permits. Section 9.3 of 3 GPP TS 38.213 states:

If a UE has a PUSCH transmission that overlaps with a PUCCH transmission that includes HARQ-ACK information and/or semi-persistent/periodic CSI and the conditions in Subclause 9.2.5 for multiplexing the UCI in the PUSCH are satisfied, the UE multiplexes the HARQ-ACK information and/or the semi- persistent/periodic CSI in the PUSCH.

For DCI formatO l, the UL-SCH indicator field may be used to explicitly indicate to the UE that requested CSI shall be sent without UL-SCH. For example, Section 7.3.1.1.2 of 3GPP TS 38.212 states:

UL-SCH indicator - 1 bit. A value of" 1" indicates UL-SCH shall be transmitted on the PUSCH and a value of "0" indicates UL-SCH shall not be transmitted on the PUSCH. A UE is not expected to receive a DCI format 0 1 with UL-SCH indicator of "0" and CSI request of all zero(s).

Certain problems exist. For example, one problem is, while Rel-15 specification allows UCI on PUSCH without UL-SCH data, this is prohibited for PUSCH of UL configured grant (CG). Forbidden UCI on a Configured Grant PUSCH without UL-SCH data will result in both spectrum and gNB process resources being used inefficiently. The PUSCH spectrum for the CG needs to be reserved for a potential UL PUSCH transmission if there is UL-SCH data and HARQ-ACK and/or CSI may be transmitted as UCI on the configured grant PUSCH resource if timing permits. But also, the PUCCH spectrum also needs to be reserved for the potential transmission of UCI HARQ-ACK and/or CSI if there is no UL-SCH data. Both spectrums are wasted because of this ambiguous behavior. Furthermore, gNB/eNB needs to perform double detection on both PUSCH and PUCCH channel to prepare the potential transmissions. As a result, processing resources are also wasted.

Another problem is that SR is currently not allowed to be multiplexed onto PUSCH; only HARQ-ACK and CSI reports can be multiplexed in a PUSCH. Additionally, PUCCH supports single-port transmission only. Tx diversity schemes for PUCCH have been discussed but are not adopted in Rel-15. Since PUSCH supports multi antenna transmission up to four ports, there may be a pre-coding/beamforming gain by transmitting UCI on PUSCH compared to PUCCH.

SUMMARY

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, according to certain embodiments, a method is provided wherein a wireless device such as a User Equipment, as an example, configured to use CG is further indicated to transmit Uplink Control Information (UCI) comprising one or more of a Scheduling Request (SR), Hybrid Automatic Repeat Request- Acknowledgment (HARQ-ACK) and Channel State Information (CSI) on Physical Uplink Shared Channel (PUSCH) on configured grant resources even if Uplink-Shared Channel (UL-SCH) is not present.

According to certain embodiments, a method by a wireless device is provided. The method includes receiving at least one configured grant for transmitting on a PUSCH. UCI is transmitted on the PUSCH though the wireless device does not have UL-SCH data to transmit.

According to certain embodiments, a wireless device is provided. The wireless device includes processing circuitry configured to receive at least one configured grant for transmitting on a PUSCH and transmit UCI on the PUSCH though the wireless device does not have UL-SCH data to transmit.

According to certain embodiments, a method by a base station is provided. The method includes transmitting, to a wireless device, at least one configured grant for transmitting on a PUSCH. UCI is received on the PUSCH from the wireless device though the wireless device does not have UL-SCH data to transmit.

According to certain embodiments, a base station is provided. The base station includes processing circuitry configured to transmit, to a wireless device, at least one configured grant for transmitting on a PUSCH and receive UCI on the PUSCH from the wireless device though the wireless device does not have UL-SCH data to transmit.

Certain embodiments may provide one or more of the following technical advantages. For example, one technical advantage may be that certain embodiments provide simplified scheduling. Specifically, where wireless devices such as UEs with CG perform all uplink (UL) transmissions on the CG resource(s), the scheduler only need to manage PUSCH resources for UEs scheduled by other means. As another example, a technical advantage may be that certain embodiments use the spectrum more efficiently since the UE only requires reserving PUSCH spectrum to transmit both Uplink-Shared Chanel (UL-SCH) data, Downlink HARQ Acknowledgment/Negative Acknowledgment (DL HARQ A/N) and CSI report. Physical Uplink Control Channel (PUCCH) resources can be used for other UE’s PUCCH/PUSCH transmissions.

Still another advantage may be that UCI transmission may be more reliable due to pre coding/beamforming gain for PUSCH as compared to PUCCH.

As still another example, a technical advantage may be that for a PUSCH of Uplink Configured Grant (UL CG), it may be useful to multiplex SR to PUSCH, where the SR indicates the scheduling request of dynamically scheduled UL data. This need exists whenever the UE has simultaneous periodic and aperiodic UL traffic. Here both the periodic and aperiodic traffic can be Enhanced Mobile BroadBand (eMBB) or Ultra-reliable low latency communication (URLLC) traffic.

Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

FIGURE 1 illustrates an example wireless network, according to certain embodiments;

FIGURE 2 illustrates an example network node, according to certain embodiments;

FIGURE 3 illustrates an example wireless device, according to certain embodiments;

FIGURE 4 illustrate an example user equipment, according to certain embodiments;

FIGURE 5 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments;

FIGURE 6 illustrates a telecommunication network connected via an intermediate network to a host computer, according to certain embodiments;

FIGURE 7 illustrates a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments;

FIGURE 8 illustrates a method implemented in a communication system, according to one embodiment;

FIGURE 9 illustrates another method implemented in a communication system, according to one embodiment;

FIGURE 10 illustrates another method implemented in a communication system, according to one embodiment;

FIGURE 11 illustrates another method implemented in a communication system, according to one embodiment;

FIGURE 12 illustrates an example method by a wireless device, according to certain embodiments;

FIGURE 13 illustrates an exemplary virtual computing device, according to certain embodiments;

FIGURE 14 illustrates another example method by a wireless device, according to certain embodiments;

FIGURE 15 illustrates another exemplary virtual computing device, according to certain embodiments;

FIGURE 16 illustrates an example method by a network node, according to certain embodiments;

FIGURE 17 illustrates another exemplary virtual computing device, according to certain embodiments;

FIGURE 18 illustrates another example method by a network node, according to certain embodiments; and

FIGURE 19 illustrates another exemplary virtual computing device, according to certain embodiments.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

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

In some embodiments, a more general term“network node” may be used and may correspond to any type of radio network node or any network node, which communicates with a UE (directly or via another node) and/or with another network node. Examples of network nodes are NodeB, MeNB, ENB, a network node belonging to MCG or SCG, base station (BS), multi -standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. MSC, MME, etc), O&M, OSS, SON, positioning node (e.g. E-SMLC), MDT, test equipment (physical node or software), etc.

In some embodiments, the non-limiting term user equipment (UE) or wireless device may be used and may refer to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, UE category Ml, UE category M2, ProSe UE, V2V UE, V2X UE, etc.

Additionally, terminologies such as base station/gNodeB and UE should be considered non-limiting and do in particular not imply a certain hierarchical relation between the two; in general,“gNodeB” could be considered as device 1 and“UE” could be considered as device 2 and these two devices communicate with each other over some radio channel. And in the following the transmitter or receiver could be either gNB, or UE.

UCI on UL CG PUSCH without Data

According to certain embodiments, the information element for configured grant (CG) comprises:

- ASN1 START

- TAG-CONFIGUREDGRANTCONFIG-START

ConfiguredGrantConfig ::= SEQUENCE {

frequencyHopping ENUMERATED {model, mode2}

OPTIONAL, — Need S,

cg-DMRS -C onfiguration DMRS -UplinkC onfig,

mcs-Table ENUMERATED {qam256, sparel}

OPTIONAL, - Need S

mcs-TableTransformPrecoder ENUMERATED {qam256, sparel}

OPTIONAL, - Need S

uci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH }, resourceAllocation ENUMERATED { resourceAllocationTypeO, resourceAllocationTypel, dynamicSwitch },

rbg-Size ENUMERATED {config2}

OPTIONAL, - Need S

powerControlLoopToUse ENUMERATED {n0, nl},

pO-PU SCH-Alpha PO-PUSCH-AlphaSetld,

transformPrecoder ENUMERATED {enabled}

OPTIONAL, - Need S

nrofHARQ-Processes INTEGER(1. 16),

repK ENUMERATED {n 1 , n2, n4, n8 } ,

repK-RV ENUMERATED {sl-0231, s2-0303, s3-

0000} OPTIONAL, - Cond RepK

periodicity ENUMERATED {

sym32xl4, sym40xl4, sym64xl4, sym80xl4, syml28xl4, syml60xl4, sym256xl4, sym320xl4, sym512x14,

sym640xl4, syml024xl4, syml280xl4, sym2560xl4, sym5120xl4, sym6, symlxl2, sym2xl2, sym4xl2, sym5xl2, sym8xl2, syml0xl2, syml6xl2, sym20xl2, sym32xl2,

sym40xl2, sym64xl2, sym80xl2, syml28xl2, syml 60x12, sym256xl2, sym320xl2, sym512xl2, sym640xl2,

syml280xl2, sym2560xl2

} ,

configuredGrantTimer INTEGER (1..64)

OPTIONAL, - Need R

uciWitoutUL-SCH BOOLEAN OPTIONAL, - Need R rrc-ConfiguredUplinkGrant SEQUENCE {

timeDomainOffset INTEGER (0..5119),

timeDomainAllocation INTEGER (0..15),

frequencyDomainAllocation BIT STRING (SIZE(18)),

antennaPort INTEGER (0..31),

dmrs-Seqlnitialization INTEGER (0..1)

OPTIONAL, — Cond NoTransformPrecoder

precodingAndNumberOfLayers INTEGER (0..63),

srs-Resourcelndicator INTEGER (0..15),

mcsAndTBS INTEGER (0..31),

frequencyHoppingOffs et INTEGER (1..

maxNrofPhysicalResourceBlocks-1) OPTIONAL, - Need M

pathlossReferencelndex INTEGER (O. maxNrofPUSCH- PathlossReferenceRSs-1),

OPTIONAL— Need R

}

CG-UCI-OnPUSCH ::= CHOICE {

dynamic SEQUENCE (SIZE (1..4)) OF BetaOffsets, semiStatic BetaOffsets

}

- TAG-CONFIGUREDGRANTCONFIG-STOP

- ASN1STOP

If uciWoithoutUL-SCH is set to true, UE may send UCI on PUSCH without UL-SCH on a CG resource. The text in Section 6.1.2.3 of 3GPP TS 38.214 may be modified as highlighted:

The UE shall not transmit anything on the resources configured by ConfiguredGrantConflg if uciWithoutUL-SCH is false and if the higher layers did not deliver a transport block to transmit on the resources allocated for uplink transmission without grant. Also the text in Section 5.4.3.1.3 of 3GPP TS 38.321 may be modified as highlighted: The MAC entity shall not generate a MAC PDU for the HARQ entity if the following conditions are satisfied:

the MAC entity is configured with skipUplinkTxDynamic and uciWithoutUL- SCH is false and the grant indicated to the HARQ entity was addressed to a C- RNTI, or the grant indicated to the HARQ entity is a configured uplink grant; and

- there is no aperiodic CSI requested for this PUSCH transmission as specified in TS 38.212 [9]; and

- the MAC PDU includes zero MAC SDUs; and

- the MAC PDU includes only the periodic BSR and there is no data available for any LCG, or the MAC PDU includes only the padding BSR.

According to a particular embodiment for Type 2 configured grant, UE may be indicated whether UCI on configured grant PUSCH is allowed is semi-persistently indicated to UE in activation DCI. In DCI format 0 1 the field“UL-SCH indicator” may indicate:

Value “0”: “UCI without UL-SCH on configured grant resource is allowed”

Value“1”:“UCI without UL-SCH on configured grant resource is not allowed

According to another particular embodiment for Type 2 CG, Radio Resource Control Information Element (RRC IE) ConfiguredGrantConfig may comprise uciWithoutUL-SCH, which is used together with semi-persistent indication using the DCI field“UL-SCH indicator” in the activation DCI. In such embodiments,

• uciWithoutUL-SCH=true indicates the UCI on PUSCH without UL- SCH is allowed while“UL-SCH indicator” in activation DCI may indicate different allowed combinations of UCI contents that are allowed on configured grant resource without UL-SCH. For example, o if CSI request field is not all zero the“UL-SCH indicator” may indicate:

Value“0”:“UCI comprising SR and/or HARQ-ACK and CSI on configured grant resource is allowed”

Value “1”: “UCI comprising SR and/or HARQ-ACK on configured grant resource is allowed” o if CSI request field is all zero the“UL-SCH indicator” may indicate:

Value “0”: “UCI comprising SR and/or HARQ-ACK on configured grant resource is allowed”

Value“1”:“UCI comprising HARQ-ACK on configured grant resource is allowed”

• uciWithoutUL-SCH=false indicates that the UCI on PUSCH without UL-SCH is not allowed. In this case, the field“UL-SCH indicator” in activation DCI is reserved.

In a particular embodiment, the CSI request field may not be all zero, indicating a request for the UE to transmit CSI. If CSI request field indicates a CSI trigger state with a semi-persistent CSI configuration then a value“0” may indicate that UCI with the semi- persistent CSI corresponding the indicated trigger state is allowed to be sent on configured grant resource without UL-SCH; otherwise it is not allowed. In such examples, uciWithoutUL- SCH in ConfiguredGrantConfig may indicate that SR and/or HARQ-ACK and/or periodic CSI is allowed on configured grant resource without UL-SCH while“UL-SCH indicator” together with CSI request field in activation DCI of the configured grant may indicate whether or not additionally semi-persistent CSI may be comprised in UCI on PUSCH without UL-SCH on the configured grant resource.

Multiplexing SR on PUSCH (both dynamic and CG based)

Currently NR Rel-15 does not allow SR to be multiplexed onto PUSCH. Only HARQ-ACK and CSI reports can be multiplexed in a PUSCH. For a PUSCH of UL CG, it is useful to multiplex SR to PUSCH, where the SR indicates the scheduling request of dynamically scheduled UL data. This need exists whenever the UE has simultaneous periodic and aperiodic UL traffic. Here both the periodic and aperiodic traffic can be eMBB or URLLC traffic.

The following revision to Section“9.3 UCI reporting in physical uplink shared channel” of 3GPP TS 38.213 provides beta offset for SR, when the SR is multiplexed onto PUSCH. The higher layer parameter betaOffsetSR can be added to RRC IE PUSCH- Config, in which case betaOffsetSR is applicable to both dynamically scheduled PUSCH and UL CG PUSCH. Alternatively, higher layer parameter betaOffsetSR can be added to RRC IE ConfiguredGrantConfig so that it is applicable to UL CG PUSCH only.

Start of edits to TS 38.213 Offset values are defined for a UE to determine a number of resources for multiplexing SR, HARQ-ACK information and for multiplexing CSI reports in a PUSCH. The offset values are signalled to a UE either by a DCI format scheduling the PUSCH transmission or by higher layers.

If DCI format 0 0, or DCI format 0 1 that does not include a beta offset indicator field, schedules the PUSCH transmission from the UE, the UE applies the S_0¾et

corresponding SR, HARQ-ACK information, Part 1 CSI reports and Part 2 CSI reports.

SR offset S_0¾et is configured to values according to Table 9.3-1. Higher layer parameter betaOffsetSR provides index 7^® _set for the UE to use if the UE multiplexes SR onto PUSCH.

If a DCI format 0 1 schedules the PUSCH transmission from the UE and if DCI format 0_1 includes a beta_offset indicator field, as configured by uci-OnPUSCH, the UE is provided by betaOffsetSR a set of four 7₀ ^® _et indexes, by each of

{betaOffsetACK-Indexl , betaOffsetACK-Index2, betaOffsetACK-Index3 } a set of four indexes, by each of {betaOffsetCSI-Partl -Index 7, betaOffsetCSI-Partl- Index2 } a set of four iff indexes and by each of {betaOffs etCSI-P art 2-Index 1 , betaOffsetCSI-Part2-Index2} a set of four iff indexes from Table 9.3-1 and 9.3-2, respectively, for multiplexing HARQ-ACK information, Part 1 CSI reports, and Part 2 CSI reports, respectively, in the PUSCH transmission. The beta offset indicator field indicates a ^ACK value, a iff value and a iff value from the respective sets of values, with the mapping defined in Table 9.3-3.

TS 38.213, Table 9.3-1: Mapping of beta offset values for HARQ-ACK information and the index signalled by higher layers

TS 38.213, Table 9.3-3: Mapping of betajolfset indicator values to offset indexes

End of edits to TS 38.213

The solutions described herein are applicable for multiple CG configurations, where uciWithoutUL-SCH can be configured for one or plurality of ConfiguredGrctntConfig. According to various embodiments, different rules can be applied to choose one transmission opportunity, e.g. first or last transmission opportunity in the slot, other conditions are not precluded.

In a particular embodiment, the gNb may avoid inter UE pre-emption or multiplexing if there is a possibility of sending UCI in PUSCH, because UCI reliability must be ensured. This may be done by a scheduler, and no standard change required. However, it may be beneficial for the UE if the network cannot expect inter UE pre emption for this transmission.

In another particular embodiment, if uciWithoutUL-SCH is true and transport block repetition with a configured grant is activated by higher layer parameters repK and repK-RV, and there is no data in UE buffer to transmit, then UE may send UCI on PUSCH without UL-SCH on configured grant resource only once, i.e., there would not be repetition for UCI.

In another particular embodiment, if uciWithoutUL-SCH is true and repetition for UCI is allowed by higher layer parameter, for example rep_UCI_K>l, and transport block repetition with a CG is activated by higher layer parameters repK > = rep JCI K, and there is no data in UE buffer to transmit, then UE is allowed to send UCI on PUSCH without UL-SCH on configured grant resource repJJCI K times.

FIGURE 1 illustrates a wireless network, in accordance with some embodiments. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIGURE 1. For simplicity, the wireless network of FIGURE 1 only depicts network 106, network nodes 160 and 160b, and wireless devices 110, 110b, and 110c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 160 and wireless device (wireless device) 110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 160 and wireless device 110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

FIGURE 2 illustrates an example network node, according to certain embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In FIGURE 2, network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Although network node 160 illustrated in the example wireless network of FIGURE 1 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 160 may be composed of multiple physically separate components (e.g., aNodeB component and aRNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.

Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality. For example, processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system on a chip (SOC).

In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160 but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.

Device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 170. Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160. Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190. In some embodiments, processing circuitry 170 and device readable medium 180 may be considered to be integrated.

Interface 190 is used in the wired or wireless communication of signalling and/or data between network node 160, network 106, and/or wireless devices 110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162. Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170. Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 may be considered a part of interface 190. In still other embodiments, interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.

Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160. For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187. As a further example, power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node 160 may include additional components beyond those shown in FIGURE 2 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject maher described herein. For example, network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

FIGURE 3 illustrates an example wireless device, according to certain embodiments. As used herein, wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term wireless device may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a wireless device may be configured to transmit and/or receive information without direct human interaction. For instance, a wireless device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a wireless device include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle-mounted wireless terminal device, etc. A wireless device may support device- to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to- everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a wireless device may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another wireless device and/or a network node. The wireless device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the wireless device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a wireless device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A wireless device as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a wireless device as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137. Wireless device 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by wireless device 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within wireless device 110.

Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from wireless device 110 and be connectable to wireless device 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a wireless device. Any information, data and/or signals may be received from a network node and/or another wireless device. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface.

As illustrated, interface 114 comprises radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116. Radio front end circuitry 114 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 may be coupled to or a part of antenna 111. In some embodiments, wireless device 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered a part of interface 114. Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other wireless device 110 components, such as device readable medium 130, wireless device 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.

As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 120 of wireless device 110 may comprise a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 122 may be a part of interface 114. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.

In certain embodiments, some or all of the functionality described herein as being performed by a wireless device may be provided by processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of wireless device 110, but are enjoyed by wireless device 110 as a whole, and/or by end users and the wireless network generally.

Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a wireless device. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120. Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non- transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120. In some embodiments, processing circuitry 120 and device readable medium 130 may be considered to be integrated.

User interface equipment 132 may provide components that allow for a human user to interact with wireless device 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to wireless device 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in wireless device 110. For example, if wireless device 110 is a smart phone, the interaction may be via a touch screen; if wireless device 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into wireless device 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from wireless device 110, and to allow processing circuitry 120 to output information from wireless device 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, wireless device 110 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein. Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by wireless devices. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario.

Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used wireless device 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of wireless device 110 which need power from power source 136 to carry out any functionality described or indicated herein. Power circuitry 137 may in certain embodiments comprise power management circuitry. Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case wireless device 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of wireless device 110 to which power is supplied.

FIGURE 4 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 2200 may be any UE identified by the 3^rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 200, as illustrated in FIGURE 4, is one example of a wireless device configured for communication in accordance with one or more communication standards promulgated by the 3^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term wireless device and UE may be used interchangeable. Accordingly, although FIGURE 4 is a UE, the components discussed herein are equally applicable to a wireless device, and vice- versa.

In FIGURE 4, UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 233, and/or any other component, or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Certain UEs may utilize all of the components shown in FIGURE 4, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In FIGURE 4, processing circuitry 201 may be configured to process computer instructions and data. Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 200 may be configured to use an output device via input/output interface 205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence- sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In FIGURE 4, RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 211 may be configured to provide a communication interface to network 243a. Network 243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243a may comprise a Wi-Fi network. Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227. Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems. Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium.

In FIGURE 4, processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231. Network 243a and network 243b may be the same network or networks or different network or networks. Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b. For example, communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another wireless device, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 200 or partitioned across multiple components of UE 200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 may be configured to include any of the components described herein. Further, processing circuitry 201 may be configured to communicate with any of such components over bus 202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIGURE 5 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 300, comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360. Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and/or instructions executable by processing circuitry 360. Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.

During operation, processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.

As shown in FIGURE 5, hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine 340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 340, and that part of hardware 330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/ or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 340 on top of hardware networking infrastructure 330 and corresponds to application 320 in FIGURE 5.

In some embodiments, one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225. Radio units 3200 may communicate directly with hardware nodes 330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signaling can be affected with the use of control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.

FIGURE 6 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

With reference to FIGURE 6, in accordance with an embodiment, a communication system includes telecommunication network 410, such as a 3GPP-type cellular network, which comprises access network 411, such as a radio access network, and core network 414. Access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c is connectable to core network 414 over a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c. A second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 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 412.

Telecommunication network 410 is itself connected to host computer 430, 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 430 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 421 and 422 between telecommunication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go via an optional intermediate network 420. Intermediate network 420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 420, if any, may be a backbone network or the Internet; in particular, intermediate network 420 may comprise two or more sub-networks (not shown).

The communication system of FIGURE 6 as a whole enables connectivity between the connected UEs 491, 492 and host computer 430. The connectivity may be described as an over-the-top (OTT) connection 450. Host computer 430 and the connected UEs 491, 492 are configured to communicate data and/or signaling via OTT connection 450, using access network 411, core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries. OTT connection 450 may be transparent in the sense that the participating communication devices through which OTT connection 450 passes are unaware of routing of uplink and downlink communications. For example, base station 412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, base station 412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 491 towards the host computer 430.

FIGURE 7 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIGURE 7. In communication system 500, host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 500. Host computer 510 further comprises processing circuitry 518, which may have storage and/or processing capabilities. In particular, processing circuitry 518 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 510 further comprises software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518. Software 511 includes host application 512. Host application 512 may be operable to provide a service to a remote user, such as UE 530 connecting via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the remote user, host application 512 may provide user data which is transmitted using OTT connection 550.

Communication system 500 further includes base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with host computer 510 and with UE 530. Hardware 525 may include communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 500, as well as radio interface 527 for setting up and maintaining at least wireless connection 570 with UE 530 located in a coverage area (not shown in FIGURE 7) served by base station 520. Communication interface 526 may be configured to facilitate connection 560 to host computer 510. Connection 560 may be direct or it may pass through a core network (not shown in FIGURE 7) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 525 of base station 520 further includes processing circuitry 528, 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 520 further has software 521 stored internally or accessible via an external connection.

Communication system 500 further includes UE 530 already referred to. Its hardware 535 may include radio interface 537 configured to set up and maintain wireless connection 570 with a base station serving a coverage area in which UE 530 is currently located. Hardware 535 of UE 530 further includes processing circuitry 538, 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 530 further comprises software 531, which is stored in or accessible by UE 530 and executable by processing circuitry 538. Software 531 includes client application 532. Client application 532 may be operable to provide a service to a human or non-human user via UE 530, with the support of host computer 510. In host computer 510, an executing host application 512 may communicate with the executing client application 532 via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the user, client application 532 may receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 may transfer both the request data and the user data. Client application 532 may interact with the user to generate the user data that it provides.

It is noted that host computer 510, base station 520 and UE 530 illustrated in FIGURE 7 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of FIGURE 6, respectively. This is to say, the inner workings of these entities may be as shown in FIGURE 7 and independently, the surrounding network topology may be that of FIGURE 6.

In FIGURE 7, OTT connection 550 has been drawn abstractly to illustrate the communication between host computer 510 and UE 530 via base station 520, 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 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection 570 between UE 530 and base station 520 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 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings 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, and/or 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 550 between host computer 510 and UE 530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 550 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 511, 531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 550 may include message format, retransmission settings, preferred routing etc. ; the reconfiguring need not affect base station 520, and it may be unknown or imperceptible to base station 520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 510’ s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 511 and 531 causes messages to be transmitted, in particular empty or‘dummy’ messages, using OTT connection 550 while it monitors propagation times, errors etc.

FIGURE 8 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 6 and 7. For simplicity of the present disclosure, only drawing references to FIGURE 8 will be included in this section. In step 610, the host computer provides user data. In substep 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIGURE 9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 6 and 7. For simplicity of the present disclosure, only drawing references to FIGURE 9 will be included in this section. In step 710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

FIGURE 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 6 and 7. For simplicity of the present disclosure, only drawing references to FIGURE 10 will be included in this section. In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In substep 821 (which may be optional) of step 820, the UE provides the user data by executing a client application. In substep 811 (which may be optional) of step 810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 830 (which may be optional), transmission of the user data to the host computer. In step 840 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.

FIGURE 11 is a flowchart illustrating a method 1000 implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 6 and 7. For simplicity of the present disclosure, only drawing references to FIGURE 11 will be included in this section. In step 910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

FIGURE 12 depicts a method by a wireless device, according to certain embodiments. At step 1002, the wireless device receives at least one grant for transmitting on a PUSCH. At step 1004, the wireless device transmits UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.

In a particular embodiment, for example, the at least one grant includes an indicator indicating that the wireless device is to transmit the UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit. In a particular embodiment, the wireless device may determine that the wireless device does not have UL-SCH data to transmit and, based on the indicator, determine that the wireless device is allowed to transmit UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit. In a particular embodiment, the UCI may include at least one of a SR, a HARQ-ACK, and CSI.

FIGURE 13 illustrates a schematic block diagram of a virtual apparatus 1100 in a wireless network (for example, the wireless network shown in FIGURE 1). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 1). Apparatus 1100 is operable to carry out the example method described with reference to FIGURE 12 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 12 is not necessarily carried out solely by apparatus 1100. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1100 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving module 1110, transmitting module 1120, and any other suitable units of apparatus 1100 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, receiving module 1110 may perform certain of the receiving functions of the apparatus 1100. For example, receiving module 1110 may receive at least one grant for transmitting on a PUSCH.

According to certain embodiments, transmitting module 1120 may perform certain of the transmitting functions of the apparatus 1100. For example, transmitting module 1120 may transmit UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein. FIGURE 14 depicts a method 1200 by a wireless device 110, according to certain embodiments. At step 1202, wireless device 110 receives at least one CG for transmitting on a PUSCH. At step 1204, the wireless device 110 transmits UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.

In a particular embodiment, the at least one CG comprises an indicator indicating that the wireless device 110 is to transmit the UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit. In a further particular embodiment, the wireless device 110 determines that the wireless device 110 does not have UL-SCH data to transmit and, based on the indicator, determines that the wireless device 110 is allowed to transmit UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.

In a further particular embodiment, the indicator comprises a uciWithoutUL-SCH indicator and the indicator is set to true.

In a particular embodiment, the UCI includes at least channel state information (CSI). Additionally or alternatively, in a particular embodiment, the UCI includes at least one of a SR and a HARQ-ACK.

In a particular embodiment, the at least one CG comprises a Type 1 configured grant.

In another particular embodiment, the at least one CG comprises a Type 2 configured grant.

In a particular embodiment, the wireless device 110 receives an indicator with an activation of DCI. The indicator indicates that the wireless device 110 is to transmit the UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit. In a further particular embodiment, the indicator is indicated to and received by the wireless device, and wherein the indicator is received as a RRC IE.

In a particular embodiment, wireless device 110 determines, based on the indicator, a type of UCI that the wireless device is permitted to transmit even though the wireless device does not have UL-SCH data to transmit, and the type of UCI includes at least one of a SR, a HARQ-ACK, and CSI.

In a particular further embodiment, the indicator is a value of 0 and not all of the fields in a CSI request are set to zero, and the wireless device 110 determines that wireless device 110 is permitted to send SR and/or HARQ-ACK and CSI on the PUSCH using at least one resource indicated in the at least one grant.

In another particular embodiment, the indicator is a value of 1 and not all of the fields in a CSI request are set to zero, and wireless device 110 determines that the wireless device 110 is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.

In another particular embodiment, the indicator is a value of 0 and all of the fields in a CSI request are set to zero, and wireless device 110 determines that the wireless device 110 is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.

In another particular embodiment, the indicator is a value of 1 and all of the fields in a CSI request are set to zero, and wireless device 110 determines that wireless device 110 is permitted to send HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.

In a particular embodiment, the UCI is multiplexed onto the PUSCH based on at least one beta offset parameter. In a further particular embodiment, the beta offset parameter is received as a radio resource control information element associated with a PUSCH configuration.

In a particular embodiment, the at least one CG comprises a plurality of CGs and the indicator applies to the plurality of CGs.

In a particular embodiment, wireless device 110 determines that only a single transmission of the UCI is allowed on the PUSCH without UL-SCH data even where a repetition parameter is set to allow repetitions of UL-SCH data.

In a particular embodiment, wireless device 110 determines that repetition of UCI is permitted a first number of times, determines that repetition of UL-SCH data is permitted a second number of times, determines that the second number of times is greater or equal to the first number of times, and transmits the UCI on the PUSCH without UL-SCH data the first number of times.

FIGURE 15 illustrates a schematic block diagram of a virtual apparatus 1300 in a wireless network (for example, the wireless network shown in FIGURE 1). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 1). Apparatus 1300 is operable to carry out the example method described with reference to FIGURE 14 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 14 is not necessarily carried out solely by apparatus 1300. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1300 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving module 1310, transmitting module 1320, and any other suitable units of apparatus 1300 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, receiving module 1310 may perform certain of the receiving functions of the apparatus 1300. For example, receiving module 1310 may receive at least one CG for transmitting on a PUSCH.

According to certain embodiments, transmitting module 1320 may perform certain of the transmitting functions of the apparatus 1300. For example, transmitting module 1320 may transmit UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

FIGURE 16 depicts a method 1400 by a network node 160, according to certain embodiments. At step 1402, the network node transmits, to a wireless device, at least one grant for transmitting on a PUSCH. At step 1404, the network node receives, from the wireless device, UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.

In a particular embodiment, the network node may include a base station.

In a particular embodiment, the at least one grant includes an indicator indicating that the wireless device is to transmit the UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit and receiving the UCI on the PUSCH comprises receiving the UCI on the PUSCH without any UL-SCH.

In a particular embodiment, the network node may transmit an indicator to the wireless device to permit transmissions of the UCI on the PUSCH without UL-SCH data. In a particular embodiment, the UCI may include at least one of a SR, a HARQ-ACK, and CSI.

FIGURE 17 illustrates a schematic block diagram of a virtual apparatus 1500 in a wireless network (for example, the wireless network shown in FIGURE 1). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 1). Apparatus 1500 is operable to carry out the example method described with reference to FIGURE 16 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 16 is not necessarily carried out solely by apparatus 1500. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause transmitting module 1510, receiving module 1520, and any other suitable units of apparatus 1300 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, transmitting module 1510 may perform certain of the transmitting functions of the apparatus 1500. For example, transmitting module 1510 may transmit, to a wireless device, at least one grant for transmitting on a PUSCH.

According to certain embodiments, receiving module 1520 may perform certain of the receiving functions of the apparatus 1500. For example, receiving module 1520 may receive, from the wireless device, UCI on the PUSCH even if the wireless device does not have UL- SCH data to transmit.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein. FIGURE 18 depicts a method 1600 by a network node 160 such as, for example, a base station, according to certain embodiments. At step 1602, the network node 160 transmits, to a wireless device 110, at least one CG for transmitting on a PUSCH. At step 1604, network node 160 receives, from wireless device 110, UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.

In a particular embodiment, the at least one CG includes an indicator indicating that the wireless device 110 is to transmit the UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.

In a particular embodiment, receiving the UCI on the PUSCH comprises receiving the UCI on the PUSCH without any UL-SCH.

In a particular embodiment, network node 160 transmits the indicator to the wireless device to permit transmissions of the UCI on the PUSCH without UL-SCH data.

In a particular embodiment, the UCI comprises at least CSI. Additionally or alternatively, the UCI may include at least one of a SR and HARQ-ACK.

In a particular embodiment, the at least one CG comprises a Type 1 CG.

In a particular embodiment, the at least one CG comprises a Type 2 CG.

In a particular embodiment, network node 160 transmits an indicator with an activation of DCI. The indicator indicates that wireless device 110 is permitted to transmit the UCI on the PUSCH without UL-SCH data. In a further particular embodiment, the indicator is indicated to wireless device 110, and the indicator is transmitted as a RRC IE.

In a particular embodiment, the indicator indicates a type of UCE that the wireless device is permitted to transmit without UL-SCH data, and the type of UCI includes at least one of a SR, a HARQ-ACK, and CSI.

In a particular embodiment, the indicator is a value of 0 and not all of the fields in a CSI request are set to zero, and wireless device 110 is permitted to send SR and/or HARQ- ACK and CSI on the PUSCH using at least one resource indicated in the at least one CG.

In another particular embodiment, the indicator is a value of 1 and not all of the fields in a CSI request are set to zero, and wireless device 110 is permitted to send SR and/or HARQ- ACK on the PUSCH using at least one resource indicated in the at least one CG.

In another particular embodiment, the indicator is a value of 0 and all of the fields in a CSI request are set to zero, and wireless device 110 is permitted to send SR and/or HARQ- ACK on the PUSCH using at least one resource indicated in the at least one CG. In a particular embodiment, the indicator is a value of 1 and all of the fields in a C SI request are set to zero, and wireless device 110 is permitted to send HARQ-ACK on the PUSCH using at least one resource indicated in the at least one CG.

In a particular embodiment, the UCI is multiplexed onto the PUSCH based on at least one beta offset parameter. In a further particular embodiment, network node 160 transmits, to the wireless device 110, the at least one beta offset parameter as a radio resource control information element associated with a PUSCH configuration.

In a particular embodiment, only a single transmission of the UCI is allowed on the PUSCH without UL-SCH data even where a repetition parameter is set to allow repetitions of UL-SCH data.

In a particular embodiment, repetition of UCI is permitted a first number of times, and repetition of UL-SCH data is permitted a second number of times. The second number of times is greater or equal to the first number of times, and the UCI is received on the PUSCH without UL-SCH data the first number of times.

FIGURE 19 illustrates a schematic block diagram of a virtual apparatus 1700 in a wireless network (for example, the wireless network shown in FIGURE 1). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 1). Apparatus 1700 is operable to carry out the example method described with reference to FIGURE 18 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 18 is not necessarily carried out solely by apparatus 1700. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause transmitting module 1710, receiving module 1720, and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, transmitting module 1710 may perform certain of the transmitting functions of the apparatus 1700. For example, transmitting module 1710 may transmit, to a wireless device 110, at least one CG for transmitting on a PUSCH.

According to certain embodiments, receiving module 1720 may perform certain of the receiving functions of the apparatus 1700. For example, receiving module 1720 may receive, from wireless device 110, UCI on the PUSCH though the wireless device 110 does not have UL-SCH data to transmit.

EXAMPLE EMBODIMENTS

Example Embodiment 1. A method performed by a wireless device, the method comprising: receiving at least one grant for transmitting on a physical uplink shared channel (PUSCH); and transmitting uplink control information (UCI) on the PUSCH even if the wireless device does not have uplink-shared channel (UL-SCH) data to transmit.

Example Embodiment 2. The method of Embodiment 1, wherein the at least one grant comprises an indicator indicating that the wireless device is to transmit the UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.

Example Embodiment 3. The method of Embodiment 2, further comprising: determining that the wireless device does not have UL-SCH data to transmit; and based on the indicator, determining that the wireless device is allowed to transmit UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.

Example Embodiment 4. The method of any one of Embodiments 2 to 3, wherein the indicator comprises a uciWithoutUL-SCH indicator and wherein the is set to true.

Example Embodiment 5. The method of any one of Embodiments 1 to 4, wherein the UCI comprises at least one of: a scheduling request (SR); a hybrid automatic repeat request acknowledgement (HARQ-ACK); and channel state information (CSI). Example Embodiment 6. The method of any one of Embodiments 1 to 5, wherein the at least one grant indicates an allocation of at least one resource for transmitting on the PUSCH, and the UCI is transmitted on the PUSCH using the at least one resource.

Example Embodiment 7. The method of any one of Embodiments 1 to 6, wherein the at least one grant comprises a Type 1 configured grant.

Example Embodiment 8. The method of any one of Embodiments 1 to 6, wherein the at least one grant comprises a Type 2 configured grant.

Example Embodiment 9. The method of Embodiment 8, further comprising receiving an indicator with an activation of downlink control information (DCI), the indicator indicating that the wireless device is to transmit the UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit.

Example Embodiment 10. The method of Embodiment 9, wherein the indicator is semi-persistently indicated to and received by the wireless device.

Example Embodiment 11. The method of Embodiment 9, wherein the indicator is received as a radio resource control information element (RRC IE).

Example Embodiment 12. The method of any one of Embodiments 10 to 11, further comprising: determining, based on the indicator, a type of UCI that the wireless device is permitted to transmit even if the wireless device does not have uplink-shared channel (UL- SCH) data to transmit.

Example Embodiment 13. The method of Embodiment 12, wherein the type of UCI comprises at least one of a scheduling request (SR), a hybrid automatic repeat request acknowledgement (HARQ-ACK), and channel state information (CSI).

Example Embodiment 14. The method of Embodiment 13, wherein, when the indicator is a value of 0 and not all of the fields in a CSI request are set to zero, the wireless device determines that it is permitted to send SR and/or HARQ-ACK and CSI on the PUSCH using at least one resource indicated in the at least one grant.

Example Embodiment 15. The method of Embodiment 13, wherein, when the indicator is a value of 1 and not all of the fields in a CSI request are set to zero, the wireless device determines that it is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.

Example Embodiment 16. The method of Embodiment 13, wherein, when the indicator is a value of 0 and all of the fields in a CSI request are set to zero, the wireless device determines that it is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant. Example Embodiment 17. The method of Embodiment 13, wherein, when the indicator is a value of 1 and all of the fields in a CSI request are set to zero, the wireless device determines that it is permitted to send HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.

Example Embodiment 18. The method of any one of Embodiments 1 to 16, wherein the UCI comprises a scheduling request (SR), and the method further comprises: multiplexing the SR onto the PUSCH.

Example Embodiment 19. The method of Embodiment 18, wherein the SR is multiplexed onto the PUSCH based on a beta offset parameter.

Example Embodiment 20. The method of Embodiment 19, wherein the beta offset parameter is received as a radio resource control information element associated with a PUSCH configuration.

Example Embodiment 21. The method of Embodiment 2, wherein the at least one grant comprises a plurality of grants and the indicator applies to the plurality of grants.

Example Embodiment 22. The method of any one of Embodiments 1 to 21, further comprising determining, by the wireless device, that no inter UE preemption applies to the transmission of the UCI on the PUSCH.

Example Embodiment 23. The method of any one of Embodiments 1 to 22, further comprising determining, by the wireless device that only a single transmission of the UCI is allowed on the PUSCH without uL-SCH data even where a repetition parameter is set to allow repetitions of UL-SCH data.

Example Embodiment 24. The method of any one of Embodiments 1 to 22, further comprising: determining that repetition of UCI is permitted a first number of times; determining that repetition of UL-SCH data is permitted a second number of times; determining that the second number of times is greater or equal to the first number of times; and transmitting the UCI on the PUSCH without UL-SCH data the first number of times.

Example Embodiment 25. A method performed by a base station, the method comprising: transmitting, to a wireless device, at least one grant for transmitting on a physical uplink shared channel (PUSCH); and receiving, from the wireless device, uplink control information (UCI) on the PUSCH even if the wireless device does not have uplink-shared channel (UL-SCH) data to transmit.

Example Embodiment 26. The method of Embodiment 25, wherein the at least one grant comprises an indicator indicating that the wireless device is to transmit the UCI on the PUSCH even if the wireless device does not have UL-SCH data to transmit. Example Embodiment 27. The method of any one of Embodiments 25 to 26, wherein receiving the UCI on the PUSCH comprises receiving the UCI on the PUSCH without any UL- SCH.

Example Embodiment 28. The method of any one of Embodiments 26 to 27, further comprising transmitting an indicator to the wireless device to permit transmissions of the UCI on the PUSCH without UL-SCH data.

Example Embodiment 29. The method of any one of Embodiments 25 to 28, wherein the UCI comprises at least one of: a scheduling request (SR); a hybrid automatic repeat request acknowledgement (HARQ-ACK); and channel state information (CSI).

Example Embodiment 30. The method of any one of Embodiments 25 to 29, wherein the at least one grant indicates an allocation of at least one resource for transmitting on the PUSCH, and the UCI is transmitted on the PUSCH using the at least one resource.

Example Embodiment 31. The method of any one of Embodiments 25 to 30, wherein the at least one grant comprises a Type 1 configured grant.

Example Embodiment 32. The method of any one of Embodiments 25 to 30, wherein the at least one grant comprises a Type 2 configured grant.

Example Embodiment 33. The method of Embodiment 32, further comprising transmitting an indicator with an activation of downlink control information (DCI), the indicator indicating that the wireless device is permitted to transmit the UCI on the PUSCH without UL-SCH data.

Example Embodiment 34. The method of Embodiment 33, wherein the indicator is semi-persistently indicated to the wireless device.

Example Embodiment 35. The method of Embodiment 33, wherein the indicator is transmitted as a radio resource control information element (RRC IE).

Example Embodiment 36. The method of any one of Embodiments 33 to 35 wherein the indicator indicates a type of UCE that the wireless device is permitted to transmit without UL-SCH data.

Example Embodiment 37. The method of Embodiment 36, wherein the type of UCI comprises at least one of a scheduling request (SR), a hybrid automatic repeat request acknowledgement (HARQ-ACK), and channel state information (CSI).

Example Embodiment 38. The method of Embodiment 36, wherein, when the indicator is a value of 0 and not all of the fields in a CSI request are set to zero, the wireless device is permitted to send SR and/or HARQ-ACK and CSI on the PUSCH using at least one resource indicated in the at least one grant. Example Embodiment 39. The method of Embodiment 36, wherein, when the indicator is a value of 1 and not all of the fields in a CSI request are set to zero, the wireless device is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.

Example Embodiment 40. The method of Embodiment 36, wherein, when the indicator is a value of 0 and all of the fields in a CSI request are set to zero, the wireless device is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.

Example Embodiment 41. The method of Embodiment 36, wherein, when the indicator is a value of 1 and all of the fields in a CSI request are set to zero, the wireless device is permitted to send HARQ-ACK on the PUSCH using at least one resource indicated in the at least one grant.

Example Embodiment 42. The method of any one of Embodiments 25 to 41, wherein the UCI comprises a scheduling request (SR) multiplexed onto the PUSCH.

Example Embodiment 43. The method of Embodiment 42, wherein the SR is multiplexed onto the PUSCH based on a beta offset parameter.

Example Embodiment 44. The method of Embodiment 43, further comprising transmitting, to the wireless device, the beta offset parameter as a radio resource control information element associated with a PUSCH configuration.

Example Embodiment 45. The method of Embodiment 26, wherein the at least one grant comprises a plurality of grants and the indicator applies to the plurality of grants.

Example Embodiment 46. The method of any one of Embodiments 25 to 45, wherein no inter UE preemption applies to the transmission of the UCI on the PUSCH.

Example Embodiment 47. The method of any one of Embodiments 25 to 46, wherein only a single transmission of the UCI is allowed on the PUSCH without uL-SCH data even where a repetition parameter is set to allow repetitions of UL-SCH data.

Example Embodiment 48. The method of any one of Embodiments 25 to 46, wherein: repetition of UCI is permitted a first number of times; repetition of UL-SCH data is permitted a second number of times; the second number of times is greater or equal to the first number of times; and the UCI is received on the PUSCH without UL-SCH data the first number of times.

Example Embodiment 49. A wireless device comprising: processing circuitry configured to perform any of the steps of any of Embodiments 1 to 24; and power supply circuitry configured to supply power to the wireless device. Example Embodiment 50. A base station comprising: processing circuitry configured to perform any of the steps of any of Embodiments 25 to 48; and power supply circuitry configured to supply power to the wireless device.

Example Embodiment 51. A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of Embodiments 1 to 24; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

Example Embodiment 52. A communication system 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 user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of Embodiments 25 to 48.

Example Embodiment 53. The communication system of the pervious embodiment further including the base station.

Example Embodiment 54. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

Example Embodiment 55. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

Example Embodiment 56. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of Embodiments 25 to 48.

Example Embodiment 57. The method of the previous embodiment, further comprising, at the base station, transmitting the user data. Example Embodiment 58. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

Example Embodiment 59. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.

Example Embodiment 60. A communication system 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 user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of Embodiments 1 to 24.

Example Embodiment 61. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

Example Embodiment 62. The communication system of the previous 2 embodiments, 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.

Example Embodiment 63. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of Embodiments 1 to 24.

Example Embodiment 64. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.

Example Embodiment 65. A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of Embodiments 1 to 24.

Example Embodiment 66. The communication system of the previous embodiment, further including the UE.

Example Embodiment 67. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

Example Embodiment 68. The communication system of the previous 3 embodiments, 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.

Example Embodiment 69. The communication system of the previous 4 embodiments, 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.

Example Embodiment 70. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of Embodiments 1 to 24.

Example Embodiment 71. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.

Example Embodiment 72. The method of the previous 2 embodiments, further comprising: at the UE, 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.

Example Embodiment 73. The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, 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.

Example Embodiment 74. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of Embodiments 25 to 48.

Example Embodiment 75. The communication system of the previous embodiment further including the base station. Example Embodiment 76. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

Example Embodiment 77. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

Example Embodiment 78. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of Embodiments 1 to 24.

Example Embodiment 79. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.

Example Embodiment 80. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

ABBREVIATIONS

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s). lx RTT CDMA2000 lx Radio Transmission Technology

3GPP 3rd Generation Partnership Project

5G 5th Generation

5GS 5G System

5QI 5G QoS Identifier

ABS Almost Blank Subframe

AN Access Network

AN Access Node

ARQ Automatic Repeat Request

AS Access Stratum AWGN Additive White Gaussian Noise

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response

CN Core Network

CP Cyclic Prefix

CPICH Common Pilot Channel

CPICH Ec/No CPICH Received energy per chip divided by the power density in the band

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

DUT Device Under Test

E-CID Enhanced Cell-ID (positioning method)

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI

eMBB Enhanced Mobile BroadBand

eNB E-UTRAN NodeB

ePDCCH enhanced Physical Downlink Control Channel

EPS Evolved Packet System

E-SMLC evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved Universal Terrestrial Radio Access Network

FDD Frequency Division Duplex FFS For Further Study

GERAN GSM EDGE Radio Access Network

gNB gNode B (a base station in NR; a Node B supporting NR and connectivity to NGC)

GNSS Global Navigation Satellite System

GSM Global System for Mobile communication

HARQ Hybrid Automatic Repeat Request

HO Handover

HSPA High Speed Packet Access

HRPD High Rate Packet Data

LOS Line of Sight

LPP LTE Positioning Protocol

LTE Long-Term Evolution

MAC Medium Access Control

MBMS Multimedia Broadcast Multicast Services

MBSFN Multimedia Broadcast multicast service Single Frequency Network

MBSFN ABS MBSFN Almost Blank Subframe

MDT Minimization of Drive Tests

MIB Master Information Block

MME Mobility Management Entity

MSC Mobile Switching Center

NGC Next Generation Core

NPDCCH Narrowband Physical Downlink Control Channel

NR New Radio

OCNG OFDMA Channel Noise Generator

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OSS Operations Support System

OTDOA Observed Time Difference of Arrival

O&M Operation and Maintenance

PBCH Physical Broadcast Channel

P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PCFICH Physical Control Format Indicator Channel

PDCCH Physical Downlink Control Channel

PDP Profile Delay Profile PDSCH Physical Downlink Shared Channel

PGW Packet Gateway

PHICH Physical Hybrid-ARQ Indicator Channel

PLMN Public Land Mobile Network

PMI Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PS Packet Switched

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RAB Radio Access Bearer

RAN Radio Access Network

RANAP Radio Access Network Application Part

RAT Radio Access Technology

RUM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR

Reference Signal Received Power

RSRQ Reference Signal Received Quality OR

Reference Symbol Received Quality

RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

RWR Release with Redirect

SCH Synchronization Channel

SCell Secondary Cell

SCS Subcarrier Spacing

SDU Service Data Unit

SFN System Frame Number SGW Serving Gateway

SI System Information

SIB System Information Block

SNR Signal to Noise Ratio

S-NSSAI Single Network Slice Selection Assistance Information

SON Self Optimized Network

SS Synchronization Signal

SSS Secondary Synchronization Signal

TBS Transport Block Size

TDD Time Division Duplex

TDOA Time Difference of Arrival

TO A Time of Arrival

TSS Tertiary Synchronization Signal

TTI Transmission Time Interval

UCI Uplink Control Information

UE User Equipment

UL Uplink

UL-SCH Uplink Shared Channel

UMTS Universal Mobile Telecommunication System

USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival

UTRA Universal Terrestrial Radio Access

UTRAN Universal Terrestrial Radio Access Network

WCDMA Wide CDMA

WLAN Wide Local Area Network

CONCLUSION

Modifications, additions, or omissions may be made to the systems and apparatuses described herein without departing from the scope of the disclosure. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and/or other logic. As used in this document,“each” refers to each member of a set or each member of a subset of a set.

Modifications, additions, or omissions may be made to the methods described herein without departing from the scope of the disclosure. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the spirit and scope of this disclosure.

Claims

1. A method (1200) performed by a wireless device (110), the method comprising: receiving (1202) at least one configured grant for transmitting on a physical uplink shared channel, PUSCH; and

transmitting (1204) uplink control information, UCI, on the PUSCH though the wireless device does not have uplink-shared channel, UL-SCH, data to transmit.

2. The method of Claim 1 , wherein the at least one configured grant comprises an indicator indicating that the wireless device is to transmit the UCI on the PUSCH though the wireless device does not have UL-SCH data to transmit.

3. The method of Claim 2, further comprising:

determining that the wireless device does not have UL-SCH data to transmit; and based on the indicator, determining that the wireless device is allowed to transmit UCI on the PUSCH though the wireless device does not have UL-SCH data to transmit.

4. The method of any one of Claims 2 to 3, wherein the indicator comprises a uciWithoutUL-SCH indicator and wherein the is set to true.

5. The method of any one of Claims 1 to 4, wherein the UCI comprises at least channel state information, CSI.

6. The method of any one of Claims 1 to 5, wherein the UCI comprises at least one of: a scheduling request, SR; and

a hybrid automatic repeat request acknowledgement, HARQ-ACK.

7. The method of any one of Claims 1 to 6, wherein the at least one configured grant comprises a Type 1 configured grant.

8. The method of any one of Claims 1 to 6, wherein the at least one configured grant comprises a Type 2 configured grant.

9. The method of Claim 8, further comprising receiving an indicator with an activation of downlink control information, DCI, the indicator indicating that the wireless device is to transmit the UCI on the PUSCH though the wireless device does not have UL-SCH data to transmit.

10. The method of Claim 9, wherein the indicator is indicated to and received by the wireless device as a radio resource control information element, RRC IE.

11. The method of any one of Claims 9 to 10, further comprising:

determining, based on the indicator, a type of UCI that the wireless device is permitted to transmit though the wireless device does not have UL-SCH data to transmit, the type of UCI comprising at least one of a scheduling request, SR, a hybrid automatic repeat request acknowledgement, HARQ-ACK, and channel state information, CSI.

12. The method of Claim 11, wherein the indicator is a value of 0 and not all of the fields in a CSI request are set to zero, and the method further comprises determining that the wireless device is permitted to send SR and/or HARQ-ACK and CSI on the PUSCH using at least one resource indicated in the at least one configured grant.

13. The method of Claim 11, wherein the indicator is a value of 1 and not all of the fields in a CSI request are set to zero, and the method further comprises determining that the wireless device is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one configured grant.

14. The method of Claim 11, wherein the indicator is a value of 0 and all of the fields in a CSI request are set to zero, and the method further comprises determining that the wireless device is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one configured grant.

15. The method of Claim 11, wherein the indicator is a value of 1 and all of the fields in a CSI request are set to zero, and the method further comprises determining that the wireless device is permitted to send HARQ-ACK on the PUSCH using at least one resource indicated in the at least one configured grant.

16. The method of any one of Claims 1 to 15, wherein the UCI is multiplexed onto the PUSCH based on at least one beta offset parameter.

17. The method of Claim 16, wherein the beta offset parameter is received as a radio resource control information element associated with a PUSCH configuration.

18. The method of any one of Claims 2 to 17, wherein the at least one configured grant comprises a plurality of configured grants and the indicator applies to the plurality of configured grants.

19. The method of any one of Claims 1 to 18, further comprising determining, by the wireless device that only a single transmission of the UCI is allowed on the PUSCH without UL-SCH data even where a repetition parameter is set to allow repetitions of UL-SCH data.

20. The method of any one of Claims 1 to 19, further comprising:

determining that repetition of UCI is permitted a first number of times;

determining that repetition of UL-SCH data is permitted a second number of times; determining that the second number of times is greater or equal to the first number of times; and

transmitting the UCI on the PUSCH without UL-SCH data the first number of times.

21. A method (1600) performed by a base station (160), the method comprising:

transmitting (1602), to a wireless device (110), at least one configured grant for transmitting on a physical uplink shared channel, PUSCH; and

receiving (1604), from the wireless device, uplink control information, UCI, on the PUSCH though the wireless device does not have uplink-shared channel, UL-SCH, data to transmit.

22. The method of Claim 21, wherein the at least one configured grant comprises an indicator indicating that the wireless device is to transmit the UCI on the PUSCH though the wireless device does not have UL-SCH data to transmit.

23. The method of any one of Claims 21 to 22, wherein receiving the UCI on the PUSCH comprises receiving the UCI on the PUSCH without any UL-SCH.

24. The method of any one of Claims 22 to 23, further comprising transmitting the indicator to the wireless device to permit transmissions of the UCI on the PUSCH without UL-SCH data.

25. The method of any one of Claims 21 to 24, wherein the UCI comprises at least channel state information, CSI.

26. The method of any one of Claims 21 to 25, wherein the UCI comprises at least one of: a scheduling request, SR; and

a hybrid automatic repeat request acknowledgement, HARQ-ACK.

27. The method of any one of Claims 21 to 26, wherein the at least one configured grant comprises a Type 1 configured grant.

28. The method of any one of Claims 21 to 27, wherein the at least one configured grant comprises a Type 2 configured grant.

29. The method of Claim 28, further comprising transmitting an indicator with an activation of downlink control information, DCI, the indicator indicating that the wireless device is permitted to transmit the UCI on the PUSCH without UL-SCH data.

30. The method of Claim 29, wherein the indicator is indicated to the wireless device, and wherein the indicator is transmitted as a radio resource control information element, RRC IE.

31. The method of any one of Claims 29 to 30, wherein the indicator indicates a type of UCE that the wireless device is permitted to transmit without UL-SCH data, the type of UCI comprising at least one of a scheduling request, SR, a hybrid automatic repeat request acknowledgement, HARQ-ACK, and channel state information, CSI.

32. The method of Claim 31, wherein, when the indicator is a value of 0 and not all of the fields in a CSI request are set to zero, the wireless device is permitted to send SR and/or HARQ-ACK and CSI on the PUSCH using at least one resource indicated in the at least one configured grant.

33. The method of Claim 31, wherein, when the indicator is a value of 1 and not all of the fields in a CSI request are set to zero, the wireless device is permitted to send SR and/or HARQ- ACK on the PUSCH using at least one resource indicated in the at least one configured grant.

34. The method of Claim 31, wherein, when the indicator is a value of 0 and all of the fields in a CSI request are set to zero, the wireless device is permitted to send SR and/or HARQ- ACK on the PUSCH using at least one resource indicated in the at least one configured grant.

35. The method of Claim 31, wherein, when the indicator is a value of 1 and all of the fields in a CSI request are set to zero, the wireless device is permitted to send HARQ-ACK on the PUSCH using at least one resource indicated in the at least one configured grant.

36. The method of any one of Claims 25 to 41, wherein the UCI is multiplexed onto the PUSCH based on at least one beta offset parameter.

37. The method of Claim 36, further comprising transmitting, to the wireless device, the at least one beta offset parameter as a radio resource control information element associated with a PUSCH configuration.

38. The method of any one of Claims 22 to 37, wherein the at least one configured grant comprises a plurality of configured grants and the indicator applies to the plurality of configured grants.

39. The method of any one of Claims 21 to 38, wherein only a single transmission of the UCI is allowed on the PUSCH without UL-SCH data even where a repetition parameter is set to allow repetitions of UL-SCH data.

40. The method of any one of Claims 21 to 39, wherein:

repetition of UCI is permitted a first number of times;

repetition of UL-SCH data is permitted a second number of times;

the second number of times is greater or equal to the first number of times; and the UCI is received on the PUSCH without UL-SCH data the first number of times.

41. A wireless device (110) comprising:

processing circuitry (120) configured to:

receive at least one configured grant for transmitting on a physical uplink shared channel, PUSCH; and

transmit uplink control information, UCI, on the PUSCH though the wireless device does not have uplink-shared channel, UL-SCH, data to transmit.

42. The wireless device of Claim 41, wherein the at least one configured grant comprises an indicator indicating that the wireless device is to transmit the UCI on the PUSCH though the wireless device does not have UL-SCH data to transmit.

43. The wireless device of Claim 42, wherein the processing circuitry is configured to: determine that the wireless device does not have UL-SCH data to transmit; and based on the indicator, determine that the wireless device is allowed to transmit UCI on the PUSCH though the wireless device does not have UL-SCH data to transmit.

44. The wireless device of any one of Claims 42 to 43, wherein the indicator comprises a uciWithoutUL-SCH indicator and wherein the is set to true.

45. The wireless device of any one of Claims 41 to 44, wherein the UCI comprises at least channel state information, CSI.

46. The wireless device of any one of Claims 41 to 45, wherein the UCI comprises at least one of:

a scheduling request, SR; and

a hybrid automatic repeat request acknowledgement, HARQ-ACK.

47. The wireless device of any one of Claims 41 to 46, wherein the at least one configured grant comprises a Type 1 configured grant.

48. The wireless device of any one of Claims 41 to 46, wherein the at least one configured grant comprises a Type 2 configured grant.

49. The wireless device of Claim 48, wherein the processing circuitry is configured to receive an indicator with an activation of downlink control information, DCI, the indicator indicating that the wireless device is to transmit the UCI on the PUSCH though the wireless device does not have UL-SCH data to transmit.

50. The wireless device of Claim 49, wherein the indicator is indicated to and received by the wireless device, and wherein the indicator is received as a radio resource control information element, RRC IE.

51. The wireless device of any one of Claims 49 to 50, wherein the processing circuitry is configured to:

determine, based on the indicator, a type of UCI that the wireless device is permitted to transmit though the wireless device does not have uplink-shared channel, UL-SCH, data to transmit, the type of UCI comprising at least one of a scheduling request, SR, a hybrid automatic repeat request acknowledgement, HARQ-ACK, and channel state information, CSI.

52. The wireless device of Claim 51, wherein the indicator is a value of 0 and not all of the fields in a CSI request are set to zero, and the processing circuitry is configured to determine that the wireless device is permitted to send SR and/or HARQ-ACK and CSI on the PUSCH using at least one resource indicated in the at least one configured grant.

53. The wireless device of Claim 51, wherein the indicator is a value of 1 and not all of the fields in a CSI request are set to zero, and the processing circuitry is configured to determine that the wireless device is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one configured grant.

54. The wireless device of Claim 51, wherein the indicator is a value of 0 and all of the fields in a CSI request are set to zero, and the method further comprises determining that the wireless device is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one configured grant.

55. The wireless device of Claim 51 , wherein the indicator is a value of 1 and all of the fields in a CSI request are set to zero, and the processing circuitry is configured to determine that the wireless device is permitted to send HARQ-ACK on the PUSCH using at least one resource indicated in the at least one configured grant.

56. The wireless device of any one of Claims 51 to 55, wherein the UCI is multiplexed onto the PUSCH based on at least one beta offset parameter.

57. The wireless device of Claim 56, wherein the beta offset parameter is received as a radio resource control information element associated with a PUSCH configuration.

58. The wireless device of any one of Claims 52 to 57, wherein the at least one configured grant comprises a plurality of configured grants and the indicator applies to the plurality of configured grants.

59. The wireless device of any one of Claims 51 to 58, wherein the processing circuitry is configured to determine, by the wireless device that only a single transmission of the UCI is allowed on the PUSCH without UL-SCH data even where a repetition parameter is set to allow repetitions of UL-SCH data.

60. The wireless device of any one of Claims 51 to 59, wherein the processing circuitry is configured to:

determine that repetition of UCI is permitted a first number of times;

determine that repetition of UL-SCH data is permitted a second number of times; determine that the second number of times is greater or equal to the first number of times; and

transmit the UCI on the PUSCH without UL-SCH data the first number of times.

61. A network node (160) comprising:

processing circuitry (170) configured to:

transmit, to a wireless device (110), at least one configured grant for transmitting on a physical uplink shared channel, PUSCH; and

receive, from the wireless device, uplink control information, UCI, on the PUSCH though the wireless device does not have uplink-shared channel, UL-SCH, data to transmit.

62. The network node of Claim 61, wherein the at least one configured grant comprises an indicator indicating that the wireless device is to transmit the UCI on the PUSCH though the wireless device does not have UL-SCH data to transmit.

63. The network node of any one of Claims 61 to 62, wherein receiving the UCI on the PUSCH comprises receiving the UCI on the PUSCH without any UL-SCH.

64. The network node of any one of Claims 62 to 63, wherein the processing circuitry is configured to transmit the indicator to the wireless device to permit transmissions of the UCI on the PUSCH without UL-SCH data.

65. The network node of any one of Claims 61 to 64, wherein the UCI comprises at least channel state information, CSI.

66. The network node of any one of Claims 61 to 65, wherein the UCI comprises at least one of:

a scheduling request, SR; and

a hybrid automatic repeat request acknowledgement, HARQ-ACK.

67. The network node of any one of Claims 61 to 66, wherein the at least one configured grant comprises a Type 1 configured grant.

68. The network node of any one of Claims 61 to 66, wherein the at least one configured grant comprises a Type 2 configured grant.

69. The network node of Claim 68, wherein the processing circuitry is configured to transmit an indicator with an activation of downlink control information, DCI, the indicator indicating that the wireless device is permitted to transmit the UCI on the PUSCH without UL- SCH data.

70. The network node of Claim 69, wherein the indicator is indicated to the wireless device, and wherein the indicator is transmitted as a radio resource control information element, RRC IE.

71. The network node of any one of Claims 69 to 70, wherein the indicator indicates a type of UCE that the wireless device is permitted to transmit without UL-SCH data, the type of UCI comprising at least one of a scheduling request, SR, a hybrid automatic repeat request acknowledgement, HARQ-ACK, and channel state information, CSI.

72. The network node of any one of Claims 69 to 70, wherein, when the indicator is a value of 0 and not all of the fields in a CSI request are set to zero, the wireless device is permitted to send SR and/or HARQ-ACK and CSI on the PUSCH using at least one resource indicated in the at least one configured grant.

73. The network node of any one of Claims 69 to 70, wherein, when the indicator is a value of 1 and not all of the fields in a CSI request are set to zero, the wireless device is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one configured grant.

74. The network node of any one of Claims 69 to 70, wherein, when the indicator is a value of 0 and all of the fields in a CSI request are set to zero, the wireless device is permitted to send SR and/or HARQ-ACK on the PUSCH using at least one resource indicated in the at least one configured grant.

75. The network node of any one of Claims 69 to 70, wherein, when the indicator is a value of 1 and all of the fields in a CSI request are set to zero, the wireless device is permitted to send HARQ-ACK on the PUSCH using at least one resource indicated in the at least one configured grant.

76. The network node of any one of Claims 61 to 75, wherein the UCI is multiplexed onto the PUSCH based on at least one beta offset parameter.

77. The network node of Claim 76, further comprising transmitting, to the wireless device, the at least one beta offset parameter as a radio resource control information element associated with a PUSCH configuration.

78. The network node of any one of Claims 61 to 77, wherein the at least one configured grant comprises a plurality of configured grants and the indicator applies to the plurality of configured grants.

79. The network node of any one of Claims 61 to 78, wherein only a single transmission of the UCI is allowed on the PUSCH without UL-SCH data even where a repetition parameter is set to allow repetitions of UL-SCH data.

80. The network node of any one of Claims 61 to 79, wherein:

repetition of UCI is permitted a first number of times;

repetition of UL-SCH data is permitted a second number of times;