TECHNICAL FIELD

The present disclosure relates to wireless communications and, in particular, to HARQ-ACK codebook construction for single DCI scheduling multiple cells.

BACKGROUND

[0001] Carrier Aggregation: Carrier Aggregation is generally used in NR (5G) and LTE systems to improve UE transmit receive data rate. With carrier aggregation (CA), the UE typically operates initially on single serving cell called a primary cell Pcell. The Pcell is operated on a component carrier in a frequency band. The UE is then configured by the network with one or more secondary serving cells (Scell(s)). Each Scell can correspond to a component carrier (CC) in the same frequency band (intra-band CA) or different frequency band (interband CA) from the frequency band of the CC corresponding to the Pcell. For the UE to transmit/receive data on the Scell(s) (e.g by receiving DL-SCH information on a PDSCH or by transmitting UL-SCH on a PUSCH), the Scell(s) need to be activated by the network. The Scell(s) can also be deactivated and later reactivated as needed via activation/deactivation signaling.

[0002] Cross-Carrier Scheduling: For NR carrier aggregation, cross-carrier scheduling (CCS) has been specified using following framework

1. UE has a primary serving cell and can be configured with one or more secondary serving cells (SCells)

2. For a given SCell with Scell index X, a. if the SCell is configured with a ‘scheduling cell’ with cell index Y (crosscarrier scheduling) i. SCell X is referred to as the ‘scheduled cell’ ii. UE monitors DL PDCCH on the scheduling cell Y for assignments/grants scheduling PDSCH/PUSCH corresponding to Sell X. iii. PDSCH/PUSCH corresponding to Sell X cannot be scheduled for the UE using a serving cell other than scheduling cell Y b. Otherwise i. SCell X is the scheduling cell for SCell X (same-carrier scheduling) ii. UE monitors DL PDCCH on SCell X for assignments/grants scheduling PDSCH/PUSCH corresponding to Sell X iii. PDSCH/PUSCH corresponding to Sell X cannot be scheduled for the UE using a serving cell other than SCell X

An SCell cannot be configured as a scheduling cell for the primary cell. The primary cell is always its own scheduling cell. In some cases, the term “primary cell” or “primary serving cell” can refer to PCell for a UE not configured with DC, and can refer to PCell of MCG or PSCell of SCG for a UE configured with DC.

[0003] Dual Connectivity: Dual Connectivity (DC) is generally used in NR (5G) and LTE systems to improve UE transmit receive data rate. With DC, the UE typically operates a master cell group (MCG) and a secondary cell group (SCG). Each cell group can have one or more serving cells. The MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection reestablishment procedure is referred to as the primary cell or PCell. The SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure is referred to as the primary SCG cell or PSCell.

[0004] PDCCH Monitoring: In 3GPP NR standard, downlink control information (DCI) is received over the physical layer downlink control channel (PDCCH). The PDCCH may carry DCI in messages with different formats. DCI format 0 0 and 0 1 are DCI messages used to convey uplink grants to the UE for transmission of the physical layer data channel in the uplink (PUSCH) and DCI format 1 0 and 1 1 are used to convey downlink grants for transmission of the physical layer data channel in the downlink (PDSCH). Other DCI formats (2 0, 2 1, 2 2 and 2_3) are used for other purposes such as transmission of slot format information, reserved resource, transmit power control information etc.

[0005] A PDCCH candidate is searched within a common or UE-specific search space which is mapped to a set of time and frequency resources referred to as a control resource set (CORESET). The search spaces within which PDCCH candidates must be monitored are configured to the UE via radio resource control (RRC) signaling. A monitoring periodicity is also configured for different PDCCH candidates. In any particular slot the UE may be configured to monitor multiple PDCCH candidates in multiple search spaces which may be mapped to one or more CORESETs. PDCCH candidates may need to be monitored multiple times in a slot, once every slot or once in multiple of slots.

[0006] The smallest unit used for defining CORESETs is a Resource Element Group (REG) which is defined as spanning 1 PRB x 1 OFDM symbol in frequency and time. Each REG contains demodulation reference signals (DM-RS) to aid in the estimation of the radio channel over which that REG was transmitted. When transmitting the PDCCH, a precoder could be used to apply weights at the transmit antennas based on some knowledge of the radio channel prior to transmission. It is possible to improve channel estimation performance at the UE by estimating the channel over multiple REGs that are proximate in time and frequency if the precoder used at the transmitter for the REGs is not different. To assist the UE with channel estimation the multiple REGs can be grouped together to form a REG bundle and the REG bundle size for a CORESET is indicated to the UE. The UE may assume that any precoder used for the transmission of the PDCCH is the same for all the REGs in the REG bundle. A REG bundle may consist of 2, 3 or 6 REGs.

[0007] A control channel element (CCE) consists of 6 REGs. The REGs within a CCE may either be contiguous or distributed in frequency. When the REGs are distributed in frequency, the CORESET is said to be using an interleaved mapping of REGs to a CCE and if the REGs are not distributed in frequency, a non-interleaved mapping is said to be used.

[0008] A PDCCH candidate may span 1, 2,4, 8 or 16 CCEs. The number of aggregated CCEs used is referred to as the aggregation level for the PDCCH candidate.

[0009] Time domain resource allocation: A UE shall determine the time domain allocation for a PUSCH or PDSCH using the time domain resource allocation (TDRA) field in the detected DCI carried in PDCCH. The TDRA field value is used to look up a TDRA entry in a TDRA table. One or more TDRA tables can be configured by higher layers (or pre-defined in specification) consisting of a list with one or more TDRA entries in it. Each TDRA entry has a slot offset (kO), a SLIV (Start and length indicator value), PDSCH mapping type (A or B) and DMRS type A position. The offset (in slots) between the slot where the DCI is detected and the slot where the corresponding PDSCH is received is based on the slot offset. The SLIV denotes the start symbol and length of PDSCH (in symbols) in the corresponding slot.

