Sidelink positioning resource selection and reselection based on sidelink discontinuous reception (SL-DRX) configuration

Abstract

Techniques for sidelink communication are disclosed. In one aspect, a user equipment (UE) selects one or more initial resources for transmitting a sidelink positioning reference signal (SL-PRS) to a plurality of UEs participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a sidelink discontinuous reception (SL-DRX) active time of at least a set of UEs of the plurality of UEs; and transmitting the SL-PRS to at least the set of UEs.

Description

Background Art 1. Technical Field

[0001] Aspects of the present disclosure relate generally to wireless communications.

[0002] 2. Description of related technologies

[0003] Wireless communication systems have evolved over many generations, including first generation analog wireless telephone service (1G), second generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third generation (3G) high speed data, wireless service with Internet capabilities, and fourth generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use today, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile Communications (GSM), and the like.

[0004] The fifth generation (5G) wireless standard, known as New Radio (NR), enables higher data transfer speeds, a greater number of connections, and better coverage, among other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on a reference signal for positioning (RS-P), such as a downlink, uplink, or sidelink positioning reference signal (PRS)), and other technical enhancements compared to previous standards.

[0005] In addition, leveraging the increased data rates and reduced latency of 5G, vehicle-to-everything (V2X) communication technologies are being implemented to support autonomous driving applications, such as wireless communications between vehicles, between vehicles and roadside infrastructure, between vehicles and pedestrians, and so on. Summary of the invention

[0006] The following presents a simplified summary of the invention related to one or more aspects disclosed herein. Thus, the following summary of the invention should neither be considered as an exhaustive overview related to all conceived aspects, nor should it be considered to identify key or decisive elements related to all conceived aspects or to delineate the scope associated with any particular aspect. Therefore, the sole purpose of the following summary of the invention is to present certain concepts related to one or more aspects of the mechanisms disclosed herein in a brief form before the detailed embodiments presented below.

[0007] In one aspect, a method for sidelink communication performed by a user equipment (UE) includes: selecting one or more initial resources for sending a sidelink positioning reference signal (SL-PRS) to multiple UEs participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a sidelink discontinuous reception (SL-DRX) active time of at least a set of UEs among the multiple UEs; and sending the SL-PRS to at least the set of UEs.

[0008] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: select one or more initial resources for sending a sidelink positioning reference signal (SL-PRS) to multiple UEs participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a sidelink discontinuous reception (SL-DRX) active time of at least a set of UEs among the multiple UEs; and send the SL-PRS to at least the set of UEs via the at least one transceiver.

[0009] In one aspect, a user equipment (UE) includes: a device for selecting one or more initial resources for sending a sidelink positioning reference signal (SL-PRS) to multiple UEs participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a sidelink discontinuous reception (SL-DRX) active time of at least a set of UEs among the multiple UEs; and a device for sending the SL-PRS to at least the set of UEs.

[0010] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: select one or more initial resources for sending a sidelink positioning reference signal (SL-PRS) to multiple UEs participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a sidelink discontinuous reception (SL-DRX) active time of at least a set of UEs among the multiple UEs; and send the SL-PRS to at least the set of UEs.

[0011] Other objects and advantages associated with the various aspects disclosed herein will be apparent to those skilled in the art based on the drawings and detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings are presented to aid in describing various aspects of the present disclosure and are provided solely for illustration and not limitation of the various aspects.

[0013] Figure 1 An example wireless communication system in accordance with aspects of the present disclosure is illustrated.

[0014] Figure 2A and Figure 2B Example wireless network structures according to aspects of the present disclosure are illustrated.

[0015] Figure 3A , Figure 3B and Figure 3C is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

[0016] Figure 4A and Figure 4B Various interesting scenarios for sidelink-only positioning or joint Uu and sidelink positioning according to aspects of the present disclosure are illustrated.

[0017] FIG. 5A illustrates an example call flow for Mode A discovery in accordance with aspects of the present disclosure, and FIG. 5B illustrates an example call flow for Mode B discovery in accordance with aspects of the present disclosure.

[0018] FIG. 6A to FIG. 6C Example discontinuous reception (DRX) configurations in accordance with aspects of the present disclosure are illustrated.

[0019] 7A illustrates an example call flow for a Mode 1 Sidelink DRX (SL-DRX) configuration in accordance with aspects of the present disclosure, and FIG. 7B illustrates an example call flow for a Mode 2 SL-DRX configuration in accordance with aspects of the present disclosure.

[0020] Figure 8 is a diagram illustrating different SL-DRX parameters according to aspects of the present disclosure.

[0021] Fig. 9 is a diagram illustrating various aspects of a long DRX cycle according to various aspects of the present disclosure.

[0022] Fig.10 is a diagram of example resource pools illustrating positioning within a side link resource pool in accordance with aspects of the present disclosure.

[0023] Fig.11 Two resource allocation modes for transmission on the sidelink in accordance with aspects of the present disclosure are illustrated.

[0024] Fig.12 Example methods of sidelink communications according to aspects of the present disclosure are illustrated. DETAILED DESCRIPTION

[0025] Various aspects of the present disclosure are provided in the following description and related drawings for various examples provided for illustrative purposes. Alternative aspects may be designed without departing from the scope of the present disclosure. Additionally, well-known elements of the present disclosure will not be described in detail or will be omitted to avoid making the relevant details of the present disclosure difficult to understand.

[0026] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" is not necessarily to be construed as preferred or superior to other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation.

[0027] Those skilled in the art will appreciate that any of a variety of different techniques and methods may be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, which depends in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.

[0028] In addition, many aspects are described in terms of a sequence of actions to be performed by, for example, an element of a computing device. It should be understood that the various actions described herein may be performed by a specific circuit (e.g., an application specific integrated circuit (ASIC)), by a program instruction executed by one or more processors, or by a combination of the two. Additionally, the sequence of actions described herein may be considered to be fully embodied in any form of non-transient computer-readable storage medium, in which a corresponding computer instruction set is stored, which, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of the present disclosure may be embodied in a variety of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the various aspects described herein, the corresponding form of any such aspect may be described herein as, for example, "a logical component configured to perform the described action".

[0029] As used herein, the terms "user equipment" (UE), "vehicle UE" (V-UE), "pedestrian UE" (P-UE), and "base station" are not intended to be dedicated to or otherwise limited to any particular radio access technology (RAT), unless otherwise specified. In general, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., a vehicle onboard computer, a vehicle navigation device, a mobile phone, a router, a tablet computer, a laptop computer, an asset location device, a wearable device (e.g., a smart watch, glasses, an augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.). A UE can be mobile or can be stationary (e.g., at certain times) and can communicate with a radio access network (RAN). As used herein, the term "UE" can be interchangeably referred to as a "mobile device," "access terminal" or "AT," "client device," "wireless device," "subscriber device," "subscriber terminal," "subscriber station," "user terminal" or UT, "mobile terminal," "mobile station," or variations thereof.

[0030] A V-UE is a type of UE and may be any in-vehicle wireless communication device, such as a navigation system, an alarm system, a head-up display (HUD), an onboard computer, an in-vehicle infotainment system, an automated driving system (ADS), an advanced driver assistance system (ADAS), etc. Alternatively, a V-UE may be a portable wireless communication device (e.g., a cellular phone, a tablet computer, etc.) carried by a driver of a vehicle or an occupant in the vehicle. The term "V-UE" may refer to an in-vehicle wireless communication device or the vehicle itself, depending on the context. A P-UE is a type of UE and may be a portable wireless communication device carried by a pedestrian (i.e., a user who is not driving or riding a vehicle). Generally speaking, a UE may communicate with a core network via a RAN, and through the core network, the UE may be connected to an external network such as the Internet and to other UEs. Of course, other mechanisms for connecting to a core network and / or the Internet are also possible for a UE, such as through a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.), etc.

[0031] A base station may communicate with a UE by operating according to one of several RATs, depending on the network in which the base station is deployed, and may alternatively be referred to as an access point (AP), a network node, a Node B, an evolved Node B (eNB), a next generation eNB (ng-eNB), a new radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be primarily used to support wireless access for a UE, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, a base station may provide only edge node signaling functions, while in other systems, a base station may provide additional control and / or network management functions. A communication link by which a UE may transmit a signal to a base station is referred to as an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link by which a base station may transmit a signal to a UE is referred to as a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) may refer to a UL / reverse or DL / forward traffic channel.

[0032] The term "base station" may refer to a single physical transmit-receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRP may be an antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP 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). Alternatively, the non-co-located physical TRP may be a serving base station that receives measurement reports from a UE and an adjacent base station whose reference radio frequency (RF) signal the UE is measuring. Because, as used herein, a TRP is a point by which a base station transmits and receives wireless signals, references to transmitting from a base station or receiving at a base station should be understood to refer to a specific TRP of a base station.

[0033] In some implementations of supporting UE positioning, the base station may not support wireless access for the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but instead may send reference RF signals to the UE for measurement by the UE, and / or may receive and measure signals sent by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of sending RF signals to the UE) and / or as a positioning measurement unit (e.g., in the case of receiving and measuring RF signals from the UE).

[0034] An "RF signal" includes an electromagnetic wave of a given frequency that transmits information through the space between a transmitter and a receiver. 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 RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between a transmitter and a receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" where it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.

[0035] Figure 1 An example wireless communication system 100 according to various aspects of the present disclosure is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled as "BS") and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base stations 102 may include eNBs and / or ng-eNBs (where the wireless communication system 100 corresponds to an LTE network) or gNBs (where the wireless communication system 100 corresponds to an NR network) or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0036] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through a backhaul link 122, and interface with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) through the core network 170. The location server 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 may be integrated with the base station 102. The UE 104 may communicate with the location server 172 directly or indirectly. For example, the UE 104 may communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 may also communicate with the location server 172 through another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., the AP 150 described below), and the like. For signaling purposes, communication between UE 104 and location server 172 may be represented as an indirect connection (e.g., through core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with intermediate nodes (if any) omitted from the signaling diagram for clarity.

[0037] Among other functions, the base station 102 can perform functions related to one or more of the following: delivering user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 can communicate with each other directly or indirectly (e.g., through EPC / 5GC) on a backhaul link 134, which can be wired or wireless.

[0038] Base station 102 may communicate wirelessly with UE 104. Each of base stations 102 may provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells may be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., via a frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access to different types of UEs. Because a cell is supported by a specific base station, the term "cell" may refer to one or both of the logical communication entity and the base station supporting it, depending on the context. In some cases, the term “cell” may also refer to a geographic coverage area (eg, a sector) of a base station, as long as a carrier frequency can be detected and used for communications within some portion of the geographic coverage area 110 .

[0039] Although the geographic coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (e.g., in a handover area), some areas of the geographic coverage areas 110 may substantially overlap with the larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that may provide services to a restricted group referred to as a closed subscriber group (CSG).

[0040] The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as a reverse link) transmissions from the UE 104 to the base station 102 and / or downlink (DL) (also referred to as a forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be over one or more carrier frequencies. The allocation of carriers may be asymmetric for the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink than to the uplink).

[0041] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 in an unlicensed spectrum (e.g., 5 GHz) via a communication link 154. When communicating in the unlicensed spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communication to determine whether a channel is available.

