EP4666774A1

EP4666774A1 - Mac pdu generation for multiple configured grant transmission occasions

Info

Publication number: EP4666774A1
Application number: EP24707988.2A
Authority: EP
Inventors: Bikramjit Singh; Jonas FRÖBERG OLSSON; Robert Karlsson
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-02-17
Filing date: 2024-02-16
Publication date: 2025-12-24
Also published as: WO2024172748A1

Abstract

A method performed by a UE is provided The method includes generating (800) a plurality of media access control (MAC) protocol data units (PDUs), for a sub-set of a plurality of transmission occasions in a group. The group includes the plurality of transmission occasions from one or more periods of one or more configured grants. The method further includes transmitting (802), based on the generated plurality of MAC PDUs, on the sub-set of the plurality of transmission occasions without skipping one or more uplink transmissions between transmissions in the subset of transmissions. Related methods and apparatus are also provided.

Description

MAC PDU GENERATION FOR MULTIPLE CONFIGURED GRANT TRANSMISSION OCCASIONS

TECHNICAL FIELD

[0001] The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.

BACKGROUND

[0002] Extended reality (XR) data transmission can have the following characteristics: Application data can be generated at a constant frames per second (FPS) (e.g., a periodical generation); downlink (DL) data can be jittery, but uplink (UL) can have optional jitter; packet sizes can be big, but volume may not be fixed (e.g., random or follow a distribution); and/or latency can be bounded (e.g., 10 to few dozens of ms).

[0003] Based on such XR characteristics, the Third Generation Partnership Project (3GPP) agreed in a work item description (WID) to specify functionality for Release 18, including:

- Enhanced discontinuous reception (DRX) for power saving o This is due to, for example, packets sizes (e.g., volume) being big and arrival rate can be frequent. Thus, a user equipment (UE) may require large processing power in order to monitor downlink control information (DCIs) for both UL and DL resource allocation, which can negatively impact battery or power usage.

Support big packet transmission o 3 GPP agreed in the WID to enhance configured grant (CG) by adding multiple occasions per period to support big packet transmissions which can arrive periodically.

[0004] There currently exist certain challenges. Currently, in 3GPP Release 17, only one physical uplink shared channel (PUSCH) (or a single start and length indicator value (SLIV)/transmission occasion (TO)) is allowed per CG period. For an XR use case, for example, the packet volume can be large. While 3GPP agreed in a WID for Release 18 to add multiple occasions per period, handling such multiple occasions is lacking. SUMMARY

[0005] Currently, in 3 GPP for example, multiple transport occasions (e.g., PUSCHs) per CG period are not provided and behavior is not defined on how data (e.g., multiple transport blocks (TBs)) can be transmitted over such multiple transport occasions.

[0006] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Examples of the present disclosure include that a UE can transmit on sub-set of transmission occasions (e.g., PUSCHs) in a period having multiple transmission occasions per period without skipping an uplink transmission(s) in between the transmissions. The UE can generate medium access protocol (MAC) protocol data units (PDUs) from data for a group of transmission occasions (e.g., PUSCHs) without skipping uplink in between. The data can be based on burst data, PDU set, or a single XR packet, for example. In some examples, skipping uplink can be performed before the first and/or last transmission.

[0007] A method performed by a UE is provided. The method includes generating a plurality of MAC PDUs for a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants. The method further includes transmitting, based on the generated plurality of MAC PDUs, on the sub-set of the plurality of transmission occasions without skipping one or more uplink transmissions between transmissions in the subset of transmissions. [0008] In some embodiments, the method further includes skipping an uplink transmission before a first uplink transmission in the subset of transmissions.

[0009] In some embodiments, the method further includes skipping an uplink transmission after a last uplink transmission in the subset of transmissions.

[0010] In some embodiments, the method further includes skipping a further uplink transmission in the group after the subset of transmissions; and omitting to further transmit over the group based on the skipping the further uplink transmission in the group.

[0011] In some embodiments, a generated MAC PDU is for a hybrid automatic repeat request, HARQ, process in a period of a configured grant associated with the group, and the method further includes skipping a further uplink transmission for a next HARQ process in the period; and omitting to generate a further MAC PDU for a HARQ entity for remaining HARQ processes in the period when a parameter is enabled.

[0012] In some embodiments, one or more of the plurality of transmission occasions includes control information that the UE is not allowed to skip and when the one or more of the plurality of transmission occasions that includes control information has no data, the method further comprises filling the one or more of the plurality of transmission occasions with dummy data or padding bits. [0013] In some embodiments, the group including the plurality of transmission occasions comprises at least one of a first type of configured grant and a second type of configured grant for multiple-physical uplink shared channel, PUSCH, configured grant transmissions; and the method further includes an activation downlink control information, DCI, for the multiple-PUSCH configured grant, the activation DCI comprising a time domain resource assignment field that indicates that more than one PUSCH or one start and length indicator value, SLIV, can be allocated.

[0014] A method performed by a network node is provided. The method includes receiving, from a UE, a sub-set of a plurality of transmission occasions in a group. The group includes the plurality of transmission occasions from one or more periods of one or more configured grants. The method further includes performing one of (i) decoding data from the sub-set of the plurality of transmission occasions in the group, and (ii) omitting to decode data from at least one transmission occasion in the sub-set of the plurality of transmission occasions in the group and, based on the omitting, sending a retransmission grant to the UE.

[0015] A UE is provided. The UE includes processing circuitry; and memory coupled with the processing circuitry. The memory includes instructions that when executed by the processing circuitry causes the UE to perform operations. The operations include to generate a plurality of MAC PDUs for a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants. The operations further includes to transmit, based on the generated plurality of MAC PDUs, on the sub-set of the plurality of transmission occasions without skipping one or more uplink transmissions between transmissions in the subset of transmissions.

[0016] A non-transitory computer readable medium is provided. The non-transitory computer readable medium includes program code to be executed by processing circuitry of a UE. Execution of the program code causes the program code to perform operations. The operations include to generate a plurality of MAC PDUs for a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants. The operations further includes to transmit, based on the generated plurality of MAC PDUs, on the sub-set of the plurality of transmission occasions without skipping one or more uplink transmissions between transmissions in the subset of transmissions.

[0017] A method implemented by a host operating in a communication system that further includes a network node and a UE is provided. The method includes 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. The UE performs the following operations to receive the user data from the host: Generating a plurality of MAC PDUs for a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants; and transmitting, based on the generated plurality of MAC PDUs, on the sub-set of the plurality of transmission occasions without skipping one or more uplink transmissions between transmissions in the subset of transmissions.

[0018] A host configured to operate in a communication system to provide over-the-top, OTT, service is provided. The host includes processing circuitry configured to provide user data. The host further includes a network interface configured to initiate transmission of the user data to a cellular network for transmission to a UE. The UE comprises a communication interface and processing circuitry. The communication interface and processing circuitry of the UE being configured to perform the following operations to receive the user data from the host: Generate a plurality of MAC PDUs, for a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants; and transmit, based on the generated plurality of MAC PDUs, on the subset of the plurality of transmission occasions without skipping one or more uplink transmissions between transmissions in the subset of transmissions.

[0019] A network node is provided. The network node includes processing circuitry; and memory coupled with the processing circuitry. The memory includes instructions that when executed by the processing circuitry causes the network node to perform operations including to receive, from a UE, a sub-set of a plurality of transmission occasions in a group. The group includes the plurality of transmission occasions from one or more periods of one or more configured grants. The operations further include to perform one of (i) decoding data from the subset of the plurality of transmission occasions in the group, and (ii) omitting to decode data from at least one transmission occasion in the sub-set of the plurality of transmission occasions in the group and, based on the omitting, sending a retransmission grant to the UE.

