EP4691123A1

EP4691123A1 - Communication device, network node and methods to operate a communication device, and a network node in a communications network

Info

Publication number: EP4691123A1
Application number: EP24715718.3A
Authority: EP
Inventors: Nithin SRINIVASAN; Ricardo BLASCO SERRANO
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 2023-04-04
Filing date: 2024-03-18
Publication date: 2026-02-11
Also published as: WO2024208573A1

Abstract

A method of operating a first communication device is provided. The method includes determining (610) to transmit first data to second communication device as part of a transport block, TB, via a communication device-to-communication device, U2U, relay. The method further includes determining (620) whether to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and/or a size of a selection window for resource allocation associated with transmission of the second data. The method further includes transmitting (630) the TB to the U2U relay.

Description

COMMUNICATION DEVICE, NETWORK NODE AND METHODS TO OPERATE A COMMUNICATION DEVICE, AND A NETWORK NODE IN A COMMUNICATIONS NETWORK

TECHNICAL FIELD

[0001] Embodiments herein relate to entities such as communication devices and network nodes and methods therein. In some aspects, they relate to operating communication devices and network nodes in a communications network.

BACKGROUND

[0002] The present disclosure is related to wireless communication systems and more particularly to logical channel prioritization restrictions in communication device-to- communi cation device relays.

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

[0004] Sidelink (“SL”) transmissions in NR is described below. Initially, the Third Generation Partnership Project (“3 GPP”) specified the long term evolution (“LTE”) device-to- device (“D2D”) technology, also known as SL or the PC5 interface. A targeted use case includes Proximity Services (communication and discovery). LTE sidelink has been extensively redesigned to support vehicular communications (commonly referred to as vehicle-to-everything (“V2X”) or vehicle-to-vehicle (“V2V”)). From the point of view of the lowest radio layers, LTE SL supports only broadcast communications (e.g., transmission from a UE) using LTE SL targeting any receiver that is in range.

[0005] The 3GPP has further introduced SL for the 5G NR (e.g., NR SL). Some use-cases include vehicular communications with more stringent requirements than those typically set in the LTE SL. Therefore, to meet these requirements, the following new enhancements were introduced to NR SL transmissions as follows. Support for unicast and groupcast transmissions are added in NR SL. For unicast and groupcast, the physical SL feedback channel (“PSFCH”) is introduced for a receiver UE to reply with the decoding status to a transmitter UE. Grant-free transmissions, which are adopted in NR uplink transmissions, are also provided in NR SL transmissions, to improve the latency performance. To alleviate resource collisions among different SL transmissions launched by different UEs, it enhances channel sensing and resource selection procedures, which also lead to a new design of Physical Sidelink Control Channel (“PSCCH”). To achieve a high connection density, congestion control and thus the quality of service (“QoS”) management is supported in NR SL transmissions.

[0006] In groupcast communications, the intended receivers of a message are typically a subset of the vehicles near the transmitter, whereas in unicast communication, there is only a single intended receiver. Both the LTE SL and the NR SL can operate with and without network coverage and with varying degrees of interaction between the UEs and the network (“NW”), including support for standalone, network-less operation.

[0007] The 3 GPP has worked on enhancements to the NR SL to not only improve the capabilities of NR SL for V2X but also to address other use-cases such as National Security and Public Safety (“NSPS”) as well as commercial use-cases such as Network Controlled Interactive Services (“NCIS”). To address such new use-cases, the 3GPP included the aspect of UE-to-Network (“U2N”) relaying over the sidelink (e.g., a relay UE capable of sidelink communications and is within coverage of a network can relay transmissions to that network from another UE, also capable of sidelink communications and is within/outside the coverage of the network). This would enable UE(s) with poor coverage or out-of-coverage of a network to reach the network for essential services.

[0008] The concept of relaying has been further enhanced in what is known as UE-to-UE (“U2U”) relaying over SL. The concept of U2U relaying is that a relay UE can relay transmissions to a destination UE from a source UE because the source/destination UE(s) are not within vicinity of each other. This is an essential aspect to improve coverage extension in the SL especially for use-cases related to public safety. In addition, the U2U relaying will be specified in the standards to include both Layer-2 based U2U relays and Layer-3 based U2U relays.

[0009] Layer 2 (“L2”) UE-to-UE relay is described below. The protocol stacks for the user plane (“UP”) and control plane (“CP”) of L2 UE-to-UE Relay architecture are described in FIGS. 2-3. An adaptation layer is supported over the second PC5 link (i.e. the PC5 link between Relay UE and Destination UE) for L2 UE-to-UE Relay. For L2 UE-to-UE Relay, the adaptation layer is put over radio link control (“RLC”) sublayer for both Control plane and User Plane over the second PC5 link. The SL Service Data Adaptation Protocol (“SDAP”)/Packet Data Convergence Protocol (“PDCP”) and radio resource control (“RRC”) are terminated between two Remote UEs, while RLC, media access control (“MAC”) and physical (“PHY”) layer are terminated in each PC5 link.

[0010] For the first hop of L2 UE-to-UE Relay, the N: 1 mapping is supported by first hop PC5 adaptation layer between Remote UE SL Radio Bearers and first hop PC5 RLC channels for relaying. The adaptation layer over first PC5 hop between Source Remote UE and Relay UE supports to identify traffic destined to different Destination Remote UEs. [0011] For the second hop of L2 UE-to-UE Relay, the second hop PC5 adaptation layer can be used to support bearer mapping between the ingress RLC channels over first PC5 hop and egress RLC channels over second PC5 hop at Relay UE.-PC5 Adaptation layer supports the N: 1 bearer mapping between multiple ingress PC5 RLC channels over first PC5 hop and one egress PC5 RLC channel over second PC5 hop and supports the Remote UE identification function. [0012] Layer 3 (“L3”) UE-to-UE relay is described below. The L3 UE to UE relay UE shall relay unicast traffic between two UEs (so called source UE and target UE). It shall provide generic function that can relay any IP, ethernet or Unstructured traffic. The protocol stack for L3 UE to UE relay is shown in FIG. 4 where relaying is performed in packet data unit (“PDU”) layer. Source UE may not be visible to the target UE and vice versa. The two endpoints of the PC5 PDCP link are the source/target UE and the relay UE, which means SL resource bearer (“SLRB”) and PC5-RRC are per hop (e.g., there is no end-to-end SLRB, PC5-RRC, and AS layer security).

[0013] Logical Channel Prioritization (“LCP”) Procedure are described below. The MAC entity shall for each SCI corresponding to a new transmission:

1> select a Destination associated to one of unicast, groupcast and broadcast, having at least one of the MAC CE and the logical channel with the highest priority, among the logical channels that satisfy all the following conditions and MAC CE(s), if any, for the SL grant associated to the SCI: 2> SL data is available for transmission; and

2> SBj > 0, in case there is any logical channel having SBj > 0; and 2> sl-configuredGrantType 1 Allowed, if configured, is set to true in case the SL grant is a Configured Grant Type 1; and

2> sl-AllowedCG-List, if configured, includes the configured grant index associated to the SL grant; and

2> sl-HARQ-FeedbackEnabled is set to disabled, if PSFCH is not configured for the SL grant associated to the SCI.

NOTE 1 : If multiple Destinations have the logical channels satisfying all conditions above with the same highest priority or if multiple Destinations have either the MAC CE and/or the logical channels satisfying all conditions above with the same priority as the MAC CE, which Destination is selected among them is up to UE implementation.

1> select the logical channels satisfying all the following conditions among the logical channels belonging to the selected Destination:

2> SL data is available for transmission; and 2> sl-configuredGrantType 1 Allowed, if configured, is set to true in case the SL grant is a Configured Grant Type 1; and.

3> if PSFCH is configured for the sidelink grant associated to the

SCI:

4> sl-HARQ-FeedbackEnabled is set to enabled, if sl-HARQ- FeedbackEnabled is set to enabled for the highest priority logical channel satisfying the above conditions; or

4> sl-HARQ-FeedbackEnabled is set to disabled, if sl-HARQ- FeedbackEnabled is set to disabled for the highest priority logical channel satisfying the above conditions.

3> else:

4> sl-JL4A )-FeedbackEnabled is set to disabled.

[0014] Scheduled Resource Allocation (Mode-1 scheduling) is described below. NG-RAN can dynamically allocate resources to the UE via the SL-Radio Network Temporary Identifier (“RNTI”) on physical downlink control channel (“PDCCH”) for NR SL communication.

[0015] In addition, NG-RAN can allocate SL resources to a UE with two types of configured SL grants. With type 1, RRC directly provides the configured SL grant only for NR SL communication. With type 2, RRC defines the periodicity of the configured SL grant while PDCCH can either signal and activate the configured SL grant, or deactivate it. The PDCCH is addressed to SL-CS-RNTI for NR SL communication.

