Candidate resources and sidelink control information design for sidelink on unlicensed spectrum

Abstract

Disclosed are methods, systems, and computer-readable medium to perform operations including: receiving sidelink control information (SCI) specifying a total number of sub-channels over a resource pool that are candidates for a sidelink transmission; selecting, based on the total number of sub-channels over the resource pool specified in the SCI, a candidate single-slot resource that includes a set of contiguous sub-channels in a set of resource blocks; and transmitting, to a user equipment (UE), a physical sidelink shared channel (PSSCH) or physical sidelink control channel (PSCCH) transmission based on the selected candidate single-slot resource that includes the set of contiguous sub-channels in the set of resource blocks.

Description

Attorney Docket No.50759-0975WO1 / P63461WO1 Candidate Resources and Sidelink Control Information Design for Sidelink on Unlicensed Spectrum CLAIM OF PRIORITY

[0001] This application claims priority under 35 U.S.C. §119(e) to U.S. Patent Application Serial No. 63 / 531,702, filed on August 9, 2023, the entire contents of which are hereby incorporated by reference. BACKGROUND

[0002] Wireless communication networks provide integrated communication platforms and telecommunication services to wireless user devices. Example telecommunication services include telephony, data (e.g., voice, audio, and / or video data), messaging, and / or other services. The wireless communication networks have wireless access nodes that exchange wireless signals with the wireless user devices using wireless network protocols, such as protocols described in various telecommunication standards promulgated by the Third Generation Partnership Project (3GPP). Example wireless communication networks include time division multiple access (TDMA) networks, frequency-division multiple access (FDMA) networks, orthogonal frequency-division multiple access (OFDMA) networks, Long Term Evolution (LTE), and Fifth Generation New Radio (5G NR). The wireless communication networks facilitate mobile broadband service using technologies such as OFDM, multiple input multiple output (MIMO), advanced channel coding, massive MIMO, beamforming, and / or other features. SUMMARY

[0003] This disclosure describes how to define candidate resources for mode 2 resource allocation (selection). For mode 2, the transmitting UE is configured to select sidelink transmission resources itself. For mode 1, the network is configured to allocate sideline transmission resources for the transmitting UE. For mode 1, the network allocates resources from candidate resources that include an RB set in a resource pool. The network defines a sub- channel within each RB set. The sub-channels are in the frequency domain. In legacy operation, a set of consecutive sub-channels are selected for a set of N sub-channels (e.g., a set of 10 sub- channels). A UE can select the consecutive sub-channels for the transmission (e.g., 2 sub- channels). However, for sidelink operation using unlicensed spectrum (SL-U), a resource pool can include multiple RB sets. In an example, the resource pool includes two RB sets (RB set 1Attorney Docket No.50759-0975WO1 / P63461WO1 and RB set 2), each including 5 sub-channels. The UE can select a first set of sub-channels in RB set 1 or RB set 2. Alternatively, the UE can select a first sub-channel from RB set 1 and a second sub-channel from RB set 2, wherein resources are allocated from two different RB sets. In legacy resource allocation signaling, the resource allocation is designated (in either mode 1 or mode 2) by an index or starting sub-channel of the RB set, as the sub-channels that are selected are consecutive in legacy operation. For example, a UE may indicate the index of sub- channel 2 to allocate sub-channels 2 and 3 of the RB set as candidate resources. In SL-U, because there are multiple RB sets available, the allocation information includes additional information that enables other UEs to determine each of the sub-channel(s) and RB set(s) allocated for transmission by the UE.

[0004] This disclosure describes process to perform SL-U mode 2 resource selection to avoid RB sets in a resource pool for which there is consistent LBT failure for a UE. For example, a particular RB set may be allocated to other devices in a network (e.g., WI-FI, etc.). When the UE performs LBT operation, the UE may repeatedly fail to transmit because the channel is constantly occupied. For example, the UE may fail to transmit using a particular RB set more than a threshold number of times or for a threshold time period. In this case, the processes described herein enable the UE to exclude one or more RB sets from the candidate resources for mode 2 resource selection when those RB sets have caused LBT failure for the UE.

[0005] This disclosure describes the configuration of sidelink control information (SCI) and downlink control information (DCI) for SL-U. For example, when a first UE sends a transmission to a second UE for side link communication, the first UE transmits control information to the second UE to configure the communications link. The SCI specifies the COT-sharing information for the first UE and the second UE and possibly for one or more additional UEs. Legacy SCI does not specify COT-sharing information for SL-U. The DCI includes content for time and frequency resources for sidelink transmissions for SL-U. The DCI, for mode 1, specifies to the transmitting UE which resources the transmitting UE should use for SL communication. The DCI is modified to provide the time and frequency resources for SL-U operation.

[0006] In accordance with one aspect of the present disclosure, a process includes identifying, from a medium access control layer, data specifying a total number of sub-channels over a resource pool that are candidates for a sidelink transmission. The process includes selecting, based on the total number of sub-channels over the resource pool specified in the SCI, aAttorney Docket No.50759-0975WO1 / P63461WO1 candidate single-slot resource that includes a set of contiguous sub-channels in a set of resource blocks. The process includes transmitting, to a user equipment (UE), a physical sidelink shared channel (PSSCH) or physical sidelink control channel (PSCCH) transmission based on the selected candidate single-slot resource that includes the set of contiguous sub-channels in the set of resource blocks.

[0007] In some implementations, the number of candidate resource block sets is an integer number that is i) less than a total number of resource blocks of the resource pool and ii) divisible by the total number of sub-channels. In some implementations, the process includes selecting the number of candidate resource block sets based on the integer number.

[0008] In some implementations, the data from the MAC layer further specifies a total number of candidate resource block sets.

[0009] In some implementations, the process includes selecting the candidate single-slot resource based on the number of candidate resource block sets, wherein a number of contiguous sub-channels in a set of contiguous RB sets is^ೞೠ್^ಹ^ೃಳೞ^^െ 1, wherein ^^^௨^^ுis the total number of sub-channels and wherein ^^ோ^^^௧is the total number of candidate resource block sets.

[0010] In some implementations, the process includes selecting the candidate single-slot resource based on the number of candidate resource block sets. A number of contiguous sub- channels in a set of contiguous RB sets is^ೞೠ್^ಹ^ೃಳೞ^^െ 1, wherein ^^^௨^^ுis the total number of sub-channels and wherein ^^ோ^^^௧is theof candidate resource block sets. In some implementations, the number of candidate resource block sets is based on a channel busy ratio (CBR) of each of the possible resource block sets. In some implementations, the number of candidate resource block sets is based on a channel occupancy ratio (CR) of each of the possible resource block sets.

[0011] In some implementations, the process includes identifying a resource block set associated with a consistent failure a listen before talk (LBT) operation. In some implementations, the number of candidate resource block sets exclude the identified resource block set associated with the failed LBT operation.

[0012] In some implementations, the process includes identifying, from a medium access control (MAC) layer, a resource block set associated with a consistent failure of a listen before talk (LBT) operation. In some implementations, the process includes excluding, from a set ofAttorney Docket No.50759-0975WO1 / P63461WO1 candidate resource blocks for sending the sidelink transmission, the resource block set associated with the consistent failed LBT operation. In some implementations, a total number of candidate single slot resources excludes the resource block set associated with the consistent failed LBT operation. In some implementations, a total number of candidate single slot resources includes the resource block set associated with the consistent failed LBT operation. In some implementations, the process includes pausing physical sidelink feedback channel (PSFCH) transmissions on the excluded RB set even when a PSSCH with the corresponding PSFCH occasion on this RB set is received. In some implementations, the process includes transmitting a PSFCH on the excluded RB set after receiving PSSCH with the corresponding PSFCH occasion on the excluded RB set. In some implementations, the process includes determining whether to transmit a PSFCH based on the resource pool configuration or pre- configuration. In some implementations, the process includes determining whether to transmit a PSFCH based on SCI associated with the PSSCH transmission.