[0020] A non-transitory computer readable medium is provided. The non-transitory computer readable medium includes program code to be executed by processing circuitry of a network node. Execution of the program code causes the program code to perform operations. The operations include to receive, from a UE, a sub-set of a plurality of transmission occasions in a group. The group includes the plurality of transmission occasions from one or more periods of one or more configured grants. The operations further include to perform one of (i) decoding data from the subset of the plurality of transmission occasions in the group, and (ii) omitting to decode data from at least one transmission occasion in the sub-set of the plurality of transmission occasions in the group and, based on the omitting, sending a retransmission grant to the UE.

[0021] A method implemented by a host operating in a communication system that further includes a network node and a UE is provided. The method includes 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. The network node performs the following operations: receive, from the UE, a sub-set of a plurality of transmission occasions in a group. The group includes the plurality of transmission occasions from one or more periods of one or more configured grants; and perform one of (i) decoding data from the sub-set of the plurality of transmission occasions in the group, and (ii) omitting to decode data from at least one transmission occasion in the sub-set of the plurality of transmission occasions in the group and, based on the omitting, sending a retransmission grant to the UE.

[0022] A host configured to operate in a communication system to provide an over-the-top, OTT, service is provided. The host includes processing circuitry configured to provide user data; and a network interface configured to initiate transmissions of the user data to a network node in a cellular network for transmission to UEs. The network node having a communication interface and processing circuitry. The processing circuitry of the network node is configured to perform the following operations: Receive, from a UE, a sub-set of a plurality of transmission occasions in a group. The group includes the plurality of transmission occasions from one or more periods of one or more configured grants; and perform one of (i) decoding data from the sub-set of the plurality of transmission occasions in the group, and (ii) omitting to decode data from at least one transmission occasion in the sub-set of the plurality of transmission occasions in the group and, based on the omitting, sending a retransmission grant to the UE.