[0010] HARQ feedback: The procedure for receiving downlink transmission is that the UE first monitors and decodes a PDDCH in slot n which points to a DL data scheduled in slot n+KO slots (K0 is larger than or equal to 0). The UE then decodes the data in the corresponding PDSCH. Finally based on the outcome of the decoding the UE sends an acknowledgement of the correct decoding (ACK) or a negative acknowledgement (NACK) to the gNB at time slot n+ K0+K1 (in case of slot aggregation n+ K0 would be replaced by the slot where PDSCH ends). Both of K0 and KI are indicated in the DCI. The resources for sending the acknowledgement are indicated by PUCCH resource indicator (PRI) field in the DCI which points to one of PUCCH resources that are configured by higher layers. [0011] Depending on DL/UL slot configurations, or whether carrier aggregation, or per code-block group (CBG) transmission used in the DL, the feedback for several PDSCHs may need to be multiplexed in one feedback. This is done by constructing Hybrid Automatic Repeat Request-ACK, HARQ-ACK, codebooks. In NR, the UE can be configured to multiplex the A/N bits using a semi-static codebook or a dynamic codebook.

[0012] Type 1 or semi-static codebook consists of a bit sequence where each element contains the A/N bit from a possible allocation in a certain slot, carrier, or transport block (TB). When the UE is configured with CBG and/or time-domain resource allocation (TDRA) table with multiple entries, multiple bits are generated per slot and TB (see below). It is important to note that the codebook is derived regardless of the actual PDSCH scheduling. The size and format of the semi-static codebook is preconfigured based on the mentioned parameters. The drawback of semi-static HARQ ACK codebook is that the size is fixed, and regardless of whether there is a transmission or not a bit is reserved in the feedback matrix.

[0013] On the case when a UE has a TDRA table with multiple time-domain resource allocation entries configured: The table is pruned (i.e. entries are removed based on a specified algorithm) to derive a TDRA table that only contains non-overlapping time-domain allocations. One bit is then reserved in the HARQ CB for each non-overlapping entry (assuming a UE is capable of supporting reception of multiple PDSCH in a slot).

[0014] To avoid reserving unnecessary bits in a semi-static HARQ codebook, in NR a UE can be configured to use a type 2 or dynamic HARQ codebook, where an A/N bit is present only if there is a corresponding transmission scheduled. To avoid any confusion between the gNB and the UE, on the number of PDSCHs that the UE has to send a feedback for, a counter downlink assignment indicator (DAI) field exists in DL assignment, which denotes accumulative number of {serving cell, PDCCH occasion} pairs in which a PDSCH is scheduled to a UE up to the current PDCCH. In addition to that, there is another field called total DAI, which when present shows the total number of {serving cell, PDCCH occasion} up to (and including) all PDCCHs of the current PDCCH monitoring occasion. The timing for sending HARQ feedback is determined based on both PDSCH transmission slot with reference to PDCCH slot (K0) and the PUCCH slot that contains HARQ feedback (KI).

[0015] Figure 1 illustrates the timeline in a simple scenario with two PDSCHs and one feedback. In this example there is in total 4 PUCCH resources configured, and the PRI indicates PUCCH 2 to be used for HARQ feedback. We explain in the following how PUCCH 2 is selected from 4 PUCCH resources based on the procedure in Rel-15. [0016] In NR Rel-15, a UE can be configured with maximum 4 PUCCH resource sets for transmission of HARQ-ACK information. Each set is associated with a range of UCI payload bits including HARQ-ACK bits. The first set is always associated to 1 or 2 HARQ-ACK bits and hence includes only PUCCH format 0 or 1 or both. The range of pay load values (minimum of maximum values) for other sets, if configured, is provided by configuration except the maximum value for the last set where a default value is used, and the minimum value of the second set being 3. The first set can include maximum 32 PUCCH resources of PUCCH format 0 or 1. Other sets can include maximum 8 bits of format 2 or 3 or 4.

[0017] As described previously, the UE determines a slot for transmission of HARQ-ACK bits in a PUCCH corresponding to PDSCHs scheduled or activated by DCI via KI value provided by configuration or a field in the corresponding DCI. The UE forms a codebook from the HARQ-ACK bits with associated PUCCH in a same slot via corresponding KI values.

[0018] The UE determines a PUCCH resource set that the size of the codebook is within the corresponding range of pay load values associated to that set. The UE determines a PUCCH resource in that set if the set is configured with maximum 8 PUCCH resources, by a field in the last DCI associated to the corresponding PDSCHs. If the set is the first set and is configured with more than 8 resources, a PUCCH resource in that set is determined by a field in the last DCI associated to the corresponding PDSCHs and implicit rules based on the CCE. A PUCCH resource for HARQ-ACK transmission can overlap in time with other PUCCH resources for CSI and/or SR transmissions as well as PUSCH transmissions in a slot. In case of overlapping PUCCH and/or PUSCH resources, first the UE resolves overlapping between PUCCH resources, if any, by determining a PUCCH resource carrying the total UCI (including HARQ- ACK bits) such that the UCI multiplexing timeline requirements are met. There might be partial or completely dropping of CSI bits, if any, to multiplex the UCI in the determined PUCCH resource. Then, the UE resolves overlapping between PUCCH and PUSCH resources, if any, by multiplexing the UCI on the PUSCH resource if the timeline requirements for UCI multiplexing is met.

[0019] Sub-slot HARQ-ACK: In NR Rel-16, an enhancement on HARQ-ACK feedback is made to support more than one PUCCH carrying HARQ-ACK in a slot for supporting different services and for possible fast HARQ-ACK feedback for URLLC. This leads to an introduction of new HARQ-ACK timing in a unit of sub-slot, i.e., KI indication in a unit of sub-slot. Sub-slot configurations for PUCCH carrying HARQ-ACK can be configured from the two options, namely “2-symbol*7” and “7-symbol*2” for the sub-slot length of 2 symbols and 7 symbols, respectively. The indication of KI is the same as that of Rel-15, that is, KI is indicated in the DCI scheduling PDSCH. To determine the HARQ-ACK timing, there exists an association of PDSCH to sub-slot configuration in that if the scheduled PDSCH ends in subslot n, the corresponding HARQ-ACK is reported in sub-slot n+Kl. In a sense, sub-slot based HARQ-ACK timing works similarly to that of Rel-15 slot-based procedure by replacing the unit of KI from slot to sub-slot.

