Adaptation of sidelink positioning in channel load management

Abstract

Techniques for adapting sidelink positioning in channel load management are disclosed. The techniques may include transmitting a message indicating a sidelink positioning reference signal (SL-PRS) congestion control processing capability of a UE; determining an applicable congestion control processing time value for congestion control of a first sidelink (SL) resource pool according to the SL-PRS congestion control processing capability of the UE, the first SL resource pool comprising SL-PRS resources; measuring a channel busy rate (CBR) of the first SL resource pool for a first time slot; selecting, based on the measured CBR, resources of the first SL resource pool for communication during a second time slot, wherein the second time slot is temporally offset from the first time slot by the applicable congestion control processing time value; and communicating using the selected resource during the second time slot.

Description

[0001] Related Applications

[0002] This application claims the benefit of Greek application No. 20220100580, filed on July 20, 2022, entitled "ACCOMMODATION FOR SIDELINKPOSITIONING IN CHANNEL LOAD MANAGEMENT," which is assigned to the assignee of this application and is incorporated herein by reference in its entirety. Background Art Technical Field

[0003] The present disclosure relates generally to the field of wireless communications, and more particularly to determining the location of a user equipment (UE) using radio frequency (RF) signals.

[0004] Related technologies

[0005] In a data communication network, various positioning techniques may be used to determine the location of a mobile device (referred to herein as a UE). Some of these positioning techniques may involve determining distance and / or angle information of RF signals received by one or more other UEs communicatively coupled to the data communication network. In the fifth generation (5G) wireless standard referred to as New Radio (NR), direct communication between UEs (including the transmission of RF signals for positioning) may be referred to as a side link (also referred to herein as a "SL"). Summary of the invention

[0006] Various aspects of this document provide improved congestion control for sidelink subchannels of a radio access network. According to the techniques herein, a UE may be configured to identify / implement different congestion control processing times for sidelink (SL) subchannels including sidelink positioning reference signal (SL-PRS) resources. This may enable the UE to better adjust the use of such SL subchannels based on the level of congestion on such SL subchannels.

[0007] An example method for wireless communication by a user equipment (UE) according to the present disclosure may include: sending a message indicating the UE's sidelink positioning reference signal (SL-PRS) congestion control handling capability. The method may also include: determining an applicable congestion control handling time value for congestion control of a first side link (SL) resource pool based on the UE's SL-PRS congestion control handling capability, the first SL resource pool including SL-PRS resources. The method may additionally include: measuring a channel busy rate (CBR) of the first SL resource pool for a first time slot; and selecting resources of the first SL resource pool for use in communicating during a second time slot based on the measured CBR, wherein the second time slot is time-shifted from the first time slot by the applicable congestion control handling time value. The method may also include: communicating using the selected resources during the second time slot.

[0008] According to the present disclosure, an example user equipment (UE) may include a transceiver, a memory, and one or more processors communicatively coupled to the transceiver and the memory. The one or more processors may be configured to send a message indicating the UE's sidelink positioning reference signal (SL-PRS) congestion control processing capability via the transceiver. The one or more processors may also be configured to determine an applicable congestion control processing time value for congestion control of a first side link (SL) resource pool based on the UE's SL-PRS congestion control processing capability, the first SL resource pool including SL-PRS resources. The one or more processors may additionally be configured to measure a channel busy rate (CBR) of a first SL resource pool for a first time slot; and select resources of the first SL resource pool based on the measured CBR for use in communicating during a second time slot, wherein the second time slot is time-shifted from the first time slot by an applicable congestion control processing time value. The one or more processors may be further configured to communicate using the selected resources during the second time slot.

[0009] An example apparatus for wireless communication according to the present disclosure may include a component for sending a message indicating a sidelink positioning reference signal (SL-PRS) congestion control handling capability of a user equipment (UE). The apparatus may also include a component for determining an applicable congestion control handling time value for congestion control of a first sidelink (SL) resource pool based on the UE's SL-PRS congestion control handling capability, the first SL resource pool including SL-PRS resources. The apparatus may additionally include a component for performing the following operations: measuring a channel busy rate (CBR) of a first SL resource pool for a first time slot; and selecting resources of the first SL resource pool for use in communicating during a second time slot based on the measured CBR, wherein the second time slot is time-shifted from the first time slot by the applicable congestion control handling time value. The apparatus may also include a component for communicating using the selected resources during the second time slot.

[0010] According to an example non-transitory computer-readable medium of the present disclosure, instructions for wireless communication by a user equipment (UE) may be stored, the instructions including code for performing the following operations: sending a message indicating the sidelink positioning reference signal (SL-PRS) congestion control handling capability of the UE. The instructions may also include code for performing the following operations: determining an applicable congestion control handling time value for congestion control of a first side link (SL) resource pool according to the SL-PRS congestion control handling capability of the UE, the first SL resource pool including SL-PRS resources. The instructions may additionally include code for performing the following operations: measuring a channel busy rate (CBR) of a first SL resource pool for a first time slot; and selecting resources of the first SL resource pool for communication during a second time slot based on the measured CBR, wherein the second time slot is time-shifted from the first time slot by the applicable congestion control handling time value. The instructions may also include code for communicating using the selected resources during the second time slot.

[0011] This summary is neither intended to identify key features or essential features of the claimed subject matter nor is it intended to be used alone to determine the scope of the claimed subject matter. The subject matter should be understood by reference to appropriate portions of the entire specification of the disclosure, any or all of the drawings, and each claim. The foregoing and other features and examples will be described in more detail in the following description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 is a diagram of a positioning system according to aspects of the present disclosure.

[0013] Figure 2 is a diagram of a 5th generation (5G) new radio (NR) positioning system, which illustrates a positioning system implemented within a 5G NR communication network (e.g., Figure 1 An example of a positioning system.

[0014] FIG. 3A to FIG. 3C is a simplified illustration of a scenario in which sidelink positioning may be used to determine the location of a target user equipment (UE).

[0015] Figure 4 is a diagram showing an example of a frame structure for NR and associated terms.

[0016] Figure 5 is a diagram showing an example of a radio frame sequence with a positioning reference signal (PRS) positioning opportunity.

[0017] Figure 6 is a diagram illustrating an example combination (comb) structure of how an example RF signal may utilize different sets of resource elements in accordance with aspects of the present disclosure.

[0018] Figure 7 is a diagram illustrating example resource pools for positioning within a sidelink resource pool in accordance with aspects of the present disclosure.

[0019] Figure 8 is a block diagram illustrating an example operating environment in accordance with aspects of the present disclosure.

[0020] Fig. 9 is a flow chart of an example method of wireless communications by a UE according to aspects of the present disclosure.

[0021] Fig.10 is a block diagram of an embodiment of a UE that may be utilized in implementations as described herein.

[0022] Similar reference symbols in the various drawings indicate similar elements according to certain example implementations. In addition, multiple instances of an element may be indicated by adding a letter or hyphen and a second number after the first number of the element. For example, multiple instances of element 110 may be indicated as 110-1, 110-2, 110-3, etc. or 110a, 110b, 110c, etc. When only the first number is used to refer to such an element, any instance of the element should be understood (for example, element 110 in the previous example will refer to elements 110-1, 110-2 and 110-3 or to elements 110a, 110b and 110c). DETAILED DESCRIPTION

[0023] The following description is directed to certain implementations for the purpose of describing the innovative aspects of the various embodiments. However, one of ordinary skill in the art will readily recognize that the teachings herein can be applied in a variety of different ways. The described implementations can be implemented in any device, system, or network capable of sending and receiving radio frequency (RF) signals according to any communication standard, such as any of the following: the Institute of Electrical and Electronics Engineers (IEEE) 802.15.4 standard for ultra-wideband (UWB), the IEEE 802.11 standard (including those identified as Wi-Fi), and the like. Technical standards), Standard, Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband CDMA (W-CDMA), Evolution-Data Optimized (EV-DO), 1xEV-DO, EV-DO Revision A, EV-DO Revision B, High Rate Packet Data (HRPD), High Speed ​​Packet Access (HSPA), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolved High Speed ​​Packet Access (HSPA+), Long Term Evolution (LTE), Advanced Mobile Phone System (AMPS), or other known signals for communicating within a wireless, cellular or Internet of Things (IoT) network, such as a system utilizing 3G, 4G, 5G, 6G or further implementations thereof.

[0024] As used herein, "RF signals" include electromagnetic waves that transmit information through the space between a transmitter (or transmitting device) and a receiver (or receiving device). As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of each RF signal through multiple channels or paths, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal.

[0025] Additionally, unless otherwise indicated, references to "reference signals," "positioning reference signals," "reference signals used for positioning," etc. may be used to refer to signals used to locate user equipment (UE). As described in more detail herein, such signals may include any of a variety of signal types, but may not necessarily be limited to positioning reference signals (PRS) as defined in relevant wireless standards.

[0026] Figure 1is a simplified illustration of a positioning system 100 according to a specific implementation, in which a UE 105, a location server 160, and / or other components of the positioning system 100 may use the techniques provided herein for locating a UE 105 (and other positioning techniques). The techniques described herein may be implemented by one or more components of the positioning system 100. The positioning system 100 may include: a UE 105; one or more satellites 110 (also referred to as space vehicles (SVs)) for a global navigation satellite system (GNSS) such as a global positioning system (GPS), GLONASS, Galileo, or BeiDou; a base station 120; an access point (AP) 130; a location server 160; a network 170; and an external client 180. In general, the positioning system 100 may estimate the location of the UE 105 based on RF signals received by and / or transmitted from the UE 105 and the known locations of other components (e.g., GNSS satellites 110, base stations 120, APs 130) that send and / or receive RF signals. Reference Figure 2 Additional details regarding specific location estimation techniques are discussed in more detail.

[0027] It should be pointed out that Figure 1 Only a generalized illustration of various components is provided, any or all of which may be utilized as appropriate, and each component may be repeated as needed. Specifically, although only one UE 105 is illustrated, it should be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the positioning system 100. Similarly, the positioning system 100 may include more than one UE 105. Figure 1 100. The illustrated connections connecting the various components in the positioning system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. In addition, the components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality. In some embodiments, for example, the external client 180 may be directly connected to the location server 160. Those of ordinary skill in the art will recognize many modifications to the illustrated components.

[0028] Depending on the desired functionality, network 170 may include any one of a variety of wireless and / or wired networks. Network 170 may, for example, include any combination of public and / or private networks, local area networks and / or wide area networks, etc. In addition, network 170 may utilize one or more wired and / or wireless communication technologies. In some embodiments, network 170 may include, for example, cellular or other mobile networks, wireless local area networks (WLANs), wireless wide area networks (WWANs), and / or the Internet. Examples of network 170 include long-term evolution (LTE) wireless networks, fifth-generation (5G) wireless networks (also referred to as new radio (NR) wireless networks or 5G NR wireless networks), Wi-Fi WLANs, and the Internet. LTE, 5G, and NR are wireless technologies defined or being defined by the Third Generation Partnership Project (3GPP). Network 170 may also include more than one network and / or more than one type of network.

[0029] Base station 120 and access point (AP) 130 may be communicatively coupled to network 170. In some embodiments, base station 120 may be owned, maintained and / or operated by a cellular network provider and may employ any of a variety of wireless technologies, as described herein below. Depending on the technology of network 170, base station 120 may include a node B, an evolved node B (eNodeB or eNB), a transceiver base station (BTS), a radio base station (RBS), an NR node B (gNB), a next generation eNB (ng-eNB), etc. In the case where network 170 is a 5G network, base station 120 as a gNB or ng-eNB may be part of a next generation radio access network (NG-RAN) that may be connected to a 5G core network (5GC). In view of the open radio access network (O-RAN) and / or virtualized radio access network (V-RAN or vRAN) in 5G or higher networks, the functionality performed by the base station 120 in the earlier networks (e.g., 3G and 4G) may be divided into different functional components (e.g., radio unit (RU), distributed unit (DU), central unit (CU)) and layers (e.g., L1 / L2 / L3), which may be executed on different devices at different locations connected, for example, via fronthaul connections, midhaul connections, and backhaul connections. As described herein, a "base station" (or ng-eNB, gNB, etc.) may include any or all of these functional components. For example, AP 130 may include a Wi-Fi AP or AP or an AP with cellular capabilities (e.g., 4G LTE and / or 5GNR). Thus, UE 105 can transmit and receive information with network-connected devices such as location server 160 by accessing network 170 via base station 120 using first communication link 133. Additionally or alternatively, because AP 130 can also be communicatively coupled with network 170, UE 105 can communicate with network-connected and Internet-connected devices (including location server 160) using second communication link 135 or via one or more other UEs 145.

[0030] As used herein, the term "base station" may generally refer to a single physical transmission point or multiple co-located physical transmission points that may be located at a base station 120. A transmit receive point (TRP) (also referred to as a transmit / receive point) corresponds to this type of transmission point, and the term "TRP" may be used interchangeably herein with the terms "gNB," "ng-eNB," and "base station" in relation to a physical transmission point (e.g., for UE positioning). In some cases, a base station 120 may include multiple TRPs—e.g., where each TRP is associated with a different antenna or a different antenna array of the base station 120. A physical transmission point may include an antenna array of the base station 120 (e.g., as in a multiple-input multiple-output (MIMO) system and / or where the base station employs beamforming). The term "base station" may additionally refer to multiple non-co-located physical transmission points, which may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station).

