WO2024099921A1 - Method of transmitting uplink control information and a communication device - Google Patents

Abstract

A dynamic scheme on indication of CG PUSCH occasion(s) or resource(s) to be unused by a UE is disclosed. A method performed by a network node comprises transmitting an indication of minimum numerical value of UCI timeline in advance to the unused CG PUSCH occasion(s). A method performed by a UE comprising transmitting a UCI indicating unused CG PUSCH occasion(s) occurring later than at least the numerical value of UCI timeline. A network node and a UE respectively performing the methods are also disclosed.

Description

METHOD OF TRANSMITTING UPLINK CONTROL INFORMATION AND A COMMUNICATION DEVICE

TECHNICAL FIELD

[0001] The present disclosure is related to wireless communication systems and more particularly to uplink control information (“UCI”) indication timeline for reporting unused resources.

BACKGROUND

[0002] FIG. 1 illustrates an example of a New Radio (“NR”) network (e.g., a 5th Generation (“5G”) network) including a 5G Core (“5GC”) network 130, network nodes 120a-b (e.g., 5G base station (“gNB”)), multiple communication devices 110 (also referred to as user equipment (“UE”)).

[0003] In the ongoing Rel-18 study item on extended Reality (“XR”), several enhancements are being proposed to increase XR capacity of 5G-Advanced systems.

[0004] extended Reality (XR), XR includes services provided by computer technologies and wearables that allow for human-machine interaction in real/virtual mixed environments. XR includes Virtual Reality (“VR”), Augmented Reality (“AR”), Mixed Reality (“MR”), Cloud Gaming, and the areas interpolated among them [2], As such, XR is usually considered a mixed eMBB/URLLC service; as illustrated in FIG. 2, XR traffic is a mixture of heterogeneous UL/DL data flows, including video, audio, and control traffic [3],

[0005] FIG. 2 illustrates an example of XR traffic characteristics and requirements identified by 3GPP [3],

[0006] FIG. 2 highlights that XR traffic flows have different characteristics (e.g., packet rate in frame per second [fps] and bit rate in bit per second [bps]) and requirements in terms of (application) packet delay budget (“PDB”) [ms]. Among XR flows, DL video and UL scene traffic are periodic (with possible jitter particularly in DL) and have variable large-sized application packets.

[0007] CG-UCI is included in every NR-U CG-PUSCH transmission and includes the information listed in FIG. 3. CG-UCI is mapped as per Rel-15 rules for uplink control information (UCI) multiplexing on PUSCH with CG-UCI having the highest priority. It is mapped on the symbols starting after first DMRS symbol. To determine the number of REs used for CG-UCI, the mechanism of beta-offset in Rel-15 NR for HARQ-ACK on CG-PUSCH is reused. Nonetheless, a new RRC configured beta-offset for CG-UCI is defined.

[0008] FIG. 3 illustrates an example of CG-UCI content.

[0009] If CG-PUSCH resources overlap with PUCCH carrying CSI-partl and/or CSI-part 2, the later can be sent on CG-PUSCH or CG-PUSCH. RRC configuration can be provided to the UE indicating whether to multiplex CG-UCI and HARQ-ACK. If configured, in the case of PUCCH overlapping with CG-PUSCH(s) within a PUCCH group, the CG-UCI and HARQ- ACK are jointly encoded as one UCI type. Otherwise, configured grant PUSCH is skipped if CG-PUSCH overlaps with PUCCH that carries HARQ ACK feedback.

SUMMARY

[0010] There currently exist certain challenges. The third generation partnership project (“3GPP”) has agreed to study whether/how the enhanced configuration grant (“CG”) candidate techniques are necessary and beneficial for improving extended reality (“XR”) capacity. In some examples, there is a focus at least on dynamic indication of the unused CG PUSCH occasion(s) or resource(s) by the UE and/or an increase of CG PUSCH transmission occasions in a duration. No consensus has been reached to continue study on differentiation of XR multiple flows based on CG enhancement in RANI XR SI.

[0011] The issue is that for XR, CG will have more or incremented PUSCHs in a CG period, Due to the nature of XR traffic, the UE may not need all the PUSCHs. Therefore, it can send some UCI to notify gNB about unused resources/PUSCHs. Various embodiments herein describe how this UCI will work and what is its timeline with regards to unused PUSCHs. [0012] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Various embodiments herein describe procedures to devise UCI notification timeline and provide relevant parameters/features where this notification indicates which resources are unused by the UE for UL PUSCH transmissions.

[0013] When UCI is sent to notify the unused resources, then there are some time constraints related to UCI transmission. The numerical value of UCI timeline must be chosen in such a manner that the timeline is greater than minimum required delay from UCI transmission until the gNB able to use unused UE’s resources for other purposes, e.g., reassigned to other UEs. [0014] According to some embodiments, a method of operating a communication device in a communications network that includes a network node is provided. The method includes determining a threshold number of symbols that uplink control information, UCI, indicating a physical uplink shared channel, PUSCH, that will be unused for transmission by the communication device is to be transmitted prior to the PUSCH that will be unused for transmission by the communication device. The method further includes transmitting the UCI indicating the PUSCH at least the threshold number of symbols prior to the PUSCH.

[0015] According to other embodiments, a method of operating a network node in a communications network that includes a communication device is provided. The method includes receiving an uplink control information, UCI, from the communication device, the UCI indicating a physical uplink shared channel, PUSCH, that is unused for transmission by the communication device, the UCI being at least a threshold number of symbols prior to the PUSCH that is unused for transmission. The method further includes adjusting use of the symbols associated with the PUSCH that is unused for transmission based on receiving the UCI. [0016] Certain aspects of the disclosure and their embodiments may provide technical advantages. To transmit bulky or large data, 3GPP is considering incrementing PUSCH resources in CG. However, there can be issue if resources are not fully utilized (e.g., low volume of data in buffer), then this can lead to wastage. In order to stop wastage, 3GPP is interested in utilizing UCI based notification to indicate unused resources. The innovations herein propose a timeline when UCI must be sent, so this wastage can be minimized.

BRIEF DESCRIPTION OF THE DRAWINGS

[0017] 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:

[0018] FIG. 1 is a schematic diagram illustrating an example of a 5th generation (“5G”) network;

[0019] FIG. 2 is a table illustrating an example of extended reality (“XR”) traffic characteristics and requirements identified by the third generation partnership project (“3GPP”); [0020] FIG. 3 is a table illustrating an example of CG-UCI content;

[0021] FIG. 4 is a schematic diagram illustrating an example of a UE indicating a UCI notification X symbols before the unused PUSCH resource allocation in accordance with some embodiments;

[0022] FIG. 5 is a schematic diagram illustrating an example of a UCI always transmitted in last PUSCH in accordance with some embodiments;

[0023] FIG. 6 is a schematic diagram illustrating an example of a UE indicating unused resources via UCI for the time period of Z time units in accordance with some embodiments; [0024] FIG. 7 is a flow chart illustrating an example of operations performed by a communication device in accordance with some embodiments;

[0025] FIG. 8 is a flow chart illustrating an example of operations performed by a network node in accordance with some embodiments;

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

[0027] Figure QQ2 is a block diagram of a user equipment in accordance with some embodiments;

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

[0029] Figure QQ4 is a block diagram of a host, which may be an embodiment of the host of Figure QQ1, in accordance with some embodiments;

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