[0020] There exist some limitations on PUCCH resources for sub-slot HARQ-ACK. That is, only one PUCCH resource configuration is used for all sub-slots in a slot. Moreover, any PUCCH resource for sub-slot HARQ-ACK cannot cross sub-slot boundaries.

[0021] Figure 2 shows an example where each PDSCH is associated with a certain subslot for HARQ feedback through the use of a KI value in units of sub-slots.

[0022] Semi-static (Type-1) HARQ codebook: Type 1 or semi-static codebook consists of a bit sequence where each element contains the A/N bit from a possible allocation in a certain slot, carrier, or transport block (TB). When the UE is configured with CBG and/or time-domain resource allocation (TDRA) table with multiple entries, multiple bits are generated per slot and TB (see below). It is important to note that the codebook is derived regardless of the actual PDSCH scheduling. The size and format of the semi-static codebook is preconfigured based on the mentioned parameters. The drawback of semi-static HARQ ACK codebook is that the size is fixed, and regardless of whether there is a transmission or not a bit is reserved in the feedback matrix.

[0023] On the case when a UE has a TDRA table with multiple time-domain resource allocation entries configured: The table is pruned (i.e. entries are removed based on a specified algorithm) to derive a TDRA table that only contains non-overlapping time-domain allocations. One bit is then reserved in the HARQ CB for each non-overlapping entry (assuming a UE is capable of supporting reception of multiple PDSCH in a slot).

[0024] Dynamic (Type-2) HARQ codebook: In type 2 or dynamic HARQ codebook, an A/N bit is present in a codebook only if there is a corresponding transmission scheduled. To avoid any confusion between the gNB and the UE, on the number of PDSCHs that the UE has to send a feedback for, a counter downlink assignment indicator (DAI) field exists in DL assignment, which denotes accumulative number of {serving cell, PDCCH occasion} pairs in which a PDSCH is scheduled to a UE up to the current PDCCH. In addition to that, there is another field called total DAI, which when present shows the total number of {serving cell, PDCCH occasion} up to (and including) all PDCCHs of the current PDCCH monitoring occasion. The timing for sending HARQ feedback is determined based on both PDSCH transmission slot with reference to PDCCH slot (KO) and the PUCCH slot that contains HARQ feedback (KI).

[0025] HARQ-ACK multiplexing in PUSCH/PUCCH: When HARQ-ACK multiplexing on PUSCH, it will calculate physical resources for HARQ-ACK bits based on the following formula.

'ACK = ^MLN (1) where (JACK i ^s the number of coded modulation symbols per layer for HARQ-ACK transmission, O _ACK is the number of HARQ-ACK bits, is configured by high layer parameters, A/ ' ^{1 1} (/) is the number of resource elements that can be used for transmission of UCI in OFDM symbol /, for / = o 1 2 JV ^PUS ™, -1 , in the PUSCH transmission and w ^pus ™, is the total number of OFDM symbols of the PUSCH, including all OFDM symbols used for DMRS, a is configured by higher layer parameter scaling.

