Preemption and cancellation in sidelink and uplink access

Abstract

Various aspects relate to obtaining, at a first scheduled entity, a first priority ranking of first uplink (UL) data and first data, and a second priority ranking of second data, respectively, wherein the first UL data is scheduled for transmission to the scheduling entity, the first data is scheduled for transmission to the second scheduled data, and the second data is scheduled for transmission to the third and fourth scheduled entities. The scheduling uses at least a portion of the sidelink resources reserved for sidelink communication for these transmissions. The scheduling of these transmissions using the at least a portion of the sidelink resources is based on the first priority ranking and the second priority ranking. Various transmission cancellations and reception preemptions are sent from the transmitting scheduled entity to other transmitting or receiving scheduled entities, respectively. Such cancellations and preemptions are based on the priority ranking, the prediction of data transmission conflicts, and the prediction of interference at the receiving entity.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to and the benefit of non-provisional patent application No. 17 / 179,216 filed in the U.S. Patent and Trademark Office on February 18, 2021, and provisional patent application No. 62 / 979,981 filed in the U.S. Patent and Trademark Office on February 21, 2020, the entire contents of which are incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] The techniques discussed below relate generally to wireless communication systems, and more particularly to adjusting wireless communication system resources in view of traffic priority.

[0004] introduction

[0005] Wireless communication between wireless devices can be facilitated using one or more communication links. For example, an access link is a communication link between a user equipment (UE) (e.g., a wireless communication device or a scheduled entity) and a network access node (e.g., an eNB, gNB, or a scheduling entity). Additionally, a sidelink is a communication link between two wireless communication devices (e.g., between two UEs or between two scheduled entities). Sidelink communications may encompass, for example, device-to-device (D2D) communications, vehicle-to-vehicle (V2V) communications, and / or vehicle-to-everything (V2X) communications. Both access and sidelink communications may utilize beamforming to steer transmissions (and focus reception) in space, thereby allowing for spatial diversity.

[0006] For access communications, there are various priorities that can be assigned to different types of traffic (referred to herein as data traffic or data). For example, a first priority can be assigned to enhanced mobile broadband (eMBB) data traffic. Today, eMBB data accounts for most access downlink (DL) and uplink (UL) data traffic. A second priority can be assigned to ultra-reliable low latency communication (URLLC). URLLC applications are time-sensitive. Due to the low latency requirement, URLLC data traffic has a higher priority than eMBB data traffic. In some examples, once the data arrives at the source, it may be necessary to transmit URLLC data traffic. In this context, the source is a network access node (e.g., eNB, gNB) or scheduling entity for downlink data traffic, or a UE or scheduled entity for uplink data traffic. For example, in the downlink, when DL URLLC arrives at the network access node buffer, the network access node may interrupt the transmission of eMBB DL data traffic to start transmitting DL URLLC data traffic.

[0007] A brief overview of some examples

[0008] The following is an overview of one or more aspects of the present disclosure to provide a basic understanding of these aspects. This overview is not an exhaustive overview of all contemplated features of the present disclosure, nor is it intended to identify key or critical elements of all aspects of the present disclosure, nor is it intended to define the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form that serves as a prelude to the more detailed description that will be provided later.

[0009] According to one aspect, a method for wireless communication at a scheduling entity in a wireless communication network is disclosed. The method includes obtaining a first priority ranking of first uplink (UL) data, the first UL data being used for a first UL data transmission from a first scheduled entity to the scheduling entity; obtaining a second priority ranking of second data, the second data being scheduled for a second data transmission from a second scheduled entity to a third scheduled entity using at least a portion of sidelink resources reserved for sidelink communication; and scheduling the first UL data transmission using the at least a portion of the sidelink resources based on the first priority ranking and the second priority ranking.

[0010] An example of an apparatus configured as a scheduling entity for wireless communication in a wireless communication network is disclosed. The apparatus includes a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. According to one aspect, the processor is configured to: obtain a first priority ranking of first uplink (UL) data, the first UL data being used for a first UL data transmission from a first scheduled entity to the scheduling entity; obtain a second priority ranking of second data, the second data being scheduled for a second data transmission from a second scheduled entity to a third scheduled entity using at least a portion of sidelink resources reserved for sidelink communication; and schedule the first UL data transmission using the at least a portion of the sidelink resources based on the first priority ranking and the second priority ranking.

[0011] According to another aspect, another method for wireless communication at a scheduling entity in a wireless communication network is disclosed. The method includes: obtaining a first priority ranking of first data, the first data for a first data transmission from a first scheduled entity to a second scheduled entity using at least a portion of sidelink resources reserved for sidelink communication; obtaining a second priority ranking of second data, the second data scheduled for a second data transmission from a third scheduled entity to a fourth scheduled entity using the at least a portion of the sidelink resources reserved for sidelink communication; and scheduling the first data transmission using the at least a portion of the sidelink resources based on the first priority ranking and the second priority ranking.

[0012] Another example of an apparatus for wireless communication is disclosed. The apparatus includes a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor. In some aspects, the processor is configured to: obtain a first priority ranking of first data, the first data for a first data transmission from a first scheduled entity to a second scheduled entity using at least a portion of sidelink resources reserved for sidelink communication; obtain a second priority ranking of second data, the second data scheduled for a second data transmission from a third scheduled entity to a fourth scheduled entity using the at least a portion of the sidelink resources; and schedule the first data transmission using the at least a portion of the sidelink resources based on the first priority ranking and the second priority ranking.

[0013] These and other aspects of the present invention will be more fully understood upon reading the following detailed description. Other aspects and features will become apparent to those of ordinary skill in the art upon reading the description of the specific examples below in conjunction with the accompanying drawings. Although various features may be discussed below with respect to certain examples and drawings, all examples may include one or more of the advantageous features discussed herein. In other words, although one or more examples may be discussed as having certain advantageous features, one or more such features may also be used according to the various examples discussed herein. In a similar manner, although various examples may be discussed below as examples of devices, systems, or methods, it should be understood that such examples may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a diagram illustrating an example of a wireless radio access network in accordance with some aspects.

[0016] Figure 2 is a diagram illustrating an example of a wireless communication network employing sidelink communications in accordance with some aspects.

[0017] Figure 3 is a schematic illustration of a wireless communication system supporting multiple-input multiple-output (MIMO) communications in accordance with some aspects of the present disclosure.

[0018] Figure 4 is a schematic illustration of radio resource organization in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to some aspects of the present disclosure.

[0019] Figure 5 is a block diagram illustrating an example of a hardware implementation of a scheduling entity according to some aspects of the present disclosure.

[0020] Figure 6 is a block diagram illustrating an example of a hardware implementation of a scheduled entity according to some aspects of the present disclosure.

[0021] Figure 7 is a schematic illustration of an example of a wireless communication system according to some aspects of the present disclosure.

[0022] Figure 8 is a schematic illustration of another example of a wireless communication system according to some aspects of the present disclosure.

[0023] Figure 9 is a schematic illustration of another example of a wireless communication system according to some aspects of the present disclosure.

[0024] Figure 10 is a schematic illustration of another example of a wireless communication system according to some aspects of the present disclosure.

[0025] Figure 11 is a flow chart illustrating an exemplary method of wireless communication at a scheduling entity in a wireless communication network according to some aspects of the present disclosure.

[0026] Figure 12 is a flow chart illustrating another exemplary method of wireless communications at a scheduling entity in a wireless communication network in accordance with some aspects of the present disclosure.

[0027] Figure 13 is a flow chart illustrating another exemplary method of wireless communications at a scheduling entity in a wireless communication network in accordance with some aspects of the present disclosure.

[0028] Figure 14 is a flow chart illustrating another exemplary method of wireless communications at a scheduling entity in a wireless communication network in accordance with some aspects of the present disclosure.

[0029] Figure 15 is a flow chart illustrating another exemplary method of wireless communications at a scheduling entity in a wireless communication network in accordance with some aspects of the present disclosure.

[0030] Figure 16 is a flow chart illustrating an example method of wireless communication at a first scheduled entity of a plurality of scheduled entities in a wireless communication network, in accordance with aspects of the present disclosure.

[0031] Detailed description

[0032] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid overstating such concepts.

[0033] Although various aspects and examples are described in this application by explaining some examples, it will be understood by those skilled in the art that additional implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, various aspects and / or uses can be generated via integrated chip examples and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for each use case or application, the wide applicability of the described innovation may occur. The scope of each implementation can range from chip-level or module components to non-module, non-chip-level implementations, and further to aggregated, distributed or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovation. In some practical environments, the equipment incorporating the various aspects and features described may also necessarily include additional components and features for implementing and practicing the claimed and described examples. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, and the like, of various sizes, shapes, and configurations.

[0034] The various concepts presented throughout this disclosure can be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1 , a schematic illustration of a radio access network 100 is provided as an illustrative example and not a limitation. The RAN 100 may implement any one or several suitable wireless communication technologies to provide radio access. As an example, the RAN 100 may operate in accordance with the Third Generation Partnership Project (3GPP) New Radio (NR) specifications (commonly referred to as 5G). As another example, the RAN 100 may operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards (commonly referred to as LTE). 3GPP refers to this hybrid RAN as the Next Generation RAN, or NG-RAN. Of course, many other examples may be utilized within the scope of the present disclosure.

[0035] The geographical area covered by the radio access network 100 may be divided into a number of cellular areas (cells) that may be uniquely identified by user equipment (UE) based on an identity broadcast over the geographical area from an access point or base station. Figure 1Cells 102, 104, 106, and 108 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of a cell. All sectors within a cell are served by the same base station. A radio link within a sector may be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell may be formed by antenna groups, where each antenna is responsible for communicating with UEs in a portion of the cell.

[0036] In general, a corresponding base station (BS) serves its own cell. Broadly speaking, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. A BS may also be referred to by those skilled in the art as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a B node (NB), an evolved B node (eNB), a g B node (gNB), a transmit receive point (TRP), or some other suitable term. In some examples, a base station may include two or more TRPs that may be co-located or non-co-located. Each TRP may communicate on the same or different carrier frequencies within the same or different frequency bands. In an example in which RAN100 operates according to both LTE and 5G NR standards, one of the base stations may be an LTE base station, and the other may be a 5G NR base station.

[0037] exist Figure 1 , two base stations 110 and 112 are shown in cells 102 and 104; and a third base station 114 is shown controlling a remote radio head (RRH) 116 in cell 106. That is, the base stations may have integrated antennas or may be connected to antennas or RRHs by feeder cables. In the illustrated example, cells 102, 104, and 106 may be referred to as macro cells because base stations 110, 112, and 114 support cells of large size. Additionally, base station 118 is shown in cell 108, which may overlap with one or more macro cells. In this example, cell 108 may be referred to as a small cell (e.g., a micro cell, a pico cell, a femto cell, a home base station, a Home NodeB, a Home eNodeB, etc.) because base station 118 supports cells of relatively small size. Cell sizing may be accomplished based on system design and component constraints. It should be understood that radio access network 100 may include any number of wireless base stations and cells. Additionally, relay nodes may be deployed to extend the size or coverage area of a given cell.Base stations 110, 112, 114, 118 provide wireless access points to the core network for any number of mobile devices.

[0038] Figure 1 Further included is an unmanned aerial vehicle (UAV) 120 (such as a quadcopter or drone) that can be configured to serve as a base station. That is, in some examples, the cell may not necessarily be stationary, and the geographic area of the cell may move depending on the location of a mobile base station (such as UAV 120).

[0039] In general, a base station may include a backhaul interface for communicating with a backhaul portion of a network (not shown). The backhaul may provide a link between the base station and a core network (not shown), and in some examples, may provide interconnection between respective base stations. The core network may be part of a wireless communication system and may be independent of the radio access technology used in the radio access network. Various types of backhaul interfaces may be employed using any suitable transport network, such as a direct physical connection, a virtual network, and the like.

[0040] RAN 100 is illustrated as supporting wireless communications for multiple mobile devices. Mobile devices are generally referred to as user equipment (UE) in the standards and specifications promulgated by the Third Generation Partnership Project (3GPP), but may also be referred to by those skilled in the art as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (ATs), mobile terminals, wireless terminals, remote terminals, handsets, terminals, user agents, mobile clients, clients, or some other suitable terminology. A UE may be a device that provides a user with access to network services.

[0041] Within this document, a "mobile" device does not necessarily need to have mobile capabilities and can be stationary. The term mobile device or mobile device refers to a wide variety of devices and technologies. For example, some non-limiting examples of mobile devices include mobile devices, cellular (cell) phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide variety of embedded systems, for example, corresponding to the "Internet of Things" (IoT). Additionally, a mobile device can be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses), a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. Additionally, the mobile device may be a digital home or smart home device, such as home audio, video, and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, and the like. Additionally, the mobile device may be a smart energy device, a security device, a solar panel or solar array, municipal infrastructure equipment that controls electricity, lighting, water, and the like (e.g., a smart grid), industrial automation and enterprise equipment, logistics controllers, agricultural equipment, and the like. Furthermore, the mobile device may provide connected medical or telemedicine support, i.e., healthcare from a distance. Telehealth devices may include telehealth monitoring devices and telehealth supervisory devices, whose communications may be given priority treatment or prioritized access over other types of information, for example, in the form of prioritized access for critical service data transmission and / or associated QoS for critical service data transmission.

[0042] Within RAN 100, cells may include UEs that may be in communication with one or more sectors of each cell. For example, UEs 122 and 124 may be in communication with base station 110; UEs 126 and 128 may be in communication with base station 112; UEs 130 and 132 may be in communication with base station 114 via RRH 116; UE 134 may be in communication with base station 118; and UE 136 may be in communication with mobile base station 120. Here, each base station 110, 112, 114, 118, and 120 may be configured to provide an access point to a core network (not shown) for all UEs in the corresponding cell. In another example, a mobile network node (e.g., quadcopter 120) may be configured to function as a UE. For example, quadcopter 120 may operate within cell 102 by communicating with base station 110.

[0043] Wireless communications between the RAN 100 and a UE (e.g., UE 122 or 124) may be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 110) to one or more UEs (e.g., UEs 122 and 124) may be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink may refer to point-to-multipoint transmissions originating at a scheduling entity (described further below; e.g., base station 110). Another way to describe this approach may be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 122) to a base station (e.g., base station 110) may be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term uplink may refer to point-to-point transmissions originating at a scheduled entity (described further below; e.g., UE 122).