[0031] Figure QQ6 shows a communication diagram of a host communicating via a network node with a user equipment over a partially wireless connection in accordance with some embodiments.

DETAILED DESCRIPTION

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

[0033] Additional information may also be found in the document(s) provided in the Appendix.

[0034] In some embodiments, the term uplink control information (“UCI”) based notification” is used herein to refer to notifying a gNB of unused configuration grant (“CG”) physical uplink shared channels (“PUSCHs”). In some examples, the UCI based notification is referred to as UCI, which should not be assumed as other UCIs (e.g., hybrid automatic repeat request (“HARQ”) acknowledgment (“ACK”)), unless and otherwise explicitly specified [0035] Additional or alternative embodiments described herein can be applied to licensed, shared, New Radio-Unlicensed (“NR-U”), New Radio (“NR”), Time Division Duplex (“TDD”), and Frequency Division Duplex (“FDD”) type of spectrum

[0036] The innovations herein are generally described in regards to an uplink configured grant (“ULCG”) scenario where a transmission (“Tx”) is performed by a communication device (also referred to as a user equipment (“UE”)) and a reception (“Rx”) is performed by the gNB for UL data transmission use case. However, the same concepts can be applied where both Tx and Rx are UEs, i.e., SideLink (SL) use case over PC5 interface, which can be based on mode 1 and mode 2 (autonomous) resource allocation.

[0037] In some embodiments, the term multi-transport block (“TB”) allocation in a period. It can also be termed as multi-slot or multi-HARQ or multi-transmission or multi-PUSCH transmissions. The essence is that a scheduled resource allocation can span over multiple scheduling time units (i.e., N time units, N is an integer and N>1) in a CG period, where the time unit can be a slot (hence: multi-slot allocation), or the time unit can be a mini-slot (hence: multi-mini-slot allocation), or the time unit can be a set of N consecutive symbols. The scheduling need not to be purely slot-based. For e.g., a CG period of 3 slots can have resource allocated for 3 TBs within a period spanned over 1.5 slots, i.e., symO to sym 5 for TB1, sym6 to sym 13 for TB2 and sym 0 to sym 6 in the next slot for TB3, i.e., a type of multi-slot allocation with 3 TBs or HARQ processes in each period.

[0038] A UCI indication timeline for notifying unused CG PUSCHs is described below and illustrated in FIG. 4.

[0039] In some embodiments, when gNB receives a UCI indication, where UE indicates PUSCHs, which are unused for transmission, not earlier than X symbols after the first symbol indicated by the UCI. This gives enough time by gNB to recycle or use the unused PUSCHs for other purpose, e.g., allocating to another UE.

[0040] FIG. 4 illustrates an example in which the UE must indicate UCI notification X symbols before the unused PUSCH resource allocations.

[0041] In additional or alternative embodiments, the parameter X is configured by gNB/network, which could be a RRC parameter and/or some bitfield in CG activation DCI. [0042] In additional or alternative embodiments, the gNB can determine this parameter X based on delays it experiences which includes non-limiting quantities including at least one of: UCI reception and decoding time; physical downlink control channel (“PDCCH”) (downlink control information (“DCI”)) preparation and transmission time; UE’s reception and decoding time of PDCCH; Time alignment delays due to slot boundaries or mini-slot boundaries or TDD pattern or control resource set (“CORESET”) allocation; and K2 delay. Hence, different gNBs/cells can have different numerical selection for parameter X.

[0043] In additional or alternative embodiments, the unused PUSCHs which are indicated by the UE, the gNB will not trigger retransmission grants for the correspond PUSCHs or HARQ processes.

[0044] In additional or alternative embodiments, if UCI indicates unused PUSCHs, which can be done by indicating non-limiting options (e.g., HARQ IDs of the PUSCHs; Resource allocation of the PUSCHs; and/or Time and frequency region of PUSCHs). [0045] In additional or alternative embodiments, the resource can be divided into timefrequency region/groups, where each group has same size of P physical resource blocks (“PRBs”) and S symbols. Each group is given unique identifier (“ID”). If a UE wants to indicate unused PUSCH resource, it can indicate those groups IDs which has PUSCHs overlapping, which UE does not intend to use. This time and frequency region/resource can be jointly indicated by a two dimensional (“2D”)-bitmap over the time and frequency partitions within the reference region. The reference design can be similar to downlink (“DL”) preemption indication or uplink (“UL”) cancellation indication reference region design.

[0046] In additional or alternative embodiments, the UCI based notification applies to specific capability UEs (e.g., XR UEs).

[0047] In additional or alternative embodiments, the UCI based notification applies to if a CG resource configured with multiple PUSCHs/resources/occasions in a CG period.

[0048] In additional or alternative embodiments, the UCI notification is sent to indicate unused resources (e.g., within the same CG period, it means UCI must sent within the CG period, and unused resource indication applies to same period; and/or of one or more CG periods).

[0049] In additional or alternative embodiments, the UCI based motivation can be allowed only if a UE is configured with N PUSCHs. For example in a CG period if allocated number of PUSCHs are few, then UE is not allowed to use UCI based notification). In some examples, the UCI based motivation can be allowed only if a UE is configured with Number of PUSCHs which spanned over T time units from 1^st to last PUSCH. In additional or alternative examples, the UCI based motivation can be allowed only if a UE is configured with Number of PUSCHs which spanned over Y symbols from 1^st to last PUSCH (e.g., the parameter Y > X).

[0050] In additional or alternative embodiments, the UE is not allowed to transmit UCI notification in the last L PUSCHs, where L = 1 or more.

[0051] In additional or alternative embodiments, the UE is allowed to send UCI in the last symbol, priori to unused resourced/PUSCHs, which are indicated by the same UCI. This feature ensures very relaxed timeline and makes UE complexity low but at the cost of some wastage of resources (as illustrated in FIG. 5).

[0052] FIG. 5 illustrates an example of a UCI always transmitted in last PUSCH.

[0053] In some embodiments, the UE must send UCI notification in the first PUSCH.

[0054] In additional or alternative embodiments, the UE must send UCI notification in all PUSCHs (transmitted or used ones).

[0055] In additional or alternative embodiments, an unused PUSCH transmission by a UE is counted towards the number of PUSCHs that a UE can support per slot.

[0056] In additional or alternative embodiments, the UCI can be sent on PUCCH which may allocated in different carrier. It means PUSCHs are allocated in carrier Cl, and UCI is sent on carrier C2.

[0057] In additional or alternative embodiments, the different carriers can be different numerology or subcarrier spacing (“SCS”).

[0058] In additional or alternative embodiments, the UE can send UCI notification to indicate unused PUSCHs for some repetitions. Let us say, a PUSCH is allocated with 4 repetitions. Then UE can send UCI to indicate the resources correspond to 2 repetitions which are not utilized.

[0059] In additional or alternative embodiments, if a PUSCH includes (multiplexed) with UCI notification, then other UCI, e.g., HARQ-ACK based UCI cannot be multiplexed (or piggybacked) with same PUSCH.

[0060] In additional or alternative embodiments, if gNB has cancelled the ‘some’ PUSCH(s) using cancellation indication (CI), then UE need not to report/indicate those ‘some’ PUSCHs using UCI notification if UE did not want to use it, because they are already cancelled by gNB. [0061] In additional or alternative embodiments, the UCI notification can be applied for dynamic grant-based allocation, containing number of PUSCHs, e.g., in case with dynamic multi-slot UL allocation.