[0023] Certain embodiments may provide one or more of the following technical advantage(s). Based on inclusion of a UE that can transmit on a sub-set of transmission occasions in a configured grant period, decoding at a network node (e.g., gNodeB (gNB)) to detect transmitted data may be improved. In the absence of such UE behavior, for example, a network node may perform a blind decode of each transmission occasion. If decoding fails, the network node may not know if there is data (e.g., a TB) or not. With such uncertainty, the network node may or may not send a retransmission grant for a hybrid automatic repeat request (HARQ) process associated with a transmission occasion (e.g., PUSCH) where the network node failed to decode a TB. Accordingly, such uncertainty can have a consequence either on an error rate (e.g., if a retransmission grant is not sent) or on capacity wastage due to unnecessary retransmission grant allocations. [0024] Based on inclusion of a UE that can transmit on a sub-set of transmission occasions in a configured grant period, however, if the network node decodes some data (e.g., a TB such as TB#1 or PUSCH 1) and other data (e.g., another TB on a different PUSCH such TB#n on PUSCH#n) in the same configured grant period, then the network node can know that all the transmission occasions (e.g., PUSCHs) in between two transmission occasions (e.g., PUSCHs) have data (e.g., TBs) as the UE is not allowed to skip uplink. Thus, if the network node cannot decode some data (e.g., TBs) from PUSCH 2 to PUSCH#n-l, for example, then the network node can send a retransmission grant with certainty.

BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

[0026] Figure 1 is a schematic diagram illustrating an example of a configured grant allocation with repeated allocation in a period according to some embodiments;

[0027] Figure 2 is a schematic diagram illustrating an example of a UE transmission on three PUSCHs without skipping UL in between according to some embodiments;

[0028] Figure 3 is a schematic diagram illustrating an example of a UE transmission on three PUSCHs without skipping UL in between in one time window, and in a next time window, the UE transmits on two PUSCHs without skipping UL in between, where the PUSCHs belong to different configured grants, according to some embodiments;

[0029] Figure 4 is a schematic diagram illustrating an example of a UE transmission on three PUSCHs without skipping UL in between according to some embodiments;

[0030] Figure 5 is a schematic diagram illustrating an example of a UE that is not allowed to transmit again in the same period after skipping uplink according to some embodiments;

[0031] Figure 6 is a schematic diagram illustrating an example of a UE that is not allowed to transmit on PUSCHs after skipping UL on the PUSCH group except on PUSCHs that have a uplink control information (UCI) resource allocation according to some embodiments;

[0032] Figure 7 is a schematic diagram illustrating an example of a UE that transmits on some PUSCHs with data (if available) or dummy data/padding bits according to some embodiments;

[0033] Figures 8-11 are flow charts illustrating operations of a UE according to some embodiments; [0034] Figure 12 is a flow chart illustrating operations of a network node according to some embodiments;

[0035] Figure 13 is a block diagram of a communication system in accordance with some embodiments;

[0036] Figure 14 is a block diagram of a UE in accordance with some embodiments;

[0037] Figure 15 is a block diagram of a network node in accordance with some embodiments;

[0038] Figure 16 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments;

[0039] Figure 17 is a block diagram of a virtualization environment in accordance with some embodiments; and

[0040] Figure 18 is a block diagram of a host computer communicating via a base station with a UE over a partially wireless connection in accordance with some embodiments.

DETAILED DESCRIPTION

[0041] 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, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

[0042] In radio access network (RAN) 3 GPP plenary meeting RAN#98-e in December 2022, RP-223502, the following objectives were agreed for specifying related functionality in Release-18:

Objective of study item (SI) or core part work item (WI) or testing part WI

Specify the enhancements related to power saving:

DRX support of XR frame rates corresponding to non-integer periodicities (through at least semi-static mechanisms e.g., radio resource control (RRC) signalling) (RAN2). Specify the enhancements related to capacity:

Multiple CG PUSCH transmission occasions in a period of a single CG PUSCH configuration (RANI, RAN2);

Dynamic indication of unused CG PUSCH occasion(s) based on UCI by the UE (RANI);

BSR (buffer status report) enhancements including at least new BS (buffer status) Table(s); (RAN2);

Delay reporting of buffered data in uplink; (RAN2);

Provision of XR traffic assistance information for DL and UL (e.g., periodicity); (RAN2);

Discard operation of PDU Sets (RAN2). . .

[0043] Currently, in Release 17, only one PUSCH (or single SLIV/TO) is allowed per CG period. Release 17 does not include multiple PUSCHs per CG period and, thus, does not include behavior defining how, e.g., multiple TBs can be transmitted over multiple PUSCHs. See e.g., 3GPP TS 38.321 V17.3.0 (December 2022); 3GPP TS 38.214 V17.4.0 (December 2022).

[0044] Release 18 seeks to enhance CG where its period can have more than single PUSCH allocation, for example. For an example XR use case, the packet volume can be large, which can be broken down to multiple TBs which can be pushed over multiple PUSCHs in CG (e.g., within the same period).

[0045] Thus, in the absence of operations (e.g., a rule(s) as discussed further herein) addressing how, e.g., multiple TBs can be transmitted over multiple PUSCHs, there may be a burden at a network node side. That is, the network node may not know whether a UE has transmitted its TBs (or the UE has skipped uplink) on each PUSCH or not (within a period). If random behavior from the UE is allowed, then the network node may have to employ excessive blind decoding to decode PUSCHs from a group of PUSCHs allocated in a period. This challenge can also impact retransmission probability, because if the network node cannot decode a TB (whether there was an actual TB or a skip uplink), then the network node may need to decide (e.g., based on implementation algorithms), whether to send a retransmission grant. In other words, the more uncertainty there is related to transmissions over PUSCHs in a CG period, the more uncertainty there may be related to a retransmission grant decision if the TB is not decoded. [0046] It is noted that this challenge also can be extended to multiple CGs allocated in such a manner (e.g., their transmission occasions (TOs)ZPUSCH allocations can be used to support big packet transmission by breaking it into multiple TBs transmitted over multiple PUSCHs).

[0047] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In examples of the present disclosure, a UE can transmit on a sub-set of transmission occasions (e.g., PUSCHs) in the period without skipping an uplink transmission(s) in between the transmissions. The UE can generate MAC PDUs from data for a group of transmission occasions (e.g., PUSCHs) without skipping uplink in between. The data can be based on burst data, PDU set, or single XR packet, for example. In some examples, skipping uplink can be performed before the first and/or last transmission. In some embodiments, the MAC PDU generations can be pushed to a physical (PHY) layer for their retransmission (e.g., as TBs) over multiple PUSCHs and, thus, impact/improve decoding and a retransmission grant decision at the network node side.

[0048] As referred to herein, a “period” refers to the time duration or window indicated by periodicity parameter, for example, such as in ConfiguredGrantConfig. For example, in a period, a PUSCH is allocated (and has an associated HARQ ID). Thus, after the end of the period, the next period starts with the same duration with a new PUSCH allocation (for which a HARQ ID can be the same or different) with a relatively similar repetitive resource allocation as of other PUSCHs in previous periods. Figure 1 is a schematic diagram illustrating an example of a configured grant allocation with repeated allocation in a period according to some embodiments. In the example of Figure 1, a CG allocation 100 with a repeated allocation is shown (that is, a PUSCH allocation 102a, 102b, 102c, 102d in a defined period (CG period #N, CG period #(N+1), CG period #(N+2)) as shown), where a period is defined by a parameter (e.g., periodicity 104 in ConfiguredGrantConfig).

[0049] Further as referred to herein, the term “configured grant (CG) with multiple transmission occasions (TOs) per period” is used in a non-limiting manner and can refer to, and may be interchangeable and replaced with, the terms “CG with multiple PUSCHs per period”, “multi-PUSCH CG”, “multi-HARQ CG”, “multi-TB CG”, “multi-occasion CG”, “multi-slot CG”, “multi-SLIV CG”, “transmission occasions allocated in a configured grant”, etc.; and refers to a CG period allocated with multiple TOs/PUSCHs/SLIVs/HARQ processes/TB resources, etc. The term “PUSCH” herein may be interchangeable and replaced with the terms “HARQ”, “SLIV”, or “TB”.

[0050] While some embodiments herein are explained in the non-limiting context of skip uplink enabled, other embodiments include operations where or on which skip uplink can be performed. In other words, restrictions on top of skip uplink behavior are included in such embodiments.

[0051] Moreover, in some examples herein, when multiple periods are defined (e.g., by a parameter such as ConfiguredGrantConfiguration), one period may be referred to as CG cl and another period may be referred to as CG c2, etc.

[0052] As previously indicated, certain embodiments may provide one or more of the following technical advantage(s). Based on inclusion of a UE that can transmit on a sub-set of transmission occasions in a configured grant period, decoding at a network node (e.g., gNB) to detect transmitted data may be improved. In the absence of such UE behavior, for example, a network node may perform a blind decode of each transmission occasion. If decoding fails, the network node may not know if there is data (e.g., a TB) or not. With such uncertainty, the network node may or may not send a retransmission grant for a HARQ process associated with a transmission occasion (e.g., PUSCH) where the network node failed to decode a TB. Accordingly, such uncertainty can have a consequence either on an error rate (e.g., if a retransmission grant is not sent) or on capacity wastage due to unnecessary retransmission grant allocations.

[0053] Based on inclusion of a UE that can transmit on a sub-set of transmission occasions in a configured grant period, however, if the network node decodes some data (e.g., a TB such as TB#1 or PUSCH 1) and other data (e.g., another TB on a different PUSCH such TB#n on PUSCH#n) in the same configured grant period, then the network node can know that all the transmission occasions (e.g., PUSCHs) in between two transmission occasions (e.g., PUSCHs) have data (e.g., TBs) as the UE is not allowed to skip uplink. Thus, if the network node cannot decode some data (e.g., TBs) from PUSCH 2 to PUSCH#n-l, for example, then the network node can send a retransmission grant with certainty.

[0054] In one example, the MAC PDUs are generated in such a manner that all the TBs which are packed from MAC PDUs must be transmitted together, that is, there is no skip uplink between the first TB transmission and the last TB transmission while transmitting over a group of TOs. It is noted that a group of PUSCHs (resource allocation) can recur with time. Thus, after doing the last transmission in some group of PUSCHs, the UE is free to transmit again (e.g., start with a first TB transmission) in the next group of PUSCHs without skipping uplink in between if the UE has data to transmit.

[0055] Some embodiments are directed to a method performed by a UE (e.g., the UE 1400 of Figure 14). For example, modules may be stored in memory 1410 of Figure 14, and these modules may provide instructions so that when the instructions of a module are executed by respective UE processing circuitry 1402, processing circuitry 1402 performs respective operations of the flow chart of Figure 8. As illustrated in Figure 8, a method performed by a UE includes generating (800) a plurality of MAC PDUs for a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants. The method further includes transmitting (802), based on the generated plurality of MAC PDUs, on the sub-set of the plurality of transmission occasions without skipping one or more uplink transmissions between transmissions in the subset of transmissions.

[0056] In another example, the group of TOs/PUSCHs belong to a same period in a multi- PUSCH CG. For example, Figure 2 shows an example where a group includes four PUSCHs 202a, 202b, 202c, 202d in a CG period 200. In Figure 2, the UE transmits on PUSCHs 202a, 202b, 202c without skipping uplink in between.

[0057] It is noted that in Figures 2-7, the diagonally patterned boxes represent TB transmission over PUSCH, and the non-patterned boxes represent a skip uplink (in other words, no transmission over PUSCH).

[0058] Multi-PUSCH CG characteristics are further discussed herein, but can include (without limitation) a tie to a higher layer (HL) parameter, such as a multi PUSCH CG parameter or an existing parameter based on pusch-TimeDomainAllocationListForMultiPUSCH, for example.

[0059] Referring again to the example in Figure 2, there can be different periods of the same CG. In Figure 2, a group can be defined of eight PUSCHs 202a, 202b, 202c, 202d, 204a, 204b, 204c, 204d that form two consecutive periods 200 as shown. It is noted that the CG can be a legacy CG with one PUSCH allocation per CG period. Thus, for example, a network can define a group of eight PUSCHs from eight consecutive periods with a legacy CG as there can be only one PUSCH per period.

[0060] There can be different CGs with the PUSCHs grouped together. For example, Figure 3 shows an example where a UE transmits on three PUSCHs 302a, 302b, 302c without skipping uplink in between in one time window 300 and, in the next time window 300, the UE transmits on two PUSCHs 304b, 304c without skipping uplink in between, where the PUSCHs belong to different CGs 300 and 302. The CGs can be multi-PUSCH CG, legacy CG, or mix of them. In the example of Figure3, a PUSCH group is formed using five PUSCHs 302a, 302b, 302c, 304b, 304c (one (302a) from legacy CG (with one PUSCH allocation per period) and four (302b, 302c, 304b, 304c) from multi-PUSCH CG). In Figure 3, for example, the UE transmits on selected PUSCHs in a group without UL skipping in between. The network can define a policy defining how to organize PUSCHs in a group. One example policy is that the PUSCHs lie close to each other, e.g., if the gap between PUSCHs is less than S symbols, then the PUSCHs are assumed to be a part of a group.

[0061] In one embodiment, for example, a group that includes the plurality of transmission occasions belongs to at least one of: (i) a same period in one configured grant, (ii) at least two different periods of one configured grant, and (iii) at least two periods for at least two different configured grants.

[0062] In another example, the UE is allowed to skip uplink before the first TB transmission. In Figure 4, for example, the UE is allowed to skip uplink 402a before the first TB transmission 402b. In some embodiments, the method further includes skipping (operation 804 in Figure 8) an uplink transmission before a first uplink transmission in the subset of transmissions.

[0063] In another example, as shown in the examples of Figures 2 and 4, the UE is allowed to skip uplink after a last TB transmission. In Figure 2, the UE is allowed to skip uplink 202d after the last data transmission over PUSCH 202c. In Figure 4, the UE is allowed to skip uplink 402e, 402f after the last data transmission over PUSCH 402d. In some embodiments, the method further includes skipping (operation 806 in Figure 8) an uplink transmission after a last uplink transmission in the subset of transmissions.

[0064] In yet another example, the UE is not allowed to transmit over the group of PUSCHs, if it has transmitted (e.g., TB(s)) already in the same group and afterwards has skipped uplink in the same group. In other words, the UE does not generate MAC PDUs after the skip uplink which is after the TB transmission within the same group, as shown in the example in Figure 5. In Figure 5, a group is six PUSCHs in a CG period: a first group of PUSCHs 502a, 502b, 502c, 502d, 502e, 502f in CG a first period 300, and a second group of PUSCHs 504a, 504b, 504c, 504d, 504e, 504f in a second period 300. In Figure 5, the UE does not generate MAC PDUs after the skip uplink 502d, 502e, 502f which is after the TB transmission 502c within the same first group; and the UE does not generate MAC PDUs after the skip uplink 504e, 504f which is after the TB transmission 504d within the same second group.

[0065] Referring to Figure 9, in some embodiments for example, the method further includes skipping (900) a further uplink transmission in the group after the subset of transmissions; and omitting (902) to further transmit over the group based on the skipping the further uplink transmission in the group.

[0066] In a further example, the MAC specifies, for e.g., UE behavior to skip generation of PDUs based on above examples, especially for a case with multi-PUSCH CG. For example: The MAC entity shall: l>if the MAC entity is configured with enhancedSkipUplinkTxDynamic with value true and the grant indicated to the HARQ entity was addressed to a C-RNTI, or if the MAC entity is configured with enhancedSkipUplinkTxConfigured with value true and the grant indicated to the HARQ entity is a configured uplink grant:

2> if there is no UCI to be multiplexed on this PUSCH transmission as specified in TS 38.213 [6]; and

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

2> if the MAC PDU includes zero MAC SDUs; and

2> if the MAC PDU includes only the periodic BSR and there is no data available for any LCG, or the MAC PDU includes only the padding BSR:

2> if the MAC PDU is generated for a given HARQ process in a configured grant period associated with <MultiPUSCHCG> and UE has skipped the uplink (did not generate MAC PDU) for next HARQ process in the same period, then for the remaining HARQ processes in the same period and Capability parameter> is enabled, then UE must:

3>not generate a MAC PDU for the HARQ entity. l>else if the MAC entity is configured with skipUplinkTxDynamic with value true and the grant indicated to the HARQ entity was addressed to a C-RNTI, or the grant indicated to the HARQ entity is a configured uplink grant:

2> if the MAC PDU includes zero MAC SDUs; and

3> not generate a MAC PDU for the HARQ entity.

[0067] For example referring to Figure 10, in some embodiments, a generated MAC PDU is for a hybrid automatic repeat request, HARQ, process in a period of a configured grant associated with the group, and the method further includes skipping (1000) a further uplink transmission for a next HARQ process in the period; and omitting (1002) to generate a further MAC PDU for a HARQ entity for remaining HARQ processes in the period when a parameter is enabled.

[0068] In another example, there can be a capability that permits a UE to transmit TBs over PUSCHs (or generate MAC PDUs) without skipping uplink. In other words, if the capability is enabled, the UE must transmit over a group of PUSCHs without skipping uplink. If the capability is disabled, the UE can transmit TBs over a group of PUSCHs with skipping uplink. As discussed herein, this capability can be tied with a capability parameter. For example, referring to Figure 8, in some embodiments, transmitting (802) without skipping is enabled based on a parameter.

[0069] In a further example, if certain PUSCHs are required to transmit some control information (e.g., MAC CEs or UCIs), then the UE cannot skip TBs or MAC PDUs for such PUSCHs. For example, as shown in the example in Figure 6, the UE is not allowed to transmit on PUSCHs 602g, 602h after skipping UL 602d, 602e on the PUSCH group except on PUSCH 602f which has a UCI resource allocation (e.g., multiplexed or non-multiplexed). For such a PUSCHs, the UE can include data alongside control information, and if there is no data, then the UE can fill the TB with padding bits. It is noted that, from any last transmission in the group, if the UE has skipped the UL in the next transmission (e.g., PUSCH 602d (which can include, e.g., HARQ ID X+3), then the UE cannot transmit in the remaining PUSCHs ( PUSCH 602e (which can include, e.g., HARQ ID#X+4 to PUSCH 602h (which can include, e.g., HARQ ID X+7) except PUSCH 602f (which can include, e.g., HARQ ID X+5) where control information transmission is included. UCI can be, e.g., HARQ-acknowledgement (ACK), channel state information (CSI), CG-UCI, or dynamic indication of unused CG PUSCH occasion(s).

[0070] Referring to Figure 11, in some embodiments for example, one or more of the plurality of transmission occasions includes control information that the UE is not allowed to skip and when the one or more of the plurality of transmission occasions that includes control information has no data, the method further includes filling (1100) the one or more of the plurality of transmission occasions with dummy data or padding bits.

[0071] In another example, if the UE does not have data, the UE skips uplink (e.g., on PUSCH 602d (which can include, e.g., HARQ ID#X+3) in Figure 6). However, there is a UCI resource allocated on the incoming PUSCH (e.g., PUSCH 702f (which can include, e.g., HARQ ID X+5, in Figure 7), then the UE transmits on all PUSCHs 702d, 702e, 702f from the last data transmission (702c which can include, e.g., HARQ ID#X+2) to the PUSCH with the UCI resource (702f which can include, e.g., HARQ ID X+5). The difference between Figures 6 and 7 is that in Figure 7, the UE transmits on PUSCHs 702d, 702e, 702f with data (if available) or dummy data/padding bits. In Figure 7, the vertically patterned boxes represent transmission of data (if available) or dummy data/padding bits).

[0072] Referring to Figure 11, in some embodiments for example, when the one or more of the plurality of transmission occasions that includes control information has no data, the subset of transmissions includes all transmission occasions between a last transmission on the subset of transmissions and the one or more of the plurality of transmission occasions that includes control information.

[0073] In another example, the UE can generate MAC PDUs and a corresponding TB to a lower layer for N PUSCH transmissions, where the n-th PUSCH is before (in time) the (n+l)-th PUSCH, n = 0, ... , N — 2, and wherein the UE generates MAC PDUs and delivers corresponding TBs to the lower layer for the n-L-th and n₂-th PUSCH, n₂ + 2 , then UE generates MAC PDUs and delivers corresponding TBs to the lower layer for m = n + 1, ... , n₂. In some embodiments, for example, the UE provides the generated MAC PDUs to a lower layer for a number, N, of the sub-set of transmission occasions in time, wherein a time of an n-th transmission occasion is before a (n+l)-th transmission occasion, n = 0, . . ., N-2; and wherein the UE delivers corresponding portions of data to the lower layer for an m-th and -th transmission occasion, where m > ni +2; and the UE generates further MAC PDUs and delivers the further generated MAC PDUs and corresponding portions of data to the lower layer for times corresponding to m, m +1, . . . m.

[0074] N can be a configured value. Alternatively, N PUSCHs can be the PUSCHs in a multi-PUSCH transmission, such as a dynamic multi-PUSCH or a configured grant rnulti- PUSCH. Further, the N PUSCHs can be any N sequential PUSCHs assigned to the UE; the N PUSCHs can be any N sequential PUSCHs for one or more configured grant configurations; or the N PUSCHs can be any N sequential PUSCHs for at most M periods of one or more configured grant configurations.

[0075] In a further example, the UE does not generate MAC PDUs for k = n₂ + 1, ... , N — 1, if the UE has skipped UL at least for n₂ + 1. In some embodiments, for example, the UE omits generating MAC PDUs for times corresponding to +1, . . ., N-l when the UE skipped an uplink transmission for at least m + 1.

[0076] In one example, must be 0. In some embodiments, m is zero.

[0077] In another example, the N PUSCHs is determined by a timer T. In some examples, T is started at the first CG PUSCH occasion of a configured grant configuration and the N PUSCHs are the CG PUSCH occasions present during which the timer is running. When timer T expires, the UE re-starts T. In some embodiments, for example, the group including the plurality of transmission occasions has a number of transmission occasions determined by a timer.

[0078] Multi-PUSCH CG transmissions are now discussed further.

[0079] In one example, in an activation downlink control information (DCI) for CG (e.g., Type 2), a time domain resource assignment field in the DCI format can indicate a row with more than single SLIV. Thus, within a CG period, more than one PUSCH or SLIV can be allocated (where each SLIV corresponds to a resource allocation of a PUSCH). In some embodiments, for example, the group comprising the plurality of transmission occasions includes at least one of a first type of configured grant and a second type of configured grant for multiple- PUSCH configured grant transmissions; and the method further includes an activation DCI for the multiple-PUSCH configured grant. The activation DCI includes a time domain resource assignment field that indicates that more than one PUSCH or SLIV can be allocated.

[0080] In another example, for a CG Type 2, its configuration can allow the possibility of having more than one SLIV in a CG period. In some embodiments, for example, the multiple- PUSCH configured grant allows more than SLIV in a time period for the multiple-PUSCH configured grant.

[0081] In a further example, a CG type 1 radio resource control (RRC) parameter (e.g., rrc- ConfiguredUplinkGrant) can be configured to provide allocation with more than one SLIV within a CG period. Parameters within rrc-ConfiguredUplinkGrant, for example, related to time and frequency domain can be configured to provide multiple SLIVs for multiple schedulable PUSCHs. In some embodiments, the multiple-PUSCH configured grant includes a parameter configured to provide an allocation with more than one SLIV within a time period for the multiple-PUSCH configured grant. The same parameter or a similar parameter based on, e.g., TimeDomainAllocationListForMultiPUSCH can be configured for the Type 1 CG.

[0082] In yet another example, in order to allocate resources for CG type 1 or 2, a maximum number of SLIVs e.g., in an entry in a time domain resource allocation (TDRA) table ( e.g., based on TimeDomainAllocationListForMultiPUSCH)) can be S where S is fixed (e.g., 8) or is a bigger number (e.g., 16 or 32). In some embodiments, for example, resources are allocated for the multiple-PUSCH configured grant based on a maximum number of SLIVs.

[0083] HARQ identifier (ID) calculations are discussed further.

[0084] HARQ IDs of PUSCHs in a multi-PUSCH CG period with M PUSCHs allocated (per period) can be derived based on a formula (e.g., some agreed formulae). In some embodiments, for example, a multiple-PUSCH configured grant includes a plurality of PUSCHs and respective HARQ IDs of respective PUSCHs in the plurality of PUSCHs, where the HARQ IDs are derived based on a calculation.

[0085] The value M can be a number of SLIVs indicated in a row of a TDRA table, which can be indicated in a DCI’s TDRA field (e.g., for type 2 CG activation DCI) or indicated in a RRC configuration (e.g., for Type 1 CG).

[0086] An example of a HARQ ID derivation formulae is included in 3GPP TS 38.321 V17.3.0 but modified by taking into account M HARQ processes/PUSCHs per period instead of 1 PUSCH per period included in the existing specification. The HARQ ID calculation includes two aspects: (1) the modified formula will give HARQ ID of a first PUSCH or first HARQ process (HP) allocated in the period, e.g., HP ID#H; and (2) for the remaining PUSCHs, their HP IDs are incremented after HP ID#H. In an example, the modified HARQ ID calculation formula is: (i) HARQ Process ID of 1^st PUSCH in a period= [floor(CURRENT_symbol*M/periodicity) ] modulo nrofHARQ-Processes; and/or (ii) HARQ Process ID of 1^st PUSCH in a period = [floor(CURRENT_symbol*M/periodicity) ] modulo nrofHARQ-Processes + harq-ProcID- Offset2.

[0087] An example of application of the HARQ ID formula is as follows. A CG with 15 KHZ subcarrier spacing (SCS) numerology has a period of 2 slots (that is, 28 symbols) is considered, which has M=4 PUSCHs allocated per CG period, which is from symO to sym2 for PUSCH# 1, sym3 to sym5 for PUSCH#2, sym6 to sym8 for PUSCH#3 and sym9 to syml 1 for PUSCH#4 in the 1^st slot in a CG period. The HARQ IDs are calculated for PUSCHs in a period X, which falls in slot number 2 and 3, and a next period, that is X+l (slot number 4 to slot 5) in subframe number (SFN) 2. It is noted that slots are numbered 0 to 13, SFN are numbered 0 to 1023. HARQ ID of the 1^st PUSCH is calculated. In this example, it is assumed CG can have a maximum of 16 HARQ IDs (0 to 15):

HARQ ID of 1^st PUSCH in period X = [floor((2*10*14 + 2*14 + 0)*4/(2*14))] mod 16 = 12. Then HARQ ID of 2^nd, 3^rd and 4^th PUSCH in period are 12 + 1 = 13, 13 + 1 = 14 and 14 + 1 = 15.

HARQ ID of 1^st PUSCH in period X+l = [floor((2*10*14 + 4*14 + 0)*4/(2*14))] mod 16 = 0. Then HARQ ID of 2^nd, 3^rd and 4^th PUSCH in period are 1, 2 and 3.

[0088] As shown in this example, the IDs from two consecutive periods do not overlap. [0089] In another example, a frequency hopping pattern is applied to multi-PUSCH CG and, e.g., 3GPP TS 38.214 V17.4.0, Section 6.3.1, can be modified accordingly. For example:

One of two frequency hopping modes can be configured: - Intra-slot frequency hopping, applicable to single slot and multi-slot configured PUSCH transmission, multi-slot PUSCH transmission scheduled by DCI format 0 1 or 0 2, each of multiple PUSCH transmissions scheduled by a DCI if the higher layer parameter pusch- TimeDomainAllocationListForMultiPUSCH is configured and each of multiple configured grant PUSCH transmissions in a configuration where the higher layer parameters cg- nrofSlots and cg-nrofPUSCH-InSlot or <cgMultiPusch> are provided.

- Inter-slot frequency hopping, applicable to multi-slot PUSCH transmission

[0090] In some embodiments, for example, a frequency hopping pattern is applied to at least a sub-set of the PUSCHs in the multiple-PUSCH configured grant.

[0091] In another example, if Type 1 CG or Type 2 CG is configured as multi-PUSCH CG, then PUSCHs are not allowed to transmit with their repetitions. Thus, repetitions cannot be configured for such PUSCHs or the repetition factor (k) is set 1. In some embodiments, for example, when at least one of the first type of configured grant and the second type of configured grant is configured as the multiple-PUSCH configured grant, repetitions are not configured for the multiple-PUSCHs or a repetition factor is set to one.

[0092] Some embodiments are directed to a method performed by a network node (e.g., the network node 1500 of Figure 15). For example, modules may be stored in memory 1504 of Figure 15, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1502, processing circuitry 1502 performs respective operations of the flow chart of Figure 12. As illustrated in Figure 12, a method performed by a network node includes receiving (1200), from a UE, a sub-set of a plurality of transmission occasions in a group. The group includes the plurality of transmission occasions from one or more periods of one or more configured grants. The method further includes performing (1202) one of (i) decoding data from the sub-set of the plurality of transmission occasions in the group, and (ii) omitting to decode data from at least one transmission occasion in the sub-set of the plurality of transmission occasions in the group and, based on the omitting, sending a retransmission grant to the UE.

[0093] Various operations from the flow charts of Figures 8-11 may be optional with respect to some embodiments of UEs and related methods. For example, operations of blocks 804, 806, 900, 902, 1000, 1002, and 1100 may be optional.

[0094] Figure 13 shows an example of a communication system 1300 in accordance with some embodiments.

[0095] In the example, the communication system 1300 includes a telecommunication network 1302 that includes an access network 1304, such as a radio access network (RAN), and a core network 1306, which includes one or more core network nodes 1308. The access network 1304 includes one or more access network nodes, such as network nodes 1310a and 1310b (one or more of which may be generally referred to as network nodes 1310), or any other similar 3 GPP access node or non-3GPP access point. The network nodes 1310 facilitate direct or indirect connection of UE, such as by connecting UEs 1312a, 1312b, 1312c, and 1312d (one or more of which may be generally referred to as UEs 1312) to the core network 1306 over one or more wireless connections.

[0096] 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 1300 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 1300 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

[0097] The UEs 1312 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 1310 and other communication devices. Similarly, the network nodes 1310 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1312 and/or with other network nodes or equipment in the telecommunication network 1302 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 1302.

[0098] In the depicted example, the core network 1306 connects the network nodes 1310 to one or more hosts, such as host 1316. 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 1306 includes one more core network nodes (e.g., core network node 1308) 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 1308. 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).

[0099] The host 1316 may be under the ownership or control of a service provider other than an operator or provider of the access network 1304 and/or the telecommunication network 1302, and may be operated by the service provider or on behalf of the service provider. The host 1316 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.

[0100] As a whole, the communication system 1300 of Figure 13 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 Microwave 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.

[0101] In some examples, the telecommunication network 1302 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 1302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1302. For example, the telecommunications network 1302 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.

[0102] In some examples, the UEs 1312 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 1304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1304. 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).

[0103] In the example, the hub 1314 communicates with the access network 1304 to facilitate indirect communication between one or more UEs (e.g., UE 1312c and/or 1312d) and network nodes (e.g., network node 1310b). In some examples, the hub 1314 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1314 may be a broadband router enabling access to the core network 1306 for the UEs. As another example, the hub 1314 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 1310, or by executable code, script, process, or other instructions in the hub 1314. As another example, the hub 1314 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 1314 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1314 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1314 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0104] The hub 1314 may have a constant/persistent or intermittent connection to the network node 1310b. The hub 1314 may also allow for a different communication scheme and/or schedule between the hub 1314 and UEs (e.g., UE 1312c and/or 1312d), and between the hub 1314 and the core network 1306. In other examples, the hub 1314 is connected to the core network 1306 and/or one or more UEs via a wired connection. Moreover, the hub 1314 may be configured to connect to an M2M service provider over the access network 1304 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1310 while still connected via the hub 1314 via a wired or wireless connection. In some embodiments, the hub 1314 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 1310b. In other embodiments, the hub 1314 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1310b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

[0105] Figure 14 shows a UE 1400 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-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

[0106] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP 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).

[0107] The UE 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input/output interface 1406, a power source 1408, a memory 1410, a communication interface 1412, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 14. 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.

[0108] The processing circuitry 1402 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 1410. The processing circuitry 1402 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 1402 may include multiple central processing units (CPUs).

[0109] In the example, the input/output interface 1406 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 1400. 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.

[0110] In some embodiments, the power source 1408 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 1408 may further include power circuitry for delivering power from the power source 1408 itself, and/or an external power source, to the various parts of the UE 1400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1408. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1408 to make the power suitable for the respective components of the UE 1400 to which power is supplied.

[OHl] The memory 1410 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 readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1410 includes one or more application programs 1414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1416. The memory 1410 may store, for use by the UE 1400, any of a variety of various operating systems or combinations of operating systems. [0112] The memory 1410 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 1410 may allow the UE 1400 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 1410, which may be or comprise a device-readable storage medium.

[0113] The processing circuitry 1402 may be configured to communicate with an access network or other network using the communication interface 1412. The communication interface 1412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1422. The communication interface 1412 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 1418 and/or a receiver 1420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1418 and receiver 1420 may be coupled to one or more antennas (e.g., antenna 1422) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0114] In the illustrated embodiment, communication functions of the communication interface 1412 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. [0115] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1412, 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).

[0116] 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.

[0117] 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 1400 shown in Figure 14. [0118] 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 3 GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3 GPP 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.

[0119] 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.

[0120] Figure 15 shows a network node 1500 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 NRNodeBs (gNBs)).

[0121] 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 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). [0122] 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).

