Edge resource block utilization in contiguous subchannels
Patent Information
- Application Number
- EP2023931352
- Authority / Receiving Office
- EP · EP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-04-06
- Publication Date
- 2026-02-11
Smart Images

Figure CN2023086460_10102024_PF_FP_ABST
Abstract
Description
EDGE RESOURCE BLOCK UTILIZATION IN CONTIGUOUS SUBCHANNELS
[0001] FIELD OF TECHNOLOGY
[0002] The following relates to wireless communications, including edge resource block utilization in contiguous subchannels.BACKGROUND
[0003] Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) . Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA) , time division multiple access (TDMA) , frequency division multiple access (FDMA) , orthogonal FDMA (OFDMA) , or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM) . A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .
[0004] SUMMARY
[0005] The described techniques relate to improved methods, systems, devices, and apparatuses that support edge resource block utilization in contiguous subchannels. For example, the described techniques provide for a transmitting user equipment (UE) to transmit or otherwise provide an indication of sidelink resources to another UE (e.g., a sidelink UE) . The sidelink resources may span or include multiple subbands (e.g., multiple 20 MHz subbands) , with each subband including a resource block (RB) set available for sidelink communications. Each subband may also include a sequentially first subchannel including at least some guard RBs that are generally not used for sidelink communications. The UE may perform a LBT procedure on the subband and adjacent subband (s) based on the sequentially first subchannel of the subband not overlapping with the subband boundary (e.g., the boundary between adjacent subbands) . The UE may transmit the sidelink communications in the RB set as well as in some or all of the guard RBs, e.g., when the LBT procedure is successful in both subbands.
[0006] In some examples, the transmitting UE may transmit or otherwise provide an indication of sidelink resources to another UE (e.g., a sidelink UE) . The sidelink resources may span or include multiple subbands (e.g., 20 MHz subbands) , with each subband including a RB set available for sidelink communications. Each subband may also include a sequentially last subchannel including at least some guard RBs that are generally not used for sidelink communications. The UE may perform a LBT procedure on the subband, on adjacent subband (s) , or both, based on the sequentially last subchannel of the subband overlapping with the RB set boundary, the subband boundary, or both. The UE may transmit the sidelink communications in the RB set as well as in some or all of the guard RBs of the sequentially last subchannel, e.g., when the LBT procedure is successful in the subband, in adjacent subband (s) , or both.
[0007] A method for wireless communications at a UE is described. The method may include transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, performing, based on the sequentially first subchannel of a subband not overlapping with a subband boundary, a channel clearance procedure in the subband and at least one adjacent subband, and transmitting sidelink communications in the RB set and in the guard RBs of the subband based on a result of the channel clearance procedure.
[0008] An apparatus for wireless communications at a UE is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to transmit an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, perform, based on the sequentially first subchannel of a subband not overlapping with a subband boundary, a channel clearance procedure in the subband and at least one adjacent subband, and transmit sidelink communications in the RB set and in the guard RBs of the subband based on a result of the channel clearance procedure.
[0009] Another apparatus for wireless communications at a UE is described. The apparatus may include means for transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, means for performing, based on the sequentially first subchannel of a subband not overlapping with a subband boundary, a channel clearance procedure in the subband and at least one adjacent subband, and means for transmitting sidelink communications in the RB set and in the guard RBs of the subband based on a result of the channel clearance procedure.
[0010] A non-transitory computer-readable medium storing code for wireless communications at a UE is described. The code may include instructions executable by a processor to transmit an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, perform, based on the sequentially first subchannel of a subband not overlapping with a subband boundary, a channel clearance procedure in the subband and at least one adjacent subband, and transmit sidelink communications in the RB set and in the guard RBs of the subband based on a result of the channel clearance procedure.
[0011] In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, performing the channel clearance procedure may include operations, features, means, or instructions for determining that the sequentially first subchannel of the subband includes the guard RBs and a subset of RBs of the RB set and that the sequentially first subchannel of the subband does not cross the subband boundary between the subband and the at least one adjacent subband.
[0012] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that transmitting the sidelink communications in the RB set fails to comply with an occupied channel bandwidth (OCB) threshold, where transmitting the sidelink communications in the guard RBs may be based on the determining.
[0013] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the channel clearance procedure may be successful in both the subband and the at least one adjacent subband, where transmitting the sidelink communications may be based on a successful channel clearance procedure.
[0014] A method for wireless communications at a UE is described. The method may include transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, performing, based on the sequentially last subchannel of a subband overlapping with a subband boundary, with a RB set boundary, or both, a channel clearance procedure in the subband, in at least one adjacent subband, or both, and transmitting sidelink communications in the guard RBs in the sequentially last subchannel of the subband based on a result of the channel clearance procedure.
[0015] An apparatus for wireless communications at a UE is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to transmit an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, perform, based on the sequentially last subchannel of a subband overlapping with a subband boundary, with a RB set boundary, or both, a channel clearance procedure in the subband, in at least one adjacent subband, or both, and transmit sidelink communications in the guard RBs in the sequentially last subchannel of the subband based on a result of the channel clearance procedure.
[0016] Another apparatus for wireless communications at a UE is described. The apparatus may include means for transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, means for performing, based on the sequentially last subchannel of a subband overlapping with a subband boundary, with a RB set boundary, or both, a channel clearance procedure in the subband, in at least one adjacent subband, or both, and means for transmitting sidelink communications in the guard RBs in the sequentially last subchannel of the subband based on a result of the channel clearance procedure.
[0017] A non-transitory computer-readable medium storing code for wireless communications at a UE is described. The code may include instructions executable by a processor to transmit an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, perform, based on the sequentially last subchannel of a subband overlapping with a subband boundary, with a RB set boundary, or both, a channel clearance procedure in the subband, in at least one adjacent subband, or both, and transmit sidelink communications in the guard RBs in the sequentially last subchannel of the subband based on a result of the channel clearance procedure.
[0018] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the sequentially last subchannel includes RBs from the RB set and the guard RBs and transmitting, based on the determining, the sidelink communications in the RBs from the RB set in the sequentially last subchannel.
[0019] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the sequentially last subchannel includes RBs from the RB set and the guard RBs and transmitting, based on the determining, the sidelink communications in the RBs from the RB set and in the guard RBs in the sequentially last subchannel.
[0020] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that transmitting the sidelink communications in the RB set fails to comply with an OCB threshold, where transmitting the sidelink communications in the guard RBs may be based on the determining.
[0021] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that transmitting the sidelink communications in the RB set complies with an OCB threshold and transmitting the sidelink communications in RBs of the sequentially last subchannel based on the channel clearance procedure being performed successfully in the subband.
[0022] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that transmitting the sidelink communications in the RB set complies with an OCB threshold and transmitting the sidelink communications in RBs and the guard RBs of the sequentially last subchannel based on an interference level associated with the channel clearance procedure being performed successfully in the subband and the at least one adjacent subband.
[0023] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to a sidelink UE receiving the sidelink communications, a puncturing indication identifying whether the sidelink communications may be to be transmitted in the guard RBs.
[0024] A method for wireless communications at a UE is described. The method may include receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially first subchannel of a subband of the multiple subbands does not overlap with a subband boundary and receiving sidelink communications in the RB set and in the guard RBs of the subband based on a result of a channel clearance procedure.
[0025] An apparatus for wireless communications at a UE is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially first subchannel of a subband of the multiple subbands does not overlap with a subband boundary and receive sidelink communications in the RB set and in the guard RBs of the subband based on a result of a channel clearance procedure.
[0026] Another apparatus for wireless communications at a UE is described. The apparatus may include means for receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially first subchannel of a subband of the multiple subbands does not overlap with a subband boundary and means for receiving sidelink communications in the RB set and in the guard RBs of the subband based on a result of a channel clearance procedure.
[0027] A non-transitory computer-readable medium storing code for wireless communications at a UE is described. The code may include instructions executable by a processor to receive an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially first subchannel of a subband of the multiple subbands does not overlap with a subband boundary and receive sidelink communications in the RB set and in the guard RBs of the subband based on a result of a channel clearance procedure.
[0028] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the sequentially first subchannel of the subband includes the guard RBs and a subset of RBs of the RB set and that the sequentially first subchannel of the subband does not cross the subband boundary between the subband and at least one adjacent subband.
[0029] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that receiving the sidelink communications in the RB set fails to comply with an OCB threshold, where receiving the sidelink communications in the guard RBs may be based on the determining.
[0030] A method for wireless communications at a UE is described. The method may include receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially last subchannel of a subband overlaps with a subband boundary, a RB set boundary, or both and receiving sidelink communications in RBs in the guard RBs in the sequentially last subchannel of the subband.
[0031] An apparatus for wireless communications at a UE is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially last subchannel of a subband overlaps with a subband boundary, a RB set boundary, or both and receive sidelink communications in RBs in the guard RBs in the sequentially last subchannel of the subband.
[0032] Another apparatus for wireless communications at a UE is described. The apparatus may include means for receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially last subchannel of a subband overlaps with a subband boundary, a RB set boundary, or both and means for receiving sidelink communications in RBs in the guard RBs in the sequentially last subchannel of the subband.
[0033] A non-transitory computer-readable medium storing code for wireless communications at a UE is described. The code may include instructions executable by a processor to receive an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially last subchannel of a subband overlaps with a subband boundary, a RB set boundary, or both and receive sidelink communications in RBs in the guard RBs in the sequentially last subchannel of the subband.
[0034] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the sequentially last subchannel includes RBs from the RB set and the guard RBs and receiving, based on the determining, the sidelink communications in the RBs from the RB set in the sequentially last subchannel.
[0035] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the sequentially last subchannel includes RBs from the RB set and the guard RBs and receiving, based on the determining, the sidelink communications in the RBs from the RB set and in the guard RBs in the sequentially last subchannel.
[0036] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that receiving the sidelink communications in the RB set complies with an OCB threshold and receiving the sidelink communications in the RBs of the sequentially last subchannel based on the determining.
[0037] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that receiving the sidelink communications in the RB set complies with an OCB threshold and receiving the sidelink communications in the RBs and the guard RBs of the sequentially last subchannel based on a puncturing indication.
[0038] Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from a sidelink UE receiving the sidelink communications, the puncturing indication identifying whether the sidelink communications may be to be received in the RBs, in the guard RBs, or both.
[0039] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. Characteristics of the concepts disclosed herein, both their organization and method of operation, together with associated advantages will be better understood from the following description when considered in connection with the accompanying figures. Each of the figures is provided for the purposes of illustration and description, and not as a definition of the limits of the claims.
[0040] While aspects and embodiments are described in this application by illustration to some examples, those skilled in the art will understand that additional implementations and use cases may come about in many different arrangements and scenarios. Innovations described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, packaging arrangements. For example, embodiments and / or uses may come about via integrated chip embodiments and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, etc. ) . While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described innovations may occur. Implementations may range in spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, radio frequency (RF) -chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders / summers, etc. ) . It is intended that innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes, and constitution.BRIEF DESCRIPTION OF THE DRAWINGS
[0041] FIG. 1 shows an example of a wireless communications system that supports edge resource block utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure.
[0042] FIG. 2 shows an example of a network architecture that supports edge resource block utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure.
[0043] FIG. 3 shows an example of a wireless communications system that supports edge resource block utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure.
[0044] FIG. 4 shows an example of a resource pool that supports edge resource block utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure.
[0045] FIG. 5 shows an example of a resource pool that supports edge resource block utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure.
[0046] FIGs. 6 and 7 show block diagrams of devices that support edge resource block utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure.
[0047] FIG. 8 shows a block diagram of a communications manager that supports edge resource block utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure.
[0048] FIG. 9 shows a diagram of a system including a device that supports edge resource block utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure.
[0049] FIGs. 10 through 13 show flowcharts illustrating methods that support edge resource block utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION
[0050] Wireless networks may allocate resources according to various allocation schemes. For example, sidelink resources may include the mapping of subchannels starting from the first physical resource block (PRB) of the resource pool, with the subchannels being mapped sequentially within the resource pool. In some aspects, this may be based on the size of the subchannel. This may include sidelink resources including or otherwise spanning multiple subbands. Each of the subbands may include a resource block (RB) set (e.g., multiple PRBs) with guard bands being configured between adjacent RB sets in adjacent subbands. That is, leading and / or trailing edge subchannels within each subband may include at least some RBs being allocated as guard RBs unusable for communications. However, allocating these guard RBs may result in the sidelink communications using the sidelink resources failing to comply with an occupied channel bandwidth (OCB) requirement for the sidelink transmissions.
[0051] Accordingly, aspects of the described techniques relate to improved methods, systems, devices, and apparatuses that support edge RB utilization in contiguous subchannels. For example, the described techniques provide for a transmitting user equipment (UE) to transmit or otherwise provide an indication of sidelink resources to another UE (e.g., a sidelink UE) . The sidelink resources may span or include multiple subbands (e.g., multiple 20 MHz subbands) , with each subband including a RB set available for sidelink communications. Each subband may also include a sequentially first subchannel including at least some guard RBs that are generally not used for sidelink communications. The UE may perform a LBT procedure on the subband and adjacent subband (s) based on the sequentially first subchannel of the subband not overlapping with the subband boundary (e.g., the boundary between adjacent subbands) . The UE may transmit the sidelink communications in the RB set as well as in some or all of the guard RBs, e.g., when the LBT procedure is successful in both subbands.
[0052] In some examples, the transmitting UE may transmit or otherwise provide an indication of sidelink resources to another UE (e.g., a sidelink UE) . The sidelink resources may span or include multiple subbands (e.g., 20 MHz subbands) , with each subband including a RB set available for sidelink communications. Each subband may also include a sequentially last subchannel including at least some guard RBs that are generally not used for sidelink communications. The UE may perform a LBT procedure on the subband, on adjacent subband (s) , or both, based on the sequentially last subchannel of the subband overlapping with the RB set boundary, the subband boundary, or both. The UE may transmit the sidelink communications in the RB set as well as in some or all of the guard RBs of the sequentially last subchannel, e.g., when the LBT procedure is successful in the subband, in adjacent subband (s) , or both.
[0053] Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to edge RB utilization in contiguous subchannels.
[0054] FIG. 1 shows an example of a wireless communications system 100 that supports edge RB utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
[0055] The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via one or more communication links 125 (e.g., a radio frequency (RF) access link) . For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
[0056] The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices, such as other UEs 115 or network entities 105, as shown in FIG. 1.
[0057] As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
[0058] In some examples, network entities 105 may communicate with the core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via one or more backhaul communication links 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) . In some examples, network entities 105 may communicate with one another via a backhaul communication link 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via a core network 130) . In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof. The backhaul communication links 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) , one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.
[0059] One or more of the network entities 105 described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or a giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) . In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as a base station 140) .
[0060] In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 105 may include one or more of a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) 180 system, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) . In some examples, one or more network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
[0061] The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU 160 may be connected to one or more DUs 165 or RUs 170, and the one or more DUs 165 or RUs 170 may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or more RUs 170) . In some cases, a functional split between a CU 160 and a DU 165, or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) . A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to one or more DUs 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to one or more RUs 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) . In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 105 that are in communication via such communication links.
[0062] In wireless communications systems (e.g., wireless communications system 100) , infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) . In some cases, in an IAB network, one or more network entities 105 (e.g., IAB nodes 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as a donor entity or an IAB donor. One or more DUs 165 or one or more RUs 170 may be partially controlled by one or more CUs 160 associated with a donor network entity 105 (e.g., a donor base station 140) . The one or more donor network entities 105 (e.g., IAB donors) may be in communication with one or more additional network entities 105 (e.g., IAB nodes 104) via supported access and backhaul links (e.g., backhaul communication links 120) . IAB nodes 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by DUs 165 of a coupled IAB donor. An IAB-MT may include an independent set of antennas for relay of communications with UEs 115, or may share the same antennas (e.g., of an RU 170) of an IAB node 104 used for access via the DU 165 of the IAB node 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) . In some examples, the IAB nodes 104 may include DUs 165 that support communication links with additional entities (e.g., IAB nodes 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) . In such cases, one or more components of the disaggregated RAN architecture (e.g., one or more IAB nodes 104 or components of IAB nodes 104) may be configured to operate according to the techniques described herein.
[0063] For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor) , IAB nodes 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130) . That is, an IAB donor may refer to a RAN node with a wired or wireless connection to core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170) , in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link) . IAB donor and IAB nodes 104 may communicate via an F1 interface according to a protocol that defines signaling messages (e.g., an F1 AP protocol) . Additionally, or alternatively, the CU 160 may communicate with the core network via an interface, which may be an example of a portion of backhaul link, and may communicate with other CUs 160 (e.g., a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of a portion of a backhaul link.
[0064] An IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities) . A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with the IAB node 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through one or more other IAB nodes 104) . Additionally, or alternatively, an IAB node 104 may also be referred to as a parent node or a child node to other IAB nodes 104, depending on the relay chain or configuration of the AN. Therefore, the IAB-MT entity of IAB nodes 104 may provide a Uu interface for a child IAB node 104 to receive signaling from a parent IAB node 104, and the DU interface (e.g., DUs 165) may provide a Uu interface for a parent IAB node 104 to signal to a child IAB node 104 or UE 115.
[0065] For example, IAB node 104 may be referred to as a parent node that supports communications for a child IAB node, or referred to as a child IAB node associated with an IAB donor, or both. The IAB donor may include a CU 160 with a wired or wireless connection (e.g., a backhaul communication link 120) to the core network 130 and may act as parent node to IAB nodes 104. For example, the DU 165 of IAB donor may relay transmissions to UEs 115 through IAB nodes 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of IAB donor may signal communication link establishment via an F1 interface to IAB nodes 104, and the IAB nodes 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through the DUs 165. That is, data may be relayed to and from IAB nodes 104 via signaling via an NR Uu interface to MT of the IAB node 104. Communications with IAB node 104 may be scheduled by a DU 165 of IAB donor and communications with IAB node 104 may be scheduled by DU 165 of IAB node 104.
[0066] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support edge RB utilization in contiguous subchannels as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes 104, DUs 165, CUs 160, RUs 170, RIC 175, SMO 180) .
[0067] A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, or vehicles, meters, among other examples.
[0068] The UEs 115 described herein may be able to communicate with various types of devices, such as other UEs 115 that may sometimes act as relays as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
[0069] The UEs 115 and the network entities 105 may wirelessly communicate with one another via one or more communication links 125 (e.g., an access link) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined physical layer structure for supporting the communication links 125. For example, a carrier used for a communication link 125 may include a portion of a RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR) . Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities 105) .
[0070] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different radio access technology) .
[0071] The communication links 125 shown in the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
[0072] A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) . Devices of the wireless communications system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
[0073] Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) . In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
[0074] One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
[0075] The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=1 / (Δfmax·Nf) seconds, for which Δfmax may represent a supported subcarrier spacing, and Nf may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) . Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
[0076] Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . In some wireless communications systems 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
[0077] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) . In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
[0078] Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET) ) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to multiple UEs 115 and UE-specific search space sets for sending control information to a specific UE 115.
[0079] A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) , or others) . In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
[0080] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a lower-powered network entity 105 (e.g., a lower-powered base station 140) , as compared with a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) . A network entity 105 may support one or multiple cells and may also support communications via the one or more cells using one or multiple component carriers.
[0081] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.
[0082] In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, the overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 provide coverage for various coverage areas 110 using the same or different radio access technologies.
[0083] The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, network entities 105 may have different frame timings, and transmissions from different network entities 105 may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.
[0084] Some UEs 115, such as MTC or IoT devices, may be low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) . M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
[0085] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently) . In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or RBs) within a carrier, within a guard-band of a carrier, or outside of a carrier.
[0086] The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) . The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
[0087] In some examples, a UE 115 may be configured to support communicating directly with other UEs 115 via a device-to-device (D2D) communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) . In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to each of the other UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
[0088] In some systems, a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115) . In some examples, vehicles may communicate using vehicle-to- everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.
[0089] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
[0090] The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) . Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
[0091] The wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170) , and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
[0092] The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) radio access technology, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) . Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
[0093] A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
[0094] The network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords) . Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) , for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO) , for which multiple spatial layers are transmitted to multiple devices.
[0095] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
[0096] A network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, a network entity 105 (e.g., a base station 140, an RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity 105 multiple times along different directions. For example, the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.
[0097] Some signals, such as data signals associated with a particular receiving device, may be transmitted by transmitting device (e.g., a transmitting network entity 105, a transmitting UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as a receiving network entity 105 or a receiving UE 115) . In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions. For example, a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.
[0098] In some examples, transmissions by a device (e.g., by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115) . The UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS) , a channel state information reference signal (CSI-RS) ) , which may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook) . Although these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170) , a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device) .
[0099] A receiving device (e.g., a UE 115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a receiving device (e.g., a network entity 105) , such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal) . The single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR) , or otherwise acceptable signal quality based on listening according to multiple beam directions) .
[0100] The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. An RLC layer may perform packet segmentation and reassembly to communicate via logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.
[0101] The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., a communication link 125, a D2D communication link 135) . HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) . HARQ may improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions) . In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
[0102] A UE 115 (e.g., a transmitting UE) may transmit an indication of sidelink resources comprising multiple subbands, each subband of the multiple subbands comprising a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications. The UE 115 may perform, based at least in part on the sequentially first subchannel of a subband not overlapping with a subband boundary, a channel clearance procedure in the subband and at least one adjacent subband. The UE 115 may transmit sidelink communications in the RB set and in the guard RBs of the subband based at least in part on a result of the channel clearance procedure.
[0103] A UE 115 (e.g., a transmitting UE) may transmit an indication of sidelink resources comprising multiple subbands, each subband of the multiple subbands comprising a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications. The UE 115 may perform, based at least in part on the sequentially last subchannel of a subband overlapping with a subband boundary, with a RB set boundary, or both, a channel clearance procedure in the subband, in at least one adjacent subband, or both. The UE 115 may transmit sidelink communications in the guard RBs in the sequentially last subchannel of the subband based at least in part on a result of the channel clearance procedure.
[0104] A UE 115 (e.g., a receiving UE) may receive an indication of sidelink resources comprising multiple subbands, each subband of the multiple subbands comprising a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, wherein the sequentially first subchannel of a subband of the multiple subbands does not overlap with a subband boundary. The UE 115 may receive sidelink communications in the RB set and in the guard RBs of the subband based at least in part on a result of a channel clearance procedure.
[0105] A UE 115 (e.g., a receiving UE) may receive an indication of sidelink resources comprising multiple subbands, each subband of the multiple subbands comprising a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, wherein the sequentially last subchannel of a subband overlaps with a subband boundary, a RB set boundary, or both. The UE 115 may receive sidelink communications in resource blocks in the guard RBs in the sequentially last subchannel of the subband.
[0106] FIG. 2 shows an example of a network architecture 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that supports edge resource block utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure. The network architecture 200 may illustrate an example for implementing one or more aspects of the wireless communications system 100. The network architecture 200 may include one or more CUs 160-a that may communicate directly with a core network 130-a via a backhaul communication link 120-a, or indirectly with the core network 130-a through one or more disaggregated network entities 105 (e.g., a Near-RT RIC 175-b via an E2 link, or a Non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO Framework) , or both) . A CU 160-a may communicate with one or more DUs 165-a via respective midhaul communication links 162-a (e.g., an F1 interface) . The DUs 165-a may communicate with one or more RUs 170-a via respective fronthaul communication links 168-a. The RUs 170-a may be associated with respective coverage areas 110-a and may communicate with UEs 115-a via one or more communication links 125-a. In some implementations, a UE 115-a may be simultaneously served by multiple RUs 170-a.
[0107] Each of the network entities 105 of the network architecture 200 (e.g., CUs 160-a, DUs 165-a, RUs 170-a, Non-RT RICs 175-a, Near-RT RICs 175-b, SMOs 180-a, Open Clouds (O-Clouds) 205, Open eNBs (O-eNBs) 210) may include one or more interfaces or may be coupled with one or more interfaces configured to receive or transmit signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105, or an associated processor (e.g., controller) providing instructions to an interface of the network entity 105, may be configured to communicate with one or more of the other network entities 105 via the transmission medium. For example, the network entities 105 may include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other network entities 105. Additionally, or alternatively, the network entities 105 may include a wireless interface, which may include a receiver, a transmitter, or transceiver (e.g., an RF transceiver) configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other network entities 105.
[0108] In some examples, a CU 160-a may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, or the like. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 160-a. A CU 160-a may be configured to handle user plane functionality (e.g., CU-UP) , control plane functionality (e.g., CU-CP) , or a combination thereof. In some examples, a CU 160-a may be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. A CU 160-a may be implemented to communicate with a DU 165-a, as necessary, for network control and signaling.
[0109] A DU 165-a may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) to control the operation of one or more RUs 170-a. In some examples, a DU 165-a may host, at least partially, one or more of an RLC layer, a MAC layer, and one or more aspects of a PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP) . In some examples, a DU 165-a may further host one or more low PHY layers. Each layer may be implemented with an interface configured to communicate signals with other layers hosted by the DU 165-a, or with control functions hosted by a CU 160-a.
[0110] In some examples, lower-layer functionality may be implemented by one or more RUs 170-a. For example, an RU 170-a, controlled by a DU 165-a, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (e.g., performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower-layer functional split. In such an architecture, an RU 170-a may be implemented to handle over the air (OTA) communication with one or more UEs 115-a. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) 170-a may be controlled by the corresponding DU 165-a. In some examples, such a configuration may enable a DU 165-a and a CU 160-a to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
[0111] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (e.g., an O1 interface) . For virtualized network entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., an O-Cloud 205) to perform network entity life cycle management (e.g., to instantiate virtualized network entities 105) via a cloud computing platform interface (e.g., an O2 interface) . Such virtualized network entities 105 can include, but are not limited to, CUs 160-a, DUs 165-a, RUs 170-a, and Near-RT RICs 175-b. In some implementations, the SMO 180-a may communicate with components configured in accordance with a 4G RAN (e.g., via an O1 interface) . Additionally, or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-a via an O1 interface. The SMO 180-a also may include a Non-RT RIC 175-a configured to support functionality of the SMO 180-a.
[0112] The Non-RT RIC 175-a may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence (AI) or Machine Learning (ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 175-b. The Non-RT RIC 175-a may be coupled to or communicate with (e.g., via an A1 interface) the Near-RT RIC 175-b. The Near-RT RIC 175-b may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (e.g., via an E2 interface) connecting one or more CUs 160-a, one or more DUs 165-a, or both, as well as an O-eNB 210, with the Near-RT RIC 175-b.
[0113] In some examples, to generate AI / ML models to be deployed in the Near-RT RIC 175-b, the Non-RT RIC 175-a may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 175-b and may be received at the SMO 180-a or the Non-RT RIC 175-a from non-network data sources or from network functions. In some examples, the Non-RT RIC 175-a or the Near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 175-a may monitor long-term trends and patterns for performance and employ AI or ML models to perform corrective actions through the SMO 180-a (e.g., reconfiguration via O1) or via generation of RAN management policies (e.g., A1 policies) .
[0114] FIG. 3 shows an example of a wireless communications system 300 that supports edge RB utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure. Wireless communications system 300 may implement aspects of wireless communications system 100 and / or aspects of network architecture 200. Wireless communications system 300 may include a UE 305 and a UE 310, which may be examples of the corresponding devices described herein. The UE 305 may be an example of, and referred to as, a transmitting UE (Tx UE) transmitting sidelink communications to the UE 310. The UE 310 may be an example of, and referred to as, a receiving UE (Rx UE) receiving sidelink communications from the UE 305.
[0115] Wireless communications system 300 may include scheduling or otherwise allocating a resource pool (e.g., sidelink resources) to be used for sidelink communications. The sidelink resources may include multiple subbands (e.g., 20 MHz subbands) , with two subbands (e.g., subband #0 and subband #1) being shown in FIG. 3 by way of example only. Within each subband, the sidelink resources may include a RB set as well as a guard band being allocated or otherwise scheduled between the RB sets of adjacent subbands. The sidelink resources may span multiple physical frequency resources (e.g., PRBs or more simply RBs) , with each RB spanning twelve frequency tones or carriers in the frequency domain. The RBs may be grouped into subchannels, with each subchannel including a number of RBs. The number of RBs included in each subchannel may depend on the SCS and / or other considerations.
[0116] The guard band may generally include a number of guard RBs that are allocated or otherwise scheduled between the RB sets in order to mitigate cross-channel interference, or other interference types, between communications in the adjacent RB sets. Generally, the guard RBs are blocked out or otherwise restricted from being used for the sidelink communications. Accordingly, in some examples the sidelink resources may include contiguous RB-based physical sidelink control channel (PSCCH) and / or physical sidelink shared channel (PSSCH) communications, collectively referred to as PSxCH 325.
[0117] In some examples, the sidelink communications may be performed in an unlicensed or shared radio frequency spectrum band. That is, a UE transmitting on the sidelink resources may perform a channel clearance procedure, such as a listen-before-talk (LBT) procedure, a clear channel assessment (CCA) procedure, or some other type of channel clearance procedure, before transmitting using the sidelink resources. Broadly, the channel clearance procedure may include the transmitting UE listening or otherwise monitoring a wireless channel to determine whether the channel is available for use or is not available for use.
[0118] In some examples, the sidelink resources may include a mapping between the subchannels and the PRBs. As one non-limiting example, this may included the sequentially first subchannel starting from the first PRB of the sidelink resource pool and being mapped sequentially within the sidelink resource pool according to the subchannel size. In the non-limiting example illustrated in FIG. 2, this may include the sidelink resources starting at subchannel #0 and being mapped to sequential subchannels up to subchannel #11. However, it is to be understood that the number of subchannels included within a subband and / or the number of RBs within each subchannel may vary.
[0119] In some networks, wireless communications are associated with an OCB requirement where the transmission bandwidth within a subband needs to fulfill at least 80 percent of the subband bandwidth (e.g., an OCB threshold) . However, this may create an issue when contiguous subchannels are configured for the resource pool, such as how the PSxCH 325 transmissions may fulfill the OCB requirement. As one non-limiting example where the SCS is 30KHz, even when the minimal subchannel size (e.g., 10 RBs per subchannel) is configured, if the subchannel (s) overlapping with intra-cell guard bands (e.g., the guard band RBs) for the PSxCH 325 transmission in one RB set are dropped, there may be some cases that the minimum OCB requirement (e.g., OBB threshold > 44 RBs) cannot be met in which at maximum four subchannels can be transmitted (e.g., =40 RBs) . That is, in some networks the subchannels overlapping with the subband boundary (e.g., the boundary between adjacent subbands in the sidelink resource pool) are not available for sidelink communications, resulting in a loss of the RBs in those subchannels. In some examples, both leading (e.g., sequentially first) and / or trailing (e.g., sequentially last) subchannels are lost due to where the subband boundary is located within the sidelink resource pool. This may reduce the number of available RBs for the PSxCH 325 transmissions, which may result in violation of the OCB threshold.
[0120] Accordingly, aspects of the techniques described herein provide for improved sidelink communications that comply with the OCB threshold. In some aspects, this may include enabling puncturing of some or all of the guard RBs in the sequentially first and / or in the sequentially last subchannel of a subband, in adjacent subbands, and the like. For example, at 315 the UE 305 may transmit or otherwise provide (and the UE 310 may receive or otherwise obtain) an indication of sidelink resources that spans or otherwise includes multiple subbands. Two subbands (e.g., subband #0 and subband #1) are shown in FIG. 2 by way of non-limiting example only. It is to be understood that more than two subbands may be allocated or otherwise schedule for the sidelink resources. The sidelink resources may be mapped to physical frequency resources, such as RBs within a subchannel.
[0121] Each subband in the sidelink resource pool may include a RB set. For example, the subband #0 may include a RB set 0 and the subband #1 may include a RB set 1. Each RB set may span multiple subchannels, with each subchannel including physical frequency resources (e.g., RBs) . The RBs included in the RB set may be scheduled, allocated, or otherwise available for the sidelink communications. Each subband in the sidelink resource pool may also include guard RBs in the sequentially first subchannel and / or in the sequentially last subchannel. The guard RBs may generally be considered unavailable for sidelink communications, such as due to those RBs being allocated within the guard band.
[0122] The sequentially first and / or the sequentially last subchannels in the subband may be associated with a RB set boundary and a subband boundary. The RB set boundary may generally define the boundary between RBs included in the RB set and RBs included in the guard band. The RB set boundary may align at a subchannel boundary or may extend into a subchannel (e.g., may overlap within the subchannel) . The subband boundary may generally define the boundary between adjacent subbands. The subband boundary may align at a subchannel boundary or may extend into a subchannel (e.g., may overlap within the subchannel) . In the non-limiting example illustrated in FIG. 2, the subband boundary is aligned with the subchannel boundary (e.g., the subband boundary does not overlap with subchannel #5 of subband #0 or with subchannel #6 of subband #1) . Aspects of the techniques described herein may be based on where the RB set boundary and / or where the subband boundary are aligned with respect to a given subchannel.
[0123] Aspect of the non-limiting example illustrated in FIG. 3 may include or otherwise support PSCCH mapping in every subchannel, including the subchannel overlapping with guard band. To fulfill the OCB constraint, the UE 305 may transmit in as many RBs as possible in one RB set. For example, to fulfill the OCB requirement in one RB set, the Tx UE may clear the wideband LBT in adjacent RB sets and transmit PSCCH / PSSCH (e.g., PSxCH 325) starting from the lead subchannel (e.g., the sequentially first subchannel) of the RB set if the leading subchannel overlaps with subband but does not cross the subband boundary. Broadly, the RB set leading subchannel may be the first subchannel in the RB set. For example, subchannel #0 may be the lead subchannel (e.g., sequentially first) and subchannel #5 may be the trailing subchannel (e.g., sequentially last) of RB set 0. The subchannel #6 may be the leading subchannel (e.g., sequentially first) and subchannel #11 may be the trailing subchannel (e.g., sequentially last) of RB set 1. The subchannel #0 and subchannel #5 of RB set 1 may include guard RBs for RB set 0. The subchannel #6 and subchannel #11 of RB set 1 may include guard RBs for RB set 1.
[0124] In some examples, if the leading subchannel overlaps with the subband but does not cross the 20MHz subband boundary, the Tx UE may clear the wideband LBT in the current and adjacent RB set and transmit multi-subchannel PSSCH starting from the leading subchannel of the RB-set. The PSCCH may be located in the leading subchannel, with the PSSCH being located in the leading subchannel and in the other subchannels in the RB set. For example, the Tx UE may identify or otherwise determine that the sequentially first subchannel of the subband includes the guard RBs and, in some example, one or more RBs of the RB set for the subband. The Tx UE may also identify or otherwise determine that the sequentially first subchannel does not cross the subband boundary.
[0125] In some examples, the wideband LBT mat be an all or nothing LBT (e.g., if one of the RB sets fails the LBT, the multi-subchannel PSCCH / PSSCH may not be transmitted) . If the leading subchannel crosses the subband boundary, it may generally not be utilized to fulfil the OCB threshold in the RB set. Instead, the UE may transmit the multi-subchannel PSCCH / PSSCH starting in the next subchannel.
[0126] As discussed, subchannel #6 does not cross or otherwise overlap with the subband boundary (e.g., the boundary between subband #0 and subband #1) . Accordingly, the UE 305 may perform a channel clearance procedure on the subband (e.g., subband #1 in this example) and at least one adjacent subband (e.g., subband #0 in this example) . The channel clearance procedure may be a wideband LBT procedure in that is spans more than on subband. The channel clearance procedure may be performed based on the sequentially first subband of the subband (e.g., subchannel #6 of subband #1, in this example) not overlapping with the subband boundary. That is, the Tx UE may perform the wideband LBT procedure in the subband and adjacent subband (s) based on the first subchannel (e.g., subchannel #6) not overlapping with the subband boundary.
[0127] Based on a result of the channel clearance procedure (e.g., a successful LBT procedure) , at 320 the Tx UE may transmit the sidelink communications (e.g., PSxCH 325) in the RB set (e.g., RB set 1 in this example) and in the guard RBs of the first subchannel (e.g., subchannel #6 in this example) in the subband. Accordingly, in this example where subchannel #6 overlaps with the guard band but does not cross the subband boundary, the Tx UE may clear the LBT in RB set 0 and RB set 1 and transmit PSCCH / PSSCH (e.g., PSxCH 325) starting from subchannel #6.
[0128] In some aspects, this may include the Tx UE transmitting the sidelink communications in the guard RBs based on the OCB threshold. For example, the Tx UE may identify or otherwise determine whether transmitting the sidelink communications in the RB set satisfies or otherwise complies with the OCB threshold requirement. If so, the Tx UE may transmit the sidelink communications in the RBs of the RB set. If not, the Tx UE may transmit the sidelink communications in the RBs of the RB set and in the guard RBs of the sequentially first subchannel of the subband.
[0129] As discussed in greater detail with reference to FIG. 3 and FIG. 4, in some examples the Tx UE may also perform the sidelink communications in the guard RBs in the sequentially last subchannel (e.g., in RBs of the RB set and / or in the guard RBs in subchannel #11 in this example) . That is, the Tx UE may clear the LBT in RB set 0 and RB set 1 and then puncture PSSCH in subchannel #11 at the subband boundary. The Rx UE (e.g., the UE 310 in this example) may assume the puncturing of subchannel #11 is at the RB set boundary.
[0130] FIG. 4 shows an example of a resource pool 400 that supports edge RB utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure. Resource pool 400 may implement or be implemented by aspects of wireless communications system 100, network architecture 200, and / or wireless communications system 300. Aspects of resource pool 400 may be implemented at or implemented by a UE, which may be an example of the corresponding device described herein.
[0131] As discussed above, aspects of the techniques described herein provide for improved utilization of sidelink resources for contiguous subchannels. For example, a Tx UE may transmit or otherwise provide an indication of sidelink resources that span or otherwise include multiple subbands. In the non-limiting example illustrated in FIG. 3, the sidelink resources may include two subbands, subband #0 and subband #1. Each subband may span or otherwise include multiple subchannels, with each subchannel including physical frequency resources (e.g., PRBs or more simply RBs) . Each RB may correspond to a set of frequency tones or subcarriers, such as spanning twelve contiguous tones or subcarriers.
[0132] Each subband may include a RB set, which includes the RBs of the subchannels within the subband that are scheduled or otherwise allocated for sidelink communications. The sidelink communications in this example may include PSCCH and / or PSSCH, which may collectively be referred to as PSxCH 405. Each, some, or all of the subbands in the sidelink resource pool may include guard RBs in the sequentially first and / or the sequentially last subchannel (s) . As one non-limiting example, the sequentially first subchannel (e.g., subchannel #6) of subband #1 may include guard RBs and the sequentially last subchannel (subchannel #11) may include guard RBs. The guard RBs are generally not available for use in the sidelink communications.
[0133] As discussed above, in some examples the sidelink communications (e.g., PSCCH) are generally not allowed to be communicated in the sequentially first subband that overlaps with the subband boundary. For example, the subband boundary between subband #0 and subband #1 lies somewhere in subchannel #6, and therefore subchannel #6 is not available for sidelink communications in subband #1. That is, if subchannel #6 is overlapping with the guard band and crosses the subband boundary, this subchannel may not used for meeting the OCB threshold in RB set 1. Instead, the Tx UE may transmit PSCCH / PSSCH starting from subchannel #7.
[0134] However, aspects of the techniques described herein provide for utilization of the guard RBs in the sequentially last subchannel (e.g., subchannel #11 in this example) , such as to comply with the OCB threshold requirements. That is, to maximally utilize the last subchannel of a RB set, the Tx UE may transmit PSSCH including in the last subchannel even when it is partially overlapping with the guard band. For example, to fulfill the OCB threshold the Tx UE may transmit multi-subchannel PSSCH (e.g., in subchannels #7 -#10) including in the last subchannel in the RB-set or subband. For example, the Tx UE may puncture PSSCH outside of the subband or outside of the RB-set. In this example, the PSSCH Rx UE may assume the PSSCH in the last subchannel of the RB set or of the subband. For example, the Rx UE may assume that the PSSCH has been punctured outside of the RB set or has been punctured outside of the subband.
[0135] In some examples, this may include the PSSCH Tx UE punctured the PSSCH transmissions outside of the RB-set, such as if the LBT in the current RB-set is successful, or puncture the PSSCH REs in the last subchannel outside of the subband, such as when Tx UE performs the wideband LBT in the current and adjacent RB set (s) and still transmits PSSCH in the guard band.
[0136] That is, the Tx UE in this example may identify or otherwise determine that the sequentially last subchannel of a subband overlaps with the subband boundary and / or with the RB set boundary. In the non-limiting example illustrated in FIG. 3, the sequentially last subchannel (e.g., subchannel #11) of subband #1 overlaps with the RB set boundary (e.g., RB set 1 extends into subchannel #11) and with the subband boundary (e.g., the boundary of subband #1 ends within subchannel #11) .
[0137] Accordingly, the Tx UE may perform the channel clearance procedure in the subband (e.g., subband #1 in this example) and, in some examples, in adjacent subband (s) (e.g., subband #0 in this example) . For example, the Tx UE may perform the channel clearance procedure in the subband containing the sequentially last subband (e.g., subband #1 in this example) . In some examples, the Tx UE may perform the channel clearance procedure in one or more adjacent subbands (e.g., in subband #0 in this example and / or in a subband following subband #1, such as a subband #2 which is not shown) .
[0138] The Tx UE may transmit or otherwise convey (and the Rx UE may receive or otherwise obtain) the sidelink communications (e.g., PSxCH 405) in the guard RBs in the sequentially last subchannel of the subband. This may include the Tx UE transmitting the sidelink communications in the RBs of the sequentially last subchannel that are included in the RB set (e.g., the RBs of subchannel #11 that are included in RB set 1) .
[0139] In some aspect, this may be based on the OCB threshold requirement. For example, the Tx UE may identify or otherwise determine that transmitting the sidelink communications in the RBs of the RB set fails to comply with the OCB threshold. In this scenario, the Tx UE may transmit the sidelink communications in the guard RBs based on the RBs included in the RB set failing to satisfy the OCB threshold. That is, this technique may enable additional RBs (e.g., the guard RBs) being used for the sidelink communications performed in the subband (e.g., in subband #1 in this example) .
[0140] In some examples, transmitting the sidelink communications in the RBs from the RB set may satisfy the OCB threshold. That is, there may be sufficient RBs available in subchannels #7 -#10 that satisfies the OCB threshold. However, the Tx UE may puncture the PSSCH transmissions (e.g., the PSSCH portion of PSxCH 405) in the RBs of the RB set in the sequentially last subchannel and, in some examples, in the guard RBs of the sequentially last subchannel. For example, the Tx UE may transmit the sidelink communications in the RBs of the RB set in the sequentially last subchannel based on the channel clearance procedure being performed in the subband. In another example, the Tx UE may transmit the sidelink communications in the RBs of the RB set as well as in the guard RBs in the sequentially last subchannel based on the channel clearance procedure being performed in the subband and in adjacent subband (s) .
[0141] That is, the Tx UE and Rx UE puncturing behavior may be determined based on the OCB threshold and / or based on a dynamic indication by Tx UE. For example, the Tx UE and / or Rx UE may choose one of the two options (e.g., puncturing the RBs of the RB set or puncturing the RBs of the RB set and the guard RBs) depending on if the PRBs available for the sidelink transmission satisfies the OCB threshold. In a first option, if the OCB threshold is satisfied, the Tx UE may prefer puncturing the RBs of the RB set in the sequentially last subchannel since it uses one subband LBT. Otherwise, the Tx UE may puncture the RBs of the RB set as well as the guard RBs in the sequentially last subchannel based on the multi-subband LBT. The Rx UE may adjust the puncturing expectations from the Tx UE accordingly (e.g., based on the same rule) .
[0142] In another option where the OCB is fulfilled for both options, the Tx UE may choose either option based on interference level for wideband LBT. That is, the Tx UE may identify or otherwise determine an interference level for the wireless channel during the channel clearance procedure. The Tx UE may select which option to follow based on the interference level. In some examples, the Tx UE may indicate the puncturing assumption to the Rx UE (e.g., such as in a sidelink control information (SCI) message) to Rx UE and the Rx UE will adjust its puncturing expectations accordingly. In some examples, the Rx UE may assume the first option (e.g., puncturing the RBs of the RB set in the sequentially last subchannel) no matter what the Tx UE chooses. That is, the Tx UE may clear the LBT in RB set 1 and 2 (not shown) and puncture the PSSCH in subchannel #11 at the subband boundary while the Rx UE ma assume the puncturing of subchannel #11 as at the RB set boundary) .
[0143] FIG. 5 shows an example of a resource pool 500 that supports edge RB utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure. Resource pool 400 may implement or be implemented by aspects of wireless communications system 100, network architecture 200, wireless communications system 300 and / or implement aspects of resource pool 400. Aspects of resource pool 500 may be implemented at or implemented by a UE, which may be an example of the corresponding device described herein.
[0144] As discussed above, aspects of the techniques described herein provide for improved utilization of sidelink resources for contiguous subchannels. For example, a Tx UE may transmit or otherwise provide an indication of sidelink resources that span or otherwise include multiple subbands. In the non-limiting example illustrated in FIG. 4, the sidelink resources may include two subbands, subband #0 and subband #1. Each subband may span or otherwise include multiple subchannels, with each subchannel including physical frequency resources (e.g., PRBs or more simply RBs) . Each RB may correspond to a set of frequency tones or subcarriers, such as spanning twelve contiguous tones or subcarriers.
[0145] Each subband may include a RB set, which includes the RBs of the subchannels within the subband that are scheduled or otherwise allocated for sidelink communications. The sidelink communications in this example may include PSCCH and / or PSSCH, which may collectively be referred to as PSxCH 505. Each, some, or all of the subbands in the sidelink resource pool may include guard RBs in the sequentially first and / or the sequentially last subchannel (s) . As one non-limiting example, the sequentially first subchannel (e.g., subchannel #0) of subband #0 may include guard RBs and the sequentially last subchannel (subchannel #5) may include guard RBs. The guard RBs are generally not available for use in the sidelink communications.
[0146] As discussed above, in some examples the sidelink communications (e.g., PSCCH) are generally not allowed to be communicated in the sequentially first subband that overlaps with the subband boundary. For example, the subband boundary (the start of the subband in this example) for subband #0 lies at the beginning of subchannel #0, and therefore subchannel #0 is not available for sidelink communications in subband #0. Instead, the Tx UE may transmit PSCCH / PSSCH starting from subchannel #1.
[0147] However, aspects of the techniques described herein provide for utilization of the guard RBs in the sequentially last subchannel (e.g., subchannel #5 in this example) , such as to comply with the OCB threshold requirements. That is, to maximally utilize the last subchannel of a RB set, the Tx UE may transmit PSSCH including in the last subchannel even when it is partially overlapping with the guard band. For example, to fulfill the OCB threshold the Tx UE may transmit multi-subchannel PSSCH (e.g., in subchannels #1 -#5) including in the last subchannel in the RB set or subband. For example, the Tx UE may puncture PSSCH outside of the subband or outside of the RB-set. In this example, the PSSCH Rx UE may assume the PSSCH in the last subchannel of the RB set or of the subband. For example, the Rx UE may assume that the PSSCH has been punctured outside of the RB set or has been punctured outside of the subband.
[0148] In some examples, this may include the PSSCH Tx UE puncturing the PSSCH transmissions outside of the RB set, such as if the LBT in the current RB set is successful, or puncture the PSSCH REs in the last subchannel outside of the subband, such as when Tx UE performs the wideband LBT in the current and adjacent RB set (s) and still transmits PSSCH in the guard band.
[0149] That is, the Tx UE in this example may identify or otherwise determine that the sequentially last subchannel of a subband overlaps with the subband boundary and / or with the RB set boundary. In the non-limiting example illustrated in FIG. 4, the sequentially last subchannel (e.g., subchannel #5) of subband #0 overlaps with the RB set boundary (e.g., RB set 0 extends into subchannel #5) and with the subband boundary (e.g., the boundary of subband #0 ends within subchannel #5) .
[0150] Accordingly, the Tx UE may perform the channel clearance procedure in the subband (e.g., subband #0 in this example) and, in some examples, in adjacent subband (s) (e.g., subband #1 in this example) . For example, the Tx UE may perform the channel clearance procedure in the subband containing the sequentially last subband (e.g., subband #0 in this example) . In some examples, the Tx UE may perform the channel clearance procedure in one or more adjacent subbands (e.g., in subband #0 in this example and / or in subband #1) .
[0151] The Tx UE may transmit or otherwise convey (and the Rx UE may receive or otherwise obtain) the sidelink communications (e.g., PSxCH 505) in the guard RBs in the sequentially last subchannel of the subband. This may include the Tx UE transmitting the sidelink communications in the RBs of the sequentially last subchannel that are included in the RB set (e.g., the RBs of subchannel #5 that are included in RB set 0) .
[0152] In some aspect, this may be based on the OCB threshold requirement. For example, the Tx UE may identify or otherwise determine that transmitting the sidelink communications in the RBs of the RB set fails to comply with the OCB threshold. In this scenario, the Tx UE may transmit the sidelink communications in the guard RBs based on the RBs included in the RB set failing to satisfy the OCB threshold. That is, this technique may enable additional RBs (e.g., the guard RBs) being used for the sidelink communications performed in the subband (e.g., in subband #0 in this example) .
[0153] In some examples, transmitting the sidelink communications in the RBs from the RB set may satisfy the OCB threshold. That is, there may be sufficient RBs available in subchannels #1 -#5 that satisfies the OCB threshold. However, the Tx UE may puncture the PSSCH transmissions (e.g., the PSSCH portion of PSxCH 505) in the RBs of the RB set in the sequentially last subchannel and, in some examples, in the guard RBs of the sequentially last subchannel. For example, the Tx UE may transmit the sidelink communications in the RBs of the RB set in the sequentially last subchannel based on the channel clearance procedure being performed in the subband. In another example, the Tx UE may transmit the sidelink communications in the RBs of the RB set as well as in the guard RBs in the sequentially last subchannel based on the channel clearance procedure being performed in the subband and in adjacent subband (s) .
[0154] That is, the Tx UE and Rx UE puncturing behavior may be determined based on the OCB threshold and / or based on a dynamic indication by Tx UE. For example, the Tx UE and / or Rx UE may choose one of the two options (e.g., puncturing the RBs of the RB set or puncturing the RBs of the RB set and the guard RBs) depending on if the PRBs available for the sidelink transmission satisfies the OCB threshold. In a first option, if the OCB threshold is satisfied, the Tx UE may prefer puncturing the RBs of the RB set in the sequentially last subchannel since it uses one subband LBT. Otherwise, the Tx UE may puncture the RBs of the RB set as well as the guard RBs in the sequentially last subchannel based on the multi-subband LBT. The Rx UE may adjust the puncturing expectations from the Tx UE accordingly (e.g., based on the same rule) .
[0155] In another option where the OCB is fulfilled for both options, the Tx UE may choose either option based on interference level for wideband LBT. That is, the Tx UE may identify or otherwise determine an interference level for the wireless channel during the channel clearance procedure. The Tx UE may select which option to follow based on the interference level. In some examples, the Tx UE may indicate the puncturing assumption to the Rx UE (e.g., such as in a SCI message) to Rx UE and the Rx UE will adjust its puncturing expectations accordingly. In some examples, the Rx UE may assume the first option (e.g., puncturing the RBs of the RB set in the sequentially last subchannel) no matter what the Tx UE chooses. That is, the Tx UE may clear the LBT in RB set 0 and 1 and puncture the PSSCH in subchannel #5 at the subband boundary while the Rx UE ma assume the puncturing of subchannel #5 as at the RB set boundary) .
[0156] FIG. 6 shows a block diagram 600 of a device 605 that supports edge RB utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
[0157] The receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to edge RB utilization in contiguous subchannels) . Information may be passed on to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.
[0158] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to edge RB utilization in contiguous subchannels) . In some examples, the transmitter 615 may be co-located with a receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.
[0159] The communications manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of edge RB utilization in contiguous subchannels as described herein. For example, the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may support a method for performing one or more of the functions described herein.
[0160] In some examples, the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some examples, a processor and memory coupled with the processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor, instructions stored in the memory) .
[0161] Additionally, or alternatively, in some examples, the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by a processor. If implemented in code executed by a processor, the functions of the communications manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure) .
[0162] In some examples, the communications manager 620 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.
[0163] The communications manager 620 may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager 620 is capable of, configured to, or operable to support a means for transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications. The communications manager 620 is capable of, configured to, or operable to support a means for performing, based on the sequentially first subchannel of a subband not overlapping with a subband boundary, a channel clearance procedure in the subband and at least one adjacent subband. The communications manager 620 is capable of, configured to, or operable to support a means for transmitting sidelink communications in the RB set and in the guard RBs of the subband based on a result of the channel clearance procedure.
[0164] Additionally, or alternatively, the communications manager 620 may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager 620 is capable of, configured to, or operable to support a means for transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications. The communications manager 620 is capable of, configured to, or operable to support a means for performing, based on the sequentially last subchannel of a subband overlapping with a subband boundary, with a RB set boundary, or both, a channel clearance procedure in the subband, in at least one adjacent subband, or both. The communications manager 620 is capable of, configured to, or operable to support a means for transmitting sidelink communications in the guard RBs in the sequentially last subchannel of the subband based on a result of the channel clearance procedure.
[0165] Additionally, or alternatively, the communications manager 620 may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager 620 is capable of, configured to, or operable to support a means for receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially first subchannel of a subband of the multiple subbands does not overlap with a subband boundary. The communications manager 620 is capable of, configured to, or operable to support a means for receiving sidelink communications in the RB set and in the guard RBs of the subband based on a result of a channel clearance procedure.
[0166] Additionally, or alternatively, the communications manager 620 may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager 620 is capable of, configured to, or operable to support a means for receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially last subchannel of a subband overlaps with a subband boundary, a RB set boundary, or both. The communications manager 620 is capable of, configured to, or operable to support a means for receiving sidelink communications in RBs in the guard RBs in the sequentially last subchannel of the subband.
[0167] By including or configuring the communications manager 620 in accordance with examples as described herein, the device 605 (e.g., a processor controlling or otherwise coupled with the receiver 610, the transmitter 615, the communications manager 620, or a combination thereof) may support techniques for improved resource efficiency and sidelink communications by leveraging guard RBs in the first and / or last subchannel of a subband scheduled for sidelink communications.
[0168] FIG. 7 shows a block diagram 700 of a device 705 that supports edge RB utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure. The device 705 may be an example of aspects of a device 605 or a UE 115 as described herein. The device 705 may include a receiver 710, a transmitter 715, and a communications manager 720. The device 705 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .
[0169] The receiver 710 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to edge RB utilization in contiguous subchannels) . Information may be passed on to other components of the device 705. The receiver 710 may utilize a single antenna or a set of multiple antennas.
[0170] The transmitter 715 may provide a means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to edge RB utilization in contiguous subchannels) . In some examples, the transmitter 715 may be co-located with a receiver 710 in a transceiver module. The transmitter 715 may utilize a single antenna or a set of multiple antennas.
[0171] The device 705, or various components thereof, may be an example of means for performing various aspects of edge RB utilization in contiguous subchannels as described herein. For example, the communications manager 720 may include a resource indication manager 725, an LBT manager 730, a sidelink manager 735, or any combination thereof. The communications manager 720 may be an example of aspects of a communications manager 620 as described herein. In some examples, the communications manager 720, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 710, the transmitter 715, or both. For example, the communications manager 720 may receive information from the receiver 710, send information to the transmitter 715, or be integrated in combination with the receiver 710, the transmitter 715, or both to obtain information, output information, or perform various other operations as described herein.
[0172] The communications manager 720 may support wireless communications at a UE in accordance with examples as disclosed herein. The resource indication manager 725 is capable of, configured to, or operable to support a means for transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications. The LBT manager 730 is capable of, configured to, or operable to support a means for performing, based on the sequentially first subchannel of a subband not overlapping with a subband boundary, a channel clearance procedure in the subband and at least one adjacent subband. The sidelink manager 735 is capable of, configured to, or operable to support a means for transmitting sidelink communications in the RB set and in the guard RBs of the subband based on a result of the channel clearance procedure.
[0173] Additionally, or alternatively, the communications manager 720 may support wireless communications at a UE in accordance with examples as disclosed herein. The resource indication manager 725 is capable of, configured to, or operable to support a means for transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications. The LBT manager 730 is capable of, configured to, or operable to support a means for performing, based on the sequentially last subchannel of a subband overlapping with a subband boundary, with a RB set boundary, or both, a channel clearance procedure in the subband, in at least one adjacent subband, or both. The sidelink manager 735 is capable of, configured to, or operable to support a means for transmitting sidelink communications in the guard RBs in the sequentially last subchannel of the subband based on a result of the channel clearance procedure.
[0174] Additionally, or alternatively, the communications manager 720 may support wireless communications at a UE in accordance with examples as disclosed herein. The resource indication manager 725 is capable of, configured to, or operable to support a means for receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially first subchannel of a subband of the multiple subbands does not overlap with a subband boundary. The sidelink manager 735 is capable of, configured to, or operable to support a means for receiving sidelink communications in the RB set and in the guard RBs of the subband based on a result of a channel clearance procedure.
[0175] Additionally, or alternatively, the communications manager 720 may support wireless communications at a UE in accordance with examples as disclosed herein. The resource indication manager 725 is capable of, configured to, or operable to support a means for receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially last subchannel of a subband overlaps with a subband boundary, a RB set boundary, or both. The sidelink manager 735 is capable of, configured to, or operable to support a means for receiving sidelink communications in RBs in the guard RBs in the sequentially last subchannel of the subband.
[0176] FIG. 8 shows a block diagram 800 of a communications manager 820 that supports edge RB utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure. The communications manager 820 may be an example of aspects of a communications manager 620, a communications manager 720, or both, as described herein. The communications manager 820, or various components thereof, may be an example of means for performing various aspects of edge RB utilization in contiguous subchannels as described herein. For example, the communications manager 820 may include a resource indication manager 825, an LBT manager 830, a sidelink manager 835, a subchannel boundary manager 840, a OCB manager 845, a subchannel RB manager 850, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
[0177] The communications manager 820 may support wireless communications at a UE in accordance with examples as disclosed herein. The resource indication manager 825 is capable of, configured to, or operable to support a means for transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications. The LBT manager 830 is capable of, configured to, or operable to support a means for performing, based on the sequentially first subchannel of a subband not overlapping with a subband boundary, a channel clearance procedure in the subband and at least one adjacent subband. The sidelink manager 835 is capable of, configured to, or operable to support a means for transmitting sidelink communications in the RB set and in the guard RBs of the subband based on a result of the channel clearance procedure.
[0178] In some examples, to support performing the channel clearance procedure, the subchannel boundary manager 840 is capable of, configured to, or operable to support a means for determining that the sequentially first subchannel of the subband includes the guard RBs and a subset of RBs of the RB set and that the sequentially first subchannel of the subband does not cross the subband boundary between the subband and the at least one adjacent subband.
[0179] In some examples, the OCB manager 845 is capable of, configured to, or operable to support a means for determining that transmitting the sidelink communications in the RB set fails to comply with an OCB threshold, where transmitting the sidelink communications in the guard RBs is based on the determining.
[0180] In some examples, the LBT manager 830 is capable of, configured to, or operable to support a means for determining that the channel clearance procedure is successful in both the subband and the at least one adjacent subband, where transmitting the sidelink communications is based on a successful channel clearance procedure.
[0181] Additionally, or alternatively, the communications manager 820 may support wireless communications at a UE in accordance with examples as disclosed herein. In some examples, the resource indication manager 825 is capable of, configured to, or operable to support a means for transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications. In some examples, the LBT manager 830 is capable of, configured to, or operable to support a means for performing, based on the sequentially last subchannel of a subband overlapping with a subband boundary, with a RB set boundary, or both, a channel clearance procedure in the subband, in at least one adjacent subband, or both. In some examples, the sidelink manager 835 is capable of, configured to, or operable to support a means for transmitting sidelink communications in the guard RBs in the sequentially last subchannel of the subband based on a result of the channel clearance procedure.
[0182] In some examples, the subchannel RB manager 850 is capable of, configured to, or operable to support a means for determining that the sequentially last subchannel includes RBs from the RB set and the guard RBs. In some examples, the subchannel RB manager 850 is capable of, configured to, or operable to support a means for transmitting, based on the determining, the sidelink communications in the RBs from the RB set in the sequentially last subchannel.
[0183] In some examples, the subchannel RB manager 850 is capable of, configured to, or operable to support a means for determining that the sequentially last subchannel includes RBs from the RB set and the guard RBs. In some examples, the subchannel RB manager 850 is capable of, configured to, or operable to support a means for transmitting, based on the determining, the sidelink communications in the RBs from the RB set and in the guard RBs in the sequentially last subchannel.
[0184] In some examples, the OCB manager 845 is capable of, configured to, or operable to support a means for determining that transmitting the sidelink communications in the RB set fails to comply with an OCB threshold, where transmitting the sidelink communications in the guard RBs is based on the determining.
[0185] In some examples, the OCB manager 845 is capable of, configured to, or operable to support a means for determining that transmitting the sidelink communications in the RB set complies with an OCB threshold. In some examples, the OCB manager 845 is capable of, configured to, or operable to support a means for transmitting the sidelink communications in RBs of the sequentially last subchannel based on the channel clearance procedure being performed successfully in the subband.
[0186] In some examples, the OCB manager 845 is capable of, configured to, or operable to support a means for determining that transmitting the sidelink communications in the RB set complies with an OCB threshold. In some examples, the OCB manager 845 is capable of, configured to, or operable to support a means for transmitting the sidelink communications in RBs and the guard RBs of the sequentially last subchannel based on an interference level associated with the channel clearance procedure being performed successfully in the subband and the at least one adjacent subband.
[0187] In some examples, the OCB manager 845 is capable of, configured to, or operable to support a means for transmitting, to a sidelink UE receiving the sidelink communications, a puncturing indication identifying whether the sidelink communications are to be transmitted in the guard RBs.
[0188] Additionally, or alternatively, the communications manager 820 may support wireless communications at a UE in accordance with examples as disclosed herein. In some examples, the resource indication manager 825 is capable of, configured to, or operable to support a means for receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially first subchannel of a subband of the multiple subbands does not overlap with a subband boundary. In some examples, the sidelink manager 835 is capable of, configured to, or operable to support a means for receiving sidelink communications in the RB set and in the guard RBs of the subband based on a result of a channel clearance procedure.
[0189] In some examples, the subchannel boundary manager 840 is capable of, configured to, or operable to support a means for determining that the sequentially first subchannel of the subband includes the guard RBs and a subset of RBs of the RB set and that the sequentially first subchannel of the subband does not cross the subband boundary between the subband and at least one adjacent subband.
[0190] In some examples, the OCB manager 845 is capable of, configured to, or operable to support a means for determining that receiving the sidelink communications in the RB set fails to comply with an OCB threshold, where receiving the sidelink communications in the guard RBs is based on the determining.
[0191] Additionally, or alternatively, the communications manager 820 may support wireless communications at a UE in accordance with examples as disclosed herein. In some examples, the resource indication manager 825 is capable of, configured to, or operable to support a means for receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially last subchannel of a subband overlaps with a subband boundary, a RB set boundary, or both. In some examples, the sidelink manager 835 is capable of, configured to, or operable to support a means for receiving sidelink communications in RBs in the guard RBs in the sequentially last subchannel of the subband.
[0192] In some examples, the subchannel RB manager 850 is capable of, configured to, or operable to support a means for determining that the sequentially last subchannel includes RBs from the RB set and the guard RBs. In some examples, the subchannel RB manager 850 is capable of, configured to, or operable to support a means for receiving, based on the determining, the sidelink communications in the RBs from the RB set in the sequentially last subchannel.
[0193] In some examples, the subchannel RB manager 850 is capable of, configured to, or operable to support a means for determining that the sequentially last subchannel includes RBs from the RB set and the guard RBs. In some examples, the subchannel RB manager 850 is capable of, configured to, or operable to support a means for receiving, based on the determining, the sidelink communications in the RBs from the RB set and in the guard RBs in the sequentially last subchannel.
[0194] In some examples, the OCB manager 845 is capable of, configured to, or operable to support a means for determining that receiving the sidelink communications in the RB set complies with an OCB threshold. In some examples, the OCB manager 845 is capable of, configured to, or operable to support a means for receiving the sidelink communications in the RBs of the sequentially last subchannel based on the determining.
[0195] In some examples, the OCB manager 845 is capable of, configured to, or operable to support a means for determining that receiving the sidelink communications in the RB set complies with an OCB threshold. In some examples, the OCB manager 845 is capable of, configured to, or operable to support a means for receiving the sidelink communications in the RBs and the guard RBs of the sequentially last subchannel based on a puncturing indication.
[0196] In some examples, the OCB manager 845 is capable of, configured to, or operable to support a means for receiving, from a sidelink UE receiving the sidelink communications, the puncturing indication identifying whether the sidelink communications are to be received in the RBs, in the guard RBs, or both.
[0197] FIG. 9 shows a diagram of a system 900 including a device 905 that supports edge RB utilization in contiguous subchannels in accordance with one or more aspects of the present disclosure. The device 905 may be an example of or include the components of a device 605, a device 705, or a UE 115 as described herein. The device 905 may communicate (e.g., wirelessly) with one or more network entities 105, one or more UEs 115, or any combination thereof. The device 905 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, code 935, and a processor 940. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 945) .
[0198] The I / O controller 910 may manage input and output signals for the device 905. The I / O controller 910 may also manage peripherals not integrated into the device 905. In some cases, the I / O controller 910 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 910 may utilize an operating system such as or another known operating system. Additionally or alternatively, the I / O controller 910 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I / O controller 910 may be implemented as part of a processor, such as the processor 940. In some cases, a user may interact with the device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.
[0199] In some cases, the device 905 may include a single antenna 925. However, in some other cases, the device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 915 may communicate bi-directionally, via the one or more antennas 925, wired, or wireless links as described herein. For example, the transceiver 915 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 915 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 925 for transmission, and to demodulate packets received from the one or more antennas 925. The transceiver 915, or the transceiver 915 and one or more antennas 925, may be an example of a transmitter 615, a transmitter 715, a receiver 610, a receiver 710, or any combination thereof or component thereof, as described herein.
[0200] The memory 930 may include random access memory (RAM) and read-only memory (ROM) . The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed by the processor 940, cause the device 905 to perform various functions described herein. The code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 935 may not be directly executable by the processor 940 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the memory 930 may contain, among other things, a basic I / O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
[0201] The processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some cases, the processor 940 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor 940. The processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks supporting edge RB utilization in contiguous subchannels) . For example, the device 905 or a component of the device 905 may include a processor 940 and memory 930 coupled with or to the processor 940, the processor 940 and memory 930 configured to perform various functions described herein.
[0202] The communications manager 920 may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager 920 is capable of, configured to, or operable to support a means for transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications. The communications manager 920 is capable of, configured to, or operable to support a means for performing, based on the sequentially first subchannel of a subband not overlapping with a subband boundary, a channel clearance procedure in the subband and at least one adjacent subband. The communications manager 920 is capable of, configured to, or operable to support a means for transmitting sidelink communications in the RB set and in the guard RBs of the subband based on a result of the channel clearance procedure.
[0203] Additionally, or alternatively, the communications manager 920 may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager 920 is capable of, configured to, or operable to support a means for transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications. The communications manager 920 is capable of, configured to, or operable to support a means for performing, based on the sequentially last subchannel of a subband overlapping with a subband boundary, with a RB set boundary, or both, a channel clearance procedure in the subband, in at least one adjacent subband, or both. The communications manager 920 is capable of, configured to, or operable to support a means for transmitting sidelink communications in the guard RBs in the sequentially last subchannel of the subband based on a result of the channel clearance procedure.
[0204] Additionally, or alternatively, the communications manager 920 may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager 920 is capable of, configured to, or operable to support a means for receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially first subchannel of a subband of the multiple subbands does not overlap with a subband boundary. The communications manager 920 is capable of, configured to, or operable to support a means for receiving sidelink communications in the RB set and in the guard RBs of the subband based on a result of a channel clearance procedure.
[0205] Additionally, or alternatively, the communications manager 920 may support wireless communications at a UE in accordance with examples as disclosed herein. For example, the communications manager 920 is capable of, configured to, or operable to support a means for receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially last subchannel of a subband overlaps with a subband boundary, a RB set boundary, or both. The communications manager 920 is capable of, configured to, or operable to support a means for receiving sidelink communications in RBs in the guard RBs in the sequentially last subchannel of the subband.
[0206] By including or configuring the communications manager 920 in accordance with examples as described herein, the device 905 may support techniques for improved resource efficiency and sidelink communications by leveraging guard RBs in the first and / or last subchannel of a subband scheduled for sidelink communications.
[0207] In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 915, the one or more antennas 925, or any combination thereof. Although the communications manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 920 may be supported by or performed by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions executable by the processor 940 to cause the device 905 to perform various aspects of edge RB utilization in contiguous subchannels as described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.
[0208] FIG. 10 shows a flowchart illustrating a method 1000 that supports edge RB utilization in contiguous subchannels in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented by a UE or its components as described herein. For example, the operations of the method 1000 may be performed by a UE 115 as described with reference to FIGs. 1 through 9. In some examples, a UE may execute a set of instructions to control the functional elements of the wireless UE to perform the described functions. Additionally, or alternatively, the wireless UE may perform aspects of the described functions using special-purpose hardware.
[0209] At 1005, the method may include transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications. The operations of 1005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed by a resource indication manager 825 as described with reference to FIG. 8.
[0210] At 1010, the method may include performing, based on the sequentially first subchannel of a subband not overlapping with a subband boundary, a channel clearance procedure in the subband and at least one adjacent subband. The operations of 1010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed by an LBT manager 830 as described with reference to FIG. 8.
[0211] At 1015, the method may include transmitting sidelink communications in the RB set and in the guard RBs of the subband based on a result of the channel clearance procedure. The operations of 1015 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1015 may be performed by a sidelink manager 835 as described with reference to FIG. 8.
[0212] FIG. 11 shows a flowchart illustrating a method 1100 that supports edge RB utilization in contiguous subchannels in accordance with aspects of the present disclosure. The operations of the method 1100 may be implemented by a UE or its components as described herein. For example, the operations of the method 1100 may be performed by a UE 115 as described with reference to FIGs. 1 through 9. In some examples, a UE may execute a set of instructions to control the functional elements of the wireless UE to perform the described functions. Additionally, or alternatively, the wireless UE may perform aspects of the described functions using special-purpose hardware.
[0213] At 1105, the method may include transmitting an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications. The operations of 1105 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1105 may be performed by a resource indication manager 825 as described with reference to FIG. 8.
[0214] At 1110, the method may include performing, based on the sequentially last subchannel of a subband overlapping with a subband boundary, with a RB set boundary, or both, a channel clearance procedure in the subband, in at least one adjacent subband, or both. The operations of 1110 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1110 may be performed by an LBT manager 830 as described with reference to FIG. 8.
[0215] At 1115, the method may include transmitting sidelink communications in the guard RBs in the sequentially last subchannel of the subband based on a result of the channel clearance procedure. The operations of 1115 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1115 may be performed by a sidelink manager 835 as described with reference to FIG. 8.
[0216] FIG. 12 shows a flowchart illustrating a method 1200 that supports edge RB utilization in contiguous subchannels in accordance with aspects of the present disclosure. The operations of the method 1200 may be implemented by a UE or its components as described herein. For example, the operations of the method 1200 may be performed by a UE 115 as described with reference to FIGs. 1 through 9. In some examples, a UE may execute a set of instructions to control the functional elements of the wireless UE to perform the described functions. Additionally, or alternatively, the wireless UE may perform aspects of the described functions using special-purpose hardware.
[0217] At 1205, the method may include receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially first subchannel of a subband of the multiple subbands does not overlap with a subband boundary. The operations of 1205 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed by a resource indication manager 825 as described with reference to FIG. 8.
[0218] At 1210, the method may include receiving sidelink communications in the RB set and in the guard RBs of the subband based on a result of a channel clearance procedure. The operations of 1210 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed by a sidelink manager 835 as described with reference to FIG. 8.
[0219] FIG. 13 shows a flowchart illustrating a method 1300 that supports edge RB utilization in contiguous subchannels in accordance with aspects of the present disclosure. The operations of the method 1300 may be implemented by a UE or its components as described herein. For example, the operations of the method 1300 may be performed by a UE 115 as described with reference to FIGs. 1 through 9. In some examples, a UE may execute a set of instructions to control the functional elements of the wireless UE to perform the described functions. Additionally, or alternatively, the wireless UE may perform aspects of the described functions using special-purpose hardware.
[0220] At 1305, the method may include receiving an indication of sidelink resources including multiple subbands, each subband of the multiple subbands including a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, where the sequentially last subchannel of a subband overlaps with a subband boundary, a RB set boundary, or both. The operations of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by a resource indication manager 825 as described with reference to FIG. 8.
[0221] At 1310, the method may include receiving sidelink communications in RBs in the guard RBs in the sequentially last subchannel of the subband. The operations of 1310 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed by a sidelink manager 835 as described with reference to FIG. 8.
[0222] The following provides an overview of aspects of the present disclosure:
[0223] Aspect 1: A method for wireless communications at a UE, comprising: transmitting an indication of sidelink resources comprising multiple subbands, each subband of the multiple subbands comprising a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications; performing, based at least in part on the sequentially first subchannel of a subband not overlapping with a subband boundary, a channel clearance procedure in the subband and at least one adjacent subband; and transmitting sidelink communications in the RB set and in the guard RBs of the subband based at least in part on a result of the channel clearance procedure.
[0224] Aspect 2: The method of aspect 1, wherein performing the channel clearance procedure comprises: determining that the sequentially first subchannel of the subband comprises the guard RBs and a subset of RBs of the RB set and that the sequentially first subchannel of the subband does not cross the subband boundary between the subband and the at least one adjacent subband.
[0225] Aspect 3: The method of any of aspects 1 through 2, further comprising: determining that transmitting the sidelink communications in the RB set fails to comply with an OCB threshold, wherein transmitting the sidelink communications in the guard RBs is based at least in part on the determining.
[0226] Aspect 4: The method of any of aspects 1 through 3, further comprising: determining that the channel clearance procedure is successful in both the subband and the at least one adjacent subband, wherein transmitting the sidelink communications is based at least in part on a successful channel clearance procedure.
[0227] Aspect 5: A method for wireless communications at a UE, comprising: transmitting an indication of sidelink resources comprising multiple subbands, each subband of the multiple subbands comprising a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications; performing, based at least in part on the sequentially last subchannel of a subband overlapping with a subband boundary, with a RB set boundary, or both, a channel clearance procedure in the subband, in at least one adjacent subband, or both; and transmitting sidelink communications in the guard RBs in the sequentially last subchannel of the subband based at least in part on a result of the channel clearance procedure.
[0228] Aspect 6: The method of aspect 5, further comprising: determining that the sequentially last subchannel comprises RBs from the RB set and the guard RBs; and transmitting, based at least in part on the determining, the sidelink communications in the RBs from the RB set in the sequentially last subchannel.
[0229] Aspect 7: The method of any of aspects 5 through 6, further comprising: determining that the sequentially last subchannel comprises RBs from the RB set and the guard RBs; and transmitting, based at least in part on the determining, the sidelink communications in the RBs from the RB set and in the guard RBs in the sequentially last subchannel.
[0230] Aspect 8: The method of any of aspects 5 through 7, further comprising: determining that transmitting the sidelink communications in the RB set fails to comply with an OCB threshold, wherein transmitting the sidelink communications in the guard RBs is based at least in part on the determining.
[0231] Aspect 9: The method of any of aspects 5 through 8, further comprising: determining that transmitting the sidelink communications in the RB set complies with an OCB threshold; and transmitting the sidelink communications in RBs of the sequentially last subchannel based at least in part on the channel clearance procedure being performed successfully in the subband.
[0232] Aspect 10: The method of any of aspects 5 through 9, further comprising: determining that transmitting the sidelink communications in the RB set complies with an OCB threshold; and transmitting the sidelink communications in RBs and the guard RBs of the sequentially last subchannel based at least in part on an interference level associated with the channel clearance procedure being performed successfully in the subband and the at least one adjacent subband.
[0233] Aspect 11: The method of aspect 10, further comprising: transmitting, to a sidelink UE receiving the sidelink communications, a puncturing indication identifying whether the sidelink communications are to be transmitted in the guard RBs.
[0234] Aspect 12: A method for wireless communications at a UE, comprising: receiving an indication of sidelink resources comprising multiple subbands, each subband of the multiple subbands comprising a RB set available for sidelink communications and guard RBs in a sequentially first subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, wherein the sequentially first subchannel of a subband of the multiple subbands does not overlap with a subband boundary; and receiving sidelink communications in the RB set and in the guard RBs of the subband based at least in part on a result of a channel clearance procedure.
[0235] Aspect 13: The method of aspect 12, further comprising: determining that the sequentially first subchannel of the subband comprises the guard RBs and a subset of RBs of the RB set and that the sequentially first subchannel of the subband does not cross the subband boundary between the subband and at least one adjacent subband.
[0236] Aspect 14: The method of any of aspects 12 through 13, further comprising: determining that receiving the sidelink communications in the RB set fails to comply with an OCB threshold, wherein receiving the sidelink communications in the guard RBs is based at least in part on the determining.
[0237] Aspect 15: A method for wireless communications at a UE, comprising: receiving an indication of sidelink resources comprising multiple subbands, each subband of the multiple subbands comprising a RB set available for sidelink communications and guard RBs in a sequentially last subchannel of the respective subband, the guard RBs being unavailable for sidelink communications, wherein the sequentially last subchannel of a subband overlaps with a subband boundary, a RB set boundary, or both; and receiving sidelink communications in RBs in the guard RBs in the sequentially last subchannel of the subband.
[0238] Aspect 16: The method of aspect 15, further comprising: determining that the sequentially last subchannel comprises RBs from the RB set and the guard RBs; and receiving, based at least in part on the determining, the sidelink communications in the RBs from the RB set in the sequentially last subchannel.
[0239] Aspect 17: The method of any of aspects 15 through 16, further comprising: determining that the sequentially last subchannel comprises RBs from the RB set and the guard RBs; and receiving, based at least in part on the determining, the sidelink communications in the RBs from the RB set and in the guard RBs in the sequentially last subchannel.
[0240] Aspect 18: The method of any of aspects 15 through 17, further comprising: determining that receiving the sidelink communications in the RB set complies with an OCB threshold; and receiving the sidelink communications in the RBs of the sequentially last subchannel based at least in part on the determining.
[0241] Aspect 19: The method of any of aspects 15 through 18, further comprising: determining that receiving the sidelink communications in the RB set complies with an OCB threshold; and receiving the sidelink communications in the RBs and the guard RBs of the sequentially last subchannel based at least in part on a puncturing indication.
[0242] Aspect 20: The method of aspect 19, further comprising: receiving, from a sidelink UE receiving the sidelink communications, the puncturing indication identifying whether the sidelink communications are to be received in the RBs, in the guard RBs, or both.
[0243] Aspect 21: An apparatus for wireless communications at a UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 4.
[0244] Aspect 22: An apparatus for wireless communications at a UE, comprising at least one means for performing a method of any of aspects 1 through 4.
[0245] Aspect 23: A non-transitory computer-readable medium storing code for wireless communications at a UE, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 4.
[0246] Aspect 24: An apparatus for wireless communications at a UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 5 through 11.
[0247] Aspect 25: An apparatus for wireless communications at a UE, comprising at least one means for performing a method of any of aspects 5 through 11.
[0248] Aspect 26: A non-transitory computer-readable medium storing code for wireless communications at a UE, the code comprising instructions executable by a processor to perform a method of any of aspects 5 through 11.
[0249] Aspect 27: An apparatus for wireless communications at a UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 12 through 14.
[0250] Aspect 28: An apparatus for wireless communications at a UE, comprising at least one means for performing a method of any of aspects 12 through 14.
[0251] Aspect 29: A non-transitory computer-readable medium storing code for wireless communications at a UE, the code comprising instructions executable by a processor to perform a method of any of aspects 12 through 14.
[0252] Aspect 30: An apparatus for wireless communications at a UE, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 15 through 20.
[0253] Aspect 31: An apparatus for wireless communications at a UE, comprising at least one means for performing a method of any of aspects 15 through 20.
[0254] Aspect 32: A non-transitory computer-readable medium storing code for wireless communications at a UE, the code comprising instructions executable by a processor to perform a method of any of aspects 15 through 20.
[0255] It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined.
[0256] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
[0257] Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0258] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) .
[0259] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
[0260] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.
[0261] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”
[0262] The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.
[0263] In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label, or other subsequent reference label.
[0264] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration, ” and not “preferred” or “advantageous over other examples. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.
[0265] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
Claims
1.An apparatus for wireless communications at a user equipment (UE) , comprising:a processor;memory coupled with the processor; andinstructions stored in the memory and executable by the processor to cause the apparatus to:transmit an indication of sidelink resources comprising multiple subbands, each subband of the multiple subbands comprising a resource block set available for sidelink communications and guard resource blocks in a sequentially first subchannel of the respective subband, the guard resource blocks being unavailable for sidelink communications;perform, based at least in part on the sequentially first subchannel of a subband not overlapping with a subband boundary, a channel clearance procedure in the subband and at least one adjacent subband; andtransmit sidelink communications in the resource block set and in the guard resource blocks of the subband based at least in part on a result of the channel clearance procedure.2.The apparatus of claim 1, wherein the instructions to perform the channel clearance procedure are executable by the processor to cause the apparatus to:determine that the sequentially first subchannel of the subband comprises the guard resource blocks and a subset of resource blocks of the resource block set and that the sequentially first subchannel of the subband does not cross the subband boundary between the subband and the at least one adjacent subband.3.The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to:determine that transmitting the sidelink communications in the resource block set fails to comply with an occupied channel bandwidth threshold, wherein transmitting the sidelink communications in the guard resource blocks is based at least in part on the determining.4.The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to:determine that the channel clearance procedure is successful in both the subband and the at least one adjacent subband, wherein transmitting the sidelink communications is based at least in part on a successful channel clearance procedure.5.An apparatus for wireless communications at a user equipment (UE) , comprising:a processor;memory coupled with the processor; andinstructions stored in the memory and executable by the processor to cause the apparatus to:transmit an indication of sidelink resources comprising multiple subbands, each subband of the multiple subbands comprising a resource block set available for sidelink communications and guard resource blocks in a sequentially last subchannel of the respective subband, the guard resource blocks being unavailable for sidelink communications;perform, based at least in part on the sequentially last subchannel of a subband overlapping with a subband boundary, with a resource block set boundary, or both, a channel clearance procedure in the subband, in at least one adjacent subband, or both; andtransmit sidelink communications in the guard resource blocks in the sequentially last subchannel of the subband based at least in part on a result of the channel clearance procedure.6.The apparatus of claim 5, wherein the instructions are further executable by the processor to cause the apparatus to:determine that the sequentially last subchannel comprises resource blocks from the resource block set and the guard resource blocks; andtransmit, based at least in part on the determining, the sidelink communications in the resource blocks from the resource block set in the sequentially last subchannel.7.The apparatus of claim 5, wherein the instructions are further executable by the processor to cause the apparatus to:determine that the sequentially last subchannel comprises resource blocks from the resource block set and the guard resource blocks; andtransmit, based at least in part on the determining, the sidelink communications in the resource blocks from the resource block set and in the guard resource blocks in the sequentially last subchannel.8.The apparatus of claim 5, wherein the instructions are further executable by the processor to cause the apparatus to:determine that transmitting the sidelink communications in the resource block set fails to comply with an occupied channel bandwidth threshold, wherein transmitting the sidelink communications in the guard resource blocks is based at least in part on the determining.9.The apparatus of claim 5, wherein the instructions are further executable by the processor to cause the apparatus to:determine that transmitting the sidelink communications in the resource block set complies with an occupied channel bandwidth threshold; andtransmit the sidelink communications in resource blocks of the sequentially last subchannel based at least in part on the channel clearance procedure being performed successfully in the subband.10.The apparatus of claim 5, wherein the instructions are further executable by the processor to cause the apparatus to:determine that transmitting the sidelink communications in the resource block set complies with an occupied channel bandwidth threshold; andtransmit the sidelink communications in resource blocks and the guard resource blocks of the sequentially last subchannel based at least in part on an interference level associated with the channel clearance procedure being performed successfully in the subband and the at least one adjacent subband.11.The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to:transmit, to a sidelink UE receiving the sidelink communications, a puncturing indication identifying whether the sidelink communications are to be transmitted in the guard resource blocks.12.An apparatus for wireless communications at a user equipment (UE) , comprising:a processor;memory coupled with the processor; andinstructions stored in the memory and executable by the processor to cause the apparatus to:receive an indication of sidelink resources comprising multiple subbands, each subband of the multiple subbands comprising a resource block set available for sidelink communications and guard resource blocks in a sequentially first subchannel of the respective subband, the guard resource blocks being unavailable for sidelink communications, wherein the sequentially first subchannel of a subband of the multiple subbands does not overlap with a subband boundary; andreceive sidelink communications in the resource block set and in the guard resource blocks of the subband based at least in part on a result of a channel clearance procedure.13.The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to:determine that the sequentially first subchannel of the subband comprises the guard resource blocks and a subset of resource blocks of the resource block set and that the sequentially first subchannel of the subband does not cross the subband boundary between the subband and at least one adjacent subband.14.The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to:determine that receiving the sidelink communications in the resource block set fails to comply with an occupied channel bandwidth threshold, wherein receiving the sidelink communications in the guard resource blocks is based at least in part on the determining.15.An apparatus for wireless communications at a user equipment (UE) , comprising:a processor;memory coupled with the processor; andinstructions stored in the memory and executable by the processor to cause the apparatus to:receive an indication of sidelink resources comprising multiple subbands, each subband of the multiple subbands comprising a resource block set available for sidelink communications and guard resource blocks in a sequentially last subchannel of the respective subband, the guard resource blocks being unavailable for sidelink communications, wherein the sequentially last subchannel of a subband overlaps with a subband boundary, a resource block set boundary, or both; andreceive sidelink communications in resource blocks in the guard resource blocks in the sequentially last subchannel of the subband.16.The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to:determine that the sequentially last subchannel comprises resource blocks from the resource block set and the guard resource blocks; andreceive, based at least in part on the determining, the sidelink communications in the resource blocks from the resource block set in the sequentially last subchannel.17.The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to:determine that the sequentially last subchannel comprises resource blocks from the resource block set and the guard resource blocks; andreceive, based at least in part on the determining, the sidelink communications in the resource blocks from the resource block set and in the guard resource blocks in the sequentially last subchannel.18.The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to:determine that receiving the sidelink communications in the resource block set complies with an occupied channel bandwidth threshold; andreceive the sidelink communications in the resource blocks of the sequentially last subchannel based at least in part on the determining.19.The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to:determine that receiving the sidelink communications in the resource block set complies with an occupied channel bandwidth threshold; andreceive the sidelink communications in the resource blocks and the guard resource blocks of the sequentially last subchannel based at least in part on a puncturing indication.20.The apparatus of claim 19, wherein the instructions are further executable by the processor to cause the apparatus to:receive, from a sidelink UE receiving the sidelink communications, the puncturing indication identifying whether the sidelink communications are to be received in the resource blocks, in the guard resource blocks, or both.