[0013] In some implementations, the candidate single-slot resource for transmission is defined as^^^௪,௫,௬, ^^௪ା^ି^,௫ା^ି^,௬൧, wherein y represents the slot index, w represents is the resource block set index, x represents the sub-channel index, and wherein J represents a number of contiguous sub-channels in a set of ^^^௨^^ு⁄ ^^ contiguous resource block sets.

[0014] In a general aspect, a process includes receiving, in downlink control information (DCI), configuration data specifying channel occupancy time (COT) sharing information; and transmitting, to one or more user equipment devices (UEs), the COT sharing information including identifiers of one or more UEs.

[0015] In some implementations, the COT sharing information including an additional identifiers field that specifies a UE destination identifier. In some implementations, the additional identifiers field further specifying a UE source identifier. In some implementations, the UE destination identifier being a group identifier. In some implementations, the COT sharing information including an additional identifiers number field that specifies whether the additional identifiers field includes a source identifier. In some implementations, the COT sharing information further specifying a COT duration in slots. In some implementations, the COT sharing information further specifying a COT offset value in slots. In some implementations, the DCI specifies a frequency resource assignment with a first field specifying a frequency assignment for a resource block set index and a second field specifying a frequency assignment for a sub-channel index in the resource block set.Attorney Docket No.50759-0975WO1 / P63461WO1

[0016] In a general aspect, a process includes receiving, in sidelink control information (SCI), configuration data specifying channel occupancy time (COT) sharing information; and transmitting, to one or more user equipment devices (UEs), PUSCH or PSSCH data based on the COT sharing information.

[0017] In some implementations, the COT sharing information including an additional identifiers field that specifies a UE destination identifier. In some implementations, the additional identifiers field further specifying a UE source identifier. In some implementations, the UE destination identifier being a group identifier. In some implementations, the COT sharing information including an additional identifiers number field that specifies whether the additional identifiers field includes a source identifier. In some implementations, the COT sharing information further specifying a COT duration in slots. in some implementations, the COT sharing information further specifying a COT offset value in slots.

[0018] In some implementations, the SCI includes fields of SCI format 2-A comprising a hybrid automatic repeat request (HARQ) process number; a new data indicator; a redundancy version; a source identifier; a destination identifier; a HARQ feedback enabled / disabled indicator; a CSI request; and a cast type indicator.

[0019] In some implementations, the SCI includes a zone identifier and a communication range value. In some implementations, the SCI includes a joint indicator specifying both a COT starting offset and a COT duration.

[0020] In a general aspect, a non-transitory computer storage medium encoded with instructions that, when executed by one or more computers, cause the one or more computers to perform the processes described herein.

[0021] In a general aspect, a system comprising one or more computers and one or more storage devices on which are stored instructions that are operable, when executed by the one or more computers, to cause the one or more computers to perform the processes described herein.

[0022] In a general aspect, an apparatus comprises one or more processors configured for performing wireless communication by performing operations for the processes described herein.

[0023] In a general aspect, one or more processors are configured for performing wireless communication by performing operations for the processes described herein.Attorney Docket No.50759-0975WO1 / P63461WO1

[0024] The details of one or more embodiments of these systems and methods are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of these systems and methods will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE FIGURES

[0025] FIG. 1 illustrates an example communication system that includes sidelink communications, according to some implementations.

[0026] FIGS. 2A-2C each illustrate a flowchart of an example method for resource allocation or SL-U, according to some implementations.

[0027] FIG. 3 illustrates a flowchart of an example method for resource allocation or SL-U, according to some implementations.

[0028] FIGS. 4A-4B each illustrates a flowchart of an example method for COT-sharing, according to some implementations.

[0029] FIG.5 illustrates an example user equipment (UE), according to some implementations.

[0030] FIG.6 illustrates an example access node, according to some implementations. DETAILED DESCRIPTION

[0031] In sidelink (SL) communications, a first UE is configured to communicate directly with a second UE without a base station. For SL transmissions, a UE is configured to perform operations based on available resource block (RB) sets in the unlicensed spectrum. In the unlicensed spectrum, the UE is competing with other technologies (e.g., WI-FI devices) for channel access. The first UE selects a channel for SL-U communications and subsequently can transmit to another UE using the selected channel. The UE may not always successfully complete a transmission, such as physical sidelink shared channel (PSSCH) or physical sidelink control channel (PSCCH) transmission. Specifically, listen-before-talk (LBT) may fail if the channel is occupied by another transmission (e.g., WI-FI). For LBT, the UE monitors the channel for a time duration before attempting to transmit on the channel.

[0032] Once the UE occupies the channel, the UE can share the channel with another UE. The time for which the UE accesses the channel is called channel occupancy time (COT). The COT of the UE can be shared with another UE by COT-sharing. For example, a first UE can use theAttorney Docket No.50759-0975WO1 / P63461WO1 resources that are allocated on the channel. The first UE can transmit to the second UE via unicast. The first UE may also share channel resources with a third UE with which the first UE is not communicating with sidelink data (e.g., using COT-sharing). The COT-sharing by a first UE can be performed based on COT-sharing information that is received by the UE from a COT initiating device. The COT initiating device, such as the first UE, can transmit data (e.g., by a unicast transmission) that specifies the COT-sharing information including one or more device identifiers. The first UE can initiate COT-sharing based on the identifier or identifiers included in the COT-sharing information. In another example, a responding UE can send a groupcast or broadcast specifying a destination identifier. The destination identifier is included in the responding UE’s transmission, such as PSCCH or PSSCH transmission. When the destination identifier matches a destination identifier from a COT initiator’s groupcast or broadcast transmission that included the COT-sharing information, or matches an additional identifier or identifiers included in the COT-sharing information, the first UE may perform COT-sharing.

[0033] The UE can use the channel access priority class (CAPC) to initiate COT-sharing. The CAPC can indicate how long the LBT is used regarding COT-sharing. This can be for mode 1 or mode 2 resource selection. The UE can indicate the COT-sharing configured based on either time domain information in the COT-sharing information or frequency domain information in the COT-sharing information. For example, particular resources in the time domain, such as RB sets, are designated by the UE for COT sharing. In another example, a UE can designate resources in the frequency domain for COT-sharing, such as specific frequencies.

[0034] This disclosure describes how to define candidate resources for mode 2 resource allocation (selection). For mode 2, the transmitting UE is configured to select sidelink transmission resources itself. For mode 1, the network is configured to allocate sideline transmission resources for the transmitting UE. For mode 1, the network allocates resources from candidate resources that include an RB set in a resource pool. The network defines a sub- channel within each RB set. The sub-channels are in the frequency domain. In legacy operation, a set of consecutive sub-channels are selected for a set of N sub-channels (e.g., a set of 10 sub- channels). A UE can select the consecutive sub-channels for the transmission (e.g., 2 sub- channels). However, for sidelink operation using unlicensed spectrum (SL-U), a resource pool can include multiple RB sets. In an example, the resource pool includes two RB sets (RB set 1 and RB set 2), each including 5 sub-channels. The UE can select a first set of sub-channels in RB set 1 or RB set 2. Alternatively, the UE can select a first sub-channel from RB set 1 and aAttorney Docket No.50759-0975WO1 / P63461WO1 second sub-channel from RB set 2, wherein resources are allocated from two different RB sets. In legacy resource allocation signaling, the resource allocation is designated (in either mode 1 or mode 2) by an index or starting sub-channel of the RB set, as the sub-channels that are selected are consecutive in legacy operation. For example, a UE may indicate the index of sub- channel 2 to allocate sub-channels 2 and 3 of the RB set as candidate resources. In SL-U, because there are multiple RB sets available, the allocation information includes additional information that enables other UEs to determine each of the sub-channel(s) and RB set(s) allocated for transmission by the UE.

[0035] This disclosure describes processes to perform SL-U mode 2 resource selection to avoid RB sets in a resource pool for which there is consistent LBT failure for a UE. For example, a particular RB set may be allocated to other devices in a network (e.g., WI-FI, etc.). When the UE performs LBT operation, the UE may repeatedly fail to transmit because the channel is constantly occupied. For example, the UE may fail to transmit using a particular RB set more than a threshold number of times or for a threshold time period. In this case, the processes described herein enable the UE to exclude one or more RB sets from the candidate resources for mode 2 resource selection when those RB sets have caused LBT failure for the UE.