[0123] The network node 1500 includes a processing circuitry 1502, a memory 1504, a communication interface 1506, and a power source 1508. The network node 1500 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 1500 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 1500 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1504 for different RATs) and some components may be reused (e.g., a same antenna 1510 may be shared by different RATs). The network node 1500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1500, 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 1500.

[0124] The processing circuitry 1502 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 1500 components, such as the memory 1504, to provide network node 1500 functionality.

[0125] In some embodiments, the processing circuitry 1502 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1502 includes one or more of radio frequency (RF) transceiver circuitry 1512 and baseband processing circuitry 1514. In some embodiments, the radio frequency (RF) transceiver circuitry 1512 and the baseband processing circuitry 1514 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 1512 and baseband processing circuitry 1514 may be on the same chip or set of chips, boards, or units. [0126] The memory 1504 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1502. The memory 1504 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 1502 and utilized by the network node 1500. The memory 1504 may be used to store any calculations made by the processing circuitry 1502 and/or any data received via the communication interface 1506. In some embodiments, the processing circuitry 1502 and memory 1504 is integrated. [0127] The communication interface 1506 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 1506 comprises port(s)/terminal(s) 1516 to send and receive data, for example to and from a network over a wired connection. The communication interface 1506 also includes radio front-end circuitry 1518 that may be coupled to, or in certain embodiments a part of, the antenna 1510. Radio front-end circuitry 1518 comprises filters 1520 and amplifiers 1522. The radio front-end circuitry 1518 may be connected to an antenna 1510 and processing circuitry 1502. The radio front-end circuitry may be configured to condition signals communicated between antenna 1510 and processing circuitry 1502. The radio front-end circuitry 1518 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 1518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1520 and/or amplifiers 1522. The radio signal may then be transmitted via the antenna 1510. Similarly, when receiving data, the antenna 1510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1518. The digital data may be passed to the processing circuitry 1502. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [0128] In certain alternative embodiments, the network node 1500 does not include separate radio front-end circuitry 1518, instead, the processing circuitry 1502 includes radio front-end circuitry and is connected to the antenna 1510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1512 is part of the communication interface 1506. In still other embodiments, the communication interface 1506 includes one or more ports or terminals 1516, the radio front-end circuitry 1518, and the RF transceiver circuitry 1512, as part of a radio unit (not shown), and the communication interface 1506 communicates with the baseband processing circuitry 1514, which is part of a digital unit (not shown).

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