[0062] In additional or alternative embodiments, if the UCI is sent in some PUSCH, say PUSCH# A, to indicate unused other PUSCH resources, where the unused PUSCH resources expected to serve similar traffic, say traffic#V, which is being served by PUSCH#A (traffic with same PHY priority or LCH restrictions). However, if the same UE has other resources allocated for other traffic overlapping unused resources, then UE is free to use the unused resources for other traffic, but not traffic#V if UE has reported unused resourced by UCI.

[0063] In additional or alternative embodiments, the UCI notification can be done over CG- UCI. Currently, The CG-UCI is used in NR-U. For NR, it’s disabled. Therefore, CG-UCI can be enabled in NR and repurpose its existing bitfield to indicate UCI notification.

[0064] In additional or alternative embodiments, the UCI notification can be sent using CG- UCI, where the HARQ field in CG-UCI can indicate the HARQ ID#J of the unused PUSCH. In additional options, all the HARQ IDs of allocated PUSCHs which is after HARQ ID#J will also be assumed unused- Let us take an example, where a CG period has allocated 6 PUSCHs with HARQ IDs, say 6, 8,10, 12, 1, 3. If UE sent UCI is some and HAR ID 12 in UCI notification based on CG-UCI, it means PUSCHs correspond to HARQ ID 12, 1 and 3 are unused.

[0065] In additional or alternative embodiments, the network can define the resource for transmitting UCI notification, which could be, for example, (1) UCI is always sent on a specific occasion in a slot; and/or (2) UCI can be sent in any symbols(s) within a span of x symbols in a slot. [0066] In additional or alternative embodiments, the UE can additionally indicate the time period or length of unused resource, say Z symbols/time units/resources, as illustrated in FIG. 6. The value Z can be configured in radio resource control (“RRC”) or can be indicated in UCI by the UE.

[0067] FIG. 6 illustrates an example of the UE indicating unused resources via UCI for the time period of Z time units.

[0068] Embodiments regarding indication of unused CG occasion(s)/resource(s) by the UE are described below.

[0069] In some embodiments, the implementation of a dynamic grant (“DG”) using hybrid method or pre-scheduling provides the largest gains. The capacity gains presented for any CG enhancement do not seem to surpass DG dramatically to justify the need for enhancements. [0070] With respect to the specific enhancement technique where the overbooked CG resources can be reused by enabling dynamic indication from the UE to provide information on the utility of the configured resources, it is possible to make several observations. In some examples, the scheme is intended to diminish the SR/BSR delay when DG is applied but suffers from inefficient resource utilization. The proposed solution to improve resource utilization is by signalling from the UE. However, the usefulness of the scheme depends on the signaling delay. This is because, there will be always delay between CG indication transmission and sending DCI to other/same UE for utilization of unused resources and finally transmission by the UE on the unused resources. Hence, even if CG indication functionality is enabled, one cannot save the resource wastage fully. In additional or alternative examples, the utilization of UCI will slightly impact the shared channel capacity negatively, which may be small but not zero. In additional or alternative examples, the inclusion of dynamic signaling to CG will bring CG closer to DG and its existing implementation flavors. In additional or alternative examples, the specification effort can be large except if the indication is based on exiting CG-UCI framework, which is already standardized for NR-U CG PUSCH transmission.

[0071] There is a delay between UCI indication in CG for unused resources and the transmission over those unused resources again. Based on above observation, i may not be advantageous to pursue such enhancements when sufficient capacity gains against dynamic methods, with or without XR awareness, are not provided.

[0072] In some embodiments, a procedure is provided to not pursue CG enhancements based on dynamic indication of unused CG occasions(s)/resource(s) by the UE. In some examples, if this enhancement is considered, there is no need to introduce new frameworks where the CG- UCI framework can be reused to provide indication.

[0073] In additional or alternative embodiments, the enhancements based on CG-UCI framework to provide indication of the unused CG PUSCH occasion(s) or resource(s) by the UE can be considered to study if the corresponding capacity performance gains with reasonable signaling delay assumptions are provided.

[0074] Operations of the communication device QQ200 (implemented using the structure of the block diagram of Figure QQ2) will now be discussed with reference to the flow chart of FIG.

7 according to some embodiments of inventive concepts. For example, modules may be stored in memory QQ210 of Figure QQ2, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry QQ202, processing circuitry QQ202 performs respective operations of the flow chart.

[0075] FIG. 7 illustrates an example of operations performed by a communication device according to some embodiments.

[0076] At block 710, processing circuitry QQ202 determines a threshold number of symbols that UCI indicating unused PUSCH will be transmitted prior to the unused PUSCH.

[0077] At block 720, processing circuitry QQ202 transmits, via communication interface QQ206, the UCI indicating the unused PUSCH.

[0078] Various operations from the flow chart of FIG. 7 may be optional with respect to some embodiments of communication devices and related methods.

[0079] Operations of the RAN node QQ300 (implemented using the structure of Figure QQ3) will now be discussed with reference to the flow chart of FIG. 8 according to some embodiments of inventive concepts. For example, modules may be stored in memory QQ304 of Figure QQ3, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry QQ220, RAN node QQ300 performs respective operations of the flow chart.

[0080] FIG. 8 illustrates an example of operations performed by a network node according to some embodiments.

[0081] At block 810, processing circuitry QQ302 receives, via communication interface QQ312, UCI indicating unused PUSCH at least a threshold number of symbols prior to the unused PUSCH.

[0082] At block 820, processing circuitry QQ302 adjusts use of the symbols associated with the unused PUSCH.

[0083] Various operations from the flow chart of FIG. 8 may be optional with respect to some embodiments of RAN nodes and related methods.

[0084] Although FIG. 8 is described in regards to a RAN node, any suitable network node may perform the operations. For example, the operations may be performed by the Core Network CN node QQ300 (implemented using the structure of Figure QQ3) [0085] Figure QQ1 shows an example of a communication system QQ100 in accordance with some embodiments.

[0086] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0087] Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system QQ100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

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

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

[0091] As a whole, the communication system QQ100 of Figure QQ1 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for 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.

[0092] In some examples, the telecommunication network QQ102 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs. [0093] In some examples, the UEs QQ112 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network

QQ 104. Additionally, a UE may be configured for operating in single- or multi -RAT or multistandard 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).

[0094] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and/or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0095] The hub QQ114 may have a constant/persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and/or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and/or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and/or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node QQ110b. In other embodiments, the hub QQ114 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

[0096] Figure QQ2 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-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.

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

[0098] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input/output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure QQ2. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0099] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs). [00100] In the example, the input/output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

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

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

[00103] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

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

[00105] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/intemet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. [00106] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

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

[00108] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure QQ2. [00109] 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.

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

[00111] Figure QQ3 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NRNodeBs (gNBs)).

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

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

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

[00115] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

[00116] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

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

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

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

[00120] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna QQ310 may be coupled to the radio frontend circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port. [00121] The antenna QQ310, communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

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

[00123] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure QQ3 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

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

[00125] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input/output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures QQ2 and QQ3, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[00126] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., 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 QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and/or indicate a different host for over-the-top (OTT) services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. [00127] Figure QQ5 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

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

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

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

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

[00131] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[00132] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

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

[00134] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650. [00135] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure QQ1) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[00136] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

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

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

Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

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

[00140] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may improve data rate and/or latency and thereby provide benefits such as reduced user waiting, better responsiveness, and improved user experience.

