Intra-ue overlapping resources

Abstract

A method for intra-UE prioritization at a user equipment (UE) is provided. The UE determines whether a transmission overlaps in time with another transmission and if so, the UE prioritizes one of the

Description

BACKGROUND Field

[0001] Certain examples of the present disclosure provide various techniques relating to prioritization of user equipment (UE) transmissions having overlapping time resources, for example within 3rd Generation Partnership Project (3GPP) 5th Generation (5G) New Radio (NR) networks. Description of the Related Art

[0002] Logical Channel Prioritization, or LCP, is a procedure carried out at the MAC layer of 5GNR, used to determine the amount of data from each individual logical channel (LCH) which is then inserted into a given MAC PDU for uplink (UL) transmission. Transmission resources are limited, and LCP provides a balance between prioritizing high-priority data, and starving lower-priority data. LCP is currently (according to legacy, Rei-18 NR and earlier, systems) carried out in two rounds. 1st and 2nd Rounds of LCP are annotated below. TS 38.321 The MAC entity shall, when a new transmission is performed: 1> allocate resources to the logical channels as follows: 2> (1st round) logical channels selected in clause 5.4.3.1.2 for the UL grant with Bj>Q are allocated resources in a decreasing priority order. If the PBR of a logical channel is set to infinity, the MAC entity shall allocate resources for all the data that is available for transmission on the logical channel before meeting the PBR of the lower priority logical channel(s); 2> decrement Bj by the total size of MAC SDUs served to logical channel j above; 2> (2nd round) if any resources remain, all the logical channels selected in clause 5.4.3.1.2 are served in a strict decreasing priority order (regardless of the value of Bj} until either the data for that logical channel or the UL grant is exhausted, whichever comes first. Logical channels configured with equal priority should be served equally.

[0003] The ongoing Rei-19 NR work includes continuation of XR (extended Reality) work, which poses new challenges due to its combination of high bit rates and low latency. The stringent requirements of XR in terms of delay in particular, require enhancements to existing NR scheduling techniques including aforementioned LCP.

[0004] In the 3GPP RAN2#127 meeting (August 2024), RAN2 made the following agreements for scheduling enhancements pertaining to XR requirements: RAN2 to no longer consider the enhancement of the LCP restriction, as one of the candidate solutions for LCP enhancements in Rei-19 XR. FFS whether / how additional priority impacts intra-UE prioritization (can be discussed in stage-3)

[0005] Also, according to the revised Rei-19 XR Work Item Description (in 3 GPP tdoc RP-241771, “Revised WID on XR (extended Reality) for NR Phase 3”), and as highlighted below, RAN2 should specify the additional logical channel priority handling using delay / deadline information of packets: Specify Enhancements for support of UL scheduling to enable high XR capacity while meeting delay requirements / avoiding too late PDUs, as follows [RAN2]: - Specify additional Logical Channel priority handling using delay / deadline information of packets; - Specify enhanced DSR (Delay Status Report) reporting with multiple pairs of remaining time and buffer size for an LCG.

[0006] In subsequent meeting (the most recent RAN2 meeting, RAN2#127-bis meeting), RAN2 made the following agreements for LCP enhancements for Rei-19 XR: Agreements on LCP enhancements 1. As a baseline, additional LCH priority is applied for an LCH in both 1st and 2nd Rounds of resource allocation procedure in LCP, as long as the LCH has delay-critical data available for transmission when starting the 1st Round. 2. FFS if we can still change the priority for the 2nd round to ensure fairness, but we need to consider tight timeline of LCP procedure and UE complexity. Companies can also check whether we can leave this to UE implementation 3. Introduce an independent per-LCH remaining time threshold for applying delay-critical priority. 4. We do not introduce any setting restrictions of this new remaining time threshold with relation to DSR triggering threshold.

[0007] And additionally, on the topic of terminology, the following was agreed: • For now, we will use “LCH priority-adjusted data”

[0008] In summary, 3GPP RAN2 agreed to introduce a new (referred to as “additional”) priority for a LCH which contains delay-critical data (referred to as “LCH priority-adjusted data”, to avoid the confusion with the term “delay-critical data” which is already used in legacy NR when describing DSR, or Delay Status Report). A channel is deemed to contain LCH priority-adjusted data, if the remaining time before discard of any buffered PDCP SDU in that LCH (as defined by a timer configured for this PDCP SDU) goes below a LCH-specific configured threshold.

[0009] In legacy NR, LCH priority is used in 1) resource allocation in LCP (as mentioned above), 2) BSR triggering (in some cases, a BSR is triggered only if data of higher priority arrives than priority of data already in the buffer), 3) truncated BSR LCG selection (when we do not have space to send the entire BSR), and 4) intra-UE prioritization.

[0010] On the issue 4), and according to 3GPP TS 38.300vl8.3.0, “in case a configured uplink grant transmissions or a dynamically allocated uplink transmission overlaps in time with a scheduling request transmission, the UE prioritizes the transmission based on the comparison between the priority of the logical channel which triggered the scheduling request and the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDU associated with the overlapping resource”.

[0011] Therefore, in this legacy intra-UE prioritization, when more than one UL grant(s) and / or SR(s) overlap in time domain, a priority-based comparison among the overlapped UL grant(s) and / or SR(s) is conducted to determine which UL grant or SR should be transmitted. The priority-based comparison is based on legacy (default) LCH priority, i.e., the priority of UL grant is defined as the highest (legacy) priority of LCHs multiplexed in the corresponding MAC PDU, and the priority of SR is defined as the (legacy) priority of the LCH triggering the SR.

[0012] In RAN2#127 meeting, during the discussion on Rel-19 LCP enhancement, an FFS was added on whether / how the additional LCH priority (originally intended to be used for LCP enhancement) will affect the intra-UE prioritization, but was not further discussed in RAN2#127-bis. The expected operation regarding this issue, would be, in the priority-based comparison elaborated above, when defining the priority of UL grant, the additional LCH priority can be used (instead of legacy priority) for LCH(s) with LCH priority-adjusted data (similar to the case of LCP enhancement). Similarly, the priority of SR can be defined as the (legacy) priority of the LCH if without LCH priority-adjusted data or the additional priority of the LCH if with LCH priority-adjusted data, for the LCH triggering the SR.

[0013] For intra-UE prioritization, we can expect similar benefit to that of LCP enhancements (i.e., preventing LCH priority-adjusted data from being delayed by non- LCH priority-adjusted data), via the prioritization of the LCH priority-adjusted data, by making use of the additional LCH priority in determining the priority of an uplink grant, and / or that of LCH triggering an SR.

[0014] However, as the present disclosure shows, it is at present unclear whether a recalculation of the new (additional) priority is needed, what its technical benefits would be, and how it would apply. The present disclosure therefore covers the decision on which priority (baseline / legacy / priority used as default for non LCH priority adjusted data, or new / additional / adjusted) to use for the case of intra-UE prioritization, but extends the decision or re-calculation considerations to other cases as well.

[0015] For LCH priority-adjusted data, in-time delivery is important. However, most of the MAC CEs, e.g., BSR / DSR / PHR, etc., still have higher absolute priorities over any of XR data, and those MAC CEs can use any type of uplink grants. This could make unexpected interruption during LCP and MAC PDU generation, resulting in LCH priority-adjusted data being delayed due to such MAC CEs. Therefore, there may be advantages in data prioritization over some less important / urgent MAC CEs.

[0016] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the present invention. SUMMARY

[0017] It is an aim of certain examples of the present disclosure to address, solve and / or mitigate, at least partly, at least one of the problems and / or disadvantages associated with the related art, for example at least one of the problems and / or disadvantages described herein. It is an aim of certain examples of the present disclosure to provide at least one advantage over the related art, for example at least one of the advantages described herein.

[0018] The present invention is defined in the independent claims. Advantageous features are defined in the dependent claims.

[0019] Embodiments or examples disclosed in the description and / or figures falling outside the scope of the claims are to be understood as examples useful for understanding the present invention.

[0020] Other aspects, advantages, and salient features of the invention will become apparent to those skilled in the art from the following detailed description taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF DRAWINGS