[0130] The antenna 1510, communication interface 1506, and/or the processing circuitry 1502 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 1510, the communication interface 1506, and/or the processing circuitry 1502 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.

[0131] The power source 1508 provides power to the various components of network node 1500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1500 with power for performing the functionality described herein. For example, the network node 1500 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 1508. As a further example, the power source 1508 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.

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

[0133] Figure 16 is a block diagram of a host 1600, which may be an embodiment of the host 1316 of Figure 13, in accordance with various aspects described herein. As used herein, the host 1600 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 1600 may provide one or more services to one or more UEs.

[0134] The host 1600 includes processing circuitry 1602 that is operatively coupled via a bus 1604 to an input/output interface 1606, a network interface 1608, a power source 1610, and a memory 1612. 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 14 and 15, such that the descriptions thereof are generally applicable to the corresponding components of host 1600.

[0135] The memory 1612 may include one or more computer programs including one or more host application programs 1614 and data 1616, which may include user data, e.g., data generated by a UE for the host 1600 or data generated by the host 1600 for a UE. Embodiments of the host 1600 may utilize only a subset or all of the components shown. The host application programs 1614 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., FLAC, 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 1614 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 1600 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1614 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. [0136] Figure 17 is a block diagram illustrating a virtualization environment 1700 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 1700 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.