[0036] This disclosure describes the configuration of sidelink control information (SCI) and downlink control information (DCI) for SL-U. For example, when a first UE sends a transmission to a second UE for sidelink communication, the first UE transmits control information to the second UE to configure the communications link. The SCI specifies the COT-sharing information for the first UE and the second UE and possibly for one or more additional UEs. Legacy SCI does not specify COT-sharing information for SL-U. The DCI includes content for time and frequency resources for sidelink transmissions for SL-U. The DCI, for mode 1, specifies to the transmitting UE which resources the transmitting UE should use for SL communication. The DCI is modified to provide the time and frequency resources for SL-U operation.

[0037] FIG. 1 illustrates an example communication system 100 that includes sidelink communications, according to some implementations. It is noted that the system of FIG. 1 is merely one example of a possible system, and that features of this disclosure may be implemented in other wireless communication systems.

[0038] The following description is provided for an example communication system that operates in conjunction with fifth generation (5G) networks as provided by 3GPP technicalAttorney Docket No.50759-0975WO1 / P63461WO1 specifications. However, the example implementations are not limited in this regard and the described examples may apply to other networks that may benefit from the principles described herein, such as 3GPP Long Term Evolution (LTE) networks, Wi-Fi or Worldwide Interoperability for Microwave Access (WiMaX) networks, and the like. Furthermore, other types of communication standards are possible, including future 3GPP systems (e.g., Sixth Generation (6G)), IEEE 802.16 protocols, or the like. While aspects may be described herein using terminology commonly associated with 5G NR, aspects of the present disclosure can be applied to other systems, such as 3G, 4G, and / or systems subsequent to 5G (e.g., 6G).

[0039] Frequency bands for 5G NR may be separated into two different frequency ranges. Frequency Range 1 (FR1) may include frequency bands operating in sub-6 GHz frequencies, some of which are bands that may be used by previous standards and may potentially be extended to cover new spectrum offerings from 410 Megahertz (MHz) to 7125 MHz. Frequency Range 2 (FR2) may include frequency bands from 24.25 GHz to 52.6 GHz. Bands in the millimeter wave (mmWave) range of FR2 may have smaller coverage but potentially higher available bandwidth than bands in the FR1.

[0040] As shown, the communication system 100 includes a number of user devices. More specifically, the communication system 100 includes two UEs 105 (UE 105-1 and UE 105-2 are collectively referred to as “UE 105” or “UEs 105”), two base stations 110 (base station 110-1 and base station 110-2 are collectively referred to as “base station 110” or “base stations 110”), two cells 115 (cell 115-1 and cell 115-2 are collectively referred to as “cell 115” or “cells 115”), and one or more servers 135 in a core network (CN) 140 that is connected to the Internet 145.

[0041] In some implementations, the UEs 105 can directly communicate with base stations 110 via links 120 (link 120-1 and link 120-2 are collectively referred to as “link 120” or “links 120”), which utilize a direct interface with the base stations referred to as a “Uu interface.” Each of the links 120 can represent one or more channels. The links 120 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communication protocols, such as a GSM protocol, a CDMA network protocol, a UMTS protocol, a 3GPP LTE protocol, an Advanced long term evolution (LTE-A) protocol, a LTE- based access to unlicensed spectrum (LTE-U), a 5G protocol, a NR protocol, an NR-based access to unlicensed spectrum (NR-U) protocol, and / or any of the other communications protocols discussed herein.Attorney Docket No.50759-0975WO1 / P63461WO1

[0042] As shown, certain user devices may be able to conduct communications with one another directly, e.g., without an intermediary infrastructure device such as base station 110-1. In this example, UE 105-1 may conduct communications directly with UE 105-2. Similarly, the UE 105-2 may conduct communications directly with UE 105-1. Such peer-to-peer communications may utilize a “sidelink” interface such as a PC5 interface. In certain implementations, the PC5 interface supports direct cellular communication between user devices (e.g., between UEs 105), while the Uu interface supports cellular communications with infrastructure devices such as base stations. For example, the UEs 105 may use the PC5 interface for a radio resource control (RRC) signaling exchange between the UEs (also called PC5-RRC signaling). The PC5 / Uu interfaces are used only as an example, and PC5 as used herein may represent various other possible wireless communications technologies that allow for direct sidelink communications between user devices, while Uu in turn may represent cellular communications conducted between user devices and infrastructure devices, such as base stations.

[0043] In some implementations, the UEs 105 may be configured with parameters for communicating via the Uu interface and / or the sidelink interface. In some examples, the UEs 105 may be “pre-configured” with some parameters. In these examples, the parameters may be hardwired into the UEs 105 or coded into spec. Additionally and / or alternatively, the UEs 105 may receive the parameters from the one or more of the base stations 110.

[0044] To transmit / receive data to / from one or more base stations 110 or UEs 105, the UEs 105 may include a transmitter / receiver (or alternatively, a transceiver), memory, one or more processors, and / or other like components that enable the UEs 105 to operate in accordance with one or more wireless communications protocols and / or one or more cellular communications protocols. The UEs 105 may have multiple antenna elements that enable the UEs 105 to maintain multiple links 120 and / or sidelinks 125 to transmit / receive data to / from multiple base stations 110 and / or multiple UEs 105. For example, as shown in FIG.1, UE 105-1 may connect with base station 110-1 via link 120 and simultaneously connect with UE 105-2 via sidelink 125.

[0045] In some implementations, one or more sidelink radio bearers may be established on the sidelink 125. The sidelink radio bearers can include signaling radio bearers (SL-SRB) and / or data radio bearers (SL-DRB).Attorney Docket No.50759-0975WO1 / P63461WO1

[0046] The PC5 interface may alternatively be referred to as a sidelink interface and may include one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Feedback Channel (PSFCH), and / or any other like communications channels. The PSFCH carries feedback related to the successful or failed reception of a sidelink transmission. The PSSCH can be scheduled by sidelink control information (SCI) carried in the sidelink PSCCH. In some examples, the sidelink interface can operate on an unlicensed spectrum (e.g., in the unlicensed 5 Gigahertz (GHz) and 6 GHz bands) or a (licensed) shared spectrum.

[0047] In one example, the sidelink interface implements vehicle-to-everything (V2X) communications. The V2X communications may, for example, adhere to 3GPP Cellular V2X (C-V2X) specifications, or to one or more other or subsequent standards whereby vehicles and other devices and network entities may communicate. V2X communications may utilize both long-range (e.g., cellular) communications as well as short- to medium-range (e.g., non- cellular) communications. Cellular-capable V2X communications may be called Cellular V2X (C-V2X) communications. C-V2X systems may use various cellular radio access technologies (RATs), such as 4G LTE or 5G NR RATs (or RATs subsequent to 5G, e.g., 6G RATs). Certain LTE standards usable in V2X systems may be called LTE-Vehicle (LTE-V) standards. As used herein in the context of V2X systems, and as defined above, the term “user devices” may refer generally to devices that are associated with mobile actors or traffic participants in the V2X system, e.g., mobile (able-to-move) communication devices such as vehicles, pedestrian user equipment (PUE) devices, and roadside units (RSUs).

[0048] In some implementations, UEs 105 may be physical hardware devices capable of running one or more applications, capable of accessing network services via one or more radio links 120 with a corresponding base station 110 (also referred to as a “serving” base station), and capable of communicating with one another via sidelink 125. Link 120 may allow the UEs 105 to transmit and receive data from the base station 110 that provides the link 120. The sidelink 125 may allow the UEs 105 to transmit and receive data from one another. The sidelink 125 between the UEs 105 may include one or more channels for transmitting information from UE 105-1 to UE 105-2 and vice versa and / or between UEs 105 and UE-type RSUs and vice versa.Attorney Docket No.50759-0975WO1 / P63461WO1

[0049] In some implementations, the base stations 110 are capable of communicating with one another over a backhaul connection 130 and may communicate with the one or more servers 135 within the CN 140 over another backhaul connection 133. The backhaul connections can be wired and / or wireless connections.

