Continuous listen before talk failure (C-LBT-F) aware sidelink positioning reference signal (SL-PRS) resource selection and transmission

Abstract

A method of performing wireless positioning performed by a UE can include determining that one or more sets of resource blocks (RBs) in a shared spectrum are in a continuous listen-before-talk failure (C-LBT-F) state. The UE can also transmit, to a serving entity, an indication of the one or more sets of RBs in the C-LBT-F state. The UE can also receive, from the serving entity, a configuration for transmitting a sidelink positioning reference signal (SL-PRS) in the shared spectrum for a sidelink (SL) positioning procedure, the configuration based at least in part on the indication of the one or more sets of RBs in the C-LBT-F state and indicating at least one wireless resource for transmitting the SL-PRS.

Description

Related applications

[0001] This application claims the benefit of Greek application No. 20240100151, filed on March 1, 2024, entitled “CONSISTENT-LISTEN-BEFORE-TALK-FAILURE (C-LBT-F)-AWARE SIDELINK POSITIONING REFERENCE SIGNAL (SL-PRS) RESOURCE SELECTION AND TRANSMISSION”, which has been assigned to the assignee of this application and is incorporated herein by reference in its entirety. Technical Field

[0002] All aspects of this disclosure relate to wireless communication in general, and specifically to techniques, apparatus and methods associated with the transmission of a multi-channel portion sidelink positioning reference signal (SL-PRS) in a sidelink unlicensed (SL-U) communication. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] These multiple access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be made, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0005] According to this disclosure, an example method for radio positioning performed by a user equipment (UE) may include: determining that one or more resource block (RB) sets in a shared spectrum are in a persistent listen-before-tell-fail (C-LBT-F) state. The method may further include: transmitting from the UE to a serving entity an indication of the one or more RB sets in the C-LBT-F state. Furthermore, the method may include: receiving at the UE, from the serving entity, a configuration for transmitting a sidelink positioning reference signal (SL-PRS) in the shared spectrum for use in a sidelink (SL) positioning procedure, the configuration being at least partially based on the indication of the one or more RB sets in the C-LBT-F state and indicating at least one radio resource for transmitting the SL-PRS.

[0006] According to this disclosure, an example user equipment (UE) may include one or more transceivers, one or more memories, and one or more processors communicatively coupled to the one or more transceivers and the one or more memories. The one or more processors may be configured to: determine that one or more resource block (RB) sets in a shared spectrum are in a state that may include a Listen-After-Speak Failure (C-LBT-F) state. The one or more processors may also be configured to: transmit an indication of the one or more RB sets in the C-LBT-F state to a serving entity via the one or more transceivers. The one or more processors may also be configured to: receive from the serving entity via the one or more transceivers a configuration for transmitting a Side Link Positioning Reference Signal (SL-PRS) in the shared spectrum for use in a side link (SL) positioning procedure, the configuration being at least partially based on the indication of the one or more RB sets in the C-LBT-F state and indicating at least one radio resource for transmitting the SL-PRS.

[0007] According to this disclosure, an example apparatus may include: means for determining that one or more resource block (RB) sets in a shared spectrum are in a state that may include a Talk-After-Listen (C-LBT-F) state. The apparatus may also include: means for transmitting to a serving entity an indication of the one or more RB sets in the C-LBT-F state. Furthermore, the apparatus may include: means for receiving from the serving entity a configuration for transmitting a Sidelink Positioning Reference Signal (SL-PRS) in the shared spectrum for use in a sidelink (SL) positioning process, the configuration being at least partially based on the indication of the one or more RB sets in the C-LBT-F state and indicating at least one radio resource for transmitting the SL-PRS.

[0008] This invention is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used alone to define the scope of the claimed subject matter. This subject matter should be understood with reference to the appropriate portions of this disclosure, any or all of the accompanying drawings, and each claim. The foregoing, as well as other features and examples, will be described in more detail in the following description, claims, and drawings. Attached Figure Description

[0009] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved through this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

[0010] Figure 1 This is a diagram illustrating an example of a wireless network according to the present disclosure.

[0011] Figure 2 This is a diagram illustrating communication between an example network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0012] Figure 3 This is a diagram illustrating an example of sidelink communication according to this disclosure.

[0013] Figure 4 These are illustrations illustrating examples of sidelink communication in different coverage scenarios according to this disclosure.

[0014] Figure 5 This is a diagram illustrating examples of unlicensed and licensed radio frequency bands according to this disclosure.

[0015] Figure 6 This is a diagram illustrating an example of a sidelink slot structure and sustained listen-before-speak (C-LBT-F) determination in sidelink positioning reference signal (SL-PRS) positioning in unlicensed spectrum according to this disclosure.

[0016] Figure 7A This is an example message flow diagram of a process that can be used to determine the SL-PRS configuration in the presence of a set of RBs in the C-LBT-F state, according to this disclosure.

[0017] Figure 8 This is a flowchart illustrating an example procedure performed by a UE according to this disclosure.

[0018] Figure 9 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation

[0019] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0020] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0021] Sidelink communication exists in various scenarios where it can be used to extend or otherwise improve positioning accuracy, including challenging environments such as dense urban areas and / or tunnels, or for certain applications that may require more robust and accurate positioning (e.g., lane-level positioning, proximity-based service detection, and / or vehicle ranging services). For example, in some cases, sidelink positioning can be based on transmitting and receiving a sidelink positioning reference signal (SL-PRS) on a sidelink resource pool. For instance, in access link communication, the positioning reference signal (PRS) is specifically designed to deliver a downlink reference signal with high accuracy, coverage, and interference avoidance and suppression. Specifically, the PRS used in access link communication typically has a large delay spread because the PRS is often received from potentially distant neighboring network nodes for positioning estimation. This large delay spread is achieved by covering a large bandwidth and transmitting the PRS on multiple symbols that can be aggregated to accumulate power. Furthermore, in a given PRS symbol, the subcarrier density (referred to as the comb size) can be configured to cover a variety of subcarriers in the frequency domain, allowing different network nodes to transmit the PRS in different sets of subcarriers to avoid interference and / or reduce latency. Furthermore, PRS signals from one or more network nodes can be silenced at a given time according to a silence mode, thereby further reducing potential interference, and / or multiple repetitions can be used to transmit to improve detection in scenarios with high transmission loss (e.g., in macro cell deployments).

[0022] Therefore, in sidelink communication scenarios, SL-PRS can be used as a supplement or alternative to PRS transmitted via the access link interface to allocate more line-of-sight opportunities for ranging between devices. For example, when two or more user equipment (UEs) are communicating on a sidelink in licensed spectrum, SL-PRS can have bandwidths up to 100 MHz, which is generally sufficient for sidelink deployments that typically have bandwidths significantly less than 100 MHz. However, ranging resolution and / or accuracy, and therefore positioning performance, are typically limited by SL-PRS bandwidths of 100 MHz or less. Therefore, in some cases, sidelink positioning can be supported on shared (e.g., unlicensed) spectrum to allocate large available bandwidth in the shared spectrum for ultra-high bandwidth (or wideband) SL-PRS transmission (e.g., greater than 100 MHz), thereby improving sidelink positioning performance. However, unlicensed sidelink (SL-U) operation (and / or other operations in the shared spectrum) typically lacks support for channel access mechanisms that would support SL-PRS transmission over large bandwidths.

[0023] For example, in a shared or unlicensed frequency band, a transmitting device (e.g., a transmitting UE) must contend for channel access with other devices before transmitting (e.g., transmitting to a receiving UE) on a shared or unlicensed channel to reduce and / or prevent collisions on the shared or unlicensed channel. To contend for channel access, the transmitting device may perform a channel access procedure for shared or unlicensed frequency band channel access, such as a Listen-Before-Speak (LBT) procedure or another type of channel access procedure. The channel access procedure may determine whether a physical channel (e.g., the radio resources of the channel) is free or busy (e.g., being used by another device). The channel access procedure may include sensing or measuring the physical channel during a channel access gap (which may also be referred to as a contention window), and determining whether the shared or unlicensed channel is free or busy based on signals sensed or measured on the physical channel (e.g., based on whether a measurement meets a threshold). If the transmitting device determines that the channel access procedure is successful (e.g., the channel is sensed as idle, free, or otherwise available), the transmitting device may perform one or more transmissions on the shared or unlicensed channel during a transmission opportunity that can be extended up to the COT. Otherwise, if the transmitting device determines that the channel is busy (e.g., the channel access process has failed), the transmitting device is not allowed to transmit and needs to continue sensing until the channel access process succeeds.

[0024] Therefore, as described herein, challenges may arise when a transmitting UE attempts to transmit SL-PRS in SL-U because shared or unlicensed sidelink channels are typically defined as a contiguous set of frequencies spanning approximately 20 MHz, which is much smaller than the bandwidth of a wideband SL-PRS. Specifically, when performing SL-U operations on a band exceeding 20 MHz, the band is typically divided into non-overlapping channels (or resource block (RB) sets, which are sets of RBs spanning a 20 MHz bandwidth of the SL-U channel), and transmissions spanning frequencies across more than one RB set (e.g., SL-PRS transmissions) are considered multichannel or wideband SL-U transmissions. In location service (LCS) sessions potentially involving more than one transmitting (TX) UE configured to use more than one RB set to transmit SL-PRS during positioning, there is currently no standardized way for persistent LBT failures (C-LBT-F) to be handled or reported to the serving entity.