[0016] Besides, NG-RAN can also semi-persistently allocate SL resources to the UE via the SL Semi-Persistent Scheduling V-RNTI on PDCCH(s) for V2X SL communication.

[0017] For the UE performing NR SL communication, there can be more than one configured SL grant activated at a time on the carrier configured for SL transmission.

[0018] When beam failure or physical layer problem occurs on master cell group (“MCG”), the UE can continue using the configured SL grant Type 1 until initiation of the RRC connection re-establishment procedure. During handover, the UE can be provided with configured SL grants via handover command, regardless of the type. If provided, the UE activates the configured SL grant Type 1 upon reception of the handover command or execution of conditional handover (“CHO”).

[0019] The UE can send SL buffer status report to support scheduler operation in NG-RAN. For NR SL communication, the SL buffer status reports refer to the data that is buffered in for a group of logical channels (“LCG”) per destination in the UE. Eight LCGs are used for reporting of the SL buffer status report (“BSR”). Two formats, which are SL BSR and truncated SL BSR, are used.

[0020] UE Autonomous Resource Selection (Mode-2 scheduling) is described below.-The UE autonomously selects SL resource(s) from resource pool(s) provided by broadcast system information or dedicated signalling while inside NG-RAN coverage or by pre-configuration while outside NG-RAN coverage.

[0021] For NR SL communication, the resource pool(s) can be provided for a given validity area where the UE does not need to acquire a new pool of resources while moving within the validity area, at least when this pool is provided by a system information block (“SIB”). The NR SIB area scope mechanism as specified is reused to enable validity area for SL resource pool configured via broadcasted system information.

[0022] The UE is allowed to temporarily use UE autonomous resource selection with random selection for SL transmission based on configuration of the exceptional transmission resource pool.

[0023] The procedure for resource selection Mode 2, involves the following operations. First, the UE determines a resource selection window [n+Tl,n+T2], where n is the time of resource selection and Tl, T2 are the start and the end of the resource selection window. The selection of Tl and T2 is often up to UE implementation subject to some bounds: Tl < Tlmax and T2min < T2. T2min is typically dependent on a priority value. Second, the UE determines a set of candidate resources for resource selection. These candidate resources belong to the resource selection window. Third, the UE selects one or several resources for transmission of a transport block (“TB”). Appendices A-B include some relevant parts of the 3GPP specifications for these operations.

SUMMARY

[0024] There currently exist certain challenges. The current logical channel prioritization (“LCP”) procedure for SL is designed for a single hop (e.g., data is transmitted from a source to a destination. In which case, the LCP chooses a destination associated with the highest priority of a logical channel. If multiple logical channels (“LCHs”) which satisfy this condition, the chosen destination is up to the source UEs implementation. Further, having chosen a destination, if the source UE fits the data from the highest logical channel into a transport block (“TB”) but can accommodate more data, the source UE can multiplex data from the second highest logical channel (with data to the same destination) into the TB. Furthermore, when using mode-2 (sensing-based) resource allocation, the sensing window is determined based on the priority of the LCH. [0025] For the case of UE-to-UE (“U2U”) relaying, the source UE communicates with the destination UE via a U2U relay over two hops. Further, it is possible that the source UE communicates with multiple destinations via the U2U relay. Furthermore, at the source UE, each Radio Link Control (“RLC”)/LCH channel is associated to a particular destination. In this scenario, if the legacy LCP procedure is applied, this would allow the source UE to multiplex data from multiple LCHs (e.g., data for different destination UEs in the first hop, between the source UE and U2U relay). This would result in issues relating to accessing the resource because mode-2 resource allocation is subject to preemption and the transmission is capitulated to the highest priority transmission. As a result, the source UE would be allowed to piggyback a high priority transmission with a low priority transmission as technically over the first hop they are associated with the same destination but over the second hop are associated with different destinations. In addition, as mentioned above, the source UE can use a smaller sensing window even for low priority transmissions.

[0026] This LCP legacy behavior may lead to the following problem. A UE1 has high- priority data to transmit to UE2 and low-priority data to transmit to UE3, in both cases through a relay UE. Since both transmissions have the relay UE as their first destination, UE1 may select resources for transmission of a packet multiplexing the data for both UE2 and UE3. Data may be multiplexed per existing procedures: 1) The resource selection is given high priority treatment since it is intended to carry a high-priority packet; and 2) The low-priority gets a treatment above its indicated priority. In other words, UE1 may select resources for transmitting both the high and low priority data. This may result in degraded performance for other UEs. Although mentioned in the context of mode-2 resource allocation, the same issue is also relevant for mode-1 resource allocation.

[0027] The following related issue happens for mode 2. A UE1 has data to transmit to UE2 which is associated with a sensing window bound T2min,2. It also has data to transmit to UE3 which is associated with a sensing window bound T2min,3. Where T2min,2< T2min,3. If UE1 selects resources for transmission to the relay using the selection window with T2min,3 and multiplexes the data for UE2 in the same transmission, the packet may be delivered to UE2 too late.

[0028] In additional or alternative examples, a UE1 has data to transmit to UE3 which is associated with a sensing window bound T2min,3. UE1 selects resources for transmission to the relay using the selection window with T2min,3. Between resource selection and the actual time of transmission, new data arrives. This data is for UE2 and is associated with a lower sensing window bound T2min,2. If UE1 uses the selected resources for transmitting the new data (e.g., multiplexed with the data for UE3), then it may result in a transmission that is too late. That is, the packet may be delivered to UE2 too late.

[0029] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In some embodiments, an LCP restriction is introduced to prevent the source UE from multiplexing data meant for different destinations with different priority levels or different sending window sizes (e.g., prevent piggybacking of low priority transmission with high priority transmission).

[0030] According to some embodiments, a method of operating a first communication device is provided. The method includes determining to transmit first data to second communication device as part of a transport block, TB, via a communication device-to- communication device, U2U, relay. The method further includes determining whether to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and/or a size of a selection window for resource allocation associated with transmission of the second data. The method further includes transmitting the TB to the U2U relay. This would enable the first communication device to multiplex only necessary data in a TB. If not, it would affect the system performance as there are limited resources and all UEs in the system are trying to access the same set of limited resources. If the low priority transmission is always multiplexed with the high priority transmission, this would lead to more resource utilization from one UE and other UEs with data priorities equal or higher than the multiplexed low priority data but lesser than the multiplexed high priority data will not be to transmit leading to starvation of resources and inefficient and unfair resource utilization. This especially affects those UEs in the system not performing SL direct communication i.e., from source UE to destination UE (without a U2U relay). In addition, the multiplexing of data is not always important because such low priority data is not delay sensitive.

[0031] According to other embodiments, a method of operating a network node in a communications network that includes a first communication device is provided. The method includes determining that the first communication device will transmit first data to second communication device as part of a transport block, TB, via a communication device-to- communication device, U2U, relay. The method further includes determining whether to configure the first communication device to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and/or a size of a selection window for resource allocation associated with transmission of the second data. The method further includes transmitting configuration information to the first communication device, the configuration information including an indication of whether the first communication device will transmit the second data as part of the TB. Similar explanation to the [0030], with the difference being that this improves the resource allocation procedure at the network and resources are more efficiently utilized. From a system perspective, there is also a fairer use of the resources.

[0032] Certain embodiments may provide one or more of the following technical advantages. In some embodiments, unnecessary transmission preemption may be prevented for UEs operating in mode-l/mode-2 resource allocation (e.g., prevents blocking the channel for other UEs in the system).

BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0035] FIG. 2 is a block diagram illustrating an example of a user plane protocol stack for L2 UE-to-UE Relay;

[0036] FIG. 3 is a block diagram illustrating an example of a control plane protocol stack for L2 UE-to-UE Relay;

[0037] FIG. 4 is a block diagram illustrating an example of a protocol stack for L3 UE-to-UE Relay;

[0038] FIG. 5 is a schematic diagram illustrating an example of a SL network including a UE- to-UE Relay in accordance with some embodiments;

[0039] FIG. 6 is a flow chart illustrating an example of operations performed by a communication device in accordance with some embodiments;

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

[0041] FIG. 8 is a block diagram of a communication system in accordance with some embodiments;

[0042] FIG. 9 is a block diagram of a user equipment in accordance with some embodiments; [0043] FIG. 10 is a block diagram of a network node in accordance with some embodiments; [0044] FIG.11 is a block diagram of a host, which may be an embodiment of the host of FIG.

8, in accordance with some embodiments; [0045] FIG 12 is a block diagram of a virtualization environment in accordance with some embodiments; and

[0046] FIG. 13 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

[0047] Example embodiments herein e.g. relate to logical channel prioritization restrictions in communication device-to-communi cation device relays.

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