[0021] FIG. 1 illustrates a method 100 in accordance with an embodiment of the present disclosure.

[0022] FIG. 2 illustrates a method 200 in accordance with an embodiment of the present disclosure.

[0023] FIG. 3 illustrates a method 300 in accordance with an embodiment of the present disclosure.

[0024] FIG. 4 illustrates an electronic device in accordance with an embodiment of the present disclosure. DETAILED DESCRIPTION

[0025] The following description of examples of the present disclosure, with reference to the accompanying drawings, is provided to assist in a comprehensive understanding of the present invention, as defined by the claims. The description includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the examples described herein can be made.

[0026] The same or similar components may be designated by the same or similar reference numerals, although they may be illustrated in different drawings.

[0027] Detailed descriptions of techniques, structures, constructions, functions or processes known in the art may be omitted for clarity and conciseness, and to avoid obscuring the subject matter of the present disclosure.

[0028] The terms and words used herein are not limited to the bibliographical or standard meanings, but, are merely used to enable a clear and consistent understanding of the examples disclosed herein.

[0029] Throughout the description and claims, the words “comprise”, “contain” and “include”, and variations thereof, for example “comprising”, “containing” and “including”, means “including but not limited to”, and is not intended to (and does not) exclude other features, elements, components, integers, steps, processes, functions, characteristics, and the like.

[0030] Throughout the description and claims, the singular form, for example “a”, “an” and “the”, encompasses the plural unless the context otherwise requires. For example, reference to “an object” includes reference to one or more of such objects.

[0031] Throughout the description and claims, language in the general form of “X for Y” (where Y is some action, process, function, activity or step and X is some means for carrying out that action, process, function, activity or step) encompasses means X adapted, configured or arranged specifically, but not necessarily exclusively, to do Y.

[0032] Features, elements, components, integers, steps, processes, functions, characteristics, and the like, described in conjunction with a particular aspect, embodiment, example or claim are to be understood to be applicable to any other aspect, embodiment, example or claim disclosed herein unless incompatible therewith.

[0033] The following examples are applicable to, and use terminology associated with, 3 GPP 5G. However, the skilled person will appreciate that the techniques disclosed herein are not limited to these examples or to 3GPP 5G, and may be applied in any suitable system or standard, for example one or more existing and / or future generation wireless communication systems or standards. The skilled person will appreciate that the techniques disclosed herein may be applied in any existing or future releases of 3GPP 5G NR or any other relevant standard.

[0034] For example, the functionality of the various network entities and other features disclosed herein may be applied to corresponding or equivalent entities or features in other communication systems or standards. Corresponding or equivalent entities or features may be regarded as entities or features that perform the same or similar role, function, operation or purpose within the network.

[0035] The skilled person will appreciate that certain examples of the present disclosure may not be directly related to standardization but rather proprietary implementation of some of the prioritization functions of NRRel-17 and beyond networks.

[0036] The skilled person will appreciate that the present invention is not limited to the specific examples disclosed herein. For example: • The techniques disclosed herein are not limited to 3GPP 5G. • One or more entities in the examples disclosed herein may be replaced with one or more alternative entities performing equivalent or corresponding functions, processes or operations. • One or more of the messages in the examples disclosed herein may be replaced with one or more alternative messages, signals or other type of information carriers that communicate equivalent or corresponding information. • One or more further elements, entities and / or messages may be added to the examples disclosed herein. • One or more non-essential elements, entities and / or messages may be omitted in certain examples. • The functions, processes or operations of a particular entity in one example may be divided between two or more separate entities in an alternative example. • The functions, processes or operations of two or more separate entities in one example may be performed by a single entity in an alternative example. • Information carried by a particular message in one example may be carried by two or more separate messages in an alternative example. • Information carried by two or more separate messages in one example may be carried by a single message in an alternative example. • The order in which operations are performed may be modified, if possible, in alternative examples. • The transmission of information between network entities is not limited to the specific form, type and / or order of messages described in relation to the examples disclosed herein.

[0037] Certain examples of the present disclosure may be provided in the form of an apparatus / device / network entity configured to perform one or more defined network functions and / or a method therefor. Such an apparatus / device / network entity may comprise one or more elements, for example one or more of receivers, transmitters, transceivers, processors, controllers, modules, units, and the like, each element configured to perform one or more corresponding processes, operations and / or method steps for implementing the techniques described herein. For example, an operation / function of X may be performed by a module configured to perform X (or an X-module). Certain examples of the present disclosure may be provided in the form of a system (e.g. a network) comprising one or more such apparatuses / devices / network entities, and / or a method therefor.

[0038] It will be appreciated that examples of the present disclosure may be realized in the form of hardware, software or a combination of hardware and software. Certain examples of the present disclosure may provide a computer program comprising instructions or code which, when executed, implement a method, system and / or apparatus in accordance with any aspect, claim, example and / or embodiment disclosed herein. Certain embodiments of the present disclosure provide a machine-readable storage storing such a program.

[0039] As mentioned above, 3GPP RAN2 agreed to introduce a new (referred to as “additional”) priority for a LCH which contains delay-critical data (referred to as “LCH priority-adjusted data”, to avoid the confusion with the term “delay-critical data” which is already used in legacy NR when describing DSR, or Delay Status Report). A channel is deemed to contain LCH priority-adjusted data, if the remaining time before discard of any buffered PDCP SDU in that LCH (as defined by a timer configured for this PDCP SDU) goes below a LCH-specific configured threshold. In the present disclosure, the term priority-adjusted data may be used interchangeably with delay-critical data to mean data (SDUs) in a LCH which has a time before discard timer (or equivalent) configured i.e. data that has ‘expiry’.

[0040] In the present disclosure, prioritizing one transmission over another may mean selecting one for transmission over the other, for sole transmission over the shared resource (at least part of which is allocated to both).

[0041] At least one of the following may be triggers for LCH priority to be revised / re-checked / re-calculated. In some examples, the LCH priority may be revised / re-checked / re-calculated for purposes of being used in a data prioritization procedure requiring relative priority of data such as intra-UE prioritization for the case of overlapping uplink resources or LCP: • Reconfiguration of existing LCHs • Addition of new LCHs • Regrouping of LCHs (regardless of whether new LCHs are configured or not) into the LCGs (logical channel groups) • MAC PDU assembly • MAC PDU transmission • B SR triggering • SR triggering • DSR triggering • Insertion of various MAC CEs into the MAC PDU

[0042] Each of the above triggers for LCH priority to be revised / re-checked / re-calculated will be described in more detail below.

[0043] Reconfiguration of existing LCHs

[0044] As triggered by reception by the UE of the relevant signaling from the network, e.g. reception of the LogicalChannelConfig Information Element

[0045] In some embodiments, re-calculation is claimed for all LCHs and not just LCHs affected by the reconfiguration

[0046] Addition of new LCHs

[0047] In some embodiments, re-calculation is claimed for all LCHs and not just the newly -added LCHs.

[0048] Regrouping of LCHs (regardless of whether new LCHs are configured or not) into the LCGs (logical channel groups)

[0049] Reception by the UE of the relevant signaling from the network, e.g. reception of the LogicalChannelConfig Information Element.

[0050] MAC PDU assembly

[0051] In prior art, LCH priority needs to be determined (whether it is legacy or additional priority) and used during MAC PDU assembly (i.e. during LCP procedure).

[0052] Rei-19 discussions covered both the case where this determination is done only at the start of the 1st round of LCP, and where it is done at the start of 1st and then again at the start or 2nd round or LCP.

[0053] However, following assembly, some or all of the delay-critical data may have been inserted into said MAC PDU and the present disclosure provides that a new priority may be applied henceforth, while based on prior art no new re-calculation is expected until another LCP needs to be carried out.

[0054] This becomes especially important if there is another procedure involving the LCH(s) whose data went into this MAC PDU (such as assembly of another MAC PDU involving some or all said LCH(s), or intra-UE prioritization of overlapping resources where priority of data is linked to said LCH(s), or the triggering of BSR or SR whose priorities become linked to priorities of said LCH(s) if they triggered said BSR or SR), before the assembly of another MAC PDU.

