Patent Description:
Third Generation Partnership Project (3GPP) technology called New Radio (NR), also called Fifth Generation (<NUM>), is being designed to support a wide range of data services including mobile broadband (MBB) and ultra-reliable low latency communications (URLLC). To enable optimized services, the transmission durations are expected to be different for different services, where URLLC may have a shorter transmission duration compared to MBB, to minimize latency in URLLC. Dynamic multiplexing of different services is highly desirable for efficient use of system resources and to achieve maximize capacity. However, it may occur that MBB data is transmitted at a time when a URLLC data packet arrives at the transmitter. It may therefore be desirable to interrupt the MBB transmission in certain time-frequency resources and perform a URLLC transmission on those resources instead. This method is sometimes called pre-emption or cancellation. Techniques to support pre-emption/cancellation are currently being considered.

Prior art patent aplication <CIT> discloses a method by a base station comprising determining a type of service associated with a UE. The method further comprises determining whether the UE belongs to a first group of UEs or a second group of UEs, based on the type of service associated with the UE. Further, the method comprises, when the UE is determined to belong to the first group of UEs, allocating resources on the PUCCH to the UE in a first section of PUCCH resources. When the UE is determined to belong to the second group of UEs, allocating resources on the PUCCH to the UE in a second section of PUCCH resources. Moreover, the determining of whether a UE should belong to, or be associated to, a first or a second group of UEs may further be based on the "geometry" or location of the UE, e.g. the location within a cell associated with the base station with regard to the distance from the base station and also with regard to e.g. the distance to the neighboring cells/base stations.

Some embodiments advantageously provide methods and network nodes for assigning of resources based on grouping of wireless devices.

According to one aspect of the present disclosure, a network node configured to communicate with a wireless device, WD, is provided. The network node includes processing circuitry. The processing circuitry is configured to cause the network node to assign the wireless device to a group with other wireless devices based at least in part on a service type of the wireless device and based at least in part on at least one of: a preemption indication monitoring capability of the wireless device; a power control capability of the wireless device; and a spatial separateness of the wireless device with respect to at least one of the other wireless devices; and assign at least one resource to the wireless device according to the group to which the wireless device is assigned.

The preemption indication monitoring capability of the wireless device corresponds to whether the wireless device is capable of monitoring for an inter-WD uplink preemption indication message from the network node. The power control capability of the wireless device corresponds to whether the wireless device is capable of an enhanced dynamic uplink, UL, power control boost. The spatial separateness of the wireless device corresponds to whether the wireless device can be scheduled on a same time-frequency resource as the at least one of the other wireless devices based at least in part on the spatial separateness of the wireless device with respect to the at least one of the other wireless devices.

In some embodiments of this aspect, the group to which the wireless device is assigned is one of: a first group of wireless devices having different service types and being assigned a same first bandwidth part; and a second group of wireless devices having a same service type and being assigned a same second bandwidth part. In some embodiments of this aspect, the processing circuitry is further configured to cause the network node to assign the at least one resource to the wireless device by being configured to cause the network node to assign the first bandwidth part to the wireless device if the wireless device has the preemption indication monitoring capability and is of a first service type and assign the second bandwidth part to the wireless device if the wireless device does not have the preemption indication monitoring capability and is of the first service type.

In some embodiments of this aspect, the group to which the wireless device is assigned is one of: a first group of wireless devices having different service types and being assigned a same first bandwidth part; and a second group of wireless devices having different service types and being assigned a same second bandwidth part. In some embodiments of this aspect, the processing circuitry is further configured to cause the network node to assign the at least one resource to the wireless device by being configured to cause the network node to assign the first bandwidth part to the wireless device if the wireless device is power limited and is of a first service type and assign the second bandwidth part to the wireless device if the wireless device is not power limited and is of the first service type. In some embodiments of this aspect, the wireless device being power limited corresponds to one of: the wireless device lacking the power control capability; and the wireless device having the power control capability and using a maximum transmit power level; and the wireless device being not power limited corresponds to: the wireless device having the power control capability and the wireless device having sufficient power to increase transmit power without exceeding the maximum transmit power level.

In some embodiments of this aspect, the processing circuitry is further configured to cause the network node to assign the at least one resource to the wireless device by being configured to cause the network node to assign a same frequency resource to a first wireless device of a first service type and to a second wireless device of a second service type if the first wireless device and the second wireless device are spatially separable. In some embodiments of this aspect, the processing circuitry is further configured to cause the network node to assign the at least one resource to the wireless device by being configured to cause the network node to assign the wireless device to uplink on a carrier associated with an aggressor wireless device if the wireless device has the preemption indication monitoring capability.

In some embodiments of this aspect, the processing circuitry is configured to cause the network node to avoid scheduling of wireless devices that are not capable of the preemption indication monitoring in a bandwidth part when other wireless devices that are capable of preemption indication monitoring are scheduled in the bandwidth part. In some embodiments of this aspect, the processing circuitry is configured to cause the network node to allow coexistence of first and second service types in a same bandwidth part if wireless devices with the first service type that are scheduled in the bandwidth part are capable of the preemption indication monitoring. In some embodiments of this aspect, the processing circuitry is configured to cause the network node to partition a bandwidth part in at least one of frequency and time to allocate a first part of the bandwidth part for wireless devices having a same service type and to allocate a second part of the bandwidth part for wireless devices having different service types.