[0044] For example, a DL transmission may include a unicast or broadcast transmission of control information and / or traffic information (e.g., user data traffic) from a base station (e.g., base station 110) to one or more UEs (e.g., UEs 122 and 124), while an UL transmission may include a transmission of control information and / or traffic information originating at a UE (e.g., UE 122). Additionally, uplink and / or downlink control information and / or traffic information may be temporally divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol may refer to a time unit in an orthogonal frequency division multiplexing (OFDM) waveform that carries one resource element (RE) per subcarrier. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or time slots may be grouped together to form a single frame or radio frame. Of course, these definitions are not required, and any suitable scheme may be used to organize the waveform, and the various time divisions of the waveform may have any suitable duration.

[0045] In order to achieve a low block error rate (BLER) for transmissions over the air interface while still achieving very high data rates, channel coding can be used. That is, wireless communications generally utilize suitable error-correcting block codes. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., CODEC) at the transmitting device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message can improve the reliability of the message, enabling correction of any bit errors that may occur due to noise.

[0046] Data encoding can be implemented in a variety of ways. In earlier 5G NR specifications, user data was encoded using quasi-cyclic low-density parity check (LDPC) with two different basemaps: one basemap was used for large code blocks and / or high code rates, and the other basemap was used for other cases. Polar coding was used based on nested sequences to encode control information and the Physical Broadcast Channel (PBCH). For these channels, puncturing, shortening, and repetition were used for rate matching.

[0047] Various aspects of the present disclosure may be implemented using any suitable channel code. Various implementations of base stations and UEs may include appropriate hardware and capabilities (eg, encoders, decoders, and / or CODECs) to utilize one or more of these channel codes for wireless communication.

[0048] The air interface in the RAN 100 may utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL or reverse link transmissions from UEs 122 and 124 to base station 110, and utilizes orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) to provide multiplexing for DL or forward link transmissions from base station 110 to UEs 122 and 124. In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spread multiple access (RSMA), or other appropriate multiple access schemes. Furthermore, multiplexing of DL transmissions from base station 110 to UEs 122 and 124 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0049] Furthermore, the air interface in RAN 100 may utilize one or more duplexing algorithms. Duplex refers to a point-to-point communication link in which both endpoints can communicate with each other in both directions. Full-duplex means that both endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can send information to the other endpoint at a time. Half-duplex emulation is often achieved for wireless links using time division duplexing (TDD). In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at some times, the channel is dedicated to transmission in one direction, while at other times, it is dedicated to transmission in the other direction, where the direction can change very quickly, for example, several times per time slot. In wireless links, full-duplex channels generally rely on physical isolation between the transmitter and receiver, as well as appropriate interference cancellation techniques. Full-duplex emulation is often achieved for wireless links using frequency division duplexing (FDD) or space division duplexing (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within a paired spectrum). In SDD, transmissions in different directions on a given channel are separated from each other using spatial division multiplexing (SDM). In other examples, full-duplex communication can be achieved within an unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different sub-bands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as sub-band full-duplex (SBFD), also known as flexible duplexing.

[0050] In the RAN 100, the ability of a UE to communicate independently of its location while moving is known as mobility. The various physical channels between the UE and the RAN are typically established, maintained, and released under the control of an access and mobility management function (AMF). In some scenarios, the AMF may include a security context management function (SCMF) and a security anchor function (SEAF) that performs authentication. The SCMF may manage the security context for both control plane and user plane functionality, in whole or in part.

[0051] In some examples, RAN 100 may implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another). For example, during a call with a scheduling entity, or at any other time, a UE may monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may undergo a handover or handover from the serving cell to the neighboring (target) cell. For example, UE 124 may move from the geographic area corresponding to its serving cell 102 to the geographic area corresponding to neighboring cell 106. When the signal strength or quality from neighboring cell 106 exceeds the signal strength or quality of its serving cell 102 for a given amount of time, UE 124 may transmit a report message to its serving base station 110 indicating this condition. In response, UE 124 may receive a handover command, and the UE may undergo a handover to cell 106.

[0052] In various implementations, the air interface in the RAN 100 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum generally provides exclusive use of a portion of the spectrum by a mobile network operator purchasing a license from a government regulator. Unlicensed spectrum provides shared use of a portion of the spectrum without the need for a government-granted license. While access to unlicensed spectrum generally still requires adherence to certain technical regulations, any operator or device may gain access. Shared spectrum may fall between licensed and unlicensed spectrum, where technical regulations or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a license holder of a portion of licensed spectrum may provide licensed shared access (LSA) to share that spectrum with other parties, e.g., with access obtained under conditions determined by the appropriate license holder.

[0053] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station) allocates resources (e.g., time-frequency resources) for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, a UE or scheduled entity utilizes resources allocated by the scheduling entity.

[0054] A base station is not the only entity that can serve as a scheduling entity. That is, in some examples, a UE can serve as a scheduling entity, thereby scheduling resources for one or more scheduled entities (e.g., one or more other UEs). For example, two or more UEs (e.g., UEs 138, 140, and 142) can communicate with each other using sidelink signals 137 without relaying the communication through a base station. In some examples, UEs 138, 140, and 142 can each act as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and communicate sidelink signals 137 between them without relying on scheduling or control information from the base station. In other examples, two or more UEs (e.g., UEs 126 and 128) within the coverage area of a base station (e.g., base station 112) can also communicate sidelink signals 127 on a direct link (sidelink) without having to communicate the communication through base station 112. In this example, base station 112 can allocate resources to UEs 126 and 128 for sidelink communication. In either case, such sidelink signaling 127 and 137 may be implemented in a peer-to-peer (P2P) network, a device-to-device (D2D) network, a vehicle-to-vehicle (V2V) network, a vehicle-to-everything (V2X) network, a mesh network, or other suitable direct-link network.

[0055] In some examples, a D2D relay framework can be included within a cellular network to facilitate relaying of communications to / from base station 112 via a D2D link (e.g., side link 127 or 137). For example, one or more UEs (e.g., UE 128) within the coverage area of base station 112 can operate as relay UEs to extend the coverage of base station 112, improve transmission reliability to one or more UEs (e.g., UE 126), and / or allow the base station to recover from a failed UE link due to, for example, blocking or fading.

[0056] The two main technologies that can be used by V2X networks include dedicated short-range communications (DSRC) based on the IEEE 802.11p standard and cellular V2X based on LTE and / or 5G (New Radio) standards. Various aspects of the present disclosure may relate to New Radio (NR) cellular V2X networks, which for simplicity will be referred to herein as V2X networks. However, it should be understood that the concepts disclosed herein may not be limited to a specific V2X standard or may refer to sidelink networks other than V2X networks.

[0057] Figure 2An example of a wireless communication network 200 configured to support D2D or sidelink communication is illustrated. In some examples, sidelink communication may include V2X communication. V2X communication involves not only the direct wireless information exchange between vehicles (e.g., vehicles 202 and 204) themselves, but also the direct wireless information exchange between vehicles 202 / 204 and infrastructure (e.g., roadside units (RSUs) 206) (such as streetlights, buildings, traffic cameras, toll booths, or other stationary objects), vehicles 202 / 204 and pedestrians 208, and vehicles 202 / 204 and a wireless communication network (e.g., base station 210). In some examples, V2X communication can be implemented according to the New Radio (NR) cellular V2X standard defined by 3GPP (Release 16) or other suitable standards.

[0058] V2X communication enables vehicles 202 and 204 to obtain information regarding weather, nearby accidents, road conditions, nearby vehicle and pedestrian activity, objects near the vehicle, and other relevant information that can be used to improve the driving experience and enhance vehicle safety. For example, such V2X data can enable autonomous driving and improve road safety and traffic efficiency. For example, V2X-connected vehicles 202 and 204 can utilize the exchanged V2X data to provide inter-vehicle collision warnings, road hazard warnings, approaching emergency vehicle warnings, pre- / post-crash warnings and information, emergency braking warnings, forward traffic jam warnings, lane change warnings, intelligent navigation services, and other similar information. Additionally, V2X data received by the V2X-connected mobile device of pedestrians / cyclists 208 can be used to trigger warning sounds, vibrations, flashing lights, and the like in the event of an impending danger situation.

[0059] Sidelink communications between vehicle UEs (V-UEs) 202 and 204, or between a V-UE 202 or 204 and an RSU 206 or a pedestrian UE (P-UE) 208, may occur over the sidelink 212 using a Proximity Services (ProSe) PC5 interface. In various aspects of the present disclosure, the PC5 interface may be further utilized to support D2D sidelink 212 communications in other proximity use cases. Examples of other proximity use cases may include public safety or business-based (e.g., entertainment, education, office, medical, and / or interactive) proximity services. Figure 2 In the example shown in , ProSe communication may further occur between UEs 214 and 216 .

[0060] ProSe communication can support different operation scenarios, such as in-coverage, out-of-coverage, and partial coverage. Out-of-coverage refers to a scenario in which UEs (e.g., V-UEs 202 and 204 and P-UE 208) are outside the coverage area of a base station (e.g., base station 210), but each UE is still configured for ProSe communication. Partial coverage refers to a scenario in which some UEs (e.g., V-UE 204) are outside the coverage area of base station 210, while other UEs (e.g., V-UE 202 and P-UE 208) are in communication with base station 210. In-coverage refers to a scenario in which UEs (e.g., UEs 214 and 216) are in communication with base station 210 (e.g., gNB) via a Uu (e.g., cellular interface) connection to receive ProSe service authorization and provisioning information to support ProSe operation.

[0061] To facilitate D2D sidelink communication, for example, between UEs 214 and 216 on sidelink 212, UEs 214 and 216 may transmit discovery signals between them. In some examples, each discovery signal may include a synchronization signal, such as a primary synchronization signal (PSS) and / or a secondary synchronization signal (SSS), that facilitates device discovery and synchronization of communications on sidelink 212. For example, the discovery signal may be used by UE 216 to measure the signal strength and channel state of a potential sidelink (e.g., sidelink 212) with another UE (e.g., UE 214). UE 216 may utilize these measurements to select a UE (e.g., UE 214) for sidelink communication or relay communication.

[0062] In a 5G NR sidelink, sidelink communications may utilize a transmit or receive resource pool. For example, the minimum resource allocation unit in frequency may be a subchannel (e.g., which may include, for example, 10, 15, 20, 25, 50, 75, or 100 consecutive resource blocks), and the minimum resource allocation unit in time may be a time slot. The radio resource control (RRC) configuration of the resource pool may be pre-configured (e.g., a factory setting on the UE, such as determined by a sidelink standard or specification) or configured by a base station (e.g., base station 210).

[0063] Additionally, sidelink (e.g., PC5) communications can have two primary resource allocation operating modes. In the first mode (Mode 1), the base station (e.g., gNB) 210 can allocate resources to sidelink devices (e.g., V2X devices or other sidelink devices) for sidelink communications between the sidelink devices in various ways. For example, the base station 210 can dynamically allocate sidelink resources to the sidelink devices (e.g., dynamic grants) in response to sidelink resource requests from the sidelink devices. The base station 210 can further activate pre-configured sidelink grants (e.g., configured grants) for sidelink communications between the sidelink devices. In Mode 1, the transmitting sidelink device can report sidelink feedback to the base station 210.

[0064] In the second mode (Mode 2), the sidelink devices can autonomously select sidelink resources for sidelink communications between them. In some examples, the transmitting sidelink device can perform resource / channel sensing to select unoccupied resources (e.g., subchannels) on the sidelink channel. Signaling on the sidelink 212 is the same between the two modes. Therefore, from the perspective of the receiver, there is no difference between these modes.

[0065] In some aspects of the present disclosure, the scheduling entity and / or the scheduled entity may be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 3 is a schematic illustration of a wireless communication system 300 supporting MIMO according to some aspects of the present disclosure. In a MIMO system, a transmitter 302 includes multiple transmit antennas 304 (e.g., N transmit antennas), and a receiver 306 includes multiple receive antennas 308 (e.g., M receive antennas). Thus, there are N×M signal paths 310 from the transmit antennas 304 to the receive antennas 308. Each of the transmitter 302 and the receiver 306 can be implemented, for example, in the scheduling entity 110, the scheduled entity 122, or any other suitable wireless communication device.

[0066] The use of such multi-antenna technology enables the wireless communication system 300 to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to transmit different data streams (also called layers) simultaneously on the same time-frequency resources. These data streams can be transmitted to a single UE to increase the data rate or to multiple UEs to increase the total system capacity, the latter being called multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data streams by different weights and phase shifts) and then transmitting each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at the UE with different spatial signatures that enable each UE to recover one or more data streams intended for that UE. On the uplink, each UE transmits a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream.

[0067] The number of data streams or layers corresponds to the rank of the transmission. In general, the rank of a MIMO system (e.g., a wireless communication system 300 supporting MIMO) is limited to the lower of the number of transmit or receive antennas 304 or 308. Additionally, the channel conditions at the UE and other considerations (such as the available resources at the base station) may also affect the transmission rank. For example, the rank (and therefore the number of data streams) assigned to a particular UE on the downlink may be determined based on a rank indicator (RI) transmitted from the UE to the base station. The RI may be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and the signal to interference plus noise ratio (SINR) measured on each receive antenna. The RI may indicate, for example, the number of layers that can be supported under the current channel conditions. The base station may use the RI together with resource information (e.g., available resources and the amount of data to be scheduled for the UE) to assign a transmission rank to the UE.

[0068] In a time division duplex (TDD) system, UL and DL are reciprocal, with each using different time slots of the same frequency bandwidth. Therefore, in a TDD system, the base station can assign a rank for DL MIMO transmission based on UL SINR measurements (e.g., based on a sounding reference signal (SRS) or other pilot signal transmitted from the UE). Based on the assigned rank, the base station can then transmit a channel state information-reference signal (CSI-RS) using a separate C-RS sequence for each layer to provide multi-layer channel estimation. Based on the CSI-RS, the UE can measure the channel quality across layers and resource blocks and feed back CQI and RI values to the base station for use in updating the rank and assigning REs for future downlink transmissions.

[0069] In the simplest case, Figure 3, a rank-2 spatial multiplexing transmission on a 2x2 MIMO antenna configuration will transmit one data stream from each transmit antenna 304. Each data stream follows a different signal path in signal path 310 to each receive antenna 308. Receiver 306 may then reconstruct the data streams using the signals received from each of receive antennas 308.

[0070] Will refer to Figure 4 Various aspects of the present disclosure are described using the OFDM waveforms schematically illustrated in

[15] . Those skilled in the art will appreciate that various aspects of the present disclosure can be applied to, for example, DFT-s-OFDMA or SC-FDMA waveforms in substantially the same manner as described below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it will be appreciated that the same principles can also be applied to DFT-s-OFDMA or SC-FDMA waveforms.