[0042] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell base station 102' can adopt LTE or NR technology and use the same 5GHz unlicensed spectrum used by the WLAN AP 150. The small cell base station 102' adopting LTE / 5G in the unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum can be referred to as NR-U. LTE in the unlicensed spectrum can be referred to as LTE-U, License Assisted Access (LAA) or MulteFire.

[0043] The wireless communication system 100 may also include a mmW base station 180, which may operate in millimeter wave (mmW) frequencies and / or near mmW frequencies to communicate with UE 182. Extremely high frequency (EHF) is part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz, and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW may extend downward to a frequency of 3 GHz, and a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, and is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (sending and / or receiving) on ​​the mmW communication link 184 to compensate for extremely high path loss and short distances. In addition, it should be understood that in an alternative configuration, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Therefore, it should be understood that the foregoing illustrations are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0044] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal to the receiving device. In order to change the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that broadcast the RF signal. For example, a network node can use an array of antennas (referred to as a "phased array" or "antenna array") that produces RF beams that can be "steered" to point in different directions without actually moving the antenna. Specifically, the RF current from the transmitter is fed to each antenna in the correct phase relationship so that the radio waves from the separate antennas are added together in the desired direction to increase radiation while canceling out in the undesired direction to suppress radiation.

[0045] The transmit beams can be quasi-co-located, meaning that they appear to the receiver (e.g., UE) to have the same parameters, regardless of whether the network node's own transmit antennas are physically co-located. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about the second reference RF signal on the second beam can be derived based on information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal sent on the same channel. If the source reference RF signal is QCL type D, the receiver may use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0046] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, a receiver may increase the gain setting of an antenna array in a particular direction and / or adjust the phase setting of an antenna array in a particular direction to amplify (e.g., increase its gain level) the RF signal received from that direction. Thus, when a receiver is said to be beamforming in a certain direction, this means that the beam gain in that direction is high relative to the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal to interference plus noise ratio (SINR), etc.) of the RF signal received from that direction.

[0047] The transmit beam and the receive beam may be spatially correlated. The spatial relationship means that parameters of a second beam (e.g., a transmit beam or a receive beam) for a second reference signal may be derived based on information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE may then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to the base station based on the parameters of the receive beam.

[0048] Note that depending on the entity forming the "downlink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to send a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam that receives a downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, the uplink beam is an uplink receive beam, while if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0049] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0050] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5GNR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz-71GHz), FR4 (52.6GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0051] In view of the above aspects, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used in this document, it can be broadly referred to as a frequency that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used in this document, it can be broadly referred to as a frequency that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may be within the EHF band.

[0052] In a multi-carrier system (such as 5G), one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) used by the UE 104 / 182 and the cell in which the UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2), which can be configured and used to provide additional radio resources once an RRC connection is established between the UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, since the primary uplink carrier and the primary downlink carrier are typically UE-specific, those UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carrier. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier through which a base station communicates, the terms "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

[0053] For example, still refer to Figure 1 , one of the frequencies used by macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies used by macrocell base station 102 and / or mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers enables UE 104 / 182 to significantly increase its data transmission and / or reception rate. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40 MHz) compared to the data rate obtained with a single 20 MHz carrier.

[0054] exist Figure 1 In the example of FIG. 1 , the UE illustrated (for simplicity, in Figure 1Any UE (shown as a single UE 104 in FIG. 1 ) can receive a signal 124 from one or more earth orbiting space vehicles (SVs) 112 (e.g., satellites). In one aspect, the SVs 112 can be part of a satellite positioning system that the UEs 104 can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable a receiver (e.g., UE 104) to determine its position on or above the earth based at least in part on positioning signals (e.g., signals 124) received from the transmitters. Such transmitters typically transmit a signal with a repeating pseudo-random noise (PN) code marked with a set number of chips. Although typically located in the SVs 112, the transmitters can sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. The UEs 104 can include one or more dedicated receivers that are specifically designed to receive the signal 124 in order to derive geographic location information from the SVs 112.

[0055] In a satellite positioning system, the use of signal 124 may be enhanced by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential corrections, and the like, such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunction Satellite Augmentation System (MSAS), Global Positioning System (GPS) Assisted Geographic Augmented Navigation, or GPS and Geographic Augmented Navigation System (GAGAN), and the like. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0056] In one aspect, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a ground antenna) or a network node in a 5GC. This element in turn will provide access to other elements in the 5G network, and ultimately provide access to entities outside the 5G network (such as Internet web servers and other user devices). In this way, instead of or in addition to communication signals from ground base stations 102, UE 104 can receive communication signals (e.g., signal 124) from SV 112.

[0057] In particular, leveraging the increased data rates and reduced latency of NR, vehicle-to-everything (V2X) communication technology is being implemented to support intelligent transportation system (ITS) applications, such as wireless communications between vehicles (vehicle-to-vehicle (V2V)), between vehicles and roadside infrastructure (vehicle-to-infrastructure (V2I)), and between vehicles and pedestrians (vehicle-to-pedestrian (V2P)). The goal is to enable vehicles to sense the environment around them and communicate that information to other vehicles, infrastructure, and personal mobile devices. Such vehicle communications will enable safety, mobility, and environmental advances that current technology cannot provide. Once fully implemented, this technology is expected to reduce non-damaged vehicle collisions by 80%.

[0058] Still reference Figure 1 , the wireless communication system 100 may include a plurality of V-UEs 160 that may communicate with a base station 102 over a communication link 120 using a Uu interface (i.e., an air interface between a UE and a base station). The V-UEs 160 may also communicate directly with each other over a wireless side link 162, with a roadside unit (RSU) 164 (roadside access point) over a wireless side link 166, or with a sidelink-capable UE 104 over a wireless side link 168 using a PC5 interface (i.e., an air interface between sidelink-capable UEs). A wireless side link (or just "sidelink") is an adaptation of a core cellular network (e.g., LTE, NR) standard that allows direct communication between two or more UEs without going through a base station. The sidelink communication may be unicast or multicast and may be used for device-to-device (D2D) media sharing, V2V communication, V2X communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, etc.), emergency rescue applications, etc. One or more V-UEs in a group of V-UEs 160 utilizing sidelink communication may be within the geographic coverage area 110 of the base station 102. Other V-UEs 160 in such a group may be outside the geographic coverage area 110 of the base station 102 or otherwise unable to receive transmissions from the base station 102. In some cases, groups of V-UEs 160 communicating via sidelink communication may utilize a one-to-many (1:M) system, where each V-UE 160 transmits to each other V-UE 160 in the group. In some cases, the base station 102 facilitates scheduling of resources for the sidelink communication. In other cases, the sidelink communication is performed between the V-UEs 160 without involving the base station 102.

[0059] In one aspect, the sidelinks 162, 166, 168 can operate over a wireless communication medium of interest, which can be shared with other vehicles and / or infrastructure access points and other wireless communications between other RATs. A "medium" may include one or more time, frequency, and / or spatial communication resources (e.g., covering one or more channels across one or more carriers) associated with wireless communications between one or more transmitter / receiver pairs.

[0060] In one aspect, the sidelinks 162, 166, 168 may be cV2X links. The first generation of cV2X has been standardized in LTE, and the next generation is expected to be defined in NR. cV2X is a cellular technology that also enables device-to-device communications. In the United States and Europe, cV2X is expected to operate in the licensed ITS bands below 6 GHz. Other frequency bands may be allocated in other countries. Thus, as a specific example, the medium of interest utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the licensed ITS bands below 6 GHz. However, the present disclosure is not limited to this frequency band or cellular technology.

[0061] In one aspect, the side links 162, 166, 168 may be dedicated short-range communication (DSRC) links. DSRC is a unidirectional or bidirectional short-range to medium-range wireless communication protocol that uses the Wireless Access in Vehicular Environment (WAVE) protocol (also known as IEEE 802.11p) for V2V, V2I, and V2P communications. IEEE 802.11p is an approved modification to the IEEE 802.11 standard and operates in the licensed ITS band of 5.9 GHz (5.85 GHz-5.925 GHz) in the United States. In Europe, IEEE 802.11p operates in the ITS G5A band (5.875 GHz-5.905 MHz). Other frequency bands may be allocated in other countries. The V2V communications briefly described above occur on a safety channel, which is typically a 10 MHz channel dedicated to safety purposes in the United States. The rest of the DSRC band (total bandwidth is 75 MHz) is intended for other services of interest to drivers, such as road regulations, toll collection, parking automation, etc. Thus, as a specific example, the medium of interest utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the licensed ITS band at 5.9 GHz.

[0062] Alternatively, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among the various RATs. Although different licensed frequency bands have been reserved for certain communication systems (e.g., by government entities such as the Federal Communications Commission (FCC) in the United States), these systems (particularly those employing small cell access points) have recently expanded operations into unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies (most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include different variations of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single carrier FDMA (SC-FDMA) systems, and the like.

[0063] Communication between V-UEs 160 is referred to as V2V communication, communication between V-UEs 160 and one or more RSUs 164 is referred to as V2I communication, and communication between V-UEs 160 and one or more UEs 104 (where these UEs 104 are P-UEs) is referred to as V2P communication. V2V communication between V-UEs 160 may include, for example, information about the position, speed, acceleration, heading, and other vehicle data of these V-UEs 160. V2I information received at V-UEs 160 from one or more RSUs 164 may include, for example, road rules, parking automation information, etc. V2P communication between V-UEs 160 and UEs 104 may include information about, for example, the position, speed, acceleration, and heading of the V-UEs 160 and the position, speed (for example, in the case where the UE 104 is carried by a user on a bicycle) and heading of the UEs 104.

[0064] Note that although Figure 1 Only two of the UEs are illustrated as V-UEs (V-UE 160), but any of the illustrated UEs (e.g., UE 104, 152, 182, 190) may be V-UEs. In addition, although only these V-UEs 160 and a single UE 104 have been illustrated as being connected via a side link, Figure 1Any of the illustrated UEs, whether V-UE, P-UE, etc., may be capable of sidelink communications. In addition, although only UE 182 is described as being capable of beamforming, any of the illustrated UEs (including V-UE 160) may be capable of beamforming. In the case where V-UE 160 is capable of beamforming, they may beamform toward each other (i.e., toward other V-UE 160), toward RSU 164, toward other UEs (e.g., UE 104, 152, 182, 190), etc. Thus, in some cases, V-UE 160 may utilize beamforming on sidelinks 162, 166, and 168.

[0065] The wireless communication system 100 may also include one or more UEs (such as UE 190) indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. Figure 1 In the example of FIG. 1 , UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through the D2D P2P link), and has a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through the D2D P2P link). In one example, D2D P2P links 192 and 194 can be supported by any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Etc. As another example, D2D P2P links 192 and 194 may be side links, as described above with reference to side links 162 , 166 , and 168 .

