Patent Description:
The following abbreviations are herewith defined, at least some of which are referred to within the following description: Third Generation Partnership Project ("3GPP"), Fifth Generation Core Network ("5CG"), Access and Mobility Management Function ("AMF"), Positive-Acknowledgment ("ACK"), Access Stratum ("AS"), Base Station ("BS"), Control Element ("CE"), Channel State Information ("CSI"), Core Network ("CN"), Control Plane ("CP"), Downlink Control Information ("DCI"), Downlink ("DL"), Evolved Node-B ("eNB"), Evolved Packet Core ("EPC"), Global System for Mobile Communications ("GSM"), Hybrid Automatic Repeat Request ("HARQ"), Home Subscriber Server ("HSS"), Information Element ("IE"), Internet-of-Things ("IoT"), Long Term Evolution ("LTE"), Multiple Access ("MA"), Mobility Management Entity ("MME"), Modulation Coding Scheme ("MCS"), Machine Type Communication ("MTC"), Negative-Acknowledgment ("NACK") or ("NAK"), New Generation (<NUM>) Node-B ("gNB"), New Generation Radio Access Network ("NG-RAN", a RAN used for <NUM> networks), New Radio ("NR", a <NUM> radio access technology; also referred to as "<NUM> NR"), Non-Access Stratum ("NAS"), Network Slice Selection Assistance Information ("NSSAI"), Packet Data Unit ("PDU", used in connection with 'PDU Session'), Physical Downlink Control Channel ("PDCCH"), Physical Downlink Shared Channel ("PDSCH"), Physical Random Access Channel ("PRACH"), Physical Resource Block ("PRB"), Physical Uplink Control Channel ("PUCCH"), Physical Uplink Shared Channel ("PUSCH"), Public Land Mobile Network ("PLMN"), Quality of Service ("QoS"), Radio Access Network ("RAN"), Radio Access Technology ("RAT"), Radio Bearer ("RB"), Radio Resource Control ("RRC"), Random-Access Channel ("RACH"), Random Access Response ("RAR"), Radio Network Temporary Identifier ("RNTI"), Reference Signal ("RS"), Registration Management ("RM", refers to NAS layer procedures and states), Receive ("RX"), Radio Link Control ("RLC"), Scheduling Request ("SR"), Shared Channel ("SCH"), Session Management Function ("SMF"), Sounding Reference Signal ("SRS"), Transport Block ("TB"), Transport Block Size ("TBS"), Transmit ("TX"), Unified Data Management ("UDM"), User Data Repository ("UDR"), Uplink Control Information ("UCI"), User Entity/Equipment (Mobile Terminal) ("UE"), Uplink ("UL"), User Plane ("UP"), Ultra-reliability and Low-latency Communications ("URLLC"), and Worldwide Interoperability for Microwave Access ("WiMAX"). As used herein, "HARQ-ACK" may represent collectively the Positive Acknowledge ("ACK") and the Negative Acknowledge ("NACK"). ACK means that a TB is correctly received while NACK (or NAK) means a TB is erroneously received.

In NR Rel-<NUM> it is not possible to preempt a dynamic uplink grant allocation with another dynamic grant received via DCI, i.e., uplink preemption is not supported. In other words, within a single cell, "out-of-order" scheduling is not supported in Rel-<NUM> for the case of two dynamic grants. Rather, once a DCI is received for a PUSCH transmission at a first time, a later received DCI should correspond to a PUSCH transmission at a later time. Moreover, for a resource conflict between configured grant resources and dynamic allocated resources, a UE according to the current specified NR Rel-<NUM> behavior would always prioritize a dynamic grant over a configured grant. However, this may lead to problems where the UE would need to use grants which are not suitable for the transmission of critical/high urgency packets.

R1-<NUM> is a 3GPP discussion document titled "<NPL>, and discusses some aspects of inter-UE UL pre-emption by URLLC transmission. R2-<NUM> is 3GPP discussion document titled "Intra-UE prioritization" submitted by Ericsson at the TSG RAN WG2 meeting #103bis in Chengdu, China on <NUM> October <NUM> and discusses the sub-area "UL/DL intra-UE prioritization/multiplexing, i.e. prioritization (for example dropping, delaying or puncturing lower priority service) between different categories of traffic in the UE, including both data and control channels and considering (RAN2/RAN1).

R1-<NUM> is a 3GPP discussion document titled "<NPL>, and describes some views on UCI multiplexing with different reliability requirement and UL inter/intra-UE data multiplexing with different reliability requirements.

Claim <NUM> defines a method in a user equipment, claim <NUM> defines a user equipment. In the following, any method and/or apparatus referred to as embodiments but nevertheless do not fall within the scope of the appended claims are to be understood as examples helpful in understanding the invention.

This disclosure provides an efficient protocol operation for the case of Intra-UE UL prioritization. For uplink, a UE may be scheduled with two dynamic uplink grants allocating overlapping PUSCH resources for data of different priority levels. For example, the gNB may schedule an urgent/critical URLLC PUSCH transmission, e.g., using a high reliable MCS for the transmission, to preempt a previously scheduled PUSCH transmission intended for lower priority eMBB data. Several embodiments of this disclosure are related to the detailed UE behavior for UL preemption.

The disclosure further contains embodiments providing solutions for cases when there is a conflict of allocated UL resources. For the uplink a UE may transmit data of high priority (e.g., URLLC) on resources allocated by a configured grant. In addition, the UE may be scheduled by dynamic UL grants e.g., for transmission of lower priority data such as eMBB which may lead to a UL resource conflict, i.e., UE has two allocated UL resources at the time of uplink transmission.

Further embodiments are related to the support of packets of different priority/urgency level within one radio bearer or QoS flow. For example, an Industrial IoT traffic flow may support critical packets, e.g., emergency stop packets, within a radio bearer or a QoS flow. Those critical packets are to be prioritized over other packets within the same radio bearer or the QoS flow.

The invention is based on <FIG> and includes a modified step <NUM>, directed receiving the second allocation via DCI including a priority allocation parameter. more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings.

Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages.

As used herein, "a member selected from the group consisting of A, B, and C and combinations thereof' includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.

The code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

Generally, the present disclosure describes systems, methods, and apparatus for efficient protocol operation for uplink preemption. This disclosure provides an efficient protocol operation for the case of Intra-UE UL prioritization. For uplink ("UL"), a UE may be scheduled with two dynamic uplink grants allocating overlapping PUSCH resources for data of different priority levels. For example, a gNB may schedule an urgent/critical URLLC PUSCH transmission, e.g., using a high reliable MCS for the transmission, to preempt a previously scheduled PUSCH transmission intended for lower priority eMBB data. Several embodiments of this disclosure are related to the detailed UE behavior for UL preemption.