[00141] In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

[00142] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and/or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

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

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

EMBODIMENTS

1. A method of operating a communication device in a communications network that includes a network node, the method comprising: determining a threshold number of symbols that uplink control information, UCI, indicating a physical uplink shared channel, PUSCH, that will be unused for transmission by the communication device is to be transmitted prior to the PUSCH that will be unused for transmission by the communication device; and transmitting the UCI indicating the PUSCH at least the threshold number of symbols prior to the PUSCH.

2. The method of Embodiment 1, wherein determining the threshold number of symbols comprises receiving an indication of the threshold number of symbols from the network node as part of at least one of: a radio resource control, RRC, parameter; and a configuration grant activation in downlink control information.

3. The method of Embodiment 2, wherein determining the threshold number of symbols comprises determining the threshold value based on delays experienced by the network node.

4. The method of Embodiment 3, wherein the delays comprises at least one of: a UCI reception time; a UCI decoding time; a physical downlink control channel, PDCCH, preparation time; a PDCCH transmission time; a downlink control information, DCI, preparation time; a DCI transmission time; a reception time of the PDCCH associated with the communication device; a decoding time of the PDCCH associated with the communication device; time alignment delays due to slot boundaries; time alignment delays due to mini-slot boundaries; time alignment delays due to time division duplex, TDD, pattern; time alignment delays due to control resource set, CORESET, allocation; and a K2 delay. 5. The method of any of Embodiments 1-4, wherein transmitting the UCI comprises transmitting the UCI in a first PUSCH in a configuration grant used by the communication device.

6. The method of any of Embodiments 1-4, wherein transmitting the UCI comprises transmitting the UCI in each PUSCH in a configuration grant used by the communication device.

7. A method of operating a network node in a communications network that includes a communication device, the method comprising: receiving an uplink control information, UCI, from the communication device, the UCI indicating a physical uplink shared channel, PUSCH, that is unused for transmission by the communication device, the UCI being at least a threshold number of symbols prior to the PUSCH that is unused for transmission; and adjusting use of the symbols associated with the PUSCH that is unused for transmission based on receiving the UCI.

8. The method of Embodiment 7, further comprising: transmitting an indication of the threshold number of symbols to the communication device as part of at least one of: a radio resource control, RRC, parameter; and a configuration grant activation in downlink control information.

9. The method of Embodiment 7, further comprising: determining the threshold value based on delays experienced by the network node.

10 The method of Embodiment 9, wherein the delays comprises at least one of: a UCI reception time; a UCI decoding time; a physical downlink control channel, PDCCH, preparation time; a PDCCH transmission time; a downlink control information, DCI, preparation time; a DCI transmission time; a reception time of the PDCCH associated with the communication device; a decoding time of the PDCCH associated with the communication device; time alignment delays due to slot boundaries; time alignment delays due to mini-slot boundaries; time alignment delays due to time division duplex, TDD, pattern; time alignment delays due to control resource set, CORESET, allocation; and a K2 delay.

11. The method of any of Embodiments 7-10, wherein receiving the UCI comprises receiving the UCI in a first PUSCH in a configuration grant used by the communication device.

12. The method of any of Embodiments 7-10, wherein receiving the UCI comprises receiving the UCI in each PUSCH in a configuration grant used by the communication device.

13. A communication device (QQ200) in a communications network that includes a network node, the communication device comprising: processing circuitry (QQ202); and memory (QQ210) coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the entity to perform operations comprising any of the operations of Embodiments 1-6.

14. A computer program comprising program code to be executed by processing circuitry (QQ202) of a communication device (QQ200) in a communications network that includes a network node, whereby execution of the program code causes the entity to perform operations comprising any operations of Embodiments 1-6.

15. A computer program product comprising a non-transitory storage medium (QQ210) including program code to be executed by processing circuitry (QQ202) of a communication device (QQ200) in a communications network that includes a network node and a communication device, whereby execution of the program code causes the entity to perform operations comprising any operations of Embodiments 1-6.

16. A non-transitory computer-readable medium having instructions stored therein that are executable by processing circuitry (QQ202) of a communication device (QQ200,) configured to perform operations comprising any of the operations of Embodiments 1-6.

17. A network node (QQ300) in a communications network that includes a communication device, the entity comprising: processing circuitry (QQ302); and memory (QQ304) coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the entity to perform operations comprising any of the operations of Embodiments 7-12.

18. A computer program comprising program code to be executed by processing circuitry (QQ302) of a network node (QQ300) in a communications network that includes a communication device, whereby execution of the program code causes the entity to perform operations comprising any operations of Embodiments 7-12.

19. A computer program product comprising a non-transitory storage medium (QQ304) including program code to be executed by processing circuitry (QQ302) of a network node (QQ300) in a communications network that includes a communication device, whereby execution of the program code causes the entity to perform operations comprising any operations of Embodiments 7-12.

20. A non-transitory computer-readable medium having instructions stored therein that are executable by processing circuitry (QQ302) of a network node (QQ300) configured to perform operations comprising any of the operations of Embodiments 7-12.

21. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform the following operations to transmit the user data from the host to the UE: receiving an uplink control information, UCI, from the communication device, the UCI indicating a physical uplink shared channel, PUSCH, that is unused for transmission by the communication device, the UCI being at least a threshold number of symbols prior to the PUSCH that is unused for transmission; and adjusting use of the symbols associated with the PUSCH that is unused for transmission based on receiving the UCI. 22. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

23. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs the following operations to transmit the user data from the host to the UE: receiving an uplink control information, UCI, from the communication device, the UCI indicating a physical uplink shared channel, PUSCH, that is unused for transmission by the communication device, the UCI being at least a threshold number of symbols prior to the PUSCH that is unused for transmission; and adjusting use of the symbols associated with the PUSCH that is unused for transmission based on receiving the UCI.

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

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

26. A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform the following operations to transmit the user data from the host to the UE: receiving an uplink control information, UCI, from the communication device, the UCI indicating a physical uplink shared channel, PUSCH, that is unused for transmission by the communication device, the UCI being at least a threshold number of symbols prior to the PUSCH that is unused for transmission; and adjusting use of the symbols associated with the PUSCH that is unused for transmission based on receiving the UCI.

27. The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment.

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

29. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform the following operations to receive the user data from the UE for the host: receiving an uplink control information, UCI, from the communication device, the UCI indicating a physical uplink shared channel, PUSCH, that is unused for transmission by the communication device, the UCI being at least a threshold number of symbols prior to the PUSCH that is unused for transmission; and adjusting use of the symbols associated with the PUSCH that is unused for transmission based on receiving the UCI.

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

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

32. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs the following operations to receive the user data from the UE for the host: receiving an uplink control information, UCI, from the communication device, the UCI indicating a physical uplink shared channel, PUSCH, that is unused for transmission by the communication device, the UCI being at least a threshold number of symbols prior to the PUSCH that is unused for transmission; and adjusting use of the symbols associated with the PUSCH that is unused for transmission based on receiving the UCI.

33. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

34. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform the following operations to receive the user data from the host: determining a threshold number of symbols that uplink control information, UCI, indicating a physical uplink shared channel, PUSCH, that will be unused for transmission by the communication device is to be transmitted prior to the PUSCH that will be unused for transmission by the communication device; and transmitting the UCI indicating the PUSCH at least the threshold number of symbols prior to the PUSCH.

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

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