[0026] Then it will do rate-matching for HARQ-ACK and UL-SCH bits. There are two cases. The first case is HARQ-ACK is less than or equal to 2 bits, the second case is HARQ- ACK is more than 2 bits. When HARQ-ACK bits is less than or equal to 2 bits, the HARQ- ACK bits will puncture the UL-SCH coded bits. When HARQ-ACK bits is more than 2 bits, the rate matching of UL-SCH coded bits will be impacted by HARQ-ACK bits. Considering the following example. UL-SCH and HARQ-ACK bits multiplexing in one slot including 144 REs for UL-SCH and HARQ-bits and using QPSK for transmission, HARQ-ACK bits equal to 3 and = 5, then the (J CK = 27 , the coded HARQ-ACK bits is 54 bits, when do rate-matching for UL-SCH, there will be 234 UL-SCH coded bits.

[0027] Considering that the UCI bits can only transmit in one slot, the maximum HARQ- ACK coded bits is limited. Also, when HARQ-ACK bits are too large, the performance of UL- SCH will be impacted.

[0028] When HARQ-ACK transmit in PUCCH, it can use different PUCCH format. UE shall determine the PUCCH resource set and resource based on dedicated resource configuration or the PUCCH configuration table in 38.213.

[0029] For PUCCH format 0/1, it can only transmit HARQ-ACK bits no more than 2 bits. [0030] For PUCCH format 0, UE shall select orthogonal sequence based on HARQ-ACK bits and do physical resource mapping.

[0031] For PUCCH format 1, the HARQ-ACK bits will be modulated, multiply frequency sequence and block-wise spread with orthogonal sequence.

[0032] For PUCCH format 2/3/4, the HARQ-ACK bits will be encoded firstly, UE shall do rate matching for HARQ-ACK bits and other UCI bits based on the following table.

Table 6.3.1.4-1: Total rate matching output sequence length Etot

PUCCH 2

[0033] Where the E _tot is the total rate matching output sequence length, N _{symb vcl} , v^bucT , and N Eu'ijcT ^are the number of symbols carrying UCI for PUCCH formats 2/3/4 respectively; ³ are the number of PRBs that are determined by the UE for PUCCH formats 2/3 transmission respectively and ⁴ is the spreading factor for PUCCH format 4. Then HARQ-ACK coded bits will be modulated. After getting the symbols for the HARQ-ACK in PUCCH format 1/2/3/4, UE shall do physical resource mapping.

[0034] There currently exist certain challenge(s). The HARQ-ACK information bits for scheduled PDSCHs by respective DCIs construct a codebook based on the information in scheduling DCIs provided in respect to the PDSCH to HARQ-ACK timing, downlink assignment index and PUCCH resource indication to carry the corresponding HARQ-ACK.

[0035] To construct HARQ-ACK codebook for scheduled PDSCHs and multiplex the corresponding HARQ-ACK feedback in a PUCCH or PUSCH transmission, the UE needs to determine few information for each PDSCH from the scheduling DCI scheduling such as PDSCH to HARQ-ACK timing, counter/total DAI and PUCCH resource indication.

[0036] When a single DCI schedules multiple PDSCHs across cells, these information should be conveyed for each PDSCH scheduled by the single DCI. Signalling such information for each PDSCH individually in the single DCI scheduling multiple cells results in a large DCI size. On the other hand, these information are needed in order to reuse the well established legacy procedures, in particular pseudo codes for HARQ-ACK codebook constructions. SUMMARY

[0037] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The embodiments include signalling and methods to construct and multiplex HARQ-ACK codebooks in a PUCCH/PUSCH when the HARQ-ACK information corresponds to PDSCHs across multiple cells that are scheduled via a single DCI. The methods use the properties of multiple PDSCHs scheduled across cells by a single DCI as well as legacy procedures to determine the needed information for each PDSCH from the information provided for all PDSCHs in the single DCI. When needed information are determined, the legacy procedures to construct and multiplex HARQ-ACK codebooks in a PUCCH/PUSCH can be reused.

[0038] Some embodiments advantageously provide methods, systems, and apparatuses for HARQ-ACK codebook construction for single DCI scheduling multiple cells.

[0039] In one embodiment there is provided a network node. The network node is configured for a HARQ-ACK codebook for single downlink control information, DCI, scheduling multiple cells. The network node includes processing circuitry configured to transmit, to a UE, a DCI configured to schedule multiple PDSCHs in at least two cells. The processing circuitry is further configured to receive, from the UE, HARQ-ACK responses based on a set of PDSCHs from the PDSCHs scheduled by the DCI, where the HARQ-ACK responses associated with the PDSCHs in the set of PDSCHs set are in the same HARQ-ACK codebook and transmitted in the same PUCCH.

[0040] In one embodiment there is provided a method. The method is performed by a network node for a HARQ-ACK codebook for single downlink control information, DCI, scheduling multiple cells. The method includes transmitting, to a UE, a DCI configured to schedule multiple PDSCHs in at least two cells. The method further includes receiving, from the UE, HARQ-ACK responses based on a set of PDSCHs from the PDSCHs scheduled by the DCI, where the HARQ-ACK responses associated with the PDSCHs in the set of PDSCHs set are in the same HARQ-ACK codebook and transmitted in the same PUCCH.

[0041] In one embodiment there is provided a wireless device. The wireless device is configured for a HARQ-ACK codebook for single downlink control information, DCI, scheduling multiple cells. The wireless device includes processing circuitry configured to receive, from a network node, a DCI configured to schedule multiple PDSCHs in at least two cells. The processing circuitry is further configured to transmitting, to the network node, HARQ-ACK responses based on a set of PDSCHs from the PDSCHs scheduled by the DCI, where the HARQ-ACK responses associated with the PDSCHs in the set of PDSCHs set are in the same HARQ-ACK codebook and transmitted in the same PUCCH.

[0042] In one embodiment there is provided another method. The method is performed by a wireless device for a HARQ-ACK codebook for single downlink control information, DCI, scheduling multiple cells. The method includes receiving, from a network node, a DCI configured to schedule multiple PDSCHs in at least two cells. The method further includes transmitting, to the network node, HARQ-ACK responses based on a set of PDSCHs from the PDSCHs scheduled by the DCI, where the HARQ-ACK responses associated with the PDSCHs in the set of PDSCHs set are in the same HARQ-ACK codebook and transmitted in the same PUCCH.

[0043] In further embodiments the HARQ-ACK responses are based on at least two sets of PDSCHs from the PDSCHs scheduled by the DCI, where each PDSCH set is associated to a HARQ-ACK codebook and to a PUCCH.

[0044] In other embodiments, the two sets of PDSCHs are scheduled on at least two different cells having different K0 and/or KI values.

[0045] In further embodiments, the scheduling DCI is configured with a counter downlink assignment, c-DAI, field and/or a total DAI, t-DAI, field for each PDSCH set.

[0046] Certain embodiments may provide one or more of the following technical advantage(s). The embodiments facilitate using the legacy procedures for HARQ-ACK codebook construction and multiplexing without increasing the DCI overhead or changing legacy procedures when single DCI scheduling multiple cells is applied.

BRIEF DESCRIPTION OF THE DRAWINGS

[0047] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein: [0048] FIG. 1 is an example of a transmission timeline;

[0049] FIG. 2 illustratively shows of KI indication based on sub-slots with “7-symbol*2” configuration for 2 PUCCHs in two sub-slots that carry the HARQ feedback of PDSCH transmissions;

[0050] FIG. 3 illustratively shows a PDSCHs scheduled by a single DCI with associated HARQ-ACK in a same codebook and a single PUCCH; [0051] FIG. 4 illustratively shows 2 sets of PDSCHs scheduled by a single DCI, due to different kO values for pair of cells. Each PDSCH set is associated to its corresponding HARQ- ACK code book and PUCCH;

[0052] FIG. 5 illustratively shows 2 sets of PDSCHs scheduled by a single DCI, due to different KI values for pair of cells. Each PDSCH set is associated to its corresponding HARQ- ACK code book and PUCCH;

[0053] FIG. 6 illustratively shows legacy procedures when single DCI schedules a single PDSCH and corresponding counter and total DAI are indicated by DCI;

[0054] FIG. 7. illustratively shows procedures to determine counter and total DAI for each PDSCH when single DCI schedules multiple PDSCHs based on the counter and total DAI are indicated by DCI;

[0055] FIG. 8 illustratively shows single DCI scheduling 2 PUSCHs across 2 cells;

[0056] FIG. 9 is a flowchart of an example process in a wireless device according to some embodiments of the present disclosure;

[0057] FIG. 10 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0058] FIG. QQ1 shows an example of a communication system QQ100 in accordance with some embodiments;