[0055] When another MAC PDU is assembled, as mentioned LCP priorities will in any case be re-calculated.

[0056] In another embodiment, LCH priority is recalculated prior to MAC PDU assembly and is used in the assembly i.e. may differ from LCH priority used in 2nd round of LCP used to assemble said MAC PDU. In another embodiment, LCH priority is recalculated after the MAC PDU assembly and may be used in procedures such as intra-UE prioritization.

[0057] MAC PDU transmission

[0058] Time may lapse between MAC PDU assembly and transmission.

[0059] When MAC PDU transmission time comes, prioritization may need to be done between different grants overlapping in time, and / or an UL grant and an SR (Scheduling request).

[0060] Therefore priority of the LCH may need to be re-calculated.

[0061] This is especially relevant for determining relative priority of SR, as the LCH which triggered BSR (whose inability to be sent then triggered the SR in question) may no longer contain any delay-critical data.

[0062] Some SRs are not linked by a BSR or a specific LCH and therefore do not have a clear priority defined.

[0063] This problem exists in prior art and so e.g. a variation of Example 5 below whereby (in said variation, not shown in Example 5) uplink grant is prioritized over SR does not apply only to uplink grants containing XR data, or any enhancements related to criticality of data.

[0064] BSR triggering

[0065] Once BSR is triggered and / or following BSR MAC CE assembly, LCH priority is revised for LCH(s) which triggered BSR.

[0066] In an alternative embodiment, once BSR is triggered and / or following BSR MAC CE assembly, LCH priority is revised for all LCH(s) and not just those which triggered BSR.

[0067] SR triggering

[0068] For SRs linked to a specific LCH (such as SRs triggered by a UE’s inability to send a BSR, or SRs triggered at the IAB-MT by the arrival at the collocated IAB-DU of a BSR or SR from a child node), SR priority (as e.g. used in intra-UE prioritization) is re-calculated at the point it needs to be used (e.g. during intra-UE prioritization, following intra-UE prioritization)

[0069] DSR triggering

[0070] When a DSR is triggered (which is also linked to delay-critical data, but defined per LCH or LCG and potentially using a different PDCP timer), re-calculation of LCH priority-adjusted data related priority is triggered.

[0071] When a DSR is sent (which is also linked to delay-critical data, but defined per LCH or LCG and potentially using a different PDCP timer), re-calculation of LCH priority-adjusted data related priority is triggered.

[0072] When DSR-related thresholds and / or timers are reconfigured, re-calculation of LCH priority-adjusted data related priority is triggered.

[0073] Insertion of various MAC CEs into the MAC PDU

[0074] Currently there is a fixed prioritization between MAC CEs and data when a MAC PDU is assembled, for instance MAC CE for Delay Status Report, and MAC CE for Buffer Status Report (except padding), are given higher priority than actual uplink data during MAC PDU assembly.

[0075] Additionally, currently MAC CEs are ordered in a priority order, and prioritization among MAC CEs of same priority is up to UE implementation.

[0076] In an embodiment of the present disclosure, a variable priority of a BSR MAC CE (or other MAC CEs linked to a specific LCH or LCG) is used, whereby it only has higher priority than uplink data, if data in the BSR MAC CE contains delay-critical data.

[0077] In any of the above embodiments of the present disclosure, re-calculation may be done based on checking of whether any SDUs with delay-critical data remain the LCH (e.g. data validity is below or at the remaining time threshold). Or, it may be done by subtracting the data from said LCH that was inserted in the MAC PDU. The latter is less accurate but also less taxing on computational resources of a UE.

[0078] In an embodiment of the present disclosure, the priority of the logical channels (that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDUs associated with the overlapping resources), is based on the priority of the 1st round of the LCP used to build said MAC PDU. In another embodiment, the priority of LCHs is based on priority of 2nd round of the LCP used to build said MAC PDU. In another embodiment, the priority is re-calculated based on whether there is any LCH priority-adjusted data in LCHs at time MAC PDU is about to be transmitted.

[0079] FIG. 1 is a flowchart illustrating an example method of the present disclosure. In block 102, a UE determines whether a transmission overlaps in time with another transmission. In block 104, the UE determines whether any of the logical channels associated with the transmissions contains priority-adjusted data to be transmitted in the overlapping time. In block 106, the UE determines, in the case that any of the logical channels associated with the transmissions contains priority-adjusted data to be transmitted in the overlapping time, whether the remaining time before discard of any buffered data in the logical channel is below a configured threshold for the logical channel. In block 108, the UE prioritizes one of the transmissions based on a comparison of priorities of logical channels associated with the transmissions by using, in the case that the remaining time before discard of any buffered data in the logical channel is below the configured threshold for the logical channel, the adjusted priority for the comparison.

[0080] In some embodiments, determining whether any of the logical channels associated with the transmissions contains priority-adjusted data comprises determining whether any of the logical channels containing priority-adjusted data to be transmitted in the overlapping time are multiplexed in MAC PDUs associated with overlapping time resources, or can be multiplexed in MAC PDUs associated with the overlapping time resources.

[0081] In some embodiments, the adjusted priority for the comparison is only used if the logical channels containing priority-adjusted data to be transmitted in the overlapping time are multiplexed in MAC PDUs associated with overlapping time resources.

[0082] In some of embodiments, one of the overlapping transmissions is a configured uplink grant transmission, and another one of the overlapping transmissions is a dynamically allocated uplink transmission in the same serving cell or another configured uplink grant transmission in the same serving cell.

[0083] In some embodiments, one of the overlapping transmissions is a scheduling request transmission, and another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission.

[0084] FIG. 2 is a flowchart illustrating an example method of the present disclosure. In block 202, a UE determines whether a transmission overlaps in time with another transmission. In block 204, the UE prioritizes, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of priorities of logical channels associated with the transmissions. In this example, one of the overlapping transmissions is a scheduling request transmission, and another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission.

[0085] In some embodiments, in the case that the scheduling request transmission is triggered according to a buffer status report procedure, the priority of the logical channel which triggered the scheduling request is the priority of the logical channel at the time of triggering the buffer status report that triggered the scheduling request.

[0086] In some embodiments, in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission in the case that any of the logical channels contain priority-adjusted data to be transmitted in the overlapping time and are multiplexed in MAC PDUs associated with overlapping time resources and the remaining time before discard of any buffered data in those logical channels is below the configured threshold for that logical channel.

[0087] In some embodiments, in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission.

[0088] In some embodiments, an adjusted priority of the logical channel which triggered the scheduling request is used for the comparison in the case that the logical channel contains priority-adjusted data at the time of intra-UE prioritization.

[0089] FIG. 3 is a flowchart illustrating an example method for intra-UE prioritization at a UE. In block 302, the method comprises determining whether a transmission overlaps in time with another transmission. In block 304 the method comprises prioritizing, in the case that the transmission overlaps in time with another transmission, one of the transmissions based on a comparison of logical channel prioritization (LCP) priorities of logical channels associated with the transmissions.

[0090] Prioritizing one of the transmissions based on a comparison of LCP priorities may comprise determining whether any of the logical channels associated with the transmissions contain logical channel (LCH) priority-adjusted data to be transmitted in the overlapping time. In the case that any of the logical channels associated with the transmissions contain LCH priority-adjusted data to be transmitted in the overlapping time, the method may further comprise determining whether the remaining time before discard of any buffered data in each logical channel containing LCH priority-adjusted data is below a configured threshold for the logical channel; and prioritizing one of the transmissions based on a comparison of LCP priorities by using, in the case that the remaining time before discard of any buffered data in a logical channel containing LCH priority-adjusted data is below the configured threshold for the logical channel, an additional LCP priority for the logical channel for the comparison.

[0091] One of the transmissions may include an uplink grant transmission or a scheduling request transmission, and the other transmission may include an uplink grant transmission.

[0092] FIG. 4 is a block diagram of an exemplary electronic device (e.g. UE) that may be used in examples of the present disclosure. The skilled person will appreciate that the electronic device illustrated in FIG. 4 may be implemented, for example, as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualised function instantiated on an appropriate platform, e.g. on a cloud infrastructure.