[0025] The embodiments described herein address these and other issues by providing procedures through which the TX UE identifies one or more sets of Restricted Blocks (RBs) in the C-LBT-F state and reports such RB sets to a serving entity that determines the radio resources available for the TX UE to use for transmitting SL-PRS during the positioning process. The serving entity can further perform this determination for other TX UEs, thereby optimizing SL-PRS transmission among the UE group participating in the positioning process when one or more RB sets in the C-LBT-F state are present. Additionally, according to some embodiments, the TX UE can provide LBT information regarding one or more RB sets not in the C-LBT-F state, enabling the serving entity to make intelligent decisions about whether to utilize these one or more RB sets for transmitting SL-PRS. Furthermore, some embodiments enable reselection of resources for SL-PRS if the TX UE determines that the resources initially determined by the serving entity for SL-PRS include one or more RB sets that subsequently enter the C-LBT-F state.

[0026] Specific aspects of the subject matter described herein can be implemented to achieve one or more of the following potential advantages. In some examples, by providing C-LBT-F information from the TX UE to the serving entity, the described techniques can be used to optimize sidelink positioning by avoiding the transmission of SL-PRS on busy channel / RB sets. In some examples, by providing resource reselection after the serving entity provides initial SL-PRS configuration to the TX UE, the implementation allows sidelink positioning to adapt to dynamic changes in the RF environment that may affect the validity and / or quality of sidelink positioning results. These and other advantages will be apparent to those skilled in the art from the embodiments provided herein. The implementation follows a brief overview of the related techniques.

[0027] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0028] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted in or implemented for 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. These technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. Such technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, etc. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0029] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0030] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, frequency bands, carriers, or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating frequency bands. In some aspects, multiple wireless networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NR RATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0031] Various operating frequency bands have been defined as frequency ranges designated FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is different from the Very High Frequency (EHF) band (30 GHz to 300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are often referred to as the mid-band frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into mid-band frequencies. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in mid-band frequencies. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in mid-band frequencies, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0032] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may also be referred to as an NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0033] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0034] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographic locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0035] Network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0036] In some aspects, network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0037] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). A network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0038] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0039] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0040] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and downlink BWP may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0041] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. In some examples, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0042] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0043] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0044] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A group of processors that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire group of processors that are configured or configured to perform the set of functions.

[0045] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0046] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be collectively referred to as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles or drones, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0047] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or lower cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between those of UEs 120 in the first category and those of UEs 120 in the second category). UEs 120 in the third category may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0048] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0049] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0050] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0051] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may perform a multichannel access procedure for one or more sets of RBs in a shared spectrum; and transmit a portion of the SL-PRS on the one or more sets of RBs, at least in part, based on a successful multichannel access procedure associated with one or more sets of RBs occupying a first number of RB sets, the first number of RB sets being less than a second number of RB sets for the wideband SL-PRS, wherein the one or more sets of RBs used to transmit the portion of the SL-PRS are subsets of a plurality of nominal RB sets associated with the wideband SL-PRS. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0052] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0053] Figure 2 This is a diagram illustrating an example network node 110 communicating with example UE 120 in a wireless network.

[0054] like Figure 2 As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0055] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0056] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The processors in the first set and the processors in the second set can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as combined... Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0057] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) according to the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0058] The TX MIMO processor 216 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a set of modems 232. For example, each output symbol stream can be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 can use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for Orthogonal Frequency Division Multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 can further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) together via a corresponding set of antennas 234.

[0059] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0060] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0061] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use to transmit and / or receive communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0062] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0063] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to perform network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0064] UE 120 may include a set of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a set of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0065] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110 and can provide a set of received downlink signals (e.g., R received signals) to a set of modems 254. For example, each received signal can be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use the corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain an input sample. Each modem 254 can use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from the set of modems 254, can perform MIMO detection on the received symbols where applicable, and can provide the detected symbols. The receiver processor 258 can process (e.g., decode) the detected symbols, provide the decoded data for the UE 120 to the data sink 260 (which may include a data pipeline, a data queue, and / or an application running on the UE 120), and provide the decoded control information and system information to the controller / processor 280.

[0066] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0067] Transmitter 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink SRS, and / or another type of reference signal. Symbols from transmitter 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by an assembly of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can provide an assembly of output symbol streams (e.g., U output symbol streams) to the assembly of modems 254. For example, each output symbol stream can be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 can use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0068] Modems 254a to 254u can transmit a set of uplink signals (e.g., R uplink signals or U uplink symbols) via a set of corresponding antennas 252. Uplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals can be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals can carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) typically uses techniques similar to those described for uplink data and control transmission and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0069] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), coplanar antenna element sets, non-coplanar antenna element sets, or with one or more transmitting or receiving components (such as...). Figure 2An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0070] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element, which can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.

[0071] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0072] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0073] In some respects, the controller / processor 280 may be a component of a processing system. A processing system can typically be a system or a series of machines or components that receive input and process it to produce output (which may be passed to other systems or components, such as UE 120). For example, the processing system of UE 120 may be a system that includes various other components or sub-components of UE 120.

[0074] The processing system of UE 120 can interface with one or more other components of UE 120, and can process information (such as input or signals) received from one or more other components, or can output information to one or more other components. For example, the chip or modem of UE 120 may include: a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, allowing UE 120 to receive information or signal input and to pass information to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, allowing UE 120 to transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0075] In some respects, the controller / processor 240 may be a component of a processing system. A processing system can typically be a system or a series of machines or components that receive input and process it to produce output (which may be passed to other systems or components, such as network node 110). For example, the processing system of network node 110 may be a system that includes various other components or sub-components of network node 110.

[0076] The processing system of network node 110 can interface with one or more other components of network node 110, and can process information (such as input or signals) received from one or more other components, or can output information to one or more other components. For example, the chip or modem of network node 110 may include: a processing system, a first interface for receiving or acquiring information, and a second interface for outputting, transmitting, or providing information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, allowing network node 110 to receive information or signal input and to pass information to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, allowing network node 110 to transmit information output from the chip or modem. Those skilled in the art will readily recognize that the second interface may also acquire or receive information or signal input, and the first interface may also output, transmit, or provide information.

[0077] Network node 110, the controller / processor 240 of network node 110, UE 120, the controller / processor 280 of UE 120, or Figure 1 or Figure 2 Any other component may implement one or more technologies associated with the multi-channel portion SL-PRS transmission in the SL-U or perform one or more operations associated with the multi-channel portion SL-PRS transmission in the SL-U, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 280 of UE 120, or... Figure 2 Any other component (or combination of components) may (alone or in combination with one or more other processors) execute or direct, for example... Figure 8 The operation of process 800 or other processes as described herein. Memory 242 may store data and program code of network node 110. Memory 282 may store data and program code of UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing instruction sets (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the instruction set may be executed by one or more processors of network node 110 or UE 120 (e.g., directly, or after compilation, transformation, or interpretation). Figure 8The process 800 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0078] In some aspects, UE 120 includes components for performing a multichannel access procedure for one or more sets of RBs in a shared spectrum; and / or components for transmitting a portion of the SL-PRS on the one or more sets of RBs, at least in part based on a successful multichannel access procedure associated with one or more sets of RBs occupying a first number of RB sets, the first number of RB sets being less than a second number of RB sets for the wideband SL-PRS, wherein the one or more RB sets for transmitting the portion of the SL-PRS are a subset of a plurality of nominal RB sets associated with the wideband SL-PRS. Components for UE 120 to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0079] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0080] Figure 3 This is a diagram illustrating example 300 of sidelink communication according to this disclosure.

[0081] like Figure 3As shown, the first UE 305-1 can communicate with the second UE 305-2 (and one or more other UEs 305) via one or more sidelink channels 310. UEs 305-1 and 305-2 can communicate using one or more sidelink channels 310 for P2P communication, D2D communication, V2X communication (e.g., which may include V2V communication, V2I communication, and / or V2P communication), and / or mesh networking. In some aspects, UEs 305 (e.g., UEs 305-1 and / or UEs 305-2) may correspond to one or more other UEs described elsewhere herein, such as UE 120. In some aspects, one or more sidelink channels 310 may use a PC5 interface and / or may operate in a high-frequency band (e.g., the 5.9 GHz band). Additionally or alternatively, UEs 305 may use Global Navigation Satellite System (GNSS) timing to synchronize the timing of transmission time intervals (TTIs) (e.g., frames, subframes, time slots, or symbols).