[0031] As used herein, the term "cell" may generally refer to a logical communication entity for communicating with base station 120, and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) for distinguishing adjacent cells operating via the same or different carriers. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), or other protocols) that may provide access for different types of devices. In some cases, the term "cell" may refer to a portion of a geographic coverage area (e.g., a sector) on which the logical entity operates.

[0032] The location server 160 may include a server and / or other computing device configured to determine an estimated location of the UE 105 and / or provide data (e.g., “assistance data”) to the UE 105 to facilitate location measurement and / or location determination by the UE 105. According to some embodiments, the location server 160 may include a Home Secure User Plane Location (SUPL) Location Platform (H-SLP), which may support the SUPL User Plane (UP) location solution defined by the Open Mobile Alliance (OMA) and may support location services for the UE 105 based on subscription information of the UE 105 stored in the location server 160. In some embodiments, the location server 160 may include a Discovery SLP (D-SLP) or an Emergency SLP (E-SLP). The location server 160 may also include an enhanced serving mobile location center (E-SMLC) that supports positioning of the UE 105 using a control plane (CP) positioning solution for LTE radio access of the UE 105. The location server 160 may also include a location management function (LMF) that supports positioning of the UE 105 using a control plane (CP) positioning solution for NR or LTE radio access of the UE 105.

[0033] In the CP positioning solution, from the perspective of the network 170, the signaling for controlling and managing the positioning of the UE 105 may use existing network interfaces and protocols and be exchanged as signaling between the elements of the network 170 and with the UE 105. In the UP positioning solution, from the perspective of the network 170, the signaling for controlling and managing the positioning of the UE 105 may be exchanged between the location server 160 and the UE 105 as data (e.g., data transmitted using the Internet Protocol (IP) and / or the Transmission Control Protocol (TCP)).

[0034] As previously noted (and discussed in more detail below), the estimated position of UE 105 may be based on measurements of RF signals transmitted from and / or received by UE 105. In particular, these measurements may provide information about the relative distances and / or angles of UE 105 from one or more components in positioning system 100 (e.g., GNSS satellites 110, APs 130, base stations 120). The estimated position of UE 105 may be estimated geometrically (e.g., using multi-angle measurements and / or multilateration) based on the distance and / or angle measurements along with the known positions of the one or more components.

[0035] Although ground components (such as AP 130 and base station 120) may be fixed, embodiments are not limited thereto. Mobile components may be used. For example, in some embodiments, the position of UE 105 may be estimated based at least in part on measurements of RF signals 140 communicated between UE 105 and one or more other UEs 145 (these UEs may be mobile or fixed). When one or more other UEs 145 are used in determining the location of a particular UE 105, the UE 105 whose location is to be determined may be referred to as a "target UE", and each of the one or more other UEs 145 may be referred to as an "anchor UE". In order to determine the location of the target UE, the corresponding location of the one or more anchor UEs may be known and / or determined jointly with the target UE. Direct communication between the one or more other UEs 145 and UE 105 may include side links and / or similar device-to-device (D2D) communication technologies. The side links defined by 3GPP are D2D communication forms based on cellular LTE and NR standards.

[0036] The estimated position of UE 105 may be used in a variety of applications, such as to assist a user of UE 105 in direction finding or navigation or to assist another user (e.g., associated with external client 180) in locating UE 105. "Position" is also referred to herein as "position estimate," "estimated position," "position," "position estimate," "position fix," "estimated position," "position fix," or "fix." The process of determining a position may be referred to as "positioning," "position determination," "position determination," or the like. The position of UE 105 may include an absolute position of UE 105 (e.g., latitude and longitude, and possibly altitude) or a relative position of UE 105 (e.g., a position expressed as a distance north or south, east or west, and possibly above or below some other known fixed position (including, for example, the position of base station 120 or AP 130) or some other location (such as the position of UE 105 at some known previous time, or the position of another UE 145 at some known previous time)). The location may be specified as a geodetic location including coordinates that may be absolute (e.g., latitude, longitude, and optionally altitude), relative (e.g., relative to some known absolute location), or local (e.g., X, Y, and optionally Z coordinates according to a coordinate system defined relative to a local area, such as a factory, warehouse, university campus, shopping mall, stadium, or convention center). The location may alternatively be a city location, and may then include one or more of a street address (e.g., including a country, state, county, city, road and / or street name or label, and / or road or street number) and / or a label or name of a place, a building, a portion of a building, a floor of a building, and / or a room within a building, etc. The location may also include uncertainty or error indications, such as horizontal distances and possibly vertical distances over which the location is expected to have error, or an indication of an area or volume (e.g., a circle or ellipse) within which the UE 105 is expected to be located with a certain confidence level (e.g., 95% confidence).

[0037] The external client 180 may be a web server or remote application that may have some association with the UE 105 (e.g., accessible by a user of the UE 105), or may be a server, application, or computer system that provides location services to one or more other users, which may include obtaining and providing the location of the UE 105 (e.g., to enable services such as friend or relative locating, or child or pet locating). Additionally or alternatively, the external client 180 may obtain the location of the UE 105 and provide it to emergency service providers, government agencies, etc.

[0038] As previously noted, the example positioning system 100 may be implemented using a wireless communication network such as an LTE-based or 5GNR-based network. Figure 2A diagram of a 5G NR positioning system 200 is shown, which illustrates an embodiment of a positioning system (e.g., positioning system 100) that implements 5G NR. The 5G NR positioning system 200 can be configured to determine the location of the UE 105 by using access nodes to implement one or more positioning methods. The access nodes can include NR Node Bs (gNBs) 210-1 and 210-2 (collectively referred to herein as gNBs 210), ng-eNBs 214, and / or WLANs 216. The gNBs 210 and / or ng-eNBs 214 can communicate with the UE 105 to determine the location of the UE 105. Figure 1 The base station 120 corresponds to the WLAN 216, and the WLAN 216 can be connected to the Figure 1 130. Optionally, the 5G NR positioning system 200 may be additionally configured to determine the location of the UE 105 by using the LMF 220 (which may correspond to the location server 160) to implement one or more positioning methods. Here, the 5G NR positioning system 200 includes the UE 105, and components of a 5G NR network, which includes a next generation (NG) radio access network (RAN) (NG-RAN) 235 and a 5G core network (5G CN) 240. The 5G network may also be referred to as an NR network; the NG-RAN 235 may be referred to as a 5G RAN or an NR RAN; and the 5G CN 240 may be referred to as an NG core network. The 5G NR positioning system 200 may further utilize information from GNSS satellites 110 of a GNSS system, such as the Global Positioning System (GPS) or a similar system, such as GLONASS, Galileo, BeiDou, Indian Regional Navigation Satellite System (IRNSS). Additional components of the 5G NR positioning system 200 are described below. The 5G NR positioning system 200 may include additional or alternative components.

[0039] It should be pointed out that Figure 2Only generalized illustrations of various components are provided, any or all of which may be utilized as appropriate, and each component may be repeated or omitted as desired. Specifically, although only one UE 105 is illustrated, it should be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the 5G NR positioning system 200. Similarly, the 5G NR positioning system 200 may include a larger (or smaller) number of GNSS satellites 110, gNB 210, ng-eNB 214, wireless local area network (WLAN) 216, access and mobility management function (AMF) 215, external client 230, and / or other components. The illustrated connections connecting the various components in the 5G NR positioning system 200 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. In addition, the components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.

[0040] UE 105 may include and / or be referred to as a device, a mobile device, a wireless device, a mobile terminal, a terminal, a mobile station (MS), a terminal (SET) enabled with secure user plane location (SUPL), or some other name. In addition, UE 105 may correspond to a cellular phone, a smart phone, a laptop computer, a tablet computer, a personal data assistant (PDA), a navigation device, an Internet of Things (IoT) device, or some other portable or mobile device. Typically, although not necessarily, UE 105 may support the use of one or more radio access technologies (RATs) such as GSM, CDMA, W-CDMA, LTE, High Rate Packet Data (HRPD), IEEE 802.11 Wi-Fi, or some other wireless communication technology. , Bluetooth, Worldwide Interoperability for Microwave Access (WiMAX TM ), 5G NR (e.g., using NG-RAN 235 and 5G CN 240). UE 105 may also support wireless communications using WLAN 216, which is similar to one or more RATs and as previously described with respect to Figure 1 The use of one or more of these RATs may allow UE 105 (e.g., via Figure 2 Elements of the 5G CN 240, not shown, may communicate with external clients 230, or possibly via a Gateway Mobile Location Center (GMLC) 225) and / or allow external clients 230 (e.g., via GMLC 225) to receive location information about UE 105. When implemented in or communicatively coupled with a 5G NR network, Figure 2 The external client 230 may correspond to Figure 1 External client 180.

[0041] UE 105 may include a single entity or may include multiple entities, such as in a personal area network in which a user may employ audio, video, and / or data I / O devices, and / or body sensors and separate wired or wireless modems. The estimate of the location of UE 105 may be referred to as location, location estimate, location fix, fix, position, position estimate, or position fix, and may be geodetic, providing location coordinates (e.g., latitude and longitude) for UE 105, which may or may not include an altitude component (e.g., height above sea level; height above or depth below ground level, floor level, or basement level). Alternatively, the location of UE 105 may be expressed as a municipal location (e.g., a postal address or a designation of a point or smaller area in a building, such as a specific room or floor). The location of UE 105 may also be expressed as an area or volume (geographically or municipally defined) within which UE 105 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.). The location of the UE 105 may also be a relative location, including, for example, a distance and direction or relative X, Y (and Z) coordinates defined relative to some origin at a known location, which may be defined geodetically, municipally, or with reference to a point, area, or volume indicated on a map, floor plan, or building plan. In the descriptions contained herein, the use of the term "location" may include any of these variations unless otherwise indicated. When calculating the location of the UE, local X, Y, and possibly Z coordinates are typically solved, and then the local coordinates are converted to absolute coordinates (e.g., with respect to latitude, longitude, and altitude above or below mean sea level) if necessary.