[0093] The electronic device comprises a processor 401 (or controller), a transmitter 403 and a receiver 405. The receiver 405 is configured for receiving one or more messages from one or more other network entities. The transmitter 403 is configured for transmitting one or more messages to one or more other network entities. The processor 401 is configured for performing operations as described above.

[0094] By way of further explanation, examples of how the existing 3 GPP standards might be modified in view of certain aspects of the present disclosure are provided. The modifications are shown below using underlined text.

[0095] It will be understood that, while shown separately, the examples below may be combined. That is, an embodiment of the present disclosure may be based on at least one of examples 1 to 8 below, alone or in combination.

[0096] Example 1: Priorities of LCHs which are actually multiplexed in the MAC PDUs or may be multiplexed are both re-calculated. ------------------------- 38.300 V18.3.0------------------------- 10.3 Uplink Scheduling If the UE is configured with enhanced intra-UE overlapping resources prioritization, in case a configured uplink grant transmission overlaps in time with dynamically allocated uplink transmission or with another configured uplink grant transmission in the same serving cell, the UE prioritizes the transmission based on the comparison between the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDUs associated with the overlapping resources. If any of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDUs associated with the overlapping resources contain priority-adjusted data, and remaining time before discard of any buffered PDCP SDU in these logical channels (as defined by a timer configured for this PDCP SDU) is below the configured threshold for the specific logical channel, the adjusted priority of these logical channels is used for this comparison; otherwise the baseline priority is used. Similarly, in case a configured uplink grant transmissions or a dynamically allocated uplink transmission overlaps in time with a scheduling request transmission, the UE prioritizes the transmission based on the comparison between the priority of the logical channel which triggered the scheduling request and the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDU associated with the overlapping resource. If any of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDUs associated with the overlapping resources contain priority-adjusted data, and remaining time before discard of any buffered PDCP SDU in these logical channels (as defined by a timer configured for this PDCP SDU) is below the configured threshold for the specific logical channel, the adjusted priority of these logical channels is used for this comparison; otherwise the baseline priority is used. In case the MAC PDU associated with a deprioritized transmission has already been generated, the UE keeps it stored to allow the gNB to schedule a retransmission. The UE may also be configured by the gNB to transmit the stored MAC PDU as a new transmission using a subsequent resource of the same configured uplink grant configuration when an explicit retransmission grant is not provided by the gNB. ------------------------- 38.300 V18.3.0-------------------------

[0097] Example 2: Only priority of LCHs which are actually multiplexed in the MAC PDUs are re-calculated. ------------------------- 38. 300 V18.3.0------------------------- 10.3 Uplink Scheduling If the UE is configured with enhanced intra-UE overlapping resources prioritization, in case a configured uplink grant transmission overlaps in time with dynamically allocated uplink transmission or with another configured uplink grant transmission in the same serving cell, the UE prioritizes the transmission based on the comparison between the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDUs associated with the overlapping resources. If any of the logical channels that have data to be transmitted and which are multiplexed in MAC PDUs associated with the overlapping resources contain priority-adjusted data, and remaining time before discard of any buffered PDCP SDU in these logical channels (as defined by a timer configured for this PDCP SDU) is below the configured threshold for the specific logical channel, the adjusted priority of these logical channels is used for this comparison; otherwise the baseline priority is used. Similarly, in case a configured uplink grant transmissions or a dynamically allocated uplink transmission overlaps in time with a scheduling request transmission, the UE prioritizes the transmission based on the comparison between the priority of the logical channel which triggered the scheduling request and the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDU associated with the overlapping resource. If any of the logical channels that have data to be transmitted and which are multiplexed in MAC PDUs associated with the overlapping resources contain priority-adjusted data, and remaining time before discard of any buffered PDCP SDU in these logical channels (as defined by a timer configured for this PDCP SDU) is below the configured threshold for the specific logical channel, the adjusted priority of these logical channels is used for this comparison; otherwise the baseline priority is used. In case the MAC PDU associated with a deprioritized transmission has already been generated, the UE keeps it stored to allow the gNB to schedule a retransmission. The UE may also be configured by the gNB to transmit the stored MAC PDU as a new transmission using a subsequent resource of the same configured uplink grant configuration when an explicit retransmission grant is not provided by the gNB. ------------------------- 38. 300 V18.3.0-------------------------

[0098] Example 3: for intra-UE prioritization involving a clash between sending an SR and an UL grant, for an SR triggered according to the BSR procedure, the priority of the logical channel which triggered the scheduling request is the priority at the time of triggering of the BSR which resulted in triggering of said SR ------------------------- 38. 300 V18.3.0------------------------- 10.3 Uplink Scheduling If the UE is configured with enhanced intra-UE overlapping resources prioritization, in case a configured uplink grant transmission overlaps in time with dynamically allocated uplink transmission or with another configured uplink grant transmission in the same serving cell, the UE prioritizes the transmission based on the comparison between the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDUs associated with the overlapping resources. Similarly, in case a configured uplink grant transmissions or a dynamically allocated uplink transmission overlaps in time with a scheduling request transmission, the UE prioritizes the transmission based on the comparison between the priority of the logical channel which triggered the scheduling request and the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDU associated with the overlapping resource. For a scheduling request triggered according to the BSR procedure, the priority of the logical channel which triggered the scheduling request is the priority at the time of triggering of the BSR which resulted in triggering of the SR. In case the MAC PDU associated with a deprioritized transmission has already been generated, the UE keeps it stored to allow the gNB to schedule a retransmission. The UE may also be configured by the gNB to transmit the stored MAC PDU as a new transmission using a subsequent resource of the same configured uplink grant configuration when an explicit retransmission grant is not provided by the gNB. ------------------------- 38. 300 V18.3.0-------------------------

[0099] Example 4: for intra-UE prioritization involving a clash between sending an SR and an UL grant, priority of SR is re-calculated at time of intra-UE procedure ------------------------- 38. 300 V18.3.0------------------------- 10.3 Uplink Scheduling If the UE is configured with enhanced intra-UE overlapping resources prioritization, in case a configured uplink grant transmission overlaps in time with dynamically allocated uplink transmission or with another configured uplink grant transmission in the same serving cell, the UE prioritizes the transmission based on the comparison between the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDUs associated with the overlapping resources. Similarly, in case a configured uplink grant transmissions or a dynamically allocated uplink transmission overlaps in time with a scheduling request transmission, the UE prioritizes the transmission based on the comparison between the priority of the logical channel which triggered the scheduling request and the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDU associated with the overlapping resource. If the logical channel which triggered the scheduling request contains priority-adjusted data at the time of intra-UE prioritization, and remaining time before discard of any buffered PDCP SDU in this logical channel (as defined by a timer configured for this PDCP SDU) is below the configured threshold for the specific logical channel, the adjusted priority of this logical channel is used for this comparison; otherwise the baseline priority is used. In case the MAC PDU associated with a deprioritized transmission has already been generated, the UE keeps it stored to allow the gNB to schedule a retransmission. The UE may also be configured by the gNB to transmit the stored MAC PDU as a new transmission using a subsequent resource of the same configured uplink grant configuration when an explicit retransmission grant is not provided by the gNB. ------------------------- 38. 300 V18.3.0-------------------------

[0100] Example 5: covers the case of SR not linked to a BSR and claims prioritization of UL data over SR if UL data contains delay critical (LCH priority-adjusted data). ------------------------- 38. 300 V18.3.0------------------------- 10.3 Uplink Scheduling If the UE is configured with enhanced intra-UE overlapping resources prioritization, in case a configured uplink grant transmission overlaps in time with dynamically allocated uplink transmission or with another configured uplink grant transmission in the same serving cell, the UE prioritizes the transmission based on the comparison between the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDUs associated with the overlapping resources. Similarly, in case a configured uplink grant transmissions or a dynamically allocated uplink transmission overlaps in time with a scheduling request transmission, the UE prioritizes the transmission based on the comparison between the priority of the logical channel which triggered the scheduling request and the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDU associated with the overlapping resource. If the SR is not triggered according to the BSR procedure or pre-emptive BSR procedure, the uplink transmission is prioritized over SR transmission if any of the logical channels that have data to be transmitted and which are multiplexed in MAC PDUs associated with the overlapping resources contain priority-adjusted data, and remaining time before discard of any buffered PDCP SDU in logical channels (as defined by a timer configured for this PDCP SDU) is below the configured threshold for the specific logical channel. In case the MAC PDU associated with a deprioritized transmission has already been generated, the UE keeps it stored to allow the gNB to schedule a retransmission. The UE may also be configured by the gNB to transmit the stored MAC PDU as a new transmission using a subsequent resource of the same configured uplink grant configuration when an explicit retransmission grant is not provided by the gNB. ------------------------- 38. 300 V18.3.0-------------------------