37. 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: determining a threshold number of symbols that uplink control information, UCI, indicating a physical uplink shared channel, PUSCH, that will be unused for transmission by the communication device is to be transmitted prior to the PUSCH that will be unused for transmission by the communication device; and transmitting the UCI indicating the PUSCH at least the threshold number of symbols prior to the PUSCH.

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

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

40. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to utilize user data; and a network interface configured to receipt of transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform the following operations to transmit the user data to the host: determining a threshold number of symbols that uplink control information, UCI, indicating a physical uplink shared channel, PUSCH, that will be unused for transmission by the communication device is to be transmitted prior to the PUSCH that will be unused for transmission by the communication device; and transmitting the UCI indicating the PUSCH at least the threshold number of symbols prior to the PUSCH.

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

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

43. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs the following operations to transmit the user data to the host: determining a threshold number of symbols that uplink control information, UCI, indicating a physical uplink shared channel, PUSCH, that will be unused for transmission by the communication device is to be transmitted prior to the PUSCH that will be unused for transmission by the communication device; and transmitting the UCI indicating the PUSCH at least the threshold number of symbols prior to the PUSCH.

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

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

APPENDIX

3GPP TSG-RAN WG1 Meeting #111 R1 -2210923

Toulouse, France, November 14^th - 18^th, 2022

Agenda Item: 9.10.2

Source: Ericsson

Title: Discussion on capacity enhancements for XR

Document for: Discussion, Decision

1 Introduction

In RAN plenary 94-e [1], a new SI for Rel-18 on extended reality (XR) was agreed [1], with objectives covering 1) XR-awareness in RAN, 2) XR-specific power saving, and 3) XR-specific capacity improvements.

In this contribution, we discuss possible study topics related to the third area, following the objectives in [1]:

“Objectives on XR-specific capacity improvements (RAN1, RAN2):

• Study mechanisms that provide more efficient resource allocation and scheduling forXR service characteristics (periodicity, multiple flows, jitter, latency, reliability, etc...). Focus is on the following mechanisms: o SPS and CG enhancements; o Dynamic scheduling / grant enhancements. ”

2 Discussion

2.1 CG enhancements

Many enhancement techniques were proposed with respect to the usage of configured grant (CG) based transmissions for uplink (UL) video XR traffic. Based on the discussions during the last meeting, the following agreement was made that prioritizes two areas of CG enhancements for further study in the remaining time of the SI:

From RAN1#110-bis-e [2]:

In the following, we discuss our view on the necessity and benefit of CG-based transmission enhancements and related focus areas as listed in the agreement above.

2.2.1 Analysis and performance evaluations

XR services include downlink (DL) and uplink (UL) traffic flows, e.g., DL/UL video application packets (also referred to as scene traffic in UL), DL audio application packets, and UL pose/control application packets. These flows have different characteristics (e.g., bit rate, periodicity, jitter) and requirements in terms of (application) packet delay budget (PDB) [5], The heterogeneity of XR traffic flows will likely require using different transmission schemes that when are mapped onto XR traffic, lead us to the following observation:

Dynamic Scheduling and Granting (DG) is a suitable transmission scheme to deal with varying and large-sized application packets and possible jitter for DL/UL video XR traffic.

Configured Grant (CG) is a suitable transmission scheme for predictable and fixed small-sized UL traffic, e.g., pose/control and BSRs triggered by UL video XR traffic.

In our view, to handle dynamic XR traffic, dynamic scheduling is in principle a better alternative to current CG framework and related enhancements. If transmission parameters need to be updated due to changes in channel conditions, traffic arrivals, packet size, jitter, etc., new dynamic grants can be provided to accommodate such changes. The main criticism to DG scheduling for improving the XR capacity is the delay due to SR and/or BSR for the gNB to determine the size of proper grant after receiving BSR. In our view, the delay can be diminished based on mechanisms using existing specifications with/without relying on XR awareness. In the following, we explain the reasons accompanied with supporting simulation results:

It should be known that the network can implement DG scheduling in multiple ways.

• For example, pre-scheduling based on dynamic allocation, being already available in gNB implementations, can be used to mimic configured scheduling while keeping the flexibility of granting dynamic resources to dynamic XR traffic. There, we consider XR awareness related information available to the gNB, e.g., traffic periodicity information, and/or statistics on data packet size. Thus, a UE can be allocated grants at regular periods without the UE needed to send an SR, while the dynamic scheduling properties are preserved by updating the link adaptation.

• Similarly, a normal DG scheme (non-prescheduling) can also leverage XR awareness. In this case, after the SR by a UE is received, the gNB can provide an initial grant that enables the UE to initiate data transmission while sending the BSR. The resource allocation in the initial grant (after the SR) can leverage information on XR packet size statistics (e.g., a grant fitting an XR packet of minimum size can be provided). Then, BSR can be used to decide if further resources are needed in the next slots to finalize the transmission of the XR packet.

• Another DG implementation variant is to rely on CG resources to indicate to the gNB the arrival of new data instead of SR. The NW can configure CG resources to not only receive indication of new data, but also receive an BSR to have an informed initial grant. After receiving data on CG, the gNB continues to serve the XR traffic using dynamic scheduling.

We have simulated the capacity performance for UL video traffic (10 Mbps and 60 fps) with CG and DG scheduling for system parameters conforming to Table A.1 in Appendix for PDB = 30 ms and PDB = 15 ms. We have considered the following cases in our simulations, for which we also provide related diagrams in dedicated figures:

• Case 1 : Dynamic grant with SR followed by a small initial UL grant: o The scheduling is based on dynamic grants where it is assumed an SR is triggered upon arrival of a new video packet in the UE buffer. The network provides a small initial grant of size 288 bits, upon receiving the SR. No knowledge of XR traffic is assumed. See Figure 1 .

Figure 1 : Illustration of dynamic scheduling grant scheme with SR followed by initial small UL grant (Case 1)

• Case 2: Dynamic grant with SR followed by a larger initial UL grant: o The scheduling is based on dynamic grants where it is assumed an SR is triggered upon arrival of a new video packet in the UE buffer. The network provides an initial grant of size 117 kbit as the minimum XR packet size used in simulation (See Note 1 below), upon receiving an SR. No knowledge of XR traffic periodicity is assumed. See Figure 2.

■ Note 1 : Given the traffic model specified in 38.838 [4], frame rate of 60 fps and data rate of 10 Mbit/s give approximate average packet size of 167 kbit. The minimum and maximum packet size are derived in such a manner that 99% of range of the gaussian distribution centred around the mean is covered, i.e., from mean minus three times standard deviation to mean plus three times standard deviation. This gives minimum packet size 117 kbit and maximum size 217 kbit.

Figure 2: Illustration of dynamic scheduling grant scheme with SR followed by initial larger UL grant (Case 2)

• Case 3: Pre-scheduling dynamic grant (Pre-scheduling DG): o The scheduling is based on dynamic grants where it is assumed that the network is provided with XR traffic periodicity. An initial grant to the UE when its traffic is expected is transmitted (implementation-based learning) without using SR. The network provides an initial grant of size 117 kbit as the minimum XR packet size used in simulation. See Figure 3.

Figure 3: Illustration of Pre-scheduling dynamic grant scheme (Case 3)

• Case 4: Configured grant: o The scheduling is based on configured grants where it is assumed that the network uses information on traffic periodicity, size statistics, TDD pattern, PDB, etc., to derive proper configurations for CG size and periodicity. The initial transmissions happen only on CG occasions, and retransmissions can occur on dynamic grants. See Figure 4. o We have simulated the performance curves for the following CG configuration parameters, and picked the best configuration for comparison with other schemes.