[0049] The embodiments herein are described in the context of new radio (“NR”) (e.g., two or more sidelink (“SL”) communication devices, also referred to herein as user equipment’s (“UEs”), are deployed in a same or different NR cell). However, the same principle may be applied to long term evolution (“LTE”) or any other technology that enables the direct connection of two (or more) nearby devices. The embodiments are also applicable to relay scenarios of UE-to-UE (“U2U”) relays where the source/destination UE and the U2U relay may be based on LTE sidelink or NR sidelink, the Uu connection between the relay UE and the base station may be LTE Uu or NR Uu.

[0050] The embodiments are applicable to layer 2 (“L2”) and layer 3 (“L3”) based U2U relay scenarios. In additional or alternative embodiments, it is assumed that the transmit (“TX”) UE and receive (“RX”) UE are U2U relay capable and can be under any form of coverage scenario (e.g., a Tx UE (also referred to as a source UE), a Rx UE (also referred to as a target UE), and a relay UE may be either within or out of network (“NW”) coverage).

[0051] The embodiments described herein are not restricted by any term defined in the above texts. Any other similar term is inter-changeably applicable here without any loss of the meaning. Though applicable to L2 and L3 relays separately, embodiments herein are written in a generic form without a reference to either of the relaying solutions (e.g., L2/L3). Furthermore, the embodiments herein are written considering a first/second LCH and two set of (final) destination UEs on the second hop, but the same is applicable to more than two LCHs and for more than two (final) destination UEs on the second hop.

[0052] FIG. 5 illustrates an example of an SL network that includes four communication devices (UE 1, UE 2, UE 3, and UE 4) communicatively coupled via a U2U Relay. E.g., referred to as a first communication device UE 1 (or QQ200), a second communication device UE 2, a third communication device UE 3, and a fourth communication device UE 4).

[0053] In some embodiments, an LCP restriction is introduced that prevents the source UE from multiplexing data belonging to different (final) destination UEs (over the second hop) with different LCH priorities. In some examples, different priorities include one of the priority value assigned (to a LCH) being greater/lesser than another priority value assigned to a different LCH. This is applicable to both mode-1 and mode-2 scheduling.

[0054] In additional or alternative embodiments, an LCP restriction is introduced that prevents the source UE from multiplexing data belonging to different (final) destination UEs (over the second hop) with priority values associated with a larger selection window (e.g., a larger value of sl-SelectionWindow). For example, if resources were selected with a Packet Delay Budget. (PDB) = 50 ms, the TB can be transmitted any time before 50 ms. In additional or alternative examples, the TB should not multiplex data from different (final) destinations if their corresponding PDBs are different i.e., one larger than the other. This is related to mode-2 scheduling.

[0055] In additional or alternative embodiments, the LCP restriction can be configured at the MAC -layer by higher layers (e.g., RRC -layer). The source UE can receive this configuration at the higher layers for e.g., RRC -layer via dedicated signaling from the network (e.g., using DL-RRC signaling from the gNB) or can self-generate this configuration.

[0056] In additional or alternative embodiments, the LCP restriction refers to data directed to different final destination UEs. For example, from source UE to destination UE even if the data goes through one or multiple SL UE relays. In contrast, the existing specification only defines such restrictions at hop level. For example, from source UE to (the next) relay UE. [0057] In additional or alternative embodiments, upon receiving this configuration from the higher layers (either from the gNB or self-generated) and applying the configuration, the source UE performs the following in the LCP procedure.

[0058] First, a destination UE is chosen for transmitting data from a LCH. The LCH chosen is the one with the highest priority of the LCH among all the available LCHs with data to be transmitted). In some examples, based on available resources, a TB size is chosen. The size of the TB is greater than the amount of data available on the LCH with the highest priority (e.g., the chosen LCH). That is, the TB can accommodate data from a second LCH or more LCHs. [0059] In some embodiments, if the destination UE on the first hop is a U2U relay, the LCP considers any one of the following aspects for selecting additional data to be included in the transport block: 1) The priority of the second LCH (i.e., the LCH of the additional data); 2) The size of the selection window for resource allocation in mode 2.; and 3) The destination UE on the second hop for the additional data.

[0060] In additional or alternative embodiments, if the priority of the second LCH is lesser than the priority of the LCH and if the second LCH is associated with a different destination UE on the second hop, the source UE does not multiplex the data from the two LCHs. In some examples, the source UE may try to find data from other LCHs that is suitable for multiplexing or may send padding for the remaining bits of the TB. In additional or alternative examples, if the priority of the second LCH is lesser than the priority of the LCH and if the second LCH is associated to the same destination UE on the second hop, the source UE is allowed to multiplex the data from the two LCHs. In additional or alternative examples, if the priority of the second LCH is equal to the priority of the LCH and if the second LCH is associated to the same/different destination UE on the second hop, the source UE is allowed to multiplex data from the two LCHs.

[0061] In additional or alternative embodiments, if the size of the selection window for selecting resources for transmission of data belonging to the LCH is smaller than the selection window for selecting resources for transmission of data belonging to the second LCH (with the second highest priority), the source UE does not multiplex the data from the two LCHs. In some examples, the source UE may try to find data from other LCHs that is suitable for multiplexing or may send padding for the remaining bits of the TB.

[0062] In additional or alternative examples, if the size of the selection window of the second LCH is different from the selection window of the LCH with highest priority and if the second LCH is associated to the same destination UE on the second hop, the source UE is allowed to multiplex the data from the two LCHs.

[0063] In additional or alternative examples, if the source UE is allowed to multiplex data associated with LCHs with different selection windows, the source UE can choose to use the minimum of the different selection windows for the multiplexed data. In additional or alternative examples, if the source UE is allowed to multiplex data associated with LCHs with different selection windows, the source UE can choose to use the selection window associated with the higher priority LCH. [0064] In additional or alternative examples, if the size of the selection window of the second LCH is equal to the selection window size of the LCH with the highest priority and if the second LCH is associated to the same/different destination UE on the second hop, the source UE is allowed to multiplex data from the two LCHs.

[0065] Various embodiments herein are described in terms of the size of the selection window. That is, if the selection window corresponds to the slots in the interval [n+Tl,n+T2] (where n is a reference time), then the selection window size is T2-T1. These embodiments may also be defined in terms of the end of the selection window. For example, “z/ the end T2_a of the

[0066] Similarly, the embodiments may be defined in terms of a bound for the selection window end or size. For example, “z/ the bound T2min_a of the (end of the) selection window [...]

[0067] Some embodiments may be defined in terms of a parameter related to the selection window.

[0068] An example implementation corresponding to the operations illustrated in Appendices A and B is illustrated below. The bolded text indicating an example of changes to the specification.

2> SL data is available for transmission; and

3> If SL data is available for more than one destination remote UE and different logical channel priorities

3> If SL data is available for more than one destination remote UE and different sl-SelectionWindows configured

4> SL data from logical channels associated with only one destination remote UE is chosen

3> else if SL data is available for more than one destination remote UE and same logical channel priorities

3> If SL data is available for more than one destination remote UE and same sl-SelectionWindows configured

4> SL data from logical channels associated with one or more than one destination remote UE is chosen

2> sl-configuredGrantType 1 Allowed, if configured, is set to true in case the SL grant is a Configured Grant Type 1; and 2> sl-AllowedCG-List, if configured, includes the configured grant index associated to the SL grant; and

3> if PSFCH is configured for the sidelink grant associated to the

SCI:

4> sl-HARQ-FeedbackEnabled is set to enabled, if sl- HARQ-FeedbackEnabled is set to enabled for the highest priority logical channel satisfying the above conditions; or

4> sl-HARQ-FeedbackEnabled is set to disabled, if sl- HARQ-FeedbackEnabled is set to disabled for the highest priority logical channel satisfying the above conditions.

3> else:

4> sl-HARQ-FeedbackEnabled is set to disabled.

[0069] Operations of the communication device QQ200 (implemented using the structure of the block diagram of Figure 9) will now be discussed with reference to the flow chart of FIG. 6 according to some embodiments of inventive concepts. For example, modules may be stored in memory QQ210 of Figure 9, 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.

[0070] FIG. 6 illustrates an example of operations performed by a first communication device, also referred to as communication device QQ200. The method is described from the perspective of first data and second data, it should be understood that this may also be applicable to a third data and/or fourth communication device and so on.

[0071] At block 610, the first communication device such as its processing circuitry QQ202 determines to transmit first data to a second communication device aa part of a TB via a U2U relay.

[0072] At block 620, the first communication device such as its processing circuitry QQ202 determines whether to transmit second data to a third communication device as part of the TB via the U2U relay. In some embodiments, the first communication device determines whether to transmit the second data to the third communication device as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and/or a size of a selection window for resource allocation associated with transmission of the second data.

[0073] In some embodiments, the first communication device is a source of the first data and the second data. The second communication device is a destination communication device of the first data. The third communication device is a destination communication device of the second data.

[0074] At block 630, the first communication device such as its processing circuitry QQ202 transmits, via communication interface QQ212, the TB to the U2U relay.