[0101] Example 6: covers the case of SR not linked to a BSR or DSR and claims prioritization of UL data over SR. In some embodiments of the present disclosure, a refinement of this example is provided where SR is not linked to a subset of {BSR, pre-emptive BSR, DSR}. ------------------------- 38. 300 V18.3.0------------------------- 10.3 Uplink Scheduling If the UE is configured with enhanced intra-UE overlapping resources prioritization, in case a configured uplink grant transmission overlaps in time with dynamically allocated uplink transmission or with another configured uplink grant transmission in the same serving cell, the UE prioritizes the transmission based on the comparison between the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDUs associated with the overlapping resources. Similarly, in case a configured uplink grant transmissions or a dynamically allocated uplink transmission overlaps in time with a scheduling request transmission, the UE prioritizes the transmission based on the comparison between the priority of the logical channel which triggered the scheduling request and the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDU associated with the overlapping resource. If the SR is not triggered according to the BSR procedure or pre-emptive BSR procedure or DSR procedure, the uplink transmission is prioritized over SR transmission. In case the MAC PDU associated with a deprioritized transmission has already been generated, the UE keeps it stored to allow the gNB to schedule a retransmission. The UE may also be configured by the gNB to transmit the stored MAC PDU as a new transmission using a subsequent resource of the same configured uplink grant configuration when an explicit retransmission grant is not provided by the gNB. ------------------------- 38. 300 V18.3.0-------------------------

[0102] Example 7: covers the case of SR not linked to a priority of a LCH. ------------------------- 38. 300 V18.3.0------------------------- 10.3 Uplink Scheduling If the UE is configured with enhanced intra-UE overlapping resources prioritization, in case a configured uplink grant transmission overlaps in time with dynamically allocated uplink transmission or with another configured uplink grant transmission in the same serving cell, the UE prioritizes the transmission based on the comparison between the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDUs associated with the overlapping resources. Similarly, in case a configured uplink grant transmissions or a dynamically allocated uplink transmission overlaps in time with a scheduling request transmission, the UE prioritizes the transmission based on the comparison between the priority of the logical channel which triggered the scheduling request and the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDU associated with the overlapping resource. If the SR is not associated with a logical channel or its priority, prioritization between the uplink transmission and the SR is left to implementation. In case the MAC PDU associated with a deprioritized transmission has already been generated, the UE keeps it stored to allow the gNB to schedule a retransmission. The UE may also be configured by the gNB to transmit the stored MAC PDU as a new transmission using a subsequent resource of the same configured uplink grant configuration when an explicit retransmission grant is not provided by the gNB.

[0103] Example 8: covers the case of SR not linked to a BSR and provides prioritization of SR over UL data. If SR is linked to a crucial action (such as actions related to maintaining or restoring the radio link or radio beam) such as beam failure recovery, it may need to be prioritized over data. In this case, SR has no priority linked to a specific LCH (like it has when SR is linked to BSR / DSR), and so, in some examples, a relative priority between SR and uplink grant may be provided, based on what triggered the SR (beam failure recovery, positioning measurement gap activation / deactivation request, consistent LBT failure recovery, Timing Advance reporting). This relative priority could be hard coded in specifications, or configurable by the network, or a combination of both (a baseline value assumed based on specifications, and then changes signaled by the network when needed). A further optimization may be to consider the cause which triggered the SR (beam failure recovery, positioning measurement gap activation / deactivation request, consistent LBT failure recovery, Timing Advance reporting, etc.), but also look at priority of uplink data (for example, using some of the recalculation techniques described above), and then decide which one to transmit based on a decision rule which takes both into account (e.g. prioritize SR triggered by positioning measurement gap activation / deactivation request over XR or URLLC data, but not other data). That is, in some examples, priority may be provided for SR even in cases where such priority does not exist in prior art as SR is not linked to BSR / DSR i.e. not linked to a specific LCH. ------------------------- 38. 300 V18.3.0------------------------- 10.3 Uplink Scheduling If the UE is configured with enhanced intra-UE overlapping resources prioritization, in case a configured uplink grant transmission overlaps in time with dynamically allocated uplink transmission or with another configured uplink grant transmission in the same serving cell, the UE prioritizes the transmission based on the comparison between the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDUs associated with the overlapping resources. Similarly, in case a configured uplink grant transmissions or a dynamically allocated uplink transmission overlaps in time with a scheduling request transmission, the UE prioritizes the transmission based on the comparison between the priority of the logical channel which triggered the scheduling request and the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDU associated with the overlapping resource. If this SR was triggered by beam failure recovery, the SR transmission is prioritized over uplink transmission. In case the MAC PDU associated with a deprioritized transmission has already been generated, the UE keeps it stored to allow the gNB to schedule a retransmission. The UE may also be configured by the gNB to transmit the stored MAC PDU as a new transmission using a subsequent resource of the same configured uplink grant configuration when an explicit retransmission grant is not provided by the gNB. ------------------------- 38. 300 V18.3.0-------------------------

[0104] While the invention has been shown and described with reference to certain examples, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the scope of the invention, as defined by the appended claims.

[0105] Certain examples of the present disclosure provide one or more techniques as disclosed in the following examples. The skilled person will appreciate that any of these techniques may be applied in combination with any of the techniques described above and illustrated in the Figures.

[0106] In a first example, there is provided a method of a user equipment (UE), the method comprising: determining whether a transmission overlaps in time with another transmission; prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of priorities of logical channels associated with the transmissions; wherein prioritizing one of the transmissions based on a comparison of priorities of logical channels associated with the transmissions comprises: determining whether any of the logical channels associated with the transmissions contains priority-adjusted data to be transmitted in the overlapping time; determining, in the case that any of the logical channels associated with the transmissions contains priority-adjusted data to be transmitted in the overlapping time, whether the remaining time before discard of any buffered data in the logical channel is below a configured threshold for the logical channel; and prioritizing one of the transmissions based on a comparison of priorities of logical channels associated with the transmissions by using, in the case that the remaining time before discard of any buffered data in the logical channel is below the configured threshold for the logical channel, the adjusted priority for the comparison.

[0107] In a second example, there is provided the method of the first example, wherein determining whether any of the logical channels associated with the transmissions contains priority-adjusted data comprises determining whether any of the logical channels containing priority-adjusted data to be transmitted in the overlapping time are at least one of: multiplexed in Medium Access Control (MAC) protocol data units (PDUs) associated with overlapping time resources; or can be multiplexed in MAC PDUs associated with the overlapping time resources.

[0108] In a third example, there is provided the method of the first or second example, wherein the adjusted priority for the comparison is only used if the logical channels containing priority-adjusted data to be transmitted in the overlapping time are multiplexed in MAC PDUs associated with overlapping time resources.

[0109] In a fourth example, there is provided the method of any one of the first to third examples, wherein one of the overlapping transmissions is a configured uplink grant transmission, and wherein another one of the overlapping transmissions is a dynamically allocated uplink transmission in the same serving cell or another configured uplink grant transmission in the same serving cell.

[0110] In a fifth example, there is provided the method of any one of the first to fourth examples, wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission in the same serving cell.

[0111] In a sixth example, there is provided the method of the fifth example, wherein in the case that the scheduling request transmission is triggered according to a buffer status report procedure, the priority of the logical channel which triggered the scheduling request is the priority of the logical channel at the time of triggering the buffer status report that triggered the scheduling request.