The disclosure further contains embodiments providing solutions for cases when there is a conflict of allocated UL resources. For UL, a UE may transmit data of high priority (e.g., URLLC) on resources allocated by a configured grant. In addition, the UE may be scheduled by dynamic UL grants, e.g., for transmission of lower priority data such as eMBB, which may lead to a UL resource conflict, i.e., UE has two allocated UL resources at the time of uplink transmission. Recall that a UE according to the current specified NR Rel-<NUM> behavior would always prioritize the dynamic grant (here, associated with the lower priority data) over the configured grant (here, associated with the higher priority data).

Further embodiments are related to the support of packets of different priority/urgency level within one radio bearer or QoS flow. For example, an Industrial loT ("IIoT") traffic flow may support critical packets, e.g., emergency stop packets, within a radio bearer or a QoS flow. Those critical packets are to be prioritized over other packets within the same radio bearer or the QoS flow.

The first problem mentioned above, i.e., detailed UE/protocol behavior for UL preemption, has not been addressed by 3GPP. Recall that in NR Rel-<NUM>, it is not possible to preempt a dynamic uplink grant allocation with another dynamic DCI, i.e., uplink preemption is not supported. In other words, within a single cell, "out-of-order" scheduling is not supported in Rel-<NUM> (at least for the case of two dynamic grants), that is, once a DCI is received for a PUSCH transmission, a later DCI is to correspond to a PUSCH transmission at a later time.

For the second problem mentioned above, i.e., resource conflict between configured grant resources and dynamic allocated resources, a UE according to the current specified NR Rel-<NUM> behavior is to prioritize a dynamic grant over a configured grant. As noted above, this may lead to problems where the UE would need to use grants which are not suitable for the transmission of critical/high urgency packets. Also, the support of packets of different priority levels within the same radio bearer/QoS flow is not supported so far in the current specified NR Rel-<NUM>.

<FIG> depicts an embodiment of a wireless communication system <NUM> for efficient protocol operation for uplink preemption, according to various embodiments of the disclosure. In one embodiment, the wireless communication system <NUM> includes remote units <NUM>, base units <NUM>, and communication links <NUM>. Even though a specific number of remote units <NUM>, base units <NUM>, and communication links <NUM> are depicted in <FIG>, one of skill in the art will recognize that any number of remote units <NUM>, base units <NUM>, and communication links <NUM> may be included in the wireless communication system <NUM>.

In one implementation, the wireless communication system <NUM> is compliant with the NR system specified in the 3GPP specifications and/or the LTE system specified in 3GPP. More generally, however, the wireless communication system <NUM> may implement some other open or proprietary communication network, for example, WiMAX, among other networks.

In one embodiment, the remote units <NUM> may include computing devices, such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. The remote units <NUM> may communicate directly with one or more of the base units <NUM> via uplink ("UL") and downlink ("DL") communication signals. Furthermore, the UL and DL communication signals may be carried over the communication links <NUM>.

In some embodiments, a remote unit <NUM> may establish a data connection (e.g., a PDU session) with the data network <NUM> via the mobile core network <NUM>. Here, the data path of a PDU session may be established over one of the multiple network slices <NUM> supported by the mobile core network <NUM>. The specific network slice <NUM> used by the PDU session may be determined by the S-NSSAI attribute of the PDU session. Here, the remote unit <NUM> may be provisioned with Network Slice Selection Policy ("NSSP") rules which it uses to determine how to route a requested PDU session.

The base units <NUM> may be distributed over a geographic region. In certain embodiments, a base unit <NUM> may also be referred to as a RAN node, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a femtocell, an access point, a device, or by any other terminology used in the art. The base units <NUM> are generally part of an access network <NUM>, such as a radio access network ("RAN"), that may include one or more controllers communicably coupled to one or more corresponding base units <NUM>. These and other elements of the access network <NUM> are not illustrated but are well known generally by those having ordinary skill in the art. The base units <NUM> connect to the mobile core network <NUM> via the access network <NUM>. The access network <NUM> and mobile core network <NUM> may be collectively referred to herein as a "mobile network" or "mobile communication network.

The base units <NUM> may communicate directly with one or more of the remote units <NUM> via communication signals. Generally, the base units <NUM> transmit downlink ("DL") communication signals to serve the remote units <NUM> in the time, frequency, and/or spatial domain. Furthermore, the DL communication signals may be carried over the communication links <NUM>. The communication links <NUM> may be any suitable carrier in licensed or unlicensed radio spectrum. The communication links <NUM> facilitate communication between one or more of the remote units <NUM> and/or one or more of the base units <NUM>.

In one embodiment, the mobile core network <NUM> is a <NUM> core network ("5GC"), which may be coupled to a data network <NUM>, like the Internet and private data networks, among other data networks. In some embodiments, the remote units <NUM> communicate with an application function ("AF") <NUM> (external to the mobile core network <NUM>) via a network connection with the mobile core network <NUM>. Each mobile core network <NUM> belongs to a single public land mobile network ("PLMN"). For example, other embodiments of the mobile core network <NUM> include an enhanced packet core ("EPC") or a Multi-Service Core as describe by the Broadband Forum ("BBF").

The mobile core network <NUM> includes several network functions ("NFs") and multiple network slices <NUM>. As depicted, the mobile core network <NUM> includes at least one unified data management with an internal user data repository ("UDM/UDR") <NUM>, at least one policy control function ("PCF") <NUM>, at least one access and mobility management function ("AMF") <NUM>, and at least one network exposure function ("NEF") <NUM>. Although a specific number of NFs are depicted in <FIG>, one of skill in the art will recognize that any number of NFs may be included in the mobile core network <NUM>. In certain embodiments, each of the multiple network slices <NUM> includes its own dedicated network functions (not shown), such as a session management function ("SMF") and user plane function ("UPF"). While the depicted embodiment shows a single AMF in the mobile core network <NUM>, in other embodiments each of the multiple network slices <NUM> may implement its own AMF.

The UDM/UDR <NUM> comprises a Unified Data Management ("UDM") and its internal component User Data Repository ("UDR"). The UDR holds subscription data including policy data. Specifically, the policy data stored by the UDM/UDR <NUM> includes the NSSP. The UDM/UDR <NUM>, PCF <NUM>, AMF <NUM>, and SMF (not shown) are examples of control plane network functions of the mobile core network <NUM>. Control plane network functions provide services such as UE registration, UE connection management, UE mobility management, session management, and the like. In contrast, a UPF provides data transport services to the remote units <NUM>.