■ PDB = 30 ms, CG with size I periodicity of (30 kbit 12.5 ms), (60 kbit I 5 ms), and (90 kbit / 7.5 ms)

• The CG configuration with 5 ms periodicity and 60 kbit occasion size outperforms other CG configurations.

■ PDB = 15 ms, CG with size I periodicity of (60 kbit I 2.5 ms) and (100 kbit I 2.5 ms)

• The CG configuration with 2.5 ms periodicity and 60 Kbit occasion size outperforms the other CG configuration.

Figure 4: Illustration of configured grant scheduling scheme (Case 4)

• Case 5: Hybrid scheduling based configured and dynamic grant (Hybrid CG-DG): o The scheduling is based on a combined use of configured and dynamic grants. SR resources are not used. Instead, CG resources are configured with minimum size in every UL slot in order to transmit BSR and small amount of data when new data arrives. Whenever a XR packet arrives in a buffer, the UE uses the nearest possible CG occasion for BSR transmission and possibly small amount of data. The network can thus use the BSR to provide dynamic grants for the following data transmission. No knowledge of XR traffic periodicity is assumed. See Figure 5.

Figure 5: Illustration of Hybrid scheduling based configured and dynamic grant (Hybrid CG-DG) (Case 5)

• Case 6: Dynamic scheduling with genie BSR (DG with genie BSR): o The scheduling is based on dynamic grants where it is assumed BSR is available with zero delay at the scheduler when a new packet arrives in the UE buffer, to be used for indicating UL grants to the UE. Hence, in this case, no SR or BSR delay is assumed. This case is simulated to show the upper bound on capacity performance. See Figure 6.

Figure 6: Illustration of dynamic scheduling without SR and with genie BSR at gNB (Case 6)

The capacity performance results are shown in Figure 7 for PDB = 15 ms and PDB = 30 ms. The results show that for larger PDB, if any potential enhancement is applied for dynamic adaptation to CG, still there will be no or very limited capacity gains as the performance with static parameters already matches quite close to the upper bound. On the other hand, in smaller PDB case, there can be room for CG improvement. However, in both scenarios, pre-scheduling DG (improved version of DG) and hybrid allocation (combination of CG and DG) seem to be lucrative options, as they can provide better performance than CG or normal DG, which is close to the upper bound. For lower PDB scenario, hybrid allocation seems to slightly outperform pre-scheduling DG. For pre-scheduling DG, the scheduling operation relies on periodicity information (XR awareness information) availability at the network. If no such framework pertinent to XR-awareness information delivery is provided/standardized, other implementation options such as scheduling based on hybrid CG and DG can deliver capacity gains.

The results support our view that the periodic nature of video XR traffic does not motivate the usage of CG based transmission. This characteristic instead motivates the usage of dynamic grant pre-scheduling or hybrid allocation schemes that are already used in practice.

Figure 7: Fraction of satisfied users, using the XR capacity KPI with target of 99% packet success rate, for dynamic scheduling with or without SR and for different assumptions on the initial grant size, pre- scheduling-based DG, legacy CG, and hybrid CG-DG for transmission of XR video in UL as percentage of number of satisfied users for PDB = 15ms Bottom PDB = 30ms.

For convenience, the results presented in figure and relative gains are summarized in Table 1 below. Table 1 Summary of simulation results for DG and CG scenarios

Summing up all of above, we think that studying dynamic adaptations for CG to serve video traffic is hardly motivated and may bring negligible gains for capacity and, on the contrary, may increase power usage and system complexity considerably.

In summary, we propose the following guidelines for assessing the necessity and benefit of the enhancement of DG and CG schemes forXR services.

To assess the necessity and benefit of the candidate enhancement techniques for improving capacity of XR video traffic, prioritize DG-based enhancement techniques.

To assess the necessity and benefit of the candidate CG enhancement techniques for improving capacity of XR video traffic, the CG-based transmissions for XR video traffic should be compared against DG-based transmissions for XR video traffic.

The necessity and benefit of the candidate enhancement techniques of DG and CG schemes for XR services should be assessed as compared to existing schemes base d on Rel-17 specifications, and/or under the assumption of XR awareness at RAN.

Moreover, based on the analysis and evaluation results for different study cases, we observe the following:

Dynamicity of XR traffic with frequent/periodic occasions can be handled by existing specifications and gNB implementation.

Necessity of supporting new features to enable dynamic adaptation of CG transmission is not justified.

Based on our observations we propose:

Deprioritize studying the enhancements based on dynamic adaptations for CG based transmissions. 2.2.2 Indication of unused CG occasion(s)/resource(s) by the UE

From our CG and DG evaluations, the implementation of DG using hybrid method or pre-scheduling provides the largest gains. The capacity gains presented for any CG enhancement do not seem to surpass DG dramatically to justify the need for enhancements.

With respect to the specific enhancement technique where the overbooked CG resources can be reused by enabling dynamic indication from the UE to provide information on the utility of the configured resources, we make the following observations:

• The scheme is intended to diminish the SR/BSR delay when DG is applied but suffers from inefficient resource utilization. The proposed solution to improve resource utilization is by signalling from the UE. However, the usefulness of the scheme depends on the signalling delay. This is because, there will be always delay between CG indication transmission and sending DCI to other/same UE for utilization of unused resources and finally transmission by the UE on the unused resources. Hence, even we employ CG indication functionality, one cannot save the resource wastage fully.

• The utilization of UCI will slightly impact the shared channel capacity negatively, which may be small but not zero.

• The inclusion of dynamic signaling to CG will bring CG closer to DG and its existing implementation flavors.

• The specification effort can be large except if the indication is based on exiting CG-UCI framework, which is already standardized for NR-U CG PUSCH transmission.

There is delay between UCI indication in CG for unused resources and the transmission over those unused resources again.

Based on above observation, we are not in favour of pursuing such enhancements when sufficient capacity gains against dynamic methods, with or without XR awareness that we discussed in the previous section, are not provided.

Do not pursue CG enhancements based on dynamic indication of unused CG occasions(s)/resource(s) by the UE.

If this enhancement is considered, there is no need to introduce new frameworks where the CG-UCI framework can be reused to provide indication.

The enhancements based on CG-UCI framework to provide indication of the unused CG PUSCH occasion(s) or resource(s) by the UE can be considered to study if the corresponding capacity performance gains with reasonable signalling delay assumptions are provided.

2.2.3 Increase CG PUSCH transmission occasions in a duration

One of the enhancements for CG discussed in the last meeting is the support of multiple PUSCH occasions per CG period to cater large video packets.

As we concluded in the previous section, DG based allocation is already capable of supporting dynamic variations in XR video traffic, so any enhancement to CG cannot provide capacity higher than dynamic grant scheduling. In addition to the questionable capacity performance gains to motivate such enhancements, we discuss the following challenges regarding complexity of the proposed candidate schemes.

Regarding the enhancements proposed based on grouping of multiple CG configurations having same periodicity but different offset, our view is as the following. To optimize multiple CG framework for multiple PUSCHs per period, the joint activation is missing, considering the enhancements done in Rel-16. It was discussed in Rel-16, whether multiple CG configurations can be grouped and activated/reactivated/de-activated jointly using a single DCI. However, only joint deactivation was specified in Rel-16. The disadvantages we observe with the support of joint activation are summarized below:

To activate as a group, we see the following challenges:

• The network may need to spend signalling to allocate individual CG IDs, then configure a group ID mapping to a group of individual CG IDs, in order to activate/update/reactivate CGs with required parameters.

• It may increase both delay and PDCCH resource usage as control signalling will be spent, at first, perhaps creating individual CGs.

• It may also need modification of DCI, or even addition of fields for group activation. This is not similar to group deactivation, where many of the fields are not useful, and thus used for validation or indicate group ID in the HARQ bitfield provided by ConfiguredGrantConfigType2DeactivationStateList.

• To have all CGs belonging a group the same parameters, such as MCS, RV pattern, etc., then it does not make sense to create multiple CGs with same parameters. Instead, one could aim for devising multiple allocations with similar parameters within the single CG.

Therefore, we are not convinced with grouping of CG configurations with joint activation, as signalling and specification complexity is high. Based on the above discussion, we propose the following:

Do not pursue enhancements based on joint activation to enable multiple CGs occasions in a period.

Although we are not convinced that CG enhancements are justified or necessary for improving XR traffic capacity performance, from the specification and complexity point of view, an extension of multi-PUSCH allocation framework to single CG seems to be the most reasonable approach, if justified to be needed.

For an extension of multi-PUSCH allocation framework to single CG, since number of allocated slots are already incorporated in TDRA table and, thus, it can be supported with activation I re-activation DCI for CG. The specification complexity may be low compared to solutions based on grouping of CGs. At the time of activation, multiple HARQ processes can be automatically associated with single CG configuration. Simultaneously, PDCCH monitoring is not increased as there is only one configuration associated with multi-PUSCH allocations. Moreover, any potential enhancements to multi-PUSCH framework for dynamic grants can be inherited.

The enhancements based on multi-PUSCH allocation for a single CG can be considered to study if the corresponding capacity performance gains are provided and the specification effort is low.

2.2 Dynamic scheduling retransmission enhancements

As regards to DG enhancements, the following agreement was reached during RAN1#110-bis-e.

From RAN1#110-bis-e [2]:

o Complexity analysis and RAN2 impact

In the following, we provide our view on the above aspect.

First, the functionality to enable HARQ retransmission of a TB on a different cell for DL has been discussed before for LAA. Several companies judged this functionality to be non-critical for LAA and we have currently no reasons to believe this is critical for XR either. The functionality has impact on gNB/UE implementation complexity as well as impact on signalling. As the proponent says, it will be required to introduce a signalling mechanism to indicate that a TB initially transmitted on a first carrier using a first HARQ process is re-transmitted on a second carrier using a second HARQ process. On a high level, the functionality may appear simple, but the specification details are often complicated. One such complication that we expect will appear is regarding timing. There are complicated timing rules already in current specification for, e.g., PUSCH preparation time. The PUSCH preparation time has been discussed intensively in previous releases when new functionality has been introduced and the resulting rules have become more and more complicated. We expect it will be required to introduce additional time for the PUSCH preparation time if a TB would be re-transmitted on a carrier different from the carrier used for previous transmission. If the involved carriers would have different numerology, it is not unlikely that complicated rules would be the result. gNB processing delay would also likely be impacted by that a TB is re-transmitted on a different carrier since soft bits to be combined do not originate from same carrier. Since timing restrictions impose scheduling restrictions and it in turn limits the potential gain with the functionality.

Re-transmitting a TB on another carrier than the carrier used for initial transmission will likely lead to timing restrictions for both UE and gNB:

- For uplink TB transmissions, additional UE restrictions w.r.t PUSCH preparation time are expected.

- For downlink, additional UE restrictions w.r.t., PDSCH-to-HARQ feedback time are expected.

- In UL and DL case, the longer gNB processing delay can be expected.

- Even more severe restrictions may apply when two carriers have different numerology.

Scheduling restrictions imposed by timing restrictions will negatively impact capacity for time- critical services.

Based on our observations and the limited remaining time for this SI, we propose:

Deprioritize the mechanism to enable HARQ retransmission of a TB on a different carrier.

2.3 Measurement Gaps Enhancements

As regards to other enhancements, the following recommendation was made during RAN1#110-bis-e.

In the following, we take into consideration the above recommendation and discuss our view regarding this aspect. As regards to Measurement Gap (MG) enhancements, the following agreements were reached during RAN1#109-e

From RAN1#109-e [2][3]:

The issue of scheduling restrictions during measurement gap and SMTC window has been extensively discussed in previous meetings. It has been shown that scheduling restrictions can negatively affect XR capacity at least in some scenarios and parameter settings.

In general, configuration of MGs and SMTC is in control of gNB which can choose measurement parameters to find the best trade-off between measurement sampling rate, mobility performance and XR capacity. Specification already today provides different options and flexibility for configuration of measurement gaps and SMTC window, e.g., SMTC window can be 1-5 ms and there are scenarios where MG is not needed.

Therefore, we believe that optimization of scheduling restrictions can’t be studied of context. When it comes to simulations provided by proponent companies, we would like to ask several questions:

• In general, how other parameter settings impact XR capacity, e.g., shorter MGs or shorter SMTC windows?

• In case of signalling from UE to gNB on usage of measurement periods: o How would UE signalling preparation delay and scheduling delay impact the XR performance? o Can it be so that UE will always measure and never skip measurements? o Can the same functionality be achieved already now if gNB does RRC reconfiguration based on available measurements and turn on/off measurement gaps when needed?

• In case of signalling from gNB to UE on skipping measurements: o If some measurement periods are skipped, how would impact measurement accuracy in the first order and mobility performance in the second order, e.g., handover success rate, radio link failure in handover? o How would signalling design impact XR performance?

We again would like to pay attention to the fact that the measurement procedures to be done by UE are defined in 38.133 which is handled by RAN4. So, any possible change or study of potential enhancement of RAN4 specification should involve RAN4 group. Also, RRM procedures are defined in TS 38.321 specification handled by RAN2. RAN1 can only provide available simulation results and recommend to RAN2 and RAN4 to study potential enhancements further. Since RAN4 was not included in Rel-18 XR SI, such studies go beyond agreed Rel-18 scope and allocated resources. However, proper study involving all needed groups can be done in future. RAN1 can recommend to RAN2 and RAN4 to study in future a need and possibility for potential improvements at least for some scenarios on scheduling restrictions due to measurements.

3 Conclusion

In the previous sections we made the following observations:

Observation 1 Dynamic Scheduling and Granting (DG) is a suitable transmission scheme to deal with varying and large-sized application packets and possible jitter for

DL/UL video XR traffic.

Observation 2 Configured Grant (CG) is a suitable transmission scheme for predictable and fixed small-sized UL traffic, e.g., pose/control and BSRs triggered bv UL video

XR traffic.

Observation 3 Dvnamicitv of XR traffic with freguent/periodic occasions can be handled bv existing specifications and gNB implementation.

Observation 4 Necessity of supporting new features to enable dynamic adaptation of CG transmission is not justified.

Observation 5 There is delav between UCI indication in CG for unused resource and the transmission of over those unused resources again.

Observation 6 Re-transmitting a TB on another carrier than the carrier used for initial transmission will likelv lead to timing restrictions for both UE and gNB: - For uplink TB transmissions, additional UE restrictions w.r.t PUSCH preparation time are expected. - For downlink, additional UE restrictions w.r.t. PDSCH-to-