[0075] In additional or alternative embodiments, determining whether to transmit the second data as part of the TB includes determining to transmit the second data as part of the TB based on determining that the priority associated with the second data is greater than or equal to a threshold priority. Transmitting the TB to the U2U relay includes transmitting the first data and the second data to the U2U relay as part of the TB.

[0076] In some examples, the threshold priority is a priority of the first data.

[0077] In additional or alternative examples, the priority of the first data is a priority of a first logical channel, LCH, associated with the first data.

[0078] In additional or alternative examples, the priority of the second data is a priority of a second logical channel, LCH, associated with the second data.

[0079] In additional or alternative embodiments, determining whether to transmit the second data as part of the TB includes determining to transmit the second data as part of the TB based on determining that the third communication device is the second communication device. Transmitting the TB to the U2U relay includes transmitting the first data and the second data to the U2U relay as part of the TB.

[0080] In additional or alternative embodiments, determining whether to transmit the second data as part of the TB includes: determining that the priority associated with the second data is less than a threshold priority; responsive to determining that the priority associated with the second data is less than the threshold priority, determining that the third communication device is the second communication device, and determining to transmit the second data as part of the TB based on determining that the third communication device is the second communication device. Transmitting the TB to the U2U relay comprises transmitting the first data and the second data to the U2U relay as part of the TB.

[0081] In additional or alternative embodiments, determining whether to transmit the second data as part of the TB includes determining to transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is less than or equal to a threshold size. Transmitting the TB to the U2U relay comprises transmitting the first data and the second data to the U2U relay as part of the TB. [0082] In additional or alternative embodiments, determining whether to transmit the second data as part of the TB includes determining to not transmit the second data as part of the TB based on determining that the priority associated with the second data is less than a threshold priority. Transmitting the TB to the U2U relay includes transmitting the first data to the U2U relay as part of the TB without the second data.

[0083] In additional or alternative embodiments, determining whether to transmit the second data as part of the TB further includes determining to not transmit the second data as part of the TB based on determining that the third communication device is separate from the second communication device. Transmitting the TB to the U2U relay comprises transmitting the first data to the U2U relay as part of the TB without the second data.

[0084] In additional or alternative embodiments, determining whether to transmit the second data as part of the TB includes determining to not transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is greater than the threshold size. Transmitting the TB to the U2U relay comprises transmitting the first data to the U2U relay as part of the TB without the second data.

[0085] In some examples, the threshold size is a size of a selection window for resource allocation associated with transmission of the first data.

[0086] In additional or alternative embodiments, determining whether to transmit the second data as part of the TB includes determining to not transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is different than a selection window for resource allocation associated with the first data. Transmitting the TB to the U2U relay comprises transmitting the first data to the U2U relay as part of the TB without the second data.

[0087] In some examples, transmitting the first data to the U2U relay as part of the TB without the second data includes transmitting the first data and dummy bits as part of the TB, the number of dummy data equal to a difference in a size of the first data and a size of the TB.

[0088] In additional or alternative examples, the selection window for resource allocation associated with the second data is different than a selection window for resource allocation associated with the first data. Determining whether to transmit the second data as part of the TB includes determining to transmit the second data as part of the TB, Transmitting the TB to the U2U relay comprises transmitting the first data and the second data to the U2U relay as part of the TB using a smaller of the selection window for resource allocation associated with the second data and the selection window for resource allocation associated with the first data.

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

[0090] Operations of the RAN node QQ300, also referred to as a network node QQ300, (implemented using the structure of Figure 10) 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 QQ304 of Figure 10, 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.

[0091] FIG.7 illustrates an example of operations performed by a network node.

[0092] At block 710, the network node such as its processing circuitry QQ302 determines that a first communication device will transmit first data to a second communication device aa part of a TB via a U2U relay.

[0093] At block 720, the network node such as its processing circuitry QQ302 determines whether to configure the first communication device to transmit second data to a third communication device as part of the TB via the U2U relay. In some embodiments, the network node determines whether to configure the first communication device to transmit the second data to the third communication device as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and/or a size of a selection window for resource allocation associated with transmission of the second data.

[0094] In some embodiments, the first communication device is a source of the first data and the second data. The second communication device is a destination communication device of the first data. The third communication device is a destination communication device of the second data.

[0095] At block 730, the network node such as its processing circuitry QQ202 transmits, via communication interface QQ306, configuration information to the first communication device. The configuration information includes an indication of whether the first communication device will transmit the second data as part of the TB.

[0096] In additional or alternative embodiments, determining whether to configure the communication device to transmit the second data as part of the TB includes determining to configure the communication device to transmit the second data as part of the TB based on determining that the priority associated with the second data is greater than or equal to a threshold priority.

[0097] In some examples, the threshold priority is a priority of the first data.

[0098] In additional or alternative examples, the priority of the first data is a priority of a first logical channel, LCH, associated with the first data.

[0099] In additional or alternative examples, the priority of the second data is a priority of a second logical channel, LCH, associated with the second data.

[00100] In additional or alternative embodiments, determining whether to configure the communication device to transmit the second data as part of the TB includes determining to configure the communication device to transmit the second data as part of the TB based on determining that the third communication device is the second communication device.

[00101] In additional or alternative embodiments, determining whether to configure the communication device to transmit the second data as part of the TB includes: determining that the priority associated with the second data is less than a threshold priority; responsive to determining that the priority associated with the second data is less than the threshold priority, determining that the third communication device is the second communication device; and determining to configure the communication device to transmit the second data as part of the TB based on determining that the third communication device is the second communication device. [00102] In additional or alternative embodiments, determining whether to transmit the second data as part of the TB includes determining to configure the communication device to transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is less than or equal to a threshold size. [00103] In additional or alternative embodiments, determining whether to configure the communication device to transmit the second data as part of the TB includes determining to configure the communication device to not transmit the second data as part of the TB based on determining that the priority associated with the second data is less than a threshold priority.

[00104] In additional or alternative embodiments, determining whether to configure the communication device to transmit the second data as part of the TB further includes determining to not transmit the second data as part of the TB based on determining that the third communication device is separate from the second communication device.

[00105] In additional or alternative embodiments, determining whether to configure the communication device to transmit the second data as part of the TB includes determining to configure the communication device to not transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is greater than the threshold size.

[00106] In some examples, the threshold size is a size of a selection window for resource allocation associated with transmission of the first data.

[00107] In additional or alternative embodiments, determining whether to configure the communication device to transmit the second data as part of the TB includes determining to configure the communication device to not transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is different than a selection window for resource allocation associated with the first data.

[00108] In some examples, transmitting the configuration information to the first communication device includes transmitting an instructions to the first communication device to cause the first data to be transmitted to the U2U relay as part of the TB without the second data. Furthermore, the configuration information can include instructions to cause the first communication device to transmit the first data and dummy bits as part of the TB, the number of dummy data equal to a difference in a size of the first data and a size of the TB.

[00109] In additional or alternative examples, transmitting the configuration information comprises transmitting instructions to cause the communication device to use a smaller of the selection window for resource allocation associated with the second data and the selection window for resource allocation associated with the first data.

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

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

[00112] 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. Moreover, as will be appreciated by those of skill in the art, the network nodes QQ110 are not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that the network nodes QQ110 may include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and/or core network nodes QQ108.

[00113] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time RAN control application (e.g., xApp) or a non-real time RAN automation application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Intents and content-aware notifications described herein may be communicated from a 3 GPP network node or an ORAN network node over 3GPP-defined interfaces (e.g., N2, N3) and/or ORAN Alliance-defined interfaces (e.g., Al, 01). Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting wireless devices 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. 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.

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

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

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

[00118] As a whole, the communication system QQ100 of Figure 8 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.

[00119] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs. [00120] In some examples, the UEs QQ112 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC). [00121] 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.

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

[00123] Figure 9 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 (3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

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

[00125] 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 9. 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.

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

[00128] 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. [00129] 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.

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

[00131] 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. [00132] 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. [00133] 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).

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

[00135] 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 9.

[00136] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 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.

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

[00138] Figure 10 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), NR NodeBs (gNBs)), 0-RAN nodes, or components of an 0-RAN node (e.g., intelligent controller, 0-RU, 0-DU, O-CU).

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

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

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

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

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

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

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

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

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

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

[00150] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 10 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.

[00151] Figure 11 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 8, 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.

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

[00153] 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 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. [00154] Figure 12 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the 0-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

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

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

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

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

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

[00160] Figure 13 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 8 and/or UE QQ200 of Figure 9), network node (such as network node QQ110a of Figure 8 and/or network node QQ300 of Figure 10), and host (such as host QQ116 of Figure 8 and/or host QQ400 of Figure 11) discussed in the preceding paragraphs will now be described with reference to Figure 13.

[00161] 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. [00162] 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 8) 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.

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

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

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

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

[00167] 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 enable the prevention of unnecessary transmission preemption for UEs operating in mode-l/mode-2 resource allocation (e.g., prevents blocking the channel for other UEs in the system).

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

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