[0137] Applications 1702 (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.

[0138] Hardware 1704 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 1706 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1708a and 1708b (one or more of which may be generally referred to as VMs 1708), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1706 may present a virtual operating platform that appears like networking hardware to the VMs 1708.

[0139] The VMs 1708 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1706. Different embodiments of the instance of a virtual appliance 1702 may be implemented on one or more of VMs 1708, 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. [0140] In the context of NFV, a VM 1708 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 1708, and that part of hardware 1704 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 1708 on top of the hardware 1704 and corresponds to the application 1702.

[0141] Hardware 1704 may be implemented in a standalone network node with generic or specific components. Hardware 1704 may implement some functions via virtualization.

Alternatively, hardware 1704 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 1710, which, among others, oversees lifecycle management of applications 1702. In some embodiments, hardware 1704 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 1712 which may alternatively be used for communication between hardware nodes and radio units.

[0142] Figure 18 shows a communication diagram of a host 1802 communicating via a network node 1804 with a UE 1806 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1312a of Figure 13 and/or UE 1400 of Figure 14), network node (such as network node 1310a of Figure 13 and/or network node 1500 of Figure 15), and host (such as host 1316 of Figure 13 and/or host 1600 of Figure 16) discussed in the preceding paragraphs will now be described with reference to Figure 18.