[0050] In some implementations, the UEs 105 are configured to use a resource pool for sidelink communications. A sidelink resource pool defines the time-frequency resources used for sidelink communications, and may be divided into multiple time slots, frequency channels, and frequency sub-channels. In some examples, the UEs 105 are synchronized and perform sidelink transmissions aligned with slot boundaries. A UE may be expected to select several slots and sub-channels for transmission of the transport block. In some examples, a UE may use different sub-channels for transmission of the transport block across multiple slots within its own resource selection window.

[0051] In some implementations, an exceptional resource pool may be configured for the UEs 105, perhaps by the base stations 110. The exceptional resource pool includes resources that the UEs 105 can use in exceptional cases, such as Radio Link Failure (RLF). The exceptional resource pool may include resources selected based on a random allocation of resources.

[0052] In some implementations, a UE that is initiating a communication with another UE is referred to as a transmitter UE (TX UE), and the UE receiving the communication is referred to as a receiver UE (RX UE). For example, UE 105-1 may be a TX UE and UE 105-2 may be an RX UE. Although FIG.1 illustrates a single TX UE communicating with a single RX UE, a TX UE may communicate with more than one RX UE via sidelink.

[0053] In some implementations, a TX UE that is initiating sidelink communication may determine the available resources (e.g., sidelink resources) and may select a subset of these resources to communicate with an RX UE based on a resource allocation scheme. Example resource allocation schemes include Mode 1 and Mode 2 resource allocation schemes. In Mode 1 resource allocation scheme (referred to as “Mode 1”), the resources are allocated by a network node for in-coverage UEs. In Mode 2 resource allocation scheme (referred to as “Mode 2”), the TX UE selects the sidelink resources (e.g., sidelink transmission resources).

[0054] In some implementations, the communication system 100 supports different cast types, including unicast, broadcast, and groupcast (or multicast) communications. Unicast refers to direction communications between two UEs. Broadcast refers to a communication that is broadcast by a single UE to a plurality of other UEs. Groupcast refers to communications thatAttorney Docket No.50759-0975WO1 / P63461WO1 are sent from a single UE to a set of UEs that satisfy a certain condition (e.g., being a member of a particular group).

[0055] FIGS. 2A-2C each illustrate a flowchart of example processes 200, 210, and 220 for resource allocation or SL-U, according to some implementations. For clarity of presentation, the description that follows generally describes each of the processes 200, 210, and 220 in the context of the other figures in this description. For example, each of processes 200, 210, and 220 can be performed by UE 105-1 or UE 105-2 of FIG.1. Processes 200, 210, and 220 can be performed, for example, by any suitable system, environment, software, hardware, or a combination of systems, environments, software, and hardware, as appropriate. In some implementations, various steps of processes 200, 210, and 220 can be run in parallel, in combination, in loops, or in any order.

[0056] FIG. 2A illustrates a flowchart of an example process 200 for resource allocation or SL-U. For process 200, the resource allocation is in an interlace RB-based PSCCH or PSSCH transmission. The process 200 is related to a single slot resource, and not a multi-slot resource. For mode 1, the medium access control (MAC) layer (or a higher layer) provides information specifying a number of sub-channels for the resource selection for SL transmission. this information indicates to the physical layer the number of sub-channels for resource selection (e.g., 1 sub-channel, 2 sub-channels, etc.).

[0057] For process 200, the MAC layer provides (202), to the physical layer, only the value for ^^^௨^^ு, or the total number of sub-channels that are to be used for a PSCCH or PSSCH transmission in a slot. For example, the number can be 1 sub-channel, 2 sub-channels, 4 sub- channels, etc. The MAC layer provides the overall number of sub-channels without specifying the number of RB sets.

[0058] The physical layer is configured to determine (204) a set of candidate single-slot resources for sidelink transmission based on the data received from the MAC layer. The resource allocation is now described. In this case, the UE can allocate all integer numbers of RB sets divisible by ^^^௨^^ுbelow a total number of RB sets of the resource pool. For example, the number of subchannels to be used for a PSCCH or PSSCH transmission is four ( ^^^௨^^ு=4) and the resource pool has 4 RB sets. Then, the possible number of RB sets can be 1, 2, or 4. Specifically, there can be four sub-channels can be selected from 4 different RB sets (1 each). In another example, 2 sub-channels can be selected from 2 different RB sets (2 each). In another example, all four sub-channels can be selected from a single RB set. In some implementations,Attorney Docket No.50759-0975WO1 / P63461WO1 the selected sub-channels are at the same frequencies in each RB set (e.g., the same sub- channels for each different RB set).

[0059] The MAC layer of the UE selects (206) a resource from the physical layer reported candidate resource set. The MAC layer selects a single-slot resource for sidelink transmission that is defined as a set of contiguous sub-channels in a set of contiguous RB sets. In this example, the process 200 includes selecting a candidate single-slot resource for transmission^^^௪,௫,௬, ^^௪ା^ି^,௫ା^ି^,௬൧. The UE can transmit (208), to a UE, a PSSCH or PSCCHselected candidate single-slot resource for transmission including a setin a set of contiguous RB sets. There are three dimensions to selecting the resource for transmission. A single-slot sub-channel is represented by ^^௪,௫,௬, where “y” represents the slot index, or the time domain resource. “x” represents the sub- channel index, or the frequency domain index. “w” represents the RB set index. Rw,x,y is the leading sub-channel and RB set index in a slot. Rw+K-1,x+J-1,y represents the ending sub-channel and RB set index in a slot. “y” is unchanged because the candidate resource for select includes a single slot. “w+K-1” represents the ending RB set index. “x+J-1” represents the ending sub- channel index. These together represent the matrix of candidate resources including the sub- channels and RB sets in the slot y. The UE defines the candidate single-slot resource as a set of J contiguous sub-channels in a set of ^^^௨^^ு⁄ ^^ contiguous RB sets. Specifically, this candidate resource ^ ^^௪,௫,௬, ^^௪ା^ି^,௫ା^ି^,௬൧ includes a set of single-slot sub-channels^^ , with w+k, i ᇱௌ^௪ା^,௫ା^,௬n slot ^^௬ , where ^^ ൌ 0,⋯ , ^^ െ 1 and ^^ ൌ0,⋯ , ^^ െ 1; ^^ ൌ ^ೞೠ್^ಹ^ . In an example, [R0,0,y, R1,1,y] specifies that R0,0,y is the startingresource index andcandidate resources include a set of single-slot sub-channels {R0,0,y; R0,1,y; R1,0,y; R1,1,y}. In another example, the candidate resources can be specified as [R0,0,y, R0,3,y], indicating that the candidate resources are {R0,0,y; R0,1,y; R0,2,y; R0,3,y}.

[0060] FIG.2B illustrates a flowchart of an example process 210 for resource allocation or SL- U. For process 210, the resource allocation is in an interlace RB-based PSCCH or PSSCH transmission. The process 210 is related to a single slot resource, and not a multi-slot resource. For mode 2, the medium access control (MAC) layer (or a higher layer) provides information specifying a number of sub-channels for the resource selection for SL transmission. this information indicates to the physical layer the number of sub-channels for resource selection (e.g., 1 sub-channel, 2 sub-channels, etc.).Attorney Docket No.50759-0975WO1 / P63461WO1

[0061] In process 210, the MAC layer provides (212) only the value for ^^^௨^^ு, or the total number of sub-channels over a resource pool, similar to process 200. In process 210, the physical layer determines a number of RB sets for the resource selection. The physical layer first determines (214) a single number of possible RB sets ( ^^ோ^^^௧). The number of RB sets is based on one or more of the following. The number of RB sets can be based on a channel busy ratio (CBR) of each of the RB sets. The number of RB sets can be based on a channel occupancy ratio (CR) of each of the RB sets. The number of RB sets can be based on which RB sets have shown consistent LBT failure, as previously described. The number of RB sets can be based on how many total RB sets are available. The MAC layer selects (216) a candidate single-slot resource for transmission. The single-slot candidate resource ^ ^^௪,௫,௬, ^^௪ା^ି^,௫ା^ି^,௬൧ is defined as a set of J contiguous sub-channels in a set of ^^^௨^^ு⁄ ^^ sets.Specifically, this candidate resource ^ ^^௪,௫,௬, ^^௪ା^ି^,௫ା^ି^,௬൧ a set sub-channels ^^ , with sub-channel x+j and RB set w ᇱௌ^௪ା^,௫ା^,௬ +k, in slot ^^௬ , where ^^ ൌ0,⋯ , ^ೞೠ್^ಹ^ೃಳೞ^^ െ 1 and ^^ ൌ 0,⋯ , ^^ோ^^^௧ െ 1, similar to the examples described for process 200.on the number of available RB sets determined bythe physical layer. The physical layer of the UE can transmit (218) a PSSCH or PSCCH transmission based on the selected single-slot resource.