In some embodiments of this aspect, the service type of the wireless device corresponds to one of enhanced mobile broadband, eMBB, and ultra-reliable low latency communications, URLLC. In some embodiments of this aspect, the processing circuitry is further configured to cause the network node to assign the wireless device to a group with other wireless devices by being configured to cause the network node to assign the wireless device to a first group of wireless devices being assigned to a first bandwidth part if the wireless device at least one of corresponds to the URLLC service type and has the preemption indication monitoring capability; and assign the wireless device to a second group of wireless devices being assigned to a second bandwidth part if the wireless device corresponds to the eMBB service type and does not have the preemption indication monitoring capability.

In some embodiments of this aspect, the processing circuitry is further configured to cause the network node to assign the wireless device to a group with other wireless devices by being configured to cause the network node to assign the wireless device to a first group of wireless devices being assigned to a first bandwidth part if the wireless device at least one of: is power limited and is of the URLLC service type; and has the preemption indication monitoring capability and is of the eMBB service type; and assign the wireless device to a second group of wireless devices being assigned to a second bandwidth part if the wireless device at least one of: is not power limited and is of the URLLC service type; and does not have the preemption indication monitoring capability and is of the eMBB service type.

According to another aspect of the present disclosure, a method implemented in a network node configured to communicate with a wireless device, WD, is provided. The method includes assigning the wireless device to a group with other wireless devices based at least in part on a service type of the wireless device and based at least in part on at least one of: a preemption indication monitoring capability of the wireless device; a power control capability of the wireless device; and a spatial separateness of the wireless device with respect to at least one of the other wireless devices; and assigning at least one resource to the wireless device according to the group to which the wireless device is assigned.

In some embodiments of this aspect, the group to which the wireless device is assigned is one of: a first group of wireless devices having different service types and being assigned a same first bandwidth part; and a second group of wireless devices having a same service type and being assigned a same second bandwidth part. In some embodiments of this aspect, assigning the at least one resource to the wireless device further includes assigning the first bandwidth part to the wireless device if the wireless device has the preemption indication monitoring capability and is of a first service type and assign the second bandwidth part to the wireless device if the wireless device does not have the preemption indication monitoring capability and is of the first service type.

In some embodiments of this aspect, the group to which the wireless device is assigned is one of: a first group of wireless devices having different service types and being assigned a same first bandwidth part; and a second group of wireless devices having different service types and being assigned a same second bandwidth part. In some embodiments of this aspect, assigning the at least one resource to the wireless device further includes assigning the first bandwidth part to the wireless device if the wireless device is power limited and is of a first service type and assign the second bandwidth part to the wireless device if the wireless device is not power limited and is of the first service type.

In some embodiments of this aspect, the wireless device being power limited corresponds to one of: the wireless device lacking the power control capability; and the wireless device having the power control capability and using a maximum transmit power level. In some embodiments of this aspect, the wireless device being not power limited corresponds to the wireless device having the power control capability and the wireless device having sufficient power to increase transmit power without exceeding the maximum transmit power level. In some embodiments of this aspect, assigning the at least one resource to the wireless device further includes assigning a same frequency resource to a first wireless device of a first service type and to a second wireless device of a second service type if the first wireless device and the second wireless device are spatially separable.

In some embodiments of this aspect, assigning the at least one resource to the wireless device further includes assigning the wireless device to uplink on a carrier associated with an aggressor wireless device if the wireless device has the preemption indication monitoring capability. In some embodiments of this aspect, the method further includes avoiding scheduling of wireless devices that are not capable of the preemption indication monitoring in a bandwidth part when other wireless devices that are capable of preemption indication monitoring are scheduled in the bandwidth part. In some embodiments of this aspect, the method further includes allowing coexistence of first and second service types in a same bandwidth part if wireless devices with the first service type that are scheduled in the bandwidth part are capable of the preemption indication monitoring.

In some embodiments of this aspect, the method further includes partitioning a bandwidth part in at least one of frequency and time to allocate a first part of the bandwidth part for wireless devices having a same service type and to allocate a second part of the bandwidth part for wireless devices having different service types. In some embodiments of this aspect, the service type of the wireless device corresponds to one of enhanced mobile broadband, eMBB, and ultra-reliable low latency communications, URLLC.

In some embodiments of this aspect, assigning the wireless device to a group with other wireless devices further includes assigning the wireless device to a first group of wireless devices being assigned to a first bandwidth part if the wireless device at least one of corresponds to the URLLC service type and has the preemption indication monitoring capability; and assigning the wireless device to a second group of wireless devices being assigned to a second bandwidth part if the wireless device corresponds to the eMBB service type and does not have the preemption indication monitoring capability.

In some embodiments of this aspect, assigning the wireless device to a group with other wireless devices further includes assigning the wireless device to a first group of wireless devices being assigned to a first bandwidth part if the wireless device at least one of: is power limited and is of the URLLC service type; and has the preemption indication monitoring capability and is of the eMBB service type; and assigning the wireless device to a second group of wireless devices being assigned to a second bandwidth part if the wireless device at least one of: is not power limited and is of the URLLC service type; and does not have the preemption indication monitoring capability and is of the eMBB service type.

Inter-wireless device (WD) pre-emption/interruption/cancellation for downlink (DL) (i.e., for transmission from a base station to a WD) was standardized in Release <NUM> of the 3GPP wireless communication standards. Downlink pre-emption is supported where the assigned downlink resource is pre-empted by another downlink transmission (e.g., from URLLC). In this case, according to one option, an indication carried in the downlink control information (DCI) message, format 2_1, is dynamically signaled to the WD to inform the WD of the time and frequency region within its assigned resource that is pre-empted. This increases the likelihood of successful demodulation and decoding of the transport block(s) transmitted within the assigned resource. In addition, one bit named by Code Block Group (CBG) Flushing Out Information (CBGFI) in the DCI message for retransmission can be used to flush the hybrid automatic repeat request (HARQ) buffer that contains the pre-empting information.