[0066] Figure 2AAn example wireless network structure 200 is illustrated. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can be functionally viewed as a control plane (C-plane) function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane (U-plane) function 212 (e.g., UE gateway function, access to data networks, IP routing, etc.), which operate in conjunction to form a core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, and specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the ng-eNB 224 can also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. In addition, the ng-eNB 224 can communicate directly with the gNB 222 via the backhaul connection 223. In some configurations, the next generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of ng-eNBs 224 and gNBs 222. Either (or both) the gNBs 222 or ng-eNBs 224 may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0067] Another optional aspect may include a location server 230 that can communicate with the 5GC 210 to provide location assistance for the UE 204. The location server 230 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The location server 230 can be configured to support one or more location services for the UE 204 that can be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). In addition, the location server 230 can be integrated into a component of the core network, or alternatively can be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0068] Figure 2B Another example wireless network structure 240 is illustrated. 5GC 260 (which may correspond to Figure 2AThe 5GC 210 in the figure can be functionally considered as a control plane function provided by an access and mobility management function (AMF) 264, and a user plane function provided by a user plane function (UPF) 262, which operate in conjunction to form a core network (i.e., 5GC 260). The functions of AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a session management function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between UE 204 and a short message service function (SMSF) (not shown), and security anchor functionality (SEAF). AMF 264 also interacts with an authentication server function (AUSF) (not shown) and UE 204, and receives an intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM), the AMF 264 retrieves security material from the AUSF. The functionality of the AMF 264 also includes security context management (SCM). The SCM receives keys from the SEAF, which are used by the SCM to derive access network specific keys. The functionality of the AMF 264 also includes location service management for regulatory services, for the transmission of location service messages between the UE 204 and the Location Management Function (LMF) 270 (which acts as a location server 230), for the transmission of location service messages between the NG-RAN 220 and the LMF 270, for the allocation of Evolved Packet System (EPS) bearer identifiers for interoperation with EPS, and UE 204 mobility event notifications. In addition, the AMF 264 also supports functionality for non-3GPP (Third Generation Partnership Project) access networks.

[0069] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, user plane quality of service (QoS) handling (e.g., uplink / downlink rate enforcement, reflective QoS marking in downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering and downlink data notification triggering, and transmitting and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the delivery of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.

[0070] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, traffic steering configuration for routing traffic to the correct destination at UPF 262, partial control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

[0071] Another optional aspect may include an LMF 270 that can communicate with the 5GC 260 to provide location assistance for the UE 204. The LMF 270 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively can each correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, which can be connected to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not illustrated). SLP 272 can support similar functionality as LMF 270, but LMF 270 can communicate with AMF 264, NG-RAN 220, and UE 204 on the control plane (e.g., using interfaces and protocols designed to carry signaling messages rather than voice or data), and SLP 272 can communicate with UE 204 and external clients (e.g., third-party servers 274) on the user plane (e.g., using protocols designed to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).

[0072] Yet another optional aspect may include a third-party server 274 that can communicate with the LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., location estimate) of UE 204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or an external client. The third-party server 274 may be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or may alternatively each correspond to a single server.

[0073] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and the AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between the gNB 222 and / or ng-eNB 224 and the AMF 264 is referred to as the "N2" interface, and the interface between the gNB 222 and / or ng-eNB 224 and the UPF 262 is referred to as the "N3" interface. The gNBs 222 and / or ng-eNBs 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as an "Xn-C" interface. One or more of the gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 via a wireless interface referred to as a "Uu" interface.

[0074] The functionality of the gNB 222 is divided between a gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically assigned to the gNB-DU 228, including delivery of user data, mobility control, radio access network sharing, positioning, session management, etc. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically hosts the Radio Link Control (RLC) and Medium Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and one or more gNB-DUs 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is typically hosted by one or more independent gNB-RUs 229, which perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is referred to as the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC layer, the SDAP layer, and the PDCP layer, communicates with the gNB-DU 228 via the RLC layer and the MAC layer, and communicates with the gNB-RU 229 via the PHY layer.

[0075] Figure 3A , Figure 3B and Figure 3C Several example components (represented by corresponding blocks) are illustrated, which may be incorporated into a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270, or alternatively may be independent of Figure 2A and Figure 2BThe depicted NG-RAN 220 and / or 5GC 210 / 260 infrastructure, such as a dedicated network, to support operations as described herein. It should be understood that these components can be implemented differently in different types of devices (e.g., in an ASIC, in a system on a chip (SoC), etc.). The illustrated components can also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Moreover, a given device may include one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0076] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, which provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for preventing transmitting, etc.) for communicating via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 can each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes (such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium of interest (e.g., a certain set of time / frequency resources in a specific spectrum). The WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to the specified RAT, and conversely, receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.) respectively. Specifically, the WWAN transceivers 310 and 350 respectively include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0077] At least in some cases, the UE 302 and the base station 304 each further include one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide for communicating over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, The short-range wireless transceivers 320 and 360 are devices for communicating with other network nodes (such as other UEs, access points, base stations, etc.) (such as dedicated short-range communications (DSRC), wireless access for vehicle environments (WAVE), near field communications (NFC), ultra-wideband (UWB), etc.) (e.g., devices for sending, devices for receiving, devices for measuring, devices for tuning, devices for preventing sending, etc.). The short-range wireless transceivers 320 and 360 can be configured in different ways to send and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to the specified RAT, and conversely, receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, the short-range wireless transceivers 320 and 360 respectively include: one or more transmitters 324 and 364 for sending and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As a specific example, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Transceiver, and / or transceiver, NFC transceiver, UWB transceiver or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceiver.

[0078] At least in some cases, the UE 302 and the base station 304 also include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 can be connected to one or more antennas 336 and 376, respectively, and can provide means for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. In the case where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 can be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian regional navigation satellite system (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. In the case where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 can be communication signals (e.g., carrying control and / or user data) originating from a 5G network. The satellite signal receivers 330 and 370 can include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request information and operations from other systems as appropriate and, at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the location of UE 302 and base station 304, respectively.

[0079] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for sending, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. For another example, the network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0080] The transceiver can be configured to communicate over a wired or wireless link. The transceiver (whether a wired transceiver or a wireless transceiver) includes a transmitter circuit (e.g., transmitters 314, 324, 354, 364) and a receiver circuit (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver can be an integrated device (e.g., implementing the transmitter circuit and the receiver circuit in a single device), in some implementations can include separate transmitter circuits and separate receiver circuits, or in other implementations can be implemented in other ways. The transmitter circuit and the receiver circuit of the wired transceiver (e.g., in some implementations, the network transceivers 380 and 390) can be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform transmit "beamforming", as described herein. Similarly, the wireless receiver circuitry (e.g., receiver 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as antenna arrays, which allow the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and the receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366) so that the corresponding device can only receive or only transmit at a given time, rather than both receive and transmit at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listening module (NLM) or the like for performing various measurements.

[0081] As used herein, various wireless transceivers (e.g., in some implementations, transceivers 310, 320, 350, and 360, and network transceivers 380 and 390) and wired transceivers (e.g., in some implementations, network transceivers 380 and 390) may be generally referred to as a "transceiver," "at least one transceiver," or "one or more transceivers." Thus, whether a particular transceiver is a wired or wireless transceiver may be inferred based on the type of communication being performed. For example, backhaul communications between network devices or servers typically involve signaling via a wired transceiver, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) will typically involve signaling via a wireless transceiver.

[0082] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302, base station 304, and network entity 306 include one or more processors 332, 384, and 394, respectively, for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 332, 384, and 394 can provide means for processing, such as means for determining, means for calculating, means for receiving, means for sending, means for indicating, etc. In one aspect, processors 332, 384, and 394 can include, for example, one or more general purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuits, or various combinations thereof.

[0083] UE 302, base station 304, and network entity 306 include memory circuitry implementing memory 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memory 340, 386, and 396 may provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 may include positioning components 342, 388, and 398, respectively. Positioning components 342, 388, and 398 may be hardware circuits that are part of or coupled to processors 332, 384, and 394, respectively, which when executed cause UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, positioning components 342, 388, and 398 may be external to processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning components 342, 388 and 398 can be memory modules stored in the memories 340, 386 and 396, respectively, which, when executed by the processors 332, 384 and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304 and the network entity 306 to perform the functionality described herein. Figure 3A Possible locations for a location component 342 are illustrated, which may be, for example, part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3B Possible locations for a location component 388 are illustrated, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations for a location component 398 are illustrated, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

[0084] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide a means for sensing or detecting movement and / or orientation information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. By way of example, sensor 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. In addition, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate positioning in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0085] In addition, the UE 302 includes a user interface 346, which provides a means for providing indications to the user (e.g., audible and / or visual indications) and / or for receiving user input (e.g., when the user actuates a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include a user interface.

[0086] Referring to the one or more processors 384 in more detail, in a downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement the functionality of the RRC layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0087] The transmitter 354 and the receiver 352 may implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The transmitter 354 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine coding and modulation schemes and for spatial processing. Channel estimates may be derived based on a reference signal and / or channel condition feedback sent by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a corresponding spatial stream for transmission.

[0088] At the UE 302, the receiver 312 receives the signal through its corresponding antenna 316. The receiver 312 recovers the information modulated onto the RF carrier and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 implement layer 1 functionality associated with various signal processing functions. The receiver 312 can perform spatial processing on the information to recover any spatial streams destined for the UE 302. If there are multiple spatial streams destined for the UE 302, they can be combined into a single OFDM symbol stream by the receiver 312. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement layer 3 (L3) and layer 2 (L2) functionality.

[0089] In the downlink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.

[0090] Similar to the functionality described in conjunction with downlink transmissions performed by the base station 304, the one or more processors 332 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0091] Channel estimates derived by the channel estimator from a reference signal or feedback sent by the base station 304 may be used by the transmitter 314 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antennas 316. The transmitter 314 may modulate an RF carrier with a corresponding spatial stream for transmission.

[0092] The uplink transmissions are processed at the base station 304 in a manner similar to that described in conjunction with the receiver functionality at the UE 302. The receiver 352 receives the signal through its respective antenna 356. The receiver 352 recovers the information modulated onto the RF carrier and provides the information to one or more processors 384.

[0093] In the uplink, the one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 302. The IP packets from the one or more processors 384 may be provided to the core network. The one or more processors 384 are also responsible for error detection.