[0071] Now refer to Figure 4 , illustrates an expanded view of an exemplary subframe 402 showing an OFDM resource grid 404. However, as those skilled in the art will readily appreciate, the physical (PHY) transmission structure for any particular application may differ from the examples described herein depending on any number of factors. Here, time is in the horizontal direction in units of OFDM symbols; and frequency is in the vertical direction in units of subcarriers of a carrier.

[0072] Resource grid 404 can be used to schematically represent the time-frequency resources for a given antenna port. That is, in a multiple-input, multiple-output (MIMO) implementation with multiple antenna ports available, a corresponding plurality of resource grids 404 may be available for communication. Resource grid 404 is divided into a plurality of resource elements (REs) 406. An RE (which is 1 subcarrier x 1 symbol) is the smallest discrete portion of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more information bits. In some examples, a block of REs may be referred to as a physical resource block (PRB) or more simply a resource block (RB) 408, which may contain any suitable number of contiguous subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, a number independent of the parameter design used. In some examples, depending on the parameter design, an RB may include any suitable number of contiguous OFDM symbols in the time domain. Within this disclosure, it is assumed that a single RB (such as RB 408) corresponds entirely to a single communication direction (transmission or reception for a given device).

[0073] Scheduling a UE or sidelink device (hereinafter collectively referred to as a UE) for downlink, uplink, or sidelink transmissions may involve scheduling one or more resource elements 406 within one or more subbands. Thus, a UE typically utilizes only a subset of the resource grid 404. In some examples, an RB may be the smallest unit of resources that can be allocated to a UE. Thus, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate for that UE. RBs may be scheduled by a base station (e.g., a gNB, eNB, etc.) or may be self-scheduled by the UE / sidelink device implementing D2D sidelink communication.

[0074] In this illustration, RB 408 is shown as occupying less than the entire bandwidth of subframe 402, with some subcarriers illustrated above and below RB 408. In a given implementation, subframe 402 may have a bandwidth corresponding to any number of one or more RBs 408. Furthermore, in this illustration, RB 408 is shown as occupying less than the entire duration of subframe 402, but this is merely one possible example.

[0075] According to some examples, a frame may refer to a duration of 10 ms, where each frame is subdivided into 10 subframes 402, each subframe 402 being 1 ms. Each 1 ms subframe 402 may include one or more adjacent time slots. As an illustrative example, in Figure 4 In the example shown in , a subframe 402 includes four time slots 410. In some examples, a time slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, with a nominal CP, a time slot can include 7 or 14 OFDM symbols. Additional examples may include mini-slots (sometimes referred to as shortened transmission time intervals (TTIs)) with shorter durations (e.g., 1, 2, 4, or 7 OFDM symbols). In some cases, these mini-slots or shortened TTIs can be transmitted using resources scheduled for ongoing time slot transmissions for the same or different UEs. Any number of resource blocks can be utilized within a subframe or time slot.

[0076] An expanded view of one of the time slots 410 illustrates that the time slot 410 includes a control region 412 and a data region 414. Generally speaking, the control region 412 may carry a control channel (e.g., PDCCH), while the data region 414 may carry a data channel (e.g., PDSCH or PUSCH). Of course, a time slot may include all DL, all UL, or at least one DL portion and at least one UL portion. Figure 4 The simple structure illustrated in is merely exemplary in nature and different slot structures may be utilized and may include one or more of each of the control region and the data region.

[0077] Although not in Figure 4Although not illustrated in FIG, each RE 406 within an RB 408 may be scheduled to carry one or more physical channels, including a control channel, a shared channel, a data channel, etc. Other REs 406 within an RB 408 may also carry pilot or reference signals. These pilot or reference signals may be used by a receiving device to perform channel estimation for the corresponding channel, which may enable coherent demodulation / detection of the control and / or data channels within the RB 408.

[0078] In some examples, time slot 410 may be used for broadcast or unicast communications. For example, broadcast, multicast, or groupcast communications may refer to point-to-multipoint transmissions from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communications are delivered to all devices, while multicast communications are delivered to multiple intended recipient devices. Unicast communications may refer to point-to-point transmissions from one device to a single other device.

[0079] In an example of cellular communication on a cellular carrier via a Uu interface, for DL transmissions, a scheduling entity (e.g., a base station) may allocate one or more REs 406 (e.g., within a control region 412) to carry DL control information including one or more DL control channels, such as a physical downlink control channel (PDCCH), to one or more scheduled entities (e.g., UEs). The PDCCH carries downlink control information (DCI), including, but not limited to, power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters) for DL and UL transmissions, scheduling information, grants, and / or RE assignments.

[0080] The PDCCH may further carry hybrid automatic repeat request (HARQ) feedback transmissions, such as acknowledgements (ACKs) or negative acknowledgements (NACKs). HARQ is a technique well known to those skilled in the art, wherein the integrity of packet transmissions may be verified on the receiving side for accuracy, for example, using any suitable integrity check mechanism, such as a checksum or cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be transmitted, whereas if it is not, a NACK may be transmitted. In response to a NACK, the transmitting device may send a HARQ retransmission, which may enable catch-up combining, incremental redundancy, and the like.

[0081] The base station may further allocate one or more REs 406 (e.g., in the control region 412 or the data region 414) to carry other DL signals, such as a demodulation reference signal (DMRS); a phase tracking reference signal (PT-RS); a channel state information (CSI) reference signal (CSI-RS); and a synchronization signal block (SSB). The SSB may be broadcast at regular intervals based on a periodicity (e.g., 5, 10, 20, 40, 80, or 140 milliseconds). The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast control channel (PBCH). The UE may utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the center of the channel (system) bandwidth in the frequency domain, and identify the physical cell identity (PCI) of the cell.

[0082] The PBCH in the SSB may further include: a master information block (MIB), which includes various system information and parameters for decoding the system information block (SIB). The SIB may be, for example, system information type 1 (SystemInformationType1) (SIB1), which may include various additional system information. The MIB and SIB1 together provide minimum system information (SI) for initial access. Examples of system information transmitted in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameter design), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell barring indicator, cell reselection indicator, raster offset, and search space for SIB1. Examples of remaining minimum system information (RMSI) transmitted in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information.

[0083] In an UL transmission, the scheduled entity may utilize one or more REs 406 to carry UL control information (UCI) to the scheduling entity, which includes one or more UL control channels, such as a physical uplink control channel (PUCCH). UCI may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include sounding reference signals (SRS) and uplink DMRS. In some examples, UCI may include a scheduling request (SR), i.e., a request for the scheduling entity to schedule an uplink transmission. Here, in response to the SR transmitted on the UCI, the scheduling entity may transmit downlink control information (DCI), which may schedule resources for uplink packet transmission. UCI may also include HARQ feedback, channel state feedback (CSF) (such as a CSI report), or any other suitable UCI.

[0084] In addition to control information, one or more REs 406 (e.g., within the data region 414) may also be allocated for traffic (e.g., user data). Such traffic may be carried on one or more traffic channels, such as the physical downlink shared channel (PDSCH) for DL transmissions or the physical uplink shared channel (PUSCH) for UL transmissions. In some examples, one or more REs 406 within the data region 414 may be configured to carry other signals, such as one or more SIBs and DMRS.

[0085] In an example of sidelink communication on a sidelink carrier via a PC5 interface, the control region 412 of a time slot 410 may include a physical sidelink control channel (PSCCH), which includes sidelink control information (SCI) transmitted by an initiator (transmitter) sidelink device (e.g., a Tx V2X or other Tx UE) to a set of one or more other receiver sidelink devices (e.g., an Rx V2X device or another Rx UE). The data region 414 of the time slot 410 may include a physical sidelink shared channel (PSSCH), which includes sidelink traffic (e.g., user data) transmitted by the transmitting sidelink device within resources reserved by the initiator (transmitter) sidelink device on the sidelink carrier via the SCI. Other information may further be transmitted on each RE 406 within the time slot 410. For example, HARQ feedback information may be transmitted from the receiving sidelink device to the transmitting sidelink device in a physical sidelink feedback channel (PSFCH) within the time slot 410.

[0086] These physical channels are typically multiplexed and mapped onto transport channels for processing by the Medium Access Control (MAC) layer. Transport channels carry blocks of information, referred to as transport blocks (TBs). The transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.

[0087] The above description and Figure 1-4 The channels or carriers illustrated in the figure are not necessarily all channels or carriers that can be utilized between the scheduling entity 108 and the scheduled entity 106, and one of ordinary skill in the art will recognize that other channels or carriers can be utilized in addition to those channels or carriers illustrated, such as other traffic, control, and feedback channels.

[0088] Figure 5is a block diagram illustrating an example of a hardware implementation of a scheduling entity 500 (e.g., equipment configured as a scheduling entity) according to some aspects of the present disclosure. According to various aspects of the present disclosure, an element, or any portion of an element, or any combination of elements may be implemented with a processing system 502 including one or more processors (such as processor 504). For example, the scheduling entity 500 may correspond to Figure 1 、 2 and / or any of the base stations illustrated in 3 (e.g., eNB or gNB).

[0089] The scheduling entity 500 can be implemented using a processing system 502 that includes one or more processors, such as a processor 504. Examples of processors (e.g., processor 504) include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In some instances, the processor 504 can be implemented via a baseband or modem chip, while in other implementations, the processor 504 itself can include several devices distinct and separate from the baseband or modem chip (e.g., which can work together in such scenarios to achieve the examples discussed herein). As mentioned above, various hardware arrangements and components outside of the baseband modem processor can be used in implementations, including RF chains, power amplifiers, modulators, buffers, interleavers, adders / summers, etc. In various examples, the scheduling entity 500 can be configured to perform any one or more of the functions described herein. That is, the processor 504 as utilized in the scheduling entity 500 may be used to implement the processes described below and, for example, in Figure 11-15 Any one or more of the processes described in the text.