Inter-WD pre-emption/interruption/cancellation for uplink (UL) transmission has been identified as an area that may need to be addressed to achieve the objectives for URLLC use cases. At least some of the discussion for 3GPP Release <NUM> has centered around two main alternatives: the pre-emption/cancellation indication based solutions (PI-based) and power control-based solutions (PC-based). A list of agreements made at previous meetings can be found at the end of this disclosure. However, design details have not been determined and are under discussion.

In short, a PC-based solution can be used to interrupt/"transmit over" legacy WDs which may not have special capabilities, but an aggressor WD may be in better radio conditions or have enough of a power budget to increase power. A PI-based solution does not set additional requirements on the aggressor WD, but the victim WD may be able to decode/receive a PI, which may require certain capabilities.

In the downlink, some WDs may not support monitoring of DCI format 2_1 because they may not have certain capabilities. In this case the WD performance might be negatively affected if interruption/cancellation takes place. The scheduler may try to avoid the interruption of such WDs, but the scheduling flexibility can suffer.

In the uplink, since a PI-based scheme may require the WD to be capable of PI reception and PC-based reception may work in some conditions, there may again be limitations on scheduling flexibility, which could lead to either blocking of URLLC transmissions or to operation at higher block error rates (BLER) than is required for URLLC.

Some embodiments include enhancements to radio resource management (RRM) and scheduling procedures by resource allocation to WDs having different cancellation/interruption/pre-emption-related capabilities on different bandwidth parts (BWPs) or on logical partitions of one BWP. Some embodiments facilitate URLLC reliability and latency requirements are met and decrease harmful impact on evolved MBB (eMBB) traffic in case eMBB and URLLC service type traffic co-exist in one cell.

Some embodiments include methods and algorithms for scheduling and radio resource management and can be divided into at least two different approaches. One approach is for the downlink and another approach is for the uplink. In both cases, it may be assumed that at least two different traffic service types have different reliability, latency or other quality of service (QoS) requirements.

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to assigning of resources based on grouping of wireless devices. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

The term "network node" used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term "radio node" used herein may be used to also denote a wireless device (WD) or a radio network node.

It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

In some embodiments, the "service type of a WD" may be considered different traffic service types having different reliability, latency and/or other QoS requirements, such as, for example URLLC service type and eMBB service type.

In some embodiments, a WD may be assigned to a group based on the service type of the WD and further based at least in part on one or more other WD factors, parameters, conditions and/or capabilities (e.g., preemption indication monitoring capability of the WD, power control capability of the WD and/or spatial separateness of the WD with respect to other WDs), as discussed in more detail below.

In some embodiments, assigning a WD to a group based at least in part on a "spatial separateness of a WD" may be considered assigning a WD to a group based at least in part on a WD property and/or condition and/or location and/or parameter(s) that indicate whether the wireless device can be scheduled on a same time-frequency resource as other wireless devices in the group due to the spatial separateness of the wireless device with respect to the other wireless devices, as with MU-MIMO technology. For example, the WD may be assigned to a group based on that the WD can be allocated a same time-frequency resource as at least one other WD in the group, but using a different antenna port/MIMO layer than the antenna port/MIMO layer of such at least one other WD.

In some embodiments, the wireless device being "power limited" means that the wireless device either lacks the power control capability or the wireless device has the power control capability but is using a maximum transmit power level (e.g., and therefore does not have enough in its power budget to boost transmit power to e.g., implement the PC-based interruption solution).

In some embodiments, the wireless device being "not power limited" means that the wireless device has the power control capability and the wireless device has sufficient power budget to increase its transmit power (e.g., to implement the PC-based interruption solution, without exceeding the maximum transmit power level allotted for the WD).

In some embodiments, the terms "aggressor WD" and "potential aggressor WD" are used interchangeably and may be used to indicate a WD whose transmission (e.g., DL or UL transmission) can pre-empt/interrupt/cancel a transmission of another WD (e.g., victim WD in this scenario) according to one or more of the techniques disclosed herein. It should be understood that a WD may be an aggressor WD in one scenario while being a victim WD in another scenario.

In some embodiments, the terms "pre-empt/pre-emption", "interrupt/interruption" and "cancel/cancellation" are used interchangeably.

In some embodiments, the terms "enhanced dynamic uplink power control boost" and "power control capability" may be used interchangeably and may be a power control-based (PC-based) pre-emption capability that implies a power boost of a URLLC transmission in a scheduling DCI while eMBB transmission continues as is. This is a backward compatible solution for Release <NUM> (Rel-<NUM>) eMBB WDs. Given that the PC-based pre-emption is a backward compatible scheme, Release <NUM> (Rel-<NUM>) capability may be used (so called "an enhanced dynamic uplink power control") for the URLLC WD while no special capability may be required for an overpowered eMBB WD. New capability may include:.

Some embodiments include a method and a network node for assigning of resources based on grouping of wireless devices. According to one aspect, a network node has processing circuitry configured to perform method steps including assigning the WD to a group with other WDs <NUM> based at least in part on a service type of the WD. Service types may include eMBB and URLLC, for example. The assigning to a group is also based at least in part on one or more of: a preemption indication monitoring capability of the WD; a power control capability of the WD; or a spatial separateness of the WD. The processing circuitry is also configured to assign resources to the WD according to the group to which the WD is assigned.