[0094] For convenience, UE 302, base station 304 and / or network entity 306 may Figure 3A , Figure 3B and Figure 3C, are shown to include various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionality in different designs. In particular, FIG. 3A to FIG. 3C The various components in are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, use of the device, or other considerations. For example, in Figure 3A In the case of , a specific implementation of UE 302 may omit WWAN transceiver 310 (e.g., a wearable device or tablet or PC or laptop may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or may omit short-range wireless transceiver 320 (e.g., only cellular, etc.), or may omit satellite signal receiver 330, or may omit sensor 344, etc. In another example, in Figure 3B In the case of a wireless cellular network, a specific implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or may omit the short-range wireless transceiver 360 (e.g., cellular only, etc.), or may omit the satellite signal receiver 370, etc. For the sake of brevity, illustrations of various alternative configurations are not provided herein, but will be readily apparent to those skilled in the art.

[0095] Various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to one another via data buses 334, 382, ​​and 392, respectively. In one aspect, the data buses 334, 382, ​​and 392 may form or be part of a communication interface for the UE 302, base station 304, and network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 334, 382, ​​and 392 may provide for communication between different logical entities.

[0096] Figure 3A , Figure 3B and Figure 3C The components of can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3CThe components of may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or combine at least one memory component for storing information or executable code used by the circuit to provide the functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by the processor and memory components of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by the processor and memory components of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Moreover, some or all of the functionality represented by blocks 390 to 398 may be implemented by the processor and memory components of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, actions and / or functions are described herein as being performed by "UE", "by base station", "by network entity", etc. However, it should be understood that such operations, actions and / or functions may actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc. (such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386 and 396, positioning components 342, 388 and 398, etc.).

[0097] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be operated differently from a network operator or cellular network infrastructure (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, the network entity 306 may be a component of a dedicated network that may be configured to communicate with the UE 302 via the base station 304 or independently of the base station 304 (e.g., via a non-cellular communication link such as WiFi).

[0098] NR supports or implements various sidelink positioning techniques. Figure 4AVarious interesting scenarios for sidelink-only positioning or joint Uu and sidelink positioning according to various aspects of the present disclosure are illustrated. In scenario 410, at least one peer UE with a known location can improve the Uu-based positioning (e.g., multi-cell RTT, downlink time difference of arrival (DL-TDOA), etc.) of the target UE by providing an additional anchor (e.g., using the sidelink round trip time (RTT) (SL-RTT)). In scenario 420, a low-end (e.g., low-capacity or "RedCap") target UE can obtain assistance from an advanced UE to determine its position using, for example, a sidelink positioning and ranging procedure with the advanced UE. Compared to a low-end UE, an advanced UE can have more capabilities, such as more sensors, faster processors, more memory, more antenna elements, higher transmit power capabilities, access to additional frequency bands, or any combination thereof. In scenario 430, a relay UE (e.g., with a known location) participates in the positioning estimation of a remote UE without performing uplink positioning reference signal (PRS) transmission over the Uu interface. Scenario 440 illustrates joint positioning of multiple UEs. Specifically, in scenario 440, two UEs with unknown locations may be jointly located under non-line-of-sight (NLOS) conditions by utilizing constraints from nearby UEs.

[0099] Figure 4B Additional interesting scenarios for sidelink-only positioning or joint Uu and sidelink positioning according to various aspects of the present disclosure are illustrated. In scenario 450, UEs used for public safety (e.g., used by police, firefighters, etc.) can perform peer-to-peer (P2P) positioning and ranging for public safety and other purposes. For example, in scenario 450, public safety UEs can be out of coverage of the network and use sidelink positioning techniques to determine the position or relative distance and relative positioning between public safety UEs. Similarly, scenario 460 shows multiple UEs that are out of coverage and use sidelink positioning techniques (such as SL-RTT) to determine the position or relative distance and relative positioning.

[0100] A UE that assists a target UE in a positioning procedure may be referred to as a "positioning peer" or "Pos-Peer" UE. Two types of positioning peer UE discovery procedures have been introduced for sidelink collaborative positioning, referred to as Mode A and Mode B. According to aspects of the present disclosure, FIG. 5A illustrates an example call flow 500 for Mode A discovery, and FIG. 5B illustrates an example call flow 550 for Mode B discovery. The purpose of these discovery procedures is to discover which positioning peer UEs are near the target UE. In Mode A, a positioning peer UE may announce its presence by broadcasting a sidelink positioning peer discovery message with a positioning flag, as shown in FIG. 5A . In Mode B, a target UE that wishes to discover a positioning peer UE may initiate by broadcasting a sidelink positioning peer request message with a field related to positioning, as shown in FIG. 5B .

[0101] As shown in Figures 5A and 5B, both the positioning peer discovery and request messages can be divided into two parts labeled "A" and "B" to achieve a more power efficient method and handshake between the target UE and the potential positioning peer UE. The target UE can rank the potential positioning peer UEs (also referred to as anchor UEs) based on the following criteria: (1) location quality criteria, (2) channel quality criteria, (3) response time criteria, (4) mobility state criteria, or any combination thereof.

[0102] Even when there is no traffic sent from the network to the UE, the UE is expected to monitor every downlink subframe on the physical downlink control channel (PDCCH). This means that the UE must always be "on" or active even when there is no traffic, because the UE cannot know exactly when the network will send data to it. However, being active all the time is a considerable power drain on the UE.

[0103] To address this issue, the UE may implement discontinuous reception (DRX) and / or connected mode discontinuous reception (CDRX) techniques. DRX and CDRX are mechanisms by which the UE enters a "sleep" mode for scheduled time periods and "wakes up" for other time periods. During the awake or active period, the UE checks to see if there is any data from the network, and if not, returns to sleep mode.

[0104] In order to implement DRX and CDRX, the UE and the network need to be synchronized. In the worst scenario, the network may try to transmit some data to the UE while the UE is in sleep mode, and the UE may wake up when there is no data to be received. To prevent such scenarios, the UE and the network should have a well-defined agreement on when the UE can be in sleep mode and when the UE should be awake / active. This agreement has been standardized in various technical specifications. It is noted that DRX includes CDRX, and thus references to DRX refer to both DRX and CDRX, unless otherwise indicated.

[0105] The network (e.g., serving cell) may configure the UE with DRX / CDRX timing using an RRC connection reconfiguration message (for CDRX) or an RRC connection setup message (for DRX). The network may signal the following DRX configuration parameters to the UE. (1) DRX cycle: the duration of one "on time" plus one "off time". This value is not explicitly specified in the RRC message; instead, it is calculated from the subframe / slot time and the "long DRX cycle start offset". (2) On duration timer: the duration of the "on time" within a DRX cycle. (3) DRX inactivity timer: how long the UE should remain "on" after receiving a PDCCH. When this timer is on, the UE remains in the "on state", which can extend the on period into a period that was originally an "off" period. (4) DRX retransmission timer: the maximum number of consecutive PDCCH subframes / slots that the UE should remain active for waiting for incoming retransmissions after the first available retransmission time. (5) Short DRX cycle: A DRX cycle that can be implemented during the "off" period of a long DRX cycle. (6) DRX short cycle timer: The number of consecutive subframes / time slots that should be followed by a short DRX cycle after the DRX inactivity timer expires.

[0106] FIG. 6A to FIG. 6C Example DRX configurations according to aspects of the present disclosure are illustrated. Fig. 6A An example DRX configuration 600A is illustrated in which a long DRX cycle (the time from the start of one On Duration to the start of the next On Duration) is configured and no PDCCH is received during the cycle. Figure 6BAn example DRX configuration 600B is illustrated in which a long DRX cycle is configured and a PDCCH is received during the on duration 610 of the illustrated second DRX cycle. Note that the on duration 610 ends at time 612. However, based on the length of the DRX inactivity timer and the time when the PDCCH is received, the time that the UE is awake / active ("active time") is extended to time 614. Specifically, when a PDCCH is received, the UE starts the DRX inactivity timer and remains in an active state until the timer expires (the timer is reset each time a PDCCH is received during the active time).

[0107] Figure 6C An example DRX configuration 600C is illustrated in which a long DRX cycle is configured and a PDCCH and a DRX command MAC control element (MAC-CE) are received during the on duration 620 of the illustrated second DRX cycle. Note that due to the PDCCH received at time 622 and the subsequent expiration of the DRX inactivity timer at time 624, the active time that started during the on duration 620 will normally end at time 624, as described above with reference to Figure 6B However, in Figure 6C In the example of , the active time is shortened to time 626 based on the time of receiving the DRX command MAC CE instructing the UE to terminate the DRX inactivity timer and start the duration timer.

[0108] In more detail, the active time of the DRX cycle is the time during which the UE is considered to be monitoring the PDCCH. The active time may include the time during which the on duration timer is running, the DRX inactivity timer is running, the DRX retransmission timer is running, the MAC contention resolution timer is running, the scheduling request has been transmitted on the PUCCH and is pending, an uplink grant for a pending HARQ retransmission may occur and there is data in the corresponding HARQ buffer, or a newly transmitted PDCCH indicating a cell radio network temporary identifier (C-RNTI) addressed to the UE has not been received after successfully receiving a random access response (RAR) for a preamble not selected by the UE. And, in non-contention based random access, after receiving the RAR, the UE should be in an active state until a newly transmitted PDCCH indicating a C-RNTI addressed to the UE is received.

[0109] Within a sidelink communication session between a transmitter (Tx) UE and a receiver (Rx) UE, the Rx UE may utilize a sidelink DRX (SL-DRX) cycle. The SL-DRX configuration may be configured to the UE via unicast signaling or groupcast / broadcast signaling. If configured via unicast signaling, the parameters of the SL-DRX configuration may be negotiated between the Tx UE and the Rx UE. There are two modes for configuring the SL-DRX configuration to the Rx UE via unicast signaling, depending on whether the Tx UE and the Rx UE are in an RRC connected state or in an RRC inactive or idle state. FIG. 7A illustrates an example call flow 700 for a mode 1 SL-DRX configuration according to various aspects of the present disclosure, and FIG. 7B illustrates an example call flow 750 for a mode 2 SL-DRX configuration according to various aspects of the present disclosure. In FIGS. 7A and 7B , communication between the UE and the base station is via RRC signaling, and communication between the UEs is via PC5-RRC signaling.

[0110] In mode 1 SL-DRX configuration (Figure 7A), the Tx UE and the Rx UE are in an RRC connected state. As shown in call flow 700, the Rx UE optionally transmits proposed SL-DRX configuration parameters to the Tx UE. The proposed SL-DRX configuration parameters may include the cycle length, offset, and turn-on duration of the SL-DRX cycle for the Rx UE. The Tx UE forwards the proposed SL-DRX configuration parameters of the Rx UE to its serving base station (BS). The base station determines the SL DRX configuration of the Rx UE based on the proposed SL-DRX configuration parameters. The base station may align the SL-DRX cycle with the Uu DRX cycle of the Tx UE. The Tx UE provides the SL-DRX configuration to the Rx UE, which accepts or rejects the SL-DRX configuration. If the Rx UE accepts the SL-DRX configuration, the Rx UE reports the received SL-DRX configuration to its serving base station. If the Rx UE rejects the SL-DRX configuration, the Tx UE reports the rejection to its serving base station, which may determine and provide a different SL-DRX configuration.

[0111] In Mode 2 SL-DRX configuration (Figure 7B), the Tx UE and the Rx UE are in RRC inactive or idle state. As shown in call flow 750, the Rx UE optionally transmits its expected / proposed SL-DRX configuration parameters to the Tx UE. The expected / proposed SL-DRX configuration parameters may include the cycle length, offset and turn-on duration of the SL-DRX cycle for the Rx UE. Based on the received parameters, the Tx UE determines the SL-DRX configuration of the Rx UE. How the Tx UE determines the SL-DRX configuration of the Rx UE depends on the specific implementation of the UE. Note that in Mode 2, the Tx UE and the Rx UE can be in coverage (IC) or out of coverage (OOC).

[0112] Figure 8 8 is a diagram 800 illustrating different SL-DRX parameters according to aspects of the present disclosure. Figure 8 As shown in , there is a SL-DRX offset from the system reference point (e.g., direct frame number (DFN)), SL-DRX cycle length, SL-DRX inactivity timer, and SL-DRX on duration timer. These parameters are similar to those in the reference above. FIG. 6A to FIG. 6C Based on these parameters, the UE can be in the active state or the extended active state, such as Figure 8 as shown in .

[0113] Now referring to the SL-DRX configuration via multicast / broadcast signaling, in this case, the SL-DRX configuration is based on a QoS profile of an L2 destination identifier (ID) (i.e., a data link layer destination ID). Specifically, if there are multiple QoS profiles, the SL-DRX cycle length is the minimum cycle length, if there are multiple QoS profiles, the SL-DRX on time is the maximum on duration, and if there are multiple QoS profiles, the SL-DRX inactivity timer is the maximum inactivity time.

[0114] For L2 destination ID based SL-DRX configuration, the SL-DRX offset parameter (given in milliseconds) is equal to the value of the L2 destination ID modulo the SL-DRX cycle length (given in milliseconds).

[0115] There are different ways to configure SL-DRX via multicast or broadcast, depending on whether the UE is in coverage (IC) or out of coverage (OOC). For the in-coverage scenario, the UE can obtain the SL-DRX configuration via SIB12 on the dedicated RRC, regardless of whether the UE is in RRC connected state, RRC inactive state or RRC idle state. The SL-DRX configuration in SIB12 implicitly indicates that the broadcast base station supports SL-DRX. For the out-of-coverage scenario, the SL-DRX configuration can be pre-configured to the UE, and it depends on the UE specific implementation to determine when to apply the SL-DRX configuration.

[0116] In order to ensure backward compatibility of SL-DRX for groupcast and broadcast SL-DRX configurations, the UE may broadcast a Tx profile indicating whether the UE supports SL-DRX for the L2 destination ID. When the Tx profile broadcast by the Rx UE indicates support for SL-DRX for the L2 destination ID, the Tx UE only assumes SL-DRX for the RX UE. If all service types / L2 destination IDs of interest have an associated Tx profile indicating support for SL-DRX, the Rx UE determines to use SL-DRX. The Rx UE implements SL-DRX operation for the L2 destination ID with the associated Tx profile. For unicast SL-DRX configuration, backward compatibility issues of SL-DRX are not assumed for sidelink transmissions after the PC5-RRC connection is established. That is, backward compatibility is handled based on PC5-RRC UE capability signaling.

[0117] Fig. 9 900 is a diagram illustrating various aspects of a long DRX cycle according to various aspects of the present disclosure. Fig. 9 In , each vertical box represents the time during which the UE is active. Once a long DRX cycle starts, the UE remains active for the duration of the DRX on duration timer, and if no PDCCH is received during this time, the UE transitions to DRX sleep state until the next on duration starts. However, if there is some PDCCH activity during the DRX on duration period, it is very likely that the UE can be scheduled again. If the UE transitions to the DRX sleep state, it is unlikely that it will receive a possible scheduling grant / assignment. Therefore, there is a timer that keeps the UE active after being scheduled. This timer is called the DRX inactivity timer and is configured by RRC signaling. The UE starts / restarts this timer whenever the PDCCH indicates a new uplink or downlink transmission, and the UE remains active and continues to monitor the PDCCH until the DRX inactivity timer expires, as Fig. 9 The DRX Inactivity Timer can be varied from 0ms to 2560ms.

[0118] The SL-DRX "active time" of the Rx UE includes the time during which any of the SL-DRX timers is running (e.g., on duration timer, inactivity timer, retransmission timer) or will run in the future (e.g., on duration timer, inactivity timer, retransmission timer). For SL-CSI reporting, the active time includes the time between the time when the SL-CSI request is transmitted and the time when the SL-CSI report is received, or the period of the parameter "sl-LatencyBound-CSI-Report". In addition, the time slots associated with the periodic transmission announced by the Tx UE are considered to be the active time of the Rx UE.

[0119] Another aspect of sidelink positioning is the configuration of a resource pool (RP-P) for sidelink positioning. The 12 symbols between the first and last symbols (gap) of a sidelink time slot (used for automatic gain control (AGC)) in the time domain and the allocated subchannels in the frequency domain form a resource pool for sidelink transmission and / or reception. RP-Ps can be specifically configured within the resource pool for positioning purposes. Each RP-P includes an offset, a periodicity, a number of consecutive symbols within a time slot (e.g., as few as one symbol), and / or a bandwidth within a component carrier (or a bandwidth across multiple component carriers). In addition, each RP-P can be associated with a zone or with a distance from a reference location.

[0120] A base station (or UE, depending on the resource allocation mode) may assign one or more resource configurations from the RP-P to another UE. Additionally or alternatively, a UE (e.g., a relay or remote UE) may request one or more RP-P configurations, and the UE may include one or more of the following in the request: (1) location information (or zone identifier) ​​of the UE; (2) periodicity; (3) bandwidth; (4) offset; (5) number of symbols; and (6) whether a configuration with "low interference" is desired (which may be determined by the assigned QoS or priority).

[0121] The base station or UE can configure / assign rate matching resources or RP-P for rate matching / silencing to the sidelink UE so that when there is a conflict between the assigned resources and another resource pool containing data (PSSCH) and / or control (PSCCH), the sidelink UE is expected to rate match / silence / puncture the data, DMRS and / or CSI-RS within the conflicting resources. This will achieve orthogonalization between positioning and data transmission to increase the coverage of the PRS signal.

[0122] Fig.10 1000 is a diagram illustrating an example of a resource pool for positioning within a side link resource pool according to aspects of the present disclosure. Fig.10In the example of , time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one orthogonal frequency division multiplexing (OFDM) symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is one subchannel.

[0123] exist Fig.10 In the example of , the entire time slot (except the first symbol and the last symbol) can be a resource pool for sidelink 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 sidelink positioning transmission / reception is allocated in the last four pre-slot symbols of the time slot. Therefore, non-positioning side link data (such as user data, CSI-RS, and control information) can only be sent in the first eight post-AGC symbols, but not in the last four pre-slot symbols to prevent conflicts with the configured RP-P. Non-side link positioning data that would have been sent in the last four pre-slot symbols can be punctured or muted, or non-side link data that would normally span more than eight post-AGC symbols can be rate matched to accommodate the eight post-AGC symbols.

[0124] A Sidelink Positioning Reference Signal (SL-PRS) has been defined to support sidelink positioning procedures between UEs. Similar to the downlink PRS (DL-PRS), the 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 resource has been designed to have a comb-based pattern to enable Fast Fourier Transform (FFT) based processing at the receiver. The SL-PRS resource consists 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. The SL-PRS may also be associated with a specific RP-P (e.g., certain SL-PRS may be allocated in certain RP-Ps). The SL-PRS is also defined to have intra-slot repetition ( Fig.10 ), to allow combining gain (if required). There may also be inter-UE coordination of RP-P to provide dynamic SL-PRS and data multiplexing while minimizing SL-PRS collisions.

[0125] Fig.11Two resource allocation modes for transmission on the NR sidelink according to various aspects of the present disclosure are illustrated. In a first mode 1110 (labeled "Mode 1"), a base station 1102 (e.g., any of the base stations described herein) allocates time and / or frequency resources for sidelink communications between UEs 1104 and 1106 via DCI 3_0. In this case, as an example, UE 1104 may be a Tx UE and UE 1106 may be an Rx UE.

[0126] In the second mode 1120 (labeled as "Mode 2"), the involved UEs 1104 and 1106 autonomously select sidelink resources for sidelink communication. The UE can use the first mode only if it has cellular coverage, but can use the second mode regardless of whether it has cellular coverage. Note that although Fig.11 Two UEs are illustrated, but it should be understood that there may be more than the two UEs 1104 and 1106 illustrated.

[0127] The signaling on the sidelink is the same between the two resource allocation modes. From the perspective of the Rx UE (e.g., UE 1106), there is no difference between the modes. That is, for the Rx UE, it does not matter whether the resources for sidelink communication are allocated by the base station 1102 or by the Tx UE (e.g., UE 1104).

[0128] Mode 1 supports dynamic grant (DG), configuration grant (CG) type 1, and CG type 2. In some cases, CG type 1 is activated via RRC signaling from base station 1102. In some cases, the modulation and coding scheme (MCS) used for sidelink transmission is determined by the involved UEs 1104 and 1106 within the limits set by base station 1102. In mode 2, the Tx UE (e.g., UE 1104) performs channel sensing by blind decoding all physical sidelink control channels (PSCCH) to determine the resources reserved for other sidelink transmissions. The Tx UE reports the available resources to its upper layer, and the upper layer determines the resource usage.

[0129] With respect to resource selection with respect to SL-DRX (e.g., which resource pool and / or which time slots and / or subchannels of the resource pool), it is expected that the Tx UE selects initial transmission resources from the resource pool only in the active time of the Rx UE (i.e., when the SL-DRX timer of the Rx UE is currently running or will run in the future). That is, the Tx UE is expected to select initial resources (e.g., a certain set of symbols and / or time slots within the resource pool) that coincide with the active time of the Rx UE in the time domain to send data to the Rx UE. Since the Tx UE may receive multiple grants for SL-PRS transmission (e.g., from a location server, base station, or anchor UE), for each such sidelink grant, the grant is used if the selected / granted resources coincide with the active time of at least one Rx UE, otherwise the grant is skipped. If there is no sidelink grant in the SL-DRX active time of the destination UE (e.g., Tx UE) with data to be transmitted, resource reselection is triggered. For resource reselection due to preemption, the reselected resource should not be earlier than the preempted resource in the time domain.

[0130] For both resource allocation Mode 1 DG and Mode 2 grants, if the initial transmission opportunity is discarded because there is no Rx UE in the DRX active time, the Tx UE (e.g., UE 1104) can use the retransmission opportunity for the initial transmission. For a Mode 1 sidelink grant that is not in the sidelink active time of any destination UE with data to be transmitted, then if the initial transmission is discarded, the Tx UE transmits an acknowledgment (ACK) to its serving base station (e.g., base station 1102). However, if the retransmission is discarded, the Tx UE transmits a negative acknowledgment (NACK) to its base station. Therefore, if the Tx UE finds at least one destination UE in the active time of its DRX cycle, resource selection for data transmission is successful.

[0131] In contrast to sidelink data communication, for a positioning session, the Tx UE needs to send SL-PRS to multiple SL UEs and receive SL-PRS from multiple SL UEs. In order to send SL-PRS to multiple UEs and receive SL-PRS from multiple UEs, the anchor UE, base station or location server needs to ensure that the resources selected (from RP-P) for SL-PRS transmission are allocated within the DRX active time of the Rx UEs and Tx UEs involved. It should be noted that the anchor UE is the UE that assigns / allocates / grants resources to the Rx UEs and Tx UEs involved in the positioning session from the RP-P and optionally determines the location of the target UE. The anchor UE may or may not be connected to the base station. The Tx UE selects the transmission resources allocated / granted by the location server, base station or anchor UE from the RP-P, and sends SL-PRS to one or more Rx UEs on the selected resources. The Rx UE measures the SL-PRS and sends a response to the Tx UE. A UE may sometimes be an anchor UE, a Tx UE or a Rx UE, depending on the operation it is performing. Furthermore, the UE may be both an anchor UE and a Tx UE, or both an anchor UE and a Rx UE.

[0132] For the sidelink data transmission use case using multicast signaling, the anchor UE (e.g., UE 1104) needs to ensure that the resource grant is selected so that it is in the active time of at least one destination UE; otherwise, the grant is skipped. However, this approach will not work for the positioning use case because the anchor UE or location server needs to obtain SL-PRS measurements from multiple UEs. For example, there may be a certain minimum number of UE measurements required to make a positioning fix.

[0133] It has been proposed to change / adjust the DRX parameters (and therefore active time) of the receiving UEs to ensure that they are all aligned, thereby ensuring that they will all be in the active time of the resource grant for positioning. In contrast, the present disclosure does not change the SL-DRX parameters of the UEs, but adjusts the resource selection and reselection procedures to address the need to have a sufficient number of UEs sending / measuring SL-PRS for the positioning session.

[0134] At a higher layer, the Tx UE shall select the initial transmission resources from the granted RP-P only if the initial transmission resources occur within the active time of the Rx UE (that is, if the SL-DRX timer is currently running or will run in the future (at least the duration timer is enabled)). For each such sidelink resource grant, if the grant is in the active time of at least "X" destination UEs (e.g., Rx UEs), the grant is used; otherwise the grant is skipped. The value of X can be (1) all UEs associated with the positioning session and expected to be recipients of the SL-PRS, (2) the minimum number of UEs for the positioning session set by the location server, (3) the minimum number of UEs for the positioning session set by the anchor UE or controller UE, (4) the minimum number of UEs for the positioning session set by the positioning session configuration, (5) the minimum number of UEs for the positioning session set by upper layers, or (6) related to the positioning method. For example, for option 6, the SL-RTT positioning procedure alone may require at least three Rx UEs, the SL-RTT / SL-AoA positioning procedure may require at least one Rx UE, and for the joint Uu / sidelink positioning procedure, the number of Rx UEs may depend on the number of Uu measurements.

[0135] There are different ways in which the Tx UE can ensure that the initial transmit resources occur within the active time of the Rx UE. The first is referred to herein as the "group resource selection mode". Consider the case where an anchor UE needs to conduct a sidelink positioning session with four other UEs (referred to as remote UEs). For resource selection from an RP-P, the anchor UE needs to ensure that all selected resources for the positioning session are within the DRX on duration of the other UEs. If any of the selected resources does not meet this condition, the anchor UE needs to continue attempting resource selection (e.g., in a different RP-P or a subsequent RP-P). When the selected resources meet the DRX active time condition of the other UEs, resource selection will stop.

[0136] In group resource selection mode, there shall be a limit on the maximum number of attempts / retries for resource selection. The maximum number of retries may be defined in the applicable wireless communication standard, or provided by the location server, anchor UE, base station, positioning session configuration or upper layers. After the maximum number of retries, the UE shall move to sequential resource selection mode as defined below.

[0137] The group resource selection mode is particularly useful for ranging and RTT type positioning methods. For example, in case of UE mobility, it is desirable to have the measurements of the involved UEs performed at approximately the same time.

[0138] In one aspect, the location server or anchor UE may provide a set of UEs that the condition needs to be met, rather than having the location server or anchor UE perform a DRX active time check for all participating UEs. For example, for an anchor UE participating in a positioning session with four remote UEs, the location server or anchor UE may indicate that the resource selection is successful if the selected resource is within any two of the four UEs' DRX active times.

[0139] Another way in which the anchor UE can ensure that the initial transmission resources occur within the active time of the remote UE is referred to herein as "sequential resource selection mode". In this mode, the anchor UE will select resource grants on a best effort basis. The anchor UE will continue to transmit the selected grants to different remote UEs in a sequential manner. The anchor UE needs to select different sets of destination IDs / UEs in a "round robin" manner to obtain measurements from all involved UEs. Once the minimum number of destination IDs / UEs / SL-PRS resources is detected, the anchor UE will stop the resource selection process.

[0140] Since the anchor UE selects different sets of destination UEs and allocates resources to them in a round-robin manner, the anchor UE will need to select multiple sets of resources for the positioning session in different (e.g., sequential) time windows to obtain a single set of measurements from all UEs. For example, the anchor UE may select a first set of remote UEs involved in the positioning session and allocate a first set of resources to them during a first time period, select a second set of remote UEs involved in the positioning session and allocate a second set of resources to them during a second (e.g., sequential) time period, and so on, until all involved UEs have been assigned resources for sending and / or measuring SL-PRS.

[0141] The sequential resource selection mode may be particularly useful for angle-based type positioning methods, such as AoD-based methods.

[0142] In one aspect, the location server or base station should provide a mode of resource selection (e.g., group resource selection or sequential resource selection) in a Mode 1 resource allocation sidelink positioning session. In contrast, the anchor UE should provide a mode of resource selection in a Mode 2 resource allocation sidelink positioning session.

[0143] In one aspect, for group resource selection mode, the location server or anchor UE should provide a count of the minimum number of attempts for resource selection.Similarly, the location server or anchor UE may need to provide a minimum set of destination IDs / UEs that need to be decoded in a given time slot / opportunity.

[0144] In one aspect, the location server or anchor UE may configure separate resource selection windows for the group resource selection mode and the sequential resource selection mode. At each resource selection opportunity within the resource selection window, the Tx UE shall count the number of UEs that will be in the active time of each potential resource, sort the potential resources based on the descending order of the number of UEs that will be in the active time of the resource, and select the potential resource according to the order (e.g., select the potential resource that will have the most UEs in the active time).

[0145] Fig.12 An example method 1200 of sidelink communication according to aspects of the present disclosure is illustrated. In one aspect, method X00 may be performed by a UE (eg, a Tx UE).

[0146] At 1210, the UE selects one or more initial resources for sending SL-PRS to a plurality of UEs (e.g., Rx UEs) participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a SL-DRX active time of at least a set of UEs among the plurality of UEs. In one aspect, operation 1210 may be performed by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered as a means for performing the operation.

[0147] At 1220, the UE sends the SL-PRS to at least the set of UEs. In one aspect, operation 1220 may be performed by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered a means for performing the operation.

[0148] It should be appreciated that a technical advantage of the method 1200 is to increase positioning performance by increasing the detectability of the Rx UE to the SL-PRS in a positioning session because the Rx UE will be in a SL-DRX active state for reception of the SL-PRS.

[0149] In the above specific embodiments, it can be seen that different features are grouped together in each example. This disclosure should not be understood as an intention that the example clauses have more features than the features explicitly mentioned in each clause. On the contrary, various aspects of the present disclosure may include less than all the features of the disclosed individual example clauses. Therefore, the following clauses should be considered to be incorporated into the description accordingly, where each clause itself can be used as a separate example. Although each subordinate clause can refer to a specific combination of one clause with other clauses in a clause, the aspects of the subordinate clause are not limited to specific combinations. It should be understood that other example clauses may also include a combination of the subject matter of the subordinate clause aspect with any other subordinate clause or independent clause or any feature with other subordinate clauses and independent clauses. Various aspects disclosed herein explicitly include these combinations, unless it is clearly expressed or can be easily inferred that a specific combination is not intended to be used (for example, contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). In addition, it is also expected that various aspects of the clause can be included in any other independent clause, even if the clause is not directly subordinate to the independent clause.

[0150] Specific implementation examples are described in the following numbered clauses:

[0151] Clause 1. A method of sidelink communication performed by a user equipment (UE), the method comprising: selecting one or more initial resources for sending a sidelink positioning reference signal (SL-PRS) to multiple UEs participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a sidelink discontinuous reception (SL-DRX) active time of at least a set of UEs among the multiple UEs; and sending the SL-PRS to at least the set of UEs.

[0152] Clause 2. A method according to clause 1, wherein the number of the UE set includes: all of the multiple UEs, the minimum number of UEs among the multiple UEs for the positioning session set by the location server, the minimum number of UEs among the multiple UEs for the positioning session set by the anchor UE, the minimum number of UEs among the multiple UEs set by the configuration of the positioning session, the minimum number of UEs among the multiple UEs set by the upper layer of the UE, or the minimum number of UEs among the multiple UEs for a certain type of the positioning session.

[0153] Clause 3. A method according to any one of clauses 1 to 2, wherein selecting the one or more initial resources includes: for each of the one or more granted resources, determining whether the granted resource is scheduled within the SL-DRX active time of at least the UE set until the one or more initial resources are selected or the maximum number of selection attempts is met.

[0154] Clause 4. The method of clause 3, wherein the maximum number of selection attempts is received from: a location server for the positioning session, an anchor UE for the positioning session, a configuration of the positioning session, or an upper layer of the UE.

[0155] Clause 5. A method as described in any of clauses 3 to 4, the method further comprising: performing sequential resource selection for a subset of the set of UEs based on the maximum number of selection attempts being satisfied.

[0156] Clause 6. The method of any one of clauses 1 to 5, further comprising: receiving a first time window during which group resource selection is performed; receiving a second time window during which sequential resource selection is performed; or any combination thereof.

[0157] Clause 7. The method according to Clause 6 further includes: determining, for each resource selection opportunity within a resource selection window, the number of UEs that will be in the SL-DRX active time for each resource within the resource selection window; and selecting the one or more initial resources based on the one or more initial resources having the highest number of UEs that will be in the SL-DRX active time.

[0158] Clause 8. According to any one of clauses 1 to 7, the method also includes: receiving the number of the multiple UEs from a location server for the positioning session or an anchor UE for the positioning session, receiving the number of the UE set from the location server or the anchor UE, or any combination thereof.

[0159] Clause 9. According to any one of clauses 1 to 8, the method further includes: sequentially selecting one or more additional resources for sending additional SL-PRS to an additional set of the multiple UEs other than the UE set until a minimum number of the multiple UEs has been met, wherein the one or more additional resources are selected based on the one or more additional resources being scheduled within the SL-DRX active time of the additional set of the multiple UEs; and sending the additional SL-PRS to the additional set of the multiple UEs.

[0160] Clause 10. The method of any one of clauses 1 to 9, further comprising: receiving one or more resource grants for the positioning session, at least one of the one or more resource grants comprising at least the one or more initial resources.

[0161] Clause 11. The method according to clause 10, further comprising: discarding resource grants from the one or more resource grants that do not include at least one transmission resource scheduled within the SL-DRX active time of at least the set of UEs.

[0162] Clause 12. According to the method described in any one of clauses 1 to 11, the method further includes: receiving a mode of resource selection from the location server or the base station based on the resources for the positioning session being allocated by the location server or the base station; or receiving the mode of resource selection from the anchor node based on the resources for the positioning session being allocated by the anchor node.

[0163] Clause 13. A method as described in any of clauses 1 to 12, wherein the number of UE sets is a minimum number of UEs used for the positioning session.

[0164] Clause 14. A method as described in any of clauses 1 to 13, the method further comprising: receiving a measurement of the SL-PRS from each UE in the set of UEs.

[0165] Clause 15. A method according to any one of clauses 1 to 14, the method further comprising: receiving SL-DRX configuration information for each of the plurality of UEs involved in the positioning session.

[0166] Clause 16. The method of clause 15, wherein the SL-DRX configuration information is received from: the plurality of UEs, a location server, a base station, or an anchor UE for the positioning session.

[0167] Clause 17. A method according to any one of clauses 1 to 16, wherein the SL-DRX active time comprises: a time during which a SL-DRX timer of the set of UEs is currently running or will run.

[0168] Clause 18. A user equipment (UE), comprising: a memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: select one or more initial resources for sending a sidelink positioning reference signal (SL-PRS) to a plurality of UEs participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a sidelink discontinuous reception (SL-DRX) active time of at least a set of UEs among the plurality of UEs; and send the SL-PRS to at least the set of UEs via the at least one transceiver.

[0169] Clause 19. A UE according to Clause 18, wherein the number of the UE set includes: all of the multiple UEs, the minimum number of UEs among the multiple UEs for the positioning session set by the location server, the minimum number of UEs among the multiple UEs for the positioning session set by the anchor UE, the minimum number of UEs among the multiple UEs set by the configuration of the positioning session, the minimum number of UEs among the multiple UEs set by the upper layer of the UE, or the minimum number of UEs among the multiple UEs for a certain type of the positioning session.

[0170] Clause 20. A UE according to any one of clauses 18 to 19, wherein the at least one processor configured to select the one or more initial resources includes the at least one processor configured to perform the following: for each of the one or more granted resources, determine whether the granted resource is scheduled within the SL-DRX active time of at least the set of UEs until the one or more initial resources are selected or the maximum number of selection attempts is met.

[0171] Clause 21. The UE of clause 20, wherein the maximum number of selection attempts is received from: a location server for the positioning session, an anchor UE for the positioning session, a configuration of the positioning session, or an upper layer of the UE.

[0172] Clause 22. A UE as described in any of clauses 20 to 21, wherein the at least one processor is further configured to: perform sequential resource selection for a subset of the set of UEs based on the maximum number of selection attempts being satisfied.

[0173] Clause 23. A UE according to any one of clauses 18 to 22, wherein the at least one processor is further configured to: receive via the at least one transceiver a first time window during which group resource selection is performed; receive via the at least one transceiver a second time window during which sequential resource selection is performed; or any combination thereof.

[0174] Clause 24. A UE according to clause 23, wherein the at least one processor is further configured to: determine, for each resource selection opportunity within a resource selection window, the number of UEs that will be in the SL-DRX active time for each resource within the resource selection window; and select the one or more initial resources based on the one or more initial resources having the highest number of UEs that will be in the SL-DRX active time.

[0175] Clause 25. A UE according to any one of clauses 18 to 24, wherein the at least one processor is further configured to: receive the number of the multiple UEs from a location server for the positioning session or an anchor UE for the positioning session via the at least one transceiver, receive the number of the UE set from the location server or the anchor UE via the at least one transceiver, or any combination thereof.

[0176] Clause 26. A UE according to any one of clauses 18 to 25, wherein the at least one processor is further configured to: sequentially select one or more additional resources for sending additional SL-PRS to an additional set of the multiple UEs other than the UE set until a minimum number of the multiple UEs has been met, wherein the one or more additional resources are selected based on the one or more additional resources being scheduled within the SL-DRX active time of the additional set of the multiple UEs; and send the additional SL-PRS to the additional set of the multiple UEs via the at least one transceiver.

[0177] Clause 27. A UE according to any one of clauses 18 to 26, wherein the at least one processor is further configured to: receive one or more resource grants for the positioning session via the at least one transceiver, at least one of the one or more resource grants including at least the one or more initial resources.

[0178] Clause 28. A UE according to clause 27, wherein the at least one processor is further configured to: discard resource grants from the one or more resource grants that do not include at least one transmission resource scheduled within the SL-DRX active time of at least the set of UEs.

[0179] Clause 29. A UE according to any one of clauses 18 to 28, wherein the at least one processor is further configured to: receive a mode of resource selection from the location server or the base station via the at least one transceiver based on the resources for the positioning session being allocated by the location server or the base station; or receive the mode of resource selection from the anchor node via the at least one transceiver based on the resources for the positioning session being allocated by the anchor node.

[0180] Clause 30. A UE as set forth in any of clauses 18 to 29, wherein the number of the set of UEs is a minimum number of UEs for the positioning session.

[0181] Clause 31. A UE as described in any of clauses 18 to 30, wherein the at least one processor is further configured to: receive a measurement of the SL-PRS from each UE in the set of UEs via the at least one transceiver.

[0182] Clause 32. A UE according to any one of clauses 18 to 31, wherein the at least one processor is further configured to: receive SL-DRX configuration information for each of the multiple UEs involved in the positioning session via the at least one transceiver.

[0183] Clause 33. The UE of clause 32, wherein the SL-DRX configuration information is received from: the plurality of UEs, a location server, a base station, or an anchor UE for the positioning session.

[0184] Clause 34. A UE according to any one of clauses 18 to 33, wherein the SL-DRX active time comprises: a time during which a SL-DRX timer of the set of UEs is currently running or is to run.

[0185] Clause 35. A user equipment (UE), comprising: a device for selecting one or more initial resources for sending a sidelink positioning reference signal (SL-PRS) to multiple UEs participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a sidelink discontinuous reception (SL-DRX) active time of at least a set of UEs among the multiple UEs; and a device for sending the SL-PRS to at least the set of UEs.

[0186] Clause 36. A UE according to clause 35, wherein the number of the UE set includes: all of the multiple UEs, the minimum number of UEs among the multiple UEs for the positioning session set by the location server, the minimum number of UEs among the multiple UEs for the positioning session set by the anchor UE, the minimum number of UEs among the multiple UEs set by the configuration of the positioning session, the minimum number of UEs among the multiple UEs set by the upper layer of the UE, or the minimum number of UEs among the multiple UEs for a certain type of the positioning session.

[0187] Clause 37. A UE according to any one of clauses 35 to 36, wherein the device for selecting the one or more initial resources includes: a device for: determining, for each of one or more granted resources, whether the granted resource is scheduled within the SL-DRX active time of at least the set of UEs until the one or more initial resources are selected or the maximum number of selection attempts is met.

[0188] Clause 38. The UE of clause 37, wherein the maximum number of selection attempts is received from: a location server for the positioning session, an anchor UE for the positioning session, a configuration of the positioning session, or an upper layer of the UE.

[0189] Clause 39. A UE as described in any of clauses 37 to 38, the UE further comprising: means for performing sequential resource selection for a subset of the set of UEs based on the maximum number of selection attempts being satisfied.

[0190] Clause 40. A UE according to any one of clauses 35 to 39, the UE further comprising: means for receiving a first time window during which group resource selection is performed; means for receiving a second time window during which sequential resource selection is performed; or any combination thereof.

[0191] Clause 41. A UE according to clause 40, wherein the UE further comprises: a device for determining, for each resource selection opportunity within the resource selection window, the number of UEs that will be in the SL-DRX active time for each resource within the resource selection window; and a device for selecting the one or more initial resources based on the one or more initial resources having the highest number of UEs that will be in the SL-DRX active time.

[0192] Clause 42. A UE according to any one of clauses 35 to 41, wherein the UE further comprises: a device for receiving the number of the multiple UEs from a location server for the positioning session or an anchor UE for the positioning session, a device for receiving the number of the UE set from the location server or the anchor UE, or any combination thereof.

[0193] Clause 43. A UE according to any one of clauses 35 to 42, wherein the UE further includes: a device for sequentially selecting one or more additional resources for sending additional SL-PRS to an additional set of the multiple UEs other than the UE set until a minimum number of the multiple UEs has been met, wherein the one or more additional resources are selected based on the one or more additional resources being scheduled within the SL-DRX active time of the additional set of the multiple UEs; and a device for sending the additional SL-PRS to the additional set of the multiple UEs.

[0194] Clause 44. A UE according to any one of clauses 35 to 43, the UE further comprising: means for receiving one or more resource grants for the positioning session, at least one of the one or more resource grants comprising at least the one or more initial resources.

[0195] Clause 45. A UE according to clause 44, the UE further comprising: means for discarding resource grants from the one or more resource grants that do not include at least one transmission resource scheduled within the SL-DRX active time of at least the set of UEs.

[0196] Clause 46. A UE according to any one of clauses 35 to 45, wherein the UE further comprises: a device for receiving a mode of resource selection from a location server or a base station based on resources for the positioning session being allocated by the location server or the base station; or a device for receiving the mode of resource selection from an anchor node based on resources for the positioning session being allocated by an anchor node.

[0197] Clause 47. A UE as set forth in any of clauses 35 to 46, wherein the number of the set of UEs is a minimum number of UEs for the positioning session.

[0198] Clause 48. A UE as described in any of clauses 35 to 47, the UE further comprising: means for receiving measurements of the SL-PRS from each UE in the set of UEs.

[0199] Clause 49. A UE according to any one of clauses 35 to 48, the UE further comprising: means for receiving SL-DRX configuration information for each of the plurality of UEs involved in the positioning session.

[0200] Clause 50. The UE of clause 49, wherein the SL-DRX configuration information is received from: the plurality of UEs, a location server, a base station, or an anchor UE for the positioning session.

[0201] Clause 51. A UE according to any of clauses 35 to 50, wherein the SL-DRX active time comprises: a time during which a SL-DRX timer of the set of UEs is currently running or is to run.

[0202] Clause 52. A non-transitory computer-readable medium storing computer-executable instructions which, when executed by a user equipment (UE), cause the UE to: select one or more initial resources for sending a sidelink positioning reference signal (SL-PRS) to a plurality of UEs participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a sidelink discontinuous reception (SL-DRX) active time of at least a set of UEs among the plurality of UEs; and send the SL-PRS to at least the set of UEs.

[0203] Clause 53. A non-transitory computer-readable medium according to clause 52, wherein the number of the UE set includes: all of the multiple UEs, the minimum number of UEs among the multiple UEs for the positioning session set by the location server, the minimum number of UEs among the multiple UEs for the positioning session set by the anchor UE, the minimum number of UEs among the multiple UEs set by the configuration of the positioning session, the minimum number of UEs among the multiple UEs set by the upper layer of the UE, or the minimum number of UEs among the multiple UEs for a certain type of the positioning session.

[0204] Clause 54. A non-transitory computer-readable medium according to any one of clauses 52 to 53, wherein the computer executable instructions that, when executed by the UE, cause the UE to select the one or more initial resources include computer executable instructions that, when executed by the UE, cause the UE to perform the following: for each of one or more granted resources, determine whether the granted resource is scheduled within at least the SL-DRX active time of the set of UEs until the one or more initial resources are selected or the maximum number of selection attempts is met.

[0205] Clause 55. The non-transitory computer-readable medium of Clause 54, wherein the maximum number of selection attempts is received from: a location server for the positioning session, an anchor UE for the positioning session, a configuration of the positioning session, or an upper layer of the UE.

[0206] Clause 56. A non-transitory computer-readable medium according to any one of clauses 54 to 55, wherein the non-transitory computer-readable medium further comprises: computer-executable instructions which, when executed by the UE, cause the UE to: perform sequential resource selection for a subset of the set of UEs based on the maximum number of selection attempts being satisfied.

[0207] Clause 57. A non-transitory computer-readable medium according to any one of clauses 52 to 56, wherein the non-transitory computer-readable medium further comprises: computer-executable instructions which, when executed by the UE, cause the UE to: receive a first time window during which group resource selection is performed; receive a second time window during which sequential resource selection is performed; or any combination thereof.

[0208] Clause 58. According to the non-transitory computer-readable medium described in Clause 57, the non-transitory computer-readable medium also includes: computer executable instructions, which, when executed by the UE, cause the UE to: determine, for each resource selection opportunity within the resource selection window, the number of UEs that will be in the SL-DRX active time for each resource within the resource selection window; and select the one or more initial resources based on the one or more initial resources having the highest number of UEs that will be in the SL-DRX active time.

[0209] Clause 59. A non-transitory computer-readable medium according to any one of clauses 52 to 58, wherein the non-transitory computer-readable medium further comprises: computer-executable instructions which, when executed by the UE, cause the UE to: receive the number of the multiple UEs from a location server for the positioning session or an anchor UE for the positioning session, receive the number of the set of UEs from the location server or the anchor UE, or any combination thereof.

[0210] Clause 60. A non-transitory computer-readable medium according to any one of clauses 52 to 59, wherein the non-transitory computer-readable medium further comprises: computer-executable instructions which, when executed by the UE, cause the UE to: sequentially select one or more additional resources for sending additional SL-PRS to an additional set of the multiple UEs other than the UE set until a minimum number of the multiple UEs has been met, wherein the one or more additional resources are selected based on the one or more additional resources being scheduled within the SL-DRX active time of the additional set of the multiple UEs; and send the additional SL-PRS to the additional set of the multiple UEs.

[0211] Clause 61. A non-transitory computer-readable medium according to any one of clauses 52 to 60, wherein the non-transitory computer-readable medium further comprises: computer-executable instructions which, when executed by the UE, cause the UE to: receive one or more resource grants for the positioning session, at least one of the one or more resource grants comprising at least the one or more initial resources.

[0212] Clause 62. According to the non-transitory computer-readable medium described in Clause 61, the non-transitory computer-readable medium also includes: computer-executable instructions, which, when executed by the UE, cause the UE to: discard the resource grant that does not include at least one transmission resource scheduled within the SL-DRX active time of at least the set of UEs in the one or more resource grants.

[0213] Clause 63. A non-transitory computer-readable medium according to any one of clauses 52 to 62, wherein the non-transitory computer-readable medium further comprises: computer-executable instructions which, when executed by the UE, cause the UE to: receive a mode of resource selection from the location server or the base station based on resources for the positioning session being allocated by the location server or the base station; or receive the mode of resource selection from the anchor node based on resources for the positioning session being allocated by the anchor node.

[0214] Clause 64. The non-transitory computer-readable medium of any of clauses 52 to 63, wherein the number of the set of UEs is a minimum number of UEs for the positioning session.

[0215] Clause 65. A non-transitory computer-readable medium according to any one of clauses 52 to 64, the non-transitory computer-readable medium further comprising: computer-executable instructions which, when executed by the UE, cause the UE to: receive measurements of the SL-PRS from each UE in the set of UEs.

[0216] Clause 66. A non-transitory computer-readable medium according to any one of clauses 52 to 65, wherein the non-transitory computer-readable medium further comprises: computer-executable instructions which, when executed by the UE, cause the UE to: receive SL-DRX configuration information for each of the multiple UEs involved in the positioning session.

[0217] Clause 67. The non-transitory computer-readable medium of Clause 66, wherein the SL-DRX configuration information is received from: the plurality of UEs, a location server, a base station, or an anchor UE for the positioning session.

[0218] Clause 68. A non-transitory computer-readable medium as described in any of clauses 52 to 67, wherein the SL-DRX active time comprises: a time during which a SL-DRX timer of the set of UEs is currently running or will run.

[0219] It should be understood by those skilled in the art that information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0220] In addition, it will be appreciated by those skilled in the art that the various exemplary logic blocks, modules, circuits and algorithmic steps described in conjunction with the aspects disclosed herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, frames, modules, circuits and steps have been generally described in terms of their functionality. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints proposed to the entire system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0221] The various illustrative logical blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0222] The methods, sequences and / or algorithms described in conjunction with the various aspects disclosed herein may be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integral with the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.