[00170] 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. [00171] 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 first communication device, the method comprising: determining (610) to transmit first data to a second communication device as part of a transport block, TB, via a communication device-to-communi cation device, U2U, relay; determining (620) whether to transmit second data to a third communication device as part of the TB via the U2U relay based on at least one of: a priority associated with the second data; an identity of the third communication device; and/or a size of a selection window for resource allocation associated with transmission of the second data; and transmitting (630) the TB to the U2U relay.

2. The method of Embodiment 1, wherein the first communication device is a source of the first data and the second data, wherein the second communication device is a destination communication device of the first data, and wherein the third communication device is a destination communication device of the second data.

3. The method of any of Embodiments 1-2, wherein determining whether to transmit the second data as part of the TB comprises determining to transmit the second data as part of the TB based on determining that the priority associated with the second data is greater than or equal to a threshold priority, and wherein transmitting the TB to the U2U relay comprises transmitting the first data and the second data to the U2U relay as part of the TB.

4. The method of any of Embodiments 1-3, wherein determining whether to transmit the second data as part of the TB comprises determining to transmit the second data as part of the TB based on determining that the third communication device is the second communication device, and wherein transmitting the TB to the U2U relay comprises transmitting the first data and the second data to the U2U relay as part of the TB.

5. The method of Embodiment 1, wherein determining whether to transmit the second data as part of the TB comprises: determining that the priority associated with the second data is less than a threshold priority; responsive to determining that the priority associated with the second data is less than the threshold priority, determining that the third communication device is the second communication device, and determining to transmit the second data as part of the TB based on determining that the third communication device is the second communication device, and wherein transmitting the TB to the U2U relay comprises transmitting the first data and the second data to the U2U relay as part of the TB.

6. The method of any of Embodiments 1-5, wherein determining whether to transmit the second data as part of the TB comprises determining to transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is less than or equal to a threshold size, and wherein transmitting the TB to the U2U relay comprises transmitting the first data and the second data to the U2U relay as part of the TB.

7. The method of any of Embodiments 1-2, wherein determining whether to transmit the second data as part of the TB comprises determining to not transmit the second data as part of the TB based on determining that the priority associated with the second data is less than a threshold priority, and wherein transmitting the TB to the U2U relay comprises transmitting the first data to the U2U relay as part of the TB without the second data.

8. The method of any of Embodiments 1-2 and 7, wherein determining whether to transmit the second data as part of the TB further comprises determining to not transmit the second data as part of the TB based on determining that the third communication device is separate from the second communication device, and wherein transmitting the TB to the U2U relay comprises transmitting the first data to the U2U relay as part of the TB without the second data.

9. The method of any of Embodiments 1-2 and 7-8, wherein determining whether to transmit the second data as part of the TB comprises determining to not transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is greater than the threshold size, and wherein transmitting the TB to the U2U relay comprises transmitting the first data to the U2U relay as part of the TB without the second data.

10. The method of any of Embodiments 5 and 7-8, wherein the threshold size is a size of a selection window for resource allocation associated with transmission of the first data.

11. The method of any of Embodiments 1-2, wherein determining whether to transmit the second data as part of the TB comprises determining to not transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is different than a selection window for resource allocation associated with the first data, and wherein transmitting the TB to the U2U relay comprises transmitting the first data to the U2U relay as part of the TB without the second data.

12. The method of any of Embodiments 7-11, wherein transmitting the first data to the U2U relay as part of the TB without the second data comprises transmitting the first data and dummy bits as part of the TB, the number of dummy data equal to a difference in a size of the first data and a size of the TB.

13. The method of any of Embodiments 3, 5, and 7, wherein the threshold priority is a priority of the first data.

14. The method of Embodiment 13, wherein the priority of the first data is a priority of a first logical channel, LCH, associated with the first data.

15. The method of any of Embodiments 1-2, wherein the selection window for resource allocation associated with the second data is different than a selection window for resource allocation associated with the first data, wherein determining whether to transmit the second data as part of the TB comprises determining to transmit the second data as part of the TB, and wherein transmitting the TB to the U2U relay comprises transmitting the first data and the second data to the U2U relay as part of the TB using a smaller of the selection window for resource allocation associated with the second data and the selection window for resource allocation associated with the first data. 16. The method of any of Embodiments 1-15, wherein the priority of the second data is a priority of a second logical channel, LCH, associated with the second data.

17. A method of operating a network node in a communications network that includes a first communication device, the method comprising: determining (710) that the first communication device will transmit first data to a second communication device as part of a transport block, TB, via a communication device-to- communication device, U2U, relay; determining (720) whether to configure the first communication device to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and/or a size of a selection window for resource allocation associated with transmission of the second data; and transmitting (730) configuration information to the first communication device, the configuration information including an indication of whether the first communication device will transmit the second data as part of the TB.

18. The method of Embodiment 16, wherein the first communication device is a source of the first data and the second data, wherein the second communication device is a destination communication device of the first data, and wherein the third communication device is a destination communication device of the second data.

19. The method of any of Embodiments 17-18, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to transmit the second data as part of the TB based on determining that the priority associated with the second data is greater than or equal to a threshold priority.

20. The method of any of Embodiments 17-19, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to transmit the second data as part of the TB based on determining that the third communication device is the second communication device.

21. The method of Embodiment 17, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises: determining that the priority associated with the second data is less than a threshold priority; responsive to determining that the priority associated with the second data is less than the threshold priority, determining that the third communication device is the second communication device, and determining to configure the first communication device to transmit the second data as part of the TB based on determining that the third communication device is the second communication device.

22. The method of any of Embodiments 17-21, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is less than or equal to a threshold size.

23. The method of any of Embodiments 17-18, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to not transmit the second data as part of the TB based on determining that the priority associated with the second data is less than a threshold priority.

24. The method of any of Embodiments 17-18 and 23, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to not transmit the second data as part of the TB based on determining that the third communication device is separate from the second communication device.

25. The method of any of Embodiments 17-18 and 23-24, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to not transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is greater than the threshold size.

26. The method of any of Embodiments 22 and 25, wherein the threshold size is a size of a selection window for resource allocation associated with transmission of the first data.

27. The method of any of Embodiments 17-18, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to not transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is different than a selection window for resource allocation associated with the first data.

28. The method of any of Embodiments 23-27, wherein transmitting the configuration information to the first communication device indicating that the first communication device transmit the first data as part of the TB without the second data comprises transmitting instructions to cause the communication device to transmit the first data and dummy bits as part of the TB, the number of dummy data equal to a difference in a size of the first data and a size of the TB.

29. The method of any of Embodiments 19, 21, and 23, wherein the threshold priority is a priority of the first data.

30. The method of Embodiment 29, wherein the priority of the first data is a priority of a first logical channel, LCH, associated with the first data.

31. The method of any of Embodiments 17-30, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to transmit the second data as part of the TB, and wherein transmitting the configuration information to the first communication device indicating that the first communication device transmits the first data and the second data as part of the TB comprises transmitting instructions to cause the communication device to transmit the first data and the second data using a smaller of the selection window for resource allocation associated with the second data and a selection window for resource allocation associated with the first data. 32. The method of any of Embodiments 17-31, wherein the priority of the second data is a priority of a second logical channel, LCH, associated with the second data.

33. A communication device (QQ200), 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 communication device to perform operations comprising any of the operations of Embodiments 1-16.

34. A computer program comprising program code to be executed by processing circuitry (QQ202) of a communication device (QQ200), whereby execution of the program code causes the communication device to perform operations comprising any operations of Embodiments 1- 16.

35. 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), whereby execution of the program code causes the entity to perform operations comprising any operations of Embodiments 1-16.

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

37. A network node (QQ300), the network node 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 network node to perform operations comprising any of the operations of Embodiments 17-32.

38. A computer program comprising program code to be executed by processing circuitry (QQ302) of a network node (QQ300), whereby execution of the program code causes the network node to perform operations comprising any operations of Embodiments 17-32. 39. 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), whereby execution of the program code causes the network node to perform operations comprising any operations of Embodiments 17-32.

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

41. 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: determining (710) that the first communication device will transmit first data to second communication device as part of a transport block, TB, via a communication device-to- communication device, U2U, relay; determining (720) whether to configure the first communication device to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and a size of a selection window for resource allocation associated with transmission of the second data; and transmitting (730) configuration information to the first communication device, the configuration information including an indication of whether the first communication device will transmit the second data as part of the TB.

42. 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. 43. 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: determining (710) that the first communication device will transmit first data to second communication device as part of a transport block, TB, via a communication device-to- communication device, U2U, relay; determining (720) whether to configure the first communication device to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and a size of a selection window for resource allocation associated with transmission of the second data; and transmitting (730) configuration information to the first communication device, the configuration information including an indication of whether the first communication device will transmit the second data as part of the TB.

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

45. 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.