[0143] Like host 1600, embodiments of host 1802 include hardware, such as a communication interface, processing circuitry, and memory. The host 1802 also includes software, which is stored in or accessible by the host 1802 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 1806 connecting via an over-the-top (OTT) connection 1850 extending between the UE 1806 and host 1802. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1850. [0144] The network node 1804 includes hardware enabling it to communicate with the host 1802 and UE 1806. The connection 1860 may be direct or pass through a core network (like core network 1306 of Figure 13) 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.

[0145] The UE 1806 includes hardware and software, which is stored in or accessible by UE 1806 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 1806 with the support of the host 1802. In the host 1802, an executing host application may communicate with the executing client application via the OTT connection 1850 terminating at the UE 1806 and host 1802. 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 1850 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 1850.

[0146] The OTT connection 1850 may extend via a connection 1860 between the host 1802 and the network node 1804 and via a wireless connection 1870 between the network node 1804 and the UE 1806 to provide the connection between the host 1802 and the UE 1806. The connection 1860 and wireless connection 1870, over which the OTT connection 1850 may be provided, have been drawn abstractly to illustrate the communication between the host 1802 and the UE 1806 via the network node 1804, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0147] As an example of transmitting data via the OTT connection 1850, in step 1808, the host 1802 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 1806. In other embodiments, the user data is associated with a UE 1806 that shares data with the host 1802 without explicit human interaction. In step 1810, the host 1802 initiates a transmission carrying the user data towards the UE 1806. The host 1802 may initiate the transmission responsive to a request transmitted by the UE 1806. The request may be caused by human interaction with the UE 1806 or by operation of the client application executing on the UE 1806. The transmission may pass via the network node 1804, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1812, the network node 1804 transmits to the UE 1806 the user data that was carried in the transmission that the host 1802 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1814, the UE 1806 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1806 associated with the host application executed by the host 1802.

[0148] In some examples, the UE 1806 executes a client application which provides user data to the host 1802. The user data may be provided in reaction or response to the data received from the host 1802. Accordingly, in step 1816, the UE 1806 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 1806. Regardless of the specific manner in which the user data was provided, the UE 1806 initiates, in step 1818, transmission of the user data towards the host 1802 via the network node 1804. In step 1820, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1804 receives user data from the UE 1806 and initiates transmission of the received user data towards the host 1802. In step 1822, the host 1802 receives the user data carried in the transmission initiated by the UE 1806.

[0149] One or more of the various embodiments improve the performance of OTT services provided to the UE 1806 using the OTT connection 1850, in which the wireless connection 1870 forms the last segment. More precisely, the teachings of these embodiments may improve power savings and/or capacity and thereby provide benefits such as extended battery lifetime and/or reduced user waiting time.

[0150] In an example scenario, factory status information may be collected and analyzed by the host 1802. As another example, the host 1802 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1802 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1802 may store surveillance video uploaded by a UE. As another example, the host 1802 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 1802 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.

[0151] 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 1850 between the host 1802 and UE 1806, 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 1802 and/or UE 1806. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1850 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 1850 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1804. 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 1802. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1850 while monitoring propagation times, errors, etc.

[0152] 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. [0153] 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.

[0154] Explanations are provided below for various abbreviations/acronyms used in the present disclosure.

Abbreviation Explanation LCID Logical Channel Identity

PDU Protocol Data Unit

MAC Medium Access Protocol

CG Configured Grant

HARQ Hybrid ARQ

UL Uplink

XR Extended Reality

DRX Discontinuous reception

DL Downlink

RRC Radio Resource Control

ARQ Automatic Repeat Request

CG Configured Grant

PUSCH Physical Uplink Shared Channel TB Transport Block

Claims

1. A method performed by a user equipment, UE, the method comprising: generating (800) a plurality of media access control, MAC, protocol data units, PDUs, for a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants; and transmitting (802), based on the generated plurality of MAC PDUs, on the sub-set of the plurality of transmission occasions without skipping one or more uplink transmissions between transmissions in the subset of transmissions.

2. The method of Claim 1, wherein the group that comprises the plurality of transmission occasions belongs to at least one of:

(i) a same period in one configured grant,

(ii) at least two different periods of one configured grant, and

(iii) at least two periods for at least two different configured grants.

3. The method of any one of Claims 1 to 2, further comprising: skipping (804) an uplink transmission before a first uplink transmission in the subset of transmissions.

4. The method of any one of Claims 1 to 3, further comprising: skipping (806) an uplink transmission after a last uplink transmission in the subset of transmissions.

5. The method of any one of Claims 1 to 4, further comprising: skipping (900) a further uplink transmission in the group after the subset of transmissions; and omitting (902) to further transmit over the group based on the skipping the further uplink transmission in the group.

6. The method of any one of Claims 1 to 5, wherein a generated MAC PDU is for a hybrid automatic repeat request, HARQ, process in a period of a configured grant associated with the group, and further comprising: skipping (1000) a further uplink transmission for a next HARQ process in the period; omitting (1002) to generate a further MAC PDU for a HARQ entity for remaining HARQ processes in the period when a parameter is enabled.

7. The method of any one of Claims 1 to 6, wherein the transmitting (802) without skipping is enabled based on a parameter.