[0062] FIG.2C illustrates a flowchart of an example process 220 for resource allocation or SL- U. For process 220, the resource allocation is in an interlace on an RB-based PSCCH or PSSCH transmission, similar to processes 200 and 210. Generally, the process 220 is related to a single slot resource, and not a multi-slot resource. For mode 1, the medium access control (MAC) layer (or a higher layer) provides information specifying a number of sub-channels for the resource selection for SL transmission. this information indicates to the physical layer the number of sub channels for resource selection (e.g., 1 sub-channel, 2 sub-channels, etc.).

[0063] For process 220, the MAC layer provides (222) the values of each of the number of RB sets ( ^^ோ^^^௧) and the number of sub-channels ( ^^^௨^^ு) are available in the RB set(s) for the PSSCH or PSCCH transmission. The physical layer of the UE determines (224) a set of candidate resources, as previously described. The MAC layer of the UE selects (226) a single- slot resource for transmission. The single-slot candidate resource for transmission ^ ^^௪,௫,௬, ^^௪ା^ି^,௫ା^ି^,௬൧ is defined as a set of J contiguous sub-channels in a set of ^^^௨^^ு⁄^^this candidate resource ^ ^^௪,௫,௬, ^^௪ା^ି^,௫ା^ି^,௬൧ includes a set of single-slot sub-channels ^^௪ା^,௫ା^,௬, with sub-channel x+j and RB set w+k, in slot ^^௬ᇱ^^,Attorney Docket No.50759-0975WO1 / P63461WO1 where ^^ ൌ 0,⋯ ,^ೞೠ್^ಹ^ೃಳೞ^^െ 1 and ^^ ൌ 0,⋯ , ^^ோ^^^௧െ 1, similar to the examples described for process 200 and 210. The candidate resources are selected based on the number of available RB sets determined by the physical layer. The process 220 includes transmitting (228), by the physical layer of the UE, a PSSCH or PSCCH transmission based on the selected single-slot resource.

[0064] In some implementations, if the higher layer parameter transmissionStructureForPSCCHandPSSCH is set to ‘interlaceRB’, a candidate multi-slot resource Rx,y,z is defined as a set of LsubCH contiguous subchannels starting from subchannel x in Nslot,MCStconsecutive slots starting from slot t’SLyin LRBsetcontiguous RB sets starting from RB set z, when the set of Nslot,MCSt slots that are consecutive in physical slots. A candidate single slot resource Rx,y,z is defined as a set of LsubCH contiguous subchannels starting from subchannel x in slot t’SLyin LRBsetcontiguous RB sets starting from RB set z.

[0065] FIG.3 illustrates a flowchart of an example process 300 for resource allocation or SL- U in interlace RB-based PSCCH / PSSCH, according to some implementations. For clarity of presentation, the description that follows generally describes the process 300 in the context of the other figures in this description. For example, the process 300 can be performed by UE 105-1 or UE 105-2 of FIG.1. The process 300 can be performed, for example, by any suitable system, environment, software, hardware, or a combination of systems, environments, software, and hardware, as appropriate. In some implementations, various steps of the process 300 can be run in parallel, in combination, in loops, or in any order.

[0066] Process 300 is performed by the UE for handling RB sets with consistent LBT failure. The UE is configured for mode 2 resource selection or reselection when the UE detects that there is a consistent LBT (C-LBT) failure on an RB set. In this scenario, the MAC layer signals (302) to the physical layer data including RB set information that specifies where SL C-LBT failure is detected. During resource selection, reselection, re-evaluation or pre-emption checking, the physical layer is configured to exclude (304) the resources for the RB set where C-LBT failure is detected. In some implementations, when the MAC layer signals to the physical layer that an RB set index (e.g., p) where SL C-LBT failure was detected, the physical layer is configured to exclude a single-slot resource [Rw, x, y, Rw+K-1, x+J-1,y] from the candidate resource set if ^^ ∈ ^ ^^, ^^ ^ ^^^. Here, p represents the excluded resource set index with C-LBT. “w” represents the starting RB set index of the excluded candidate resource, and w+K represents the ending RB set index of the excluded candidate resources. For example, if aAttorney Docket No.50759-0975WO1 / P63461WO1 candidate single-slot resource is [Rw, x, y, Rw+K-1,x+J-1,y], which includes a set of single-slot sub- channels Rw+k, x+j, ywith 0<= k<= K-1, 0<= j <=J-1. A candidate resource of [R1, 3, 0, R2, 3, 0], which is composed of sub-channels {R1,3,0, R2,3,0}. If p is 1 or 2, (i.e., RB set 1 or RB set 2 has C-LBT and is not suitable for resource selection), then the resource [R1, 3, 0, R2, 3, 0] is excluded from candidate resource set. If p is 0, then the resource [R1, 3, 0, R2, 3, 0] is still in candidate resource set.

[0067] In some implementations, the initial total number of candidate single-slot resources (Mtotal) (i.e., in Step 1 of resource selection procedure in Section 8.1.4 of TS 38.214) does not include the resources in C-LBT failure RB sets. In this case, the total number of candidate single-slot resources is denoted by Mtotal, which already excludes any resources having overlap with the RB sets with C-LBT failure in the middle of Step 1 of resource selection procedure inSection 8.1.4 of TS 38.214 for step 302. Prior to excluding the identified resource from the candidate resource set, the number of total RB sets is reduced to exclude the identified number of RB sets with C-LBT failure. In an example, a resource pool in a resource selection window includes 300 resources, and each RB set includes 100 resources. In this example, a given RB set has consistent LBT failure, so the number of available resources is reduced to 200 (i.e., Mtotal=200). The physical layer reports the “good” candidate resources to a higher layer based on a configured percentage. For example, the physical layer can report 20% of the 200 remaining resources (40 total) as candidate resources for SL-U transmissions to the higher layer.

[0068] In some implementations, if rbSetsWithConsecutiveLBTFailure is provided, the UE excludes candidate single slot resources or candidate multi-slot resources whose associated one or more RB sets is or are included in the rbSetsWithConsecutiveLBTFailure parameter. The total number of remaining single slot resources or candidate multi-slot resources is denoted by Mtotal.

[0069] In some implementations, the initial total number of candidate single-slot resources (Mtotal) includes the resources in C-LBT failure RB sets. In this scenario, the total number of single-slot resources is denoted by Mtotal, which includes resources having overlap with the RB sets with C-LBT failure in stepThen, the resources having overlap with the RB sets with C-LBT failure are excluded from this initial set of candidate resources at the end of Step 1 of resource selection procedure in Section 8.1.4 of TS 38.214, which does not change the value of Mtotal. The CE field of “sl-TxPercentageList” may be differently configured forAttorney Docket No.50759-0975WO1 / P63461WO1 this case to account for the subsequent exclusion of RB sets. This example is performed as part of the resource selection. For example, a resource pool within a resource selection window includes 300 resources (i.e., Mtotal=300)., and each RB set includes 100 resources (RBs). In this example, a given RB set has consistent LBT failure, so the number of available candidate resources is reduced to 200. The physical layer reports the “good” candidate resources to a higher layer based on a configured percentage that is determined based on the original set of 300 resources. The physical layer therefore reports 60 (i.e., 20% of Mtotal=300) “good” resources to the higher layer.