[0042] Figure 2 The base stations in the NG-RAN 235 shown may correspond to Figure 1 The base stations 120 in the NG-RAN 235 may include gNBs 210. Pairs of gNBs 210 in the NG-RAN 235 may be connected to each other (e.g., Figure 2 The communication interface between the base stations (gNB 210 and / or ng-eNB 214) may be referred to as an Xn interface 237. Access to the 5G network is provided to the UE 105 via wireless communication between the UE 105 and one or more gNBs 210, which may provide wireless communication access to the 5G CN 240 on behalf of the UE 105 using 5G NR. The wireless interface between the base station (gNB 210 and / or ng-eNB 214) and the UE 105 may be referred to as an Uu interface 239. 5G NR radio access may also be referred to as NR radio access or 5G radio access. Figure 2, it is assumed that the serving gNB for UE 105 is gNB 210-1, but other gNBs (e.g., gNB 210-2) may act as serving gNBs if UE 105 moves to another location, or may act as secondary gNBs to provide additional throughput and bandwidth to UE 105.

[0043] Figure 2 The base stations in the illustrated NG-RAN 235 may additionally or alternatively include a next generation evolved Node B (also referred to as ng-eNB) 214. The ng-eNB 214 may be connected to one or more gNBs 210 in the NG-RAN 235—e.g., directly, or indirectly via other gNBs 210 and / or other ng-eNBs. The ng-eNB 214 may provide LTE radio access and / or evolved LTE (eLTE) radio access to the UE 105. Figure 2 Some of the gNBs 210 (e.g., gNB 210-2) and / or ng-eNBs 214 may be configured to function as positioning-only beacons that may transmit signals (e.g., positioning reference signals (PRS)) and / or may broadcast assistance data to assist in positioning UE 105, but may not receive signals from UE 105 or other UEs. Some of the gNBs 210 (e.g., gNB 210-2 and / or another gNB not shown) and / or ng-eNBs 214 may be configured to function as detection-only nodes that may scan for signals containing, for example, PRS data, assistance data, or other location data. Such detection-only nodes may not transmit signals or data to the UE, but may transmit signals or data (related to, for example, PRS, assistance data, or other location data) to other network entities (e.g., one or more components of 5G CN 240, external clients 230, or a controller), which may receive and store the data or use the data to locate at least UE 105. It should be noted that although Figure 2 Only one ng-eNB 214 is shown in FIG, but some embodiments may include multiple ng-eNBs 214. Base stations (e.g., gNB 210 and / or ng-eNB 214) may communicate directly with each other via an Xn communication interface. Additionally or alternatively, the base station may communicate directly or indirectly with other components of the 5G NR positioning system 200 (such as LMF 220 and AMF 215).

[0044] The 5G NR positioning system 200 may also include one or more WLANs 216 that may be connected to a non-3GPP interworking function (N3IWF) 250 in the 5GCN 240 (e.g., in the case of an untrusted WLAN 216). For example, the WLAN 216 may support IEEE 802.11 Wi-Fi access for the UE 105 and may include one or more Wi-Fi APs (e.g., Figure 1 Here, the N3IWF 250 may be connected to other elements in the 5G CN 240, such as the AMF 215. In some embodiments, the WLAN 216 may support another RAT, such as Bluetooth. The N3IWF 250 may provide support for secure access of the UE 105 to other elements in the 5G CN 240 and / or may support interworking of one or more protocols used by the WLAN 216 and the UE 105 with one or more protocols used by other elements of the 5G CN 240 (such as the AMF 215). For example, the N3IWF 250 may support: IPSec tunnel establishment with the UE 105, termination of the IKEv2 / IPSec protocol with the UE 105, termination of the N2 and N3 interfaces with the 5G CN 240 for the control plane and the user plane, respectively, and relay of uplink (UL) and downlink (DL) control plane non-access stratum (NAS) signaling across the N1 interface between the UE 105 and the AMF 215. In some other embodiments, the WLAN 216 may be directly connected to elements in the 5G CN 240 (e.g., Figure 2 215) and not via N3IWF 250. For example, direct connection of WLAN 216 to 5GCN 240 may occur when WLAN 216 is a trusted WLAN for 5GCN 240 and may use a trusted WLAN interworking function (TWIF) ( Figure 2 It should be noted that although Figure 2 Only one WLAN 216 is shown in FIG. 2 , but some embodiments may include multiple WLANs 216 .

[0045] The access node may include any of a variety of network entities that enable communication between the UE 105 and the AMF 215. As noted, this may include a gNB 210, an ng-eNB 214, a WLAN 216, and / or other types of cellular base stations. However, the access node providing the functionality described herein may additionally or alternatively include a cellular network entity that enables communication with the UE 105. Figure 2An entity that communicates with any of a variety of RATs not illustrated in the specification (which may include non-cellular technologies). Therefore, as used in the embodiments described below, the term "access node" may include but is not necessarily limited to gNB 210, ng-eNB 214, or WLAN 216.

[0046] In some embodiments, an access node (such as gNB 210, ng-eNB 214, and / or WLAN 216) (alone or in combination with other components of 5G NR positioning system 200) may be configured to: in response to receiving a request for location information from LMF 220, obtain a location measurement for an uplink (UL) signal received from UE 105 and / or obtain a DL location measurement from UE 105 for a downlink (DL) signal received by UE 105 from one or more access nodes. As noted, although Figure 2 The access nodes (gNB 210, ng-eNB 214, and WLAN 216) are depicted as being configured to communicate in accordance with 5G NR, LTE, and Wi-Fi communication protocols, respectively, but access nodes configured to communicate in accordance with other communication protocols may be used, such as, for example, a Node B using a Wideband Code Division Multiple Access (WCDMA) protocol for a Universal Mobile Telecommunications Service (UMTS) Terrestrial Radio Access Network (UTRAN), an eNB using an LTE protocol for an Evolved UTRAN (E-UTRAN), or an eNB using a Bluetooth protocol for a WLAN. For example, in a 4G Evolved Packet System (EPS) that provides LTE radio access to UE 105, the RAN may include an E-UTRAN, which may include base stations including eNBs that support LTE radio access. The core network for the EPS may include an Evolved Packet Core (EPC). The EPS may then include the E-UTRAN plus the EPC, where Figure 2 , E-UTRAN corresponds to NG-RAN 235 and EPC corresponds to 5GCN 240. The methods and techniques described herein for obtaining the municipal location of UE 105 may be applicable to such other networks.

[0047] The gNB 210 and ng-eNB 214 may communicate with the AMF 215, which communicates with the LMF 220 for positioning functionality. The AMF 215 may support mobility of the UE 105, including cell change and handover of the UE 105 from an access node of a first RAT (e.g., a gNB 210, ng-eNB 214, or WLAN 216) to an access node of a second RAT. The AMF 215 may also be involved in supporting signaling connections with the UE 105 and possibly supporting data and voice bearers for the UE 105. The LMF 220 may support positioning the UE 105 using a CP positioning solution when the UE 105 accesses the NG-RAN 235 or the WLAN 216, and may support various positioning procedures and methods, including UE-assisted / UE-based and / or network-based procedures / methods, such as Assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA) (which may be referred to as Time Difference of Arrival (TDOA) in NR), Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (ECID), Angle of Arrival (AoA), Angle of Departure (AoD), WLAN positioning, Round Trip Signal Propagation Delay (RTT), Multi-Cell RTT, and / or other positioning procedures and methods. The LMF 220 may also process a location service request for the UE 105 received, for example, from the AMF 215 or from the GMLC 225. The LMF 220 may be connected to the AMF 215 and / or the GMLC 225. In some embodiments, the network (such as 5GCN 240) may additionally or alternatively implement other types of location support modules, such as an evolved serving mobile location center (E-SMLC) or a SUPL location platform (SLP). It should be noted that in some embodiments, at least a portion of the positioning functionality (including determining the location of UE 105) may be performed at UE 105 (e.g., by measuring downlink PRS (DL-PRS) signals sent by wireless nodes (such as gNB 210, ng-eNB 214 and / or WLAN 216), and / or using assistance data provided to UE 105, for example, by LMF 220).

[0048] The Gateway Mobile Location Center (GMLC) 225 may support location requests for the UE 105 received from the external client 230, and may forward such location requests to the AMF 215 for forwarding by the AMF 215 to the LMF 220. A location response (e.g., including a location estimate for the UE 105) from the LMF 220 may similarly be returned to the GMLC 225 directly or via the AMF 215, and the GMLC 225 may then return the location response (e.g., including the location estimate) to the external client 230.

[0049] A network exposure function (NEF) 245 may be included in the 5GCN 240. The NEF 245 may support secure exposure of capabilities and events regarding the 5GCN 240 and the UE 105 to the external client 230, which may therefore be referred to as an access function (AF) and may enable secure provisioning of information from the external client 230 to the 5GCN 240. The NEF 245 may be connected to the AMF 215 and / or the GMLC 225 for obtaining the location (e.g., municipal location) of the UE 105 and providing the location to the external client 230.

[0050] like Figure 2 As further illustrated, LMF 220 may communicate with gNB 210 and / or with ng-eNB 214 using NR Positioning Protocol Annex (NRPPa) as defined in 3GPP Technical Specification (TS) 38.455. NRPPa messages may be transmitted between gNB 210 and LMF 220 and / or between ng-eNB 214 and LMF 220 via AMF 215. Figure 2 As further illustrated, the LMF 220 and the UE 105 may communicate using the LTE Positioning Protocol (LPP) as defined in 3GPP TS 37.355. Here, LPP messages may be transmitted between the UE 105 and the LMF 220 via the AMF 215 and the serving gNB 210-1 or the serving ng-eNB 214 of the UE 105. For example, the LPP messages may be transmitted between the LMF 220 and the AMF 215 using messages for service-based operations (e.g., based on the Hypertext Transfer Protocol (HTTP)), and may be transmitted between the AMF 215 and the UE 105 using the 5G NAS protocol. The LPP protocol may be used to support positioning of the UE 105 using UE-assisted and / or UE-based positioning methods such as A-GNSS, RTK, TDOA, multi-cell RTT, AoD, and / or ECID. The NRPPa protocol may be used to support positioning of UE 105 using network-based positioning methods such as ECID, AoA, uplink TDOA (UL-TDOA), and / or may be used by LMF 220 to obtain location-related information from gNB 210 and / or ng-eNB 214, such as parameters defining DL-PRS transmissions from gNB 210 and / or ng-eNB 214.

[0051] In the case where the UE 105 accesses the WLAN 216, the LMF 220 may use NRPPa and / or LPP to obtain the location of the UE 105 in a manner similar to that just described for the UE 105 accessing the gNB 210 or ng-eNB 214. Thus, NRPPa messages may be transmitted between the WLAN 216 and the LMF 220 via the AMF 215 and the N3IWF 250 to support network-based positioning of the UE 105 and / or to transmit other location information from the WLAN 216 to the LMF 220. Alternatively, NRPPa messages may be transmitted between the N3IWF 250 and the LMF 220 via the AMF 215 to support network-based positioning of the UE 105 based on location-related information and / or location measurements that are known or accessible to the N3IWF 250 and transmitted from the N3IWF 250 to the LMF 220 using NRPPa. Similarly, LPP and / or LPP messages may be transmitted between the UE 105 and the LMF 220 via the AMF 215, the N3IWF 250, and the serving WLAN 216 of the UE 105 to support UE-assisted or UE-based positioning of the UE 105 by the LMF 220.

[0052] In the 5G NR positioning system 200, positioning methods may be classified as "UE-assisted" or "UE-based". This may depend on where the request to determine the location of the UE 105 originates. For example, where the request originates from the UE (e.g., from an application or "app" executed by the UE), the positioning method may be classified as UE-based. On the other hand, where the request originates from an external client 230, LMF 220, or other device or service within the 5G network, the positioning method may be classified as UE-assisted (or "network-based").

[0053] With UE-assisted positioning methods, the UE 105 may obtain location measurements and transmit these measurements to a location server (e.g., LMF 220) for use in computing a location estimate for the UE 105. For RAT-dependent positioning methods, the location measurements may include one or more of the following for one or more access points of the gNB 210, ng-eNB 214, and / or WLAN 216: received signal strength indicator (RSSI), round trip signal propagation time (RTT), reference signal received power (RSRP), reference signal received quality (RSRQ), reference signal time difference (RSTD), time of arrival (TOA), AoA, receive time-transmit time difference (Rx-Tx), differential AoA (DAoA), AoD, or timing advance (TA). Additionally or alternatively, similar measurements may be made on sidelink signals sent by other UEs, which may be used as anchor points for positioning the UE 105 if the locations of these other UEs are known. The position measurements may additionally or alternatively include measurements for a RAT-independent positioning method, such as GNSS (eg, GNSS pseudoranges with respect to GNSS satellites 110 , GNSS code phase, and / or GNSS carrier phase), WLAN, and the like.

[0054] Using the UE-based positioning method, the UE 105 can obtain a position measurement (e.g., which can be the same or similar to the position measurement of the UE-assisted positioning method), and the position of the UE 105 can be further calculated (e.g., with the aid of auxiliary data received from a location server such as LMF 220, SLP or broadcast by gNB 210, ng-eNB 214, or WLAN 216).

[0055] Using network-based positioning methods, one or more base stations (e.g., gNB 210 and / or ng-eNB 214), one or more APs (e.g., in WLAN 216), or N3IWF 250 may obtain location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, AoA, or TOA) of signals sent by UE 105, and / or may receive measurements obtained by UE 105 or, in the case of N3IWF 250, by APs in WLAN 216, and may transmit these measurements to a location server (e.g., LMF 220) for use in calculating a position estimate for UE 105.

[0056] The positioning of UE 105 may also be classified as UL-based, DL-based, or DL-UL-based according to the type of signal used for positioning. For example, in the case where positioning is based only on signals received at UE 105 (e.g., from a base station or other UE), the positioning may be classified as DL-based. On the other hand, in the case where positioning is based only on signals sent by UE 105 (which may be received by, for example, a base station or other UE), the positioning may be classified as UL-based. DL-UL-based positioning includes positioning based on signals sent and received by UE 105, such as RTT-based positioning. Sidelink (SL)-assisted positioning includes signals communicated between UE 105 and one or more other UEs. According to some embodiments, UL, DL, or DL-UL positioning as described herein may be able to use SL signaling as a supplement or replacement for SL, DL, or DL-UL signaling.

[0057] Depending on the type of positioning (e.g., UL-based, DL-based, or DL-UL-based), the type of reference signal used may be different. For example, for DL-based positioning, these signals may include PRS (e.g., DL-PRS sent by a base station or SL-PRS sent by other UEs), which may be used for TDOA measurements, AoD measurements, and RTT measurements. Other reference signals that may be used for positioning (UL, DL, or DL-UL) may include: Sounding Reference Signal (SRS), Channel State Information Reference Signal (CSI-RS), Synchronization Signal (e.g., Synchronization Signal Block (SSB) Synchronization Signal (SS)), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Physical Sidelink Shared Channel (PSSCH), Demodulation Reference Signal (DMRS), etc. In addition, the reference signal may be sent in a Tx beam and / or received in an Rx beam (e.g., using beamforming techniques), which may affect angle measurements such as AoD and / or AoA.

[0058] FIG. 3A to FIG. 3C According to some embodiments, sidelink positioning may be used to determine the target UE 305 (e.g., Figure 1 and Figure 2 A simplified diagram of a positioning scenario of the system shown in FIG. FIG. 3A to FIG. 3C In the embodiment of the present invention, one or more anchor UEs 310 may be used to transmit and / or receive reference signals via a side link. As shown, positioning may also be determined using one or more TRPs 320 (base stations) via a corresponding Uu interface. However, it will be appreciated that the signals used for positioning of the UE 305 may vary depending on the desired functionality. More specifically, some types of positioning may utilize other than FIG. 3A to FIG. 3C Signals other than RTT / TDOA illustrated in .

[0059] Figure 3A The diagram of illustrates a configuration in which positioning of a target UE 305 may include RTT and / or TDOA measurements between the target UE 305 and three TRPs 320. In this configuration, the target UE 305 may be within the coverage of a DL and / or UL signal via a Uu connection with the TRPs 320. Additionally, an anchor UE 310 at a known location may be used to improve positioning determination of the target UE 305 by providing an additional anchor. As illustrated, ranging may be performed between the target UE 305 and the anchor UE 310 by performing RTT measurements via a sidelink connection between the target UE 305 and the anchor UE 310.

[0060] Figure 3B The diagram of illustrates a configuration in which the positioning of the target UE 305 can be sidelink-only (SL-only) positioning / ranging. In this configuration, the target UE 305 can perform RTT measurements via a sidelink connection between multiple anchor UEs 310. In this instance, the target UE 305 may not be in the UL coverage of the TRP 320, and therefore each anchor UE 310 may report RTT measurement information to the network via a Uu connection between each anchor UE 310 and the TRP 320. (In the case where the UE relays information between the remote UE and the TRP, the UE may be referred to as a "relay" UE). Such a scenario may exist when the target UE 305 has a weaker transmit power than the anchor UE 310 (for example, the target UE 305 includes a wearable device, and the anchor UE includes a larger cellular phone, an IOT device, etc.). In other scenarios where the target UE 305 is within the UL coverage of the TRP 320, the target UE 305 may report the RTT measurement directly to the TRP 320. In some embodiments, TRP 320 may not be used, in which case one of the UEs (eg, one of the target UE 305 or anchor UE 310 ) may receive the RTT measurement information and determine the location of the target UE 305 .

[0061] Figure 3C 310 and the anchor UE 310 receive a reference signal (DL-PRS) from the TRP 320 and the target UE 305 transmits a reference signal (SL-PRS) to the anchor UE 310. The positioning of the target UE may be determined based on the known positions of the TRP 320 and the anchor UE 310 and the time difference between the time when the anchor UE 310 receives the reference signal from the TRP 320 and the time when the anchor UE 310 receives the reference signal from the target UE 305.

[0062] As previously discussed, sidelink positioning (e.g., FIG. 3A to FIG. 3CAs illustrated in , only SL or Uu / SL positioning) can utilize RP-P. RP-P can be delivered to the UE via the sidelink configuration (e.g., using the techniques described below), and a specific resource pool for the sidelink reference signal can be specified in different scenarios. The resource pool includes a set of resources (e.g., frequency and time resources in an orthogonal frequency division multiplexing (OFDM) scheme used by 4G and 5G cellular technologies) that can be used to send RF signals via the sidelink for positioning. Each resource pool may also include a specific subcarrier spacing (SCS), a cyclic prefix (CP) type, a bandwidth (BW) (e.g., subcarriers, bandwidth parts, etc.), a time domain position (e.g., periodicity and time slot offset). The resource pool may include, for example, a Tx resource pool for "mode 1" sidelink positioning, where sidelink positioning is performed using one or more UEs connected to the network, in which case the UE connected to the network can receive network-based resource allocations via a Uu interface with TRP (e.g., via downlink control information (DCI) or radio resource control (RRC)). Tx resource pool for "mode 2" sidelink positioning, where autonomous resource selection is performed by the UE in the absence of network-based resource allocation. The resource pool may also include Rx resource pools, which may be used in mode 1 or mode 2 sidelink positioning. Each RP-P configuration may be relayed via a physical sidelink control channel (PSCCH), which may retain one or more SL-PRS configurations. Each of the one or more SL-PRS configurations in the RP-P may include corresponding specific physical layer features, such as the number of symbols, comb type, comb offset, number of subchannels, a certain channel size, and a starting resource block (RB). The RP-P configuration may also include sensing configuration, power control and / or channel busy rate (CBR). According to some embodiments, an abnormal RP-P may be specified and used in situations where it may not be desirable or possible to perform sidelink positioning via an available resource pool of a standard RP-P for a sidelink.

[0063] Figure 4 is a diagram showing an example of a frame structure for NR and associated terminology, which may serve as the basis for physical layer communications between a UE 105 and a base station / TRP. The transmit timeline for each of the downlink and uplink may be divided into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be divided into 10 subframes of 1 ms each with indices 0 to 9. Depending on the subcarrier spacing, each subframe may include a variable number of slots. Depending on the subcarrier spacing, each slot may include a variable number of symbol periods (e.g., 7 or 14 symbols). An index may be assigned to the symbol period in each slot. A mini slot may include a subslot structure (e.g., 2, 3, or 4 symbols). In Figure 4Additionally shown in FIG. 1 is the full orthogonal frequency division multiplexing (OFDM) of a subframe, showing how a subframe can be divided into multiple resource blocks (RBs) across both time and frequency. A single RB may include a grid of resource elements (REs) spanning 14 symbols and 12 subcarriers.

[0064] Each symbol in a slot may indicate a link direction (e.g., downlink (DL), uplink (UL), or flexible) or data transmission, and the link direction for each subframe may be switched dynamically. The link direction may be based on the slot format. Each slot may include DL / UL data and DL / UL control information. In NR, a synchronization signal (SS) block is transmitted. The SS block includes a primary SS (PSS), a secondary SS (SSS), and a two-symbol physical broadcast channel (PBCH). The SS block may be sent in a fixed slot position, such as Figure 4 Symbols 0-3 are shown. PSS and SSS can be used by UE for cell search and cell acquisition. PSS can provide half-frame timing, and SS can provide cyclic prefix (CP) length and frame timing. PSS and SSS can provide cell identity. PBCH carries some basic system information, such as downlink system bandwidth, timing information within radio frames, SS burst set period, system frame number, etc.

[0065] Figure 5 is a diagram showing an example of a radio frame sequence 500 with a PRS positioning opportunity. A "PRS instance" or "PRS opportunity" is an instance of a periodically repeating time window (e.g., a group of one or more consecutive time slots) in which a PRS is expected to be sent. A PRS opportunity may also be referred to as a "PRS positioning opportunity," "PRS positioning instance," "positioning opportunity," "positioning instance," or simply "opportunity" or "instance." The subframe sequence 500 may be applicable to broadcasting of a PRS signal (DL-PRS signal) from a base station 120 in a positioning system 100. The radio frame sequence 500 may be used in 5G NR (e.g., the 5G NR positioning system 200) and / or LTE. Similar to Figure 4 ,exist Figure 5 Time is represented horizontally (eg, on the X-axis) and time increases from left to right. Frequency is represented vertically (eg, on the Y-axis) and frequency increases (or decreases) from bottom to top.

[0066] Figure 5How PRS positioning opportunities 510-1, 510-2, and 510-3 (collectively and generally referred to herein as positioning opportunities 510) are determined by a system frame number (SFN), a cell-specific subframe offset (ΔPRS) 515, a length or span of an LPRS subframe, and a PRS periodicity (TPRS) 520 is shown. The cell-specific PRS subframe configuration may be defined by a "PRS configuration index" IPRS included in assistance data (e.g., TDOA assistance data), which may be defined by a governing 3GPP standard. The cell-specific subframe offset (ΔPRS) 515 may be defined according to the number of subframes transmitted starting from system frame number (SFN) 0 to the start of the first (subsequent) PRS positioning opportunity.

[0067] The PRS may be sent by a wireless node (e.g., a base station 120) after appropriate configuration (e.g., configuration by an operations and maintenance (O&M) server). The PRS may be sent in special positioning subframes or time slots that are grouped into positioning opportunities 510. For example, a PRS positioning opportunity 510-1 may include NPRS consecutive positioning subframes, where the number NPRS may be between 1 and 160 (e.g., may include values ​​1, 2, 4, and 6, among other values). The PRS opportunities 510 may be grouped into one or more PRS opportunity groups. As mentioned, the PRS positioning opportunities 510 may occur periodically at intervals (represented by an interval of TPRS milliseconds (or subframes)), where TPRS may be equal to 5, 10, 20, 40, 80, 160, 320, 640, or 1280 (or any other suitable value). In some embodiments, TPRS may be measured based on the number of subframes between the start of consecutive positioning opportunities.

[0068] In some embodiments, when the UE 105 receives the PRS configuration index IPRS in assistance data for a particular cell (e.g., a base station), the UE 105 can use the stored indexed data to determine the PRS periodicity TPRS 520 and the cell-specific subframe offset (ΔPRS) 515. The UE 105 can then determine the radio frame, subframe, and time slot when the PRS is scheduled in the cell. The assistance data can be provided by, for example, a location server (e.g., Figure 1 The location server 160 and / or Figure 2 The LMF 220 in the wireless node is determined and includes auxiliary data for a reference cell and several neighboring cells supported by each wireless node.

[0069] Typically, the PRS opportunities from all cells in the network that use the same frequency are aligned in time and may have a fixed known time offset (e.g., a cell-specific subframe offset (ΔPRS) 515) relative to other cells in the network that use different frequencies. In a SFN synchronous network, all wireless nodes (e.g., base stations 120) may be aligned on both frame boundaries and system frame numbers. Thus, in a SFN synchronous network, all cells supported by each wireless node may use the same PRS configuration index for any specific frequency of PRS transmission. On the other hand, in a SFN asynchronous network, each wireless node may be aligned on frame boundaries but not on system frame numbers. Thus, in a SFN asynchronous network, the PRS configuration index for each cell may be individually configured by the network so that the PRS opportunities are aligned in time. If the UE 105 can obtain the cell timing (e.g., SFN or frame number) of at least one cell (e.g., a reference cell or a serving cell), the UE 105 may determine the timing of the PRS opportunities 510 of the reference cell and the neighboring cells for TDOA positioning. The timing of other cells may then be derived by the UE 105, for example, based on an assumption that PRS opportunities from different cells overlap.

[0070] refer to Figure 4 In the frame structure of OFDM, the set of REs used to send PRS is called "PRS resources". This set of resource elements may span multiple RBs in the frequency domain and span one or more consecutive symbols within a time slot in the time domain, in which a pseudo-random quadrature phase shift keying (QPSK) sequence is sent from the antenna port of the TRP. In a given OFDM symbol in the time domain, the PRS resources occupy consecutive RBs in the frequency domain. The transmission of PRS resources within a given RB has a specific combination or "comb tooth" size. (The comb tooth size may also be referred to as "comb tooth density"). The comb tooth size "N" represents the subcarrier spacing (or frequency / frequency modulation spacing) within each symbol of the PRS resource configuration, where the configuration uses every Nth subcarrier of a specific symbol of the RB. For example, for comb tooth -4, for each of the four symbols of the PRS resource configuration, the RE corresponding to every fourth subcarrier (e.g., subcarriers 0, 4, 8) is used to send the PRS of the PRS resource. Comb tooth sizes such as comb tooth -2, comb tooth -4, comb tooth -6, and comb tooth -12 may be used in PRS. In Figure 6 Examples of different comb sizes using different numbers of symbols are provided in .

[0071] A "PRS resource set" includes a group of PRS resources for the transmission of a PRS signal, wherein each PRS resource has a PRS resource ID. In addition, the PRS resources in the PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and is associated with a specific TRP (identified by a cell ID). "PRS resource repetition" is a repetition of a PRS resource during a PRS opportunity / instance. The number of repetitions of a PRS resource may be defined by a "repetition factor" for a PRS resource. In addition, the PRS resources in the PRS resource set have the same periodicity, a common silent mode configuration, and the same cross-slot repetition factor. The periodicity may have a length selected from the following: 2m×{4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} time slots, where μ=0, 1, 2, 3. The repetition factor may have a length selected from {1, 2, 4, 6, 8, 16, 32} slots.

[0072] A PRS resource ID in a PRS resource set may be associated with a single beam (and / or beam ID) transmitted from a single TRP (wherein a TRP may transmit one or more beams). That is, each PRS resource in a PRS resource set may be transmitted on a different beam, and thus, a PRS resource (or simply "resource") may also be referred to as a "beam". Note that this does not have any implication on whether the UE knows the TRP and beam on which the PRS is transmitted.

[0073] exist Figure 2 In the illustrated 5G NR positioning system 200, the TRP (gNB 210, ng-eNB 214 and / or WLAN 216) may transmit frames or other physical layer signaling sequences supporting PRS signals (i.e., DL PRS) according to the frame configuration as described above, which may be measured and used for positioning determination of UE 105. As mentioned, other types of radio network nodes (including other UEs) may also be configured to transmit PRS signals configured in a manner similar (or the same) as described above. Because the transmission of PRS by a radio network node may be directed to all UEs within radio range, the radio network node may be considered to transmit (or broadcast) PRS.

[0074] Figure 7 is a diagram showing an example of a side chain resource pool 700. Figure 7 In the example of , time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one OFDM symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is one subchannel.

[0075] exist Figure 7In the example of , the entire time slot (except the first symbol and the last symbol) can be a resource pool for side link transmission and / or reception. That is, any symbol except the first symbol and the last symbol can be allocated for transmission and / or reception. However, the RP-P for side link transmission / reception is allocated in the last eight front slot symbols of the time slot. Therefore, non-side link positioning data (such as user data, CSI-RS, and control information) can be sent only in the first four post-AGC symbols, but not in the last eight front slot symbols to prevent conflict with the configured RP-P. The non-side link positioning data that would have been sent in the last eight front slot symbols can be truncated or silenced, and / or the non-side link data that would normally span more than four post-AGC symbols can be rate matched to accommodate the four post-AGC symbols.

[0076] A Sidelink Positioning Reference Signal (SL-PRS) has been defined to support sidelink positioning procedures between UEs. Just like PRS and SRS, a SL-PRS resource consists of one or more resource elements (i.e., one OFDM symbol in the time domain and one subcarrier in the frequency domain). The SL-PRS resources may be designed to have a comb-based pattern to enable Fast Fourier Transform (FFT) based processing at the receiver. The SL-PRS resources may consist of uninterleaved or only partially interleaved resource elements in the frequency domain to provide small time of arrival (TOA) uncertainty for each SL-PRS resource and reduced overhead. Figure 7 In the example of FIG. 4 , as shown in the figure, four SL-PRS resources (labeled as SL-PRS1, SL-PRS2, SL-PRS 3, SL-PRS 4) are sent in RP-P (or are scheduled for sending in RP-P). Note that although Figure 7 The SL-PRS are illustrated as being continuous in the frequency domain, but they may alternatively follow a comb pattern within a subchannel.

[0077] The SL-PRS may be associated with a specific RP-P (eg, certain SL-PRS may be allocated in certain RP-Ps). The SL-PRS may be configured to have a repetition feature within a time slot ( Figure 7 ), to allow combining gain (if required). Inter-UE coordination of RP-P may be performed to provide dynamic SL-PRS and data multiplexing while minimizing SL-PRS collisions.

[0078] Figure 88 is a block diagram of an operating environment 800 in which the techniques disclosed herein for adapting sidelink positioning in channel load management may be implemented. In operating environment 800, UE 805 may wirelessly communicate with one or more sidelink nodes 825 using sidelink resources 810. Sidelink nodes 825 may include other UEs with sidelink capabilities and / or other types of devices capable of sidelink communications. Sidelink resources 810 may include sidelink resource pools 815 and sidelink resource pools 820. Sidelink resource pools 815 (which may be similar to Figure 7 The side link resource pool 700 includes SL-PRS resources 818. The side link resource pool 820 does not include SL-PRS resources.

[0079] In order to detect and alleviate sidelink congestion in the operating environment 800, the UE 805 may perform sidelink channel busy rate (SL CBR) and sidelink channel occupancy rate (SL CR) measurements. The SL CBR (or simply CBR) may be used by the UE and other network entities (if reported) to manage channel load and, if necessary, adapt resources dedicated to the sidelink. The CBR measurement may provide an indication of congestion on the medium. The CBR measured in time slot n may be defined as the portion of the subchannel in the resource pool for which the sidelink received signal strength indication (SL-RSSI) measured by the UE exceeds a (pre) configured threshold sensed within the CBR measurement window [na, n-1], where a is equal to 100 or 100·2μ time slots, and μ is a parameter set that acts on the resource pool in question (and defines the subcarrier spacing of the resource pool). The SL CR (or simply CR) evaluated at time slot n can be defined as the total number of subchannels used by the UE for transmission in time slot [na,n-1] and granted in time slot [n,n+b] divided by the total number of configured subchannels in the transmission pool within [na,n+b], where a is a positive integer, b is a non-negative integer, and a+b+1=1000 or 1000*2μ time slots.

[0080] UE 805 may implement a congestion control mechanism according to which it controls its utilization of SL resources 810 to satisfy constraints on its use of those resources. Relative to the transmission of sidelink data of a given priority level k on a given sidelink resource pool during time slot n, UE 805 may control its utilization of the sidelink resource pool to ensure that the sum of its CRs for priorities less than or equal to k evaluated at time slot nN is less than or equal to a CR limit, where N represents the congestion control processing time. The CR limit may depend on the priority level k and the CBR value measured by UE 805 for time slot nN. UE 805 may measure the CBR of the sidelink resource pool for time slot nN, for a given priority level k, identify a CR limit corresponding to a CBR range that includes the measured CBR, and control its utilization of the sidelink resource pool during time slot n to observe the CR limit.

[0081] The congestion control handling capability of the UE 805 may specify a congestion control handling time value set, which includes N values ​​to be applied to various μ values. The UE 805 may apply different values ​​of the congestion control handling time N according to the applicable parameter set value μ. When performing congestion control with respect to a specific side link resource pool, the UE 805 may identify an applicable μ value with respect to the side link resource pool, identify an N value corresponding to the μ value according to the congestion control handling capability of the UE 805, and apply the N value in conjunction with congestion control of the side link resource pool.

[0082] The congestion control processing time (the value of N) observed by UE 805 for a sidelink resource pool that does not include SL-PRS resources (e.g., sidelink resource pool 820) may not be suitable for use in conjunction with congestion control for a sidelink resource pool that includes SL-PRS resources (e.g., sidelink resource pool 815). Factors that may contribute to a suboptimal "non-SL-PRS" congestion control processing time for a sidelink resource pool that includes SL-PRS resources may include the possibility that the SL-PRS resources occupy a larger bandwidth than the sidelink data resources, and that multiple UEs may be operating during the same symbol (e.g., using code orthogonality or other features such as Figure 6 The possibility of sending SL-PRS (with the comb structure shown).

[0083] In order to improve the results of congestion control in conjunction with congestion control of a side link resource pool that includes SL-PRS resources (such as, side link resource pool 815), UE 805 may be configured to identify / implement a different set of congestion control processing time values ​​for such side link resource pool, rather than a set of congestion control processing time values ​​for a side link resource pool that does not include SL-PRS resources.

[0084] In some implementations, the UE 805 may be configured to identify / implement SL-PRS congestion control handling capabilities that are different from the congestion control handling capabilities identified / implemented by the UE 805 in conjunction with congestion control for a sidelink resource pool that does not include SL-PRS resources. In such implementations, for a sidelink resource pool that includes SL-PRS resources (e.g., sidelink resource pool 815), the SL-PRS congestion control handling capabilities may specify a different set of congestion control handling time values ​​than that governing congestion control for a sidelink resource pool that does not include SL-PRS resources (e.g., sidelink resource pool 820).

[0085] In an implementation where the UE 805 is configured to identify / implement different SL-PRS congestion control handling capabilities, the UE 805 may report the SL-PRS congestion control handling capabilities to other devices (e.g., ng-eNB or gNB, other UEs) by sending a capability message 830 indicating the SL-PRS congestion control handling capabilities of the UE 805. In some implementations, the capability message 830 may include an information element (IE) 832 indicating the SL-PRS congestion control handling capabilities of the UE 805.

[0086] In some implementations, the UE 805 may also report the congestion control handling capability of the UE 805 with respect to a sidelink resource pool that does not include SL-PRS resources (e.g., the sidelink resource pool 820) using the capability message 830. In some implementations, in addition to indicating the SL-PRS congestion control handling capability of the UE 805, the IE 832 may also indicate the congestion control handling capability of the UE 805 with respect to the sidelink resource pool that does not include SL-PRS resources. In some other implementations, the capability message 830 may include a different IE 833 that indicates the congestion control handling capability of the UE 805 with respect to the sidelink resource pool that does not include SL-PRS resources.

[0087] In some implementations, the UE 805 may determine an applicable congestion control handling time value for congestion control of the sidelink resource pool 815 based on the SL-PRS congestion control handling capability of the UE 805. This may involve identifying a set of congestion control handling time values ​​corresponding to the SL-PRS congestion control handling capability of the UE 805, and identifying a value in the set of congestion control handling time values ​​as the applicable congestion control handling time value (e.g., based on the subcarrier spacing of the sidelink resource pool 815).

[0088] In some implementations, different SL-PRS congestion control handling time value sets may be explicitly defined and associated with various possible SL-PRS congestion control handling capabilities. In some such implementations, the UE 805 may identify a SL-PRS congestion control handling time value set corresponding to the SL-PRS congestion control handling capabilities of the UE 805, and may identify a value in the SL-PRS congestion control handling time value set as an applicable congestion control handling time value for congestion control of the sidelink resource pool 815. In some implementations, the explicitly defined SL-PRS congestion control handling time value sets may include some value sets applied in sidelink mode 1 and other different value sets applied in sidelink mode 2.

[0089] In some implementations, the congestion control handling capabilities of the UE 805 for congestion control of a sidelink resource pool that does not include SL-PRS resources may serve as a common congestion control handling capabilities that also constitute the SL-PRS congestion control handling capabilities of the UE 805. In some such implementations, different sets of SL-PRS congestion control handling time values ​​may be explicitly defined and associated with various possible common congestion control handling capabilities. In some implementations, the capability message 830 may indicate (e.g., using IE 832) such common congestion control handling capabilities of the UE 805. In some implementations, based on the common congestion control handling capabilities indicated by the capability message 830, the UE 805 may identify both the applicable SL-PRS congestion control handling time value set and the applicable congestion control handling time value set for congestion control of a sidelink resource pool that does not include SL-PRS resources.

[0090] In some implementations where a common congestion control handling capability is implemented, different sets of SL-PRS congestion control handling time values ​​may not be explicitly defined. In some such implementations, a scheme may be defined according to which the SL-PRS congestion control handling time value is determined as a function of the congestion control handling time value of a sidelink resource pool that does not include SL-PRS resources. Such a scheme may specify a modification factor according to which the values ​​in the set of non-SL-PRS congestion control handling time values ​​are to be modified in order to determine the SL-PRS congestion control handling time value. Such modification factors may generally define the modifications to be made to the non-SL-PRS congestion control handling time value based on the characteristics of the SL-PRS resource allocation / distribution. Such characteristics may include, for example, the ratio between the SL-PRS resource pool bandwidth and the SL data resource pool bandwidth, the number of SL-PRS resources configured per SL-PRS instance, the SL-PRS repetition factor, and / or the comb / symbol structure of the SL-PRS transmission.

[0091] In some implementations, according to this scheme, the UE 805 may determine an applicable congestion control processing time value for congestion control of the side link resource pool 815 based on the non-SL-PRS congestion control processing time value set. In some implementations, the UE 805 may modify the values ​​in the non-SL-PRS congestion control processing time value set according to one or more modification factors to determine the applicable congestion control processing time value for congestion control of the side link resource pool 815. In an example implementation, the UE 805 may scale the values ​​in the non-SL-PRS congestion control processing time value set based on a ratio between a bandwidth of the side link resource pool 815 and a bandwidth of the side link resource pool 820 to determine the applicable congestion control processing time value for congestion control of the side link resource pool 815.

[0092] In some implementations, the UE 805 may be configured to identify / implement a sidelink congestion control SL-PRS resource handling capability. In some implementations, associated with the sidelink congestion control SL-PRS resource handling capability may be a limit on the number of SL-PRS resources to be processed within a given amount of time (e.g., a time slot or number of time slots) in conjunction with congestion control of a sidelink resource pool (e.g., sidelink resource pool 815) that includes SL-PRS resources. If the number of SL-PRS resources in the sidelink resource pool in question exceeds the maximum number to be processed within the relevant time interval, once the UE 805 has processed a number of SL-PRS resources equal to the limit, the UE may ignore the remaining SL-PRS resources for the purpose of CBR and CR determination. In some implementations, the capability message 830 may indicate the sidelink congestion control SL-PRS resource handling capability of the UE 805.

[0093] In some implementations, the UE 805 may be configured to also identify / implement a general SL-PRS resource processing capability that indicates the maximum number of SL-PRS resources that the UE 805 can typically process within a given amount of time (e.g., a time slot or number of time slots). In some implementations, the limit imposed by the sidelink congestion control SL-PRS resource processing capability on the number of SL-PRS resources to be processed in conjunction with congestion control may be defined as a function of the total limit indicated by the general SL-PRS resource processing capability. In some implementations, for example, the limit imposed by the sidelink congestion control SL-PRS resource processing capability may be defined as equal to the total limit indicated by the general SL-PRS resource processing capability multiplied by a scaling factor. In some implementations, the capability message 830 may indicate the general SL-PRS resource processing capability of the UE 805. In some implementations, the capability message 830 may indicate both the general SL-PRS resource processing capability of the UE 805 and the sidelink congestion control SL-PRS resource processing capability of the UE 805.

[0094] In some implementations, the UE 805 may be configured to recognize a SL-PRS resource processing capability limit expressed in the form of a parameter value pair [D, T]. In some implementations, based on a specified parameter value pair [D, T], the UE 805 may recognize a duration D (in ms) of a SL-PRS symbol that the UE 805 may process per Tms.

[0095] In some implementations, the UE 805 may be configured to identify / implement a sidelink congestion control SL-PRS resource handling capability that indicates a value pair [D, T] applicable for sidelink congestion control. In some implementations, the UE 805 may be configured to identify the sidelink congestion control SL-PRS resource handling capability as indicating a duration D (in ms) of a SL-PRS symbol that the UE 805 may process per Tms in conjunction with sidelink congestion control.

[0096] In some implementations, the UE 805 may also be configured to identify / implement a general SL-PRS resource processing capability indicating a value pair [D, T] defining a SL-PRS resource processing capability limit that is not specific to the context of sidelink congestion control. In some implementations, the UE 805 may be configured to identify the general SL-PRS resource processing capability as indicating the duration D (in ms) of a SL-PRS symbol that the UE 805 can typically process every Tms.

[0097] In some implementations, a general set of allowed value pairs [D, T] may be defined, and the general SL-PRS resource handling capability may indicate one of the allowed value pairs [D, T] in the general set. In some implementations, the general set of allowed value pairs [D, T] may also serve as the set of allowed value pairs [D, T] for sidelink congestion control, and the sidelink congestion control SL-PRS resource handling capability may indicate one of the allowed value pairs [D, T] in the general set. In some other implementations, a different set of allowed value pairs [D, T] may be defined for sidelink congestion control, and the sidelink congestion control SL-PRS resource handling capability may indicate one of the allowed value pairs [D, T] in the different set.

[0098] In some implementations, the UE 805 may be configured to identify / implement SL-PRS buffering capabilities. In some implementations, the SL-PRS buffering capabilities may indicate the granularity of the SL-PRS buffering. In some implementations, the SL-PRS buffering capabilities may be set to a value to indicate slot-level SL-PRS buffering, or may be set to another value to indicate sub-slot / symbol-level buffering. In some implementations, the capability message 830 may indicate the SL-PRS buffering capabilities of the UE 805. In some implementations, the UE 805 may also be configured to identify / implement a DL-PRS buffering capability indicating the granularity of the DL-PRS buffering (e.g., slot-level or sub-slot / symbol-level), and the capability message 830 may indicate both the DL-PRS buffering capabilities of the UE 805 and the SL-PRS buffering capabilities of the UE 805.

[0099] Fig. 9 is a flow chart of a method 900 for wireless communication by a UE according to various aspects of the present disclosure. Fig. 9 Means of functionality illustrated in one or more of the illustrated blocks may be performed by hardware and / or software components of the UE. Fig.10 Example components of a UE are illustrated in FIG. 4 , and are described in more detail below.

[0100] At block 910, the functionality includes sending a message indicating the UE's sidelink positioning reference signal (SL-PRS) congestion control handling capability. Figure 8 In the operating environment 800, the UE 805 can send a capability message 830, which can indicate the SL-PRS congestion control processing capability of the UE 805.

[0101] In some implementations, the message sent at block 910 may include an IE (e.g., Figure 8 832), which indicates the congestion control handling capability that constitutes the SL-PRS congestion control handling capability of the UE. In some such specific implementations, the message may also include a second IE (e.g., Figure 8 IE 833), the second IE indicating the SL resource pool (for example, Figure 8 In some implementations, the message may include an IE (e.g., Figure 8 IE 832), which indicates the SL-PRS congestion control handling capability of the UE and the SL resource pool (e.g., Figure 8 The congestion control processing capacity of the congestion control of the SL resource pool 820) is the common congestion control processing capacity of the two.

[0102] In some implementations, the message sent at block 910 may indicate the sidelink congestion control SL-PRS resource handling capability of the UE. In some implementations, the sidelink congestion control SL-PRS resource handling capability may be combined with a sidelink resource pool including SL-PRS resources (e.g., Figure 8 The sidelink congestion control SL-PRS resource handling capability may specify a parameter value pair [D, T], and the UE may be configured to identify the sidelink congestion control SL-PRS resource handling capability as indicating the duration D (in ms) of the SL-PRS symbol that the UE can process per Tms in conjunction with the sidelink congestion control.

[0103] In some implementations, the message sent at block 910 may indicate the SL-PRS buffering capability of the UE. In some implementations, the SL-PRS buffering capability may indicate the granularity of the SL-PRS buffering. In some implementations, the SL-PRS buffering capability may be set to a value to indicate slot-level SL-PRS buffering, or may be set to another value to indicate sub-slot / symbol-level buffering.

[0104] Means for performing the functionality at block 910 may include a bus 1005, a processor 1010, a digital signal processor (DSP) 1020, a wireless communication interface 1030, a memory 1060, and / or other components of the UE, as described in more detail below. Fig.10 exemplified in .

[0105] At block 920, the functionality includes determining an applicable congestion control processing time value for congestion control of a sidelink (SL) resource pool including SL-PRS resources based on the SL-PRS congestion control processing capability of the UE. Figure 8 In the operating environment 800, the UE 805 can determine the applicable congestion control processing time value for congestion control of the SL resource pool 815 according to the SL-PRS congestion control processing capability of the UE 805.

[0106] In some implementations, a SL resource pool (eg, Figure 8 In some implementations, the values ​​in the set of congestion control handling time values ​​corresponding to the SL-PRS congestion control handling capability of the UE may be based on the SL resource pool (e.g., Figure 8The subcarrier spacing (or associated parameter set value μ) of the SL resource pool 815) is identified as the applicable congestion control processing time value.

[0107] In some implementations, the message sent at block 910 may include an IE (e.g., Figure 8 IE 833), which indicates the SL resource pool (for example, Figure 8 The congestion control processing capability of the congestion control of the SL resource pool 820) may be determined, and the applicable congestion control processing time value for congestion control of the SL resource pool may be determined based on the congestion control processing capability.

[0108] In some implementations, the message sent at block 910 may include an IE (e.g., Figure 8 832), which indicates a common congestion control handling capability as described above, and the functionality at block 920 may include determining a SL resource pool (e.g., Figure 8 The applicable congestion control processing time value for congestion control of the SL resource pool 815 of the SL resource pool 815) and the applicable congestion control processing time value for the SL resource pool that does not include SL-PRS resources (e.g., Figure 8 In some such implementations, the SL resource pool (e.g., SL resource pool 820) that does not include SL-PRS resources may be modified according to one or more modification factors. Figure 8 The applicable congestion control processing time value of the congestion control of the SL resource pool 820) is used to determine the SL resource pool (e.g., Figure 8 In some implementations, the applicable congestion control processing time value for congestion control of the SL resource pool 815 that does not include SL-PRS resources (e.g., Figure 8 Such modification of the applicable congestion control processing time value for congestion control of the SL resource pool 820) may include scaling the applicable congestion control processing time value based on a ratio between a bandwidth of the SL resource pool that includes SL-PRS resources and a bandwidth of the SL resource pool that does not include SL-PRS resources (e.g., a ratio between the bandwidth of SL resource pool 815 and the bandwidth of SL resource pool 820).

[0109] Means for performing the functionality at block 920 may include a bus 1005, a processor 1010, a digital signal processor (DSP) 1020, a wireless communication interface 1030, a memory 1060, and / or other components of the UE, as described in more detail below. Fig.10 exemplified in .

[0110] At block 930, the functionality includes measuring a channel busy rate (CBR) of a SL resource pool including SL-PRS resources of a first time slot. Figure 8 In the operating environment 800 of , the UE 805 can measure the CBR of the SL resource pool 815 in time slot nN, where N represents the applicable congestion control processing time value determined at block 920.

[0111] Means for performing the functionality at block 930 may include bus 1005, processor 1010, digital signal processor (DSP) 1020, wireless communication interface 1030, memory 1060, and / or other components of the UE, as described in more detail below. Fig.10 exemplified in .

[0112] At block 940, the functionality includes selecting a resource of the SL resource pool for the UE to communicate during a second time slot based on the measured CBR, wherein the second time slot is offset in time from the first time slot by an applicable congestion control processing time value. Figure 8 In the operating environment 800 of , UE 805 may select resources of SL resource pool 815 for communication during time slot n based on the CBR measured for time slot nN. In some implementations, resource selection of the SL resource pool may be performed to ensure that for each possible value of k, the sum of the CRs of UEs with a priority less than or equal to priority k evaluated at time slot nN is less than or equal to a CR limit. In some implementations, as previously described, the CR limit may vary depending on the value of k and the CBR measured at block 930.

[0113] Means for performing the functionality at block 940 may include bus 1005, processor 1010, digital signal processor (DSP) 1020, wireless communication interface 1030, memory 1060, and / or other components of the UE, as described in more detail below. Fig.10 exemplified in .

[0114] At block 950, the functionality includes communicating using the selected resource during the second time slot. Figure 8 In the operating environment 800, the UE 805 can communicate during time slot n using the resources of the SL resource pool 815 selected at box 940.

[0115] Means for performing the functionality at block 950 may include a bus 1005, a processor 1010, a digital signal processor (DSP) 1020, a wireless communication interface 1030, a memory 1060, and / or other components of the UE, as described in more detail below. Fig.10 exemplified in .

[0116] Fig.10is as described above (for example, in conjunction with Figure 1 To Figure 3 and Figures 8 to 9 ) is a block diagram of an implementation of the UE 105 being utilized. For example, the UE 105 may execute Fig. 9 One or more of the functions of the method shown. It should be noted that Fig.10 It is intended only to provide a generalized illustration of various components, any or all of which may be utilized as appropriate. It may be noted that in some cases, Fig.10 The illustrated components may be localized as a single physical device and / or distributed among various networked devices that may be located at different physical locations. In addition, as previously noted, the functionality of the UE discussed in the previously described embodiments may be provided by Fig.10 The invention may be executed by one or more of the illustrated hardware and / or software components.

[0117] UE 105 is shown as including hardware elements that may be electrically coupled via bus 1005 (or may communicate in other ways as appropriate). The hardware elements may include a processor 1010, which may include, but is not limited to, one or more general-purpose processors (e.g., application processors), one or more special-purpose processors (such as digital signal processor (DSP) chips, graphics acceleration processors, application-specific integrated circuits (ASICs), etc.), and / or other processing structures or components. Processor 1010 may include one or more processing units, which may be housed in a single integrated circuit (IC) or multiple ICs. Fig.10 As shown, some embodiments may have a separate DSP 1020, depending on the desired functionality. Position determination and / or other determinations based on wireless communication (discussed below) may be provided in the processor 1010 and / or the wireless communication interface 1030. The UE 105 may also include one or more input devices 1070, which may include but are not limited to one or more keyboards, touch screens, touch pads, microphones, buttons, dials, switches, etc.; and one or more output devices 1015, which may include but are not limited to one or more displays (e.g., touch screens), light emitting diodes (LEDs), speakers, etc.

[0118] UE 105 may also include a wireless communication interface 1030, which may include but is not limited to a modem, a network card, an infrared communication device, a wireless communication device and / or a chipset (such as Device, IEEE 802.11 device, IEEE 802.15.4 device, Wi-Fi device, WiMAX device, WAN device and / or various cellular devices, etc.), etc., the wireless communication interface may enable UE 105 to communicate with other devices as described in the above embodiments. The wireless communication interface 1030 may allow the TRP of the network to communicate (e.g., send and receive) data and signaling, such as via eNB, gNB, ng-eNB, access point, various base stations and / or other access node types, and / or other network components, computer systems, and / or any other electronic device communicatively coupled to the TRP, as described herein. Communication may be performed via one or more wireless communication antennas 1032 that send and / or receive wireless signals 1034. According to some embodiments, the wireless communication antenna 1032 may include multiple discrete antennas, antenna arrays, or any combination thereof. The antenna 1032 may be capable of using beams (e.g., Tx beams and Rx beams) to send and receive wireless signals. Beamforming may be performed using digital and / or analog beamforming techniques with corresponding digital and / or analog circuitry. Wireless communication interface 1030 may include such circuitry.

[0119] Depending on the desired functionality, the wireless communication interface 1030 may include separate receivers and transmitters, or any combination of transceivers, transmitters, and / or receivers to communicate with base stations (e.g., ng-eNBs and gNBs) and other terrestrial transceivers (such as wireless devices and access points). The UE 105 may communicate with different data networks, which may include various network types. For example, the WWAN may be a CDMA network, a time division multiple access (TDMA) network, a frequency division multiple access (FDMA) network, an orthogonal frequency division multiple access (OFDMA) network, a single carrier frequency division multiple access (SC-FDMA) network, a WiMAX (IEEE 802.16) network, etc. A CDMA network may implement one or more RATs, such as WCDMA, etc. Includes IS-95, IS-2000, and / or IS-856 standards. A TDMA network may implement GSM, Digital Advanced Mobile Phone System (D-AMPS), or some other RAT. An OFDMA network may employ LTE, Advanced LTE, 5G NR, and the like. 5G NR, LTE, Advanced LTE, GSM, and WCDMA are described in documents from 3GPP. Described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). 3GPP and 3GPP2 documents are publicly available. A wireless local area network (WLAN) may also be an IEEE 802.11x network, while a wireless personal area network (WPAN) may be a Bluetooth network, IEEE 802.15x, or some other type of network. The techniques described herein may also be used for any combination of WWAN, WLAN, and / or WPAN.

[0120] The UE 105 may also include sensors 1040. The sensors 1040 may include, but are not limited to, one or more inertial sensors and / or other sensors (e.g., accelerometers, gyroscopes, cameras, magnetometers, altimeters, microphones, proximity sensors, light sensors, barometers, etc.), some of which may be used to obtain location-related measurements and / or other information.

[0121] Embodiments of UE 105 may also include a global navigation satellite system (GNSS) receiver 1080 that is capable of receiving signals 1084 from one or more GNSS satellites using antenna 1082 (which may be the same as antenna 1032). Positioning based on GNSS signal measurements may be used to supplement and / or incorporate the techniques described herein. GNSS receiver 1080 may extract the location of UE 105 using conventional techniques from GNSS satellites of GNSS systems such as Global Positioning System (GPS), Galileo, GLONASS, Quasi-Zenith Satellite System (QZSS) covering Japan, IRNSS covering India, BeiDou Navigation Satellite System (BDS) covering China, etc. In addition, the GNSS receiver 1080 may be used with various augmentation systems, such as, for example, a satellite-based augmentation system (SBAS), which may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems, such as, for example, the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multifunction Satellite Augmentation System (MSAS), and the Geographic Augmentation Navigation System (GAGAN), among others.

[0122] It may be pointed out that although Fig.101080 is illustrated as a different component, but the embodiments are not limited thereto. As used herein, the term "GNSS receiver" may include hardware and / or software components configured to obtain GNSS measurements (measurements from GNSS satellites). Therefore, in some embodiments, the GNSS receiver may include (as software) a measurement engine executed by one or more processors, such as processor 1010, DSP 1020, and / or a processor within wireless communication interface 1030 (e.g., in a modem). The GNSS receiver may also optionally include a positioning engine that can use the GNSS measurements from the measurement engine to determine the position of the GNSS receiver using an extended Kalman filter (EKF), a weighted least squares method (WLS), a hatch filter, a particle filter, etc. The positioning engine may also be executed by one or more processors, such as processor 1010 or DSP 1020.

[0123] The UE 105 may also include and / or be in communication with memory 1060. The memory 1060 may include, but is not limited to, local and / or network accessible storage, disk drives, drive arrays, optical storage devices, solid-state storage devices such as random access memory (RAM) and / or read-only memory (ROM), which may be programmable, flash-updatable, etc. Such storage devices may be configured to implement any suitable data storage, including, but not limited to, various file systems, database structures, etc.

[0124] The memory 1060 of the UE 105 may also include software elements ( Fig.10 105), including an operating system, device drivers, executable libraries, and / or other code (such as one or more applications), which software elements may include computer programs provided by various embodiments, and / or may be designed to implement methods provided by other embodiments and / or configure systems provided by other embodiments, as described herein. By way of example only, one or more procedures described with respect to the methods discussed above may be implemented as code and / or instructions in memory 1060 that can be executed by UE 105 (and / or processor 1010 or DSP 1020 within UE 105). Then, in some embodiments, such code and / or instructions may be used to configure and / or adapt a general purpose computer (or other device) to perform one or more operations according to the described methods.

[0125] With reference to the accompanying drawings, components that may include memory may include non-transient machine-readable media. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any storage medium that participates in providing data that enables a machine to operate in a particular manner. In the embodiments provided above, various machine-readable media may be involved when providing instructions / codes to a processor and / or other devices for execution. Additionally or alternatively, machine-readable media may be used to store and / or carry such instructions / codes. In many specific implementations, computer-readable media are physical and / or tangible storage media. Such media may take many forms, including but not limited to non-volatile media and volatile media. Common forms of computer-readable media include, for example: magnetic and / or optical media, any other physical media with hole patterns, RAM, programmable ROM (PROM), erasable PROM (EPROM), FLASH-EPROM, any other memory chip or memory box, or any other medium from which a computer can read instructions and / or codes.

[0126] The methods, systems and devices discussed herein are examples. Various embodiments may omit, replace or add various procedures or components as appropriate. For example, the features described in certain embodiments may be combined in various other embodiments. Different aspects and elements of the embodiments may be combined in a similar manner. The various components of the drawings provided herein may be embodied in hardware and / or software. In addition, technology may evolve, and therefore many elements are examples, which do not limit the scope of the present disclosure to those specific examples.

[0127] It has proven convenient at times, primarily for reasons of common usage, to refer to such signals as bits, information, values, elements, symbols, characters, variables, terms, numbers, digital symbols, and the like. However, it should be understood that all of these or similar terms are to be associated with the appropriate physical quantities and are merely convenient labels. Unless otherwise specifically stated, as will be apparent from the above discussion, it should be understood that throughout this specification, discussions utilizing terms such as "processing," "computing," "calculating," "determining," "ascertaining," "identifying," "correlating," "measuring," "performing," and the like refer to the actions or processes of a particular device such as a special-purpose computer or similar special-purpose electronic computing device. Thus, in the context of this specification, a special-purpose computer or similar special-purpose electronic computing device is capable of manipulating or transforming signals, typically represented as physical, electronic, electrical, or magnetic quantities in a memory, register, or other information storage device, a transmitting device, or a display device of the special-purpose computer or similar special-purpose electronic computing device.

[0128] As used herein, the terms "and" and "or" may include multiple meanings that are also intended to depend at least in part on the context in which such terms are used. Generally, "or", if used in association with a list, such as A, B, or C, is intended to mean A, B, and C (inclusive meanings are used here) as well as A, B, or C (exclusive meanings are used here). In addition, as used herein, the term "one or more" may be used to describe any feature, structure, or characteristic in the singular form, or may be used to describe a certain combination of features, structures, or characteristics. However, it should be noted that this is merely an illustrative example, and the subject matter claimed is not limited to this example. In addition, the term "at least one of...", if used in association with a list, such as A, B, or C, may be interpreted to mean any combination of A, B, and / or C, such as A, AB, AA, AAB, AABBCCC, etc.

[0129] Several embodiments have been described, and various modifications, alternative configurations, and equivalents may be used without departing from the scope of the present disclosure. For example, the above elements may be components of a larger system, wherein other rules may take precedence over the application of the various embodiments or otherwise modify the application of the various embodiments. In addition, multiple steps may be performed before, during, or after considering the above elements. Accordingly, the above description does not limit the scope of the present disclosure.

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

[0131] Clause 1. A method for wireless communication by a user equipment (UE), the method comprising: sending a message indicating a sidelink positioning reference signal (SL-PRS) congestion control processing capability of the UE; determining an applicable congestion control processing time value for congestion control of a first side link (SL) resource pool based on the SL-PRS congestion control processing capability of the UE, the first SL resource pool comprising SL-PRS resources; measuring a channel busy rate (CBR) of the first SL resource pool for a first time slot; selecting resources of the first SL resource pool based on the measured CBR for use in communication during a second time slot, wherein the second time slot is offset in time from the first time slot by the applicable congestion control processing time value; and communicating using the selected resources during the second time slot.

[0132] Clause 2. The method of clause 1, wherein the applicable congestion control handling time value is determined based on a set of congestion control handling time values ​​corresponding to the SL-PRS congestion control handling capability of the UE.

[0133] Clause 3. The method according to Clause 2 includes: identifying a value in the congestion control processing time value set as the applicable congestion control processing time value based on the subcarrier spacing of the first SL resource pool.

[0134] Clause 4. A method according to any one of clauses 1 to 3, wherein the message comprises: a first information element, the first information element indicating a first congestion control processing capability constituting the SL-PRS congestion control processing capability of the UE; and a second information element, the second information element indicating a second congestion control processing capability constituting the congestion control processing capability of the UE for congestion control of a second SL resource pool, the second SL resource pool not including SL-PRS resources.

[0135] Clause 5. The method according to Clause 4 comprises: determining an applicable congestion control processing time value for congestion control of the second SL resource pool according to the second congestion control processing capability.

[0136] Clause 6. A method according to any one of clauses 1 to 3, wherein the message includes an information element indicating a common congestion control handling capability of both the SL-PRS congestion control handling capability constituting the UE and the congestion control handling capability of the UE for congestion control of a second SL resource pool, the second SL resource pool not including SL-PRS resources.

[0137] Clause 7. The method according to Clause 6 comprises: determining, based on the common congestion control processing capability: a first congestion control processing time value, the first congestion control processing time value constituting an applicable congestion control processing time value for congestion control of the first SL resource pool; and a second congestion control processing time value, the second congestion control processing time value constituting an applicable congestion control processing time value for congestion control of the second SL resource pool.

[0138] Clause 8. The method of clause 7, comprising: modifying the second congestion control handling time value according to one or more modification factors to determine the first congestion control handling time value.

[0139] Clause 9. A method according to Clause 8, wherein modifying the second congestion control processing time value according to the one or more modification factors includes scaling the second congestion control processing time value based on a ratio between a bandwidth of the first SL resource pool and a bandwidth of the second SL resource pool.

[0140] Clause 10. A method as described in any of clauses 1 to 9, wherein the message indicates the sidelink congestion control SL-PRS resource handling capability of the UE.

[0141] Clause 11. A method as described in any of clauses 1 to 10, wherein the message indicates a SL-PRS buffering capability of the UE.

[0142] Clause 12. A user equipment (UE) comprising: a transceiver; a memory; and one or more processors, the one or more processors being communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: send a message indicating a sidelink positioning reference signal (SL-PRS) congestion control handling capability of the UE via the transceiver; determine an applicable congestion control handling time value for congestion control of a first side link (SL) resource pool based on the SL-PRS congestion control handling capability of the UE, the first SL resource pool comprising SL-PRS resources; measure a channel busy rate (CBR) of the first SL resource pool for a first time slot; select resources of the first SL resource pool based on the measured CBR for use in communication during a second time slot, wherein the second time slot is offset in time from the first time slot by the applicable congestion control handling time value; and communicate using the selected resources during the second time slot.

[0143] Clause 13. A UE as described in Clause 12, wherein the applicable congestion control handling time value is determined based on a set of congestion control handling time values ​​corresponding to the SL-PRS congestion control handling capability of the UE.

[0144] Clause 14. A UE according to Clause 13, wherein the one or more processors are configured to: identify a value in the congestion control processing time value set as the applicable congestion control processing time value based on the subcarrier spacing of the first SL resource pool.

[0145] Clause 15. A UE according to any one of clauses 12 to 14, wherein the message comprises: a first information element, the first information element indicating a first congestion control processing capability constituting the SL-PRS congestion control processing capability of the UE; and a second information element, the second information element indicating a second congestion control processing capability constituting the congestion control processing capability of the UE for congestion control of a second SL resource pool, the second SL resource pool not including SL-PRS resources.

[0146] Clause 16. A UE according to clause 15, wherein the one or more processors are configured to: determine an applicable congestion control processing time value for congestion control of the second SL resource pool based on the second congestion control processing capability.

[0147] Clause 17. A UE according to any one of clauses 12 to 14, wherein the message includes an information element indicating a common congestion control handling capability constituting the SL-PRS congestion control handling capability of the UE and a congestion control handling capability of the UE for congestion control of a second SL resource pool, the second SL resource pool not including SL-PRS resources.

[0148] Clause 18. A UE according to Clause 17, wherein the one or more processors are configured to determine, based on the common congestion control processing capability: a first congestion control processing time value, the first congestion control processing time value constituting the applicable congestion control processing time value for congestion control of the first SL resource pool; and a second congestion control processing time value, the second congestion control processing time value constituting the applicable congestion control processing time value for congestion control of the second SL resource pool.

[0149] Clause 19. A UE as described in Clause 18, wherein the one or more processors are configured to modify the second congestion control processing time value according to one or more modification factors to determine the first congestion control processing time value.

[0150] Clause 20. A UE according to clause 19, wherein modifying the second congestion control processing time value according to the one or more modification factors includes scaling the second congestion control processing time value based on a ratio between a bandwidth of the first SL resource pool and a bandwidth of the second SL resource pool.

[0151] Clause 21. A UE as described in any of clauses 12 to 20, wherein the message indicates a sidelink congestion control SL-PRS resource handling capability of the UE.

[0152] Clause 22. A UE as set forth in any of clauses 12 to 21, wherein the message indicates a SL-PRS buffering capability of the UE.

[0153] Clause 23. An apparatus for wireless communication, comprising: a component for sending a message indicating a sidelink positioning reference signal (SL-PRS) congestion control handling capability of a user equipment (UE); a component for determining an applicable congestion control handling time value for congestion control of a first side link (SL) resource pool based on the SL-PRS congestion control handling capability of the UE, the first SL resource pool comprising SL-PRS resources; a component for measuring a channel busy rate (CBR) of the first SL resource pool for a first time slot; a component for selecting resources of the first SL resource pool for use in communication during a second time slot based on the measured CBR, wherein the second time slot is offset in time from the first time slot by the applicable congestion control handling time value; and a component for communicating using the selected resources during the second time slot.

[0154] Clause 24. The apparatus of clause 23, wherein the applicable congestion control handling time value is determined based on a set of congestion control handling time values ​​corresponding to the SL-PRS congestion control handling capability of the UE.

[0155] Clause 25. The apparatus according to clause 24 comprises: a component for identifying a value in the congestion control processing time value set as the applicable congestion control processing time value based on the subcarrier spacing of the first SL resource pool.

[0156] Clause 26. An apparatus according to any one of clauses 23 to 25, wherein the message comprises: a first information element, the first information element indicating a first congestion control processing capability constituting the SL-PRS congestion control processing capability of the UE; and a second information element, the second information element indicating a second congestion control processing capability constituting the congestion control processing capability of the UE for congestion control of a second SL resource pool, the second SL resource pool not including SL-PRS resources.

[0157] Clause 27. The apparatus according to clause 26, comprising: means for determining an applicable congestion control processing time value for congestion control of the second SL resource pool according to the second congestion control processing capability.

[0158] Clause 28. An apparatus according to any one of clauses 23 to 25, wherein the message includes an information element indicating a common congestion control handling capability of both the SL-PRS congestion control handling capability constituting the UE and the congestion control handling capability of the UE for congestion control of a second SL resource pool, the second SL resource pool not including SL-PRS resources.

[0159] Clause 29. The apparatus according to Clause 28 comprises: a component for determining, based on the common congestion control processing capability: a first congestion control processing time value, the first congestion control processing time value constituting the applicable congestion control processing time value for congestion control of the first SL resource pool; and a second congestion control processing time value, the second congestion control processing time value constituting the applicable congestion control processing time value for congestion control of the second SL resource pool.

[0160] Clause 30. The apparatus of clause 29, comprising means for modifying the second congestion control handling time value according to one or more modification factors to determine the first congestion control handling time value.

[0161] Clause 31. An apparatus according to Clause 30, wherein modifying the second congestion control processing time value according to the one or more modification factors includes scaling the second congestion control processing time value based on a ratio between a bandwidth of the first SL resource pool and a bandwidth of the second SL resource pool.

[0162] Clause 32. An apparatus as described in any of clauses 23 to 31, wherein the message indicates a sidelink congestion control SL-PRS resource handling capability of the UE.

[0163] Clause 33. An apparatus as described in any of clauses 23 to 32, wherein the message indicates a SL-PRS buffering capability of the UE.

[0164] Clause 34. A non-transitory computer-readable medium storing instructions for wireless communications by a user equipment (UE), the instructions comprising code for performing the following operations: sending a message indicating a sidelink positioning reference signal (SL-PRS) congestion control handling capability of the UE; determining an applicable congestion control handling time value for congestion control of a first side link (SL) resource pool based on the SL-PRS congestion control handling capability of the UE, the first SL resource pool comprising SL-PRS resources; measuring a channel busy rate (CBR) of the first SL resource pool for a first time slot; selecting resources of the first SL resource pool based on the measured CBR for use in communication during a second time slot, wherein the second time slot is offset in time from the first time slot by the applicable congestion control handling time value; and communicating using the selected resources during the second time slot.

[0165] Clause 35. The non-transitory computer-readable medium of Clause 34, wherein the applicable congestion control handling time value is determined based on a set of congestion control handling time values ​​corresponding to the SL-PRS congestion control handling capability of the UE.

[0166] Clause 36. According to the non-transitory computer-readable medium described in Clause 35, the instructions include code for performing the following operations: based on the subcarrier spacing of the first SL resource pool, identifying a value in the congestion control processing time value set as the applicable congestion control processing time value.

[0167] Clause 37. A non-transitory computer-readable medium according to any one of clauses 34 to 36, wherein the message comprises: a first information element, the first information element indicating a first congestion control processing capability constituting the SL-PRS congestion control processing capability of the UE; and a second information element, the second information element indicating a second congestion control processing capability constituting the congestion control processing capability of the UE for congestion control of a second SL resource pool, the second SL resource pool not including SL-PRS resources.

[0168] Clause 38. The non-transitory computer-readable medium of Clause 37, the instructions comprising code for determining an applicable congestion control handling time value for congestion control of the second SL resource pool based on the second congestion control handling capability.

[0169] Clause 39. A non-transitory computer-readable medium according to any one of clauses 34 to 36, wherein the message includes an information element indicating a common congestion control handling capability of both the SL-PRS congestion control handling capability constituting the UE and the congestion control handling capability of the UE for congestion control of a second SL resource pool, the second SL resource pool not including SL-PRS resources.

[0170] Clause 40. According to the non-transitory computer-readable medium described in Clause 39, the instructions include code for performing the following operations: determining, based on the common congestion control processing capability: a first congestion control processing time value, the first congestion control processing time value constituting the applicable congestion control processing time value for congestion control of the first SL resource pool; and a second congestion control processing time value, the second congestion control processing time value constituting the applicable congestion control processing time value for congestion control of the second SL resource pool.

[0171] Clause 41. The non-transitory computer-readable medium of Clause 40, the instructions comprising code for modifying the second congestion control processing time value according to one or more modification factors to determine the first congestion control processing time value.

[0172] Clause 42. A non-transitory computer-readable medium according to Clause 41, wherein modifying the second congestion control processing time value according to the one or more modification factors includes scaling the second congestion control processing time value based on a ratio between a bandwidth of the first SL resource pool and a bandwidth of the second SL resource pool.

[0173] Clause 43. The non-transitory computer-readable medium of any of clauses 34 to 42, wherein the message indicates a sidelink congestion control SL-PRS resource handling capability of the UE.

[0174] Clause 44. The non-transitory computer-readable medium of any of clauses 34 to 43, wherein the message indicates a SL-PRS buffering capability of the UE.

Claims

1. A method for wireless communication by a user equipment (UE), the method comprising: sending a message indicating a sidelink positioning reference signal (SL-PRS) congestion control handling capability of the UE; determining an applicable congestion control processing time value for congestion control of a first side link (SL) resource pool according to the SL-PRS congestion control processing capability of the UE, the first SL resource pool including SL-PRS resources; Measuring a channel busy rate (CBR) of the first SL resource pool for a first time slot; selecting, based on the measured CBR, resources of the first SL resource pool for use in communicating during a second time slot, wherein the second time slot is offset in time from the first time slot by the applicable congestion control handling time value; as well as Communicating using the selected resources during the second time slot.

2. The method according to claim 1, wherein the applicable congestion control handling time value is determined based on a congestion control handling time value set corresponding to the SL-PRS congestion control handling capability of the UE.

3. The method according to claim 2, comprising: Based on the subcarrier spacing of the first SL resource pool, the value in the congestion control processing time value set is identified as the applicable congestion control processing time value.

4. The method of claim 1, wherein the message comprises: a first information element, wherein the first information element indicates a first congestion control handling capability constituting the SL-PRS congestion control handling capability of the UE; and A second information element, wherein the second information element indicates a second congestion control processing capability constituting the congestion control processing capability of the UE for congestion control of a second SL resource pool, wherein the second SL resource pool does not include SL-PRS resources.

5. The method according to claim 4, comprising: An applicable congestion control processing time value for congestion control of the second SL resource pool is determined according to the second congestion control processing capability.

6. The method according to claim 1, wherein the message includes an information element, wherein the information element indicates a common congestion control processing capability of both the SL-PRS congestion control processing capability constituting the UE and the congestion control processing capability of the UE for congestion control of a second SL resource pool, and the second SL resource pool does not include SL-PRS resources.

7. The method according to claim 6, comprising: Determined according to the public congestion control processing capability: a first congestion control processing time value, the first congestion control processing time value constituting the applicable congestion control processing time value for congestion control of the first SL resource pool; and A second congestion control processing time value, which constitutes an applicable congestion control processing time value for congestion control of the second SL resource pool.

8. The method according to claim 7, comprising: The second congestion control processing time value is modified according to one or more modification factors to determine the first congestion control processing time value.

9. The method according to claim 8, wherein modifying the second congestion control processing time value according to the one or more modification factors includes scaling the second congestion control processing time value based on a ratio between a bandwidth of the first SL resource pool and a bandwidth of the second SL resource pool.

10. The method of claim 1, wherein the message indicates a sidelink congestion control (SL-PRS) resource handling capability of the UE.

11. The method of claim 1, wherein the message indicates a SL-PRS buffering capability of the UE.

12. A user equipment (UE), comprising: Transceiver; Memory; and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: sending, via the transceiver, a message indicating a sidelink positioning reference signal (SL-PRS) congestion control handling capability of the UE; determining an applicable congestion control processing time value for congestion control of a first side link (SL) resource pool according to the SL-PRS congestion control processing capability of the UE, the first SL resource pool including SL-PRS resources; Measuring a channel busy rate (CBR) of the first SL resource pool for a first time slot; selecting, based on the measured CBR, resources of the first SL resource pool for use in communicating during a second time slot, wherein the second time slot is offset in time from the first time slot by the applicable congestion control handling time value; as well as Communicating using the selected resources during the second time slot.

13. The UE according to claim 12, wherein the applicable congestion control handling time value is determined based on a congestion control handling time value set corresponding to the SL-PRS congestion control handling capability of the UE.

14. The UE according to claim 13, wherein the one or more processors are configured to: identify a value in the congestion control processing time value set as the applicable congestion control processing time value based on the subcarrier spacing of the first SL resource pool.

15. The UE according to claim 12, wherein the message comprises: a first information element, wherein the first information element indicates a first congestion control handling capability constituting the SL-PRS congestion control handling capability of the UE; and A second information element, wherein the second information element indicates a second congestion control processing capability constituting the congestion control processing capability of the UE for congestion control of a second SL resource pool, wherein the second SL resource pool does not include SL-PRS resources.

16. The UE according to claim 15, wherein the one or more processors are configured to determine an applicable congestion control processing time value for congestion control of the second SL resource pool according to the second congestion control processing capability.

17. A UE according to claim 12, wherein the message includes an information element, which indicates a common congestion control processing capability of both the SL-PRS congestion control processing capability constituting the UE and the congestion control processing capability of the UE for congestion control of a second SL resource pool, and the second SL resource pool does not include SL-PRS resources.

18. The UE of claim 17, wherein the one or more processors are configured to: Determined according to the public congestion control processing capability: a first congestion control processing time value, the first congestion control processing time value constituting the applicable congestion control processing time value for congestion control of the first SL resource pool; and A second congestion control processing time value, which constitutes an applicable congestion control processing time value for congestion control of the second SL resource pool.

19. The UE of claim 18, wherein the one or more processors are configured to modify the second congestion control processing time value according to one or more modification factors to determine the first congestion control processing time value.

20. The UE of claim 19, wherein modifying the second congestion control processing time value according to the one or more modification factors comprises scaling the second congestion control processing time value based on a ratio between a bandwidth of the first SL resource pool and a bandwidth of the second SL resource pool.

21. The UE of claim 12, wherein the message indicates a sidelink congestion control SL-PRS resource handling capability of the UE.

22. The UE of claim 12, wherein the message indicates a SL-PRS buffering capability of the UE.

23. An apparatus for wireless communication, comprising: means for sending a message indicating a sidelink positioning reference signal (SL-PRS) congestion control handling capability of a user equipment (UE); means for determining an applicable congestion control handling time value for congestion control of a first side link (SL) resource pool according to the SL-PRS congestion control handling capability of the UE, the first SL resource pool comprising SL-PRS resources; means for measuring a channel busy rate (CBR) of the first SL resource pool for a first time slot; means for selecting resources of the first SL resource pool for use in communicating during a second time slot based on the measured CBR, wherein the second time slot is offset in time from the first time slot by the applicable congestion control handling time value; and Means for communicating using the selected resources during the second time slot.

24. The apparatus of claim 23, wherein the applicable congestion control handling time value is determined based on a set of congestion control handling time values ​​corresponding to the SL-PRS congestion control handling capability of the UE.

25. A non-transitory computer-readable medium storing instructions for wireless communications by a user equipment (UE), the instructions comprising code for: sending a message indicating a sidelink positioning reference signal (SL-PRS) congestion control handling capability of the UE; determining an applicable congestion control processing time value for congestion control of a first side link (SL) resource pool according to the SL-PRS congestion control processing capability of the UE, the first SL resource pool including SL-PRS resources; Measuring a channel busy rate (CBR) of the first SL resource pool for a first time slot; selecting, based on the measured CBR, resources of the first SL resource pool for use in communicating during a second time slot, wherein the second time slot is offset in time from the first time slot by the applicable congestion control handling time value; and Communicating using the selected resources during the second time slot.

26. The non-transitory computer-readable medium of claim 25, wherein the applicable congestion control handling time value is determined based on a set of congestion control handling time values ​​corresponding to the SL-PRS congestion control handling capability of the UE.

27. According to the non-transitory computer-readable medium of claim 26, the instructions include code for performing the following operations: based on the subcarrier spacing of the first SL resource pool, identifying a value in the congestion control processing time value set as the applicable congestion control processing time value.

28. The non-transitory computer readable medium of claim 25, wherein the message comprises: a first information element, wherein the first information element indicates a first congestion control handling capability constituting the SL-PRS congestion control handling capability of the UE; and A second information element, wherein the second information element indicates a second congestion control processing capability constituting the congestion control processing capability of the UE for congestion control of a second SL resource pool, wherein the second SL resource pool does not include SL-PRS resources.

29. The non-transitory computer-readable medium of claim 28, the instructions comprising code for determining an applicable congestion control processing time value for congestion control of the second SL resource pool based on the second congestion control processing capability.

30. A non-transitory computer-readable medium according to claim 25, wherein the message includes an information element, which indicates a common congestion control processing capability of both the SL-PRS congestion control processing capability constituting the UE and the congestion control processing capability of the UE for congestion control of a second SL resource pool, and the second SL resource pool does not include SL-PRS resources.

31. The non-transitory computer readable medium of claim 30, the instructions comprising code for: Determined according to the public congestion control processing capability: a first congestion control processing time value, the first congestion control processing time value constituting the applicable congestion control processing time value for congestion control of the first SL resource pool; and A second congestion control processing time value, which constitutes an applicable congestion control processing time value for congestion control of the second SL resource pool.

32. The non-transitory computer-readable medium of claim 31, the instructions comprising code for modifying the second congestion control processing time value according to one or more modification factors to determine the first congestion control processing time value.

33. A non-transitory computer-readable medium according to claim 32, wherein modifying the second congestion control processing time value according to the one or more modification factors includes scaling the second congestion control processing time value based on a ratio between a bandwidth of the first SL resource pool and a bandwidth of the second SL resource pool.

34. The non-transitory computer-readable medium of claim 34, wherein the message indicates a sidelink congestion control (SL-PRS) resource handling capability of the UE.

35. The non-transitory computer-readable medium of claim 25, wherein the message indicates a SL-PRS buffering capability of the UE.

Images