[0082] like Figure 3 As further shown, one or more sidelink channels 310 may include PSCCH 315, PSSCH 320, and / or PSFCH 325. PSCCH 315 can be used to convey control information, similar to PDCCH and / or PUCCH used for cellular communication with network node 110 via an access link or access channel. PSSCH 320 can be used to convey data, similar to PDSCH and / or PUSCH used for cellular communication with network node 110 via an access link or access channel. For example, PSCCH 315 may carry sidelink control information (SCI) 330, which may indicate various control information for sidelink communication, such as one or more resources (e.g., time resources, frequency resources, and / or spatial resources), wherein TB 335 may be carried on PSSCH 320. TB 335 may include data. PSFCH 325 can be used to communicate sidelink feedback 340, such as HARQ feedback (e.g., acknowledgment or negative acknowledgment (ACK / NACK) information), transmit power control (TPC), and / or scheduling request (SR).

[0083] Although shown on PSCCH 315, SCI 330 may include multiple communications at different levels, such as Level 1 SCI (SCI-1) and Level 2 SCI (SCI-2) in some respects. SCI-1 may be transmitted on PSCCH 315. SCI-2 may be transmitted on PSSCH 320. SCI-1 may include, for example, indications of one or more resources (e.g., time resources, frequency resources, and / or space resources) reserved for future transmissions using PSSCH 320, information for decoding sidelink communications on PSSCH, Quality of Service (QoS) priority values, resource reservation periods, PSSCH DMRS modes, SCI format for SCI-2, β offset for SCI-2, number of PSSCH DMRS ports, and / or MCS. SCI-2 may include information associated with data transmissions on PSSCH 320, such as HARQ process ID, New Data Indicator (NDI), source identifier, destination identifier, and / or CSI report triggering.

[0084] In some respects, one or more sidelink channels 310 may use a resource pool. For example, PSCCH 315 (e.g., utilizing resource reservations included in SCI 330) may be transmitted together with PSSCH 320 (e.g., utilizing data transmission) in selected resources (e.g., time slots in time and multiple sub-channels in frequency).

[0085] In some aspects, UE 305 may operate using a first resource allocation mode (e.g., mode 1, which may be referred to herein as a centralized scheduling mode or network control scheduling mode), in which resource selection and / or scheduling is performed by network node 110. For example, in centralized scheduling mode or network control scheduling mode, UE 305 may receive permission from network node 110 for sidelink channel access and / or scheduling (e.g., in downlink control information (DCI) indicating resources with sidelink dynamic permission or activating resources with sidelink configuration permission type 2, or in RRC messages configuring resources with sidelink configuration permission type 1). In some aspects, UE 305 may operate using a second resource allocation mode (e.g., mode 2, which may be referred to herein as a distributed scheduling mode or autonomous scheduling mode), in which resource selection and / or scheduling is performed by UE 305 (e.g., instead of network node 110). In some respects, UE 305 can perform resource selection and / or scheduling in a distributed or autonomous scheduling mode by sensing the availability of resources for transmission. For example, UE 305 can decode SCIs associated with various sidelink communications and exclude resources reserved in the SCIs, or it can measure SL RSSI parameters (e.g., sidelink-RSSI (S-RSSI) parameters), SL RSRP parameters (e.g., sidelink PSCCH-RSRP or sidelink PSSCH-RSRP parameters), and / or SL RSRQ parameters (e.g., sidelink PSCCH-RSRQ or sidelink PSSCH-RSRQ parameters) associated with various resources (e.g., used with various sidelink communications), and exclude resources based on the associated measurements (e.g., SL RSSI measurements are above a threshold), and can select resources for transmission of sidelink communications at least in part based on the measurements (e.g., after excluding resources).

[0086] Alternatively or additionally, UE 305 may use SCI 330 received in PSCCH 315 to perform resource selection and / or scheduling in distributed or autonomous scheduling mode, which may indicate reserved resources and / or channel parameters. Alternatively or additionally, UE 305 may perform resource selection and / or scheduling by determining the Channel Busy Rate (CBR) associated with various sidelink resources, which may be used for rate control (e.g., by indicating the maximum number of resource blocks that UE 305 may use for a particular subframe set).

[0087] In a distributed or autonomous scheduling mode where resource selection and / or scheduling is performed by UE 305, UE 305 may generate sidelink grants and may transmit these grants in SCI 330. Sidelink grants may indicate one or more parameters (e.g., transmission parameters) to be used for an upcoming sidelink transmission, such as one or more resource blocks (e.g., for TB 335) to be used for an upcoming sidelink transmission on PSSCH 320, one or more time slots to be used for an upcoming sidelink transmission, and / or the MCS to be used for an upcoming sidelink transmission. In some aspects, UE 305 may generate sidelink grants indicating one or more parameters of SPS (such as the periodicity of sidelink transmission). Additionally or alternatively, UE 305 may generate sidelink grants for event-driven scheduling (such as for on-demand sidelink messages).

[0088] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0089] Figure 4 These are illustrations illustrating examples of sidelink communication in different coverage scenarios 400, 410, and 420 according to this disclosure. For example, Figure 4 Examples of sidelink communication in in-coverage scenario 400, examples of sidelink communication in partial-coverage scenario 410, and examples of sidelink communication in out-of-coverage scenario 420 are illustrated.

[0090] like Figure 4 As shown, in the covered scenario 400, Tx / Rx UE 402 and Rx / Tx UE 404 can communicate with each other via a side link (e.g., PC5 interface), as described above. Figure 3 As described, network node 110 can communicate with Tx / Rx UE 402 via a first access link and with Rx / Tx UE 404 via a second access link (e.g., a corresponding Uu interface). As shown, in the coverage scenario 400, both Tx / Rx UE 402 and Rx / Tx UE 404 are within the coverage of network node 110, so sidelink communication between Tx / Rx UE 402 and Rx / Tx UE 404 can be performed in a centralized or network-controlled scheduling mode (e.g., mode 1) where network node 110 schedules sidelink resources, or in a distributed or autonomous scheduling mode (e.g., mode 2) where UE 402 / 404 autonomously selects sidelink resources from a configured sidelink resource pool based on a resource-sensing mechanism.

[0091] like Figure 4As further illustrated, in the in-coverage scenario 410, Tx / Rx UE 402 is within the coverage area of ​​network node 110, while Rx / Tx UE 404 is outside the coverage area of ​​network node 110. In the in-coverage scenario 410, Tx / Rx UE 402 and Rx / Tx UE 404 can communicate with each other via a side link (e.g., a PC5 interface), and network node 110 can communicate with Tx / Rx UE 402 via an access link (e.g., a Uu interface). Therefore, in the in-coverage scenario 410, network node 110 can enable either a centralized scheduling mode or a distributed scheduling mode for Tx / Rx UE 402 within its coverage area, and Rx / Tx UE 404 outside its coverage area can use only the distributed scheduling mode. Furthermore, in the out-of-coverage scenario 420, Tx / Rx UE 402 and Rx / Tx UE 404 are outside the coverage area of ​​any network node. Therefore, in the off-coverage scenario 420, only the distributed scheduling mode can be used to realize the sidelink communication between Tx / Rx UE 402 and Rx / Tx UE 404.

[0092] As described herein, when a UE performs sidelink transmission, the sidelink transmission can be performed according to one or more sidelink procedures and / or using one or more transmission parameters configured to simplify the channel access scheme followed by the UE in a centralized or network-controlled scheduling mode or in a distributed or autonomous scheduling mode. Generally, all communication parameters (e.g., transmission parameters such as transmit power and / or DMRS mode, and procedure parameters indicating whether certain sidelink features and / or procedures are enabled or disabled) are centrally selected by the network in a centralized scheduling mode (e.g., Mode 1) or otherwise controlled. For example, in a centralized scheduling mode, the network node is aware of congestion, traffic conditions, interference, load, and / or other factors that may affect the performance of the network node and the UEs within its coverage area, and the network node accordingly configures the sidelink communication parameters to optimize overall sidelink and / or cellular performance and / or per-UE performance.

[0093] On the other hand, in distributed scheduling mode, the Tx UE independently or autonomously selects various sidelink communication parameters. For example, in distributed scheduling mode, sidelink communication parameters may include pre-configured or configured parameters with fixed values ​​(e.g., the number of sub-channels, sub-channel bandwidth, and / or timeslot duration, etc.) and locally configured parameters selected by the Tx UE. For example, locally configured parameters may include MCS, DMRS mode, transmit power, maximum retransmission count for a given TB, multicast option 1 NACK distance (e.g., the distance at which the receiving UE can transmit NACKs for sidelink transmissions), and / or β parameters (e.g., related to decoding associated with the transmitted waveform), etc. In some cases, the Tx UE may independently select locally configured parameters, possibly limited to a set of allowed or permitted values, where the locally configured parameters have values ​​selected by the UE to optimize UE performance relative to one or more metrics typically dependent on the application. For example, the Tx UE may select the maximum number of MCS and HARQ retransmissions to maximize packet reliability, maximize throughput, and / or minimize latency, etc. In addition, the transmitting UE may select locally configured parameters based on pre-configured schemes (e.g., using application-dependent defaults, such as defaults in Basic Security Messages (BSM)) and / or using more sophisticated techniques based on real-time (e.g., current or instantaneous) measurements (such as CBR or perceived congestion on sidelink channels).

[0094] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.

[0095] Figure 5 This is an illustration of example 500 of unlicensed and licensed radio frequency bands according to this disclosure.