The multiple network slices <NUM> are logical networks within the mobile core network <NUM>. The network slices <NUM> are partitions of resources and/or services of the mobile core network <NUM>. Different network slices <NUM> may be used to meet different service needs (e.g., latency, reliability, and capacity). Examples of different types of network slices <NUM> include enhanced mobile broadband ("eMBB"), massive machine-type communication ("mMTC"), and ultra-reliability and low latency communications ("URLLC"). A mobile core network <NUM> may include multiple network slice instances of the same network slice type. Different network slice instance of the same type may be distinguished by a slice "tenant" (also known as "slice differentiator") associated with the instance.

In some embodiments, a remote unit <NUM> may be scheduled with two dynamic uplink grants allocating overlapping PUSCH resources for data of different priority levels. Here, the later received dynamic grant may allocate resources for higher priority traffic. Accordingly, the remote unit <NUM> acts on the uplink grants "out-of-order" by preempting the first received dynamic grant (associated with lower priority traffic) in order to process and fulfill the second received grant (associated with higher priority traffic).

In some embodiments, a remote unit <NUM> may receive a dynamic grant of PUSCH resources that conflicts (e.g., overlaps) with a previously configured grant. Here, the (previously) configured grant may be associated with higher priority traffic, while the later received dynamic grant may allocate resources for lower priority traffic. Although dynamic grants are typically prioritized over configured grants, here the remote unit <NUM> recognizes that the configured grant is associated with higher urgency traffic than the dynamic grant and thus preempts the dynamic grant (associated with lower priority traffic) in order to process and fulfill the configured grant (associated with higher priority traffic).

In some embodiments, a remote unit <NUM> may support different priority levels within the same radio bearer or QoS flow. Here, the remote unit <NUM> prioritizes the higher priority (e.g., more critical) data packets over other packets within the same radio bearer or QoS flow.

For uplink preemption, if a DCI which is preempted is for scheduling a retransmission, then the remote unit <NUM> follows the preemption DCI (e.g., associated with higher priority data) and also further processes the TB in accordance to the preempted grant, which TB may be stored in a HARQ transmission buffer for retransmission (similar treatment as for measuring gap). However, if the DCI which is preempted is for scheduling an initial transmission, then the remote unit <NUM> may ignore the preempted DCI and only follow the preemption DCI, e.g., no TB is generated for the preempted lower priority DCI. Note that if processing of the preempted DCI has already begun, then the remote unit may pause (e.g., interrupt) processing of the preempted (lower priority) DCI to follow the preemption (higher priority) DCI.

In some embodiments, the remote unit <NUM> may receive a DCI that explicitly indicates that it is a preempting grant. In one embodiment, a UL-SCH indicator in DCI <NUM>-<NUM> (e.g., a <NUM>-bit field) may be used to indicate the preemption (e.g., that the DCI is associated with high urgency). In another embodiment, an SRS with invalid state is used to indicate a high urgency/ preempting grant. In yet another embodiment, a specific RNTI may be used to indicate the preemption.

In case the remote unit <NUM> has some (dynamically) scheduled UL resources which are intended for low priority traffic like eMBB and then high urgency/reliable data arrives in the remote unit's buffer, the remote unit <NUM> may be allowed to use the scheduled resources for the transmission of high urgency/reliable data. In certain embodiments, the remote unit <NUM> uses a different MCS/TB size for the transmission of high urgency data than the scheduled MCS/TB size. Therefore, the remote unit <NUM> may also include some UCI (uplink control information ) in the assigned resources which indicate the used MCS for gNB detection.

Here, UCI inclusion will be done at the PHY layer entity. Moreover, the UCI position may be fixed such that the base unit <NUM> is able to detect UCI based on CRC check. In certain embodiments, the UCI is positioned at the start of the PUSCH resource, e.g. after upfront DM-RS. In certain embodiments, the modulation scheme of UCI could be predefined or fixed (e.g., always QPSK). Additionally, the remote unit <NUM> may modify power control parameters. For example, the remote unit <NUM> may use some predefined power setting (Po, alpha) for the transmission of the high urgency data. Further, the remote unit <NUM> may determine whether it is allowed/can use the allocated UL resource for the transmission of the high urgency/reliable data. In one embodiment, the remote unit <NUM> may have one table where for different TB sizes the required number of allocated RBs are defined. In case the allocated RB size of the low priority grant supports the packet size of the high urgency data then the remote unit <NUM> is allowed to transmit the data on the allocated UL resources. In another embodiment, the remote unit <NUM> may use the modulation scheme given for the allocated UL resource and calculate the coding rate for the transmission of the high urgency data. In case the determined code rate is lower than a predefined threshold then the remote unit <NUM> transmits the data on the allocated UL resources.

For the case that the remote unit <NUM> has a configured grant and a dynamic scheduled resource and needs to transmit critical/high urgency data. the remote unit <NUM> determines which UL resources to use for the transmission of the critical data depending on certain defined criteria. For example, if the high urgency data packet size fits only in dynamic scheduled UL resources the remote unit <NUM> uses the dynamic scheduled UL resources. If the high urgency data packet size fits only in configured UL resources, then the remote unit <NUM> uses the configured UL resources. If the high urgency data packet size fits both in dynamic scheduled UL resources as well as in configured UL resources, then the remote unit <NUM> decides based on further criteria. If the high urgency data packet size fits neither in dynamic scheduled UL resources nor in configured UL resources, then the remote unit <NUM> sends some "high urgency BSR" together with eMBB (or other non-high-urgency) data on the dynamically allocated UL resources indicating the size of the high urgency data.

Moreover, protocol behavior for the case that packets of different priority is supported within one bearer/QoS flow may include the remote unit <NUM> having one PDCP entity mapped to several RLC entities/LCHs without duplication.

<FIG> depicts a network procedure <NUM> for efficient uplink preemption, according to embodiments of the disclosure. The network procedure <NUM> involves a UE <NUM> and a RAN node <NUM>. Here, the UE <NUM> may be one embodiment of the remote unit <NUM>. Moreover, the RAN node <NUM> may be one embodiment of the base unit <NUM>. Examples of a RAN node <NUM> include a gNB or other <NUM>th generation base station.