[0070] When a UE detects consistent LBT failure on an RB set, in one implementation, it does not transmit PSFCH on this RB set even if it receives PSSCH with the corresponding PSFCH occasion on this RB set. This implies the consistent LBT failure also pauses the PSFCH transmissions. In another implementation, it transmits PSFCH on this RB set, after receiving PSSCH with the corresponding PSFCH occasion on this RB set. This implies the consistent LBT failure does not impact the PSFCH transmissions. In another implementation, whether or not a UE sends PSFCH on an RB set with consistent LBT failure depends on the resource pool configuration or pre-configuration. In another implementation, whether or not a UE sends PSFCH on an RB set with consistent LBT failure is dynamically indicated by SCI associated with the PSSCH transmission.

[0071] FIGS.4A-4B shows respective processes 400, 410 for COT-sharing by a Tx UE or an Rx UE, respectively. For clarity of presentation, the description that follows generally describes the processes 400, 410 in the context of the other figures in this description. For example, the processes 400, 410 can be performed by UE 105-1 or UE 105-2 of FIG.1. The processes 400, 410 can be performed, for example, by any suitable system, environment, software, hardware, or a combination of systems, environments, software, and hardware, as appropriate. In some implementations, various steps of the process 300 can be run in parallel, in combination, in loops, or in any order.

[0072] In FIG. 4A, for process 400, a Tx UE is configured for receiving (402) COT sharing information. The COT sharing information can be received in the DCI 3_0 format. The COT- sharing information includes additional UE identifier(s). The one or more additional identifiers specify additional UEs for sharing the channel in addition to the identifier of the second, receiver UE that receives the transmission from the first, transmitting UE. For example, a third UE can be identified to share resources for channel occupancy time in the COT-sharingAttorney Docket No.50759-0975WO1 / P63461WO1 information. The UE can be preconfigured or configured to support COT-sharing with a third UE which is not the targeted receiver UE of the PSSCH associated with COT-sharing information. Specifically, the UE is configured or pre-configured to support additional identifiers for COT-sharing with a number of UEs. The configuration data or pre-configuration of the UE specifies how many additional devices can share the channel occupancy time. The number of devices is specified by their identifiers or identifier pairs (e.g., 1 or 2 devices) to support for COT-sharing.

[0073] The SL-U can include a modified DCI 3_0 format. In this example, the base station (gNB) allocates the SL resources. For interlace RB-based transmission, the DCI 3_0 replaces “SCI format 1-A field” of the frequency resource assignment by values for a “frequency RIV (FRIV) for RB set index” field and a “FRIV for sub-channel index in an RB set” field. For example, the network can set the “FRIV for RB set index” field value to 0 or 1 to select the RB set. The network can set the “FRIV for sub-channel index in an RB set” value to 1, 2, and / or 3. The FRIV generally indicates the subchannels 1, 2, or 3. The RB set index is added to specify which RB set index is being allocated in the FRIV. DCI 3_0 further includes a field of “lowest index of the RB set allocation to the initial transmission”.

[0074] In some implementations, the DCI 3_0 filed specifies a lowest index of the RB set allocation to the initial transmission – [log2(NRBset)] bits, wherein the resource allocation unit in the frequency domain is the sub-channel. The sub-channel assignment for sidelink transmission is determined using the "frequency resource assignment" field in the associated SCI. The lowest sub-channel for sidelink transmission is the sub-channel on which the lowest PRB of the associated PSCCH is transmitted. If a PSSCH scheduled by a PSCCH would overlap with resources containing the PSCCH, the resources corresponding to a union of the PSCCH that scheduled the PSSCH, and associated PSCCH DM-RS are not available for the PSSCH.

[0075] The Tx UE is configured to transmit (404) to one or more UEs, COT sharing information including identifiers of one or more UEs, a COT duration, and / or a COT offset value. The UEs can receive the COT sharing information and determine if they are indicated in the identifiers included in the COT sharing information. If the UE is identified, the UE can transmit during the COT sharing time period based on the offset and duration of the COT.

[0076] Turning to FIG.4B, a process 410 for an Rx UE is shown. The Rx UE can receive (412) SCI stage 2 signaling that indicates COT sharing configuration information. The Rx UE canAttorney Docket No.50759-0975WO1 / P63461WO1 then transmit (414) to one or more other UEs PSSCH or PSCCH data based on the COT sharing information.

[0077] The UE can support a number of additional devices, specified by additional identifiers in the configuration or pre-configuration of the UE. For example, a control element (CE), or other signaling such as SCI stage 2, can include an “additional identifier number” field that includes 1 bit to indicate how an “additional identifiers” field (e.g., of the CE) represents the identifiers of the additional device(s) that are supported for COT-sharing. In a unicast case, the additional identifiers each include a 16-bit destination identifier and an 8-bit source identifier. In the groupcast (additional broadcast) case, the additional identifiers include the 16-bit destination identifier only. For example, in the groupcast case, the destination identifier is the group identifier that are shared by the UEs of the group. All the UEs in the identified group can share the COT. No source identifier is needed because no matter which UE in the group is selected, the UEs of the group can share the COT.

[0078] The “additional identifiers” field can be 24 bits. In an example, when the “additional identifier number” field value is 0, then the first 16 bits are the destination identifier, and the remaining 8 bits are the source identifier. In another example, when the “additional identifier number” field is 1, then the first 16 bits are the destination identifier, and the remaining 8 bits are reserved.

[0079] In some implementations, each of the “additional identifier number” field and the “additional identifiers” field can be included in the SCI stage 2 signaling. The SCI stage 2 format (e.g., format 2-D) for SL-U can include the following. The format of SCI format 2-D can include the fields of SCI format 2-A, and / or 2-B, in addition to extra fields. The fields of SCI format 2-A are 35 bits and include the following fields: a hybrid automatic repeat request (HARQ) process number; a new data indicator; a redundancy version; a source identifier; a destination identifier; a HARQ feedback enabled / disabled indicator; a CSI request; and a cast type indicator. The fields of the SCI format 2-B can be included in SCI format 2-D. The fields of SCI format 2-B include: a zone identifier (e.g., 12 bits); and a communication range (e.g., 4 bits). The SCI format 2-D can include the fields of the CAPC (e.g., 2 bits); a list of additional identifiers (e.g., 24 bits); and an additional identifier number (e.g., 1 bit), as previously described.

[0080] In some implementations, the additional identifiers for UEs are signaled as follows. The COT sharing flag field in the SCI format 1-A is present and set to 1. The remaining fields areAttorney Docket No.50759-0975WO1 / P63461WO1 set as now described. The CAPC 2-bits including values 00, 01, 10, and 11 correspond to CAPC values 1, 2, 3, and 4 as defined in Table 4.5-1 of [14,TS 37.213]. The COT sharing cast type includes 2 bits are defined in Table 1. The COT sharing additional ID includes 24 bits. The 16 LSBs provide the layer 1 destination ID and the 8 most significant bits (MSBs) provide the layer 1 source ID as defined in [6, TS 38.214]. The 8 MSBs are reserved when the COT sharing cast type field is set to ‘00’ or ‘01’. The remaining COT duration – [log2*(10∙2µ)] bits as defined in clause 4.5.3 of [14,TS 37.213], where µ is defined in Table 4.2-1 of Clause 4.2 of [4,TS 38.211]. Table 1: Cast Type Indicator or COT Sharing Cast Type Value of Cast Type Indicator or COT Sharing Cast Type Cast Type

[0081] In some implementations, the SCI stage 2 format 2-D includes a separate indication specifying the remaining COT duration. For example, the UE can specify that the COT is to be shared, and also the duration of the COT-sharing. The fields include the remaining COT duration (e.g., 5 bits). In some implementations, because the maximum COT duration is 10 milliseconds (ms), which is 20 slots in SCS=30 kHz, the length of the field is 5-bits to indicate up to 20 slots. Other such lengths (greater or fewer than 5 bits) can be used if the maximum COT duration is extended or shortened. The field can also include a COT starting offset value (e.g., 5 bits). Once the UE initiates the COT, it may specify which slots can be used by the other UEs. For example, the UE may be transmitting on the first 3 or 4 slots and specify this as an offset.