[0096] To accommodate increasing service demands, various efforts have been made to improve spectrum efficiency in wireless networks, thereby increasing network capacity (e.g., through the use of higher-order modulation, advanced MIMO antenna technology, and / or multi-cell coordination techniques). Another potential way to increase network capacity is to expand system bandwidth. However, as shown by licensed RF band 550, available spectrum in lower frequency bands that has traditionally been licensed or otherwise allocated to mobile network operators has become very scarce. Therefore, various technologies have been developed to enable cellular RATs to operate in unlicensed spectrum or other shared spectrum. For example, Licensed Assisted Access (LAA) uses downlink carrier aggregation to combine LTE in licensed bands with LTE in unlicensed bands (e.g., the 2.4 GHz and / or 5 GHz bands already occupied by wireless LAN (WLAN) or “Wi-Fi” devices). In other examples, enhanced LAA (eLAA) and further enhanced LAA (feLAA) technologies implement both uplink and downlink LTE operations in unlicensed spectrum; MulteFire is an LTE-based technology that operates in independent mode in both unlicensed and shared spectrum; NR Unlicensed (NR-U) implements NR operations in unlicensed spectrum; and SL-U implements sidelink communication in unlicensed spectrum. In some examples, UE 120 may have a set of UE capabilities for communication in unlicensed spectrum that differs from the set of UE capabilities UE 120 uses for communication in licensed spectrum.

[0097] For example, as in Figure 5 As shown by reference numeral 505, an unlicensed RF band (such as a 6 GHz unlicensed RF band) may span a frequency range and may utilize FDD. In an FDD system, a first band (e.g., a first sub-band of an unlicensed RF band) may be used for downlink communication (as shown by reference numeral 510), and a second band (e.g., a second sub-band of an unlicensed RF band) may be used for uplink communication (as shown by reference numeral 515). Downlink communication may refer to communication from a control node to (e.g., communication controlled, configured, and / or scheduled by the control node) nodes, such as communication from a network node to a UE, and / or communication from a WLAN access point to a WLAN station. Uplink communication may refer to communication from a node to a control node, such as communication from a UE to a network node, and / or communication from a WLAN station to a WLAN access point.

[0098] For example, further Figure 5As shown by reference numeral 520, the downlink bandwidth can be divided into multiple downlink channels (sometimes called downlink frequency channels). Similarly, as shown by reference numeral 525, the uplink bandwidth can be divided into multiple uplink channels (sometimes called uplink frequency channels). As shown by reference numeral 530, each downlink channel may correspond to a single uplink channel. This can be referred to as channel pairing, where a downlink channel is paired with an uplink channel. In this configuration, control nodes and nodes can use a specific downlink channel for downlink communication and can use a specific uplink channel paired with or corresponding to that specific downlink channel for uplink communication. In Example 500, downlink channel 1 is paired with uplink channel 1, downlink channel 2 is paired with uplink channel 2, downlink channel 3 is paired with uplink channel 3, and so on.

[0099] Although Figure 5 Example 500 illustrates an unlicensed RF band utilizing FDD, but in some cases, unlicensed communication channels may utilize TDD. For example, in an unlicensed communication channel utilizing TDD, uplink and downlink transmissions can be time-separated and performed on the same frequency channel. However, unlike TDD in licensed spectrum, subframes, time slots, and / or symbols are not limited to being configured for uplink or downlink communication and can be configured for downlink transmissions by network nodes or uplink transmissions by UEs. Furthermore, unlicensed communication may support dynamic TDD, where uplink-downlink allocation can change over time to adapt to traffic conditions. For example, to implement dynamic TDD, a radio device (e.g., a network node, UE, or another device) can determine when to transmit and in which resource to transmit based on an indication of the channel occupancy time structure. Generally, channel occupancy time may include multiple transmission intervals (e.g., multiple time slots), and each transmission interval may include one or more downlink resources, and / or one or more uplink resources, one or more flexible resources, etc. In this way, the channel occupancy time structure reduces power consumption and / or channel access delay, etc.

[0100] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.

[0101] Figure 6 This is an illustration of Example 600, which illustrates the side-link time slot structure and persistent listen-before-speak (C-LBT-F) determination in SL-PRS positioning in unlicensed spectrum according to this disclosure.

[0102] More specifically, as described herein, there are various scenarios where sidelink communication can be used to extend or otherwise improve positioning accuracy, including challenging environments such as dense urban areas and / or tunnels, or for certain applications that may require more robust and accurate positioning (e.g., lane-level positioning, proximity-based service detection, and / or vehicle ranging services). For example, in some cases, sidelink positioning can be based on sending and receiving SL-PRS on a sidelink resource pool. For example, in addition to PSCCH, PSSCH, and PSFCH transmissions, SL-PRS can also be sent in a shared resource pool that supports SL-PRS transmission, or in a dedicated resource pool that only supports SL-PRS transmission and associated PSCCH transmission. For example, Figure 6 Figure 610 in the figure depicts an example of a sidelink slot structure that supports SL-PRS transmission in a shared resource pool, wherein SL-PRS is transmitted together with PSCCH and PSSCH.

[0103] Therefore, in sidelink communication scenarios, SL-PRS can be used to supplement or replace PRS transmitted via the access link interface, allowing more line-of-sight opportunities to be used for ranging between devices. For example, when two or more UEs communicate on a sidelink in licensed spectrum, SL-PRS can have bandwidths up to 100MHz, which is generally sufficient for sidelink deployments that typically have significantly less than 100MHz of bandwidth. However, ranging resolution and / or accuracy, and therefore positioning performance, are usually limited by SL-PRS bandwidth of 100MHz or less. Therefore, in some cases, sidelink positioning can be supported in unlicensed spectrum to utilize the large available bandwidth in the unlicensed spectrum for ultra-high bandwidth (or wideband) SL-PRS transmission (e.g., greater than 100MHz), thereby improving sidelink positioning performance. However, SL-U operation typically lacks support for channel access mechanisms that would support SL-PRS transmission over large bandwidths.

[0104] For example, in a shared or unlicensed frequency band, a transmitting device (e.g., a transmitting UE) must contend for channel access with other devices before transmitting (e.g., transmitting to a receiving UE) on a shared or unlicensed channel to reduce and / or prevent collisions on the shared or unlicensed channel. To contend for channel access, the transmitting device may perform a channel access procedure for shared or unlicensed frequency band channel access, such as a Listen-Before-Speak (LBT) procedure or another type of channel access procedure. The channel access procedure may determine whether a physical channel (e.g., the radio resources of the channel) is free to use or busy (e.g., being used by another device). The channel access procedure may include sensing or measuring the physical channel during a channel access gap (which may also be referred to as a contention window) of a sustained pre-configured duration, and determining whether the shared or unlicensed channel is free or busy based on the signals sensed or measured on the physical channel (e.g., based on whether the measurement meets a threshold). If the transmitting device determines that the channel access procedure is successful, the transmitting device may perform one or more transmissions on the shared or unlicensed channel during a transmission opportunity that may extend the Channel Occupancy Time (COT). Otherwise, if the transmitting device determines that the channel is busy (e.g., the channel access process has failed), the transmitting device is not allowed to transmit and needs to continue sensing until the channel access process succeeds.

[0105] Therefore, challenges can arise when a transmitting UE attempts to transmit SL-PRS in SL-U because channel access procedures (e.g., LBT procedures) need to be performed in unlicensed spectrum. This is because unlicensed sidelink channels are typically defined as a contiguous set of frequencies spanning approximately 20 MHz, which is much smaller than the bandwidth of a wideband SL-PRS. Specifically, when performing SL-U operations in a band exceeding 20 MHz, the band is typically divided into non-overlapping channels (or resource block (RB) sets, which are sets of RBs spanning a 20 MHz bandwidth of the SL-U channel), and transmissions spanning frequencies across more than one RB set (e.g., SL-PRS transmissions) are considered multichannel or wideband SL-U transmissions. If the transmitting UE uses the LBT procedure to determine that there is activity on an RB set (e.g., the energy in the RB set is above a threshold), that RB set can be considered in an LBT failure (LBT-F) or “channel busy” state, and transmissions on that RB set may not be permitted. This means that continuous full-bandwidth transmission is not always possible in unlicensed (shared) spectrum operations, as one or more sets of RBs in the resource pool may experience LBT failure (channel busy) during transmission.

[0106] There are two types of LBT-F states that an RB set can experience. The first is an occasional or sporadic LBT-F state that occurs when LBT-F occurs relatively infrequently. The second is a persistent LBT-F (C-LBT-F) state that occurs when LBT-F occurs relatively frequently (typically when the RB set is severely congested). When an RB set is in a C-LBT-F state, the sensing node (e.g., the UE) typically won't even attempt to transmit on that RB set because it knows the probability of LBT failure is high.