[0112] In a seventh example, there is provided the method of the fifth or sixth example, wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission in the case that any of the logical channels containing priority- adjusted data to be transmitted in the overlapping time are multiplexed in MAC PDUs associated with overlapping time resources.

[0113] In an eighth example, there is provided the method of of the fifth or sixth example, wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission.

[0114] In a ninth example, there is provided the method of of the fifth example, wherein the adjusted priority of the logical channel which triggered the scheduling request is used for the comparison in the case that the logical channel contains the priority-adjusted data at the time of intra-UE prioritization.

[0115] In a tenth example, there is provided the method of any one of the fifth to ninth examples, wherein in the case that the scheduling request does not have a priority associated with a logical channel, a priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

[0116] In an eleventh example, there is provided the method of the tenth example, wherein the trigger for the scheduling request is at least one of beam failure recovery, positioning measurement gap activation / deactivation request, consistent LBT failure recovery, or timing advance reporting.

[0117] In a twelfth example, there is provided a method of a user equipment (UE), the method comprising: determining whether a transmission overlaps in time with another transmission; prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of priorities of logical channels associated with the transmissions; wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission; and wherein in the case that the scheduling request transmission is triggered according to a buffer status report procedure, the priority of the logical channel which triggered the scheduling request is the priority of the logical channel at the time of triggering the buffer status report that triggered the scheduling request.

[0118] In a thirteenth example, there is provided the method of the twelfth example, wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission in the case that any of the logical channels contain priority-adjusted data to be transmitted in the overlapping time and are multiplexed in Medium Access Control (MAC) protocol data units (PDUs) associated with overlapping time resources and the remaining time before discard of any buffered data in those logical channels is below the configured threshold for that logical channel.

[0119] In a fourteenth example, there is provided the method of the twelfth example, wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission.

[0120] In a fifteenth example, there is provided the method of the thirteenth or fourteenth example, wherein an adjusted priority of the logical channel which triggered the scheduling request is used for the comparison in the case that the logical channel contains priority-adjusted data at the time of intra-UE prioritization.

[0121] In a sixteenth example, there is provided the method of any one of the twelfth to fifteenth examples, wherein in the case that the scheduling request does not have a priority associated with a logical channel, a priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

[0122] In a seventeenth example, there is provided the method of the sixteenth example, wherein the trigger for the scheduling request is at least one of beam failure recovery, positioning measurement gap activation / deactivation request, consistent LBT failure recovery, or timing advance reporting.

[0123] In an eighteenth example, there is provided a method of a user equipment (UE), the method comprising: determining whether a transmission overlaps in time with another transmission; prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of priorities of logical channels associated with the transmissions; wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission; wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission in the case that any of the logical channels contain priority-adjusted data to be transmitted in the overlapping time and are multiplexed in Medium Access Control (MAC) protocol data units (PDUs) associated with overlapping time resources and the remaining time before discard of any buffered data in those logical channels is below the configured threshold for that logical channel.

[0124] In a nineteenth example, there is provided a method of a user equipment (UE), the method comprising: determining whether a transmission overlaps in time with another transmission; prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of priorities of logical channels associated with the transmissions; wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission; wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission.

[0125] In a twentieth example, there is provided the method of the eighteenth or nineteenth example, wherein an adjusted priority of the logical channel which triggered the scheduling request is used for the comparison in the case that the logical channel contains priority-adjusted data at the time of intra-UE prioritization.

[0126] In a twenty-first example, there is provided the method of any of of the eighteenth to twentieth examples, wherein in the case that the scheduling request does not have a priority associated with a logical channel, a priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

[0127] In a twenty-second example, there is provided the method of the twenty-first example, wherein the trigger for the scheduling request is at least one of beam failure recovery, positioning measurement gap activation / deactivation request, consistent LBT failure recovery, or timing advance reporting.

[0128] In a twenty-third example, there is provided method of a user equipment (UE), the method comprising: determining whether a transmission overlaps in time with another transmission; prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of priorities of logical channels associated with the transmissions; wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission; wherein an adjusted priority of the logical channel which triggered the scheduling request is used for the comparison in the case that the logical channel contains priority-adjusted data at the time of intra-UE prioritization.

[0129] In a twenty-fourth example, there is provided the method of the twenty-third example, wherein in the case that the scheduling request does not have a priority associated with a logical channel, a priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

[0130] In a twenty-fifth example, there is provided the method of the twenty-fourth example, wherein the trigger for the scheduling request is at least one of beam failure recovery, positioning measurement gap activation / deactivation request, consistent LBT failure recovery, or timing advance reporting.

[0131] In a twenty-sixth example, there is provided a method of a user equipment (UE), the method comprising: determining whether a transmission overlaps in time with another transmission; prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of priorities of logical channels associated with the transmissions; wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission; and wherein in the case that the scheduling request does not have a priority associated with a logical channel, a priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

[0132] In a twenty-seventh example, there is provided the method of the twenty-sixth example, wherein the trigger for the scheduling request is at least one of beam failure recovery, positioning measurement gap activation / deactivation request, consistent LBT failure recovery, or timing advance reporting.

[0133] In a twenty-eighth example, there is provided a method of a user equipment, the method comprising: recalculating a priority of a logical channel (LCH), wherein the recalculation is triggered by at least one of: reconfiguration of existing LCHs, addition of new LCHs, regrouping of LCHs into logical channel groups (LCGs), Medium Access Control (MAC) protocol data units (PDU) assembly, MAC PDU transmission, buffer status report (BSR) triggering, scheduling request (SR) triggering, delay status report (DSR) triggering, or insertion of MAC control elements (CEs) into the MAC PDU.

[0134] In a twenty-ninth example, there is provided the method of the twenty-eighth example, further comprising the method of any one of the first to twenty-seventh examples.

[0135] In a thirtieth example, there is provided a user equipment (UE) configured to operate according to a method of any one of the first to twenty-ninth examples.

[0136] In a thirty-first example, there is provided a computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out a method according any one of the first to twenty-ninth examples.

[0137] In a thirty-second example, there is provided a computer or processor-readable data carrier having stored thereon a computer program according to the thirty-first example.

[0138] In a thirty-third example, there is provided a method for intra-UE prioritization at a user equipment (UE), the method comprising: determining whether a transmission overlaps in time with another transmission; prioritizing, in the case that the transmission overlaps in time with another transmission, one of the transmissions based on a comparison of logical channel prioritization (LCP) priorities of logical channels associated with the transmissions; wherein prioritizing one of the transmissions based on a comparison of LCP priorities comprises: determining whether any of the logical channels associated with the transmissions contain logical channel (LCH) priority-adjusted data to be transmitted in the overlapping time; determining, in the case that any of the logical channels associated with the transmissions contain LCH priority-adjusted data to be transmitted in the overlapping time, whether the remaining time before discard of any buffered data in each logical channel containing LCH priority-adjusted data is below a configured threshold for the logical channel; and prioritizing one of the transmissions based on a comparison of LCP priorities by using, in the case that the remaining time before discard of any buffered data in a logical channel containing LCH priority-adjusted data is below the configured threshold for the logical channel, an additional LCP priority for the logical channel for the comparison, wherein one of the transmissions includes an uplink grant transmission or a scheduling request transmission, and wherein the other transmission includes an uplink grant transmission.

[0139] In a thirty-fourth example, there is provided the method of the thirty-third example, wherein determining whether any of the logical channels associated with the transmissions contains LCH priority-adjusted data comprises determining whether any of the logical channels containing LCH priority-adjusted data to be transmitted in the overlapping time are at least one of: multiplexed in Medium Access Control (MAC) protocol data units (PDUs) associated with overlapping time resources; or can be multiplexed in MAC PDUs associated with the overlapping time resources.

[0140] In a thirty-fifth example, there is provided the method of the thirty-fourth example, wherein the additional LCP priority for the comparison is only used if the logical channels containing LCH priority-adjusted data to be transmitted in the overlapping time are multiplexed in MAC PDUs associated with overlapping time resources.