[0082] In some implementations, the SCI stage 2 format 2-D includes a joint indication field. In this case, the field includes a COT starting offset value (S) and a remaining COT duration value (L). The values are composed of RIV or TDRA. The resource indication value (RIV) is a value that corresponds to a starting virtual resource block number (RBstart) and a length inAttorney Docket No.50759-0975WO1 / P63461WO1 terms of contiguously allocated VRBs (LRBs). It is also possible of TRIV (time domain RIV). See, for example, section 8.1.5 of TS 38.213. The time domain resource allocations (TDRA) are pre-configured or configured in lookup tables that specify uplink (UL) or downlink (DL) TDRAs for the UE. The For example, the offset value S can be 4 slots, and the remaining COT duration can be 10 (for 10 slots). In an example, if ^ ^^ െ 1^ ^^்ଶ^, then ^^ ^^ ^^ ൌ ^^^ ^^ െ 1^ ^ ^^; else, ^^ ^^ ^^ ൌ ^^^ ^^ െ ^^ ^ 1^ ^ ^ ^^ െ 1 െ ^^^. In this example, T represents a maximum COT duration.

[0083] FIG.5 illustrates an example UE 500, according to some implementations. The UE 500 may be similar to and substantially interchangeable with UEs 105 of FIG.1.

[0084] The UE 500 may be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (for example, microphones, pressure sensors, thermometers, motion sensors, accelerometers, inventory sensors, electric voltage / current meters, etc.), video devices (for example, cameras, video cameras, etc.), wearable devices (for example, a smart watch), relaxed-IoT devices.

[0085] The UE 500 may include processors 502, RF interface circuitry 504, memory / storage 506, user interface 508, sensors 510, driver circuitry 512, power management integrated circuit (PMIC) 514, one or more antenna(s) 516, and battery 518. The components of the UE 500 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram of FIG.5 is intended to show a high-level view of some of the components of the UE 500. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.

[0086] The components of the UE 500 may be coupled with various other components over one or more interconnects 520, which may represent any type of interface, input / output, bus (local, system, or expansion), transmission line, trace, optical connection, etc. that allows various circuit components (on common or different chips or chipsets) to interact with one another.

[0087] The processors 502 may include processor circuitry such as, for example, baseband processor circuitry (BB) 522A, central processor unit circuitry (CPU) 522B, and graphics processor unit circuitry (GPU) 522C. The processors 502 may include any type of circuitry orAttorney Docket No.50759-0975WO1 / P63461WO1 processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage 506 to cause the UE 500 to perform operations as described herein.

[0088] In some implementations, the baseband processor circuitry 522A may access a communication protocol stack 524 in the memory / storage 506 to communicate over a 3GPP compatible network. In general, the baseband processor circuitry 522A may access the communication protocol stack to perform user plane functions at a physical (PHY) layer, medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, service data adaptation protocol (SDAP) layer, and PDU layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a non-access stratum layer. In some implementations, the PHY layer operations may additionally / alternatively be performed by the components of the RF interface circuitry 504. The baseband processor circuitry 522A may generate or process baseband signals or waveforms that carry information in 3GPP-compatible networks. In some implementations, the waveforms for NR may be based cyclic prefix orthogonal frequency division multiplexing (OFDM) “CP-OFDM” in the uplink or downlink, and discrete Fourier transform spread OFDM “DFT-S-OFDM” in the uplink.

[0089] The memory / storage 506 may include one or more non-transitory, computer-readable media that includes instructions (for example, communication protocol stack 524) that may be executed by one or more of the processors 502 to cause the UE 500 to perform various operations described herein. The memory / storage 506 include any type of volatile or non- volatile memory that may be distributed throughout the UE 500. In some implementations, some of the memory / storage 506 may be located on the processors 502 themselves (for example, L1 and L2 cache), while other memory / storage 506 is external to the processors 502 but accessible thereto via a memory interface. The memory / storage 506 may include any suitable volatile or non-volatile memory such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), Flash memory, solid-state memory, or any other type of memory device technology.

[0090] The RF interface circuitry 504 may include transceiver circuitry and radio frequency front module (RFEM) that allows the UE 500 to communicate with other devices over a radio access network. The RF interface circuitry 504 may include various elements arranged inAttorney Docket No.50759-0975WO1 / P63461WO1 transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0091] In the receive path, the RFEM may receive a radiated signal from an air interface via antenna(s) 516 and proceed to filter and amplify (with a low-noise amplifier) the signal. The signal may be provided to a receiver of the transceiver that downconverts the RF signal into a baseband signal that is provided to the baseband processor of the processors 502.

[0092] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier prior to the signal being radiated across the air interface via the antenna(s) 516. In various implementations, the RF interface circuitry 504 may be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0093] The antenna(s) 516 may include one or more antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. The antenna elements may be arranged into one or more antenna panels. The antenna(s) 516 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input, multiple output communications. The antenna(s) 516 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna(s) 516 may have one or more panels designed for specific frequency bands including bands in FR1 or FR2.

[0094] The user interface 508 includes various input / output (I / O) devices designed to enable user interaction with the UE 500. The user interface 508 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (for example, a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number or combinations of audio or visual display, including, inter alia, one or more simple visual outputs / indicators (for example, binary status indicators such as light emitting diodes “LEDs” and multi-character visual outputs), or more complex outputs such as display devices orAttorney Docket No.50759-0975WO1 / P63461WO1 touchscreens (for example, liquid crystal displays “LCDs,” LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 500.

[0095] The sensors 510 may include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other device, module, subsystem, etc. Examples of such sensors include, inter alia, inertia measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; temperature sensors (for example, thermistors); pressure sensors; image capture devices (for example, cameras or lensless apertures); light detection and ranging sensors; proximity sensors (for example, infrared radiation detector and the like); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other like audio capture devices; etc.

[0096] The driver circuitry 512 may include software and hardware elements that operate to control particular devices that are embedded in the UE 500, attached to the UE 500, or otherwise communicatively coupled with the UE 500. The driver circuitry 512 may include individual drivers allowing other components to interact with or control various input / output (I / O) devices that may be present within, or connected to, the UE 500. For example, driver circuitry 512 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of sensors 510 and control and allow access to sensors 510, drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

[0097] The PMIC 514 may manage power provided to various components of the UE 500. In particular, with respect to the processors 502, the PMIC 514 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.

[0098] In some implementations, the PMIC 514 may control, or otherwise be part of, various power saving mechanisms of the UE 500. A battery 518 may power the UE 500, although in some examples the UE 500 may be mounted deployed in a fixed location and may have a power supply coupled to an electrical grid. The battery 518 may be a lithium-ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like.Attorney Docket No.50759-0975WO1 / P63461WO1 In some implementations, such as in vehicle-based applications, the battery 518 may be a typical lead-acid automotive battery.

[0099] FIG.6 illustrates an example access node 600 (e.g., a base station or gNB), according to some implementations. The access node 600 may be similar to and substantially interchangeable with base stations 110. The access node 600 may include processors 602, RF interface circuitry 604, core network (CN) interface circuitry 606, memory / storage circuitry 608, and one or more antenna(s) 610.

[0100] The components of the access node 600 may be coupled with various other components over one or more interconnects 612. The processors 602, RF interface circuitry 604, memory / storage circuitry 608 (including communication protocol stack 614), antenna(s) 610, and interconnects 612 may be similar to like-named elements shown and described with respect to FIG. 5. For example, the processors 602 may include processor circuitry such as, for example, baseband processor circuitry (BB) 616A, central processor unit circuitry (CPU) 616B, and graphics processor unit circuitry (GPU) 616C.

[0101] The CN interface circuitry 606 may provide connectivity to a core network, for example, a 5th Generation Core network (5GC) using a 5GC-compatible network interface protocol such as carrier Ethernet protocols, or some other suitable protocol. Network connectivity may be provided to / from the access node 600 via a fiber optic or wireless backhaul. The CN interface circuitry 606 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 606 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

[0102] As used herein, the terms “access node,” “access point,” or the like may describe equipment that provides the radio baseband functions for data and / or voice connectivity between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth, and can include ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). As used herein, the term “NG RAN node” or the like may refer to an access node 600 that operates in an NR or 5G system (for example, a gNB), and the term “E-UTRAN node” or the like may refer to an access node 600 that operates in an LTE or 4G system (e.g., an eNB). According to various implementations, the access node 600 may be implemented as one or more of a dedicated physical device such as a macrocell base station,Attorney Docket No.50759-0975WO1 / P63461WO1 and / or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0103] In some implementations, all or parts of the access node 600 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In V2X scenarios, the access node 600 may be or act as a “Roadside Unit.” The term “Roadside Unit” or “RSU” may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a “UE-type RSU,” an RSU implemented in or by an eNB may be referred to as an “eNB-type RSU,” an RSU implemented in or by a gNB may be referred to as a “gNB-type RSU,” and the like.