[0107] Figure 6 Figure 620 illustrates an example timeline of how the C-LBT-F state can be triggered and canceled. In this illustration, the UE (e.g., an anchor UE for sidelink positioning) determines that the RB set experiences LBT-F at various times 630-1, 630-2, 630-3, and 630-4. Each of these times triggers a corresponding reset of the following failure detection timers: 635-1, 635-2, 635-3, and 635-4. Generally, if the LBT-F determination occurs before the failure detection timer expires, the LBT counter value is incremented and the failure detection timer is reset. (Note that, for illustrative purposes, arrows 635-1, 635-2, 635-3, 635-4, and 635-5 show the full length of the failure detection timer. However, as described herein, only a single failure detection timer can be used and reset.) If the LBT counter value reaches a threshold number before the failure detection timer expires, the C-LBT-F state can be triggered, which triggers the reset of the failure detection timer (as shown by arrow 635-5). The RB set can remain in the C-LBT-F state until the C-LBT-F timer 635-5 (the failure detection timer during the C-LBT-F state) expires. Figure 6In this process, the transmitting UE determines LBT-F at times 630-1, 630-2, 630-3, 630-4, and 640. After the initial failure detection timer 635-1 is set due to the initial LBT-F determination at time 630-1, each subsequent LBT-F determination occurs during the failure detection timer's runtime, thus incrementing the LBT counter value. At the final time 640, the LBT counter value reaches a threshold (five in this example), at which point the UE marks the RB set as being in the C-LBT-F state. The RB set remains in this state during the C-LBT-F timer (failure detection timer 635-5). If no other LBT-F determination occurs during the C-LBT-F timer, the C-LBT-F mark is removed at time 650 once the C-LBT-F timer expires. At this point, the RB set can be considered for RF transmission (including SL-PRS for sidelink positioning), and an LBT check is performed to help ensure the RB set is available for RF transmission.

[0108] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0109] The fact that one or more RB sets intended for SL-PRS transmission in sidelink positioning may be in a C-LBT-F state may require a different solution than solutions available for RB sets experiencing occasional or sporadic LBT-F. This is because RB sets experiencing C-LBT-F may remain unavailable for a period of time in the future, at least in principle, at least until the timer (e.g., 635-5) expires (due to significant media congestion). Therefore, it may not make sense to consider RB sets in a C-LBT-F state as part of future SL-PRS TX resources for sidelink positioning.

[0110] The implementation described below can be implemented when it is recognized that coordination between SL-PRS TX and RX UEs may be needed to determine the appropriate SL-PRS frequency allocation for sidelink positioning in the presence of a set of RBs experiencing C-LBT-F. Therefore, according to some implementations, the set of RBs in C-LBT-F state can be identified (e.g., to the serving entity, such as the serving UE, the base station (gNB), or the location server coordinating transmission (e.g., LMF, if connected to the cellular network)) to enable the determination of SL-PRS resources available for SL-PRS transmission, or even if, for example, the set of available RBs is deemed insufficient to support the positioning requirements for sidelink positioning, SL-PRS transmission can be completely cancelled.

[0111] Figure 7AThis is a message flow diagram of process 700, based on some implementation schemes, which can be used to determine the SL-PRS configuration in the presence of a set of RBs in the C-LBT-F state. (This is in conjunction with other appendices in this document.) Figure 1 Sample, Figure 7A This is only illustrated as a non-limiting example. Alternative implementations can add, remove, combine, and / or rearrange operations as needed for various applications. Procedure 700 can be performed as part of a location session that includes a TX UE and is coordinated by a serving entity (e.g., the serving UE), and the operations and / or communications illustrated in procedure 700 can be combined and / or integrated into other operations and / or communications related to the location session. As described in more detail below, dashed lines indicate optional functionality. Here, for simplicity, the serving entity (e.g., UE, base station (gNB), or location server (if connected to a cellular network)) that coordinates the sidelink location procedure using SL-PRS is illustrated as communicating with a single TX UE. However, it should be noted that the serving entity can communicate with multiple UEs, which may include one or more additional TX UEs and / or RX UEs participating in the location procedure. It can be further noted that procedure 700 may be particularly suitable for situations where no network coverage is available. That is, procedure 700 is not necessarily limited to such situations.