[0059] FIG. QQ2 shows a UE QQ200 in accordance with some embodiments. As used herein;

[0060] FIG. QQ3 shows a network node QQ300 in accordance with some embodiments

[0061] FIG. QQ4 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure QQ1, in accordance with various aspects described herein;

[0062] FIG. QQ5 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized;

[0063] FIG. QQ6 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments;

DETAILED DESCRIPTION

[0064] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Further, the embodiments are not limited for the illustrative examples disclosed herein. The embodiments may be extended to include cells with same or different subcarrier spacing, as well as slot or sub-slot configurations of PUCCH slots as well as same or different physical layer priority associated to transmissions.

[0065] In the embodiments a mapping is introduced to translate the information provided in the single DCI for multiple PDSCHs/PUSCHs to information for each individual PDSCH/PUSCH without increasing the DCI overhead or changing legacy procedures for codebook constructions or multiplexing.

[0066] Single DCI scheduling multiple PDSCHs across cells:

[0067] HARQ-ACK timing determination and multiplexing, in PUCCH. When a UE detects a DCI configured to schedule multiple PDSCHs across cells, based on the information in the DCI fields the UE determines a set of PDSCHs from the PDSCHs scheduled by the DCI that their corresponding HARQ-ACK would be transmitted in a same slot as part of a same HARQ- ACK codebook. See illustration in Figure 3.

[0068] The maximum number of sets can be provided by RRC configuration. The maximum number of sets can be derived implicitly from other RRC parameters configurations. In one example, due to the configured time domain resource allocation (TDRA) table, an indicated index to the TDRA table in DCI results in different kO values for different cells that in turn results in PDSCHs scheduled in different slots with reference to PUCCH slots if same KI value is indicated by DCI. See illustration in Figure 4. In another example, the scheduling DCI indicates two KI values when scheduling PDSCHs such that the PUCCH corresponding to HARQ-ACK for PDSCHs would be indicated to be transmitted into two different slots. See illustration in Figure 5. The procedures to determine counter downlink assignment (c-DAI) and/or total DAI values for each PDSCH are applied per set.

[0069] The maximum number of sets can be provided by RRC configuration.

[0070] The maximum number of sets can be derived implicitly from other RRC parameters configurations. In one example, due to the configured time domain resource allocation (TDRA) table, an indicated index to the TDRA table in DCI results in different kO values for different cells that in turn results in PDSCHs scheduled in different slots with reference to PUCCH slots if same KI value is indicated by DCI. See illustration in Figure 4.

[0071] In another example, the scheduling DCI indicates two KI values when scheduling PDSCHs such that the PUCCH corresponding to HARQ-ACK for PDSCHs would be indicated to be transmitted into two different slots. See illustration in Figure 5. [0072] The procedures to determine counter downlink assignment (c-DAI) and/or total DAI values for each PDSCH are applied per set.

[0073] HARQ-ACK codebook constructions. The scheduling DCI is configured with counter downlink assignment (c-DAI) field and/or total DAI field corresponding to each set as shown in an example in Figure 7 where PDCCH A schedules 4 PDSCHs and PDCCH B schedules 2 PDSCHs. Both PDCCHs indicate (c-DAI, t-DAI) values. As a reference the same scenario is illustrated in Figure 6 where each PDSCH is scheduled by a single DCI.

[0074] The UE determines the number of PDSCHs in a set. For each PDSCH in the set, the UE determines the corresponding c-DAI and T-DAI value if applicable, as the following:

Ordering PDSCHs

• The UE orders the PDSCH(s) in each set. For example in Figure 7, set A includes 4 PDSCHs and set B include 2 PDSCHs. PDSCHs in each set are scheduled only one DCI.

• To order the PDSCHs in a set, the UE determines the corresponding PDSCH reception starting time and associated scheduled cell for each PDSCH in the set.

• The PDSCHs in the set are then ordered based on the corresponding {scheduled cell index, PDSCH reception starting time}. The PDSCHs are ordered by first in ascending order of cell index and then in ascending order of PDSCH starting time. For example, PDSCHs scheduled by PDCCH A are ordered as {PDSCH0, PDSCH1, PDSCH2, PDSCH3} and PDSCHs scheduled by PDCCH B are ordered as {PDSCH4, PDSCH5}. c-DAI association for PDSCHs

In one embodiment the UE applies the following procedures for c-DAI association for PDSCHs:

• The UE determines an associated c-DAI value based on the value of the c-DAI in the DCI and ordering procedures for each PDSCH in the set.

• The UE determines the value of the c-DAI from DCI which is referred to as Vtempl .

• c-DAI value for the first PDSCH in set is initiated by Vtempl (i.e. the c-DAI value that is obtained from the DCI field).

• The UE continues the following procedures until all PDSCHs in the set are associated a c-DAI value and respecting modulo operation based on the bit-size of the t-DAI field.

• Vtempl is increased by one. • The UE associates Vtempl as the corresponding c-DAI value to the next PDSCH in the set following first ascending order of cell index and then in ascending order of PDSCH starting time. This procedure continues until a c-DAI value is determined for the last PDSCH in the set.

In the above embodiment, the UE can include the following steps when applicable:

• If the UE determines another DCI that schedules another PDSCH scheduled on a cell with a PDSCH starting symbol that is the same as at least one of the PDSCHs in the set scheduled by a single DCI scheduling multiple cell, and the HARQ-ACK feedback of this PDSCH belongs to the same HARQ-ACK codebook of the PDSCHs in the set scheduled by a single DCI scheduling multiple cell, the UE includes this PDSCH in the set (as a dummy PDSCH for example for the purpose determining c-DAI association of the original PDSCHs in the set.

• The UE doesn’t change the c-DAI corresponding to the dummy PDSCH.

• The UE doesn’t expect that the c-DAI corresponding to the dummy PDSCH conflicts with the c-DAI that the UE would determine from the procedure to determine c-DAI association for the actual PDSCHs in the set. t-DAI association for PDSCHs (if applicable)

In one embodiment the UE applies the following procedures for t-DAI association for PDSCHs:

• The UE determines an associated t-DAI value based on the value of the t-DAI in the DCI and ordering procedures for each PDSCH in the set.

• The UE determines the value of the t-DAI from DCI which is referred to as Vtemp2.

• t-DAI value for the last PDSCH in the set is initiated by Vtemp2 (i.e. the t-DAI value that is obtained from the DCI field).

• The UE associates Vtemp2 as the corresponding t-DAI value to the previous PDSCHs in the set that have the same PDSCH reception starting time as the last PDSCH, if any.

The UE continues the following procedures until all PDSCHs in the set are associated a t-DAI value and respecting modulo operation based on the bit-size of the t-DAI field: o Vtemp2 is decremented by one. o The UE associates Vtemp2 as the corresponding t-DAI value to the previous PDSCHs in the set that have the same PDSCH reception starting time as the last PDSCH without t-DAI association, if any. In another embodiment the UE applies the following procedures for t-DAI association for PDSCHs:

• The UE determines an associated t-DAI value based on the value of the t-DAI in the DCI and ordering procedures for each PDSCH in the set.

• The UE determines the value of the t-DAI from DCI which is referred to as Vtemp2.

• t-DAI value for the first PDSCH in the set is initiated by Vtemp2 (i.e. the t-DAI value obtained from the DCI field).

• The UE associates Vtemp2 as the corresponding t-DAI value to the next PDSCHs in the set that have the same PDSCH reception starting time as the first PDSCH, if any.

The UE continues the following procedures until all PDSCHs in the set are associated a t-DAI value and respecting modulo operation based on the bit-size of the t-DAI field: o Vtemp2 is increased by one. o The UE associates Vtemp2 as the corresponding t-DAI value to the next PDSCHs in the set that have the same PDSCH reception starting time as the earliest PDSCH without t-DAI association, if any.

[0075] The illustration in example in Figure 6 and Figure 7 explains the procedures described above.

[0076] When for each PDSCH in the set, the associated c-DAI value and T-DAI, if applicable, are determined, the legacy HARQ-ACK codebook constructions procedures, such as Type-1 HARQ-ACK codebook, or Type-2 HARQ-ACK code book, which ever applicable, are followed to construct the HARQ-ACK codebook.

[0077] In one embodiment, for a DCI configured to schedule multiple PDSCHs across cells, configuration of T-DAI field for a set can be omitted.

[0078] In one embodiment, for a DCI configured to schedule multiple PDSCHs across cells when configuration of T-DAI field for a set can be omitted, the DCI can be configured with two fields for c-DAI, for example the first c-DAI field as the legacy field for c-DAI and second c-DAI field replacing the T-DAI field. In this case, scheduling two sets of PDSCHs as described in previous embodiments is feasible without increasing the DCI overhead.

[0079] HARQ-ACK multiplexing in PUSCH when a single DCI scheduling multiple PUSCHs:

[0080] In one embodiment, when a single DCI schedules multiple PUSCHs and the DCI is configured with UL T-DAI field, the DCI can be configured with one UL T-DAI field. [0081] In one embodiment, when a single DCI schedules multiple PUSCHs and the DCI includes UL T-DAI field, the DCI can be configured with more than one UL-TDAI field. A configured UL T-DAI field by configuration is associated to a set of cell(s) for UL transmission in the cell group, or time durations for UL transmissions or combination of both.

[0082] When a configured UL T-DAI field is associated to more than one PUSCHs scheduled by a single DCI across cells, the value of the UL T-DAI is applicable for multiplexing of HARQ-ACK in any of the PUSCHs if that PUSCH is determined for HARQ- ACK multiplexing following the existing procedures. An example is shown in Figure 8.

[0083] Scheduling conditions for a single DCI scheduling multiple PDSCHs/PUSCH across cells:

In one embodiment, when a UE is scheduled by a DCI scheduling multiple PDSCHs across cells with resources for these PDSCHs transmissions within a time span, for example starting from tO and ending by tl, one of more of the following conditions, as well as their combinations may be applicable:

• the UE is not expected to detect a PDCCH with a DCI format that schedules another PDSCH(s) within the time span.

• the UE is not expected to detect a PDCCH with a DCI format that schedules another PDSCH(s) that starts after the earliest PDSCH in the set scheduled by a single DCI and its duration overlaps with the time span.

• the UE is not expected to detect a PDCCH with a DCI format that schedules another PDSCH(s) that starts before the last PDSCH in the set scheduled by a single DCI and its duration overlaps with the time span.

In one embodiment, when a UE is scheduled by a DCI scheduling multiple PDUCHs across cells with resources for these PUSCHs transmissions within a time span, for example starting from tO and ending by tl, one of more of the following conditions, as well as their combinations may be applicable:

• the UE is not expected to detect a PDCCH with a DCI format that schedules another PUSCH(s) within the time span.

• the UE is not expected to detect a PDCCH with a DCI format that schedules another PUSCH(s) that starts after the earliest PDSCH in the set scheduled by a single DCI and its duration overlaps with the time span.

• the UE is not expected to detect a PDCCH with a DCI format that schedules another PUSCH(s) that starts before the last PDSCH in the set scheduled by a single DCI and its duration overlaps with the time span. [0084] FIG. 9 is a flowchart of an example process in a wireless device QQ200 according to some embodiments of the present disclosure. One or more Blocks and/or functions performed by wireless device QQ200 may be performed by one or more elements of wireless device 22 such as processing circuitry QQ202, an input/output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, etc. In one or more embodiments, wireless device QQ200 such as via a processing circuitry QQ202, an input/output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212 is configured to receive (Block S201 ) a DCI, from a network node, configured to schedule multiple PDSCHs in at least two cells, as described herein. In one or more embodiments, In one or more embodiments, wireless device QQ200 such as via a processing circuitry QQ202, an input/output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212 is configured to transmit (Block S202) HARQ-ACK responses, to the network node, based on a set of PDSCHs from the PDSCHs scheduled by the DCI, where the HARQ-ACK responses associated with the PDSCHs in the set of PDSCHs set are in the same HARQ-ACK codebook and transmitted in the same PUCCH.

[0085] According to one or more embodiments, the transmitted HARQ-ACK responses are based on at least two sets of PDSCHs from the PDSCHs scheduled by the DCI, where each PDSCH set is associated to a HARQ-ACK codebook and to a PUCCH. According to one or more embodiments, the two sets of PDSCHs are scheduled on at least two different cells having different KO and/or KI values. According to one or more embodiments, the scheduling DCI is configured with a counter downlink assignment, c-DAI, field and/or a total DAI, t-DAI, field for each PDSCH set.

[0086] FIG. 10 is a flowchart of an example process in a network node QQ300 according to some embodiments of the present disclosure. One or more Blocks and/or functions performed by network node QQ300 may be performed by one or more elements of network node QQ300 such as by processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308 etc. In one or more embodiments, network node QQ300 such as via one or more of processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308 is configured to transmit (Block S301) a DCI, to a wireless device, configured to schedule multiple PDSCHs in at least two cells. In one or more embodiments, network node QQ300 such as via one or more of receiving a DCI, from a network node, configured to schedule multiple PDSCHs in at least two cells is configured to receive (Block S302) HARQ-ACK responses, from the wireless device QQ200, based on a set of PDSCHs from the PDSCHs scheduled by the DCI, where the HARQ-ACK responses associated with the PDSCHs in the set of PDSCHs set are in the same HARQ-ACK codebook and transmitted in the same PUCCH.

[0087] According to one or more embodiments, the received HARQ-ACK responses are based on at least two sets of PDSCHs from the PDSCHs scheduled by the DCI, where each PDSCH set is associated to a HARQ-ACK codebook and to a PUCCH. According to one or more embodiments, the two sets of PDSCHs are scheduled on at least two different cells having different KO and/or KI values. According to one or more embodiments, the scheduling DCI is configured with a counter downlink assignment, c-DAI, field and/or a total DAI, t-DAI, field for each PDSCH set.

[0088] Having generally described arrangements for HARQ-ACK codebook construction for single DCI scheduling multiple cells, details for these arrangements, functions and processes are provided as follows, and which may be implemented by the network node Q200, wireless device QQ300 and/or host computer QQ400.

[0089] Figure QQ1 shows an example of a communication system QQ100 in accordance with some embodiments.

[0090] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQl lOa and QQl lOb (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3 ^rd Generation Partnership Project (3GPP) access nodes or non- 3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and/or core network nodes QQ108.

[0091] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or anon-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0092] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, 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. The communication system QQ100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

[0093] The UEs QQ 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs QQ112 and/or with other network nodes or equipment in the telecommunication network QQ102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network QQ102.

[0094] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

[0095] The host QQ 116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and/or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0096] As a whole, the communication system QQ100 of Figure QQ1 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Micro wave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0097] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0098] In some examples, the UEs QQ112 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN- DC).