46. 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: determining (710) that the first communication device will transmit first data to second communication device as part of a transport block, TB, via a communication device-to- communication device, U2U, relay; determining (720) whether to configure the first communication device to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and a size of a selection window for resource allocation associated with transmission of the second data; and transmitting (730) configuration information to the first communication device, the configuration information including an indication of whether the first communication device will transmit the second data as part of the TB.

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

48. 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.

49. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to 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: determining (710) that the first communication device will transmit first data to second communication device as part of a transport block, TB, via a communication device-to- communication device, U2U, relay; determining (720) whether to configure the first communication device to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of a priority associated with the second data; an identity of the third communication device; and a size of a selection window for resource allocation associated with transmission of the second data; and transmitting (730) configuration information to the first communication device, the configuration information including an indication of whether the first communication device will transmit the second data as part of the TB.

50. 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.

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

52. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, 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: determining (710) that the first communication device will transmit first data to second communication device as part of a transport block, TB, via a communication device-to- communication device, U2U, relay; determining (720) whether to configure the first communication device to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and a size of a selection window for resource allocation associated with transmission of the second data; and transmitting (730) configuration information to the first communication device, the configuration information including an indication of whether the first communication device will transmit the second data as part of the TB.

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

54. 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 (610) to transmit first data to second communication device as part of a transport block, TB, via a communication device-to-communi cation device, U2U, relay; determining (620) whether to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and/or a size of a selection window for resource allocation associated with transmission of the second data; and transmitting (630) the TB to the U2U relay.

55. 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.

56. 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. 57. 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 (610) to transmit first data to second communication device as part of a transport block, TB, via a communication device-to-communi cation device, U2U, relay; determining (620) whether to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and/or a size of a selection window for resource allocation associated with transmission of the second data; and transmitting (630) the TB to the U2U relay.

58. 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.

59. 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.

60. 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 (610) to transmit first data to second communication device as part of a transport block, TB, via a communication device-to-communi cation device, U2U, relay; determining (620) whether to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and/or a size of a selection window for resource allocation associated with transmission of the second data; and transmitting (630) the TB to the U2U relay.

61. 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.

62. 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.

63. 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 (610) to transmit first data to second communication device as part of a transport block, TB, via a communication device-to-communi cation device, U2U, relay; determining (620) whether to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and/or a size of a selection window for resource allocation associated with transmission of the second data; and transmitting (630) the TB to the U2U relay.

64. 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.

65. 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.

ABBREVIATIONS

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

LCH Logical Channel

LCP Logical Channel Prioritization

TB Transport Block

RRC Radio Resource Control

U2U UE-to-UE

Ix RTT CDMA2000 lx Radio Transmission Technology

3 GPP 3rd Generation Partnership Project

5G 5th Generation

6G 6th Generation

ABS Almost Blank Subframe

ARQ Automatic Repeat Request

AWGN Additive White Gaussian Noise

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response

CP Cyclic Prefix

CPICH Common Pilot Channel

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

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

DUT Device Under Test

E-CID Enhanced Cell-ID (positioning method) eMBMS evolved Multimedia Broadcast Multicast Services E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH Enhanced Physical Downlink Control Channel

E-SMLC Evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

FDD Frequency Division Duplex

FFS For Further Study gNB Base station in NR GNSS Global Navigation Satellite System

HARQ Hybrid Automatic Repeat Request

HO Handover

HSPA High Speed Packet Access

HRPD High Rate Packet Data

LOS Line of Sight

LPP LTE Positioning Protocol

LTE Long-Term Evolution

MAC Medium Access Control

MAC Message Authentication Code

MBSFN Multimedia Broadcast multicast service Single Frequency Network

MBSFN ABS MBSFN Almost Blank Subframe

MDT Minimization of Drive Tests

MIB Master Information Block

MME Mobility Management Entity

MSC Mobile Switching Center

NPDCCH Narrowband Physical Downlink Control Channel

NR New Radio OCNG OFDM A Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OSS Operations Support System

OTDOA Observed Time Difference of Arrival

O&M Operation and Maintenance

PBCH Physical Broadcast Channel

P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PCFICH Physical Control Format Indicator Channel

PDCCH Physical Downlink Control Channel

PDCP Packet Data Convergence Protocol

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel

PGW Packet Gateway

PHICH Physical Hybrid-ARQ Indicator Channel

PLMN Public Land Mobile Network

PMI Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RAN Radio Access Network

RAT Radio Access Technology

RLC Radio Link Control

RLM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR Reference Signal Received Power

RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality

RS SI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell

SDAP Service Data Adaptation Protocol

SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway

SI System Information

SIB System Information Block

SNR Signal to Noise Ratio

SON Self Optimized Network ss Synchronization Signal sss Secondary Synchronization Signal

TDD Time Division Duplex

TDOA Time Difference of Arrival

TOA Time of Arrival

TSS Tertiary Synchronization Signal

TTI Transmission Time Interval

UE User Equipment

UL Uplink

USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival

WCDMA Wide CDMA

WLAN Wide Local Area Network APPENDIX A

3GPP TS 38.211/4

8.1.4 UE procedure for determining the subset of resources to be reported to higher layers in PSSCH resource selection in sidelink resource allocation mode 2

In resource allocation mode 2, the higher layer can request the UE to determine a subset of resources from which the higher layer will select resources for PSSCH/PSCCH transmission. To trigger this procedure, in slot n, the higher layer provides the following parameters for this PSSCH/PSCCH transmission:

- the resource pool from which the resources are to be reported;

- LI priority, prio_TX,'

- the remaining packet delay budget;

- the number of sub-channels to be used for the PSSCH/PSCCH transmission in a slot, 'subCHi

[ •]

The following higher layer parameters affect this procedure:

- sl-SelectionWindowList'. internal parameter T_2min is set to the corresponding value from higher layer parameter sl-SelectionWindowList for the given value of prio_TX.

[ •]

The following steps are used:

1) A candidate single-slot resource for transmission R_{x y} is defined as a set of L_subCH contiguous sub-channels with sub-channel x+j in slot t' ^L where j = 0, . . . , L_subCH ^— 1 The UE shall assume that any set of L_subCH contiguous sub-channels included in the corresponding resource pool within the time interval [n + T₁, n + T₂] correspond to one candidate single-slot resource for UE performing full sensing, in a set of Y candidate slots within the time interval [n + T₁, n + T₂] correspond to one candidate single-slot resource for UE performing periodic-based partial sensing together with contiguous partial sensing and resource (re)selection triggered by periodic transmission (P_{rsvp TX} A 0), or in a set of Y' candidate slots within the time interval [n + 7 , n + T₂] correspond to one candidate single-slot resource for UE performing at least contiguous partial sensing and resource (re)selection triggered by aperiodic transmission (P_{rsvp TX} = 0), where

- selection of 7 is up to UE implementation under 0 < T < is defined in slots in Table 8.1.4-2 where p_SL is the SCS configuration of the SL BWP;

■ if T_2min is shorter than the remaining packet delay budget (in slots) then T₂ is up to UE implementation subject to T_2min < T₂ < remaining packet delay budget (in slots); otherwise T₂ is set to the remaining packet delay budget (in slots).

[ •]

The UE shall report set S_A to higher layers.

APPENDIX B

3GPP TS 38.211/4

5.22.1.1 SL Grant reception and SCI transmission

[ •]

1> if the MAC entity has selected to create a selected sidelink grant corresponding to transmission(s) of a single MAC PDU, and if SL data is available in a logical channel, or an SL-CSI reporting is triggered, or a Sidelink DRX Command indication is triggered or a Sidelink Inter-UE Coordination Information reporting is triggered, or a Sidelink Inter-UE Coordination Request is triggered:

[ •]

2>else if SL data for NR sidelink communication is available in the logical channel:

3> if sl-HARQ-FeedbackEnabled is set to enabled for the logical channel:

4> select any pool of resources configured with PSFCH resources among the pools of resources except the pool(s) in sl-BWP-DiscPoolConfig or sl-BWP- DiscPoolConfigCommon, if configured.

3>else:

4> select any pool of resources among the pools of resources except the pool(s) in sl- BWP-DiscPoolConfig or sl-BWP-DiscPoolConfigCommon, if configured.

[ •]

2> perform the TX resource (re-) sei ection check on the selected pool of resources as specified in clause 5.22.1.2;

2> if the TX resource (re-)selection is triggered as the result of the TX resource

(re-) sei ection check:

3> if one or multiple SL DRX(s) is configured in the destination UE(s) receiving SL- SCH data:

4> indicate to the physical layer SL DRX Active time in the destination UE(s) receiving SL-SCH data, as specified in clause 5.28.2.