[0112] Process 700 may begin with the operation illustrated at box 705, where the TX UE determines the C-LBT-F status of one or more RB sets. This may be accomplished, for example, using LBT procedures that may be defined in applicable standards (e.g., SL-U). This determination may be based on previous transmission attempts and / or performing sensing of RB sets for potential LBT transmissions. According to some implementations, this sensing may be in response to the serving entity ( Figure 7A (Not shown in the image) Execute a sensing request, or a similar triggering event.

[0113] As illustrated by arrow 710, the TX UE can then provide C-LBT-F information to the serving entity. This can be used, for example, as auxiliary data (e.g., in...). provideAssistanceData The C-LBT-F information may be provided in the SLPP message. It may include a list of one or more RB sets in the C-LBT-F state. Optionally, according to some implementations, the C-LBT-F information may include the remaining time before the C-LBT-F state expires, which can help the service entity determine whether the C-LBT-F state is likely to persist during the positioning process (including the transmission of SL PRS).

[0114] Optionally, the additional LBT information may accompany the C-LBT-F information. This LBT information may include information about other RB sets not in the C-LBT-F state, which helps the serving entity determine whether any of these RB sets is likely to enter the C-LBT-F state during a potential SL-PRS transmission. The LBT information may include an identifier for each RB set not in the C-LBT-F state monitored by the TX UE. According to some implementations, for each of these RB sets, the LBT information may also include the current corresponding LBT counter value and the corresponding failure detection timer. (In some implementations, the failure detection timer may not be part of a cell-specific configuration and therefore may not be known to the serving entity.) The length of the failure detection timer may indicate the TX UE's "sensitivity" to the determination of C-LBT-F RB sets and may provide the serving entity with some insight into the likelihood that one of the RB sets in the used RB sets might enter the C-LBT-F state during the positioning process.

[0115] Additionally or alternatively, the LBT information for each RB set not in C-LBT-F state monitored by the TX UE may include a binary value indicating the likelihood that the RB set will experience C-LBT-F in the "near future". The value of this indicator may be based on a pre-configured rule (e.g., mapping the current LBT counter value and the C-LBT-F timer) or depend on the specific UE implementation. Here, "near future" may correspond to a time interval that begins at the time the LBT information is provided and ends after a predetermined time interval. The duration of this time interval may be (pre)configured, indicated by higher-layer signaling (e.g., SLPP), or depend on the specific UE implementation.

[0116] At box 715, the serving entity may then determine the SL-PRS configuration for the TX UE based at least in part on the C-LBT-F information provided at arrow 710. This determination at box 715 may be made after the serving entity receives additional C-LBT-F information (and other information related to the location process), thereby enabling the serving entity to coordinate the SL-PRS configuration across multiple TX UEs participating in the location process. Based on this information, the serving entity may then allocate resources for the SL-PRS to be transmitted by the TX UE, and include the allocation of these resources in the SL-PRS configuration provided to the TX UE, as indicated by arrow 720. In some instances (e.g., when the C-LBT-F information indicates that there is not enough RB set available for the location process), the serving entity may exclude the TX UE from the location process. If the TX UE is not excluded from the location process, the TX UE may then continue to transmit SL PRS for the location process, as indicated by box 725.

[0117] As illustrated, the TX UE may optionally perform additional functionality. That is, according to some embodiments, the TX UE may determine the C-LBT-F state of one or more RB sets of the SL-PRS configuration, as indicated at box 730. In other words, according to some embodiments, one or more RB sets of one or more resources may enter the C-LBT-F state after the TX UE has been allocated / assigned for one or more resources for its SL-PRS transmission, and before that transmission. This may be more likely to occur, for example, where there is a relatively long time interval between determining the SL PRS configuration at box 715 and transmitting the SL PRS at box 725. Additionally or alternatively, the SL-PRS configuration may cause the TX UE to perform multiple transmissions, in which case the TX UE may perform the determination at box 730 after one or more transmissions in progress but before at least another transmission in progress.

[0118] According to some implementation schemes, determining that one or more sets of RBs of one or more resources enter the C-LBT-F state can trigger actions such as SL-PRS resource reselection, examples of which are provided by Figure 7A Operations 732, 734, and 736 are illustrated. At arrow 732, the TX UE provides a C-LBT-F report to the serving entity, whereby the TX UE indicates that one or more RB sets of one or more resources that will be used to send SL-PRS are experiencing C-LBT-F. This indication may include, for example, the number of RB sets experiencing C-LBT-F and / or the identifier of each RB set among those experiencing C-LBT-F. According to some implementations, a single C-LBT-F report may contain information about the C-LBT-F status of more than one future SL-PRS TX resource. Additionally or alternatively, C-LBT-F reporting by the TX UE may be enabled / disabled, and this enable / disable of C-LBT-F reporting may be included in the SL-PRS configuration and / or another message transmitted by the serving entity to the TX UE. This enable / disable may be communicated, for example, using a higher layer (e.g., SLPP).

[0119] It can be noted that including the RB set in the C-LBT-F report at arrow 732 depends on determining whether the C-LBT-F status of the RB set meets certain factors. This can potentially help avoid declaring the RB set as being in the C-LBT-F state for the purpose of C-LBT-F reporting (at arrow 732) if there is a possibility that the C-LBT-F state may be canceled before one or more SL-PRS resources begin. Factors used to determine whether to include the RB set in the C-LBT-F report at arrow 732 may include, for example, that the C-LBT-F state has been triggered for the RB set, and that its failure detection timer will terminate after the start time of one or more resources used to send SL PRS. (Described below) Figure 7B Additional details regarding the timing involved in these considerations are illustrated in the text.

[0120] Figure 7B It is used to determine whether to include the RB set in the C-LBT-F report (e.g., as...). Figure 7A An example timeline of events (indicated by arrow 732 in the image). Here, the events shown on the timeline include the reception of the SL PRS configuration at time 750 (e.g., with the TX UE at...). Figure 7A Arrow 720 in the image corresponds to the reception of the SL-PRS configuration, and time 755 is used to transmit the SL PRS (e.g., with...). Figure 7A The start time of one or more resources (possibly) sent by the SL-PRS at box 725.

[0121] According to the implementation plan, a time preceding the start time of one or more resources used to send SL PRS can be established as the final time. Before this final time, the TX UE can provide a C-LBT-F report to the serving entity (e.g., Figure 7A Arrow 732). Figure 7B In this context, time 760 is defined as a length of time T preceding the start time of one or more resources at time 755. The length of time T is... Figure 7B The middle is shown as arrow 765. As indicated above, if as Figure 7BAs shown, if the TX UE identifies the RB set as being in C-LBT-F state at time 770, before time 760 (time T prior to the start time established for transmitting one or more resources of SL PRS), the TX UE may include that RB set in the C-LBT-F report at arrow 732. As an additional factor, according to some implementations, the TX UE may not indicate such an RB set as being in C-LBT-F state unless the RB set further has a C-LBT-F timer expiring at time 780 after the start time for transmitting one or more resources of SL PRS (arrow 775).

[0122] Depending on the desired functionality, the length of time T can be determined and / or communicated in any of a variety of ways. For example, according to some implementations, time T is (pre-)configured according to the Bandwidth Partial (BWP) or Resource Pool (RP), determined by a higher layer (e.g., SLPP) based on the desired UE-specific implementation, equal to the LBT (Lack-Based Bit-of-Beat) failure detection timer, or any combination thereof. According to some implementations, time T may potentially depend on the subcarrier spacing (SCS) used by the sidelink equipment, similar to other sidelink timers. According to some implementations, the TX UE may (or may not) be allowed to assess resources before T (and potentially report C-LBT-F, such as...). Figure 7A (As shown by arrow 732). According to some implementations, enabling / disabling this functionality may be based on configuration received by the TX UE (e.g., by the serving entity).

[0123] It can be noted that even when implementing resource reselection operations (e.g., by...) Figure 7AEven when performing operations as shown in items 730, 732, 734, and 736, the TX UE may still eventually find itself transmitting on a nominal SL-PRS resource for which one or more RB sets are undergoing C-LBT-F and are therefore unlikely to be available. According to some implementations, such a situation, where the TX UE is about to transmit SL-PRS on a resource where one or more of its RB sets are in a C-LBT-F state, can be resolved by the TX UE by: (i) transmitting (or attempting to transmit) a portion of the SL-PRS signal on the remaining available RB sets that are not in a C-LBT-F state (e.g., by utilizing type A or type B LBT as defined in SL-U), or (ii) completely avoiding transmitting SL-PRS TX (e.g., not attempting to transmit SL-PRS even on RB sets that are not in a C-LBT-F state). In the latter case, the TX UE may notify one or more other devices (e.g., the serving entity) in a subsequent transmission to avoid transmitting SL-PRS. According to some implementation schemes, this subsequent transmission may be included as part of a sidelink positioning session. ProvideAssistanceData or ProvideLocationInformaton In the SLPP message, the determination of whether (i) to send a partial SL-PRS signal or (ii) to avoid sending an SL-PRS can be based on an assessment of conditions related to the number / type of available RB sets (and their comparison with the nominal number / type of RB sets), the priority of the SL-PRS TX, and / or other such conditions.

[0124] As indicated above, Figure 7A and Figure 7B This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7A and Figure 7B The examples described are different.

[0125] Figure 8 This is a flowchart of an example method 800 for wireless positioning performed by a UE according to an implementation plan. (It is available in...) Figure 9 Example components / structures (hardware and / or software components of the UE) that may be able to perform the operation of method 800 are found, which will be described in more detail below. Here, the UE may correspond to the TX UE as described in the above embodiments. Furthermore, method 800 may be described as previously discussed regarding... Figure 7A Some aspects of the TX UE functionality described herein. Some or all of the functionality illustrated in method 800 may be performed when the UE is not within the coverage of the wireless cellular network. As previously noted, the serving entity may include another UE or a base station (e.g., a gNB).

[0126] At box 810, this functionality includes determining that one or more sets of RBs in the shared spectrum are in a persistent listen-before-tell (C-LBT-F) state. As previously noted, this determination can be made via LBT as part of a previous transmit / transmit attempt and / or in response to a request to do so (e.g., from a service entity). This functionality can be integrated with... Figure 7A The determination made at frame 705 corresponds to this.

[0127] At box 820, this functionality includes transmitting from the UE to the serving entity an indication of one or more sets of RBs in the C-LBT-F state. Depending on some aspects, this functionality may be related to that described above. Figure 7A The functionality of arrow 710 corresponds to this. As noted, this indication can be provided via SLPP communication between the UE and the serving entity. More specifically, according to some implementations, transmitting an indication for one or more RB sets in the C-LBT-F state may include including the indication for one or more RB sets in the C-LBT-F state in a provideAssistanceData sidelink positioning protocol (SLPP) message.

[0128] As noted, according to some implementations, the UE can provide information about one or more RB sets that are not in the C-LBT-F state. For example, some implementations of method 800 may further include: determining that one or more RB sets in the shared spectrum are not in the C-LBT-F state; and transmitting an indication from the UE to the serving entity of the one or more RB sets that are not in the C-LBT-F state. Such implementations may also include transmitting LBT information from the UE to the serving entity. For each of the one or more RB sets that are not in the C-LBT-F state, the LBT information may include a corresponding current LBT counter value and a corresponding failure detection timer, or a corresponding binary value indicating the probability that the RB set will enter the C-LBT-F state within a threshold time amount.

[0129] At box 830, the functionality includes receiving at the UE, from the serving entity, a configuration for transmitting SL-PRS in the shared spectrum for use in the SL positioning procedure, the configuration being at least partially based on an indication of one or more RB sets in the C-LBT-F state and indicating at least one radio resource for transmitting the SL-PRS. This functionality may, for example, be as described above. Figure 7A The functionality is illustrated by arrow 720.

[0130] As previously noted, some implementations may allow subsequent C-LBT-F reporting and resource reselection. For example, some implementations of method 800 may further include: after receiving configuration for transmitting SL-PRS and before the start time of at least one radio resource, determining one or more RB sets that have entered the C-LBT-F state in at least one radio resource; and transmitting from the UE to the serving entity a report indicating one or more RB sets that have entered the C-LBT-F state in at least one radio resource. In such implementations, the report may indicate, for example, the total number of one or more RB sets that have entered the C-LBT-F state in at least one radio resource, the identifier of each of the one or more RB sets that have entered the C-LBT-F state in at least one radio resource, or any combination thereof. Additionally or alternatively, transmitting the report may be based at least in part on determining that for each of the one or more RB sets that have entered the C-LBT-F state in at least one radio resource, the corresponding C-LBT-F state will not terminate before the start time of at least one radio resource. According to some implementation schemes, it is determined that one or more sets of RBs that have entered the C-LBT-F state in at least one radio resource occur before the start time of at least one radio resource, where time T is configured according to the bandwidth portion (BWP) or resource pool (RP), is indicated to the UE by the SLPP, is determined by the UE, is equal to the LBT failure detection timer, or any combination thereof.

[0131] As also noted herein, implementations may provide alternative functionality if the UE determines, after receiving the SL-PRS configuration, that one or more RB sets have entered the C-LBT-F state. For example, some implementations of method 800 may include: after receiving the configuration for transmitting the SL-PRS and before the start time of at least one radio resource, determining one or more RB sets in at least one radio resource that have entered the C-LBT-F state; and (i) transmitting the SL-PRS using one or more RB sets in at least one radio resource that have not yet entered the C-LBT-F state, or (ii) not transmitting the SL-PRS.

[0132] As indicated above, Figure 8 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8 The examples described are different.

[0133] Figure 9This is a diagram illustrating an example device 900 for wireless communication according to the present disclosure. Device 900 may be a UE, or a UE may include device 900. In some aspects, device 900 includes a receiving component 902, a transmitting component 904, and / or a communication manager 906 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, the communication manager 906 is combined with... Figure 1 The described communication manager 140. As shown, device 900 can use receiving component 902 and transmitting component 904 to communicate with another device 908 (such as UE or network node (such as CU, DU, RU or base station)).

[0134] In some respects, device 900 can be configured to perform the functions described herein. Figures 6 to 7B One or more operations described herein. Additionally or alternatively, device 900 may be configured to perform one or more processes described herein, such as Figure 8 The process is 800. In some respects, Figure 9 The illustrated device 900 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 9 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0135] Receiver 902 may receive communications from device 908, such as reference signals, control information, data communications, or combinations thereof. Receiver 902 may provide the received communications to one or more other components of device 900. In some aspects, receiver 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.), and may provide the processed signals to one or more other components of device 900. In some aspects, receiver 902 may include combinations of... Figure 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0136] Transmitting component 904 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 908. In some aspects, one or more other components of device 900 can generate communications and provide the generated communications to transmitting component 904 for transmission to device 908. In some aspects, transmitting component 904 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 908. In some aspects, transmitting component 904 may include combinations of... Figure 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 904 may co-located with the receive component 902 in one or more transceivers.