8. The method of any one of Claims 1 to 7, wherein one or more of the plurality of transmission occasions includes control information that the UE is not allowed to skip and when the one or more of the plurality of transmission occasions that includes control information has no data, the method further comprises: filling (1100) the one or more of the plurality of transmission occasions with dummy data or padding bits.

9. The method of Claim 8, wherein when the one or more of the plurality of transmission occasions that includes control information has no data, the subset of transmissions includes all transmission occasions between a last transmission on the subset of transmissions and the one or more of the plurality of transmission occasions that includes control information.

10. The method of any one of Claims 1 to 9, wherein the UE provides the generated MAC PDUs to a lower layer for a number, N, of the sub-set of transmission occasions in time, wherein a time of an n-th transmission occasion is before a (n+l)-th transmission occasion, n = 0, . . ., N-2, and wherein the UE delivers the generated MAC PDUS and corresponding portions of data to the lower layer for an m-th and -th transmission occasion, where m > ni +2, and the UE generates further MAC PDUs and delivers the further generated MAC PDUs and corresponding portions of data to the lower layer for times corresponding to m, m +1, . . . m.

11. The method of Claim 10, further comprising: omitting the generating MAC PDUs for times corresponding to m +1, . . ., N-l when the UE skipped an uplink transmission for at least m + 1.

12. The method of any one of Claims 10 to 11, wherein m is zero.

13. The method of any one of Claims 1 to 12, wherein the group comprising the plurality of transmission occasions has a number of transmission occasions determined by a timer.

14. The method of any one of Claims 1 to 13, wherein the group comprising the plurality of transmission occasions comprises at least one of a first type of configured grant and a second type of configured grant for multiple-physical uplink shared channel, PUSCH, configured grant transmissions, and further comprising: an activation downlink control information, DCI, for the multiple-PUSCH configured grant, the activation DCI comprising a time domain resource assignment field that indicates that more than one PUSCH or one start and length indicator value, SLIV, can be allocated.

15. The method of Claim 14, wherein the multiple-PUSCH configured grant allows more than one start and length indicator value, SLIV, in a time period for the multiple-PUSCH configured grant.

16. The method of any one of Claims 14 to 15, wherein the multiple-PUSCH configured grant comprises a parameter configured to provide an allocation with more than one start and length indicator value, SLIV, within a time period for the multiple-PUSCH configured grant.

17. The method of any one of Claims 14 to 16, wherein resources are allocated for the multiple-PUSCH configured grant based on a maximum number of start and length indicator values, SLIVs.

18. The method of any one of Claims 14 to 17, wherein the multiple-PUSCH configured grant comprises a plurality of PUSCHs and respective hybrid automatic repeat request, HARQ, identifiers, IDs, of respective PUSCHs in the plurality of PUSCHs, the HARQ IDs derived based on a calculation.

19. The method of any one of Claims 14 to 18, wherein a frequency hopping pattern is applied to at least a sub-set of PUSCHs in the multiple-PUSCH configured grant.

20. The method of any one of Claims 14 to 19, wherein when at least one of the first type of configured grant and the second type of configured grant is configured as the multiple- PUSCH configured grant, repetitions are not configured for the multiple-PUSCHs or a repetition factor is set to one.

21. A method performed by a network node, the method comprising: receiving (1200), from a user equipment (UE), a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants; and performing (1202) one of (i) decoding data from the sub-set of the plurality of transmission occasions in the group, and (ii) omitting to decode data from at least one transmission occasion in the sub-set of the plurality of transmission occasions in the group and, based on the omitting, sending a retransmission grant to the UE.

22. A user equipment, UE, (1312, 1400) comprising: processing circuitry (1402); memory (1410) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the UE to perform operations comprising: generate a plurality of media access control, MAC, protocol data units, PDUs, for a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants; and transmit, based on the generated plurality of MAC PDUs, on the sub-set of the plurality of transmission occasions without skipping one or more uplink transmissions between transmissions in the subset of transmissions.

23. The UE of Claim 22, wherein the operations further comprise any of the operations of Claims 2 to 20.

24. A non-transitory computer readable medium (1410) including program code to be executed by processing circuitry (1402) of a UE (1312, 1400), whereby execution of the program code causes the program code to perform operations comprising: generate a plurality of media access control, MAC, protocol data units, PDUs, for a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants; and transmit, based on the generated plurality of MAC PDUs, on the sub-set of the plurality of transmission occasions without skipping one or more uplink transmissions between transmissions in the subset of transmissions.

25. The non-transitory computer readable medium of Embodiment 24, the operations further comprising any of the operations of Claims 2 to 20.

26. 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 the following operations to receive the user data from the host: generating (800) a plurality of media access control, MAC, protocol data units, PDUs, for a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants; and transmitting (802), based on the generated plurality of MAC PDUs, on the sub-set of the plurality of transmission occasions without skipping one or more uplink transmissions between transmissions in the subset of transmissions.

27. The method of Claim 26 further comprising: performing the method of any of Claims 2 to 20.

28. A host (1316, 1600) configured to operate in a communication system to provide over-the-top, OTT, service, the host comprising: processing circuitry (1602) configured to provide user data; and a network interface (1608) configured to initiate transmission of the user data to a cellular network for transmission to a user equipment, UE (1312, 1400), wherein the UE comprises a communication interface (1412) and processing circuitry (1402), the communication interface and processing circuitry of the UE being configured to perform the following operations to receive the user data from the host: generate a plurality of media access control, MAC, protocol data units, PDUs, for a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants; and transmit, based on the generated plurality of MAC PDUs, on the sub-set of the plurality of transmission occasions without skipping one or more uplink transmissions between transmissions in the subset of transmissions.

29. The method of Claim 28, wherein the processing circuitry of the UE is further configured to perform the method of any of Claims 2 to 20.

30. A network node (1310, 1500) comprising: processing circuitry (1502); memory (1504) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the network node to perform operations comprising: receive, from a user equipment (UE), a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants; and perform one of (i) decoding data from the sub-set of the plurality of transmission occasions in the group, and (ii) omitting to decode data from at least one transmission occasion in the subset of the plurality of transmission occasions in the group and, based on the omitting, sending a retransmission grant to the UE.

31. A non-transitory computer readable medium (1504) including program code to be executed by processing circuitry (1502) of a network node (1310, 1500), whereby execution of the program code causes the program code to perform operations comprising: receive, from a user equipment (UE), a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants; and perform one of (i) decoding data from the sub-set of the plurality of transmission occasions in the group, and (ii) omitting to decode data from at least one transmission occasion in the subset of the plurality of transmission occasions in the group and, based on the omitting, sending a retransmission grant to the UE.

32. 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 network node (1310, 1500) performs the following operations: receive, from the UE, a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants; and perform one of (i) decoding data from the sub-set of the plurality of transmission occasions in the group, and (ii) omitting to decode data from at least one transmission occasion in the subset of the plurality of transmission occasions in the group and, based on the omitting, sending a retransmission grant to the UE.

33. A host (1316, 1600) configured to operate in a communication system to provide an over-the-top, OTT, service, the host comprising: processing circuitry (1602) configured to provide user data; and a network interface (1608) configured to initiate transmissions of the user data to a network node (1310, 1500) in a cellular network for transmission to user equipments, UEs, the network node having a communication interface (1506) and processing circuitry (1502), the processing circuitry of the network node configured to perform the following operations: receive, from a UE, a sub-set of a plurality of transmission occasions in a group, wherein the group comprises the plurality of transmission occasions from one or more periods of one or more configured grants; and perform one of (i) decoding data from the sub-set of the plurality of transmission occasions in the group, and (ii) omitting to decode data from at least one transmission occasion in the subset of the plurality of transmission occasions in the group and, based on the omitting, sending a retransmission grant to the UE.