3> select the number of HARQ retransmissions from the allowed numbers, if configured by RRC, in sl-MaxTxTransNumPSSCH included in sl-PSSCH- TxConfigList and, if configured by RRC, overlapped in sl-MaxTxTransNumPSSCH indicated in sl-CBR-PriorityTxConfigList for the highest priority of the logical channel(s) allowed on the carrier and the CBR measured by lower layers according to clause 5.1.27 of TS 38.215 [24] if CBR measurement results are available or the corresponding sl-defaultTxConfiglndex configured by RRC if CBR measurement results are not available;

3> select an amount of frequency resources within the range, if configured by RRC, between sl-MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH included in sl-PSSCH-TxConfigList and, if configured by RRC, overlapped between sl-MinSubChannelNumPSSCH and sl-MaxSubChannelNumPSSCH indicated in sl-

CBR-PriorityTxConfigList for the highest priority of the logical channel(s) allowed on the carrier and the CBR measured by lower layers according to clause 5.1.27 of TS 38.215 [24] if CBR measurement results are available or the corresponding sl- defaultTxConfiglndex configured by RRC if CBR measurement results are not available;

[ •]

APPENDIX C

3GPP TS38.300, Sections 16.12, 16.12.7

3GPP TS 38.331, Sections 5.8.13.3, 5.3.5.16

1 Introduction

The following agreements were made in the RAN#121 meeting on the CP aspects for U2U relays:

In this paper we’ll discuss the Layer-2 specific aspects and RAN2 details for the control plane (CP) procedures, adaptation layer design and QoS handling based on SA2’s progress.

2 Discussion

The descriptions below are written in the context of a source remote (SRC) UE communicating with one or more destination (DST) remote UEs via a relay UE (U2U relay).

2.2 SRAP Layer Design

It was agreed in the last meeting that the E2E RB ID of the remote UE is included in the adaptation layer. In addition, it was also agreed that the remote UE determines the egress PC5 RLC channel based on bearer mapping i.e., E2E bearer ID to egress RLC channel, for a particular DST UE.

Similarly, based on the E2E bearer ID, the adaptation layer in the U2U relay should perform bearer mapping like in Layer-2 U2N relaying i.e., U2U relay performs a mapping from the SRC UE’s E2E bearer ID to an egress PC5 RLC channel on the second hop.

U2U relay determines the egress RLC channel based on mapping from a SRC UE’s E2E bearer ID to egress RLC channel of a particular DST UE.

For the mappable ID on the first and second hop, we believe that the SRC ID is sufficient. On the second hop, the combination of the SRC ID and the E2E bearer ID is sufficient for mapping to the egress RLC channel of a particular DST UE. The adaptation layer should only perform bearer mapping.

SRC ID should be included in the adaptation layer in the first and second hop.

Further, as the adaptation layer header is unprotected, local ID can be used as in Rel-17 L2 U2N relaying.

Local IDs are used to identify the SRC and DST UEs.

This local ID should be unique for a SRC and DST UE and different values should be assigned for the SRC and DST. By assigning different values, if required, it is possible to reconfigure only one link without affecting the other link. For example, if there is a change in the local ID and if the local ID was common, then both the first and second hop links would have to be reconfigured to use the new local ID. As opposed to having different values where the change in the local ID over one link will not affect the other link.

Different local IDs are assigned to the SRC and DST UEs.

Unlike in the case of U2N relaying, in U2U relaying, the SRC/DST/U2U relays would need to operate in any coverage scenario i.e., in-coverage, partial coverage and out-of-coverage. In which case, it is not possible to rely on the gNB to provide the appropriate configurations and local ID assignments. As a result, we believe the U2U relay should be responsible for the appropriate bearer mapping and should also be the one to assign the local IDs to the SRC/DST UEs.

The U2U relay assigns the local ID for the SRC and DST UEs.

Observation 16 FFS if multiplexing of different destinations in the same RLC channel is supported.

We discuss the case for the first hop and second hop separately.

Multiplexing over first hop:

The SRC UE can multiplex data intended for different destinations from the same U2U relay over the first hop i.e., N-to-1 mapping over the first hop. In this case, the adaptation layer can consist of the SRC ID and E2E bearer IDs of the different destinations. The SRC UE can map the E2E bearer IDs to a single egress RLC channel on the first hop.

The U2U relay upon receiving the data from this RLC channel, can based on using the SRC ID an E2E bearer IDs demultiplex the data and perform the corresponding mapping of the E2E bearer ID to the appropriate egress RLC channel for a particular DST UE in the second hop.

Multiplexing over second hop:

Upon receiving the data from multiple SRC UEs at the adaptation layer, the U2U relay can determine if there are multiple SRC UEs communicating with the same DST UE. In which case, the U2U relay can multiplex the data for the same destination from different SRC UEs over the second hop i.e., N-to-1 mapping over the second hop.

The U2U relay can based on the SRC IDs and E2E bearer IDs multiplex the data intended for one DST and perform the corresponding mapping of the E2E bearer IDs to a single egress RLC channel over the second hop.

In general, multiplexing over the first/second hop is upto SRC UE and U2U relay implementation. In addition, bearer mapping at both the SRC UE and U2U relay with SRC ID and E2E bearer ID in the header of the adaptation layer is sufficient to enable multiplexing over the first and second hop. 2.3 QoS Handling

For QoS split, in L2 U2N relaying, it is up to gNB implementation to perform PDB split between Uu hop and PC5 hop. For L2 U2U relaying, however, gNB should not be involved in the QoS split as the UEs might be in out-of-coverage and the traffic does not go through the network. In our view, the QoS split shall be performed by the U2U relay as it knows the channel situation of both the links i.e., first hop and the second hop.

The U2U relay configures the QoS split for the end-to-end unicast link.

Moreover, to avoid that the SRC UE is unhappy with the QoS split configured by the U2U relay, the SRC UE may provide some assistance information to the U2U relay which takes this into account when configuring the QoS split.

SRC UE can provide the U2U relay with assistance info to assist in splitting the QoS.

2.4 Multiplexing at the MAC-layer

In the previous meeting, there was a discussion on the multiplexing of data from the different logical channels in the MAC-layer. In general, for direct sidelink without relaying, it would make sense to multiplex the data from the different logical channels as they are intended for the same destination over the first hop. However, for U2U relaying, it is likely that the different logical channels are associated to different destinations over the second hop. As a result, the current LCP procedure will always allow multiplexing of the data intended for different final destinations over the first hop i.e., the source remote UE will always be allowed to multiplex the data intended for different final destinations over the first hop to the U2U relay.

However, we believe there are issues when the source remote UE is always allowed to multiplex the data intended for different destinations over the first hop:

• As the different logical channels are associated with different (final) destination remote UEs, it is possible that low priority transmissions get a treatment above its indicated priority. Thereby degrading the performance of the other UEs in the system. In addition, as the source remote UE can communicate with multiple final destinations further exacerbating the problem.

• For mode-2, the selection window (sl-SelectionWindow-r16) is configured independently for each priority value (sl-Priority-r16). In which case, it is possible that the sl-SelectionWindow-r16 are different for different (final) destination remote UEs i.e., T1 for destination remote UE1 , T2 for destination remote UE2 and T1 < T2. The source remote UE can select resources for transmission using T2 in which case multiplexing would of data could result in the PDB not being satisfied for one of the (final) destination remote UEs. The same is also applicable for the case when a high priority data arrives for a different (final) destination UEs.

Based on our concerns above, we think RAN2 should discuss the issue of multiplexing of data at the MAC- layer when the LCHs associated with different (final) destination remote UEs. One possible way to deal with the issue would be to capture an LCP restriction when multiplexing data associated with different (final) destination remote UEs.

RAN2 to discuss the issue of multiplexing of data at the MAC-layer when the LCHs are associated with different (final) destination remote UEs.

2.1 End-to-End Connection Establishment

As mentioned above, SA2 has concluded the following procedures for connection establishment in L2 and L3 U2U relays [2]: a. Standalone Discovery Procedure based PC5 end-to-end unicast link establishment b. Integrated PC5 end-to-end unicast link establishment

Although SA2 has specified the solutions, the details for the L2 U2U relaying have not yet been captured and is up to RAN2 to finalize the details. In addition, RAN2 also needs to discuss the details of the sidelink relay adaptation protocol (SRAP) layer and handling of end-to-end QoS. Figure 1 below illustrates the RAN2 related CP procedures in L2 U2U relaying for link establishment based on the details as captured in [2].

Although SA2 has specified the solutions for standalone and integrated end-to-end unicast link establishment in general, the details for L2 U2U relaying have not yet been captured. RAN2 needs to finalize the details and in addition, study the aspects of SRAP and QoS handling.

(a) Standalone Discovery Procedure based PC5 end-to-end unicast link establishment

(b) Integrated PC5 end-to-end unicast link establishment

Figure 1. Connection Establishment Procedure for L2 U2U relays

The following are the steps involved in the end-to-end connection establishment procedure for both cases (a) and (b). The order of these steps can vary but the intention is to use the following as a starting point for discussions.