[0090] In this example, processing system 502 may be implemented using a bus architecture generally represented by bus 506. Depending on the specific application and overall design constraints of processing system 502, bus 506 may include any number of interconnecting buses and bridges. Bus 506 communicatively couples various circuits including one or more processors (generally represented by processor 504), memory 508, and computer-readable media (generally represented by computer-readable storage media 510). Computer-readable storage media 510 may be referred to as non-transitory computer-readable storage media. Computer-readable storage media 510 may store computer-executable code. Computer-executable code may include code that causes a computer (e.g., a processor of a computer) to perform one or more of the functions described herein. Bus 506 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further. Bus interface 512 provides an interface between bus 506 and transceiver 514. Transceiver 514 may be a wireless transceiver. The transceiver 514 provides a communication interface or means for communicating with various other equipment over a transmission medium. An antenna or antenna array (not shown) may be coupled to the transceiver 514 to transmit energy to and receive energy from the transmission medium. Depending on the characteristics of the equipment, a user interface 516 (e.g., a keypad, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 516 is optional and may be omitted in some examples (such as a base station).

[0091] The processor 504 is responsible for managing the bus 506 and general processing, including the execution of software stored on the computer-readable storage medium 510. The software, when executed by the processor 504, causes the processing system 502 to perform the various functions described below for any particular implementation. The computer-readable storage medium 510 and the memory 508 may also be used to store data that is manipulated by the processor 504 when executing the software.

[0092] One or more processors (such as processor 504 in processing system 502) can execute software. Software should be construed broadly to mean instructions, an instruction set, code, a code segment, program code, a program, a subroutine, a software module, an application, a software application, a software package, a routine, a subroutine, an object, an executable, a thread of execution, a procedure, a function, etc., whether referred to as software, firmware, middleware, microcode, a hardware description language, or other terms. The software may reside on a computer-readable storage medium 510. The computer-readable storage medium 510 may be a non-transitory computer-readable storage medium. By way of example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, flash memory devices (e.g., card, stick, or key-type drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer-readable storage medium 510 can reside in processing system 502, external to processing system 502, or distributed across multiple entities including processing system 502. Computer-readable storage medium 510 can be embodied in a computer program product. By way of example, a computer program product can include computer-readable storage medium 510 in packaging materials. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the specific application and the overall design constraints imposed on the overall system.

[0093] In some aspects of the present disclosure, the processor 504 may include a communication and processing circuit system 540 configured for various functions, including, for example, communicating with a scheduled entity (e.g., a UE), a network core (e.g., a 5G core network), or any other entity (such as, for example, local infrastructure). In some examples, the communication and processing circuit system 540 may include one or more hardware components that provide a physical structure for performing processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). The communication and processing circuit system 540 may also be configured to execute communication and processing instructions 560 (e.g., software) stored on the computer-readable storage medium 510 to implement one or more functions described herein, including the following in conjunction with Figure 7-16 Describes one or more features.

[0094] In some aspects of the present disclosure, the processor 504 may include a ranking obtaining circuitry 542 configured for various functions, including, for example, obtaining a first priority ranking of first uplink (UL) data for transmission from a first scheduled entity, such as Figure 6 The scheduled entity 600, Figure 7 710, Figure 8 810, Figure 9 912, or Figure 10 1012) to the first UL data transmission of the scheduling entity 500. The scheduling entity may correspond to any of the scheduling entities described herein, such as Figure 5 Scheduling entity 500, Figure 7 702, Figure 8 802, Figure 9 902 and Figure 10 Additionally or alternatively, the ranking obtaining circuitry 542 may be configured for various functions, including, for example, obtaining a second priority ranking of second data (e.g., sidelink data) scheduled for transmission from a second scheduled entity (e.g., Figure 6 The scheduled entity 600, Figure 7 712, Figure 8 812, Figure 9 904 or Figure 10 1004) to a third scheduled entity (such as Figure 6 The scheduled entity 600, Figure 7 708, Figure 8 804, Figure 9 906 and Figure 10 The transmission from the second scheduled entity to the third scheduled entity may use at least a portion of the sidelink resources (e.g., predetermined frequency and time resources). The sidelink resources may be reserved for sidelink communications. For example, the ranking circuit system 542 may be configured to implement the following regarding, for example Figure 11 (including blocks 1102 and 1104), Figure 12 (including blocks 1202 and 1204), Figure 13 (including blocks 1302 and 1304), Figure 14 (including blocks 1402 and 1404) or Figure 15 (including blocks 1502 and 1504). The ranking circuit system 542 may also be configured to execute the ranking instructions 562 (e.g., software) stored on the computer-readable storage medium 510 to implement one or more functions described herein, including the following with respect to, for example, Figure 11 (including blocks 1102 and 1104), Figure 12 (including blocks 1202 and 1204), Figure 13 (including blocks 1302 and 1304), Figure 14 (including blocks 1402 and 1404) or Figure 15 (including blocks 1502 and 1504) to describe one or more functions.

[0095] In some aspects of the present disclosure, the processor 504 may include a transmission scheduling circuit system 544, which is configured to perform various functions, including, for example, using at least a portion of the side link resources to schedule a first UL data transmission of the first UL data and / or using the at least a portion of the side link resources to schedule a second data transmission of the second data. The scheduling may occur in view of the priority ranking. For example, the transmission scheduling circuit system 544 may use at least a portion of the side link resources to schedule a first UL data transmission of the first UL data and / or use the side link resources to schedule the transmission of the second data based on the first priority ranking and the second priority ranking. According to some aspects, if the first priority ranking indicates a higher priority than the second priority ranking, the scheduling circuit system 544 may use the side link resources to schedule the transmission of the second data. For example, the transmission scheduling circuit system 544 may be configured to implement the following with respect to, for example Figure 11 (including block 1106), Figure 12 (including blocks 1206 and 1208 and / or 1210), Figure 13 (including blocks 1312 and / or 1314), Figure 14 (including block 1406) or Figure 15 (including blocks 1506 and 1508 and / or 1510) to perform one or more functions described herein. The transmission scheduling circuitry 544 may also be configured to execute transmission scheduling instructions 564 (e.g., software) stored on the computer-readable storage medium 510 to implement one or more functions described herein, including those described below with respect to, for example, Figure 11 (including block 1106), Figure 12 (including blocks 1206 and 1208 and / or 1210), Figure 13 (including blocks 1312 and / or 1314), Figure 14 (including block 1406) or Figure 15 (including blocks 1506 and 1508 and / or 1510) describing one or more functions.

[0096] In some aspects of the present disclosure, the processor 504 may include a ranking comparison circuitry 546 configured for various functions, including, for example, comparing a first priority ranking (e.g., a first ranking value) to a second priority ranking (e.g., a second ranking value) to determine whether the first priority ranking represents a higher priority than the second priority ranking. For example, the ranking comparison circuitry 546 may be configured to implement the following description of, for example, Figure 11(including block 1106), Figure 12 (including block 1206), Figure 13 (including block 1308), Figure 14 (including block 1406), Figure 15 (including block 1506). The ranking comparison circuitry 546 may also be configured to execute ranking comparison instructions 566 (e.g., software) stored on the computer-readable storage medium 510 to implement one or more functions described herein, including those described below with respect to, for example, Figure 11 (including block 1106), Figure 12 (including block 1206), Figure 13 (including block 1308), Figure 14 (including block 1406) or Figure 15 (including block 1506 ) describes one or more functions.

[0097] In some aspects of the present disclosure, the processor 504 may include an interference level prediction circuit system 548 configured for various functions, including, for example, predicting an interference level caused at the scheduling entity due to the second data transmission (of the second data from the second scheduled entity). For example, the interference level prediction circuit system 548 may be configured to implement the following with respect to, for example Figure 12 (including block 1214), Figure 13 (including block 1310) or Figure 15 (including block 1514). The interference level prediction circuitry 548 may also be configured to execute interference level instructions 568 (e.g., software) stored on the computer-readable storage medium 510 to implement one or more functions described herein, including those described below with respect to, for example, Figure 12 (including block 1214), Figure 13 (including block 1310) or Figure 15 (including block 1514) describes one or more functions.

[0098] In some aspects of the present disclosure, the processor 504 may include a transmission cancellation indication circuit system 550, which is configured for various functions, including, for example, generating a transmission cancellation indication and / or sending the transmission cancellation indication to a scheduled entity to cancel the transmission of first data (e.g., first sidelink data), second data (e.g., second sidelink data), or first data and / or first UL data (e.g., URLLC data). In one example, if the second data transmission will conflict with the first UL data transmission in at least one of frequency or time, the transmission cancellation indication circuit system 550 may send a transmission cancellation indication to cancel the second data transmission (of the second data). In another example, the transmission cancellation indication circuit system 550 may send a transmission cancellation indication to cancel the second data transmission (of the second data) or the first UL data, for example based on a priority ranking of each of the second data and the first UL data. In another example, the transmission cancellation indication circuit system 550 may send a transmission cancellation indication to cancel the second data transmission of the second data or the first UL data, for example based on a predicted interference level. For example, the transmission cancellation indication circuit system 550 may be configured to implement the following description of, for example Figure 12 (including blocks 1212 and 1216), Figure 13 (including blocks 1306, 1308, 1310, and 1316) or Figure 15 (including blocks 1514 and 1516). The transmission cancellation indication circuit system 550 may also be configured to execute the transmission cancellation indication instructions 570 (e.g., software) stored on the computer-readable storage medium 510 to implement one or more functions described herein, including the following with respect to, for example, Figure 12 (including blocks 1212 and 1216), Figure 13 (including blocks 1306, 1308, 1310, and 1316) or Figure 15 (including blocks 1514 and 1516) to perform one or more of the functions described.

[0099] In some aspects of the present disclosure, the processor 504 may include a data conflict determination circuit system 552 that is configured for various functions, including, for example, determining whether a first data transmission will conflict with a first UL data transmission in at least one of frequency or time. In another example, the data conflict determination circuit system 552 may be configured for various functions, including, for example, determining whether a first data (e.g., first sidelink data) and a second data (e.g., second sidelink data), or a first data transmission and a first UL data transmission will conflict in at least one of frequency or time. For example, the data conflict determination circuit system 552 may be configured to implement the following with respect to, for example Figure 13 (including block 1306) or Figure 15(including block 1512). The data conflict determination circuitry 552 may also be configured to execute data conflict determination instructions 572 (e.g., software) stored on the computer-readable storage medium 510 to implement one or more functions described herein, including those described below with respect to, for example, Figure 13 (including block 1306) or Figure 15 (including block 1512) describes one or more functions.

[0100] In some aspects of the present disclosure, the processor 504 may include a preemption indication circuit system 554 configured for various functions, including, for example, sending a preemption indication to one or more scheduled entities, or, for example, sending a preemption indication to indicate that a receiving scheduled entity (including a third scheduled entity) is to ignore data received during the at least a portion of the sidelink resource. For example, the preemption indication circuit system 554 may be configured to implement the following with respect to, for example Figure 12 (including frame 1218), Figure 13 (including block 1318) or Figure 15 (including block 1518). The preemption indication circuitry 554 may also be configured to execute preemption indication instructions 574 (e.g., software) stored on the computer-readable storage medium 510 to implement one or more functions described herein, including those described below with respect to, for example, Figure 12 (including frame 1218), Figure 13 (including block 1318) or Figure 15 (including block 1518) describes one or more functions.

[0101] Figure 6 is a block diagram illustrating an example of a hardware implementation of a scheduled entity 600 (e.g., a device configured as a scheduled entity) according to some aspects of the present disclosure. According to various aspects of the present disclosure, an element, or any portion of an element, or any combination of elements may be implemented with a processing system 602 including one or more processors (such as processor 604). For example, the scheduled entity 600 may correspond to Figure 1 、 2 and / or any of the scheduled entities illustrated in 3 (e.g., UE).

[0102] The scheduled entity 600 may be implemented using a processing system 602. The processing system 602 may be implemented with Figure 5 The processing system 502 is substantially the same as that described in , including a bus interface 612, a bus 606, a memory 608, a processor 604, and a computer-readable storage medium 610. The computer-readable storage medium 610 may be a non-transitory computer-readable storage medium. In addition, the scheduled entity 600 may include the same as described above in Figure 5That is, the processor 604 as utilized in the scheduled entity 600 may be used to implement the processes described below and, for example, in Figure 16 Any one or more of the processes described in the text.

[0103] In some aspects of the present disclosure, the processor 604 may include a communication and processing circuit system 640 configured for various functions, including, for example, communicating with a scheduling entity (e.g., a base station, eNB, gNB), another scheduled entity (e.g., a UE), or any other entity (such as, for example, local infrastructure). In some examples, the communication and processing circuit system 640 may include one or more hardware components that provide a physical structure for performing processes related to wireless communication (e.g., signal reception and / or signal transmission) and signal processing (e.g., processing received signals and / or processing signals for transmission). The communication and processing circuit system 640 may also be configured to execute communication and processing instructions 660 (e.g., software) stored on the computer-readable storage medium 610 to implement one or more functions described herein, including the following in conjunction with Figure 7-16 Describes one or more features.

[0104] In some aspects of the present disclosure, the processor 604 may include an instruction receiving circuit system 642 configured for various functions, including, for example, receiving an instruction from a scheduling entity to cancel the transmission of first data, the first data being scheduled for transmission using at least a portion of the side link resources reserved for side link communication. For example, the instruction receiving circuit system 642 may be configured to implement the following description of Figure 16 (including, for example, block 1602) to perform one or more functions described herein. The instruction receiving circuit system 642 may also be configured to execute instruction receiving instructions 662 (e.g., software) stored on the computer-readable storage medium 610 to implement one or more functions described herein, including the following with respect to Figure 16 (including, for example, block 1602) describing one or more functions.

[0105] In some aspects of the present disclosure, the processor 604 may include a transmission cancellation circuit system 644 configured for various functions, including, for example, canceling a transmission based on a received instruction. For example, the transmission cancellation circuit system 644 may be configured to implement the following description of Figure 16 The transmission cancellation circuitry 644 may also be configured to execute transmission cancellation instructions 664 (e.g., software) stored on the computer-readable storage medium 610 to implement one or more functions described herein, including those described below with respect to Figure 16 (including, for example, block 1604) describing one or more functions.

[0106] In some aspects of the present disclosure, the processor 604 may include a preemption indication circuit system 646 configured for various functions, including, for example, sending a preemption indication to at least one of the plurality of scheduled entities to indicate that the at least one of the plurality of scheduled entities will ignore data (e.g., signals) received during the side link resource in view of the cancellation of the corresponding transmission, or, for example, sending a preemption indication to indicate that the receiving scheduled entity (including the third scheduled entity) will ignore data received during the at least a portion of the side link resource. For example, the preemption indication circuit system 646 may be configured to implement the following description of Figure 16 The preemption indication circuitry 646 may also be configured to execute preemption indication instructions 666 (e.g., software) stored on the computer-readable storage medium 610 to implement one or more functions described herein, including those described below with respect to Figure 16 (including, for example, block 1606) describing one or more functions.

[0107] Currently, Downlink Control Information (DCI) format 2_1 provides a way to send a preemption indication to a group of UEs (scheduled entities) to inform the group of UEs that physical resource blocks (PRBs) and OFDM symbols intended for the UE are not being transmitted. A preemption indication is a mechanism by which a gNB informs a UE that it is scheduled to transmit downlink data traffic to the UE, but that it is not transmitting downlink data traffic because some URLLC data traffic is being transmitted instead. Therefore, a preemption indication informs the UE to refrain from decoding the data it finds in its scheduled downlink resources because the scheduled downlink resources are no longer available to the UE.

[0108] Additionally, in the uplink direction, if the first UE is scheduled to transmit uplink data (e.g., normal uplink data, such as eMBB uplink data) to the gNB in the first sidelink resources, but the second UE needs to transmit uplink URLLC data in the same resources, the gNB may schedule the uplink URLLC data of the second UE for transmission in the transmit uplink resources of the first UE, and will send a cancellation indication to the first UE to notify the first UE that its uplink transmission resources are cancelled.

[0109] In a wireless communication system, for example, considering time division duplex (TDD) uplink time slots, the uplink time slots may be scheduled by a network access node (e.g., a gNB, a scheduling entity) for uplink transmissions from a UE (e.g., a scheduled entity) to the network access node. Additionally, for transmissions between UEs (e.g., sidelink communications) using Mode 1, for example, the network access node (gNB) schedules sidelink activity. That is, using the example of Mode 1, the scheduling entity schedules sidelink communications.

[0110] In the context of URLLC and sidelink communications, three different scenarios may exist. According to the first scenario, uplink URLLC data (which is URLLC traffic from a scheduled entity toward a scheduling entity) arrives at a buffer at the source (e.g., a UE, a scheduled entity). The uplink URLLC data may need to be transmitted to the scheduling entity using frequency and time resources scheduled for sidelink communications. In the first scenario, the uplink URLLC data may preempt sidelink data (e.g., non-URLLC sidelink data, such as sidelink eMBB data).

[0111] According to the second scenario, sidelink URLLC data (e.g., high-priority sidelink data) arrives at a buffer at the scheduled entity. The URLLC data may need to be transmitted in at least a portion of the sidelink resources that have been scheduled for normal sidelink data (e.g., non-URLLC sidelink data, such as sidelink eMBB data, or low-priority sidelink data). In this scenario, the sidelink URLLC data may preempt the scheduled normal sidelink data transmission.

[0112] According to a third scenario, sidelink URLLC data (e.g., high-priority sidelink data) arrives at a buffer at the scheduled entity. The URLLC data may need to be transmitted in at least a portion of the sidelink resources that have been scheduled for normal uplink data (e.g., for eMBB uplink transmission from the scheduled entity to the scheduling entity). In this scenario, the sidelink URLLC data may preempt the scheduled normal uplink data transmission.

[0113] As described herein, there may be two priority levels: normal (low) and URLLC (high); however, adding levels and grading the levels may also be possible. For example, in sidelink transmissions, there may be three bits for indicating up to 8 priority levels. For sidelink data to preempt other sidelink data, the three bits for each sidelink transmission can be compared. For uplink data (e.g., data transmitted from a scheduled entity to a scheduling entity) compared to sidelink data, there is currently no known method for comparing priorities because the three bits for sidelink priority are not used to compare with uplink priority.

[0114] According to one aspect described herein, a comparison method for uplink data compared to sidelink data may be referred to herein as "thresholding". When thresholding is implemented, a lower priority may be attributed to sidelink data having a priority between 0 and 5 (e.g., a low priority) than a priority between 6 and 7 (e.g., a high priority). According to an exemplary aspect, sidelink data with a priority between 0 and 5 may not be able to preempt uplink data, while sidelink data with a priority between 6 and 7 may be able to preempt uplink data; however, uplink URLLC data may preempt sidelink data of any priority, and sidelink URLLC data (e.g., sidelink high priority data) may preempt normal (e.g., eMBB, non-URLLC) uplink data. The above is exemplary, and other priority sorting and comparisons fall within the scope of this disclosure.

[0115] Figure 7 is a schematic illustration of an example of a wireless communication system 700 according to some aspects of the present disclosure. The wireless communication system 700 includes a scheduling entity 702 (such as Figure 5 Scheduling entity 500, or Figure 1 、 2 or a network access node or gNB of any one of Mode 1 or 3). In some examples, the scheduling entity 702 schedules sidelink communications (e.g., sidelink data). The sidelink data may be of normal priority (e.g., eMBB data) or high priority (e.g., URLLC data). The sidelink data may be assigned a priority ranking (e.g., a ranking value from 0 to 7). As in the example of Mode 1 sidelink operation, the scheduling entity 702 may allocate sidelink resources for the sidelink communications. According to some examples, the scheduling entity 702 allocates frequency and time resources for the sidelink communications in the same space (same frequency and time resources) that would otherwise be used for uplink transmissions from user equipment (e.g., scheduled entities 704, 706, 708, 710, 712) to the scheduling entity 702 (e.g., a network access node or gNB).

[0116] exist Figure 7In the schematic illustration of , high priority URLLC uplink data traffic (e.g., first uplink data) needs to be sent from the first scheduled entity 710 to the scheduling entity 702. The high priority URLLC uplink data traffic or the first uplink data is represented by a transmitted radiation lobe 716 emitted from the first scheduled entity 710. In some examples, it may be necessary to schedule the first uplink data during the side link resources allocated for side link communication. Similar to the first scenario previously described, uplink communication may preempt side link communication. According to one aspect, the scheduling entity 702 has a first priority ranking of uplink data (first UL data) and a second priority ranking of side link data (represented by the transmitted radiation lobe 718), which is scheduled for transmission from the second scheduled entity 712 to the third scheduled entity 708 using at least a portion of the side link resources reserved for side link communication.

[0117] In other words, according to one aspect, the scheduling entity 702 obtains a first priority ranking (see transmit radiation lobe 716) for first uplink (UL) data for a first UL data transmission from the first scheduled entity 710 to the scheduling entity 702. The scheduling entity 702 obtains a second priority ranking (see transmit radiation lobe 718) for second data scheduled for a second data transmission from the second scheduled entity 712 to the third scheduled entity 708 using at least a portion of the sidelink resources reserved for sidelink communication. If the first priority ranking indicates a higher priority than the second priority ranking, the scheduling entity 702 schedules the transmission of the first UL data using at least a portion of the sidelink resources.

[0118] For illustrative purposes, high priority URLLC uplink data traffic (e.g., first UL data) is represented as a solid transmit radiation lobe 716 emanating from the first scheduled entity 710, while sidelink data (e.g., first data) is represented as a dashed transmit radiation lobe 718 emanating from the second scheduled entity 712. Beamforming to receive the first UL data is represented as a solid receive radiation lobe 714 emanating from the scheduling entity 702, while beamforming to receive the first data is represented as a dashed receive radiation lobe 720 emanating from the scheduled entity 708. Figure 7 The scheduled entities 704, 706, 708, 710, 712 can be scheduled to transmit or receive in the sidelink resources. These scheduled entities 704, 706, 708, 710, 712 can be collectively referred to as a sidelink network 722.

[0119] because Figure 7Given the geometry of the respective entities in [ 710 ], there is no need to send a cancellation indication to the scheduled entity 712 because the transmit radiation lobe 718 of the scheduled entity 712 is perpendicular to the transmit radiation lobe 716 of the scheduled entity 710. Therefore, the signals transmitted from either scheduled entity can be received by their respective receivers at very low power, and there may not be obvious interference between the first UL data and the first data in the frequency domain or time domain. For the same or similar reasons, the predicted interference level (or measured interference level) caused at the scheduling entity 702 due to the second data transmission (second data from the second scheduled entity 712) may be small and unlikely to cross any predetermined interference power threshold. Accordingly, there may be no need to cancel the transmission of the first data from the scheduled entity 712.

[0120] Figure 8 is a schematic illustration of another example of a wireless communication system 800 according to some aspects of the present disclosure. The wireless communication system 800 includes a scheduling entity 802 (such as Figure 5 Scheduling entity 500, or Figure 1 、 2 or a network access node or gNB of any one of 3). The scheduling entity 802 schedules sidelink communications (e.g., sidelink data). The sidelink data may be of normal priority (e.g., eMBB data) or high priority (e.g., URLLC data). The sidelink data may be assigned a priority ranking (e.g., a ranking value from 0 to 7). As in the example of mode 1 sidelink operation, the scheduling entity 802 may allocate sidelink resources for the sidelink communications. According to some examples, the scheduling entity 802 allocates frequency and time resources for the sidelink communications in the same space (same frequency and time resources) that would otherwise be used for uplink transmissions from user equipment (e.g., scheduled entities 804, 806, 808, 810, 812) to the scheduling entity 802.

[0121] exist Figure 8In the schematic illustration of , high priority URLLC uplink data traffic (e.g., first uplink data) needs to be sent from the first scheduled entity 810 to the scheduling entity 802. The high priority URLLC uplink data traffic or the first uplink data is represented by a transmitted radiation lobe 816 emitted from the first scheduled entity 810. It may be necessary to schedule the first uplink data during the sidelink resources allocated for sidelink communication. Similar to the first scenario previously described, uplink communication may preempt sidelink communication. According to one aspect, the scheduling entity 802 has a first priority ranking of uplink data (first UL data) and a second priority ranking of sidelink data (represented by the transmitted radiation lobe 818), which is scheduled for transmission from the second scheduled entity 812 to the third scheduled entity 804 using at least a portion of the sidelink resources reserved for sidelink communication.

[0122] In other words, according to one aspect, the scheduling entity 802 obtains a first priority ranking (see transmitted radiation lobe 816) for first uplink (UL) data for a first UL transmission from a first scheduled entity 810 to the scheduling entity 802. The scheduling entity 802 obtains a second priority ranking (see transmitted radiation lobe 818) for second data scheduled for a second data transmission from a second scheduled entity 812 to a third scheduled entity 808 using at least a portion of the sidelink resources reserved for sidelink communication. The scheduling entity 802 may schedule the transmission of the first UL data using at least a portion of the sidelink resources based on the first priority ranking and the second priority ranking. For example, if the first priority ranking indicates a higher priority than the second priority ranking, the scheduling entity 802 may schedule the transmission of the first UL data using the at least a portion of the sidelink resources.

[0123] For illustrative purposes, high priority URLLC uplink data traffic (e.g., first UL data) is represented as a solid transmit radiation lobe 816, while sidelink data (e.g., first data) is represented as a dashed transmit radiation lobe 818. Beamforming for receiving the first UL data is represented as a solid receive radiation lobe 814 emanating from the scheduling entity 802, while beamforming for receiving the first data is represented as a dashed receive radiation lobe 820 emanating from the scheduled entity 804. Scheduled entities 806, 808, 810, 812 are all scheduled entities that are scheduled to transmit or receive in the side link resources and may be referred to as a sidelink network 822.

[0124] because Figure 8The scheduling entity 802 may send a cancellation indication to the scheduled entity 812 because the transmit radiation lobe 818 of the scheduled entity 812 and the receive radiation lobe 814 of the scheduling entity 802 are substantially aligned, and thus the signal transmitted from the scheduled entity 812 may interfere with the receive radiation lobe 814 of the scheduling entity 802 receiving the signal transmitted from the first scheduled entity 810. For the same or similar reasons, data collision between the first UL data transmitted from the scheduled entity 810 and the first data transmitted from the scheduled entity 812 may occur in at least one of frequency or time.

[0125] Figure 9 is a schematic illustration of another example of a wireless communication system 900 according to some aspects of the present disclosure. The wireless communication system 900 includes a scheduling entity 902 (such as Figure 5 Scheduling entity 500, or Figure 1 、 2 or a network access node or gNB of any one of 3). The scheduling entity 902 schedules sidelink communications (e.g., sidelink data). The sidelink data may be of normal priority (e.g., eMBB data) or high priority (e.g., URLLC data). The sidelink data may be assigned a priority ranking (e.g., a ranking value from 0 to 7). As in the example of mode 1 sidelink operation, the scheduling entity 902 may allocate sidelink resources for the sidelink communications. According to some examples, the scheduling entity 902 allocates frequency and time resources for the sidelink communications in the same space (same frequency and time resources) that would otherwise be used for uplink transmissions from user equipment (e.g., scheduled entities 904, 906, 908, 910, 912) to the scheduling entity 902. The scheduled entities 904, 906, 908, 910, 912 are all scheduled entities that are scheduled to transmit or receive in the sidelink resources and may be referred to as a sidelink network 922.

[0126] exist Figure 9In the schematic illustration of , high priority URLLC sidelink data (e.g., first data) needs to be sent from the first scheduled entity 912 to the second scheduled entity 904. The high priority URLLC sidelink data or the first data is represented by the transmitted radiation lobe 918 emitted from the first scheduled entity 912. In some examples, it may be necessary to schedule the first data during the side link resources allocated for the side link communication. Similar to the second scenario previously described, the high priority URLLC sidelink data or the first data may preempt another side link communication (e.g., the second data). According to one aspect, the scheduling entity 902 may obtain a first priority ranking for the first data and a second priority ranking for the second data (e.g., side link data represented by the transmitted radiation lobe 920), the second data being scheduled for transmission from the third scheduled entity 906 to the fourth scheduled entity 910 using at least a portion of the side link resources reserved for the side link communication.

[0127] The first scheduled entity 912 may transmit some indication of the sorting priority of the first data to the scheduling entity 902. Accordingly, the scheduling entity 902 may obtain (e.g., receive) at least one of a scheduling request (SR) or a buffer status report (BSR) 924 from the first scheduled entity 912. The SR and / or BSR may indicate the sorting priority of the first data. The scheduling entity 902 knows the sorting priority of the sidelink second data (represented by the transmit radiation lobe 920) (e.g., eMBB, non-URLLC, or low-priority data) because the scheduling entity 902 scheduled the second data. Based on these sorting priorities, the scheduling entity 902 may schedule the first data and may send a transmission cancellation indication (CI) 926 to the third scheduled entity 906. The transmission cancellation indication CI 926 may be used to cancel the transmission of the second data. For example, if the second data transmission will conflict with the first data transmission in at least one of frequency or time, the transmission cancellation indication may be sent. The CI 926 may stop the transmission of the second data and prevent interference with the first data. In another example, a preemption indication (PI) may be sent to the receiving scheduled entity. The PI may be sent from the scheduling entity 902 or the first scheduled entity 912. The CI and PI may be based on at least one of a scheduled entity interference graph or a scheduled entity resource schedule.

[0128] Figure 10 is a schematic illustration of another example of a wireless communication system 1000 according to some aspects of the present disclosure. The wireless communication system 1000 includes a scheduling entity 1002 (such as Figure 5 Scheduling entity 500, or Figure 1 、 2or a network access node or gNB of any one of 3). Scheduling entity 1002 schedules sidelink communications (e.g., sidelink data). Sidelink data may be of normal priority (e.g., eMBB data) or high priority (e.g., URLLC data). Sidelink data may be assigned a priority ranking (e.g., a ranking value from 0 to 7). As in the example of mode 1 sidelink operation, scheduling entity 1002 may allocate sidelink resources for sidelink communications. According to some examples, scheduling entity 1002 allocates frequency and time resources for sidelink communications in the same space (same frequency and time resources) that would otherwise be used for uplink transmissions from user equipment (e.g., scheduled entities 1004, 1006, 1008, 1010, 1012) to scheduling entity 1002. Scheduled entities 1004, 1006, 1008, 1010, 1012 are all scheduled entities that are scheduled to transmit or receive in the sidelink resources and may be referred to as sidelink network 1022.

[0129] exist Figure 10 In the schematic illustration of , high priority URLLC sidelink data (e.g., first data) needs to be sent from the first scheduled entity 1012 to the second scheduled entity 1004. The high priority URLLC sidelink data or the first data is represented by a transmitted radiation lobe 1018 emitted from the first scheduled entity 1012. In some examples, it may be necessary to schedule the first data during the sidelink resources allocated for sidelink communication. Similar to the third scenario previously described, the high priority URLLC sidelink data or the first data may preempt uplink data (e.g., first UL data). The first UL data is represented by a transmitted radiation lobe 1020 emitted from the third scheduled entity 1010. According to one aspect, the scheduling entity 1002 obtains a first priority ranking for the first data and a second priority ranking for the first UL data (e.g., uplink data represented by the transmitted radiation lobe 1020), and the first UL data is scheduled for transmission from the third scheduled entity 1010 to the scheduling entity 1002 using at least a portion of the sidelink resources reserved for uplink communication.

[0130] The first scheduled entity 1012 may transmit some indication of a ranking priority of the first data to the scheduling entity 1002. Accordingly, the scheduling entity 1002 may obtain (e.g., receive) at least one of a scheduling request (SR) or a buffer status report (BSR) 1024 from the first scheduled entity 1012. The SR and / or BSR may indicate the ranking priority of the first data. The scheduling entity 1002 is aware of the ranking priority of the uplink first UL data (represented by the transmitted radiation lobe 1020) (e.g., eMBB, non-URLLC, or low priority data) because the scheduling entity 1002 scheduled the first UL data. Based on these ranking priorities, the scheduling entity 1002 may schedule the first data and may send a transmission cancellation indication (CI) 1026 to the third scheduled entity 1010. The transmission cancellation indication may be used to cancel the transmission of the first UL data. For example, the transmission cancellation indication may be sent if the first data transmission will conflict with the first UL data transmission in at least one of frequency or time. The CI 1026 may stop transmission of the first UL data and prevent interference with the first data at the second scheduled entity 1004. In another example, a preemption indication (PI) may be sent to the receiving scheduled entity. The PI may be sent from the scheduling entity 1002 or the first scheduled entity 1012. The CI and the PI may be based on at least one of a scheduled entity interference graph or a scheduled entity resource schedule.

[0131] Figure 11 is a flow chart illustrating an exemplary method 1100 (e.g., process) for wireless communication at a scheduling entity in a wireless communication network according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1100 may be respectively Figure 5 The scheduling entity 500 or Figure 7-10 The method 1100 may be performed by any scheduling entity 702, 802, 902, 1002. In some examples, the method 1100 may be performed by any suitable device or apparatus for implementing the functions or algorithms described below.

[0132] At block 1102, the scheduling entity may obtain a first priority ranking for first uplink (UL) data, the first UL data being used for a first UL transmission from a first scheduled entity to the scheduling entity. At block 1104, the scheduling entity may obtain a second priority ranking for second data, the second data being scheduled for a second data transmission from a second scheduled entity to a third scheduled entity using at least a portion of sidelink resources reserved for sidelink communication. At block 1106, the scheduling entity may schedule the transmission of the first UL data using the at least a portion of the sidelink resources based on the first priority ranking and the second priority ranking. For example, at block 1106, if the first priority ranking indicates a higher priority than the second priority ranking, the scheduling entity may schedule the transmission of the first UL data using the at least a portion of the sidelink resources.

[0133] According to some aspects, the method 1100 may further include obtaining at least one of the first priority ranking or the second priority ranking in at least one of a scheduling request (SR) or a buffer status report (BSR) received from the first scheduled entity or the second scheduled entity, respectively. The SR and / or BSR may be received from the first scheduled entity at the scheduling entity.

[0134] Figure 12 is a flow chart illustrating another exemplary method 1200 (e.g., process) of wireless communication at a scheduling entity in a wireless communication network according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1200 may be respectively Figure 5 The scheduling entity 500 or Figure 7-10 The method 1200 may be performed by any scheduling entity 702, 802, 902, 1002. In some examples, the method 1200 may be performed by any suitable device or apparatus for implementing the functions or algorithms described below.

[0135] At block 1202, the scheduling entity may obtain a first priority ranking for first uplink (UL) data, the first UL data being used for a first UL data transmission from a first scheduled entity to the scheduling entity. At block 1204, the scheduling entity may obtain a second priority ranking for second data, the second data being scheduled for a second data transmission (from a second scheduled entity to a third scheduled entity) using at least a portion of sidelink resources reserved for sidelink communication. At block 1206, a determination may be made as to whether the first priority ranking indicates a higher priority than the second priority ranking.

[0136] If the first priority ranking does not indicate a higher priority than the second priority ranking, the scheduling entity may schedule transmission of the second data using the at least a portion of the sidelink resources at block 1208. Following block 1208, method 1200 may end.

[0137] Returning to block 1206 , if the first priority ranking indicates a higher priority than the second priority ranking, the scheduling entity may schedule transmission of the first UL data using the at least a portion of the sidelink resources at block 1210 .

[0138] At block 1212, if the second data transmission will conflict with the first UL data transmission in at least one of frequency or time, the scheduling entity may send a transmission cancellation indication to cancel the transmission of the second data after, simultaneously with, or substantially simultaneously with the scheduling of the transmission of the first UL data. Alternatively or additionally, at block 1214, the scheduling entity may predict an interference level at the scheduling entity due to the second data transmission (of the second data from the second scheduled entity). Thereafter, at block 1216, if the predicted interference level is greater than a predetermined threshold, the scheduling entity may send a transmission cancellation indication to cancel the second data transmission (of the second data). Canceling the transmission of the second data may improve the signal-to-interference ratio of the first UL data received at the second scheduled entity.

[0139] In some aspects, predicting the interference level can be accomplished using, for example, at least one of: a sidelink interference graph, a transmit beam of a second scheduled entity (e.g., information about the transmit beam, including, for example, a direction or a relative direction), or a receive beam for the first UL data of the scheduling entity (e.g., information about the receive beam, including, for example, a direction or a relative direction).

[0140] According to some aspects, method 1200 may further include sending the transmission cancellation indication to at least one of: at least the second scheduled entity, the scheduled entities including the second scheduled entity scheduled to transmit in at least a portion of the side link resources, or a portion of the scheduled entities including the second scheduled entity scheduled to transmit in at least a portion of the side link resources, which portion of the scheduled entities will cause interference to the reception of UL data.

[0141] According to some aspects, method 1200 may optionally include, at block 1218, sending a preemption indication to indicate that a receiving scheduled entity (e.g., a third scheduled entity) is to ignore data (e.g., a signal) received during the at least a portion of the sidelink resources, or, for example, sending a preemption indication to indicate that a receiving scheduled entity (including the third scheduled entity) is to ignore data, including the second data, received during the at least a portion of the sidelink resources. In some examples, the preemption indication may be sent to at least one of: at least the third scheduled entity, scheduled entities including the third scheduled entity scheduled to receive in the at least a portion of the sidelink resources, or a portion of scheduled entities including the third scheduled entity scheduled to receive in the at least a portion of the sidelink resources that may receive interference from the transmission of the first UL data.

[0142] In some aspects, method 1200 further includes instructing (e.g., causing) the second scheduled entity to send a preemption indication to indicate that a receiving scheduled entity (e.g., a third scheduled entity) is to ignore (e.g., disregard) data received during the at least a portion of the sidelink resource, or, for example, sending a preemption indication to indicate that a receiving scheduled entity, including the third scheduled entity, is to ignore data, including the second data, received during the at least a portion of the sidelink resource. In some aspects, the second scheduled entity may send the preemption indication without being instructed to do so by the scheduling entity. In other aspects, the scheduling entity may instruct the second scheduled entity to send the preemption indication to at least one of: at least the third scheduled entity, scheduled entities including the third scheduled entity scheduled to receive in the at least a portion of the sidelink resource, or a portion of scheduled entities including the third scheduled entity scheduled to receive in the at least a portion of the sidelink resource that may receive interference from the transmission of the first UL data.

[0143] In one aspect, the scheduling entity may send a transmission cancellation indication to cancel the transmission of the second data in response to: a first determination that the second data transmission (of the second data) will interfere with the first UL data transmission (of the first UL data) in frequency, time, or both; or a second determination that a predicted interference level received at the scheduling entity due to the second data transmission is greater than a predetermined threshold.

[0144] According to another aspect, an exemplary method for wireless communication at a scheduling entity according to some aspects of the present disclosure may include: obtaining a first priority ranking of first uplink (UL) data, the first UL data being used for a first UL data transmission from a first scheduled entity to the scheduling entity; obtaining a second priority ranking of second data, the second data being scheduled for a second data transmission from a second scheduled entity to a third scheduled entity using at least a portion of sidelink resources reserved for sidelink communication; and scheduling a first UL data transmission of the first UL data based on the first priority ranking and the second priority ranking. For example, if the first priority ranking indicates a higher priority than the second priority ranking, the scheduling entity may schedule the first UL data transmission using the at least a portion of the sidelink resources.

[0145] In some aspects, the method may further include obtaining a second priority ranking based on at least one of a scheduling request (SR) or a buffer status report (BSR) received from the second scheduled entity. Additionally or alternatively, the method may further include sending a transmission cancellation indication to cancel the second data transmission (of the second data) in response to: a first determination that the second data transmission will interfere with the first UL data transmission (of the first UL data) in frequency, time, or both; or a second determination that a predicted interference level received at the scheduling entity due to the second data transmission is greater than a predetermined threshold. In one aspect, the scheduling entity may use the following to predict the interference level: a sidelink interference graph, a transmit beam of the second scheduled entity, a receive beam for the first UL data of the scheduling entity, or some combination thereof. In one example, the scheduling entity may send the transmission cancellation indication to at least one of: at least the second scheduled entity, scheduled entities including the second scheduled entity that are scheduled to transmit in the at least a portion of the sidelink resources, or a portion of the scheduled entities including the second scheduled entity that are scheduled to transmit in the at least a portion of the sidelink resources, which portion of the scheduled entities will interfere with reception of the UL data.

[0146] The method may further include sending a preemption indication to indicate to a receiving scheduled entity that it will ignore data (e.g., a signal) received during the sidelink resource. In one example, the scheduling entity may send the preemption indication to at least one of: at least a third scheduled entity, scheduled entities including the third scheduled entity scheduled to receive in the sidelink resource, or a portion of scheduled entities including the third scheduled entity scheduled to receive in the sidelink resource, the portion of which will receive interference from the transmission of the first UL data.

[0147] According to yet another aspect, the method may include instructing (e.g., causing) a second scheduled entity to send a preemption indication to indicate that a receiving scheduled entity will ignore data (e.g., a signal) received during the sidelink resource. In one example, the scheduling entity may instruct the second scheduled entity to send the preemption indication to at least one of: at least a third scheduled entity, scheduled entities including the third scheduled entity scheduled to receive in the sidelink resource, or a portion of scheduled entities including the third scheduled entity scheduled to receive in the sidelink resource, the portion of which will receive interference from the transmission of the first UL data.

[0148] Figure 13 is a flow chart illustrating another exemplary method 1300 (e.g., process) of wireless communication at a scheduling entity in a wireless communication network according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1300 may be respectively Figure 5 The scheduling entity 500 or Figure 7-10 The method 1300 may be performed by any scheduling entity 702, 802, 902, 1002. In some examples, the method 1300 may be performed by any suitable device or apparatus for implementing the functions or algorithms described below.

[0149] At block 1302, the scheduling entity may obtain a first priority ranking for first data, the first data to be used for a first data transmission from a first scheduled entity to a second scheduled entity using at least a portion of sidelink resources reserved for sidelink communication. At block 1304, the scheduling entity may obtain a second priority ranking for second data, the second data to be scheduled for a second data transmission from a third scheduled entity to a fourth scheduled entity using the at least a portion of the sidelink resources. Scheduling the first data transmission using the at least a portion of the sidelink resources may occur based on the first priority ranking and the second priority ranking. According to some aspects, scheduling the first data transmission using the at least a portion of the sidelink resources may occur at block 1314 if: at block 1308, the first priority ranking indicates a higher priority than the second priority ranking, or at block 1306, the first data transmission will conflict with the second data transmission (e.g., in at least one of frequency or time), or at block 1310, a predicted interference level at the second scheduled entity from the second data transmission (of the second data from the third scheduled entity) is greater than a predetermined threshold. Thereafter, if the scheduling entity determines to schedule the first data transmission, the scheduling entity may send a transmission cancellation indication to cancel the second data transmission of the second data at block 1316. In some aspects, if the scheduling entity is scheduling the first data transmission, the scheduling entity may send a transmission cancellation to cancel the second data transmission.

[0150] However, if at box 1308 the first priority sorting does not indicate a higher priority than the second priority sorting, or if at box 1306 the first data transmission will not conflict with the second data transmission in at least one of frequency or time, or if at box 1310 the predicted interference level from the second data transmission (of the second data from the third scheduled entity) at the second scheduled entity is not greater than a predetermined threshold, the scheduling entity may use at least a portion of the side link resources at box 1312 to schedule the second data transmission of the second data.

[0151] In some aspects, method 1300 may further include at least one of: obtaining a first priority ranking in at least one of a first scheduling request (SR) or a first buffer status report (BSR) received from a first scheduled entity, or obtaining a second priority ranking in at least one of a second scheduling request (SR) or a second buffer status report (BSR) received from a third scheduled entity.

[0152] According to some other aspects, method 1300 may further include predicting the interference level using at least one of: a sidelink interference graph, sidelink scheduling, a transmit beam for transmitting second data from a third scheduled entity to a fourth scheduled entity (e.g., information about the transmit beam, such as including the direction or relative direction of the beam), or a receive beam for receiving first data from the first scheduled entity at the second scheduled entity (e.g., information about the receive beam, such as including the direction or relative direction of the beam).

[0153] In yet other aspects, method 1300 may further include sending the transmission cancellation indication to at least one of: at least a third scheduled entity, a scheduled entity including the third scheduled entity that is scheduled to transmit in at least a portion of the side link resource, or a portion of the scheduled entities including the third scheduled entity that is scheduled to transmit in at least a portion of the side link resource, which portion of the scheduled entities will cause interference to the reception of the first data at the second scheduled entity.

[0154] Following block 1316, the scheduling entity may send a preempt indication to indicate to a receiving scheduled entity (e.g., a fourth scheduled entity) that data, including the second data, received during the at least a portion of the sidelink resources, at block 1318. In accordance with some aspects, sending the preempt indication includes sending the preempt indication to at least one of: at least the fourth scheduled entity, scheduled entities including the fourth scheduled entity scheduled to receive in the at least a portion of the sidelink resources, or a portion of the scheduled entities including the fourth scheduled entity scheduled to receive in the at least a portion of the sidelink resources that will receive interference from the transmission of the first data.

[0155] In accordance with some aspects, the scheduling entity may further act by instructing (e.g., causing) a third scheduled entity to send a preempt indication to indicate that a receiving scheduled entity (e.g., a fourth scheduled entity) is to ignore data, including the second data, received during the at least a portion of the sidelink resources. In accordance with some aspects, the third scheduled entity may send the preempt indication without being instructed to do so by the scheduling entity. In some examples, the scheduling entity may instruct the third scheduled entity to send the preempt indication to at least one of: at least the fourth scheduled entity, scheduled entities including the fourth scheduled entity that are scheduled to receive in the at least a portion of the sidelink resources, or a portion of the scheduled entities including the fourth scheduled entity that are scheduled to receive in the at least a portion of the sidelink resources that will receive interference from the transmission of the first data.

[0156] Figure 14is a flow chart illustrating another exemplary method 1400 (e.g., process) of wireless communication at a scheduling entity in a wireless communication network according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1400 may be respectively Figure 5 The scheduling entity 500 or Figure 7-10 The method 1400 may be performed by any scheduling entity 702, 802, 902, 1002. In some examples, the method 1400 may be performed by any suitable device or apparatus for implementing the functions or algorithms described below.

[0157] At block 1402, the scheduling entity may obtain a first priority ranking for first data, the first data for a first data transmission from a first scheduled entity to a second scheduled entity using at least a portion of sidelink resources reserved for uplink (UL) communication at the scheduling entity. The scheduling entity may also obtain a second priority ranking for second UL data, scheduled for a second UL data transmission from a third scheduled entity to the scheduling entity using the at least a portion of the sidelink resources, at block 1404. The scheduling entity may further schedule a first data transmission of the first data based on the first priority ranking and the second priority ranking, at block 1406. For example, if the first priority ranking indicates a higher priority than the second priority ranking, the scheduling entity may schedule the first data transmission using the at least a portion of the sidelink resources.

[0158] According to some aspects, the method further includes obtaining a first priority ranking in at least one of a scheduling request (SR) or a buffer status report (BSR) received from the first scheduled entity.

[0159] Figure 15 is a flow chart illustrating another exemplary method 1500 (e.g., process) of wireless communication at a scheduling entity in a wireless communication network according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1400 may be respectively Figure 5 The scheduling entity 500 or Figure 7-10 The method 1500 may be performed by any scheduling entity 702, 802, 902, 1002. In some examples, the method 1500 may be performed by any suitable device or apparatus for implementing the functions or algorithms described below.

[0160] At block 1502, the scheduling entity may obtain a first priority ranking for first data, the first data for first data transmission from a first scheduled entity to a second scheduled entity using at least a portion of sidelink resources reserved for uplink (UL) communication. The sidelink resources reserved for UL communication may be reserved for UL communication from the scheduled entity to the scheduling entity. The scheduling entity may also obtain a second priority ranking for first UL data, the first UL data scheduled for transmission from a third scheduled entity to the scheduling entity using the at least a portion of the sidelink resources, at block 1504. Scheduling may be based on the first priority ranking and the second priority ranking. For example, at block 1506, a determination may be made as to whether the first priority ranking indicates a higher priority than the second priority ranking.

[0161] If the first priority ranking does not indicate a higher priority than the second priority ranking, the scheduling entity may schedule a first UL data transmission (of the first UL data) using the at least a portion of the sidelink resources at block 1508. Returning to block 1506, if the first priority ranking indicates a higher priority than the second priority ranking, the scheduling entity may schedule a first data transmission of the first data using the at least a portion of the sidelink resources at block 1510. After scheduling the transmission of the first data using the sidelink resources at block 1510, if the first data transmission will conflict with the first UL data transmission in at least one of frequency or time at block 1512, the scheduling entity may send a transmission cancellation indication to cancel the first UL data transmission (of the first UL data). Additionally or alternatively, the scheduling entity may predict an interference level at the second scheduled entity due to the first UL data transmission (of the first UL data from the third scheduled entity) at block 1514, and if the predicted interference level is greater than a predetermined threshold, send a transmission cancellation indication to cancel the first UL data transmission (of the first UL data) at block 1516 to improve the signal-to-interference ratio of the first data received at the second scheduled entity.

[0162] In some aspects, predicting the interference level can be accomplished using at least one of: a sidelink interference graph, or a transmit beam of first UL data for a first UL data transmission from a third scheduled entity to the scheduling entity (e.g., information about the beam, such as including a direction or a relative direction), or a receive beam of first data for a first data transmission from a first scheduled entity to a second scheduled entity (e.g., information about the beam, such as including a direction or a relative direction).

[0163] According to some aspects, a transmission cancellation indication may be sent to at least one of the following to cancel the transmission of the first UL data: at least a third scheduled entity, a scheduled entity including the third scheduled entity scheduled to transmit in the side link resource, or a portion of the scheduled entities including the third scheduled entity scheduled to transmit in the side link resource, which portion of the scheduled entities will cause interference to the reception of the first UL data at the second scheduled entity.

[0164] Figure 16 is a flow chart illustrating an exemplary method 1600 (e.g., process) for wireless communication at a first scheduled entity in a plurality of scheduled entities according to some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in certain implementations within the scope of the present disclosure, and some of the illustrated features may not be required to implement all examples. In some examples, the method 1500 may be performed by Figure 6 The scheduled entity 600 or Figure 7 Any scheduled entity 704, 706, 708, 710, 712, Figure 8 804, 806, 808, 810, 812, Figure 9 904, 906, 908, 910, 912, or Figure 10 In some examples, the method 1600 can be performed by any suitable equipment or device for implementing the functions or algorithms described below.

[0165] At block 1602, a first scheduled entity among a plurality of scheduled entities may receive an instruction from a scheduling entity to cancel transmission of first data scheduled for transmission using at least a portion of the sidelink resources reserved for sidelink communication. The first scheduled entity may cancel the transmission according to the received instruction at block 1604. The first scheduled entity may send a preemption indication to at least one other scheduled entity among the plurality of scheduled entities to indicate that the at least one other scheduled entity among the plurality of scheduled entities will ignore data (e.g., signals) received during the at least a portion of the sidelink resources at block 1606.

[0166] In accordance with some aspects, the scheduled entity may send a preemption indication to at least one of: a unique one of a plurality of scheduled entities; a scheduled entity scheduled to receive data during the side link resource; or a portion of the scheduled entities scheduled to receive data during the side link resource, which portion of the scheduled entities will receive interference from the transmission of the first UL data during the side link resource.

[0167] In one aspect, a scheduling entity (e.g., Figure 5 The scheduling entity 500 includes: means for obtaining a first priority ranking of first uplink (UL) data, the first UL data being for a first UL data transmission from a first scheduled entity to the scheduling entity; means for obtaining a second priority ranking of second data, the second data being scheduled for a second data transmission from a second scheduled entity to a third scheduled entity using at least a portion of sidelink resources reserved for sidelink communication; and means for scheduling a first UL data transmission of the first UL data using the at least a portion of the sidelink resources based on the first priority ranking and the second priority ranking. For example, means for scheduling the first UL data transmission of the first UL data using the at least a portion of the sidelink resources if the first priority ranking indicates a higher priority than the second priority ranking.

[0168] On the other hand, a scheduling entity for conducting wireless communications in a wireless communication network includes: a device for obtaining a first priority ranking of first data, the first data being used for a first data transmission from a first scheduled entity to a second scheduled entity using at least a portion of side link resources reserved for side link communication; a device for obtaining a second priority ranking of second data, the second data being scheduled for a second data transmission from a third scheduled entity to a fourth scheduled entity using the at least a portion of the side link resources; a device for scheduling the first data transmission using the at least a portion of the side link resources when: the first priority ranking indicates a higher priority than the second priority ranking, the first data transmission will conflict with the second data transmission (for example, in at least one of frequency or time), or the predicted interference level of the second data transmission (of the second data from the third scheduled entity) at the second scheduled entity is greater than a predetermined threshold; and a device for sending a transmission cancellation indication to cancel the transmission of the second data.

[0169] In yet another aspect, a scheduled entity (e.g., Figure 6 The scheduled entity 600 includes: a device for receiving an instruction from a scheduling entity to cancel the transmission of first data, the first data being scheduled for transmission using at least a portion of the side link resources reserved for side link communication; a device for canceling the transmission according to the received instruction; and a device for sending a preemption indication to at least one other scheduled entity of the multiple scheduled entities to indicate that the at least one other scheduled entity of the multiple scheduled entities will ignore data (e.g., a signal) received during the at least a portion of the side link resources in view of canceling the transmission.

[0170] In any of the above aspects, the aforementioned devices may be respectively Figure 5 and Figure 6The processor 504 and / or the processor 604 shown in the figure are configured to perform the functions described by the aforementioned means. Additionally or alternatively, in any of the above aspects, the aforementioned means may be a circuit or any equipment configured to perform the functions described by the aforementioned means.

[0171] Of course, in the above examples, the circuit systems included in the processor 504 and the processor 604 are provided only as examples, and other means for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 510 or the computer-readable storage medium 610, or in Figure 1 、 2 , 3 and 5-10 and using, for example, Figure 11-16 Any other suitable apparatus or device that implements the described methods, processes and / or algorithms.

[0172] The following provides an overview of the present disclosure:

[0173] Aspect 1: A method for performing wireless communication at a scheduling entity in a wireless communication network, comprising: obtaining a first priority ranking of first uplink (UL) data, the first UL data being used for a first UL data transmission from a first scheduled entity to the scheduling entity; obtaining a second priority ranking of second data, the second data being scheduled for a second data transmission from a second scheduled entity to a third scheduled entity using at least a portion of side link resources reserved for side link communication; and scheduling the first UL data transmission using the at least a portion of the side link resources based on the first priority ranking and the second priority ranking.

[0174] Aspect 2: The method of Aspect 1 further includes: using at least a portion of the side link resources to schedule a first UL data transmission when the first priority ranking indicates a higher priority than the second priority ranking; and sending a transmission cancellation indication to cancel the second data transmission when the second data transmission will conflict with the first UL data transmission.

[0175] Aspect 3: The method of Aspect 1 or 2 further includes: predicting an interference level received at the scheduling entity due to the second data transmission; and sending a transmission cancellation indication to cancel the second data transmission when the predicted interference level is greater than a predetermined threshold.

[0176] Aspect 4: The method of Aspect 3 further includes: sending the transmission cancellation indication to at least one of the following: at least the second scheduled entity, the scheduled entity including the second scheduled entity scheduled to transmit in at least a part of the side link resource, or a part of the scheduled entities including the second scheduled entity scheduled to transmit in at least a part of the side link resource, which part of the scheduled entities will cause interference to the reception of the first UL data.

[0177] Aspect 5: The method of any one of Aspects 1 to 4, further comprising: sending a preemption indication to indicate that the receiving scheduled entities including the third scheduled entity will ignore data including the second data received during the at least a portion of the side link resources.

[0178] Aspect 6: The method of any one of Aspects 1 to 5 further comprises: instructing the second scheduled entity to send a preemptive indication to indicate that the receiving scheduled entities including the third scheduled entity will ignore data including the second data received during at least a portion of the side link resource.

[0179] Aspect 7: The method of any one of Aspects 1 to 6 further includes: sending a transmission cancellation indication to cancel the second data transmission in response to: a first determination that the second data transmission will interfere with the first UL data transmission; or a second determination that the predicted interference level received at the scheduling entity due to the second data transmission is greater than a predetermined threshold.

[0180] Aspect 8: An apparatus configured as a scheduling entity for wireless communication in a wireless communication network, comprising: a processor; a transceiver communicatively coupled to the processor; and a memory communicatively coupled to the processor, wherein the processor is configured to: obtain a first priority ranking of first uplink (UL) data, the first UL data being used for a first UL data transmission from a first scheduled entity to the scheduling entity; obtain a second priority ranking of second data, the second data being scheduled for a second data transmission from a second scheduled entity to a third scheduled entity using at least a portion of side link resources reserved for side link communication; and schedule the first UL data transmission using the at least a portion of the side link resources based on the first priority ranking and the second priority ranking.

[0181] Aspect 9: An apparatus as in Aspect 8, wherein the processor is further configured to: schedule a first UL data transmission using at least a portion of the side link resources when the first priority ranking indicates a higher priority than the second priority ranking; and send a transmission cancellation indication to cancel the second data transmission when the second data transmission will conflict with the first UL data transmission.

[0182] Aspect 10: An apparatus as in Aspect 8 or 9, wherein the processor is further configured to: predict an interference level received at the scheduling entity due to the second data transmission; and send a transmission cancellation indication to cancel the second data transmission when the predicted interference level is greater than a predetermined threshold.

[0183] Aspect 11: An apparatus as in any one of Aspects 8 to 10, wherein the processor is further configured to: send the transmission cancellation indication to at least one of: at least a second scheduled entity, a scheduled entity including the second scheduled entity scheduled to transmit in at least a portion of the side link resources, or a part of the scheduled entities including the second scheduled entity scheduled to transmit in at least a portion of the side link resources, which part of the scheduled entities will cause interference to the reception of the first UL data.

[0184] Aspect 12: An apparatus as in any of Aspects 8 to 11, wherein the processor is further configured to: send a preemption indication to indicate that the receiving scheduled entities including the third scheduled entity will ignore data including the second data received during the at least a portion of the side link resources.

[0185] Aspect 13: An apparatus as in any of Aspects 8 to 12, wherein the processor is further configured to: instruct the second scheduled entity to send a preemption indication to indicate that the receiving scheduled entities including the third scheduled entity will ignore data including the second data received during at least a portion of the side link resource.

[0186] Aspect 14: An apparatus as in any one of Aspects 8 to 13, wherein the processor is further configured to: send a transmission cancellation indication to cancel the second data transmission in response to: a first determination that the second data transmission will interfere with the first UL data transmission; or a second determination that the predicted interference level received at the scheduling entity due to the second data transmission is greater than a predetermined threshold.

[0187] Aspect 15: A method for performing wireless communications at a scheduling entity in a wireless communication network, comprising: obtaining a first priority ranking of first data, the first data being used for a first data transmission from a first scheduled entity to a second scheduled entity using at least a portion of the side link resources reserved for side link communication; obtaining a second priority ranking of second data, the second data being scheduled for a second data transmission from a third scheduled entity to a fourth scheduled entity using the at least a portion of the side link resources reserved for side link communication; and scheduling a first data transmission of the first data using the at least a portion of the side link resources based on the first priority ranking and the second priority ranking.

[0188] Aspect 16: The method of Aspect 15 further includes: sending a transmission cancellation indication to cancel the second data transmission in the following circumstances: the first priority ranking indicates a higher priority than the second priority ranking, the first data transmission will conflict with the second data transmission, or the predicted interference level from the second data transmission at the second scheduled entity is greater than a predetermined threshold.

[0189] Aspect 17: The method of Aspect 15 or 16 further includes: sending the transmission cancellation indication to at least one of the following: at least a third scheduled entity, a scheduled entity including the third scheduled entity scheduled to transmit in at least a part of the side link resource, or a part of the scheduled entities including the third scheduled entity scheduled to transmit in at least a part of the side link resource, which part of the scheduled entities will cause interference to the reception of the first UL data.

[0190] Aspect 18: The method of any one of Aspects 15 to 17, further comprising: predicting the interference level using at least one of: a sidelink interference graph, sidelink scheduling, a transmit beam for transmitting second data from a third scheduled entity to a fourth scheduled entity, or a receive beam for receiving first data from the first scheduled entity at the second scheduled entity.

[0191] Aspect 19: The method of any one of Aspects 15 to 18, further comprising: sending a preemption indication to indicate that the receiving scheduled entities including the fourth scheduled entity are to ignore data including the second data received during the at least a portion of the sidelink resources.

[0192] Aspect 20: The method of any one of Aspects 15 to 19 further includes: sending the preemption indication to at least one of: at least a fourth scheduled entity, a scheduled entity including the fourth scheduled entity scheduled to receive in at least a portion of the side link resource, or a part of the scheduled entities including the fourth scheduled entity scheduled to receive in at least a portion of the side link resource, which part of the scheduled entities will receive interference from the first data transmission.

[0193] Aspect 21: The method of any one of Aspects 15 to 20, further comprising: instructing the third scheduled entity to send a preemption indication to indicate that the receiving scheduled entities including the fourth scheduled entity will ignore data including the second data received during at least a portion of the side link resource.

[0194] Aspect 22: The method of any one of Aspects 15 to 21 further includes: instructing the third scheduled entity to send the preemption indication to at least one of: at least a fourth scheduled entity, a scheduled entity including the fourth scheduled entity scheduled to receive in at least a portion of the side link resource, or a part of the scheduled entities including the fourth scheduled entity scheduled to receive in at least a portion of the side link resource, which part of the scheduled entities will receive interference from the first data transmission.

[0195] Aspect 23: An apparatus configured as a scheduling entity for wireless communication in a wireless communication network, comprising: a processor; a transceiver communicatively coupled to the processor; and a memory communicatively coupled to the processor, wherein the processor is configured to: obtain a first priority ranking of first data, the first data being used for a first data transmission from a first scheduled entity to a second scheduled entity using at least a portion of the side link resources reserved for side link communication; obtain a second priority ranking of second data, the second data being scheduled for a second data transmission from a third scheduled entity to a fourth scheduled entity using the at least a portion of the side link resources reserved for side link communication; and schedule a first data transmission of the first data using the at least a portion of the side link resources based on the first priority ranking and the second priority ranking.

[0196] Aspect 24: An apparatus as in Aspect 23, wherein the processor is further configured to: send a transmission cancellation indication to cancel the second data transmission in the following circumstances: the first priority ranking indicates a higher priority than the second priority ranking, the first data transmission will conflict with the second data transmission, or the predicted interference level from the second data transmission at the second scheduled entity is greater than a predetermined threshold.

[0197] Aspect 25: An apparatus as in Aspect 23 or 24, wherein the processor is further configured to: send the transmission cancellation indication to at least one of: at least a third scheduled entity, a scheduled entity including the third scheduled entity scheduled to transmit in at least a portion of the side link resources, or a part of the scheduled entities including the third scheduled entity scheduled to transmit in at least a portion of the side link resources, which part of the scheduled entities will cause interference to the reception of the first UL data.

[0198] Aspect 26: An apparatus as in any of Aspects 23 to 25, wherein the processor is further configured to: predict the interference level using at least one of: a sidelink interference graph, sidelink scheduling, a transmit beam for transmitting second data from a third scheduled entity to a fourth scheduled entity, or a receive beam for receiving first data from the first scheduled entity at the second scheduled entity.

[0199] Aspect 27: An apparatus as in any of Aspects 23 to 26, wherein the processor is further configured to: send a preemption indication to indicate that the receiving scheduled entities including the fourth scheduled entity will ignore data including the second data received during the at least a portion of the side link resources.

[0200] Aspect 28: An apparatus as in any one of Aspects 23 to 27, wherein the processor is further configured to: send the preemption indication to at least one of: at least a fourth scheduled entity, a scheduled entity including the fourth scheduled entity scheduled to receive in at least a portion of the side link resources, or a portion of scheduled entities including the fourth scheduled entity scheduled to receive in at least a portion of the side link resources, which portion of the scheduled entities will receive interference from the first data transmission.

[0201] Aspect 29: An apparatus as in any of Aspects 23 to 28, wherein the processor is further configured to: instruct the third scheduled entity to send a preemption indication to indicate that the receiving scheduled entities including the fourth scheduled entity will ignore data including the second data received during at least a portion of the side link resource.

[0202] Aspect 30: An apparatus as in any one of Aspects 23 to 29, wherein the processor is further configured to: instruct the third scheduled entity to send the preemption indication to at least one of: at least a fourth scheduled entity, a scheduled entity including the fourth scheduled entity scheduled to receive in at least a portion of the side link resource, or a part of the scheduled entities including the fourth scheduled entity scheduled to receive in at least a portion of the side link resource, which part of the scheduled entities will receive interference from the first data transmission.

[0203] Aspect 31: An apparatus configured as a scheduling entity for wireless communication in a wireless communication network, comprising: at least one means for performing the method of any one of aspects 1 to 7 or 15 to 22.

[0204] Aspect 32: A non-transitory computer-readable medium storing computer-executable code, the computer-executable code comprising code for causing an apparatus to perform the method of any one of aspects 1 to 7 or 15 to 22.

[0205] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0206] By way of example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2), such as CDMA 2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0207] Within this disclosure, the word "exemplary" is used to mean "serving as an example, instance, or illustration." Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior or preferable to other aspects of the disclosure. Likewise, the term "aspect" does not require that all aspects of the disclosure include the features, advantages, or modes of operation discussed. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other—even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object even if the first object is never in direct physical contact with the second object. The terms "circuit" and "circuitry" are used broadly and are intended to include both hardware implementations of electronic devices and conductors that, when connected and configured, enable the functions described in this disclosure to be performed without limitation on the type of electronic circuitry, and software implementations of information and instructions that, when executed by a processor, enable the functions described in this disclosure to be performed.