[0099] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and/or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices. [0100] The hub QQ114 may have a constant/persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and/or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and/or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and/or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node QQl lOb. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

[0101] Figure QQ2 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

[0102] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a 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). [0103] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input/output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure QQ2. 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.

[0104] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, 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 QQ202 may include multiple central processing units (CPUs).

[0105] In the example, the input/output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include 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. An input device may allow a user to capture information into the UE QQ200. Examples of an input device 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, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0106] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and/or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0107] The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0108] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), 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 tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and 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 as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0109] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and/or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0110] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, 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. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/intemet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0111] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0112] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input. [0113] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure QQ2.

[0114] As yet another specific example, in an loT scenario, a UE 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 UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

[0115] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. [0116] Figure QQ3 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication 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)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0117] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may 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, distributed units (e.g., in an O-RAN access node) 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).

[0118] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, 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), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).

[0119] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 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 NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) 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 QQ300.

[0120] The processing circuitry QQ302 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 QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

[0121] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 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 QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0122] The memory QQ304 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 computerexecutable memory devices that store information, data, and/or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and/or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0123] The communication interface QQ306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface QQ306 comprises port(s)/terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and/or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

[0124] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0125] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0126] The antenna QQ310, communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

[0127] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0128] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure QQ3 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 matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

[0129] Figure QQ4 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure QQ1, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

[0130] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input/output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures QQ2 and QQ3, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400. [0131] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FL AC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and/or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0132] Figure QQ5 is a block diagram illustrating a virtualization environment QQ500 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 any device described herein, 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. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0133] Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

[0134] Hardware QQ504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0135] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. 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.

[0136] In the context of NFV, a VM QQ508 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 the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502. [0137] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes 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 provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0138] Figure QQ6 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure QQ1 and/or UE QQ200 of Figure QQ2), network node (such as network node QQl lOa of Figure QQ1 and/or network node QQ300 of Figure QQ3), and host (such as host QQ116 of Figure QQ1 and/or host QQ400 of Figure QQ4) discussed in the preceding paragraphs will now be described with reference to Figure QQ6.

[0139] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

[0140] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure QQ1) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet. [0141] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

[0142] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0143] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

[0144] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0145] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may reduce complexity for HARQ-ACK codebooks when using a single DCI to schedule data in multiple cells. The embodiments provide examples on how to re-use legacy procedures for HARQ-ACK codebook construction and multiplexing without increasing the DCI overhead or changing legacy procedures when single DCI scheduling multiple cells are applied.

[0146] In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data. [0147] In some examples, 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 the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and/or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 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 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

[0148] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information 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. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0149] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 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 non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

Abbreviation Explanation

ACK Acknowledgment

ACK/NACK Acknowledgment/Not-acknowledgment

BWP Bandwidth Part

DCI Downlink Control Information

MIMO Multiple Input Multiple Output

NACK Not-acknowledgment

PDCCH Physical Downlink Control Channel

PDSCH Physical Shared Data Channel

PUCCH Physical Uplink Control Channel

TB Transport Block

UCI Uplink Control Information

SSB Synchronization Signal Block