HARQ feedback time are expected. - In UL and DL case, the longer gNB processing delav can be expected. - Even more severe restrictions mav apply when two carriers have different numerology.

Observation 7 Scheduling restrictions imposed bv timing restrictions will negatively impact capacity for time-critical services.

Based on the discussion in the previous sections we propose the following:

Proposal 1 To assess the necessity and benefit of the candidate enhancement technigues for improving capacity of XR video traffic, prioritize DG-based enhancement technigues.

Proposal 2 To assess the necessity and benefit of the candidate CG enhancement technigues for improving capacity of XR video traffic, the CG-based transmissions for XR video traffic should be compared against DG-based transmissions for XR video traffic.

Proposal 3 The necessity and benefit of the candidate enhancement technigues of DG and

CG schemes for XR services should be assessed as compared to existing schemes base d on Rel-17 specifications, and/or under the assumption of XR awareness at RAN.

Proposal 4 Deprioritize studying the enhancements based on dynamic adaptations for CG based transmissions.

Proposal 5 Do not pursue CG enhancements based on dynamic indication of unused CG occasions(s)/resource(s) by the UE.

Proposal 6 The enhancements based on CG-UCI framework to provide indication of the unused CG PUSCH occasion(s) or resource(s) bv the UE can be considered to studv if the corresponding capacity performance gains with reasonable signalling delav assumptions are provided.

Proposal 7 Do not pursue enhancements based on joint activation to enable multiple CGs occasions in a period. Proposal 8 The enhancements based on multi-PUSCH allocation for a single CG can be considered to study if the corresponding capacity performance gains are provided and the specification effort is low.

Proposal 9 Deprioritize the mechanism to enable HARQ retransmission of a TB on a different carrier.

Proposal 10 RAN1 can recommend to RAN2 and RAN4 to study in future a need and possibility for potential improvements at least for some scenarios on scheduling restrictions due to measurements.

References RP-213587, Study on XR Enhancements for NR, Nokia, RAN#94e, December 2021

3GPP TSG RAN WG1 #110-bis-e RAN1 Chair’s Note, October 10^th - 19^th, 2022

3GPP TSG RAN WG1 #109-e RAN1 Chair’s Notes, May 9th - 20th, 2022

3GPP TSG RAN WG1 #110 Toulouse RAN1 Chair’s Notes, August 22nd - 26th, 2022

3GPP TSG RAN, “Study on XR (Extended Reality) Evaluations for NR (Release 17)”, TR 38.838 v1 .0.1 Appendix

Table A.1 : System simulation parameters

Claims

1. A method performed by a network node in a communications network that includes a communication device, comprising: transmitting an indication of a threshold number of symbols to the communication device so that when the communication device transmits an uplink control information, UCI, message indicating one or more physical uplink shared channel, PUSCH, transmission occasions being configured by the network node will be unused by the communication device, the UCI should be transmitted at least the threshold number of symbols prior to the one or more PUSCH transmission occasions to be unused; receiving a UCI message from the communication device indicating one or more PUSCH transmission occasions to be unused; and adjusting use of the indicated one or more PUSCH transmission occasions to be unused by the communication device.

2. Method according to Claim 1, wherein the transmitting the indication comprising: transmitting a radio resource control, RRC, message in which the threshold number is indicated in a RRC parameter; or transmitting a downlink control information, DCI, message indicating a configuration grant, CG, activation.

3. Method according to Claims 1 or 2, wherein the receiving the UCI message indicating one or more PUSCH transmission occasions to be unused comprising: receiving the UCI comprising a bitmap over time and frequency region of PUSCH transmission occasions configured for the communication device, the bitmap indicating the one or more PUSCH transmission occasions to be unused.

4. Method according to any of Claims 1 to 3, wherein the UCI is received within a same CG period to which the indicated one or more PUSCH transmission occasions to be unused belong.

5. Method according to any of preceding claims, wherein prior to transmitting the indication of the threshold number of symbols, further comprising: determining the threshold number of symbols based on at least one of: a UCI reception time; a UCI decoding time; a PDCCH preparation time; a PDCCH transmission time; a DCI preparation time; a DCI transmission time; a reception time of the PDCCH associated with the communication device; a decoding time of the PDCCH associated with the communication device; time alignment delays due to slot boundaries; time alignment delays due to mini-slot boundaries; time alignment delays due to time division duplex, TDD, pattern; time alignment delays due to control resource set, CORESET, allocation; and a K2 delay.

6. Method according to any of preceding claims, wherein adjusting use of the indicated one or more PUSCH transmission occasions to be unused by the communication device comprises: scheduling the one or more PUSCH transmission occasions for another communication device.

7. A network node in a communications network that includes a communication device, comprising: processing circuitry; and memory coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the network node to: transmit an indication of a threshold number of symbols to the communication device so that when the communication device transmits an uplink control information, UCI, message indicating one or more physical uplink shared channel, PUSCH, transmission occasions being configured by the network node will be unused by the communication device, the UCI should be transmitted at least the threshold number of symbols prior to the one or more PUSCH transmission occasions to be unused; receive a UCI message from the communication device indicating one or more PUSCH transmission occasions to be unused; and adjust use of the indicated one or more PUSCH transmission occasions to be unused by the communication device.

8. Network node according to Claim 7, wherein according to the instructions stored in the memory, the processing circuitry further causes the network node to perform the method according to any of Claims 2 to 6.

9. A method performed by a communication device in a communication network that includes a network node, comprising: receiving, from the network node, an indication of a threshold number of symbols so that when the communication device transmits an uplink control information, UCI, message indicating one or more physical uplink shared channel, PUSCH, transmission occasions being configured by the network node will be unused by the communication device, the UCI should be transmitted at least the threshold number of symbols prior to the one or more PUSCH transmission occasions to be unused; and transmitting, at least the threshold number of symbols prior to one or more PUSCH transmission occasions to be unused, a UCI message indicating the one or more PUSCH transmission occasions to be unused.

10. Method of Claim 9, wherein receiving an indication of a threshold number of symbols comprising: receiving an RRC message in which the threshold number is indicated in a RRC parameter; or receiving a DCI message indicating a CG activation.

11. Method of Claims 9 or 10, wherein the transmitted UCI comprises a bitmap over time and frequency region of PUSCH transmission occasions configured for the communication device, the bitmap indicating the one or more PUSCH transmission occasions to be unused by the communication device.

12. Method according to any of Claims 9 to 11, wherein the UCI message is transmitted within a same CG period to which the indicated one or more PUSCH transmission occasions to be unused belong.

13. Method according to any of Claims 9 to 12, further comprising: sending a decoding time of PDCCH associated with the communication device to the network node.

14. A communication device in a communications network that includes a network node, comprising: processing circuitry; and memory coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the communication device to: receive, from the network node, an indication of a threshold number of symbols so that when the communication device transmits a UCI message indicating one or more PUSCH transmission occasions being configured by the network node will be unused by the communication device, the UCI should be transmitted at least the threshold number of symbols prior to the one or more PUSCH transmission occasions to be unused; transmit, at least the threshold number of symbols prior to one or more PUSCH transmission occasions to be unused, a UCI message indicating the one or more PUSCH transmission occasions to be unused.

15. Communication device according to Claim 14, wherein according to the instructions stored in the memory, the processing circuitry further causes the communication device to perform the method according to any of Claims 10 to 13.