[0208] Figure 1-16 One or more of the components, steps, features, and / or functions described herein may be rearranged and / or combined into a single component, step, feature, or function, or implemented in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figure 1 、 2 , 3, and / or 5-10 may be configured to perform one or more of the methods, features, or steps described herein (including Figure 11-16 The novel algorithms described herein may also be efficiently implemented in software and / or embedded in hardware.

[0209] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of exemplary processes. Based on design preferences, it will be understood that the specific order or hierarchy of steps in these methods may be rearranged. The accompanying method claims present elements of the various steps in a sample order and are not meant to be limited to the specific order or hierarchy presented unless specifically recited herein.

[0210] The preceding description is provided to enable any person skilled in the art to practice the various aspects of this disclosure. Various modifications to the various aspects will be readily apparent to those skilled in the art, and the universal principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but should be granted the full scope consistent with the language of the claims, wherein singular references to elements are not intended to mean "one and only one" unless specifically stated otherwise, but rather "one or more." Unless specifically stated otherwise, the term "some" refers to one or more. A phrase referring to "at least one of" a list of items refers to any combination of those items, including individual members. As an example, "at least one of a, b, or c" is intended to encompass: a; b; c; a and b; a and c; b and c; and a, b, and c. Similarly, the structure "A and / or B" may be understood to mean A; B; or A and B. All structural and functional equivalents currently or hereafter known to those of ordinary skill in the art for the elements of the various aspects described throughout this disclosure are expressly incorporated herein by reference and are intended to be covered by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims

1. A method for performing wireless communication at a scheduling entity in a wireless communication network, comprising: obtaining a first priority ranking of first uplink (UL) data, where the first UL data is used for first UL data transmission from a first scheduled entity to the scheduling entity; obtaining a second priority ranking of second data scheduled for second data transmission from the second scheduled entity to the third scheduled entity using at least a portion of the sidelink resources reserved for sidelink communication; as well as The first UL data transmission is scheduled using the at least a portion of the sidelink resources based on the first prioritization and the second prioritization.

2. The method of claim 1, further comprising: scheduling the first UL data transmission using the at least a portion of the sidelink resources if the first priority ranking indicates a higher priority than the second priority ranking; as well as A transmission cancellation indication is sent to cancel the second data transmission if the second data transmission will collide with the first UL data transmission.

3. The method of claim 1, further comprising: predicting an interference level received at the scheduling entity due to the second data transmission; as well as If the predicted interference level is greater than a predetermined threshold, a transmission cancellation indication is sent to cancel the second data transmission.

4. The method of claim 3, further comprising: Sending the transmission cancellation indication to at least one of: at least the second scheduled entity, scheduled entities including said second scheduled entity that are scheduled to transmit in said at least a portion of said sidelink resources, or A portion of scheduled entities including the second scheduled entity that are scheduled to transmit in the at least one portion of the sidelink resources will cause interference to reception of the first UL data.

5. The method of claim 1, further comprising: A preempt indication is sent to indicate that receiving scheduled entities including the third scheduled entity are to ignore data including the second data received during the at least a portion of the sidelink resources.

6. The method of claim 1, further comprising: The second scheduled entity is instructed to send a preempt indication to indicate that receiving scheduled entities including the third scheduled entity are to ignore data including the second data received during the at least a portion of the sidelink resources.

7. The method of claim 1, further comprising: sending a transmission cancellation indication to cancel the second data transmission in response to: a first determination that the second data transmission will interfere with the first UL data transmission; or A second determination is made that a predicted interference level received at the scheduling entity due to the second data transmission is greater than a predetermined threshold.

8. An apparatus configured as a scheduling entity for wireless communication in a wireless communication network, comprising: processor; a transceiver communicatively coupled to the processor; as well as a memory communicatively coupled to the processor, wherein the processor is configured to: obtaining a first priority ranking of first uplink (UL) data, where the first UL data is used for first UL data transmission from a first scheduled entity to the scheduling entity; obtaining a second priority ranking of second data scheduled for second data transmission from the second scheduled entity to the third scheduled entity using at least a portion of the sidelink resources reserved for sidelink communication; as well as The first UL data transmission is scheduled using the at least a portion of the sidelink resources based on the first prioritization and the second prioritization.

9. The apparatus of claim 8, wherein the processor is further configured to: scheduling the first UL data transmission using the at least a portion of the sidelink resources if the first priority ranking indicates a higher priority than the second priority ranking; and A transmission cancellation indication is sent to cancel the second data transmission if the second data transmission will collide with the first UL data transmission.

10. The apparatus of claim 8, wherein the processor is further configured to: predicting an interference level received at the scheduling entity due to the second data transmission; and If the predicted interference level is greater than a predetermined threshold, a transmission cancellation indication is sent to cancel the second data transmission.

11. The apparatus of claim 10, wherein the processor is further configured to: Sending the transmission cancellation indication to at least one of: at least the second scheduled entity, scheduled entities including said second scheduled entity that are scheduled to transmit in said at least a portion of said sidelink resources, or A portion of scheduled entities including the second scheduled entity that are scheduled to transmit in the at least one portion of the sidelink resources will cause interference to reception of the first UL data.

12. The apparatus of claim 8, wherein the processor is further configured to: A preempt indication is sent to indicate that receiving scheduled entities including the third scheduled entity are to ignore data including the second data received during the at least a portion of the sidelink resources.

13. The apparatus of claim 8, wherein the processor is further configured to: The second scheduled entity is instructed to send a preempt indication to indicate that receiving scheduled entities including the third scheduled entity are to ignore data including the second data received during the at least a portion of the sidelink resources.

14. The apparatus of claim 8, wherein the processor is further configured to: sending a transmission cancellation indication to cancel the second data transmission in response to: a first determination that the second data transmission will interfere with the first UL data transmission; or A second determination is made that a predicted interference level received at the scheduling entity due to the second data transmission is greater than a predetermined threshold.

15. A method for performing wireless communication at a scheduling entity in a wireless communication network, comprising: obtaining a first priority ranking of first data for a first data transmission from a first scheduled entity to a second scheduled entity using at least a portion of sidelink resources reserved for sidelink communication; obtaining a second priority ranking of second data scheduled for second data transmission from a third scheduled entity to a fourth scheduled entity using the at least a portion of the sidelink resources reserved for sidelink communication; as well as The first data transmission of the first data is scheduled using the at least a portion of the sidelink resources based on the first prioritization and the second prioritization.

16. The method of claim 15, further comprising sending a transmission cancellation indication to cancel the second data transmission in the following case: the first priority ranking indicates a higher priority than the second priority ranking, The first data transmission will conflict with the second data transmission, or A predicted interference level at the second scheduled entity from the second data transmission is greater than a predetermined threshold.

17. The method of claim 16, further comprising: Sending the transmission cancellation indication to at least one of: at least said third scheduled entity, scheduled entities including said third scheduled entity that are scheduled to transmit in said at least a portion of said sidelink resources, or A portion of the scheduled entities including the third scheduled entity that are scheduled to transmit in the at least one portion of the sidelink resources will cause interference to reception of the first data.

18. The method of claim 16, further comprising: The interference level is predicted using at least one of: Sidelink interference graph, Sidelink scheduling, transmitting the second data from the third scheduled entity to the transmit beam of the fourth scheduled entity, or A receive beam of the first data is received at the second scheduled entity from the first scheduled entity.

19. The method of claim 15, further comprising: A preempt indication is sent to indicate that receiving scheduled entities including the fourth scheduled entity are to ignore data including the second data received during the at least a portion of the sidelink resources.

20. The method of claim 19, further comprising: The preemption indication is sent to at least one of: at least said fourth scheduled entity, scheduled entities including said fourth scheduled entity that are scheduled to receive in said at least a portion of said sidelink resources, or A portion of the scheduled entities including the fourth scheduled entity that are scheduled to receive in the at least a portion of the sidelink resources will receive interference from the first data transmission.

21. The method of claim 15, further comprising: The third scheduled entity is instructed to send a preempt indication to indicate that receiving scheduled entities including the fourth scheduled entity are to ignore data including the second data received during the at least a portion of the sidelink resources.

22. The method of claim 21, further comprising: instructing the third scheduled entity to send the preemption indication to at least one of the following: at least said fourth scheduled entity, scheduled entities including said fourth scheduled entity that are scheduled to receive in said at least a portion of said sidelink resources, or A portion of the scheduled entities including the fourth scheduled entity that are scheduled to receive in the at least a portion of the sidelink resources will receive interference from the first data transmission.

23. An apparatus configured as a scheduling entity for wireless communication in a wireless communication network, comprising: processor; a transceiver communicatively coupled to the processor; as well as a memory communicatively coupled to the processor, wherein the processor is configured to: obtaining a first priority ranking of first data for a first data transmission from a first scheduled entity to a second scheduled entity using at least a portion of sidelink resources reserved for sidelink communication; obtaining a second priority ranking of second data scheduled for second data transmission from a third scheduled entity to a fourth scheduled entity using the at least a portion of the sidelink resources reserved for sidelink communication; as well as The first data transmission of the first data is scheduled using the at least a portion of the sidelink resources based on the first prioritization and the second prioritization.

24. The apparatus of claim 23, wherein the processor is further configured to: A transmission cancellation indication is sent to cancel the second data transmission in the following circumstances: the first priority ranking indicates a higher priority than the second priority ranking, The first data transmission will conflict with the second data transmission, or A predicted interference level at the second scheduled entity from the second data transmission is greater than a predetermined threshold.

25. The apparatus of claim 24, wherein the processor is further configured to: Sending the transmission cancellation indication to at least one of: at least said third scheduled entity, scheduled entities including said third scheduled entity that are scheduled to transmit in said at least a portion of said sidelink resources, or A portion of the scheduled entities including the third scheduled entity that are scheduled to transmit in the at least one portion of the sidelink resources will cause interference to reception of the first data.

26. The apparatus of claim 24, wherein the processor is further configured to: The interference level is predicted using at least one of: Sidelink interference graph, Sidelink scheduling, transmitting the second data from the third scheduled entity to the transmit beam of the fourth scheduled entity, or A receive beam of the first data is received at the second scheduled entity from the first scheduled entity.

27. The apparatus of claim 23, wherein the processor is further configured to: A preempt indication is sent to indicate that receiving scheduled entities including the fourth scheduled entity are to ignore data including the second data received during the at least a portion of the sidelink resources.

28. The apparatus of claim 27, wherein the processor is further configured to: The preemption indication is sent to at least one of: at least said fourth scheduled entity, scheduled entities including said fourth scheduled entity that are scheduled to receive in said at least a portion of said sidelink resources, or A portion of the scheduled entities including the fourth scheduled entity that are scheduled to receive in the at least a portion of the sidelink resources will receive interference from the first data transmission.

29. The apparatus of claim 23, wherein the processor is further configured to: The third scheduled entity is instructed to send a preempt indication to indicate that receiving scheduled entities including the fourth scheduled entity are to ignore data including the second data received during the at least a portion of the sidelink resources.

30. The apparatus of claim 29, wherein the processor is further configured to: instructing the third scheduled entity to send the preemption indication to at least one of the following: at least said fourth scheduled entity, scheduled entities including said fourth scheduled entity that are scheduled to receive in said at least a portion of said sidelink resources, or A portion of the scheduled entities including the fourth scheduled entity that are scheduled to receive in the at least a portion of the sidelink resources will receive interference from the first data transmission.

Images