[0137] The communication manager 906 may support the operation of the receiving component 902 and / or the transmitting component 904. For example, the communication manager 906 may receive information associated with configuring the reception of communications by the receiving component 902 and / or the transmission of communications by the transmitting component 904. Additionally or alternatively, the communication manager 906 may generate control information and / or provide such control information to the receiving component 902 and / or the transmitting component 904 to control the reception and / or transmission of communications.

[0138] The communication manager 906 can perform a multichannel access procedure for one or more sets of RBs in a shared spectrum. The transmitting component 904 can transmit a portion of the SL-PRS on the one or more sets of RBs, at least in part, based on a successful multichannel access procedure associated with one or more sets of RBs occupying a first number of RBs, wherein the first number of RBs is less than a second number of RBs for the broadband SL-PRS, and wherein the one or more sets of RBs used to transmit the portion of the SL-PRS are a subset of a plurality of nominal RBs associated with the broadband SL-PRS.

[0139] The receiving component 902 may receive configuration information indicating one or more conditions for sending a portion of the SL-PRS within a resource pool comprising one or more sets of RBs, wherein the portion of the SL-PRS is sent according to the configuration information.

[0140] The receiving component 902 can receive signaling from the network entity to enable or disable partial SL-PRS transmission for the current LCS session, wherein the sending component 904 is configured to send partial SL-PRS at least in part based on the signaling to enable partial SL-PRS transmission for the current LCS session.

[0141] The receiving component 902 can receive signaling from a network entity to enable or disable partial SL-PRS transmission for all LCS sessions within a resource pool that includes one or more RB sets, wherein the sending component 904 is configured to send partial SL-PRS at least in part based on the signaling to enable partial SL-PRS transmission for all LCS sessions within a resource pool that includes one or more RB sets.

[0142] The transmitting component 904 can send information related to the ability to transmit a portion of the SL-PRS to one or more of the scheduling nodes or receiving nodes, wherein the portion of the SL-PRS is transmitted on one or more sets of RBs based on the information related to the ability to transmit the SL-PRS.

[0143] The receiving component 902 can receive information related to the ability to receive or process a portion of the SL-PRS from one or more of the scheduling nodes or receiving nodes, wherein the portion of the SL-PRS is transmitted on one or more sets of RBs based on the information related to the ability to receive or process the SL-PRS.

[0144] The transmitting component 904 can transmit information indicating that a portion of the SL-PRS is being transmitted in the SCI accompanying the portion of the SL-PRS.

[0145] The transmitting component 904 can transmit information indicating that a partial SL-PRS is being transmitted and information indicating one or more parameters associated with the partial SL-PRS in the SCI accompanying the partial SL-PRS.

[0146] The transmitting component 904 may transmit information indicating one or more parameters associated with a portion of the SL-PRS after that portion of the SL-PRS.

[0147] Figure 9 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. Figure 9 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 9 The two or more components shown can be implemented within a single component, or Figure 9 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 9 The collection of (one or more) components shown is executable and described as being composed of Figure 9 Another set of components shown performs one or more functions.

[0148] It will be apparent to those skilled in the art that basic modifications can be made to suit specific requirements. For example, custom hardware can also be used, and / or specific elements can be implemented in hardware, software (including portable software such as applets), or both. Furthermore, connections to other computing devices, such as network input / output devices, can be employed.

[0149] In view of this specification, various embodiments may include different combinations of features. Specific implementation examples are described in the following numbered clauses.

[0150] Clause 1: A method for radio positioning performed by a user equipment (UE), the method comprising: determining that one or more resource block (RB) sets in a shared spectrum are in a persistent listen-before-say (C-LBT-F) state; transmitting from the UE to a serving entity an indication of the one or more RB sets in the C-LBT-F state; and receiving at the UE, from the serving entity, a configuration for transmitting a sidelink positioning reference signal (SL-PRS) in the shared spectrum for use in a sidelink (SL) positioning procedure, the configuration being at least in part based on the indication of the one or more RB sets in the C-LBT-F state and indicating at least one radio resource for transmitting the SL-PRS.

[0151] Clause 2: The method described in Clause 1, wherein the UE is not within the coverage of the wireless cellular network.

[0152] Clause 3: The method according to Clause 1 or Clause 2, wherein transmitting the indication to the one or more RB sets in the C-LBT-F state comprises: including the indication to the one or more RB sets in the C-LBT-F state in a provideAssistanceData sidelink positioning protocol (SLPP) message.

[0153] Clause 4: The method according to any one of Clauses 1 to 3 further comprises: determining that one or more RB sets in the shared spectrum are not in the C-LBT-F state; and transmitting from the UE to the serving entity an indication of the one or more RB sets that are not in the C-LBT-F state.

[0154] Clause 5: The method according to Clause 4 further includes: transmitting Listen-Before-Speak (LBT) information from the UE to the serving entity, wherein for each of the one or more RB sets that is not in the C-LBT-F state, the LBT information includes: a corresponding current LBT counter value and a corresponding failure detection timer, or a corresponding binary value indicating the probability that the RB set will enter the C-LBT-F state within a threshold time amount.

[0155] Clause 6: The method according to any one of Clauses 1 to 5, the method further comprising: after receiving the configuration for transmitting the SL-PRS and before the start time of the at least one radio resource: determining one or more RB sets in the at least one radio resource that have entered the C-LBT-F state; and transmitting from the UE to the serving entity a report indicating the one or more RB sets in the at least one radio resource that have entered the C-LBT-F state.

[0156] Clause 7: The method according to Clause 6, wherein the report indicates: the total number of the one or more RB sets that have entered the C-LBT-F state in the at least one radio resource, the identifier of each of the one or more RB sets that have entered the C-LBT-F state in the at least one radio resource, or any combination thereof.

[0157] Clause 8: The method according to any one of Clauses 6 to 7, wherein the transmission of the report is based at least in part on determining that for each of the one or more RB sets that has entered the C-LBT-F state in the at least one radio resource, the corresponding C-LBT-F state will not terminate before the start time of the at least one radio resource.

[0158] Clause 9: The method according to any one of Clauses 1 to 8, wherein the determination of the set of one or more RBs that have entered the C-LBT-F state in the at least one radio resource occurs before the time T prior to the start time of the at least one radio resource, wherein the time T is configured according to a bandwidth portion (BWP) or resource pool (RP), is indicated to the UE by the SLPP, is determined by the UE, is equal to the LBT failure detection timer, or any combination thereof.

[0159] Clause 10: The method according to any one of Clauses 1 to 9 further comprises: after receiving the configuration for transmitting the SL-PRS and before the start time of the at least one radio resource: determining one or more sets of RBs in the at least one radio resource that have entered the C-LBT-F state; and (i) transmitting the SL-PRS using one or more sets of RBs in the at least one radio resource that have not yet entered the C-LBT-F state, or (ii) not transmitting the SL-PRS.

[0160] Clause 11: The method according to any one of Clauses 1 to 10, wherein the service entity includes another UE or base station.

[0161] Clause 12: A User Equipment (UE) comprising: one or more transceivers; one or more memories; and one or more processors communicatively coupled to the one or more transceivers and the one or more memories, the one or more processors being configured to: determine that one or more resource block (RB) sets in a shared spectrum are in a persistent listen-before-tell-fail (C-LBT-F) state; transmit an indication of the one or more RB sets in the C-LBT-F state to a serving entity via the one or more transceivers; and receive from the serving entity via the one or more transceivers a configuration for transmitting a sidelink positioning reference signal (SL-PRS) in the shared spectrum for use in a sidelink (SL) positioning procedure, the configuration being at least in part based on the indication of the one or more RB sets in the C-LBT-F state and indicating at least one radio resource for transmitting the SL-PRS.

[0162] Clause 13: The UE according to Clause 12, wherein, in order to transmit the indication to the one or more RB sets in the C-LBT-F state, the one or more processors are configured to include the indication to the one or more RB sets in the C-LBT-F state in a provideAssistanceData side-link positioning protocol (SLPP) message.

[0163] Clause 14: The UE according to Clause 12 or Clause 13, wherein the one or more processors are further configured to: determine that one or more RB sets in the shared spectrum are not in the C-LBT-F state; and transmit an indication to the serving entity via the one or more transceivers of the one or more RB sets that are not in the C-LBT-F state.

[0164] Clause 15: For any UE pursuant to any one of Clauses 12 to 14, wherein the one or more processors are further configured to transmit Listen-Before-Speak (LBT) information to the serving entity via the one or more transceivers, wherein for each of the one or more RB sets that is not in the C-LBT-F state, the LBT information includes: a corresponding current LBT counter value and a corresponding failure detection timer, or a corresponding binary value indicating the probability that the RB set will enter the C-LBT-F state within a threshold time amount.