[0223] In one or more example aspects, the described functions can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored on a computer-readable medium or sent via a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, which include any media that facilitates the transfer of computer programs from one place to another. Storage media can be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other media that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, a server, or other remote source using a coaxial cable, a fiber optic cable, a twisted pair, a digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer readable media.

[0224] Although the foregoing disclosure shows the exemplary aspects of the present disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the present disclosure as defined by the appended claims. In addition, the functions, steps and / or actions of the method claims according to the various aspects of the present disclosure as described herein do not need to be performed in any particular order. In addition, although the elements of the present disclosure may be described or claimed in the singular, plural forms may also be considered unless explicitly stated to be limited to the singular.

Claims

1. A method of sidelink communication performed by a user equipment (UE), the method comprising: selecting one or more initial resources for transmitting a sidelink positioning reference signal (SL-PRS) to a plurality of UEs participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a sidelink discontinuous reception (SL-DRX) active time of at least a set of UEs among the plurality of UEs; and The SL-PRS is sent to at least the set of UEs.

2. The method according to claim 1, wherein the number of the UE set comprises: all of the plurality of UEs, a minimum number of UEs among the plurality of UEs set by the location server for the positioning session, a minimum number of UEs among the plurality of UEs set by the anchor UE for the positioning session, a minimum number of UEs among the plurality of UEs set by the configuration of the positioning session, a minimum number of UEs among the plurality of UEs set by an upper layer of the UE, or A minimum number of UEs among the plurality of UEs for the positioning session of a certain type.