1. With a standalone procedure, the SRC UE performs a discovery procedure (using model A/B) to find the DST UE. In the integrated procedure, the SRC UE initiates a direct communication request message (contents of which are decided by SA2) to find the DST UE.

2. In the integrated procedure, the DST UE then performs the relay selection. Then, in both procedures, a PC5 link establishment/modification can be performed.

3. In both procedures, the U2U relay can then configure the SRC UE and DST UE with the SRAP configuration along with the local ID(s).

4. Subsequent messages for establishing an end-to-end unicast link are transmitted using the SRAP layer. 5. Once the end-to-end unicast link is established, the per-hop bearer mapping with the option to perform QoS split can be performed.

RAN2 to consider Figure 1. as the baseline for L2 U2U relaying in PC5 end-to-end link establishment for cases (a) and (b).

Claims

2. The method of Claim 1, wherein the first communication device is a source of the first data and the second data, wherein the second communication device is a destination communication device of the first data, and wherein the third communication device is a destination communication device of the second data.

3. The method of any of Claims 1-2, wherein determining whether to transmit the second data as part of the TB comprises determining to transmit the second data as part of the TB based on determining that the priority associated with the second data is greater than or equal to a threshold priority, and wherein transmitting the TB to the U2U relay comprises transmitting the first data and the second data to the U2U relay as part of the TB.

4. The method of any of Claims 1-3, wherein determining whether to transmit the second data as part of the TB comprises determining to transmit the second data as part of the TB based on determining that the third communication device is the second communication device, and wherein transmitting the TB to the U2U relay comprises transmitting the first data and the second data to the U2U relay as part of the TB.

5. The method of Claim 1, wherein determining whether to transmit the second data as part of the TB comprises: determining that the priority associated with the second data is less than a threshold priority; responsive to determining that the priority associated with the second data is less than the threshold priority, determining that the third communication device is the second communication device, and determining to transmit the second data as part of the TB based on determining that the third communication device is the second communication device, and wherein transmitting the TB to the U2U relay comprises transmitting the first data and the second data to the U2U relay as part of the TB.

6. The method of any of Claims 1-5, wherein determining whether to transmit the second data as part of the TB comprises determining to transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is less than or equal to a threshold size, and wherein transmitting the TB to the U2U relay comprises transmitting the first data and the second data to the U2U relay as part of the TB.

7. The method of any of Claims 1-2, wherein determining whether to transmit the second data as part of the TB comprises determining to not transmit the second data as part of the TB based on determining that the priority associated with the second data is less than a threshold priority, and wherein transmitting the TB to the U2U relay comprises transmitting the first data to the U2U relay as part of the TB without the second data.

8. The method of any of Claims 1-2 and 7, wherein determining whether to transmit the second data as part of the TB further comprises determining to not transmit the second data as part of the TB based on determining that the third communication device is separate from the second communication device, and wherein transmitting the TB to the U2U relay comprises transmitting the first data to the U2U relay as part of the TB without the second data.

9. The method of any of Claims 1-2 and 7-8, wherein determining whether to transmit the second data as part of the TB comprises determining to not transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is greater than the threshold size, and wherein transmitting the TB to the U2U relay comprises transmitting the first data to the U2U relay as part of the TB without the second data.

10. The method of any of Claims 5 and 7-8, wherein the threshold size is a size of a selection window for resource allocation associated with transmission of the first data.

11. The method of any of Claims 1-2, wherein determining whether to transmit the second data as part of the TB comprises determining to not transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is different than a selection window for resource allocation associated with the first data, and wherein transmitting the TB to the U2U relay comprises transmitting the first data to the U2U relay as part of the TB without the second data.

12. The method of any of Claims 7-11, wherein transmitting the first data to the U2U relay as part of the TB without the second data comprises transmitting the first data and dummy bits as part of the TB, the number of dummy data equal to a difference in a size of the first data and a size of the TB.

13. The method of any of Claims 3, 5, and 7, wherein the threshold priority is a priority of the first data.

14. The method of Claim 13, wherein the priority of the first data is a priority of a first logical channel, LCH, associated with the first data.

15. The method of any of Claims 1-2, wherein the selection window for resource allocation associated with the second data is different than a selection window for resource allocation associated with the first data, wherein determining whether to transmit the second data as part of the TB comprises determining to transmit the second data as part of the TB, and wherein transmitting the TB to the U2U relay comprises transmitting the first data and the second data to the U2U relay as part of the TB using a smaller of the selection window for resource allocation associated with the second data and the selection window for resource allocation associated with the first data.

16. The method of any of Claims 1-15, wherein the priority of the second data is a priority of a second logical channel, LCH, associated with the second data.

17. A method of operating a network node in a communications network that includes a first communication device, the method comprising: determining (710) that the first communication device will transmit first data to second communication device as part of a transport block, TB, via a communication device-to- communication device, U2U, relay; determining (720) whether to configure the first communication device to transmit second data to a third communication device via the U2U relay as part of the TB based on at least one of: a priority associated with the second data; an identity of the third communication device; and/or a size of a selection window for resource allocation associated with transmission of the second data; and transmitting (730) configuration information to the first communication device, the configuration information including an indication of whether the first communication device will transmit the second data as part of the TB.

18. The method of Claim 17, wherein the first communication device is a source of the first data and the second data, wherein the second communication device is a destination communication device of the first data, and wherein the third communication device is a destination communication device of the second data.

19. The method of any of Claims 17-18, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to transmit the second data as part of the TB based on determining that the priority associated with the second data is greater than or equal to a threshold priority.

20. The method of any of Claims 17-19, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to transmit the second data as part of the TB based on determining that the third communication device is the second communication device.

21. The method of Claim 17, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises: determining that the priority associated with the second data is less than a threshold priority; responsive to determining that the priority associated with the second data is less than the threshold priority, determining that the third communication device is the second communication device, and determining to configure the first communication device to transmit the second data as part of the TB based on determining that the third communication device is the second communication device.

22. The method of any of Claims 17-21, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is less than or equal to a threshold size.

23. The method of any of Claims 17-18, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to not transmit the second data as part of the TB based on determining that the priority associated with the second data is less than a threshold priority.

24. The method of any of Claims 17-18 and 23, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to not transmit the second data as part of the TB based on determining that the third communication device is separate from the second communication device.

25. The method of any of Claims 17-18 and 23-24, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to not transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is greater than the threshold size.

26. The method of any of Claims 22 and 25, wherein the threshold size is a size of a selection window for resource allocation associated with transmission of the first data.

27. The method of any of Claims 17-18, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to not transmit the second data as part of the TB based on determining that the selection window for resource allocation associated with the second data is different than a selection window for resource allocation associated with the first data.

28. The method of any of Claims 23-27, wherein transmitting the configuration information to the first communication device indicating that the first communication device transmit the first data as part of the TB without the second data comprises transmitting instructions to cause the communication device to transmit the first data and dummy bits as part of the TB, the number of dummy data equal to a difference in a size of the first data and a size of the TB.

29. The method of any of Claims 19, 21, and 23, wherein the threshold priority is a priority of the first data.

30. The method of Claim 29, wherein the priority of the first data is a priority of a first logical channel, LCH, associated with the first data.

31. The method of any of Claims 17-30, wherein determining whether to configure the first communication device to transmit the second data as part of the TB comprises determining to configure the first communication device to transmit the second data as part of the TB, and wherein transmitting the configuration information to the first communication device indicating that the first communication device transmits the first data and the second data as part of the TB comprises transmitting instructions to cause the communication device to transmit the first data and the second data using a smaller of the selection window for resource allocation associated with the second data and a selection window for resource allocation associated with the first data.

32. The method of any of Claims 17-31, wherein the priority of the second data is a priority of a second logical channel, LCH, associated with the second data.

33. A communication device (QQ200), 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 communication device to perform operations comprising any of the operations of Claims 1-16.

34. A computer program comprising program code to be executed by processing circuitry (QQ202) of a communication device (QQ200), whereby execution of the program code causes the communication device to perform operations comprising any operations of Claims 1-16.

35. 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), whereby execution of the program code causes the entity to perform operations comprising any operations of Claims 1-16.

36. A non-transitory computer-readable medium having instructions stored therein that are executable by processing circuitry (QQ202) of an communication device (QQ200) to cause the communication device to perform operations comprising any of the operations of Claims 1-16.

37. A network node (QQ300), the network node 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 network node to perform operations comprising any of the operations of Claims 17-32.

38. A computer program comprising program code to be executed by processing circuitry (QQ302) of a network node (QQ300), whereby execution of the program code causes the network node to perform operations comprising any operations of Claims 17-32.

39. 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), whereby execution of the program code causes the network node to perform operations comprising any operations of Claims 17-32.

40. A non-transitory computer-readable medium having instructions stored therein that are executable by processing circuitry (QQ302) of a network node (QQ300) to cause the network node to perform operations comprising any of the operations of Claims 17-32.