[0165] Clause 16: The UE pursuant to any one of Clauses 12 to 15, wherein the one or more processors are further configured to: after receiving the configuration for transmitting the SL-PRS and before the start time of the at least one radio resource: determine one or more sets of RBs in the at least one radio resource that have entered the C-LBT-F state; and transmit, via the one or more transceivers, a report indicating the one or more sets of RBs in the at least one radio resource that have entered the C-LBT-F state to the serving entity.

[0166] Clause 17: The UE as described in Clause 16, wherein the one or more processors are further configured to include in the report an indication of: the total number of the one or more RB sets that have entered the C-LBT-F state in the at least one radio resource, the identifier of each of the one or more RB sets that have entered the C-LBT-F state in the at least one radio resource, or any combination thereof.

[0167] Clause 18: A UE pursuant to any one of Clauses 16 to 17, wherein the one or more processors are configured to transmit the report based at least in part on determining that for each of the one or more RB sets that has entered the C-LBT-F state in the at least one radio resource, the corresponding C-LBT-F state will not terminate before the start time of the at least one radio resource.

[0168] Clause 19: A UE pursuant to any one of Clauses 16 to 18, wherein the one or more processors are configured to: determine that the one or more RB sets in the at least one radio resource have entered the C-LBT-F state before a time T prior to the start time of the at least one radio resource, wherein the time T is configured according to a Bandwidth Part (BWP) or Resource Pool (RP), is indicated to the UE via SLPP, is determined by the UE, is equal to the LBT Failure Detection Timer, or any combination thereof.

[0169] Clause 20: An apparatus comprising: means for determining that one or more resource block (RB) sets in a shared spectrum are in a persistent listen-before-tell-fail (C-LBT-F) state; means for transmitting to a serving entity an indication of the one or more RB sets in the C-LBT-F state; and means for receiving from the serving entity a configuration for transmitting a sidelink positioning reference signal (SL-PRS) in the shared spectrum for a sidelink (SL) positioning procedure, the configuration being at least in part based on the indication of the one or more RB sets in the C-LBT-F state and indicating at least one radio resource for transmitting the SL-PRS.

[0170] Clause 21: An apparatus having components for performing the method according to any one of Clauses 1 to 11.

[0171] Clause 22: A non-transitory computer-readable medium storing instructions, said instructions including code for performing a method according to any one of Clauses 1 to 11.

Claims

1. A method for wireless positioning performed by a user equipment (UE), the method comprising: Determine that one or more resource blocks (RBs) in the shared spectrum are in a persistent listen-before-speak (C-LBT-F) state; The UE transmits an indication to the serving entity of one or more RB sets that are in the C-LBT-F state; as well as At the UE, a configuration is received from the serving entity for transmitting a sidelink positioning reference signal (SL-PRS) in the shared spectrum for use in a sidelink (SL) positioning process. The configuration is based at least in part on the indication of the one or more RB sets in the C-LBT-F state and indicates at least one radio resource for transmitting the SL-PRS.

2. The method according to claim 1, wherein the UE is not within the coverage of the wireless cellular network.

3. The method of claim 1, wherein transmitting the indication to the one or more RB sets in the C-LBT-F state comprises: The indication for the one or more RB sets in the C-LBT-F state is included in the provideAssistanceData sidelink positioning protocol (SLPP) message.

4. The method according to claim 1, further comprising: It is determined that one or more RB sets in the shared spectrum are not in the C-LBT-F state; as well as The UE transmits an indication to the serving entity of one or more RB sets that are not in the C-LBT-F state.

5. The method according to claim 4, further comprising: The UE transmits Listen-Before-Speak (LBT) information to the serving entity, wherein for each of the one or more RB sets that is not in the C-LBT-F state, the LBT information includes: The corresponding current LBT counter value and the corresponding failure detection timer, or A corresponding binary value indicating the probability that the RB set will enter the C-LBT-F state within a threshold time amount.

6. The method according to claim 1, further comprising: After receiving the configuration for transmitting the SL-PRS and before the start time of the at least one radio resource: Identify one or more sets of RBs in the at least one radio resource that have entered the C-LBT-F state; as well as The UE transmits a report to the serving entity indicating that one or more sets of RBs in at least one radio resource have entered the C-LBT-F state.

7. The method of claim 6, wherein the report indicates: The total number of the one or more RB sets that have entered the C-LBT-F state in at least one radio resource. The identifier of each of the one or more RB sets that has entered the C-LBT-F state in the at least one radio resource, or Any combination of them.

8. The method of claim 6, wherein transmitting the report is based at least in part on determining that for each of the one or more RB sets that has entered the C-LBT-F state in the at least one radio resource, the corresponding C-LBT-F state will not terminate before the start time of the at least one radio resource.

9. The method of claim 6, wherein determining the set of one or more RBs that have entered the C-LBT-F state in the at least one radio resource occurs before a time T prior to the start time of the at least one radio resource, wherein the time T: It is configured according to the Bandwidth Part (BWP) or Resource Pool (RP). It is indicated to the UE via SLPP. It is determined by the UE. Equal to LBT failure detection timer, or Any combination of them.

10. The method according to claim 1, further comprising: After receiving the configuration for transmitting the SL-PRS and before the start time of the at least one radio resource: Identify one or more sets of RBs in the at least one radio resource that have entered the C-LBT-F state; as well as: (i) Transmit the SL-PRS using one or more RB sets from the at least one radio resource that have not yet entered the C-LBT-F state, or (ii) Do not send the SL-PRS.

11. The method of claim 1, wherein the service entity includes another UE or a base station.

12. A user equipment (UE), the user equipment (UE) comprising: One or more transceivers; One or more memory units; and One or more processors, said one or more processors being communicatively coupled to said one or more transceivers and said one or more memories, said one or more processors being configured to: Determine that one or more resource blocks (RBs) in the shared spectrum are in a persistent listen-before-speak (C-LBT-F) state; Indications for the one or more RB sets in the C-LBT-F state are transmitted to the serving entity via the one or more transceivers; as well as The configuration received from the serving entity via the one or more transceivers for transmitting a sidelink positioning reference signal (SL-PRS) in the shared spectrum for use in a sidelink (SL) positioning process is at least in part based on the indication of the one or more RB sets in the C-LBT-F state and the indication of at least one radio resource for transmitting the SL-PRS.

13. The UE of claim 12, wherein, in order to transmit the indication to the one or more RB sets in the C-LBT-F state, the one or more processors are configured to include the indication to the one or more RB sets in the C-LBT-F state in a provideAssistanceData sidelink positioning protocol (SLPP) message.

14. The UE of claim 12, wherein the one or more processors are further configured to: Determine that one or more sets of RBs in the shared spectrum are not in the C-LBT-F state; and Indications for the one or more RB sets that are not in the C-LBT-F state are transmitted to the serving entity via the one or more transceivers.

15. The UE of claim 14, wherein the one or more processors are further configured to: transmit Listen-Before-Speak (LBT) information to the serving entity via the one or more transceivers, wherein for each of the one or more RB sets not in the C-LBT-F state, the LBT information includes: The corresponding current LBT counter value and the corresponding failure detection timer, or A corresponding binary value indicating the probability that the RB set will enter the C-LBT-F state within a threshold time amount.

16. The UE of claim 12, wherein the one or more processors are further configured to: after receiving the configuration for transmitting the SL-PRS and before the start time of the at least one radio resource: Determine one or more sets of RBs in the at least one radio resource that have entered the C-LBT-F state; and The service entity is transmitted via the one or more transceivers a report indicating that the one or more sets of RBs in the at least one radio resource have entered the C-LBT-F state.

17. The UE of claim 16, wherein the one or more processors are further configured to include indications of the following in the report: The total number of the one or more RB sets that have entered the C-LBT-F state in at least one radio resource. The identifier of each of the one or more RB sets that has entered the C-LBT-F state in the at least one radio resource, or Any combination of them.

18. The UE of claim 16, wherein the one or more processors are configured to transmit the report based at least in part on determining that for each of the one or more RB sets that has entered the C-LBT-F state in the at least one radio resource, the corresponding C-LBT-F state will not terminate before the start time of the at least one radio resource.

19. The UE of claim 16, wherein the one or more processors are configured to: determine that the one or more RB sets in the at least one radio resource have entered the C-LBT-F state before a time T prior to the start time of the at least one radio resource, wherein the time T: It is configured according to the Bandwidth Part (BWP) or Resource Pool (RP). It is indicated to the UE via SLPP. It is determined by the UE. Equal to LBT failure detection timer, or Any combination of them.

20. An apparatus, the apparatus comprising: A component used to determine that one or more resource blocks (RBs) in a shared spectrum are in a persistent listen-before-speak (C-LBT-F) state; A component for transmitting to a service entity an indication of one or more sets of RBs in the C-LBT-F state; and Components for receiving from the serving entity a configuration for transmitting a sidelink positioning reference signal (SL-PRS) in the shared spectrum for use in a sidelink (SL) positioning process, the configuration being at least in part based on the indication of the one or more RB sets in the C-LBT-F state and indicating at least one radio resource for transmitting the SL-PRS.

Images