3. The method of claim 1 , wherein selecting the one or more initial resources comprises: For each of the one or more granted resources, determining whether the granted resource is scheduled within at least the SL-DRX active time of the set of UEs until the one or more initial resources are selected or a maximum number of selection attempts is met.

4. The method of claim 3, wherein the maximum number of selection attempts is received from: a location server for said positioning session, an anchor UE for the positioning session, the configuration of the positioning session, or The upper layer of the UE.

5. The method according to claim 3, further comprising: Sequential resource selection is performed for a subset of the set of UEs based on the maximum number of selection attempts being satisfied.

6. The method according to claim 1, further comprising: receiving a first time window during which group resource selection is performed; receiving a second time window during which sequential resource selection is performed; or Any combination of them.

7. The method according to claim 6, further comprising: for each resource selection opportunity within a resource selection window, determining a number of UEs that will be in SL-DRX active time for each resource within the resource selection window; as well as The one or more initial resources are selected based on the one or more initial resources having a highest number of UEs that will be in the SL-DRX active time.

8. The method according to claim 1, further comprising: receiving the number of the plurality of UEs from a location server for the positioning session or an anchor UE for the positioning session, receiving the number of the set of UEs from the location server or the anchor UE, or Any combination of them.

9. The method according to claim 1, further comprising: sequentially selecting one or more additional resources for transmitting additional SL-PRS to additional sets of the plurality of UEs other than the set of UEs until a minimum number of the plurality of UEs has been met, wherein the one or more additional resources are selected based on the one or more additional resources being scheduled within an SL-DRX active time of the additional set of the plurality of UEs; and The additional SL-PRS is sent to the additional set of the plurality of UEs.