[0141] In a thirty-sixth example, there is provided the method of any one of the thirty-third to thirty-fifth examples, wherein one of the overlapping transmissions is a configured uplink grant transmission, and wherein another one of the overlapping transmissions is a dynamically allocated uplink transmission in the same serving cell or another configured uplink grant transmission in the same serving cell.

[0142] In a thirty-seventh example, there is provided the method of any one of the thirty-third to thirty-fifth examples, wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission in the same serving cell.

[0143] In a thirty-eighth example, there is provided the method of the thirty-seventh example, wherein in the case that the scheduling request transmission is triggered according to a buffer status report procedure, the LCP priority of the logical channel which triggered the scheduling request is the LCP priority of the logical channel at the time of triggering the buffer status report that triggered the scheduling request.

[0144] In a thirty-ninth example, there is provided the method of the thirty-seventh or thirtyeighth examples, wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission in the case that any of the logical channels containing LCH priority-adjusted data to be transmitted in the overlapping time are multiplexed in MAC PDUs associated with overlapping time resources.

[0145] In a fortieth example, there is provided the method of the thirty-seventh or thirtyeighth examples, wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission.

[0146] In a forty-first example, there is provided the method of the thirty-seventh example, wherein the additional priority of the logical channel which triggered the scheduling request is used for the comparison in the case that the logical channel contains the LCH priority-adjusted data at the time of intra-UE prioritization.

[0147] In a forty-second example, there is provided the method of any one of the thirtyseventh to forty-first examples, wherein in the case that the scheduling request does not have a LCP priority associated with a logical channel, a LCP priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

[0148] In a forty-third example, there is provided the method of the forty-second example, wherein the trigger for the scheduling request is at least one of beam failure recovery, positioning measurement gap activation / deactivation request, consistent LBT failure recovery, or timing advance reporting.

[0149] In a forty-fourth example, there is provided a method for intra-UE prioritization at a user equipment (UE), the method comprising: determining whether a transmission overlaps in time with another transmission; prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of logical channel prioritization (LCP) priorities of logical channels associated with the transmissions; wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission; and wherein in the case that the scheduling request transmission is triggered according to a buffer status report procedure, the LCP priority of the logical channel which triggered the scheduling request is the LCP priority of the logical channel at the time of triggering the buffer status report that triggered the scheduling request.

[0150] In a forty-fifth example, there is provided the method of the forty-fourth example, wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission in the case that any of the logical channels contain logical channel (LCH) priority-adjusted data to be transmitted in the overlapping time and are multiplexed in Medium Access Control (MAC) protocol data units (PDUs) associated with overlapping time resources and the remaining time before discard of any buffered data in those logical channels is below the configured threshold for that logical channel.

[0151] In a forty-sixth example, there is provided the method of the forty-fourth example, wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission.

[0152] In a forty-seventh example, there is provided the method of the forty-fifth or fortysixth example, wherein an additional LCP priority of the logical channel which triggered the scheduling request is used for the comparison in the case that the logical channel contains LCH priority-adjusted data at the time of intra-UE prioritization.

[0153] In a forty-eighth example, there is provided the method of any one of the forty-fourth to forty-seventh examples, wherein in the case that the scheduling request does not have a LCP priority associated with a logical channel, a priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

[0154] In a forty-ninth example, there is provided the method of the forty-eighth example, wherein the trigger for the scheduling request is at least one of beam failure recovery, positioning measurement gap activation / deactivation request, consistent LBT failure recovery, or timing advance reporting.

[0155] In a fiftieth example, there is provided a method for intra-UE prioritization at a user equipment (UE), the method comprising: determining whether a transmission overlaps in time with another transmission; prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of logical channel prioritization (LCP) priorities of logical channels associated with the transmissions; wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission; wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission in the case that any of the logical channels contain logical channel (LCH) priority-adjusted data to be transmitted in the overlapping time and are multiplexed in Medium Access Control (MAC) protocol data units (PDUs) associated with overlapping time resources and the remaining time before discard of any buffered data in those logical channels is below the configured threshold for that logical channel.

[0156] In a fifty-first example, there is a method for intra-UE prioritization at a user equipment (UE), the method comprising: determining whether a transmission overlaps in time with another transmission; prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of logical channel prioritization (LCP) priorities of logical channels associated with the transmissions; wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission; wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission.

[0157] In a fifty-second example, there is provided the method of the fiftieth or fifty-first example, wherein an additional priority of the logical channel which triggered the scheduling request is used for the comparison in the case that the logical channel contains logical channel (LCH) priority-adjusted data at the time of intra-UE prioritization.

[0158] In a fifty-third example, there is provided the method of any one of the fiftieth to fifty-second examples, wherein in the case that the scheduling request does not have a LCP priority associated with a logical channel, a LCP priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

[0159] In a fifty-fourth example, there is provided the method of the fifty-third example, wherein the trigger for the scheduling request is at least one of beam failure recovery, positioning measurement gap activation / deactivation request, consistent LBT failure recovery, or timing advance reporting.

[0160] In a fifty-fifth example, there is provided a method for intra-UE prioritization at a user equipment (UE), the method comprising: determining whether a transmission overlaps in time with another transmission; prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of logical channel prioritization (LCP) priorities of logical channels associated with the transmissions; wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission; wherein an additional priority of the logical channel which triggered the scheduling request is used for the comparison in the case that the logical channel contains logical channel (LCH) priority-adjusted data at the time of intra-UE prioritization.

[0161] In a fifty-sixth example, there is provided the method of the fifty-fifth example, wherein in the case that the scheduling request does not have a LCP priority associated with a logical channel, a LCP priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

[0162] In a fifty-seventh example, there is provided the method of the fifty-sixth example, wherein the trigger for the scheduling request is at least one of beam failure recovery, positioning measurement gap activation / deactivation request, consistent LBT failure recovery, or timing advance reporting.

[0163] In a fifty-eighth example, there is provided a method for intra-UE prioritization at a user equipment (UE), the method comprising: determining whether a transmission overlaps in time with another transmission; prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of logical channel prioritization (LCP) priorities of logical channels associated with the transmissions; wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission; and wherein in the case that the scheduling request does not have a LCP priority associated with a logical channel, a LCP priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

[0164] In a fifty-ninth example, there is provided the method of the fifty-eighth example, wherein the trigger for the scheduling request is at least one of beam failure recovery, positioning measurement gap activation / deactivation request, consistent LBT failure recovery, or timing advance reporting.

[0165] In a sixtieth example, there is provided a method of a user equipment, the method comprising: recalculating a logical channel prioritization (LCP) priority of a logical channel (LCH), wherein the recalculation is triggered by at least one of: reconfiguration of existing LCHs, addition of new LCHs, regrouping of LCHs into logical channel groups (LCGs), Medium Access Control (MAC) protocol data units (PDU) assembly, MAC PDU transmission, buffer status report (BSR) triggering, scheduling request (SR) triggering, delay status report (DSR) triggering, or insertion of MAC control elements (CEs) into the MAC PDU.

[0166] In a sixty-first example, there is provided the method of the sixtieth example, further comprising the method of any one of the thirty-third to fifty-ninth examples.

[0167] In a sixty-second example, there is provided a user equipment (UE) configured to operate according to a method of any of the thirty-third to sixty-first examples.

[0168] In a sixty-third example, there is provided a computer program comprising instructions which, when the program is executed by a computer or processor, cause the computer or processor to carry out a method according any one of the thirty-third to sixty-first examples.