Referring now to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in <FIG> a schematic diagram of a communication system <NUM>, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (<NUM>), which comprises an access network <NUM>, such as a radio access network, and a core network <NUM>. The access network <NUM> comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes <NUM>), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas <NUM>). Each network node 16a, 16b, 16c is connectable to the core network <NUM> over a wired or wireless connection <NUM>. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices <NUM>) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node <NUM>. Note that although only two WDs <NUM> and three network nodes <NUM> are shown for convenience, the communication system may include many more WDs <NUM> and network nodes <NUM>.

A network node <NUM> is configured to include a group assignment unit <NUM> which is configured to assign the wireless device <NUM> to a group with other wireless devices <NUM> based at least in part on a service type of the wireless device <NUM> and based at least in part on at least one of: a preemption indication monitoring capability of the wireless device <NUM>; a power control capability of the wireless device <NUM>; and a spatial separateness of the wireless device <NUM> with respect to at least one of the other wireless devices <NUM>; and assign at least one resource to the wireless device <NUM> according to the group to which the wireless device <NUM> is assigned.

In some embodiments, network node <NUM> includes a group assignment unit <NUM> which is configured to assign the WD <NUM> to a group with other WDs <NUM> based at least in part on one of a service type of the WD <NUM> and based at least in part on one or more of: a preemption indication monitoring capability of the WD <NUM>, a power control capability of the WD <NUM>; or a spatial separateness of the WD <NUM>.

The host application <NUM> may be operable to provide a service to a remote user, such as a WD <NUM> connecting via an OTT connection <NUM> terminating at the WD <NUM> and the host computer <NUM>. The "user data" may be data and information described herein as implementing the described functionality. In one embodiment, the host computer <NUM> may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry <NUM> of the host computer <NUM> may enable the host computer <NUM> to observe, monitor, control, transmit to and/or receive from the network node <NUM> and or the wireless device <NUM>.

Thus, the network node <NUM> further has software <NUM> stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node <NUM> via an external connection. The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node <NUM>. Processor <NUM> corresponds to one or more processors <NUM> for performing network node <NUM> functions described herein. The memory <NUM> is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to network node <NUM>. For example, processing circuitry <NUM> of the network node <NUM> may include group assignment unit <NUM> configured to assign the WD to a group with other WDs <NUM> based at least in part on one of a service type of the WD and based at least in part on one or more of: a preemption indication monitoring capability of the WD, a power control capability of the WD; or a spatial separateness of the WD.

The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD <NUM>. The processor <NUM> corresponds to one or more processors <NUM> for performing WD <NUM> functions described herein. The WD <NUM> includes memory <NUM> that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> and/or the client application <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to WD <NUM>.