10. The method according to claim 1, further comprising: One or more resource grants are received for the positioning session, at least one of the one or more resource grants including at least the one or more initial resources.

11. The method according to claim 10, further comprising: The one or more resource grants do not include at least one transmission resource scheduled within the SL-DRX active time of at least the set of UEs.

12. The method according to claim 1, further comprising: a mode for receiving resource selection from a location server or a base station based on resources for the positioning session being allocated by the location server or the base station; or The mode of resource selection is received from an anchor node based on the resources for the positioning session being allocated by the anchor node.

13. The method according to claim 1, wherein the number of the set of UEs is a minimum number of UEs used for the positioning session.

14. The method according to claim 1, further comprising: A measurement of the SL-PRS is received from each UE in the set of UEs.

15. The method according to claim 1, further comprising: SL-DRX configuration information is received for each of the plurality of UEs involved in the positioning session.

16. The method of claim 15, wherein the DRX configuration information is received from: the plurality of UEs, Location Server, Base station, or An anchor UE for the positioning session.

17. The method according to claim 1, wherein the SL-DRX active time comprises: The time during which the SL-DRX timer of the set of UEs is currently running or will run.

18. A user equipment (UE), the user equipment (UE) comprising: Memory; at least one transceiver; and at least one processor, the at least one processor being communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: selecting one or more initial resources for transmitting a sidelink positioning reference signal (SL-PRS) to a plurality of UEs participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a sidelink discontinuous reception (SL-DRX) active time of at least a set of UEs among the plurality of UEs; as well as The SL-PRS is sent to at least the set of UEs via the at least one transceiver.