[0104] Various components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) interpretation for that component.

[0105] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

[0106] Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0107] Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the aboveAttorney Docket No.50759-0975WO1 / P63461WO1 disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.

[0108] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Claims

Attorney Docket No.50759-0975WO1 / P63461WO1 WHAT IS CLAIMED IS:

1. One or more processors configured for performing wireless communication by performing operations comprising: identifying, from a medium access control (MAC) layer, data specifying a total number of sub-channels over a resource pool that are candidates for a sidelink transmission; selecting, based on the total number of sub-channels over the resource pool specified in the MAC layer, a candidate single-slot resource that includes a set of contiguous sub- channels in a set of resource blocks; and preparing, for transmission to a user equipment (UE), a sidelink transmission based on the selected candidate single-slot.

2. The one or more processors of claim 1, wherein the number of candidate resource block sets is an integer number that is i) less than a total number of resource blocks of the resource pool and ii) divisible by the total number of sub-channels, and wherein the operations further comprise: selecting the number of candidate resource block sets based on the integer number.

3. The one or more processors of claim 1 or claim 2, wherein the data from the MAC layer further specifies a total number of candidate resource block sets.

4. The one or more processors of claim 3, the operations further comprising: selecting the candidate single-slot resource based on the number of candidate resource block sets, wherein a number of contiguous sub-channels in a set of contiguous RB sets is ^ೞೠ್^ಹ^ೃಳೞ^^െ 1, wherein ^^^௨^^ுis the total number of sub-channels and wherein ^^ோ^^^௧is the total number of candidate resource block sets.

5. The one or more processors of any of claim 1 through claim 4, the operations further comprising: selecting the candidate single-slot resource based on the number of candidate resource block sets, wherein a number of contiguous sub-channels in a set of contiguous RB sets is ^ೞೠ್^ಹ^ೃಳೞ^^െ 1, wherein ^^^௨^^ுis the total number of sub-channels and wherein ^^ோ^^^௧is the total number candidate resource block sets.Attorney Docket No.50759-0975WO1 / P63461WO1 6. The one or more processors of claim 5, wherein the number of candidate resource block sets is based on a channel busy ratio (CBR) of each of the candidate resource block sets.

7. The one or more processors of claim 5, wherein the number of candidate resource block sets is based on a channel occupancy ratio (CR) of each of the candidate resource block sets.

8. The one or more processors of claim 5, the operations further comprising: identifying a resource block set associated with a consistent failure a listen before talk (LBT) operation; and wherein the number of candidate resource block sets exclude the identified resource block set associated with the failed LBT operation.

9. The one or more processors of any of claim 1 through claim 8, the operations further comprising: identifying, from a medium access control (MAC) layer, a resource block set associated with a consistent failure of a listen before talk (LBT) operation; and excluding, from a set of candidate resource blocks for sending the sidelink transmission, the resource block set associated with the consistent failed LBT operation.

10. The one or more processors of claim 9, wherein a total number of candidate single slot resources excludes the resource block set associated with the consistent failed LBT operation.

11. The one or more processors of claim 9, wherein a total number of candidate single slot resources includes the resource block set associated with the consistent failed LBT operation.

12. The one or more processors of claim 9, the operations further comprising: pausing physical sidelink feedback channel (PSFCH) transmissions on the excluded resource block set even when a PSSCH with the corresponding PSFCH occasion on this resource block set is received.Attorney Docket No.50759-0975WO1 / P63461WO1 13. The one or more processors of claim 9, the operations further comprising: causing transmission of a PSFCH on the excluded resource block set after receiving PSSCH with the corresponding PSFCH occasion on the excluded resource block set.

14. The one or more processors of claim 9, the operations further comprising: determining whether to transmit a PSFCH based on the resource pool configuration or pre- configuration.

15. The one or more processors of claim 9, the operations further comprising: determining whether to transmit a PSFCH based on sidelink control information (SCI) associated with the PSSCH transmission.

16. The one or more processors of any of claim 1 through claim 15, wherein the candidate single-slot resource for transmission is defined as ^ ^^௪,௫,௬, ^^௪ା^ି^,௫ା^ି^,௬൧, wherein y represents a slot index, w represents a resource block channelindex, and wherein J represents a number of contiguous sub-channels in a set of ^^^௨^^ு⁄ ^^ contiguous resource block sets.

17. One or more processors configured for performing wireless communication by performing operations comprising: receiving, in downlink control information (DCI), configuration data specifying channel occupancy time (COT) sharing information; and preparing, for transmission to one or more user equipment devices (UEs), the COT sharing information including identifiers of one or more UEs.

18. The one or more processors of claim 17, the COT sharing information including an additional identifiers field that specifies a UE destination identifier.

19. The one or more processors of claim 18, the additional identifiers field further specifying a UE source identifier.

20. The one or more processors of claim 18, the UE destination identifier being a group identifier.Attorney Docket No.50759-0975WO1 / P63461WO1 21. The one or more processors of claim 18, the COT sharing information including an additional identifiers number field that specifies whether the additional identifiers field includes a source identifier.

22. The one or more processors of any of claims 17 through claim 21, the COT sharing information further specifying a COT duration in slots.

23. The one or more processors of any of claims 17 through claim 22, the COT sharing information further specifying a COT offset value in slots.

24. The one or more processors of any of claim 17 through claim 23, wherein the DCI specifies a frequency resource assignment with a first field specifying a frequency assignment for a resource block set index.

25. The one or more processors of claim 24, the DCI further specifying the frequency resource assignment with a second field specifying a frequency assignment for a sub-channel index in the resource block set, as well as the lowest index of the RB set allocation to the initial transmission.

26. One or more processors configured for performing wireless communication by performing operations comprising: receiving, in sidelink control information (SCI), configuration data specifying channel occupancy time (COT) sharing information; and preparing, for transmission to one or more user equipment devices (UEs), PUSCH or PSSCH data based on the COT sharing information.

27. The one or more processors of claim 26, the COT sharing information including an additional identifiers field that specifies a UE destination identifier.

28. The one or more processors of claim 27, the additional identifiers field further specifying a UE source identifier.

29. The one or more processors of claim 27, the UE destination identifier being a group identifier.Attorney Docket No.50759-0975WO1 / P63461WO1 30. The one or more processors of claim 27, the COT sharing information including an additional identifiers number field that specifies whether the additional identifiers field includes a source identifier.

31. The one or more processors of any of claim 26 through claim 30, the COT sharing information further specifying a COT duration in slots.

32. The one or more processors of any of claim 26 through claim 31, the COT sharing information further specifying a COT offset value in slots.

33. The one or more processors of any of claim 26 through claim 32, wherein the SCI includes fields of SCI format 2-A comprising a hybrid automatic repeat request (HARQ) process number; a new data indicator; a redundancy version; a source identifier; a destination identifier; a HARQ feedback enabled / disabled indicator; a CSI request; and a cast type indicator.

34. The one or more processors of any of claim 26 through claim 33, wherein the SCI includes a zone identifier and a communication range value.

35. The one or more processors of any of claim 26 through claim 34, wherein the SCI includes a joint indicator specifying both a COT starting offset and a COT duration.

36. A system for wireless communication comprising one or more processors and one or more storage devices on which are stored instructions that are operable, when executed by the one or more computers, to cause the one or more computers to perform the method of any of claim 1 through claim 35.

37. An apparatus for wireless communication comprising the one or more processors of any of claim 1 through claim 35.

38. A method for wireless communication performed by one or more processors to perform the operations of any of claim 1 through claim 35.

Images