The RAN node <NUM> sends a first UL grant <NUM> to the UE <NUM>. At a later point in time, but prior to the UE <NUM> transmitting according to the first UL grant, the RAN node <NUM> sends a second (dynamic) UL grant <NUM> to the UE <NUM>. In one embodiment, the first UL grant <NUM> is a configured grant (e.g., a semi-static grant) involving periodic UL resources. In another embodiment, the first UL grant <NUM> is a dynamic grant allocating UL resources. A configured grant differs from a dynamically scheduled grant in that the resources in a configured grant are periodic and semi-persistently scheduled. In certain embodiments, multiple devices may share the periodic resources. In contrast, a dynamic grant is a one-time grant of (aperiodic) resources. Typically, resources scheduled by dynamic grant are not shared among multiple devices.

In order to efficiently process UL transmissions, the UE <NUM> identifies traffic types associated with the "conflicting" UL grants (e.g., UL grants scheduled for the same transmission opportunity, e.g., same and or/overlapping frame, slot, TTI, etc.) and, if needed, preempts a higher priority grant type in order to act on the highest priority traffic type (see block <NUM>).

For example, the first UL grant <NUM> may be a dynamic grant. As mentioned above, the UE <NUM> will typically act on the first received dynamic UL grant prior to acting on the second received dynamic UL grant. However, where the traffic type associated with the second received dynamic UL grant is of a higher priority than the traffic associated with the first received dynamic UL grant, the UE <NUM> will preempt the first received dynamic UL grant in order to act upon the second received dynamic UL grant.

In another example, the first UL grant <NUM> may be a configured (e.g., semi-persistent) grant. As mentioned above, the UE <NUM> will typically act on the dynamic UL grant prior to acting on the configured UL grant (e.g., a dynamic grant has priority over a configured grant). However, where the traffic type associated with the configured UL grant is of a higher priority than the traffic associated with the dynamic UL grant, the UE <NUM> will preempt the dynamic UL grant (e.g., the second UL grant) in order to act upon the configured UL grant.

As depicted, the UE <NUM> transmits to the RAN node <NUM> PUSCH <NUM> associated with the higher priority traffic type. In the first example above, the UE <NUM> transmits PUSCH <NUM> associated with the second received UL grant <NUM> because it is associated with higher priority traffic then the first received UL grant <NUM>. In the second example above, the UE <NUM> transmits PUSCH <NUM> associated with the configured UL grant because it is associated with higher priority traffic in the dynamic UL grant.