19. The UE according to claim 18, wherein the number of the UE set comprises: all of the plurality of UEs, a minimum number of UEs among the plurality of UEs set by the location server for the positioning session, a minimum number of UEs among the plurality of UEs set by the anchor UE for the positioning session, a minimum number of UEs among the plurality of UEs set by the configuration of the positioning session, a minimum number of UEs among the plurality of UEs set by an upper layer of the UE, or A minimum number of UEs among the plurality of UEs for the positioning session of a certain type.

20. The UE of claim 18, wherein the at least one processor configured to select the one or more initial resources comprises the at least one processor configured to: For each of the one or more granted resources, determining whether the granted resource is scheduled within at least the SL-DRX active time of the set of UEs until the one or more initial resources are selected or a maximum number of selection attempts is met.

21. The UE of claim 20, wherein the at least one processor is further configured to: Sequential resource selection is performed for a subset of the set of UEs based on the maximum number of selection attempts being satisfied.

22. The UE of claim 18, wherein the at least one processor is further configured to: receiving, via the at least one transceiver, a first time window during which group resource selection is performed; receiving, via the at least one transceiver, a second time window during which sequential resource selection is performed; or Any combination of them.

23. The UE of claim 22, wherein the at least one processor is further configured to: for each resource selection opportunity within a resource selection window, determining a number of UEs that will be in SL-DRX active time for each resource within the resource selection window; and The one or more initial resources are selected based on the one or more initial resources having a highest number of UEs that will be in the SL-DRX active time.

24. The UE of claim 18, wherein the at least one processor is further configured to: receiving, via the at least one transceiver, a number of the plurality of UEs from a location server for the positioning session or an anchor UE for the positioning session, receiving the number of the set of UEs from the location server or the anchor UE via the at least one transceiver, or Any combination of them.

25. The UE of claim 18, wherein the at least one processor is further configured to: sequentially selecting one or more additional resources for transmitting additional SL-PRS to additional sets of the plurality of UEs other than the set of UEs until a minimum number of the plurality of UEs has been met, wherein the one or more additional resources are selected based on the one or more additional resources being scheduled within an SL-DRX active time of the additional set of the plurality of UEs; and The additional SL-PRS is sent to the additional set of the plurality of UEs via the at least one transceiver.

26. The UE of claim 18, wherein the at least one processor is further configured to: One or more resource grants for the positioning session are received via the at least one transceiver, at least one of the one or more resource grants including at least the one or more initial resources.

27. The UE of claim 26, wherein the at least one processor is further configured to: The one or more resource grants do not include at least one transmission resource scheduled within the SL-DRX active time of at least the set of UEs.

28. The UE of claim 18, wherein the at least one processor is further configured to: receiving a mode of resource selection from a location server or a base station via the at least one transceiver based on resources for the positioning session being allocated by the location server or the base station; or The pattern of resource selection is received from the anchor node via the at least one transceiver based on the resources for the positioning session being allocated by the anchor node.

29. A user equipment (UE), the user equipment (UE) comprising: means for selecting one or more initial resources for transmitting a sidelink positioning reference signal (SL-PRS) to a plurality of UEs participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a sidelink discontinuous reception (SL-DRX) active time of at least a set of UEs among the plurality of UEs; and Means for sending the SL-PRS to at least the set of UEs.

30. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: selecting one or more initial resources for transmitting a sidelink positioning reference signal (SL-PRS) to a plurality of UEs participating in a positioning session with the UE, wherein the one or more initial resources are selected based on the one or more initial resources being scheduled within a sidelink discontinuous reception (SL-DRX) active time of at least a set of UEs among the plurality of UEs; and The SL-PRS is sent to at least the set of UEs.

Images