Although <FIG> and <FIG> show various "units" such as group assignment unit <NUM> as being within a processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG> and <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG>. In a first step of the method, the host computer <NUM> provides user data (Block S <NUM>). In an optional substep of the first step, the host computer <NUM> provides the user data by executing a host application, such as, for example, the host application <NUM> (Block S102). In a second step, the host computer <NUM> initiates a transmission carrying the user data to the WD <NUM> (Block S104). In an optional third step, the network node <NUM> transmits to the WD <NUM> the user data which was carried in the transmission that the host computer <NUM> initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block S106). In an optional fourth step, the WD <NUM> executes a client application, such as, for example, the client application <NUM>, associated with the host application <NUM> executed by the host computer <NUM> (Block S108).

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG> and <FIG>. In a first step of the method, the host computer <NUM> provides user data (Block S110). In an optional substep (not shown) the host computer <NUM> provides the user data by executing a host application, such as, for example, the host application <NUM>. In a second step, the host computer <NUM> initiates a transmission carrying the user data to the WD <NUM> (Block S112). In an optional third step, the WD <NUM> receives the user data carried in the transmission (Block S114).

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG> and <FIG>. In an optional first step of the method, the WD <NUM> receives input data provided by the host computer <NUM> (Block S116). In an optional substep of the first step, the WD <NUM> executes the client application <NUM>, which provides the user data in reaction to the received input data provided by the host computer <NUM> (Block S118). Additionally or alternatively, in an optional second step, the WD <NUM> provides user data (Block S120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application <NUM> (Block S122). In providing the user data, the executed client application <NUM> may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD <NUM> may initiate, in an optional third substep, transmission of the user data to the host computer <NUM> (Block S124). In a fourth step of the method, the host computer <NUM> receives the user data transmitted from the WD <NUM>, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

<FIG> is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of <FIG>, in accordance with one embodiment. The communication system may include a host computer <NUM>, a network node <NUM> and a WD <NUM>, which may be those described with reference to <FIG> and <FIG>. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node <NUM> receives user data from the WD <NUM> (Block S128). In an optional second step, the network node <NUM> initiates transmission of the received user data to the host computer <NUM> (Block S130). In a third step, the host computer <NUM> receives the user data carried in the transmission initiated by the network node <NUM> (Block S132).

<FIG> is a flowchart of an exemplary process in a network node for assigning of resources based on grouping of wireless devices according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node <NUM> such as by one or more of processing circuitry <NUM> (including the group assignment unit <NUM>), processor <NUM>, radio interface <NUM> and/or communication interface <NUM>. Network node <NUM> such as via processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is configured to (Block S <NUM>) assign the wireless device <NUM> to a group with other wireless devices <NUM> based at least in part on a service type of the wireless device <NUM> and based at least in part on at least one of: a preemption indication monitoring capability of the wireless device <NUM>; a power control capability of the wireless device <NUM>; and a spatial separateness of the wireless device <NUM> with respect to at least one of the other wireless devices <NUM>. Network node <NUM>, such as via processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM>, is configured to (Block S136) assign at least one resource to the wireless device <NUM> according to the group to which the wireless device <NUM> is assigned.

In some embodiments, the preemption indication monitoring capability of the wireless device <NUM> corresponds to whether the wireless device <NUM> is capable of monitoring for an inter-WD uplink preemption indication message from the network node <NUM>. In some embodiments, the power control capability of the wireless device <NUM> corresponds to whether the wireless device <NUM> is capable of an enhanced dynamic uplink, UL, power control boost. In some embodiments, the spatial separateness of the wireless device <NUM> corresponds to whether the wireless device <NUM> can be scheduled on a same time-frequency resource as the at least one of the other wireless devices <NUM> based at least in part on the spatial separateness of the wireless device <NUM> with respect to the at least one of the other wireless devices <NUM>. In some embodiments, the spatial separateness of the wireless device <NUM> corresponds to whether the wireless device <NUM> can be scheduled on a same time-frequency resource, but different antenna port/MIMO layer, as the at least one of the other wireless devices <NUM> based at least in part on the spatial separateness of the wireless device <NUM> with respect to the at least one of the other wireless devices <NUM>.

In some embodiments, the group to which the wireless device <NUM> is assigned is one of: a first group of wireless devices <NUM> having different service types and being assigned a same first bandwidth part; and a second group of wireless devices <NUM> having a same service type and being assigned a same second bandwidth part. In some embodiments, the processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is further configured to cause the network node <NUM> to assign the at least one resource to the wireless device <NUM> by being configured to cause the network node to: assign the first bandwidth part to the wireless device <NUM> if the wireless device <NUM> has the preemption indication monitoring capability and is of a first service type and assign the second bandwidth part to the wireless device <NUM> if the wireless device <NUM> does not have the preemption indication monitoring capability and is of the first service type.

In some embodiments, the group to which the wireless device <NUM> is assigned is one of: a first group of wireless devices <NUM> having different service types and being assigned a same first bandwidth part; and a second group of wireless devices <NUM> having different service types and being assigned a same second bandwidth part. In some embodiments, the processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is further configured to cause the network node <NUM> to assign the at least one resource to the wireless device <NUM> by being configured to cause the network node to: assign the first bandwidth part to the wireless device <NUM> if the wireless device <NUM> is power limited and is of a first service type and assign the second bandwidth part to the wireless device <NUM> if the wireless device <NUM> is not power limited and is of the first service type.

In some embodiments, the wireless device <NUM> being power limited corresponds to one of: the wireless device <NUM> lacking the power control capability; and the wireless device <NUM> having the power control capability and using a maximum transmit power level. In some embodiments, the wireless device <NUM> being not power limited corresponds to: the wireless device <NUM> having the power control capability and the wireless device <NUM> having sufficient power to increase transmit power without exceeding the maximum transmit power level.

In some embodiments, the processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is further configured to cause the network node <NUM> to assign the at least one resource to the wireless device <NUM> by being configured to cause the network node to assign a same frequency resource to a first wireless device <NUM> of a first service type and to a second wireless device <NUM> of a second service type if the first wireless device <NUM> and the second wireless device <NUM> are spatially separable. In some embodiments, the processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is further configured to cause the network node <NUM> to assign the at least one resource to the wireless device <NUM> by being configured to cause the network node <NUM> to: assign the wireless device <NUM> to uplink on a carrier associated with an aggressor wireless device <NUM> if the wireless device <NUM> has the preemption indication monitoring capability.

In some embodiments, the processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is configured to cause the network node <NUM> to avoid scheduling of wireless devices <NUM> that are not capable of the preemption indication monitoring in a bandwidth part when other wireless devices <NUM> that are capable of preemption indication monitoring are scheduled in the bandwidth part. In some embodiments, the processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is configured to cause the network node <NUM> to allow coexistence of first and second service types in a same bandwidth part if wireless devices <NUM> with the first service type that are scheduled in the bandwidth part are capable of the preemption indication monitoring.

In some embodiments, the processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is configured to cause the network node <NUM> to partition a bandwidth part in at least one of frequency and time to allocate a first part of the bandwidth part for wireless devices <NUM> having a same service type and to allocate a second part of the bandwidth part for wireless devices <NUM> having different service types. In some embodiments, the service type of the wireless device <NUM> corresponds to one of enhanced mobile broadband, eMBB, and ultra-reliable low latency communications, URLLC.

In some embodiments, the processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is further configured to cause the network node <NUM> to assign the wireless device <NUM> to a group with other wireless devices <NUM> by being configured to cause the network node <NUM> to: assign the wireless device <NUM> to a first group of wireless devices <NUM> being assigned to a first bandwidth part if the wireless device <NUM> at least one of corresponds to the URLLC service type and has the preemption indication monitoring capability; and assign the wireless device <NUM> to a second group of wireless devices <NUM> being assigned to a second bandwidth part if the wireless device <NUM> corresponds to the eMBB service type and does not have the preemption indication monitoring capability.

In some embodiments, the processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is further configured to cause the network node <NUM> to assign the wireless device <NUM> to a group with other wireless devices <NUM> by being configured to cause the network node <NUM> to: assign the wireless device <NUM> to a first group of wireless devices <NUM> being assigned to a first bandwidth part if the wireless device <NUM> at least one of: is power limited and is of the URLLC service type; and has the preemption indication monitoring capability and is of the eMBB service type; and assign the wireless device <NUM> to a second group of wireless devices <NUM> being assigned to a second bandwidth part if the wireless device <NUM> at least one of: is not power limited and is of the URLLC service type; and does not have the preemption indication monitoring capability and is of the eMBB service type.

In some embodiments, network node <NUM> such as via processing circuitry <NUM> and/or processor <NUM> and/or radio interface <NUM> and/or communication interface <NUM> is configured to assign the WD <NUM> to a group with other WDs <NUM> based at least in part on one of a service type of the WD <NUM> and based at least in part on one or more of: a preemption indication monitoring capability of the WD <NUM>, a power control capability of the WD <NUM>; or a spatial separateness of the WD <NUM>. The process also includes assigning resources to the WD <NUM> according to the group to which the WD <NUM> is assigned. In one or more embodiments, the service type is not explicitly signaled to the WD <NUM> assuming service type URLLC/eMBB, for example. In one or more embodiments, the grouping described herein is based at least in part on preemption capability and/or lack thereof when performing an initial random access procedure.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for assigning of resources based on grouping of wireless devices.

In one or more embodiments of the uplink description, an assumption is made that there are at least two possible approaches to inter-WD pre-emption, where one requires special victim WD capability, while another one can be used with all WDs <NUM>, including legacy WDs <NUM> without special capabilities.

In one embodiment, when at least two BWPs are configured in a cell, the network node <NUM>, via, for example, processing circuitry <NUM> and/or group assignment unit <NUM>, allocates all or a majority of legacy WDs <NUM> or WDs <NUM> without PI monitoring capability to a BWP where the pre-emption cannot happen. In a typical example, Release-<NUM> eMBB- compatible WDs <NUM> and some Release <NUM> compatible WDs <NUM> do not have UL pre-emption monitoring capability, and these are called non-UL-PI-capable WDs <NUM>. Other Release <NUM> (and later) eMBB WDs <NUM> have UL pre-emption monitoring capability, and these are called UL-PI-capable WDs <NUM>. Non-UL-PI-capable WDs <NUM> are allocated to BWP1 so that they do not co-exist with aggressor WDs <NUM>. Conversely, the embodiment also can be interpreted such that in another BWP (e.g., BWP <NUM>), where eMBB and URLLC services co-exist, the network node <NUM> allocates resources only to eMBB WDs <NUM> which have PI monitoring capability (i.e., certain Release <NUM> and later eMBB WDs <NUM>), but not Release <NUM> eMBB WDs <NUM>. This is illustrated in <FIG>.

In another embodiment, URLLC WDs <NUM> can also be allocated to different BWPs according to WD <NUM> radio conditions. Since power control-based inter-WD pre-emption may require the aggressor URLLC WD <NUM> to have enough power budget to increase power (i.e., the wireless device being not power limited), the WDs <NUM> satisfying this condition can be multiplexed in the same BWP with eMBB WDs <NUM> without PI monitoring capability. This is shown in <FIG>, where URLLC WDs <NUM> that are not power limited, and eMBB WDs <NUM> without PI monitoring capability are grouped together and assigned to the BWP <NUM>. While power-limited URLLC WDs <NUM> and eMBB WDs with PI monitoring capability are grouped together and assigned to another BWP, BWP <NUM>.

In another embodiment, WD grouping can be performed, via the group assignment unit <NUM>, on a resource block basis within one BWP.

In yet another embodiment, WD grouping can be performed, via the group assignment unit, based on spatial properties of eMBB and URLLC WDs <NUM>. For example, based on UL channels, the network node <NUM> can, via processing circuitry <NUM>, determine which and how well eMBB WDs <NUM> and URLLC WDs <NUM> can be multiplexed (for example, multi-user multiple input multiple output (MU-MIMO)). In an example of such an embodiment, the network node <NUM> may, via the processing circuitry <NUM>, schedule eMBB WDs <NUM> such that there is a resource in the frequency domain for a potentially scheduled URLLC WD <NUM>, where the potentially scheduled URLLC WD <NUM> is spatially separable from an eMBB WD <NUM> on the same resource.

In some embodiments non-UL-PI-capable WDs <NUM> are scheduled, via processing circuitry <NUM>, if one or more of the following requirements/conditions are fulfilled/satisfied:.

In another embodiment, grouping of a UL pre-empting WD <NUM> (also called an aggressor WD <NUM>) and the two types of UL pre-empted WDs <NUM> (also called victim WDs <NUM>) is performed, via the group assignment unit <NUM>, according to component carriers in a carrier aggregation (CA).

In one example, for a UL component carrier with the aggressor WD <NUM>, only victim WDs <NUM> with UL PI monitoring capability are allowed to be assigned, via the processing circuitry <NUM>, to this UL component carrier, for example component carrier <NUM>. WDs <NUM> without PI monitoring capability are assigned to a different UL component carrier (e.g., component carrier <NUM>), where there are no aggressor WDs <NUM>.

Since a WD <NUM> may behave as an aggressor WD <NUM> when it serves certain traffic types (e.g., aperiodic URLLC), but behave as a victim WD <NUM> when it serves other traffic types (e.g., eMBB, machine type communication (MTC)), a same WD <NUM> may be assigned, via processing circuitry <NUM>, to different component carriers according to the traffic type that the WD <NUM> currently serves. For example, when the network node <NUM> receives an indication that the WD <NUM> is to start serving aperiodic URLLC traffic on the uplink, the network node <NUM> may, via processing circuitry <NUM>, assign the WD <NUM> with component carrier <NUM> on the UL, where the WD <NUM> behaves as an aggressor WD <NUM> and transmits UL data for the aperiodic URLLC traffic. When the network node <NUM> receives an indication that the WD <NUM> is to terminate the aperiodic URLLC traffic on the uplink, the network node <NUM> may, via the processing circuitry <NUM>, move the WD's UL to component carrier <NUM>.

Note that for periodic URLLC traffic, UL Cell Group (CG) can be used to reserve resources for initial transmission and the WD <NUM> may not behave as an aggressor. For retransmission of an UL CG packet, the WD <NUM> may need to pre-empt other WDs <NUM>' UL transmission in order to get the retransmission through quicker.

For a WD <NUM> that is serving eMBB and URLLC traffic simultaneously, the network node <NUM> may, via processing circuitry <NUM>, assign the WD <NUM> two component carriers, where the WD <NUM> may use component carrier <NUM> to serve the URLLC traffic (hence, the WD <NUM> acts as an aggressor WD <NUM>), whereas the WD <NUM> may use component carrier <NUM> to serve the eMBB traffic (hence, the WD <NUM> act as a victim WD <NUM>).

In another embodiment, grouping of a UL pre-empting WD <NUM> (also called an aggressor WD <NUM>, e.g., a WD <NUM> with UL URLLC service) and the two types of UL pre-empted WDs <NUM> (also called victim WDs <NUM>) is performed, via the group assignment <NUM>, according to different network nodes in a dual-connectivity configuration. The network node can be either a master network node <NUM> or a secondary network node <NUM>.

In one example, for a network node (e.g., network node 16a) with the aggressor WD <NUM>, only victim WDs <NUM> with UL PI monitoring capability may be allowed to be assigned to this network node. WDs <NUM> without PI monitoring capability are assigned to a different network node (e.g., network node 16b), where there is no aggressor WDs <NUM>.

Similar to the CA case, in another example, a same WD <NUM> may be assigned, via the processing circuitry <NUM>, to different network nodes according to the traffic type that the WD <NUM> currently serves. For example, when a master network node 16c receives an indication that the WD <NUM> is to start serving aperiodic URLLC traffic on the uplink, the master network node 16c assigns, via processing circuitry <NUM>, network node 16a to the WD <NUM> as a serving network node <NUM>, where the WD <NUM> can behave as an aggressor. When the master network node 16c receives, via radio interface <NUM> an indication that the WD <NUM> is to terminate the aperiodic URLLC traffic on the uplink, the master network node <NUM>, via processing circuitry <NUM>, deletes network node 16a from the WD's serving network node 16a set.

Similar to the CA case, in another example, for a WD <NUM> that is serving eMBB and URLLC traffic simultaneously, the master network node 16c may assign, via processing circuitry <NUM>, the WD <NUM> two network nodes. The WD <NUM> uses network node 16a to serve the URLLC traffic (hence, the WD <NUM> act as an aggressor WD <NUM>), whereas the WD <NUM> uses network node 16b to serve the eMBB traffic (hence, the WD <NUM> act as a victim WD <NUM>).

In the downlink, co-existence of different traffic types may force the scheduler implemented by processing circuitry <NUM> of a network node <NUM> to interrupt/pre-empt ongoing transmission(s) and fully or partially replace the ongoing transmission(s) by another transmission. But in a current BWP candidate, victim WDs <NUM> may or may not be capable of receiving, via radio interface <NUM>, a "preemption indication" (PI) message, due to lower capabilities. For WDs <NUM> without the DL pre-emption indication monitoring capability, the pre-emption may be more harmful, because such WDs <NUM> cannot flush, via its processing circuitry <NUM>, the corrupted part of a soft-buffer, while WDs <NUM> having this capability can recover the transmission. To help avoid this situation, one or more scheduling techniques described herein can be used.

In a first embodiment, the scheduler, which may be implemented in processing circuitry <NUM>, of network node <NUM> avoids pre-emption of WDs <NUM> which are not capable of receiving a "preemption indication" message, when avoiding pre-emption is possible, i.e., if there are other WDs <NUM> scheduled in BWP with the required capability and their allocated resources are enough for pre-emption.

In a second embodiment, the network node <NUM> allows co-existence of service types with different requirements (e.g., eMBB and URLLC) in one BWP only if potentially pre-empted WDs <NUM> are able to receive, via radio interface <NUM>, a "preemption indication" message. In this case, WDs <NUM> without this capability will be allocated, via processing circuitry <NUM> of the network node <NUM>, to another BWP.

In a third embodiment, the network node <NUM>, via processing circuitry <NUM>, creates virtual partitions of a BWP in the frequency domain (<FIG>) and/or the time domain (<FIG>) and allows coexistence of service types with different requirements (e.g. eMBB and URLLC) only in a subset of partitions where the preemption is possible. Low priority data can be allocated in the partitions only if potentially preempted WDs <NUM> are able to receive, via radio interface <NUM>, a "preemption indication" message. In this case, WDs <NUM> without this capability may be allocated to other partitions.

The grouping/partitioning can further, or alternatively, be based on spatial properties. The eMBB and URLLC WDs <NUM> scheduled in different beams may be MU-MIMO-scheduled without sacrificing reliability for URLLC WDs <NUM>. For pre-coded transmission the grouping/partitioning, via processing circuitry <NUM> and group assignment unit <NUM>, can be based on estimated spatial separateness of eMBB and URLLC WDs <NUM> using the reported pre-coders. The grouping can further be based on a number of WD <NUM> receive antenna ports and scheduled rank for eMBB WDs <NUM>.

In some embodiments, the scheduler of network node <NUM> selects a lower rank or reduced power for one or more eMBB WDs <NUM> on resources where URLLC WDs <NUM> potentially need to be scheduled. In another embodiment, similar to the UL, grouping of DL preempting WDs <NUM> (also called aggressor WDs <NUM>) and the two types of DL preempted WDs <NUM> (also called victim WDs <NUM>) is performed according to component carriers in a carrier aggregation (CA). The two types of DL preempted WDs <NUM> refer to: non-DL-PI-capable WDs <NUM> and DL-PI-capable WDs <NUM>.

In another embodiment, similar to the UL, grouping of DL preempting WDs <NUM> and the two types of UL preempted WDs <NUM> (also called victim WDs <NUM>) is performed, via group assignment unit <NUM>, according to different network nodes in a dual-connectivity configuration. The network node can be either a master network node <NUM> or a secondary network node <NUM>.

Note that the grouping of one or more WDs <NUM> might be changed dynamically during communication and/or while the WD <NUM> is in connection with the network node <NUM>, e.g. according to changes in communication conditions and/or service type. For example, if a service or communication according to a specific service type is established or released for a WD <NUM> (e.g., an URLLC service or communication) and/or a WD <NUM> changes position, a WD <NUM> might be associated with a different group (which might be dynamically set up or released, or be one of the groups already present) and/or be reassigned.

Thus, some embodiments include a method and a network node for assigning of resources based on grouping of wireless devices. According to one aspect, a network node has processing circuitry configured to perform method steps including assigning the WD to a group with other WDs <NUM> based at least in part on a service type of the WD. The assigning to a group is also based at least in part on one or more of: a preemption indication monitoring capability of the WD <NUM>; or a power control capability of the WD <NUM>; or a spatial separateness of the WD <NUM> with respect to other WDs <NUM>. The processing circuitry is also configured to assign resources to the WD <NUM> according to the group to which the WD <NUM> is assigned.

According to this aspect, in some embodiments, a group to which the WD is assigned is one of: a first group of WDs <NUM> having different service types and being assigned a same first bandwidth part, and a second group of WDs <NUM> having a same service type and being assigned a same second bandwidth part. In some embodiments, the WD <NUM> that has an uplink preemption indication monitoring capability and is of a first service type is assigned the first bandwidth part and a WD <NUM> that does not have an uplink preemption indication monitoring capability and is of the first service type is assigned to the second bandwidth part. In some embodiments, if the WD <NUM> is power limited and of a first service type the WD <NUM> is assigned the first bandwidth part and if the WD <NUM> is not power limited and of the first service type the WD is assigned the second bandwidth part. In some embodiments, a same frequency resource is assigned to a first WD <NUM> of a first service type and to a second WD <NUM> of a second service type only if the first and second WDs <NUM> are spatially separable. In some embodiments, the WD <NUM> is assigned to uplink on a carrier associated with an aggressor WD <NUM> only if the WD <NUM> has an uplink preemption indication monitoring capability. In some embodiments, the processor is further configured to avoid scheduling of WDs <NUM> not capable of preemption indication monitoring in a bandwidth part when other WDs <NUM> that are capable of preemption indication monitoring are scheduled in the bandwidth part. In some embodiments, the network node allows coexistence of service types in a same bandwidth part only for WDs <NUM> that are capable of preemption indication monitoring are scheduled in the bandwidth part. In some embodiments, the network node partitions a bandwidth part in frequency or time to allocate a first part of the bandwidth part for WDs <NUM> having a same service type and to allocate a second part of the bandwidth part for WDs <NUM> having different service types.

Some embodiments may include one or more of the following:.

For inter WD Tx prioritization/multiplexing, UL cancellation scheme and enhanced UL power control scheme may be supported in 3GPP Rel-<NUM>.

Claim 1:
A network node (<NUM>) configured to communicate with a wireless device (<NUM>), WD, the network node (<NUM>) comprising processing circuitry (<NUM>), the processing circuitry (<NUM>) configured to cause the network node (<NUM>) to:
assign the wireless device (<NUM>) to a group with other wireless devices (<NUM>) based at least in part on a service type of the wireless device (<NUM>) and based at least in part on at least one of:
a preemption indication monitoring capability of the wireless device (<NUM>);
a power control capability of the wireless device (<NUM>); and
a spatial separateness of the wireless device (<NUM>) with respect to at least one of the other wireless devices (<NUM>); and
assign at least one resource to the wireless device (<NUM>) according to the group to which the wireless device (<NUM>) is assigned, wherein the preemption indication monitoring capability of the wireless device (<NUM>) corresponds to whether the wireless device (<NUM>) is capable of monitoring for an inter-WD uplink preemption indication message from the network node (<NUM>), wherein the power control capability of the wireless device (<NUM>) corresponds to whether the wireless device (<NUM>) is capable of an enhanced dynamic uplink, UL, power control boost, and wherein the spatial separateness of the wireless device (<NUM>) corresponds to whether the wireless device (<NUM>) can be scheduled on a same time-frequency resource as the at least one of the other wireless devices (<NUM>) based at least in part on the spatial separateness of the wireless device (<NUM>) with respect to the at least one of the other wireless devices (<NUM>).