[0169] In a sixty-fourth example, there is provided a computer or processor-readable data carrier having stored thereon a computer program according to the sixty-third example. ABBREVIATIONS / DEFINITIONS In the present disclosure, the following abbreviations and definitions may be used. 3 GPP 3rd Generation Partnership Project 5G 5th Generation 5GC 5G Core BSR Buffer Status Report CE Control Element DSR Delay Status Report DU Distributed Unit FFS For Further Study gNB 5G base station IAB Integrated Access and Backhaul ID Identity / Identification IP Internet Protocol IE Information Element LBT Listen-Before-Talk LCG Logical Channel Group LCH Logical Channel LCID Logical Channel ID LCP Logical Channel Prioritization LTE Long Term Evolution MAC Medium Access Control NR New Radio PBR Prioritized Bit Rate PDCP Packet Data Conversion Protocol PDU Protocol Data Unit PHR Power Headroom Report RAN Radio Access Network RAN2 Radio layer 2 and Radio layer 3 Working Group Rei Release SDU Service Data Unit TR Technical Report TS Technical Specification UE User Equipment UL UpLink URLLC Ultra-Reliable and Low Latency Communications XR extended Reality

Claims

What is claimed is:

1. A method for intra-UE prioritization at a user equipment (UE), the method comprising:determining whether a transmission overlaps in time with another transmission;prioritizing, in the case that the transmission overlaps in time with another transmission, one of the transmissions based on a comparison of logical channel prioritization (LCP) priorities of logical channels associated with the transmissions;wherein prioritizing one of the transmissions based on a comparison of LCP priorities comprises:determining whether any of the logical channels associated with the transmissions contain logical channel (LCH) priority-adjusted data to be transmitted in the overlapping time;determining, in the case that any of the logical channels associated with the transmissions contain LCH priority-adjusted data to be transmitted in the overlapping time, whether the remaining time before discard of any buffered data in each logical channel containing LCH priority-adjusted data is below a configured threshold for the logical channel; andprioritizing one of the transmissions based on a comparison of LCP priorities by using, in the case that the remaining time before discard of any buffered data in a logical channel containing LCH priority-adjusted data is below the configured threshold for the logical channel, an additional LCP priority for the logical channel for the comparison,wherein one of the transmissions includes an uplink grant transmission or a scheduling request transmission, and wherein the other transmission includes an uplink grant transmission.

2. The method of claim 1, wherein determining whether any of the logical channels associated with the transmissions contains LCH priority-adjusted data comprises determiningwhether any of the logical channels containing LCH priority-adjusted data to be transmitted in the overlapping time are at least one of:multiplexed in Medium Access Control (MAC) protocol data units (PDUs) associated with overlapping time resources; orcan be multiplexed in MAC PDUs associated with the overlapping time resources.

3. The method of claim 2, wherein the additional LCP priority for the comparison is only used if the logical channels containing LCH priority-adjusted data to be transmitted in the overlapping time are multiplexed in MAC PDUs associated with overlapping time resources.

4. The method of any one of claims 1 to 3, wherein one of the overlapping transmissions is a configured uplink grant transmission, and wherein another one of the overlapping transmissions is a dynamically allocated uplink transmission in the same serving cell or another configured uplink grant transmission in the same serving cell.

5. The method of any one of claims 1 to 3, wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission in the same serving cell.

6. The method of claim 5, wherein in the case that the scheduling request transmission is triggered according to a buffer status report procedure, the LCP priority of the logical channel which triggered the scheduling request is the LCP priority of the logical channel at the time of triggering the buffer status report that triggered the scheduling request.

7. The method of claim 5 or 6, wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission in the case that any of the logical channels containing LCH priority-adjusted data to be transmitted in the overlapping time are multiplexed in MAC PDUs associated with overlapping time resources.

8. The method of claim 5 or 6, wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission.

9. The method of claim 5, wherein the additional priority of the logical channel which triggered the scheduling request is used for the comparison in the case that the logical channel contains the LCH priority-adjusted data at the time of intra-UE prioritization.

10. The method of any one of claims 5 to 9, wherein in the case that the scheduling request does not have a LCP priority associated with a logical channel, a LCP priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

11. The method of claim 10, wherein the trigger for the scheduling request is at least one of beam failure recovery, positioning measurement gap activation / deactivation request, consistent LBT failure recovery, or timing advance reporting.

12. A method for intra-UE prioritization at a user equipment (UE), the method comprising:determining whether a transmission overlaps in time with another transmission;prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of logical channel prioritization (LCP) priorities of logical channels associated with the transmissions;wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission; andwherein in the case that the scheduling request transmission is triggered according to a buffer status report procedure, the LCP priority of the logical channel which triggered the scheduling request is the LCP priority of the logical channel at the time of triggering the buffer status report that triggered the scheduling request.

13. The method of claim 12, wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission in the case that any of the logical channels contain logical channel (LCH) priority-adjusted data to be transmitted in the overlapping time and are multiplexed in Medium Access Control (MAC) protocol data units (PDUs) associated with overlapping time resources and the remaining time before discard of any buffered data in those logical channels is below the configured threshold for that logical channel.

14. The method of claim 12, wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission.

15. The method of claim 13 or 14, wherein an additional LCP priority of the logical channel which triggered the scheduling request is used for the comparison in the case that the logical channel contains LCH priority-adjusted data at the time of intra-UE prioritization.

16. The method of any one of claims 12 to 15, wherein in the case that the scheduling request does not have a LCP priority associated with a logical channel, a priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

17. A method for intra-UE prioritization at a user equipment (UE), the method comprising:determining whether a transmission overlaps in time with another transmission;prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of logical channel prioritization (LCP) priorities of logical channels associated with the transmissions;wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission;wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission in the case that any of the logical channels contain logical channel (LCH) priority-adjusted data to be transmitted in the overlapping time and are multiplexed in Medium Access Control (MAC) protocol data units (PDUs) associated with overlapping time resources and the remaining time before discard of any buffered data in those logical channels is below the configured threshold for that logical channel.

18. A method for intra-UE prioritization at a user equipment (UE), the method comprising:determining whether a transmission overlaps in time with another transmission;prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of logical channel prioritization (LCP) priorities of logical channels associated with the transmissions;wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission;wherein in the case that the scheduling request transmission is not triggered according to a buffer status report procedure or a pre-emptive buffer status report procedure, the configured uplink grant transmission or dynamically allocated uplink transmission is prioritized over the scheduling request transmission.

19. The method of claim 17 or 18, wherein an additional priority of the logical channel which triggered the scheduling request is used for the comparison in the case that the logical channel contains logical channel (LCH) priority-adjusted data at the time of intra-UE prioritization.

20. The method of any one of claims 17 to 19, wherein in the case that the scheduling request does not have a LCP priority associated with a logical channel, a LCP priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

21. A method for intra-UE prioritization at a user equipment (UE), the method comprising:determining whether a transmission overlaps in time with another transmission;prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of logical channel prioritization (LCP) priorities of logical channels associated with the transmissions;wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission;wherein an additional priority of the logical channel which triggered the scheduling request is used for the comparison in the case that the logical channel contains logical channel (LCH) priority-adjusted data at the time of intra-UE prioritization.

22. The method of claim 21, wherein in the case that the scheduling request does not have a LCP priority associated with a logical channel, a LCP priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

23. A method for intra-UE prioritization at a user equipment (UE), the method comprising:determining whether a transmission overlaps in time with another transmission;prioritizing, in the case that the a transmission overlaps in time with another transmission, one of the transmissions based on a comparison of logical channel prioritization (LCP) priorities of logical channels associated with the transmissions;wherein one of the overlapping transmissions is a scheduling request transmission, and wherein another one of the overlapping transmissions is dynamically allocated uplink transmission or another configured uplink grant transmission; andwherein in the case that the scheduling request does not have a LCP priority associated with a logical channel, a LCP priority of the scheduling request transmission is determined based on the trigger for the scheduling request.

24. A method of a user equipment, the method comprising:recalculating a logical channel prioritization (LCP) priority of a logical channel (LCH), wherein the recalculation is triggered by at least one of: reconfiguration of existing LCHs, addition of new LCHs, regrouping of LCHs into logical channel groups (LCGs), Medium Access Control (MAC) protocol data units (PDU) assembly, MAC PDU transmission, buffer status report (BSR) triggering, scheduling request (SR) triggering, delay status report (DSR) triggering, or insertion of MAC control elements (CEs) into the MAC PDU.

25. The method of claim 24, further comprising the method of any one of claims 1 to 24.

26. A user equipment (UE) configured to operate according to a method of any preceding claim.A

Images