<FIG> depicts a timing diagram for a UL preemption scenario <NUM>, according to embodiments of the disclosure. The UL preemption scenario <NUM> may be implemented at a UE, such as the remote unit <NUM> and/or the UE <NUM>. At time 't1', the UE receives an allocation of uplink resources (e.g., PUSCH resources) via PDCCH. In the embodiment of <FIG>, it is assumed that the scheduled resources are for normal priority data and are associated with an initial transmission for a first HARQ process (HARQ#<NUM>). Here, the allocation of uplink resources may be a dynamic grant received via DCI. As depicted, the allocated uplink resources (PUSCH resources) begin at time 't2'. Accordingly, the UE sends data for HARQ#<NUM> in the PUSCH transmission that begins at time 't2.

At time 't3', the UE receives another allocation of uplink resources (e.g., PUSCH resources) via PDCCH. The second grant is also associated with an initial transmission for the first HARQ process (HARQ#<NUM>). Here, the allocation of uplink resources may be a dynamic grant received via DCI. As depicted, the allocated uplink resources (PUSCH resources) begin at time 't5'.

At time 't4' (e.g., after receiving the allocation of uplink resources, but before time 't5') the UE receives a preempting DCI allocating resources for high urgency (or critical) data which at least partially overlaps with the resource allocation scheduled by the grant received at time 't3'. In the embodiment of <FIG>, the high urgency/critical data is associated with an initial transmission for a different HARQ process (e.g., HARQ#<NUM>). The DCI received at 't4' preempts the PUSCH transmission scheduled by DCI received in 't3,' therefore the UE transmits the high urgency/critical data in the PUSCH resources scheduled at 't5.

According to a first solution for efficient uplink preemption, a UE is scheduled with two dynamic grants (DCI) allocating overlapping PUSCH resources, whereby the second dynamic grant which is received later than the first dynamic grant allocates UL resources for high urgency/priority traffic. The second (later) DCI allocating PUSCH resources for high urgency data, according to this embodiment, takes priority over the PUSCH resources allocated by the first DCI, i.e., second DCI preempts the previously scheduled PUSCH transmission (by the first DCI). In one example gNB schedules a URLLC PUSCH transmission by means of a DCI to preempt a previously scheduled PUSCH transmission for eMBB traffic.

According to this first solution, a UE, e.g., the MAC entity of the UE, processes and acts according to the second (later) received DCI scheduling PUSCH resources for high urgency/priority/reliability traffic, which is also referred to as the "preempting grant" or "preempting DCI. " For cases when the first received DCI, which is referred to as "preempted grant," is scheduling PUSCH resources for a retransmission, i.e., where the NDI is not toggled, the UE may also further execute/process the first received DCI in parallel. To be more specific, the MAC entity identifies the HARQ process associated with the preempting grant, generates a MAC PDU in accordance with the transport block size indicated in the grant (assuming that the preempting grant requests a new initial transmission), and stores the generated MAC PDU in the associated HARQ buffer. In addition, the MAC entity in the UE generates a retransmission of the TB stored in the HARQ process indicated in the preempted grant, i.e., MAC delivers the TB stored in the HARQ process (Tx buffer) to the physical layer.

Even though the physical layer may not perform the retransmission of the TB because the high urgency grant takes priority over the preempted retransmission grant (i.e., the physical layer performs transmission according to the preempting grant), from MAC layer/HARQ protocol point of view the (re)transmission takes place (this behavior is similar to the case of a PUSCH transmission colliding with a measurement gap). It should be noted that the assumption for the described behavior is, that the HARQ process indicated by the preempting grant is different than the HARQ process addressed by the preempted grant.

According to one implementation of the first solution, a UE, e.g., the MAC entity of the UE, may process and execute the second (later) received DCI scheduling PUSCH resources for high urgency/priority/reliability traffic, i.e., "preempting grant /DCI," and ignores the first received uplink grant, i.e., "preempted grant," for cases when the preempted grant is scheduling an initial new transmission, i.e., where the NDI is toggled. To be more specific, the MAC entity identifies the HARQ process associated with the preempting grant, generates a MAC PDU in accordance with the transport block size indicated in the grant (assuming that the preempting grant requests a new initial transmission), and stores the generated MAC PDU in the associated HARQ buffer. Here, the UE, e.g., the MAC entity of the UE, ignores the preempted uplink grant, i.e., it considers the preempted grant as not having been received.

One of the consequences of ignoring the preempted grant is, that the grant (even though received) is not stored for the corresponding HARQ process and that the NDI signaled within this grant is not used for a later NDI comparison, i.e., to determine whether an initial or retransmission is requested by gNB. One motivation to ignore the preempted grant, i.e., first received DCI, is that the UE might not be able to finish the generation of the Transport block respectively the channel coding/rate matching according to the first received DCI in addition to the generation/transmission of the high urgency TB due to processing time constraints.

According to another implementation of the first solution, the UE, e.g., the MAC entity of the UE, processes/executes the preempting grant and also processes the first received uplink grant, i.e., "preempted grant," for cases when the preempted grant is scheduling an initial new transmission, i.e., where the NDI is toggled. According to this implementation, the UE will still follow/process the preempted uplink grant but may interrupt the generation/processing of the transport block while executing/processing the preempting grant. The assumption is that UE has already started executing/processing the first received uplink grant, i.e., LCP has been already started, when the second DCI, i.e., the preempting grant, is received. The processing of the preempted grant may be resumed, e.g., finishing the generation of the MAC PDU and storing it in the corresponding HARQ buffer, once the generation of the high urgency/critical TB (with channel coding/rate matching etc.) is finished respectively when UE has sufficient processing resources available.

According to a further implementation of the first solution, the UE does not process/execute a received UL grant, e.g., start LCP procedure, until the point of time, i.e., slot or PDCCH occasion, where a potential preemption UL grant may occur. The latest timing, i.e., slot or PDCCH occasion, where a potential preemption DCI may occur before an allocated PUSCH resource may be configured or fixed, i.e., minimum processing time of the UE for a PUSCH transmission (e.g., as defined in section <NUM> of TS <NUM>).

In various embodiments, the MAC entity is aware of a received DCI preempting an earlier scheduled PUSCH allocation in order to act according to above specified behavior, e.g., ignore the preempted grant if the UE did not start processing it (UE has not started with the formation of corresponding MAC TB) or interrupt processing the preempted grant and resume the processing at next available opportunity after having processed the preempting grant, etc. In various embodiments, the Physical layer indicates to the MAC entity whether the received grant is a high urgency respectively preemption DCI, e.g., in addition to the legacy grant information like TBS, NDI, numerology, RV etc. Therefore, according to a second solution for efficient uplink preemption, the DCI (uplink grant) explicitly indicates that this DCI is a high urgency/priority PUSCH allocation (potentially) preempting an earlier overlapping PUSCH allocation.

According to one implementation of the second solution, a new RNTI is defined which indicates that a DCI (uplink grant) addressed to this RNTI is a high urgency/priority DCI preempting a potential earlier overlapping PUSCH allocation. In a certain implementation the INT-RNTI indicating in legacy NR specifications a preemption in the DL, is used to indicate also an UL preemption. According to another implementation of the second embodiment one or more fields respectively codepoints of field(s) in the DCI are used to indicate high urgency/preemption. In one implementation the "UL-SCH indicator" field in the DCI, e.g., DCI format <NUM>-<NUM>, in conjunction with the "CSI request" field is used to indicate a high urgency/ preempting grant. A value of "<NUM>" for the UL-SCH indicator field with "CSI request" field set to all zero(s) indicates a high urgency /preemption DCI.

In an alternative implementation of the second solution, the SRS request field set to a predefined value/codepoint indicates a high urgency/ preempting grant, i.e., no SRS transmission is to be performed by the UE in this case.

According to a third solution for efficient uplink preemption, the UE determines whether to use a configured grant allocation or dynamically scheduled UL resources for transmission of high urgency/critical data depending on at least one of the following criteria: packet size, code rate, modulation level, spectral efficiency, and power headroom.

In various embodiments, the UE considers data packet size when determining whether to use a configured grant allocation or dynamically scheduled UL resources for transmission of high urgency/critical data. If the high urgency data packet size fits only in dynamic scheduled UL resources the UE uses the dynamic scheduled UL resources. If the high urgency data packet size fits only in configured UL resources the UE uses the configured UL resources.

If the high urgency data packet size fits both in dynamic scheduled UL resources as well as in configured UL resources the UE determines the UL resource for transmission at least based on one of the following defined options: In a first option, the UE is configured which resource to use (or it is fixed by specification). According to a second option, the UE uses the resource where the resulting code rate is lower. According to a third option, the UE uses the resource where the modulation level is rate is lower and reverts to Option <NUM> if the modulation level is identical. According to a fourth option, the UE uses the resource where the resulting spectral efficiency is lower. According to a fifth option, the UE uses the resource where the resulting power headroom is larger.

If the high urgency data packet size fits neither in dynamic scheduled UL resources nor in configured UL resources, then the UE sends some "high urgency BSR" together with eMBB (or other non-high-urgency) data on the dynamically allocated UL resources indicating the size of the high urgency data. Here, the "high urgency BSR" indicates the size (amount) of the high urgency/critical data.

<FIG> depicts a timing diagram for a UL preemption scenario <NUM>, according to embodiments of the disclosure. The UL preemption scenario <NUM> may be implemented at a UE, such as the remote unit <NUM> and/or the UE <NUM>. At time 't1', the UE receives an allocation of uplink resources (e.g., PUSCH resources) via PDCCH. In the embodiment of <FIG>, it is assumed that the scheduled resources are for normal priority data and are associated with an initial transmission for a first HARQ process (HARQ#<NUM>). Here, the allocation of uplink resources may be a dynamic grant received via DCI. As depicted, the allocated uplink resources (PUSCH resources) begin at time 't3'.

At time 't2' (e.g., after receiving the allocation of uplink resources, but before time 't3') high urgency/critical data arrives in the UE's buffer. The arrival of the high urgency/critical data causes the UE to preempt the lower priority data and instead transmit the high urgency/critical data at time 't3' using the previously scheduled PUSCH resources.

According to a fourth solution, a UE may transmit high urgency/critical data on PUSCH resources allocated for lower priority data. There might be cases where a UE has been allocated PUSCH resources intended for low priority traffic like eMBB - those PUSCH resources might have been allocated by a DCI - when high urgency/critical data arrives in UEs buffer. It should be noted that the transmission parameters of the PUSCH resources, i.e., MCS, number of RBs, etc., scheduled by the DCI might not be suitable for the transmission of high urgency/critical data. The critical data may require a very reliable transmission, e.g., successful decoding should be possible without any HARQ retransmissions in order to meet the latency requirements.

According to one implementation of the fourth solution, a UE may use allocated PUSCH resources for the transmission of the critical/urgency data. In order to meet the reliability/QoS requirements of the critical data, the UE may use different uplink transmission parameters such as modulation scheme, coding rate, TB size, redundancy version etc. as the ones scheduled for the PUSCH (e.g., by the DCI). In order to facilitate decoding at the gNB and to avoid an increased blind decoding, when using different transmission parameters for the uplink transmission than the ones allocated by the scheduler the UE may include uplink control information (UCI) indicating the transmission parameter(s) used in the PUSCH transmission. Here, the inclusion of the UCI will be done at the PHY by e.g., rate matching. The position of the UCI within the PUSCH resources may be fixed. In certain embodiments, a gNB may detect the presence of UCI based on some CRC which is attached to the UCI. In certain embodiments, the UCI may be positioned at the start of the PUSCH resource, e.g., after upfront DM-RS in order to allow for a fast detection of the UCI at the gNB side. The modulation scheme used for the transmission of the UCI may be predefined/configured or fixed in the specification, e.g., QPSK is always used.

According to one implementation of the fourth solution, when adapting the transmission parameters, e.g., TBS, MCS, RV, etc., scheduled for a PUSCH resource the UE may also use different transmission power control parameters compared to the power control parameters UE would use for a PUSCH transmission according to the scheduling grant. The power control parameters, e.g., P0 or alpha, used for a high urgency/critical transmission may be different compared to the power control parameters used for a lower priority data transmission (eMBB). In a certain implementation the power control parameters for a high urgency/critical data transmission are predefined/configured or fixed in the specification.

According to another implementation of the fourth solution, the UE determines whether it is allowed to use the allocated (low priority) UL resources for the transmission of the high urgency/critical data based on certain criteria. According to one possible implementation, the UE is configured with a table indicating for different TB sizes the corresponding minimum required number of allocated Resource Blocks (RBs). For cases when the number of RBs of the allocated (low priority) PUSCH resource is larger than or equal to the minimum #RBs as given in the table for the TB size required for the high urgency data, the UE determines that it is allowed to transmit the critical/high urgency data on the allocated (low priority) PUSCH resource, i.e., with adapted transmission parameters and/or power control parameter. According to an alternative approach, the UE uses the modulation scheme scheduled for the allocated (low priority) PUSCH resource and calculates - based on the number of allocated RBs - the coding rate for the transmission of the high urgency/critical data. In case the calculated code rate is lower than a threshold, i.e., threshold may be either fixed or preconfigured, UE is to transmit the data on the dynamically allocated UL resources.

In case UE determines that it is not allowed to transmit the high urgency/critical data on the dynamically allocated UL resources, e.g., determined code rate is too high, or number of RBs too small, the UE may send a "critical data BSR" together with other non-critical data on the dynamically allocated UL resources. This new type of buffer status report ("BSR") indicates the size of the pending high urgency/critical data. A new BSR MAC CE format may be introduced for the critical data BSR, the new format being identified by a reserved logical channel ID.

In various embodiments, when UE is configured with uplink resources, i.e., by means of a configured grant, for high urgency/critical data there may be a resource conflict between the configured grant resources and additional dynamic UL allocations (intended for other lower priority data) in case they overlap in the time domain. If high urgency/critical data is available for transmission in the UE and UE has dynamically scheduled UL resources in addition to the configured UL resources, then UE behavior needs to be defined. According to the legacy NR Rel-<NUM> specification configured grant allocations are always preempted/overridden by a dynamic grant (DCI/PDCCH).

<FIG> depicts a network procedure <NUM> for uplink preemption, according to embodiments of the disclosure. The network procedure <NUM> involves the UE <NUM> and the RAN node <NUM>. As depicted, the UE receives a configured UL grant <NUM> that is shared by multiple UEs served by the RAN node <NUM>. At some time after receiving the configured UL grant <NUM>, the UE <NUM> detects arrival of high urgency/critical data <NUM>. The UE <NUM> generates a TB <NUM> with the high urgency/critical data that includes the C-RNTI. Additionally, the UE <NUM> sends a PUSCH transmission <NUM> of the higher priority data (e.g., the high urgency/critical data).

According to a fifth solution, a UE may transmit high urgency/critical data on PUSCH resources allocated semi-statically, e.g., by means of a configured grant, for high priority/critical data which are shared by several UEs. Whenever urgent/critical data arrives in the UE buffer, the UE uses those configured UL resources for the transmission of the critical data. Because the configured resources are not allocated in a dedicated manner for only one UE, but rather shared among a group of UEs, the UE includes an identifier, e.g., C-RNTI, in the PUSCH transmission in order to provide gNB with information on the UE identity.

Note that the transmission parameters of the PUSCH resources, i.e., MCS, number of RBs, etc., allocated by the configured grant may not be always suitable for the transmission of the high urgency/critical data, i.e., there may be different packet sizes. Therefore, the UE may use different uplink transmission parameters such as modulation scheme, coding rate, TB size, redundancy version etc. as the ones scheduled for the PUSCH (e.g., by the configured grant allocation). In order to facilitate decoding at the gNB and to avoid an increased blind decoding, the UE may include uplink control information (UCI) indicating the used transmission parameter in the PUSCH transmission as well as the UE identity (e.g. C-RNTI). The UCI may also contain the ID of the used HARQ process. The inclusion of the UCI will be done at the PHY by, e.g., rate matching. The position of the UCI within the PUSCH resources may be fixed. In one embodiment, a gNB may detect the presence of UCI based on some CRC. In certain embodiments, the UCI may be positioned at the start of the PUSCH resource (e.g., after upfront DM-RS) in order to allow for a fast detection of the UCI at the gNB side. The modulation scheme used for the transmission of the UCI may be predefined/configured or fixed in the specification, e.g., QPSK may always be used.

<FIG> depicts a protocol stack <NUM> for use with UL preemption, according to embodiments of the disclosure. The protocol stack <NUM> may be implemented within a UE, such as the UE <NUM>. The protocol stack <NUM> includes a PDCP entity <NUM> located at the PDCP layer. The PDCP entity <NUM> is mapped to multiple RLC entities, here the first RLC entity <NUM> (associated with a first Logical Channel <NUM>) and a second RLC entity <NUM> (associated with a second Logical Channel <NUM>). Here, the first RLC entity <NUM> is mapped to normal data and the second RLC entity <NUM> is mapped to high urgency data. In the depicted embodiment, each RLC entity <NUM>, <NUM> is mapped to the same MAC entity <NUM>.

According to a sixth solution for efficient uplink preemption, in the UE <NUM> one PDCP entity (e.g., the PDCP entity <NUM>) may be mapped to multiple RLC entities/Logical channels in order to support packets of different priority/urgency level within one radio bearer or QoS flow. For example, an IIoT traffic flow may support critical packets, e.g. emergency stop packets, within a radio bearer or a QoS flow. Those critical packets are to be prioritized over other packets within the same radio bearer or the QoS flow. The PDCP entity in the UE receives the SDUs with a marking indicating if a particular SDU is considered critical/high urgency. Such packet marking may be done by a higher layer such as application layer or IP layer. The PDCP PDU containing such SDU will be submitted to another RLC entity (RLC entity other than the one used for "normal" packets) handling such critical packets. If there are different levels of criticalness/urgency level then the PDCP PDU containing such SDU will be submitted to RLC entities handling the corresponding criticality/urgency level, e.g., one RLC entity/LCH supports one urgency level.

In order to enable efficient scheduling of uplink transmissions by having a closer match of uplink transmission parameters (including numerology, PUSCH transmission duration, MCS, etc.) for the PUSCH transmission to logical channel (LCH) requirements, an NR system may support an early indication to the gNB of the type of traffic on the logical channel(s) triggering the SR, through the use of multiple, single-bit SR configurations. An SR configuration may consist of a set of PUCCH resources for SR across different Bandwidth Parts (BWP) and serving cells. According to one implementation of the sixth solution, each LCH of a bearer supporting packets of different priority/urgency level (e.g., of a radio bearer having more than one associated LCHs/RLC entities) may be mapped to zero or one SR configuration. In other words, a radio bearer mapped to multiple LCHs may be mapped to more than one SR configuration. Each SR configuration indicates to the gNB the type of traffic on the logical channel(s) triggering the SR, i.e. certain priority/urgency level of the data.

<FIG> depicts a user equipment apparatus <NUM> that may be used operation for uplink preemption, according to embodiments of the disclosure. The user equipment apparatus <NUM> may be one embodiment of the remote unit <NUM> or UE, described above. Furthermore, the user equipment apparatus <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, an output device <NUM>, and a transceiver <NUM>. In some embodiments, the input device <NUM> and the output device <NUM> are combined into a single device, such as a touchscreen. In certain embodiments, the user equipment apparatus <NUM> may not include any input device <NUM> and/or output device <NUM>. In various embodiments, the user equipment apparatus <NUM> may include one or more of: the processor <NUM>, the memory <NUM>, and the transceiver <NUM>, and may not include the input device <NUM> and/or the output device <NUM>.

In various embodiments, the user equipment apparatus <NUM> receives (e.g., via the transceiver <NUM>) a first allocation of uplink resources in a mobile communication network and receives a second allocation of uplink resources in the mobile communication network. Here, the second allocation at least partially overlaps in time with the first allocation and the second allocation is received at a later time than the first allocation.

The processor <NUM> determines whether the second allocation is associated with higher priority traffic than the first allocation and preempts the first allocation to generate a TB according to the second allocation in response to the second allocation being associated with higher priority traffic than the first allocation.

In some embodiments, the second allocation is indicated using DCI, wherein the DCI includes a parameter indicating that the second allocation is a high priority allocation. Here, the first allocation may be a dynamic grant indicated using DCI or may be a configured grant. In certain embodiments, the parameter indicating a high priority allocation may be a particular RNTI. In certain embodiments, the parameter indicating a high priority allocation may be an SRS request field that is set to a predefined value. In certain embodiments, the parameter indicating a high priority allocation may be an UL-SCH indicator field that is set to a first predetermined value in conjunction with a CSI request field that is set to a second predetermined value.

In some embodiments, the processor <NUM> defers processing of the first allocation until a predetermined time before a transmission occasion corresponding to the uplink resources of the first allocation.

In some embodiments, preempting the first allocation to generate the TB according to the second allocation includes the processor <NUM> interrupting generation of a first TB corresponding to the first allocation to generate a second TB corresponding to the second allocation and resuming generation of the first TB in response to completing generation of the second TB.

In some embodiments, preempting the first allocation to generate the TB according to the second allocation includes the processor <NUM> determining whether the first allocation corresponds to an initial transmission of data or a retransmission of data, generating a retransmission TB according to the first allocation in response to the first allocation corresponding to a retransmission of data, and delivering the retransmission TB to a transmit buffer.

In one embodiment, preempting the first allocation to generate the TB according to the second allocation further includes the processor <NUM> ignoring the first allocation in response to the first allocation corresponding to an initial transmission of data. In certain embodiments, the retransmission TB and a TB corresponding to the second allocation belong to different HARQ processes. In certain embodiments, the first allocation is indicated using first DCI, and wherein determining whether the first allocation corresponds to an initial transmission of data or a retransmission of data includes examining an NDI field of the first DCI.

In some embodiments, the memory <NUM> stores data related to preempting an uplink resource allocation. For example, the memory <NUM> may store data relating to configured grants, dynamic grants, priorities, and the like. In certain embodiments, the memory <NUM> also stores program code and related data, such as an operating system or other controller algorithms operating on the user equipment apparatus <NUM>.

The transceiver <NUM> communicates with one or more network functions of a mobile communication network via one or more access networks. The transceiver <NUM> operates under the control of the processor <NUM> to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor <NUM> may selectively activate the transceiver (or portions thereof) at particular times in order to send and receive messages.

The transceiver <NUM> may include one or more transmitters <NUM> and one or more receivers <NUM>. Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the user equipment apparatus <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>. Further, the transmitter(s) <NUM> and the receiver(s) <NUM> may be any suitable type of transmitters and receivers. In one embodiment, the transceiver <NUM> includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.

In various embodiments, one or more transmitters <NUM> and/or one or more receivers <NUM> may be implemented and/or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an ASIC, or other type of hardware component. In certain embodiments, one or more transmitters <NUM> and/or one or more receivers <NUM> may be implemented and/or integrated into a multi-chip module. In some embodiments, other components such as the network interface <NUM> or other hardware components/circuits may be integrated with any number of transmitters <NUM> and/or receivers <NUM> into a single chip. In such embodiment, the transmitters <NUM> and receivers <NUM> may be logically configured as a transceiver <NUM> that uses one more common control signals or as modular transmitters <NUM> and receivers <NUM> implemented in the same hardware chip or in a multi-chip module.

<FIG> depicts a method <NUM> for supporting edge data network discovery, according to embodiments of the disclosure. In some embodiments, the method <NUM> is performed by a UE, such as the remote unit <NUM>, the UE <NUM>, and/or the user equipment apparatus <NUM>. In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> begins and receives <NUM> a first allocation of uplink resources in a mobile communication network. The method <NUM> includes receiving <NUM> a second allocation of uplink resources. Here, the second allocation at least partially overlaps in time with the first allocation and the second allocation is received at a later time than the first allocation.

The method <NUM> includes determining <NUM> whether the second allocation is associated with higher priority traffic than the first allocation. The method <NUM> includes preempting <NUM> the first allocation to generate a TB according to the second allocation in response to the second allocation being associated with higher priority traffic than the first allocation. The method <NUM> ends.

Disclosed herein is a first apparatus for preempting an uplink resource allocation, according to embodiments of the disclosure. The first apparatus may be implemented by a UE, such as the remote unit <NUM>, the UE <NUM>, and/or the user equipment apparatus <NUM>. The first apparatus includes a processor and a transceiver that receives a first allocation of uplink resources in a mobile communication network and receives a second allocation of uplink resources. Here, the second allocation is received at a later time than the first allocation, wherein the second allocation at least partially overlaps in time with the first allocation. The processor determines whether the second allocation is associated with higher priority traffic than the first allocation and preempts the first allocation to generate a TB according to the second allocation in response to the second allocation being associated with higher priority traffic than the first allocation.

According to the invention, the second allocation is indicated using DCI, wherein the DCI includes a parameter indicating that the second allocation is a high priority allocation. In such certain, the parameter indicating that the second allocation is a high priority allocation may be a particular RNTI. In certain embodiments, the parameter indicating that the second allocation is a high priority allocation may be an SRS request field that is set to a predefined value. In certain embodiments, the parameter indicating that the second allocation is a high priority allocation may be an UL-SCH indicator field that is set to a first predetermined value in conjunction with a CSI request field that is set to a second predetermined value.

In some embodiments, the processor defers processing of the first allocation until a predetermined time before a transmission occasion corresponding to the uplink resources of the first allocation.

In some embodiments, preempting the first allocation to generate the TB according to the second allocation includes the processor interrupting generation of a first TB corresponding to the first allocation to generate a second TB corresponding to the second allocation and resuming generation of the first TB in response to completing generation of the second TB.

In some embodiments, preempting the first allocation to generate the TB according to the second allocation includes the processor determining whether the first allocation corresponds to an initial transmission of data or a retransmission of data, generating a retransmission TB according to the first allocation in response to the first allocation corresponding to a retransmission of data, and delivering the retransmission TB to a transmit buffer.

In one embodiment, preempting the first allocation to generate the TB according to the second allocation further includes ignoring the first allocation in response to the first allocation corresponding to an initial transmission of data. In certain embodiments, the retransmission TB and the TB corresponding to the second allocation belong to different HARQ processes. In certain embodiments, the first allocation is indicated using first DCI, and wherein determining whether the first allocation corresponds to an initial transmission of data or a retransmission of data includes examining an NDI field of the first DCI.

Disclosed herein is a first method for preempting an uplink resource allocation, according to embodiments of the disclosure. The first method may be performed by a UE, such as the remote unit <NUM>, the UE <NUM>, and/or the user equipment apparatus <NUM>. The first method includes receiving a first allocation of uplink resources in a mobile communication network and receiving a second allocation of uplink resources. Here, the second allocation at least partially overlaps in time with the first allocation and the second allocation is received at a later time than the first allocation. The first method includes determining whether the second allocation is associated with higher priority traffic than the first allocation and preempting the first allocation to generate a TB according to the second allocation in response to the second allocation being associated with higher priority traffic than the first allocation.

In some embodiments, the second allocation is indicated using a DCI, wherein the DCI includes a parameter indicating that the second allocation is a high priority allocation. Here, the first allocation may be a dynamic grant indicated using DCI or may be a configured grant. In certain embodiments, the parameter indicating that the second allocation is a high priority allocation may include a particular Radio RNTI. In certain embodiments, the parameter indicating that the second allocation is a high priority allocation may include an SRS request field that is set to a predefined value. In certain embodiments the parameter indicating that the second allocation is a high priority allocation may include an UL-SCH indicator field that is set to a first predetermined value in conjunction with a CSI request field that is set to a second predetermined value.

In some embodiments, the first method includes deferring processing of the first allocation until a predetermined time before a transmission occasion corresponding to the uplink resources of the first allocation.

In some embodiments, preempting the first allocation to generate the TB according to the second allocation includes interrupting generation of a first TB corresponding to the first allocation to generate a second TB corresponding to the second allocation and resuming generation of the first TB in response to completing generation of the second TB.

In some embodiments, preempting the first allocation to generate the TB according to the second allocation includes: determining whether the first allocation corresponds to an initial transmission of data or a retransmission of data, generating a retransmission TB according to the first allocation in response to the first allocation corresponding to a retransmission of data, and delivering the retransmission TB to a transmit buffer.

In such embodiments, preempting the first allocation to generate the TB according to the second allocation further includes ignoring the first allocation in response to the first allocation corresponding to an initial transmission of data. In certain embodiments, the retransmission TB and the TB corresponding to the second allocation belong to different HARQ processes. In certain embodiments, the first allocation is indicated using first DCI, and wherein determining whether the first allocation corresponds to an initial transmission of data or a retransmission of data includes examining an NDI field of the first DCI.

Claim 1:
A method (<NUM>) performed by a user equipment, the method (<NUM>) comprising:
receiving (<NUM>) a first allocation of uplink resources in a mobile communication network, wherein the first allocation comprises a configured grant;
receiving (<NUM>) a second allocation of uplink resources, wherein the uplink resources of the second allocation at least partially overlap in time with the uplink resources of the first allocation, wherein the second allocation is indicated using downlink control information, wherein the downlink control information includes a parameter indicating that the second allocation is a high priority allocation, wherein the second allocation is received at a later time than the first allocation;
determining (<NUM>) whether the second allocation is associated with higher priority traffic than the first allocation, such that the second allocation preempts the first allocation; and
generating (<NUM>) a transmission block, TB, according to the second allocation in response to the second allocation being associated with higher priority traffic than the first allocation.