SNR Signal to Noise Ratio

DRX Discontinuous Reception

PO Paging Occasion

MCS Modulation and Coding Scheme

SE Spectral efficiency

PRB Physical Resource Block

PPM Parts Per Million

TRS Tracking Reference Signal or CSI-RS for tracking

CSI-RS Channel State Information Reference Signal

SFN System Frame Number

SI System Information

A-TRS Aperiodic TRS EMBODIMENTS

Group A Embodiments

1. A method performed by a user equipment, UE, for a HARQ-ACK codebook for single downlink control information, DCI, scheduling multiple cells, the method comprising: receiving (201) a DCI, from a network node, configured to schedule multiple PDSCHs in at least two cells; transmitting (202) HARQ-ACK responses, to the network node, based on a set of PDSCHs from the PDSCHs scheduled by the DCI, wherein the HARQ-ACK responses associated with the PDSCHs in the set of PDSCHs set are in the same HARQ-ACK codebook and transmitted in the same PUCCH.

2. The method of embodiment 1 wherein the transmitted HARQ-ACK responses, to the network node, are based on at least two sets of PDSCHs from the PDSCHs scheduled by the DCI, wherein each PDSCH set is associated to a HARQ-ACK codebook and to a PUCCH.

3. The method of any of embodiments 2, wherein the two sets of PDSCHs are scheduled on at least two different cells having different KO values.

4. The method of any of embodiment 2, wherein the two sets of PDSCHs are scheduled on at least two different cells having different KI values.

5. The method of any of embodiments 2-4, wherein the at least two HARQ-ACK codebooks associated with the two different sets of PDSCHs are different HARQ-ACK codebooks.

6. The method of any embodiments 2-4, wherein the at least two PUCCHs associated with the two different sets of PDSCHs are different PUCCHs.

7. The method of any of embodiments 1-6, wherein the scheduling DCI is configured with a counter downlink assignment, c-DAI, field and/or a total DAI, t-DAI, field for each PDSCH set.

8. The method of embodiment 7, wherein the UE determines the number of PDSCHs in a set and wherein for each PDSCH in the set, the UE determines a corresponding c-DAI and/or t-DAI value. 9. The method of embodiment 8, wherein the UE orders the PDSCHs in a PDSCH set based on the scheduled cell index and/or the PDSCH reception starting time.

10. The method of any of embodiments 7-9, wherein the UE determines the value of the c- D Al from DCI.

11. The method of embodiment 10, wherein the c-DAI value for the first PDSCH in a PDSCH set is initiated by the c-DAI value that is obtained from the DCI field.

12. The method of embodiment 11, wherein the UE assigns a c-DAI to the next PDSCH in the PDSCH set by increasing the c-DAI with 1, and wherein the next PDSCH is determined based on, firstly, ascending order of cell index and, secondly, on ascending order of PDSCH starting time.

13. The method of any of embodiments 7-9, wherein the UE determines the value of the t- D Al from DCI.

14. The method of embodiment 13, wherein the t-DAI value for the first PDSCH in a PDSCH set is initiated by the t-DAI value that is obtained from the DCI field.

15. The method of embodiment 14, wherein the UE assigns corresponding t-DAI value to the next PDSCHs in the set that have the same PDSCH reception starting time as the first PDSCH is set.

16. The method of embodiment 15, wherein the t-DAI value for the last PDSCH in a set is initiated by the t-DAI value that is obtained from the DCI field.

17. The method of embodiment 15, wherein the UE assigns corresponding t-DAI value to the next PDSCHs in the set that have the same PDSCH reception starting time as the last PDSCH is set.

18. The method of embodiment 1, wherein the maximum number of sets is configured by RRC signaling. 19. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

Group B Embodiments

20. A method performed by a network node for a HARQ-ACK codebook for single downlink control information, DCI, scheduling multiple cells, the method comprising: transmitting (301) a DCI, to a UE, configured to schedule multiple PDSCHs in at least two cells; receiving (302) HARQ-ACK responses, from the UE, based on a set of PDSCHs from the PDSCHs scheduled by the DCI, wherein the HARQ-ACK responses associated with the PDSCHs in the set of PDSCHs set are in the same HARQ-ACK codebook and transmitted in the same PUCCH.

21. The method of embodiment 20, wherein the received HARQ-ACK responses, to the network node, are based on at least two sets of PDSCHs from the PDSCHs scheduled by the DCI, wherein each PDSCH set is associated to a HARQ-ACK codebook and to a PUCCH.

22. The method of any of embodiments 21, wherein the two sets of PDSCHs are scheduled on at least two different cells having different KO values.

23. The method of any of embodiment 21, wherein the two sets of PDSCHs are scheduled on at least two different cells having different KI values.

24. The method of any of embodiments 21-23, wherein the at least two HARQ-ACK codebooks associated with the two different sets of PDSCHs are different HARQ-ACK codebooks.

25. The method of any embodiments 21-23, wherein the at least two PUCCHs associated with the two different sets of PDSCHs are different PUCCHs.

26. The method of any of embodiments 20-25, wherein the scheduling DCI is configured with a counter downlink assignment, c-DAI, field and/or a total DAI, t-DAI, field for each PDSCH set.

27. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

Group C Embodiments

28. A user equipment for a HARQ-ACK codebook for single downlink control information, DCI, scheduling multiple cells , comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

29. A network node for a HARQ-ACK codebook for single downlink control information, DCI, scheduling multiple cells , the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.

30. A user equipment (UE) for a HARQ-ACK codebook for single downlink control information, DCI, scheduling multiple cells , the 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 the Group A embodiments; 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. 31. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

32. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

33. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

34. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

35. The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

36. A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

37. The communication system of the previous embodiment, further comprising: the network node; and/or the UE.

38. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.

39. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

40. The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

41. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host. 42. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

43. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the operations of any of the Group A embodiments to receive the user data from the host.

44. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

45. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

46. A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.

47. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the host application.

48. The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

49. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.

50. The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

51. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

52. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.

53. The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE. 54. The method of the previous 2 embodiments, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.