DRX configuration for sidelink positioning

Abstract

Aspects of the disclosure relate to DRX configuration adaptation for SL positioning. A UE (800) may be configured to: participate (1102) in a positioning session with a group of UEs, receive CSI report settings; and configuring (1104) a DRX configuration comprising the DRX activity time. The UE (800) may be configured to: receive (1106) signaling information from at least one UE of the set of UEs; and in response to the reception of signaling information, adjusting (1108) the DRX activity time to include a time period corresponding to the transmission of the SL-PRS, where the signaling information includes timing information for the transmission of the SL-PRS.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and more particularly to adjusting a discontinuous reception ("DRX") configuration for transmitting a sidelink positioning reference signal ("SL-PRS"). Background Art

[0002] A wireless communication system may include one or more network communication devices, such as a base station, which may also be referred to as an evolved NodeB (eNB), a next generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices (which may also be referred to as user equipment (UE) or other suitable terms). A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers). Additionally, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology (RAT), fourth generation (4G) RAT, fifth generation (5G) RAT, and other suitable RATs above 5G (e.g., sixth generation (6G)).

[0003] Sidelink communication refers to point-to-point communication conducted directly between user equipment ("UE") devices. Thus, the UEs communicate with each other without relaying the communication via a mobile network (ie, without a base station). Summary of the invention

[0004] The article "one" before an element is not limited and is understood to refer to "at least one" of these elements or "one or more" of these elements. The terms "one", "at least one", "one or more" and "at least one of one or more" are interchangeable. As used herein (including in the claims), "or" used in a list of items (for example, a list of items beginning with phrases such as "at least one" or "one or more" or "one or two") indicates an inclusive list, so that, for example, a list of at least one of A, B or C means A or B or C or AB or AC or BC or ABC (i.e. A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, the example steps described as "based on condition A" can be based on condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on". In addition, as used herein (including in the claims), a "group" can include one or more elements.

[0005] Some implementations of the methods and apparatus described herein may include: a UE participating in a positioning session with a group of UEs; and configuring a DRX configuration including a DRX active time. The methods and apparatus described herein may also include: the UE receiving signaling information from at least one UE in the group of UEs; and in response to receiving the signaling information, adjusting the DRX active time to include a time period corresponding to the transmission of the SL-PRS, wherein the signaling information includes timing information for the transmission of the SL-PRS.

[0006] Some implementations of the methods and apparatus described herein may also include: the UE initiating a positioning session with a group of UEs; and the UE configuring a DRX configuration including a DRX active time. The methods and apparatus described herein may also include: the UE sending signaling information to at least one UE in the group of UEs; and the UE adjusting the DRX active time to include a time period corresponding to the reception of the signaling information and the SL-PRS, wherein the signaling information includes a request for transmission of the SL-PRS. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 An example of a wireless communication system according to aspects of the present disclosure is illustrated.

[0008] Figure 2 An example of a 3rd Generation Partnership Project (3GPP) New Radio (NR) protocol stack showing different protocol layers in a UE and a network according to aspects of the present disclosure is illustrated.

[0009] Figure 3 An example of a SL protocol stack showing different protocol layers in a pair of UEs according to aspects of the present disclosure is illustrated.

[0010] Figure 4 An example of a timing diagram for a multi-cell round trip time (Multi-RTT) measurement procedure according to aspects of the present disclosure is illustrated.

[0011] Figure 5 An example of distance estimation using a single-unit round trip time (RTT) positioning framework is illustrated in accordance with aspects of the present disclosure.

[0012] Fig. 6A An example of a relative positioning, variable coordinate system according to aspects of the present disclosure is illustrated.

[0013] Figure 6B Examples of relative positioning, variable and moving coordinate systems according to aspects of the present disclosure are illustrated.

[0014] Figure 6C An example of an absolute positioning, fixed coordinate system according to aspects of the present disclosure is illustrated.

[0015] Figure 7 An example of a beam-based positioning framework according to aspects of the present disclosure is illustrated.

[0016] Figure 8 An example of a user equipment (UE) 800 according to aspects of the present disclosure is illustrated.

[0017] Fig. 9 An example of a processor 900 according to aspects of the present disclosure is illustrated.

[0018] Fig.10 An example of a network device (NE) 1000 according to aspects of the present disclosure is illustrated.

[0019] Fig.11 A flow chart of a first method of DRX configuration adaptation for SL positioning, performed by an Rx UE, according to aspects of the present disclosure is illustrated.

[0020] Fig.12 A flow chart of a second method of DRX configuration adaptation for SL positioning, performed by an Rx UE, according to aspects of the present disclosure is illustrated.

[0021] Fig.13 A flowchart of a third method of DRX configuration adaptation for SL positioning, performed by an Rx UE, according to aspects of the present disclosure is illustrated.

[0022] Fig.14 A flowchart of a fourth method of DRX configuration adaptation for SL positioning, performed by a Tx UE according to aspects of the present disclosure, is illustrated.

[0023] Fig.15 A flowchart of a fifth method of DRX configuration adaptation for SL positioning, performed by a Tx UE, according to aspects of the present disclosure is illustrated.

[0024] Fig.16 A flowchart of a sixth method of DRX configuration adaptation for SL positioning, performed by a NE, according to aspects of the present disclosure is illustrated.

[0025] Fig.17 A flowchart of a seventh method of DRX configuration adaptation for SL positioning, performed by a NE, according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0026] In general, the present disclosure describes systems, methods, and apparatus for reporting CSI feedback with CQI values. In some embodiments, the method may be performed using computer executable code embedded on a computer readable medium. In some embodiments, the apparatus or system may include: a computer readable medium containing computer readable code, which, when executed by a processor, causes the apparatus or system to perform at least a portion of the following solution.

[0027] In a wireless communication network, CSI feedback is reported by a UE to the network, where the CSI feedback may take various forms based on CSI feedback report size, time and frequency granularity or other CSI reporting settings.

[0028] For CSI reporting in 3GPP NR Release 16 specifications (Rel-16), two types of codebooks are defined. The NR Type-I codebook uses multiple predefined matrices, from which selection is made by the user equipment (UE) report and / or RRC configuration. In contrast, the NR Type-II codebook is not based on a predefined table, but on a specifically designed mathematical formula with multiple parameters. The parameters in the formula are determined by the RRC configuration and / or UE report. The NR Type-II codebook is based on a more detailed CSI report and supports multi-user multiple input multiple output (MU-MIMO) communication.

[0029] In NR Rel-16, high-resolution CSI feedback reporting (i.e., Type-II) is specified, where the frequency granularity of the CSI feedback can be indirectly parameterized. For 3GPP NR Rel-16 Type-II codebooks with high resolution, the number of precoding matrix indicator (PMI) bits fed back from the UE in the next generation Node B (gNB) via uplink control information (UCI) may be very large (>1000 bits at large bandwidths), even for single-point transmission. The purpose of multi-panel transmission is to improve spectral efficiency, as well as the reliability and robustness of connections in different scenarios, and it covers both ideal and non-ideal backhaul. In order to improve the reliability of using multi-panel transmission, ultra-reliable low-latency communication (URLLC) under multi-panel transmission has been negotiated, where the UE can be served by multiple transmit-receive points (TRPs) forming a coordinated cluster, which may be connected to a central processing unit.

[0030] In addition, CSI feedback enhancement corresponding to scenarios with relatively high UE speeds is being studied. While one proposal is to report multiple CSI reports, each report including a rank indicator (RI) and / or PMI and / or CQI with lower periodicity (i.e., more frequent reporting) to address faster channel variations at high speeds, the disadvantage of this proposal is that the CSI feedback overhead is larger and the complexity of reporting / calculating multiple CSI reports at the UE is higher. While another proposal is to report a single CQI value corresponding to a time interval equivalent to the traditional CSI report periodicity value, the disadvantage of this proposal is that a single CQI value may not capture the channel variations within a single CSI report periodicity value.

[0031] In order to adapt to this high-speed scenario while maintaining similar service quality, a modified CSI framework including measurement and reporting is needed. At high speeds, the channel coherence time is expected to be lower than the traditional CSI reporting periodicity value, and therefore the channel quality may vary within a CSI reporting interval. Therefore, it may be necessary to enhance the CQI format. CQI enhancement is proposed for the CSI framework at high speeds. The proposed solution includes the following items:

[0032] According to a first solution, multiple CQI values ​​are fed back within a CSI report, where a reference CQI value is reported with high resolution (eg, subband (SB) format) and subsequent CQI values ​​are reported with lower resolution (eg, wideband (WB) format).

[0033] According to a second solution, the UE reports multiple CQI values ​​with a lower periodicity value (ie, more frequent reporting) compared to the PMI / RI reporting periodicity.

[0034] According to a third solution, only two CQI values ​​are fed back in the CSI report, and a configured (and / or reported and / or indicated) extrapolation method is utilized to infer the channel quality in intervals other than the two reference intervals corresponding to the two CQI values.

[0035] Aspects of the disclosure are described in the context of a wireless communication system.

[0036] Figure 1An example of a wireless communication system 100 according to aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be an NR network, such as a 5G network, an advanced 5G (5G-A) network, or a 5G ultra-wideband (5G-UWB) network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communication system 100 may support radio access technologies above 5G, such as 6G. Additionally, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0037] One or more NEs 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more NEs 102 described herein may be or include or may be referred to as network nodes, base stations, network elements, network functions, network entities, radio access networks (RAN), NodeBs, eNodeBs (eNBs), next generation NodeBs (gNBs), or other suitable terms. NE 102 and UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, NE 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0038] NE 102 can provide a geographic coverage area within which NE 102 can support services for one or more UEs 104. For example, NE 102 and UE 104 can support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, NE 102 can be mobile, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas can be associated with different NE 102.

[0039] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, etc.

[0040] The UE 104 may be capable of directly supporting wireless communications with other UEs 104 via a communication link. For example, the UE 104 may directly support wireless communications with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, the UE 104 may directly support wireless communications with another UE 104 via a PC5 interface.

[0041] NE 102 can support communication with CN 106, or communication with another NE 102, or both. For example, NE 102 can be connected to other NE 102 or CN 106 through one or more backhaul links (e.g., S1, N2, N2 or network interface). In some implementations, NE 102 can communicate directly with each other. In some other implementations, NE 102 can communicate with each other or communicate indirectly (e.g., via CN 106). In some implementations, one or more NE 102 may include a subcomponent, such as an access network entity, which may be an example of an access node controller (ANC). ANC can communicate with one or more UE 104 through one or more other access network transmission entities, which may be referred to as radio heads, smart radio heads or transmission-reception points (TRPs).

[0042] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include: control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)), and user plane entities that route packets or interconnect with external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearer, signal bearer, etc.) for one or more UEs 104 served by one or more NEs 102 associated with the CN 106.

[0043] The CN 106 may communicate with a packet data network via one or more backhaul links (e.g., via S1, N2, N2 or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. The UE 104 may establish a session (e.g., a protocol data unit (PDU) session, etc.) with the CN 106 via the NE 102. The CN 106 may use the established session (e.g., the established PDU session) to route traffic (e.g., control information, data, etc.) between the UE 104 and the application server. A PDU session may be an example of a logical connection between a UE 104 and a CN 106 (e.g., one or more network functions of the CN 106).

[0044] In the wireless communication system 100, the NE 102 and the UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, the NE 102 and the UE 104 may support different resource structures. For example, the NE 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the NE 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the NE 102 and the UE 104 may support various frame structures (i.e., multiple frame structures). The NE 102 and the UE 104 may support various frame structures based on one or more digital technologies.

[0045] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefixes. A first digital technology (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15kHz) and a conventional cyclic prefix. In some implementations, a first digital technology (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15kHz) may utilize one time slot for each subframe. A second digital technology (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a conventional cyclic prefix. A third digital technology (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60kHz) and a conventional cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120kHz) and a conventional cyclic prefix. A fifth digital technology (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a conventional cyclic prefix.

[0046] The time intervals of resources (e.g., communication resources) can be organized according to frames (also referred to as radio frames). Each frame can have a duration, for example, a duration of 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, a duration of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0047] Additionally or alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth digital technologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with the corresponding subcarrier spacings of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz may utilize a single time slot for each subframe, two time slots for each subframe, four time slots for each subframe, eight time slots for each subframe, and 16 time slots for each subframe, respectively. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots for a subframe may depend on the digital technology. For a conventional cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on the digital technology. It should be understood that references to a first digital technology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0048] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc. based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range representations FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4 to 1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some implementations, the NE 102 and the UE 104 can perform wireless communications on one or more operating frequency bands. In some implementations, FR1 can be used by the NE 102 and the UE 104 and other devices or apparatuses for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by the NE 102 and the UE 104 and other devices or apparatuses for short-range, high data rate capabilities.

[0049] FR1 may be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 may be associated with a first digital technology (e.g., μ=0) including a 15kHz subcarrier spacing, a second digital technology (e.g., μ=1) including a 30kHz subcarrier spacing, and a third digital technology (e.g., μ=2) including a 60kHz subcarrier spacing. FR2 may be associated with one or more digital technologies (e.g., at least 2 digital technologies). For example, FR2 may be associated with a third digital technology (e.g., μ=2) including a 60kHz subcarrier spacing, and a fourth digital technology (e.g., μ=3) including a 120kHz subcarrier spacing.

[0050] Figure 2 An example of an NR protocol stack 200 according to aspects of the present disclosure is illustrated. Figure 2 UE 206, RAN node 208, and 5G core network (5GC) 210 (e.g., including at least one AMF) are shown, but they represent a group of UEs 104 interacting with NE 102 (e.g., base station) and CN 106. As depicted, NR protocol stack 200 includes user plane protocol stack 202 and control plane protocol stack 204. User plane protocol stack 202 includes: physical (PHY) layer 212, medium access control (MAC) sublayer 214, radio link control (RLC) sublayer 216, packet data convergence protocol (PDCP) sublayer 218 and service data adaptation protocol (SDAP) layer 220. Control plane protocol stack 204 includes: PHY layer 212, MAC sublayer 214, RLC sublayer 216 and PDCP sublayer 218. Control plane protocol stack 204 also includes: radio resource control (RRC) layer 222 and non-access stratum (NAS) layer 224.

[0051] The AS layer 226 (also referred to as the "AS protocol stack") for the user plane protocol stack 202 consists of at least SDAP, PDCP, RLC and MAC sublayers and a physical layer. The AS layer 228 for the control plane protocol stack 204 consists of at least RRC, PDCP, RLC and MAC sublayers and a physical layer. Layer 1 (L1) includes the PHY layer 212. Layer 2 (L2) is divided into the SDAP layer 220, the PDCP sublayer 218, the RLC sublayer 216 and the MAC sublayer 214. Layer 3 (L3) includes the RRC layer 222 and the NAS layer 224 for the control plane, and includes, for example, an IP layer and / or a PDU layer (not depicted) for the user plane. L1 and L2 are referred to as "lower layers", while L3 and above (e.g., transport layer, application layer) are referred to as "high layers" or "upper layers".

[0052] The PHY layer 212 provides a transport channel to the MAC sublayer 214. The PHY layer 212 may use an energy detection threshold to perform a beam failure detection process, as described herein. In some embodiments, the PHY layer 212 may send an indication of a beam failure to a MAC entity at the MAC sublayer 214. The MAC sublayer 214 provides a logical channel to the RLC sublayer 216. The RLC sublayer 216 provides an RLC channel to the PDCP sublayer 218. The PDCP sublayer 218 provides a radio bearer to the SDAP sublayer 220 and / or the RRC layer 222. The SDAP sublayer 220 provides QoS flows to the core network (e.g., 5GC). The RRC layer 222 provides carrier aggregation and / or dual connectivity addition, modification, and release. The RRC layer 222 also manages the establishment, configuration, maintenance, and release of signaling radio bearers (SRBs) and data radio bearers (DRBs).

[0053] The NAS layer 224 is located between the UE 206 and the AMF in the 5GC 210. NAS messages are passed transparently through the RAN. The NAS layer 224 is used to manage the establishment of communication sessions and is used to maintain continuous communication with the UE 206 when the UE 206 moves between different cells in the RAN. In contrast, the AS layers 226 and 228 are located between the UE 206 and the RAN (i.e., the RAN node 208) and carry information through the wireless part of the network. Although Figure 2 Not depicted in , but an IP layer exists above the NAS layer 224, a transport layer exists above the IP layer, and an application layer exists above the transport layer.

[0054] The MAC sublayer 214 is the lowest sublayer in the L2 architecture of the NR protocol stack. Its connection with the PHY layer 212 below is through a transport channel, and its connection with the RLC sublayer 216 above is through a logical channel. Therefore, the MAC sublayer 214 performs multiplexing and demultiplexing between logical channels and transport channels: the MAC sublayer 214 in the transmitting side constructs a MAC PDU (also called a transport block (TB)) from a MAC service data unit (SDU) received through a logical channel, and the MAC sublayer 214 in the receiving side recovers a MAC SDU from a MAC PDU received through a transport channel.

[0055] The MAC sublayer 214 provides a data transfer service for the RLC sublayer 216 through a logical channel, which is a control logical channel carrying control data (e.g., RRC signaling) or a service logical channel carrying user plane data. On the other hand, data from the MAC sublayer 214 is exchanged with the PHY layer 212 through a transport channel, which is classified as UL or DL. Data is multiplexed into a transport channel according to how it is sent over the air.

[0056] The PHY layer 212 is responsible for the actual transmission of data and control information via the air interface, i.e., the PHY layer 212 carries all information from the MAC transport channel over the air interface on the transmission side. Some of the important functions performed by the PHY layer 212 include: coding and modulation, link adaptation (e.g., adaptive modulation and coding (AMC)), power control, cell search and random access (for initial synchronization and handover purposes), and other measurements for the RRC layer 222 (within the 3GPP system (i.e., NR and / or LTE system) and between systems). The PHY layer 212 performs transmission based on transmission parameters such as modulation scheme, coding rate (i.e., modulation and coding scheme (MCS)), number of physical resource blocks (PRBs), etc.

[0057] Note that the LTE protocol stack includes a similar structure to the NR protocol stack 200, except that the LTE protocol stack lacks the SDAP sublayer 220 in the AS layer 226, the EPC replaces the 5GC 510, and the NAS layer 224 is located between the UE 206 and the MME in the EPC. It should also be noted that the present disclosure distinguishes between protocol layers (such as the aforementioned PHY layer 212, MAC sublayer 214, RLC sublayer 216, PDCP sublayer 218, SDAP layer 240, RRC layer 222, and NAS layer 224) and transport layers (also referred to as "MIMO layers" or "data streams") in MIMO communications.

[0058] Figure 3 SL protocol stack 300 according to an embodiment of the present disclosure is depicted. Figure 3 A transmitting SL UE 302 (labeled as "TX UE") and a receiving SL UE 304 (labeled as "RX UE") are shown, but these represent a group of UEs communicating point-to-point via a PC5 interface, and other embodiments may involve different UEs. As depicted, the SL protocol stack 300 includes: a physical layer 306, a MAC sublayer 308, an RLC sublayer 310, a PDCP sublayer 312, and RRC and SDAP layers (depicted as a combined element "RRC / SDAP" 314), for the control plane and the user plane, respectively. The physical layer 306, the MAC sublayer 308, the RLC sublayer 310, the PDCP sublayer 312, and the RRC / SDAP layer 314 can perform substantially the same functions as described above with reference to the NR protocol stack 200, but support UE-to-UE communication between the TX UE 302 and the RX UE 304.

[0059] The AS protocol stack for the control plane in the SL protocol stack 300 is composed of at least RRC, PDCP, RLC and MAC sublayers and a physical layer. The AS protocol stack for the user plane in the SL protocol stack 300 is composed of at least SDAP, PDCP, RLC and MAC sublayers and a physical layer. L2 is divided into SDAP, PDCP, RLC and MAC sublayers. L3 includes an RRC sublayer for the control plane and includes, for example, an IP layer for the user plane. L1 and L2 are referred to as "lower layers", while L3 and above (e.g., transport layer, V2X layer, application layer) are referred to as "high layers" or "upper layers".

[0060] Regarding positioning performance requirements and positioning methods, for Rel-17, different positioning requirements are particularly strict in terms of accuracy, latency and reliability.

[0061] The following table 1 lists the positioning technologies supported in Rel-16. These technologies are defined in 3GPP Technical Specification (TS) 38.306.

[0062] Table 1: Supported Rel-16 UE positioning methods

[0063]

[0064]

[0065] Currently, the individual positioning techniques indicated in Table 1 can be configured and performed based on the requirements of the location management function (LMF) and the user equipment (UE) capabilities. The transmission of the positioning reference signal (PRS) enables the UE to perform UE positioning related measurements to enable the calculation of the UE's position estimate and is configured for each transmission reception point (TRP), where the TRP can transmit one or more beams.

[0066] The following RAT-related positioning technologies are supported in Rel-16: Downlink Time Difference of Arrival (DL-TDOA); Downlink Angle of Departure (DL-AoD); Multi-RTT; Enhanced Cell Identity (E-CID); Uplink Time Difference of Arrival (UL-TDOA); Uplink Angle of Arrival (UL-AoA).

[0067] At the UE, the DL-TDOA positioning method utilizes the DL Reference Signal Time Difference (RSTD) (and optionally, the DL PRS Reference Signal Received Power (RSRP)) of downlink signals received from multiple transmission points (TPs). The UE uses the assistance data received from the positioning server to measure the DL RSTD (and optionally, the DL PRS RSRP) of the received signal, and uses the resulting measurement together with other configuration information to position the UE relative to neighboring TPs.

[0068] At the UE, the DL-AoD positioning method utilizes the measured DL PRS RSRP of downlink signals received from multiple TPs. The UE uses the assistance data received from the positioning server to measure the DL PRS RSRP of the received signal and uses the resulting measurement with other configuration information to position the UE relative to neighboring TPs.

[0069] The Multi-RTT positioning method utilizes UE Rx-Tx measurements and DL PRS RSRP of downlink signals received from multiple TRPs measured by the UE, and gNB Rx-Tx measurements and UL Sounding Reference Signal RSRP (SRS-RSRP) measured at multiple TRPs of uplink signals sent by the UE.

[0070] Figure 4 An exemplary Multi-RTT process 400 is depicted. The UE measures UE Rx-Tx measurements (and optionally DL PRS RSRP of received signals) using assistance data received from a positioning server (e.g., LMF server) and TRP measures gNB Rx-Tx measurements (and optionally UL SRS-RSRP of received signals) using assistance data received from the positioning server. These measurements are used to determine the round trip time (RTT) at the positioning server, which is used to estimate the UE's position.

[0071] Figure 5 An example process 500 for relative distance estimation using RTT positioning techniques is depicted. The process 500 involves an LMF server 502, a gNB 504, and a plurality of UEs, including a first UE 506 (labeled as "UE1"), a second UE 508 (labeled as "UE2"), and a third UE 510 (labeled as "UE3"). The LMF server 502 may be an embodiment of the LMF 146, the gNB 504 may be an embodiment of the RAN node 208 and / or the NE 102, and the UE may be an embodiment of the UE 206, the TX UE 302, and / or the RX UE 304.

[0072] At step 1, the gNB-UE distance is determined as half the gNB-UE RTT multiplied by the speed of light. The gNB-UE RTT is calculated and used by the LMF server 502 to obtain the absolute position of the UE. Note that the LMF server 502 may use RTT measurements and beam directions from a single gNB 504 to obtain the absolute UE position. In other embodiments, the LMF server 502 may use RTT measurements from multiple TRPs to obtain the absolute UE position.

[0073] At step 2, the relative distance between UEs (i.e., UE-to-UE distance) may be calculated. Note that the relative UE-to-UE direction may also be calculated. UE1 506, UE2 508, and UE3 510 may determine the UE-to-UE distance and direction using the SL positioning techniques described below.

[0074] FIG. 6A to FIG. 6C Depicts an overview of absolute and relative positioning using different coordinate systems.

[0075] Fig. 6A An example of relative positioning using a variable coordinate system 600 is depicted. In some embodiments, the coordinate system 600 can be used to determine a relative positioning 616 between a first UE (labeled as "UE-1") 604 and a 5G positioning node such as a gNB 602 (having a fixed position) when the nodes are within 10 meters of each other. In some embodiments, the coordinate system 600 can be used to determine a relative positioning 618 between two or more UEs such as a second UE (labeled as "UE-2") 606 and a fourth UE (labeled as "UE-4") 610 when the UEs are within 10 meters of each other. In some embodiments, the coordinate system 600 can be used to determine a vertical position 620 of a third UE (labeled as "UE-3") 608 relative to a local ground plane at a relative height (or depth). In some embodiments, the coordinate system 600 may be used to determine a relative position 622 between a fifth UE (designated as "UE-5") 612 located outside of network coverage 626 and one or more UEs (e.g., UE-4) located within network coverage 628 when the UEs are in proximity. Additionally or alternatively, the coordinate system 600 may be used to determine a relative position 624 between UE-5 612 and a sixth UE (designated as "UE-6") 614 also located outside of network coverage 626. The depicted gNB may be an embodiment of a NE 102 and / or a RAN node 208, and the UE may be an embodiment of a UE 104, a UE 206, a TX UE 302, and / or a RX UE 304.

[0076] Figure 6BAn example of relative positioning using a variable and moving coordinate system 630 is depicted. Compared to system 600, in system 630, the gNB 632 is moving, so the coordinate system also moves relative to a fixed ground location. In some embodiments, the coordinate system 630 can be used to determine the relative longitudinal position 634 (e.g., with an accuracy of less than 0.5m error) for UEs supporting V2X applications for close-range queuing. In some embodiments, the coordinate system 630 can be used to determine the relative lateral position 636 (e.g., with an accuracy of less than 0.1m error) between UEs supporting V2X applications. The depicted gNB 632 can be an embodiment of the NE 102 and / or the RAN node 208, and the UE can be an embodiment of the UE 104 and / or the UE 206.

[0077] Figure 6C An example of absolute positioning using a fixed coordinate system 640 is depicted. Compared to systems 600 and 630, there are multiple fixed gNBs in the fixed coordinate system 640. In some embodiments, the coordinate system 640 can be used to determine an absolute position 642 of a UE 644 using a first gNB 646, a second gNB 648, and a third gNB 650. In some embodiments, the absolute position can be expressed using x, y, and z coordinates. The gNB depicted can be an embodiment of a NE 102 and / or a RAN node 208, and the UE can be an embodiment of a UE 104 and / or a UE 206.

[0078] Referring again to the RAT-dependent positioning techniques, in the E-CID positioning method, the position of the UE 206 is estimated using knowledge of its serving ng-eNB, gNB, and cell, and is based on Uu (e.g., LTE) signals. Information about the serving ng-eNB, gNB, and cell may be obtained through paging, registration, or other methods. The NR E-CID positioning method refers to a technique that uses additional UE measurements and / or NR radio resource and other measurements to improve the UE position estimate using NR signals.

[0079] Although the NR E-CID positioning method can utilize some of the same measurements as the measurement control system in the RRC protocol, the UE 206 should generally not perform additional measurements solely for positioning purposes; that is, the positioning process does not supply measurement configuration or measurement control messages, and the UE 206 reports its available measurements rather than being required to take additional measurement actions.

[0080] The UL-TDOA positioning method utilizes the arrival time difference (and optionally, UL SRS-RSRP) of an uplink signal transmitted from the UE 206 at multiple reception points. The reception points measure the UL TDOA (and optionally, UL SRS-RSRP) of the received UL signal using assistance data received from the positioning server, and use the resulting measurements together with other configuration information to estimate the position of the UE 206.

[0081] The UL-AoA positioning method utilizes the azimuth and zenith angles of arrival measured at multiple reception points of uplink signals transmitted from the UE 206. The reception points measure the azimuth angle of arrival (A-AoA) and / or the zenith angle of arrival (Z-AoA) of the received signal using assistance data received from a positioning server, and use the resulting measurements together with other configuration information to estimate the position of the UE 206.

[0082] RAT-dependent positioning technology involves 3GPP RAT and core network entities to perform position estimation of UE 206, which is different from RAT-independent positioning technology that relies on Global Navigation Satellite System (GNSS), Inertial Measurement Unit (IMU) sensors, WLAN and Bluetooth technologies to perform positioning of the target device (i.e., UE 206).

[0083] The following RAT-independent positioning technologies are supported in Rel-16: network-assisted GNSS, air pressure sensor positioning, WLAN positioning, Bluetooth positioning, TBS positioning, and motion sensor positioning.

[0084] The network-assisted GNSS (Global Navigation Satellite System) method utilizes a UE 206 equipped with a radio receiver capable of receiving GNSS signals. In the 3GPP specifications, the term GNSS covers both Global Navigation Satellite Systems and Regional / Augmented Navigation Satellite Systems.

[0085] Examples of global navigation satellite systems include: Global Positioning System (GPS), modernized GPS, Galileo, Global Navigation Satellite System (GLONASS) and BeiDou Navigation Satellite System (BDS). Regional navigation satellite systems include Quasi-Zenith Satellite System (QZSS), while many augmentation systems are classified under the general term of Space-Based Augmentation System (SBAS) and provide regional augmentation services. In this concept, different GNSS (e.g., GPS, Galileo, etc.) can be used alone or in combination to determine the location of UE 206.

[0086] Regarding air pressure sensor positioning, the air pressure sensor method utilizes an air pressure sensor to determine the vertical component of the position of the UE 206. The UE 206 measures the air pressure (optionally with the aid of assistance data) to calculate the vertical component of its position or sends the measurement to a positioning server for position calculation. This method should be combined with other positioning methods to determine the 3D position of the UE 206.

[0087] Regarding WLAN positioning, the WLAN positioning method utilizes WLAN measurements (e.g., WLAN AP identifiers, and (optionally) signal strength or other measurements) and a database to determine the location of UE 206. UE 206 measures the signals received from the WLAN APs (optionally with assistance data) to send the measurements to a positioning server for position calculation. Using the measurement results and a reference database, the location of UE 206 is calculated. Alternatively, UE 206 utilizes WLAN measurements and (optionally) WLAN AP assistance data provided by a positioning server to determine its location.

[0088] Regarding Bluetooth positioning, the Bluetooth positioning method utilizes Bluetooth measurements (beacon identifiers and (optionally) other measurements) to determine the location of UE 206. UE 206 measures the signals received from Bluetooth beacons. Using the measurement results and a reference database, the location of UE 206 is calculated. The Bluetooth method can be combined with other positioning methods (e.g., WLAN) to improve the positioning accuracy of UE 206.

[0089] The TBS consists of a network of ground-based transmitters that broadcast signals for positioning purposes only. With regard to TBS positioning, the current types of TBS positioning signals are Metropolitan Beacon System (MBS) signals and PRS. The UE 206 measures the received TBS signals, optionally with the help of assistance data, to calculate its position or sends the measurements to a positioning server for position calculation.

[0090] Regarding IMU / motion sensor positioning, this method utilizes different sensors (such as accelerometers, gyroscopes, magnetometers) to calculate the displacement of UE 206. UE 206 estimates the relative displacement based on a reference position and / or a reference time. UE 206 sends a report including the determined relative displacement, which can be used to determine the absolute position. This method should be used together with other positioning methods for hybrid positioning.

[0091] Figure 7A diagram 700 is shown for NR beam-based positioning measurements and reference signals (RS) according to an embodiment of the present disclosure. Here, downlink positioning reference signals (DL-PRS) can be sent by different base stations (serving gNB and neighboring gNB) using narrow beams on FR1 (i.e., frequency from 410 MHz to 7125 MHz) and FR2 (i.e., frequency from 24.25 GHz to 52.6 GHz), which is relatively different from LTE where PRS is sent over the entire cell. Figure 7 As illustrated in the figure, the UE 206 can receive DL-PRS from a neighboring first gNB / TRP (labeled as "gNB1-TRP1") 704, from a neighboring second gNB (labeled as "gNB2-TRP1") 706, and from a third gNB / TRP (labeled as "gNB3-TRP1") 708 which serves as a reference or serving gNB.

[0092] Here, the DL-PRS may be locally associated with a DL-PRS resource identifier (ID) and a resource set ID for a base station (i.e., a TRP). In the depicted embodiment, each gNB 704, 706, 708 is configured with a first resource set ID (depicted as "resource set ID #0") 710 and a second resource set ID (depicted as "resource set ID #1") 712. As depicted, UE 206 receives DL-PRS on the transmit beam; here, DL-PRS is received from gNB1-TRP1 704 on DL-PRS resource ID#3 in the second resource set ID (resource set ID#1) 712, DL-PRS is received from gNB2-TRP1 706 on DL-PRS resource ID#3 in the first resource set ID (resource set ID#0) 710, and DL-PRS is received from gNB3-TRP1 708 on DL-PRS resource ID#1 in the second resource set ID (resource set ID#1) 712.

[0093] Similarly, UE positioning measurements (such as reference signal time difference (RSTD) and PRS RSRP measurements) are made between different beams (e.g., between different DL PRS resource pairs or DL ​​PRS resource sets) - rather than between different cells as is the case in LTE. The LMF server 702 uses the UE positioning measurements to determine the location (e.g., absolute location) of the UE. In addition, additional UL positioning methods for the network are utilized to calculate the location of the target UE. Tables 2 and 3 show the mapping of reference signals to measurements required for each supported RAT-related positioning technique at the UE and gNB, respectively.

[0094] Table 2: UE measurements used to implement RAT-dependent positioning techniques

[0095]

[0096] Table 3: gNB measurements implementing RAT-dependent positioning techniques

[0097]

[0098] Regarding RAT-related positioning measurements, different DL measurements required for the supported RAT-related positioning techniques, including DL PRS-RSRP, DL RSTD, and UE Rx-Tx time difference, are shown in Table 4. The following measurement configurations are specified as follows: A) 4 pairs of DL RSTD measurements can be performed for each pair of cells (each measurement is performed between different DL PRS resource pairs / resource sets with a single reference timing); B) 8 DL PRS RSRP measurements can be performed on different DL PRS resources from the same cell.

[0099] Table 4: DL measurements required for DL-based positioning techniques

[0100]

[0101]

[0102] The integrity and reliability of the position estimate are defined by the following parameters: Alarm Limit (AL); Time to Alarm (TTA); Target Integrity Risk (TIR); Protection Level (PL).

[0103] The AL parameter indicates the maximum permissible positioning error so that the positioning system can be used for the intended application. If the positioning error exceeds the AL parameter, operation is dangerous and the positioning system should be declared unusable for the intended application to prevent loss of integrity. Note that when the AL parameter defines the positioning error in the horizontal plane or on the vertical axis, it is called the horizontal alarm limit (HAL) or the vertical alarm limit (VAL), respectively.

[0104] The TTA parameter indicates the probability that the positioning error exceeds the AL parameter without alerting the user within the required time defined by the TTA parameter.

[0105] The TIR parameter indicates the maximum allowable elapsed time from when the positioning error exceeds the AL parameter to when the function providing position integrity issues a corresponding alarm. Note that the TIR parameter is usually defined as a probability for each certain time unit (e.g., per hour, per second, or per independent sample).

[0106] The PL parameter is a real-time upper limit on the positioning error at the required confidence level, where the confidence level is determined by the TIR probability. PL is a statistical upper limit on the positioning error (PE), which ensures that the probability that the true error per unit time is greater than AL and PL is less than or equal to AL (for a duration greater than TTA) is less than the required TIR, that is, PL satisfies the following inequality:

[0107] The probability per unit time [when the duration exceeds TTA, ((PE>AL)&(PL<=AL))] < the required TIR

[0108] For the purpose of this disclosure, a positioning-related reference signal may be referred to as a reference signal used for positioning process / purpose in order to estimate the position of a target UE, such as a PRS, or based on an existing reference signal, such as a channel state information reference signal (CSI-RS) or a sounding reference signal (SRS); a target UE may be referred to as a device / entity whose position / positioning is to be determined. In various embodiments, the term "PRS" may refer to any signal that may be used for positioning, such as a reference signal, even if the signal is not primarily used for positioning.

[0109] SL positioning technologies include, but are not limited to: RTT type solutions using SL (including both unilateral (also known as one-way) RTT and bilateral (also known as two-way) RTT); sidelink angle of arrival (SL-AoA) (including both A-AoA and Z-AoA); SL-TDOA (utilizing SL RSTD (and optionally SL PRS RSRP) of SL signals received from multiple TPs at the UE); sidelink angle of departure (SL-AoD) (corresponding to the method of RSRP and / or RSRPP measurement, similar to the DL-AoD method in Uu, including both azimuth departure angle (A-AoD) and zenith departure angle (Z-AoD)).

[0110] Regarding SL DRX operation, when SL DRX is configured, the active time includes the following time: A) when sl-drx-onDurationTimer or sl-drx-InactivityTimer is running; or B) when sl-drx-RetransmissionTimer is running; or C) when no SL-CSI report MAC CE is received, during the sl-LatencyBoundCSI-Report period configured by RRC; or D) when SL-CSI report MAC CE is received, during the time between the request to transmit the SL-CSI report and the reception of the SL-CSI report MAC CE; or E) during the time slot associated with the announced periodic transmission of SL-SCH data sent by the UE.

[0111] When one or more SL DRXs are configured, and if multiple SL DRX cycles mapped to multiple SL-QoS-Profiles of the destination Layer 2ID and the cast type of interest are associated with multicast or broadcast, the MAC entity selects one sl-drx-cycle with the shortest length among the multiple SL DRX cycles mapped to the multiple SL-QoS-Profiles associated with the destination Layer 2ID. Additionally, the MAC entity selects one sl-drx-onDurationTimer with the longest length among the multiple SL DRX on-duration timers mapped to the multiple SL-QoS-Profiles associated with the destination Layer 2ID.

[0112] When one or more SL DRX are configured, and if the sl-drx-HARQ-RTT-Timer expires, then if the data of the corresponding side link process is not successfully decoded, or if the hybrid automatic repeat request ("HARQ") feedback (i.e., negative acknowledgment) for unicast is not sent due to UL / SL priority, then the MAC entity starts the sl-drx-RetransmissionTimer for the corresponding side link process in the first time slot after the sl-drx-HARQ-RTT-Timer expires.

[0113] When the broadcast type is multicast or broadcast as indicated by higher layers, sl-drx-StartOffset and sl-drx-SlotOffset are derived from the following equations:

[0114] sl-drx-StartOffset (ms) = destination layer 2 ID modulo sl-drx-Cycle;

[0115] sl-drx-SlotOffset (ms) = destination layer 2 ID modulo the number of slots in one subframe.

[0116] When the broadcast type is multicast or broadcast, and if the SL DRX cycle is used, and [(SFN×10)+subframe number] modulo (sl-drx-Cycle)=sl-drx-StartOffset, the MAC entity starts sl-drx-onDurationTimer after sl-drx-SlotOffset from the start of the subframe.

[0117] If the SL DRX is in the active time, the MAC entity monitors the SCI (i.e., the first phase SCI and the second phase SCI) in this SL DRX. Then, if the SCI indicates a new SL transmission, and if the source layer 1ID of the SCI is equal to the 8 least significant bits ("LSBs") of the expected destination layer 2ID, and the destination layer 1ID of the SCI is equal to the 16 LSBs of the expected source layer 2ID, and the broadcast type indicator in the SCI is set to unicast, then the MAC entity starts (or restarts) the sl-drx-InactivityTimer for the corresponding source layer 2ID and destination layer 2ID pair after the first time slot of the SCI reception.

[0118] In addition, if the SCI indicates a new SL transmission, and if the destination Layer 1 ID of the SCI (i.e., Phase 2 SCI) is equal to the 16 LSBs of the expected destination Layer 1 ID, and the broadcast type indicator in the SCI is set to multicast, then the MAC entity selects a sl-drx-InactivityTimer whose length is the maximum of multiple SL DRX inactivity timers (SL DRX Inactivity timers) of multiple SL-QoS-Profiles mapped to the destination Layer 2 ID associated with the destination Layer 1 ID of the SCI. Additionally, the MAC entity starts (or restarts) the sl-drx-InactivityTimer for the corresponding destination Layer 2 ID after the first timeslot of SCI reception.

[0119] When SL DRX is in active time, and if SCI indicates SL transmission, then if the next retransmission opportunity is scheduled in SCI, the MAC entity derives the sl-drx-HARQ-RTT-Timer from the retransmission resource timing of the next retransmission resource in SCI. Otherwise, the MAC entity uses the sl-drx-HARQ-RTT-Timer configured by the higher layer.

[0120] When SCI indicates SL transmission, if PSFCH resources for the SL authorization associated with the SCI are not configured, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the time slot after the end of the PSSCH transmission (i.e., the currently received PSSCH).

[0121] However, if PSFCH resources for SL grant associated with SCI are configured, then if HARQ feedback is enabled by SCI and the broadcast type indicator in SCI is set to unicast, or if HARQ feedback is enabled by SCI and the broadcast type indicator in SCI is set to groupcast and positive-negative confirmation is selected, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the first time slot after the end of the corresponding PSFCH transmission carrying the SL HARQ feedback. Alternatively, when SL HARQ feedback is not sent due to UL / SL priority, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the first time slot after the end of the corresponding PSFCH resources used for SL HARQ feedback.

[0122] When PSFCH resources for SL grant associated with SCI are configured, if HARQ feedback is enabled by SCI and the broadcast type indicator in SCI is set to groupcast and only negative acknowledgment is selected, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the first time slot after the end of the corresponding PSFCH transmission carrying the SLHARQ feedback. Alternatively, when SL HARQ feedback is not sent due to UL / SL priority, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the first time slot after the end of the corresponding PSFCH resource for SL HARQ feedback. Alternatively, when the SL HARQ feedback is positive acknowledgment, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the first time slot after the end of the corresponding PSFCH resource for SL HARQ feedback.

[0123] When PSFCH resources are configured for SL grants associated with SCI, if HARQ feedback is disabled by SCI and no (multiple) resources are scheduled in the SCI for one or more retransmission opportunities, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding side link process in the time slot after the end of the PSFCH resources.

[0124] When PSFCH resources are configured for SL grants associated with SCI, then if HARQ feedback is disabled by SCI and (multiple) resources for one or more retransmission opportunities are scheduled in SCI, the MAC entity starts the sl-drx-HARQ-RTT-Timer for the corresponding sidelink process in the time slot after the end of the PSSCH transmission (i.e., the currently received PSSCH). In addition, the MAC entity stops the sl-drx-RetransmissionTimer for the corresponding sidelink process.

[0125] When the broadcast type is multicast or broadcast, if a SL DRX command MAC CE is received for a source layer 2ID and destination layer 2ID pair for unicast, the MAC entity stops the sl-drx-onDurationTimer for the source layer 2ID and destination layer 2ID pair for unicast. Additionally, the MAC entity stops the sl-drx-InactivityTimer for the source layer 2ID and destination layer 2ID pair for unicast.

[0126] Regarding UE behavior when sending SL-SCH data during SL DRX operation, the UE sending SL-SCH data should remain aligned with its intended UE receiving SL-SCH data regarding the SL DRX active time as described above. In addition, the UE sending SL-SCH data determines the SL DRX active time based on the SL DRX timer (e.g., sl-drx-onDurationTimer, sl-drx-InactivityTimer, sl-drx-RetransmissionTimer) running at the (multiple) UEs receiving the SL-SCH data or the SL DRX timer (e.g., sl-drx-onDurationTimer, sl-drx-InactivityTimer, sl-drx-RetransmissionTimer) to be run in the future.

[0127] The UE may select resources for the initial transmission of the multicast within the time that the sl-drx-onDurationTimer or sl-drx-InactivityTimer at the destination is running. Note that if the initial transmission causes the sl-drx-RetransmissionTimer to be started at the receiving UE, the UE may assume that the resources for the retransmission are within the active time.

[0128] According to the current 3GPP specifications, SL DRX operation does not apply to SL-PRS transmissions. This can lead to a situation where a UE participating in a positioning session is not awake and not ready to receive SL-PRS transmissions from the initiating UE. On the other hand, if a UE participating in a sidelink positioning session is always active and monitoring for potential SL-PRS transmissions, this can harm battery consumption. This negative impact can be avoided by extending the SL DRX scheme to also apply to SL-PRS transmissions.

[0129] This disclosure details a solution for enhancing distributed resource allocation for UEs / devices performing SL positioning, particularly considering positioning techniques that require involving one or more UEs. An overview of the solution is presented as follows:

[0130] In the first set of solutions, the UE considers the transmission of SL-PRS as active time. The following solutions describe how to make the Rx UE aware of the DRX configuration / timing. For example, for unicast, there may be some link establishment procedures with SL-PRS configuration exchange. The Tx UE informs the Rx UE when it sends SL-PRS. The following solutions describe how the Rx UE can inform the Tx UE of its DRX configuration, in such an embodiment, the Tx UE sends SL-PRS during active time. According to some solutions, the unicast SL-PRS is coordinated between the target UE and the anchor UE.

[0131] In another set of solutions, multicast / broadcast SL-PRS may be treated like a service (i.e., corresponding to a predefined active time / DRX configuration). In some solutions, the UE treats the DRX solution for SL-PRS similar to a data service. For example, there may be a set of predefined SL-PRS DRX configurations where the UE selects a specific solution based on the QoS / accuracy / method required for the location service. In some solutions, one DRX configuration may contain SL-PRS to / from multiple UEs.

[0132] Although presented as different solutions, one or more of the solutions described herein may be implemented in combination with each other to coordinate DRX operation with SL-PRS.

[0133] As used herein, the initiator device that initiates the SL positioning / ranging session can be a network entity (e.g., gNB, LMF), UE, and / or roadside unit ("RSU"). RSU refers to a traffic infrastructure entity (e.g., an entity that sends speed notifications or other V2X-related notifications). An RSU that performs UE-like behavior is called a UE-type RSU, while an RSU that performs BS-like behavior is called a gNB-type RSU.

[0134] As used herein, a responder device responds to a SL positioning / ranging session from an initiator device, which may be a network entity (e.g., gNB, LMF), UE, and / or RSU.

[0135] As used herein, a target UE refers to a UE of interest, whose location (absolute location or relative location) is to be acquired by the network and / or by the UE itself.

[0136] Sidelink positioning as used in this article refers to the use of a reference signal sent through the SL (ie, PC5 interface) to obtain absolute position, relative position, or ranging information.

[0137] Ranging as used herein refers to determining the distance and / or direction between a UE and another entity (eg, an anchor UE).

[0138] As used herein, SL-PRS refers to a reference signal sent through the SL for positioning purposes.

[0139] SL-PRS (pre-) configuration: (pre-) configuration parameters of SL-PRS, such as time-frequency resources (not excluding other parameters), including its bandwidth and periodicity.

[0140] As used herein, an anchor UE refers to a UE that supports positioning of a target UE, for example, sending and / or receiving a reference signal for positioning through a SL interface, providing positioning related information, etc. An anchor UE may also be referred to as a SL reference UE.

[0141] As used herein, an assisting UE refers to a UE that supports ranging / sidelink positioning between a SL reference UE and a target UE through PC5 when direct ranging / sidelink positioning between the SL reference UE / anchor UE and the target UE cannot be supported. Measurements / results of ranging / sidelink positioning between the assisting UE and the SL reference UE and between the assisting UE and the target UE are determined and used to derive ranging / sidelink positioning results between the target UE and the SL reference UE.

[0142] As used in this article, the SL positioning server UE refers to a UE that provides location server functionality (instead of LMF) for sidelink positioning and ranging via a sidelink. It interacts with the target UE, reference UE, auxiliary UE, and already located UE as needed to calculate the position of the target UE.

[0143] As used in this article, the SL positioning client UE refers to a UE that provides position calculation for SL positioning and ranging based services. It interacts with other UEs through PC5 as needed to calculate the position of the target UE. If position calculation is supported, the target UE or SL reference UE can act as a SL positioning server UE.

[0144] As used herein, a SL positioning node may refer to a network entity and / or device / UE participating in a SL positioning session, such as a LMF (location server), a gNB, a UE, an RSU, an anchor UE, an initiator UE and / or a responder UE.

[0145] As used herein, a configuration entity refers to a network node or device / UE that is capable of configuring time-frequency resources and related SL positioning configuration.

[0146] Regarding the positioning session, assuming that the positioning server (e.g., SL positioning server UE) has received a location request for a given target UE, which triggers that a positioning session will be initiated. The positioning server can exchange messages with the target UE - that is, the lower protocol layers can provide for the transmission of positioning protocol level messages.

[0147] The first transaction of a positioning session is a capability exchange (e.g., LPP request / offer capability). This information exchange makes the server aware of the UE positioning capabilities (GNSS support, supported cellular network measurements). Based on this information, the server can make a decision about the positioning method to be used based on both the UE capabilities and the requested location quality (response time, accuracy). Similar to a PDU session (which is used for data transmission), a positioning session is used to support location-based services.

[0148] An embodiment of the first solution involves adjusting the DRX configuration for SL positioning. According to the first solution, one or more UEs participating in the SL positioning session regard the time slot / symbol (or any time domain configuration) in which the SL-PRS transmission is configured as the DRX active time, for example, the Rx UE (responder UE) should be prepared to receive the SL-PRS from the Tx UE (or initiator UE). According to one implementation of the first solution, the Rx UE regards the time slot in which the Tx UE sends the SL-PRS as the active time.

[0149] In some embodiments, the Tx UE notifies the Rx UE of the SL-PRS configuration / transmission. For example, for SL-PRS resource allocation for Mode-1, the Tx UE may receive resource allocation for the SL-PRS from the gNB (e.g., RAN node 208). In this case, the Tx UE forwards the SL resource / configuration for the SL-PRS to the (multiple) related Rx UEs.

[0150] According to one implementation of the first solution, the Tx UE notifies the Rx UE of the SL-PRS transmission via a PC5 RRC message. In one example, the Tx UE notifies the Rx UE of the SL-PRS configuration / transmission timing using a PC5-RRC message (e.g., an RRCReconfigurationSidelink message). In another implementation of the first solution, a new positioning protocol message may be used to deliver the SL-PRS configuration to the Rx UE. In one example, the Tx UE notifies the Rx UE of the SL-PRS configuration / transmission timing using a ProvideSLAssistanceData message. In one embodiment, the positioning protocol used is the SL Positioning Protocol ("SLPP"). In another embodiment, the positioning protocol used is the Ranging SL Positioning Protocol ("RSPP").

[0151] According to another implementation of the first solution, the Tx UE uses MAC control signaling to inform the Rx UE of future SL-PRS transmissions. In one example, a new MAC CE is introduced that carries information about upcoming SL-PRS transmissions. According to one aspect of the first solution, the UE considers the SL resources indicated for the reserved SL-PRS transmission as part of the active time.

[0152] According to another alternative implementation of the first solution, the sidelink control information ("SCI") indicates the presence of the corresponding SL-PRS transmission and information about future SL-PRS transmissions. In one example, a one-bit field within the SCI indicates the SL resources used for the SL-PRS transmission and the associated transmission parameters. According to one implementation of the first solution, a new field set to "0" indicates that the SCI carries control information on the associated PSSCH, as in the conventional scheme, while a field set to "1" indicates that the control information refers to the SL-PRS transmission. In one example, the SCI indicates information derived from reserved resources for additional future SL-PRS transmissions.

[0153] An embodiment of the second solution relates to the behavior of the UE with respect to the DRX timer. According to the second solution, one or more UEs participating in the SL positioning session do not start the sl-drx-InactivityTimer / sl-DRX-GC-InactivityTimer for the case where an SCI is received during the active time determined by the SL-PRS transmission opportunity. Unlike the currently defined DRX process, according to an implementation of the second solution, the Rx UE does not start the sl-drx-InactivityTimer / sl-DRX-GC-InactivityTimer in response to receiving an SCI indicating SL resource / SL-PRS transmission (without indicating SL data transmission). Even if the UE considers the time slots in which SL-PRS from the peer UE is expected to be active time, different DRX behaviors are applied for those time slots that are part of the active time.

[0154] An embodiment of the third solution relates to the behavior of the UE with respect to SL transmissions. According to the third solution, an SCI indicating the transmission of an SL-PRS is not considered to indicate a new SL transmission. The consequence of not considering an SCI indicating the transmission of an SL-PRS as indicating a new SL transmission is that the UE does not start a sl-drx-InactivityTimer / sl-DRX-GC-InactivityTimer in response to reception of an SCI.

[0155] An embodiment of the fourth solution relates to the behavior of the UE with respect to the DRX timer. According to the fourth solution, the RxUE does not start the sl-drx-HARQ-RTT-Timer in response to receiving an SCI indicating the transmission of SL-PRS. Since no HARQ protocol is applied to SL-PRS transmission, i.e., there is no SL-SCH / TB, there is no need to extend the active time by starting the sl-drx-HARQ-RTT-Timer and the sl-drx-RetransmissionTimer in sequence. According to the DRX process specified for the sidelink, an sl-drx-HARQ-RTT-Timer is maintained for each HARQ process. However, SL-PRS transmission has no associated HARQ process.

[0156] An embodiment of the fifth solution involves configuring a gNB (or other network entity) with a set of DRX configurations for SL positioning. According to the fifth solution, the SL positioning UE uses a predefined DRX mode (e.g., configured by the gNB) for receiving / transmitting SL-PRS. The DRX mode includes an active time (or on-duration), idle time, offset, and number of transmission opportunities for the SL-PRS. In one example, a predefined DRX mode is configured for each resource pool. In some embodiments, there may be a set of predefined DRX modes for SL-PRS, for example, depending on the required SL positioning QoS / accuracy of the associated positioning method and the received SL positioning / ranging service request.

[0157] In one implementation of the fifth solution, a UE (e.g., a Tx UE) determines a predefined DRX mode based on positioning accuracy defined for different positioning methods. For example, SL positioning can be treated as a SL service with associated QoS / accuracy requirements, where the associated QoS / accuracy requirements are used to select one of a set of predefined DRX configurations. In another implementation of the fifth solution, a UE (e.g., a Tx UE) determines a predefined DRX mode based on a required SL positioning delay to achieve end-to-end absolute / relative positioning determination / estimation.

[0158] In another implementation of the fifth solution, the UE (e.g., Tx UE) determines a predefined DRX mode based on the required SL positioning reliability associated with, for example, some integrity metric (such as PL, TTA, AL or any other reliability metric) to ensure the SL positioning reliability of the absolute / relative positioning determination / estimation. In other embodiments, the RAN informs the UE which predefined DRX mode to use, for example, depending on the associated positioning method, the required SL positioning QoS / accuracy and the received SL positioning / ranging service request.

[0159] According to certain embodiments, each SL-PRS configuration is associated with an identifier / indicator that is used as a reference for positioning accuracy characteristics, e.g., also referred to hereinafter as an accuracy QoS indicator ("AQI"). In one implementation of the fifth solution, a UE (e.g., a Tx UE) selects a predefined DRX pattern for transmission / reception of SL-PRS, which is selected based on the AQI of the corresponding SL-PRS transmission.

[0160] In one implementation of the fifth solution, the predefined DRX configuration consists of an on-duration pattern and a slot / frame offset. In such an embodiment, there is no need to have a sl-drx-InactivityTimer or other timers (such as sl-drx-RetransmissionTimer, etc.) configured in the predefined DRX configuration.

[0161] An embodiment of the sixth solution involves aligning DRX configurations between SL positioning members. According to the sixth solution, the target UE (e.g., the target UE sending the SL positioning request) regards the time between the transmission of the request for SL-PRS report / transmission and the reception of the SL-PRS as the active time. According to one implementation of the sixth solution, the target UE that sends a request for SL-PRS to one or more SL UEs (e.g., sends a MAC CE or SCI indicating a SL-PRS request) remains in the active time after the transmission request until the SL-PRS is received.

[0162] An embodiment of the seventh solution relates to resource selection for SL positioning taking into account the DRX configuration. According to the seventh solution, the Tx UE selects SL resources for SL-PRS transmission within the active time of the destination / Rx UE. This means that the Tx UE (i.e., the UE that is sending the SL-PRS and therefore selecting the SL resources in the Mode-2 resource allocation) needs to consider the DRX configuration / active time of the destination UE, and the Tx UE sends the SL-PRS to the destination UE. In other words, the Tx UE is only allowed to send within the active time of the Rx UE.

[0163] According to one implementation of the seventh solution, when the Tx UE performs a resource selection process for the SL-PRS, it needs to consider the active time of the destination when selecting the SL resource for SL-PRS transmission, so that only the SL resources within the active time of the destination are valid candidates for SL-PRS transmission. In one example, the Tx UE determines the destination ID for the SL-PRS transmission. Therefore, the SL-PRS transmission will only occur within the active time of the destination UE.

[0164] According to one implementation of the seventh solution, the UE sending the SL-PRS aligns its DRX configuration / activity time with the configuration / activity time of the destination UE receiving the SL-PRS. According to another implementation, the configuration entity (e.g., SL positioning server UE, LMF, gNB) is made aware of the activity time configuration of one or more destination / responder UEs. Therefore, the configuration entity can notify the UE sending the SL-PRS (e.g., anchor node, reference UE, etc.) of the activity time of one or more destination / responder UEs (e.g., target UE).

[0165] An embodiment of the eighth solution relates to MAC layer DRX considerations for SL positioning. According to the eighth solution, from the perspective of the MAC layer, the UE does not regard the SL-PRS transmission as a SL transmission. According to the current 3GPP standard, certain timers are specified in the MAC layer to be triggered based on sidelink transmission and / or reception. For example, if an authorization for SL transmission is received, the SL UE will trigger certain DRX-related timers, including but not limited to DRX timers, HARQ retransmission timers, etc. Therefore, by not considering the SL-PRS as a SL transmission from the MAC perspective (i.e., completely ignoring the SL-PRS as a SL transmission), the SL will not start the relevant timers. In some embodiments, the eighth solution can be combined with other embodiments (e.g., the first solution).

[0166] Following the DRX procedures currently defined for the sidelink (MAC layer procedures, TS 38.321), certain actions are related to SL transmission in the MAC layer, for example, starting specific DRX related timers. When SL-PRS transmission is not considered as a sidelink transmission from a MAC perspective, for example, SL-PRS transmission does not involve TB / MAC PDU, the sidelink DRX procedure will be largely independent of SL-PRS transmission, for example, the SL DRX process is not affected by SL-PRS transmission.

[0167] An embodiment of the ninth solution involves that the UE does not consider SL-PRS transmission as not being considered as DRX active time. In contrast to the first solution, SL-PRS transmission is not considered as DRX active time here. In one embodiment, SL-PRS transmission is considered similar to HARQ ACK / NACK transmission. As used herein, "HARQ-ACK / NACK" may collectively represent a positive acknowledgement ("ACK") and a negative acknowledgement ("NACK"), where ACK means that a transport block ("TB") is correctly received, and NACK means that a TB is incorrectly received. According to the ninth solution, the Tx UE notifies the (multiple) intended Rx UEs of the selected SL-PRS configuration and / or SL-PRS resources, so that the (multiple) Rx UEs are ready to receive (multiple) SL-PRS transmissions. However, from the perspective of the MAC layer or DRX, the SL-PRS is not considered in a particular manner.

[0168] Figure 8An example of a UE 800 according to aspects of the present disclosure is illustrated. The UE 800 may include a processor 802, a memory 804, a controller 806, and a transceiver 808. The processor 802, the memory 804, the controller 806, or the transceiver 808, or various combinations thereof, or various components thereof may be examples of components for performing various aspects of the present disclosure described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0169] The processor 802, memory 804, controller 806, or transceiver 808, or various combinations or components thereof, may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or other programmable logic device, or any combination of the foregoing components configured to or otherwise support the functions described in the present disclosure.

[0170] The processor 802 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 802 may be configured to operate the memory 804. In some other implementations, the memory 804 may be integrated into the processor 802. The processor 802 may be configured to execute computer-readable instructions stored in the memory 804 so that the UE 800 performs various functions of the present disclosure.

[0171] The memory 804 may include volatile or non-volatile memory. The memory 804 may store computer-readable, computer-executable code including instructions that, when executed by the processor 802, cause the UE 800 to perform various functions described herein. The code may be stored in a non-transient computer-readable medium such as the memory 804 or another type of memory. Computer-readable media include both non-transient computer storage media and communication media, including any media that facilitates the transfer of a computer program from one location to another. Non-transient storage media may be any available media that can be accessed by a general or special purpose computer.

[0172] In some implementations, the processor 802 and the memory 804 coupled to the processor 802 may be configured to cause the UE 800 to perform one or more Rx UE functions described herein (e.g., the processor 802 executes instructions stored in the memory 804). For example, the processor 802 may support wireless communications at the UE 800 according to the examples disclosed herein. The UE 800 may be configured to support components for participating in a positioning session with a group of UEs. Additionally, the processor 802 may configure the UE 800 with a DRX configuration including a DRX active time.

[0173] UE 800 may be configured to support components for receiving signaling information from at least one UE in the group of UEs. Here, the signaling information includes timing information for SL-PRS transmission. In some implementations, the signaling information includes a MAC CE. In some implementations, the signaling information includes an RRC message. In some implementations, the signaling information includes a SL positioning protocol (e.g., SLPP, RSPP) message.

[0174] The UE 800 may be configured to support a component for treating a time period (ie, slot / symbol) configured for SL-PRS transmission as a DRX active time by adjusting the DRX active time to include a time period corresponding to SL-PRS transmission after receiving signaling information.

[0175] In some implementations, the UE 800 may be configured to monitor the SCI during a time period corresponding to a transmission of a SL-PRS received within the signaling information. In some implementations, the SCI includes information about future SL-PRS transmissions. In some implementations, the SCI includes a flag to indicate whether the corresponding SL resource is used for non-positioned SL data or SL-PRS transmission.

[0176] In some implementations, the UE 800 may be configured to treat the time period configured for SL-PRS transmission as DRX active time by pausing (or not starting) the timer after receiving the SCI allocating the sidelink resources for SL-PRS transmission. In other implementations, the UE 800 may be configured to stop or cancel the timer upon receiving the SCI allocating the resources for SL-PRS transmission. In one implementation, the timer is sl-drx-InactivityTimer. In another implementation, the timer is sl-DRX-GC-InactivityTimer. In yet another implementation, the timer is sl-drx-HARQ-RTT-Timer. In other implementations, the timer is sl-drx-RetransmissionTimer.

[0177] In some implementations, the UE 800 may be configured to treat the time period configured for SL-PRS transmission as DRX active time by not treating the SCI of the sidelink resources allocated for SL-PRS transmission as indicating SL transmission for the DRX process. In some implementations, the UE 800 may be configured to not treat the SL-PRS transmission as a SL transmission that triggers a MAC layer timer for the DRX process.

[0178] In some implementations, the processor 802 and the memory 804 coupled to the processor 802 may be configured to cause the UE 800 to perform one or more Tx UE functions described herein (e.g., the processor 802 executes instructions stored in the memory 804). For example, the processor 802 may support wireless communications at the UE 800 according to the examples disclosed herein. The UE 800 may be configured to support components for initiating a positioning session with a group of UEs, and components for configuring a DRX configuration including a DRX active time.

[0179] The UE 800 may be configured to support a component for sending signaling information to at least one UE in the group of UEs, wherein the signaling information includes a request for transmission of a SL-PRS. In some implementations, the signaling information includes a MAC CE. In some implementations, the signaling information includes an SCI.

[0180] UE 800 may be configured to support a component for treating the time between transmitting a request for SL-PRS report / transmission and receiving SL-PRS as active time by adjusting the DRX active time to include a time period (e.g., time slot / symbol) corresponding to the reception of signaling information and SL-PRS.

[0181] In some implementations, the UE 800 may be configured to align the DRX active time with the corresponding active time configuration of at least one UE. In some implementations, the UE 800 may be configured to select a set of SL resources for SL-PRS transmission during the active time of at least one UE. In some implementations, the UE 800 may be configured to receive information of the active time configuration of the group of UEs.

[0182] In some implementations, UE 800 may be configured to send timing information for transmitting SL-PRS. In some implementations, the timing information is included in the MAC CE. In some implementations, the signaling information is included in the RRC message. In some implementations, the signaling information is included in the SL positioning protocol (e.g., SLPP, RSPP) message.

[0183] The controller 806 may manage input and output signals for the UE 800. The controller 806 may also manage peripheral devices that are not integrated into the UE 800. In some implementations, the controller 806 may utilize an operating system, such as Or other operating systems. In some implementations, the controller 806 can be implemented as part of the processor 802.

[0184] In some implementations, the UE 800 may include at least one transceiver 808. In some other implementations, the UE 800 may have more than one transceiver 808. The transceiver 808 may represent a wireless transceiver. The transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

[0185] The receiver chain 810 may be configured to receive a signal (e.g., control information, data, packet) over a wireless medium. For example, the receiver chain 810 may include one or more antennas for receiving signals over the air or wireless medium. The receiver chain 810 may include at least one amplifier (e.g., a low noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 810 may include at least one demodulator configured to demodulate the received signal and obtain the transmission data by inverting the modulation technique applied during the transmission of the signal. The receiver chain 810 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0186] The transmitter chain 812 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 812 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or a digital modulation scheme, such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 812 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmitter chain 812 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0187] Fig. 9 An example of a processor 900 according to aspects of the present disclosure is illustrated. The processor 900 may be an example of a processor configured to perform various operations according to the examples described herein. The processor 900 may include a controller 902 configured to perform various operations according to the examples described herein. The processor 900 may optionally include at least one memory 904, which may be, for example, an L1 / L2 / L3 cache. Additionally or alternatively, the processor 900 may optionally include one or more arithmetic logic units (ALUs) 906. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0188] The processor 900 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, obtain, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory located locally in the processor chipset (e.g., processor 900) or included in the processor chipset (e.g., processor 900) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM)), etc.).

[0189] The controller 902 may be configured to manage and coordinate various operations (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 900 so that the processor 900 supports various operations according to the examples described herein. For example, the controller 902 may operate as a control element of the processor 900, generating control signals that manage the operation of various components of the processor 900. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0190] The controller 902 may be configured to extract (e.g., obtain, retrieve, receive) instructions from the memory 904 and determine (multiple) subsequent instructions to be executed so that the processor 900 supports various operations according to the examples described herein. The controller 902 may be configured to track the memory addresses of instructions associated with the memory 904. The controller 902 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, the controller 902 may be configured to interpret instructions and determine control signals to be output to other components of the processor 900 so that the processor 900 supports various operations according to the examples described herein. Additionally or alternatively, the controller 902 may be configured to manage data flow within the processor 900. The controller 902 may be configured to control data transfer between registers, arithmetic logic units (ALUs), and other functional units of the processor 900.

[0191] The memory 904 may include one or more caches (e.g., memory or other memory local to or included in the processor 900, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, the memory 904 may reside within or on a processor chipset (e.g., local to the processor 900). In some other implementations, the memory 904 may reside external to the processor chipset (e.g., remote from the processor 900).

[0192] The memory 904 may store computer-readable, computer-executable code including instructions that, when executed by the processor 900, cause the processor 900 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. The controller 902 and / or the processor 900 may be configured to execute computer-readable instructions stored in the memory 904 so that the processor 900 performs various functions. For example, the processor 900 and / or the controller 902 may be coupled to or coupled to the memory 904, and the processor 900, the controller 902, and the memory 904 may be configured to perform various functions described herein. In some examples, the processor 900 may include multiple processors, and the memory 904 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform various functions herein.

[0193] One or more ALUs 906 may be configured to support various operations according to the examples described herein. In some implementations, one or more ALUs 906 may reside in or on a processor chipset (e.g., processor 900). In some other implementations, one or more ALUs 906 may reside outside a processor chipset (e.g., processor 900). One or more ALUs 906 may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 906 may receive input operands and an opcode, which determines the operation to be performed. One or more ALUs 906 may be configured with various logic and arithmetic circuits (including adders, subtractors, shifters, and logic gates) to process and manipulate data according to the operation. Additionally or alternatively, one or more ALUs 906 may support logical operations (such as AND, OR, XOR, NOR, and NAND), so that one or more ALUs 906 can process conditional operations, comparisons, and bitwise operations.

[0194] The processor 900 may support wireless communications according to the examples disclosed herein. For example, the processor 900 may perform one or more Rx UE functions described herein. The processor 900 may be configured or operable to support components for participating in a positioning session with a group of UEs. Additionally, the processor 802 may be configured or operable to support components for setting a DRX configuration including a DRX active time.

[0195] The processor 900 may be configured or operable to support a component for receiving signaling information from at least one UE in the group of UEs. Here, the signaling information includes timing information for transmitting the SL-PRS. In some implementations, the signaling information includes a MAC CE. In some implementations, the signaling information includes an RRC message. In some implementations, the signaling information includes a SL positioning protocol (e.g., SLPP, RSPP) message.

[0196] The processor 900 may be configured or operable to support a component for treating a time period (i.e., time slot / symbol) configured for SL-PRS transmission as a DRX active time by adjusting the DRX active time to include a time period corresponding to the transmission of the SL-PRS after receiving signaling information.

[0197] In some implementations, the processor 900 may be configured or operable to monitor the SCI during a time period corresponding to a transmission of a SL-PRS received within the signaling information. In some implementations, the SCI includes information about future SL-PRS transmissions. In some implementations, the SCI includes a flag to indicate whether the corresponding SL resource is used for non-positioned SL data or SL-PRS transmission.

[0198] In some implementations, the processor 900 may be configured or operable to, after receiving an SCI allocating sidelink resources for SL-PRS transmission, suspend (or not start) a timer to treat the time period configured for SL-PRS transmission as DRX active time. In other implementations, the processor 900 may be configured or operable to, upon receiving an SCI allocating resources for SL-PRS transmission, stop or cancel the timer. In one implementation, the timer is sl-drx-InactivityTimer. In another implementation, the timer is sl-DRX-GC-InactivityTimer. In yet another implementation, the timer is sl-drx-HARQ-RTT-Timer. In other implementations, the timer is sl-drx-RetransmissionTimer.

[0199] In some implementations, the processor 900 may be configured or operable to not consider the SCI allocating sidelink resources for SL-PRS transmission as indicating SL transmission for the DRX process, and to consider the time period configured for SL-PRS transmission as DRX active time. In some implementations, the processor 900 may be configured or operable to not consider the SL-PRS transmission as a SL transmission that triggers a MAC layer timer for the DRX process.

[0200] The processor 900 may perform one or more of the Tx UE functions described herein.The processor 900 may be configured or operable to support components for initiating a positioning session with a group of UEs, and components for configuring a DRX configuration including a DRX active time.

[0201] The processor 900 may be configured or operable to support a component for sending signaling information to at least one UE in the group of UEs, wherein the signaling information includes a request for transmission of a SL-PRS. In some implementations, the signaling information includes a MAC CE. In some implementations, the signaling information includes an SCI.

[0202] Processor 900 may be configured or operable to support a component for treating the time between transmitting a request for a SL-PRS report / transmission and receiving the SL-PRS as an active time by adjusting the DRX active time to include a time period (e.g., time slot / symbol) corresponding to the reception of signaling information and the SL-PRS.

[0203] In some implementations, the processor 900 may be configured or operable to align the DRX active time with the corresponding active time configuration of at least one UE. In some implementations, the processor 900 may be configured or operable to select a set of SL resources for SL-PRS transmission within the active time of at least one UE. In certain implementations, the processor 900 may be configured or operable to receive information of the active time configuration of the group of UEs.

[0204] In some implementations, the processor 900 may be configured or operable to send timing information for the transmission of the SL-PRS. In some implementations, the timing information is included in the MAC CE. In some implementations, the signaling information is included in the RRC message. In some implementations, the signaling information is included in the SL positioning protocol (e.g., SLPP, RSPP) message.

[0205] Fig.10An example of a NE 1000 according to aspects of the present disclosure is illustrated. The NE 1000 may include a processor 1002, a memory 1004, a controller 1006, and a transceiver 1008. The processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0206] The processor 1002, the memory 1004, the controller 1006, or the transceiver 1008, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or other programmable logic device, or any combination of the above components configured or otherwise supporting the functions described in the present disclosure.

[0207] The processor 1002 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1002 may be configured to operate the memory 1004. In some other implementations, the memory 1004 may be integrated into the processor 1002. The processor 1002 may be configured to execute computer-readable instructions stored in the memory 1004 so that the NE 1000 performs various functions of the present disclosure.

[0208] The memory 1004 may include volatile or non-volatile memory. The memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1002, cause the NE 1000 to perform various functions described herein. The code may be stored in a non-transient computer-readable medium (such as the memory 1004 or another type of memory). Computer-readable media include non-transient computer storage media and communication media, including any media that facilitates the transfer of a computer program from one location to another. Non-transient storage media may be any available media that can be accessed by a general or special purpose computer.

[0209] In some implementations, the processor 1002 and the memory 1004 coupled to the processor 1002 may be configured to cause the NE 1000 to perform one or more of the functions described herein (e.g., the processor 1002 executes instructions stored in the memory 1004). For example, the processor 1002 may support wireless communications at the NE 1000 according to the examples disclosed herein. The NE 1000 may be configured to support components for configuring a set of DRX configurations for transmission of SL-PRS. In some implementations, the set of DRX configurations is configured for each resource pool. In some implementations, a specific DRX configuration includes an active time and an idle time, an offset, and a number of transmissions.

[0210] In some implementations, the NE 1000 may be configured to formulate the set of DRX configurations based on SL positioning accuracy requirements. In some implementations, the NE 1000 may be configured to formulate the set of DRX configurations based on SL positioning QoS requirements of the associated positioning methods.

[0211] The NE 1000 may be configured to support means for allocating a set of SL time-frequency resources for positioning sessions to a set of UEs. Note that the NE 1000 configures the UEs with the set of DRX configurations, and the corresponding UEs select a DRX configuration from the set of DRX configurations based on the SL positioning QoS requirements.

[0212] In some implementations, the NE 1000 may be configured to obtain information about the active time configurations of the group of UEs, and send the information to an initiator UE in the group of UEs.

[0213] Controller 1006 may manage input and output signals for NE 1000. Controller 1006 may also manage peripheral devices that are not integrated into NE 1000. In some implementations, controller 1006 may utilize an operating system, such as In some implementations, the controller 1006 may be implemented as part of the processor 1002 .

[0214] In some implementations, the NE 1000 may include at least one transceiver 1008. In some other implementations, the NE 1000 may have more than one transceiver 1008. The transceiver 1008 may represent a wireless transceiver. The transceiver 1008 may include one or more receiver chains 1010, one or more transmitter chains 1012, or a combination thereof.

[0215] The receiver chain 1010 may be configured to receive a signal (e.g., control information, data, packet) over a wireless medium. For example, the receiver chain 1010 may include one or more antennas for receiving signals over the air or wireless medium. The receiver chain 1010 may include at least one amplifier (e.g., a low noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 1010 may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by inverting the modulation technique applied during the transmission of the signal. The receiving chain 1010 may include at least one decoder for decoding and processing the demodulated signal to receive the transmitted data.

[0216] The transmitter chain 1012 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 1012 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or a digital modulation scheme, such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 1012 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmitter chain 1012 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0217] Fig.11 A flow chart of a method 1100 according to aspects of the present disclosure is illustrated. The operations of the method 1100 may be implemented by an Rx UE as described herein. In some implementations, the Rx UE may execute a set of instructions to control functional elements of the Rx UE to perform the described functions.

[0218] At step 1102, method 1100 may include: receiving CSI report settings. The operations of step 1102 may be performed according to the examples described herein. In some implementations, aspects of the operations of step 1102 may be as described in reference to Figure 8 The described Rx UE is executed.

[0219] At step 1104, method 1100 may include: receiving a set of channel measurement reference signals including at least one NZP CSI-RS resource. The operations of step 1104 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1104 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0220] At step 1106, method 1100 may include: generating a CSI feedback report according to the CSI report setting, the CSI feedback report including multiple CSI report segments and multiple CQI values ​​associated with the multiple CSI report segments. The operation of step 1106 may be performed according to the examples described herein. In some implementations, aspects of the operation of step 1106 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0221] At step 1108, method 1100 may include sending a CSI feedback report. The operations of step 1108 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1108 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0222] It should be noted that the method 1100 described herein describes one possible implementation, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0223] Fig.12 A flow chart of a method 1200 according to aspects of the present disclosure is illustrated. The operations of the method 1200 may be implemented by an Rx UE as described herein. In some implementations, the Rx UE may execute a set of instructions to control functional elements of the Rx UE to perform the described functions.

[0224] At step 1202, method 1200 may include participating in a positioning session with a group of UEs. The operations of step 1202 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1202 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0225] At step 1204, the method 1200 may include configuring a DRX configuration including a DRX active time. The operations of step 1204 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1204 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0226] At step 1206, method 1200 may include: receiving signaling information from at least one UE in the group of UEs, the signaling information including timing information for transmission of the SL-PRS. The operation of step 1206 may be performed according to the examples described herein. In some implementations, aspects of the operation of step 1206 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0227] At step 1208, method 1200 may include: adjusting the DRX active time to include a time period corresponding to the transmission of the SL-PRS after receiving the signaling information. The operation of step 1208 may be performed according to the examples described herein. In some implementations, aspects of the operation of step 1208 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0228] At step 1210, method 1200 may include monitoring the SCI during a time period corresponding to the transmission of the received SL-PRS. The operations of step 1210 may be performed according to the examples described herein. In some implementations, aspects of the operations of step 1210 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0229] At step 1212, method 1200 may optionally include: in response to receiving the SCI allocating sidelink resources for SL-PRS transmission, pausing the timer. The operations of step 1212 may be performed according to the examples described herein. In some implementations, aspects of the operations of step 1212 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0230] At step 1214, the method 1200 may optionally include: not considering the SCI of the sidelink resource allocated for the SL-PRS transmission as indicating the SL transmission for the DRX process. The operation of step 1214 may be performed according to the examples described herein. In some implementations, aspects of the operation of step 1214 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0231] It should be noted that the method 1200 described herein describes one possible implementation, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0232] Fig.13 A flow chart of a method 1300 according to aspects of the present disclosure is illustrated. The operations of the method 1300 may be implemented by an Rx UE as described herein. In some implementations, the Rx UE may execute a set of instructions to control functional elements of the Rx UE to perform the described functions.

[0233] At step 1302, method 1300 may include participating in a positioning session with a group of UEs. The operations of step 1302 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1302 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0234] At step 1304, method 1300 may include configuring a DRX configuration including a DRX active time. The operations of step 1304 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1304 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0235] At step 1306, method 1300 may include: receiving signaling information from at least one UE in the group of UEs, the signaling information including timing information for transmission of the SL-PRS. The operation of step 1306 may be performed according to the examples described herein. In some implementations, aspects of the operation of step 1306 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0236] At step 1308, method 1300 may include adjusting the DRX active time to include a time period corresponding to the transmission of the SL-PRS after receiving the signaling information. The operations of step 1308 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1308 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0237] At step 1310, the method 1300 may include not treating (i.e., not considering) the SL-PRS transmission as a SL transmission that triggers a MAC layer timer for a DRX process. The operations of step 1310 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1310 may be performed as described in reference to Figure 8 The described Rx UE is executed.

[0238] It should be noted that the method 1300 described herein describes one possible implementation, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0239] Fig.14 A flow chart of a method 1400 according to aspects of the present disclosure is illustrated. The operations of the method 1400 may be implemented by a Tx UE as described herein. In some implementations, the Tx UE may execute a set of instructions to control functional elements of the Tx UE to perform the described functions.

[0240] At step 1402, method 1400 may include initiating a positioning session with a group of UEs. The operations of step 1402 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1402 may be performed as described in reference to Figure 8 The described Tx UE is executed.

[0241] At step 1404, method 1400 may include configuring a DRX configuration including a DRX active time. The operations of step 1404 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1404 may be performed as described in reference to Figure 8 The described Tx UE is executed.

[0242] At step 1406, method 1400 may include: sending signaling information to at least one UE in the group of UEs, wherein the signaling information includes a request for transmission of the SL-PRS. The operation of step 1406 may be performed according to the examples described herein. In some implementations, aspects of the operation of step 1406 may be performed as described in reference to Figure 8 The described Tx UE is executed.

[0243] At step 1408, method 1400 may include adjusting the DRX active time to include a time period corresponding to the reception of the signaling information and the SL-PRS. The operations of step 1408 may be performed according to the examples described herein. In some implementations, aspects of the operations of step 1408 may be performed as described in reference to Figure 8 The described Tx UE is executed.

[0244] It should be noted that the method 1400 described herein describes one possible implementation, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0245] Fig.15 A flow chart of a method 1500 according to aspects of the present disclosure is illustrated. The operations of the method 1500 may be implemented by a Tx UE as described herein. In some implementations, the Tx UE may execute a set of instructions to control functional elements of the Tx UE to perform the described functions.

[0246] At step 1502, method 1500 may include initiating a positioning session with a group of UEs. The operations of step 1502 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1502 may be performed as described in reference to Figure 8 The described Tx UE is executed.

[0247] At step 1504, method 1500 may include configuring a DRX configuration including a DRX active time. The operations of step 1504 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1504 may be performed as described in reference to Figure 8 The described Tx UE is executed.

[0248] At step 1506, method 1500 may include: sending signaling information to at least one UE in the group of UEs, wherein the signaling information includes a request for transmission of the SL-PRS. The operation of step 1506 may be performed according to the examples described herein. In some implementations, aspects of the operation of step 1506 may be performed as described in reference to Figure 8 The described Tx UE is executed.

[0249] At step 1508, method 1500 may include adjusting the DRX active time to include a time period corresponding to the reception of the signaling information and the SL-PRS. The operations of step 1508 may be performed according to the examples described herein. In some implementations, aspects of the operations of step 1508 may be performed as described in reference to Figure 8 The described Tx UE is executed.

[0250] At step 1510, method 1500 may include aligning the DRX active time with a corresponding active time configuration of at least one UE. The operations of step 1510 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1510 may be performed as described in reference to Figure 8 The described Tx UE is executed.

[0251] At step 1512, method 1500 may optionally include: receiving information about the active time configuration of the group of UEs. The operation of step 1512 may be performed according to the examples described herein. In some implementations, aspects of the operation of step 1512 may be performed as described in reference to Figure 8 The described Tx UE is executed.

[0252] At step 1514, method 1500 may optionally include: selecting a set of SL resources for SL-PRS transmission during the active time of at least one UE. The operation of step 1514 may be performed according to the examples described herein. In some implementations, aspects of the operation of step 1514 may be performed as described in reference to Figure 8 The described Tx UE is executed.

[0253] It should be noted that the method 1500 described herein describes one possible implementation, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0254] Fig.16 A flow chart of a method 1600 according to aspects of the present disclosure is illustrated. The operations of the method 1600 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control functional elements of the NE to perform the described functions.

[0255] At step 1602, method 1600 may include configuring a set of DRX configurations for transmission of SL-PRS. The operations of step 1602 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1602 may be performed as described in reference to Fig.10 The NE described here is used for execution.

[0256] At step 1604, method 1600 may include: allocating a set of SL time-frequency resources for a positioning session to a set of UEs. The operation of step 1604 may be performed according to the examples described herein. In some implementations, aspects of the operation of step 1604 may be performed as described in reference to Fig.10 The NE described here is used for execution.

[0257] It should be noted that the method 1600 described herein describes one possible implementation, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0258] Fig.17 A flow chart of a method 1700 according to aspects of the present disclosure is illustrated. The operations of the method 1700 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control functional elements of the NE to perform the described functions.

[0259] At step 1702, method 1700 may include configuring a set of DRX configurations for transmission of SL-PRS. The operations of step 1702 may be performed according to examples as described herein. In some implementations, aspects of the operations of step 1702 may be performed as described in reference to Fig.10 The NE described here is used for execution.

[0260] At step 1704, method 1700 may include: allocating a set of SL time-frequency resources for a positioning session to a set of UEs. The operations of step 1704 may be performed according to the examples described herein. In some implementations, aspects of the operations of step 1704 may be performed as described in reference to Fig.10 The NE described here is used for execution.

[0261] At step 1706, method 1700 may include configuring the set of DRX configurations based on the SL positioning accuracy requirements and / or SL positioning QoS requirements of the associated positioning technology. The operations of step 1706 may be performed according to the examples described herein. In some implementations, aspects of the operations of step 1706 may be performed as described in reference to Fig.10 NE described here to execute.

[0262] At step 1708, method 1700 may include: obtaining information about the active time configuration of the group of UEs. The operation of step 1708 may be performed according to the examples described herein. In some implementations, aspects of the operation of step 1708 may be performed as described in reference to Fig.10 NE described here to execute.

[0263] At step 1710, method 1700 may include: sending the information to an initiator UE in the group of UEs. The operation of step 1710 may be performed according to the examples described herein. In some implementations, aspects of the operation of step 1710 may be performed as described in reference to Fig.10 NE described here to execute.

[0264] It should be noted that the method 1700 described herein describes one possible implementation, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0265] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein can be applied to other variants without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; as well as at least one processor, coupled to the at least one memory, and configured to cause the UE to: Participating in a positioning session with a group of UEs; Configuration including DRX configuration including DRX activity time; receiving signaling information from at least one UE in the set of UEs, wherein the signaling information includes timing information for transmission of a sidelink positioning reference signal (SL-PRS); as well as In response to the reception of the signaling information, the DRX active time is adjusted to include a time period corresponding to the transmission of the SL-PRS.

2. The UE according to claim 1, wherein the signaling information comprises: Medium Access Control (MAC) Control Element (CE), or Radio Resource Control (RRC) message, or Sidelink (SL) positioning protocol message.

3. The UE according to claim 1, wherein the at least one processor is configured to cause the UE to: monitor sidelink control information (SCI) during a time period corresponding to the transmission of the SL-PRS received within the signaling information.

4. The UE according to claim 3, wherein the SCI comprises: Information about future SL-PRS transmissions.

5. The UE according to claim 3, wherein the SCI includes a flag, and the flag is used to indicate whether the corresponding side link (SL) resource is used for non-positioning SL data or SL-PRS transmission.

6. The UE according to claim 3, wherein the at least one processor is configured to cause the UE to: suspend a timer in response to receiving an SCI allocating sidelink resources for SL-PRS transmission.

7. The UE according to claim 6, wherein the timer comprises: sl-drx-InactivityTimer, sl-DRX-GC-InactivityTimer, sl-drx-HARQ-RTT-Timer, or sl-drx-RetransmissionTimer, or a combination thereof.

8. The UE according to claim 3, wherein the at least one processor is configured to cause the UE to: not regard the SCI of the sidelink resources allocated for SL-PRS transmission as indicating a sidelink (SL) transmission for a DRX process.

9. The UE of claim 1, wherein the at least one processor is configured to cause the UE to: not regard SL-PRS transmission as a sidelink (SL) transmission that triggers a media access control (MAC) layer timer for a DRX process.

10. A processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to cause the processor to: Participating in a positioning session with a group of user equipments (UEs); Configuration including DRX configuration including DRX activity time; receiving signaling information from at least one UE in the set of UEs, wherein the signaling information includes timing information for transmission of a sidelink positioning reference signal (SL-PRS); as well as In response to the reception of the signaling information, the DRX active time is adjusted to include a time period corresponding to the transmission of the SL-PRS.

11. A user equipment (UE) for wireless communication, comprising: at least one memory; as well as at least one processor, coupled to the at least one memory, and configured to cause the UE to: Initiate a positioning session with a group of user UEs; Configuration including DRX configuration including DRX activity time; sending signaling information to at least one UE in the group of UEs, wherein the signaling information includes a request for transmission of a sidelink positioning reference signal (SL-PRS); and The DRX active time is adjusted to include a time period corresponding to the reception of the signaling information and the SL-PRS.

12. The UE according to claim 11, wherein the signaling information comprises: Medium Access Control (MAC) Control Element (CE), or Sidelink Control Information (SCI).

13. The UE according to claim 11, wherein the at least one processor is configured to enable the UE to: select a set of sidelink (SL) resources for SL-PRS transmission during the active time of the at least one UE. 14 . The UE according to claim 13 , wherein the at least one processor is configured to cause the UE to: receive information of activity time configuration of the group of UEs.

15. The UE of claim 11, wherein the at least one processor is configured to cause the UE to: align the DRX active time with a corresponding active time configuration of the at least one UE.

16. A base station for wireless communication, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the base station to: configuring a set of discontinuous reception (DRX) configurations for transmission of a sidelink positioning reference signal (SL-PRS); and A group of sidelink (SL) time-frequency resources for a positioning session is allocated to a group of user equipments (UEs).

17. The base station of claim 16, wherein the set of DRX configurations is configured for each resource pool.

18. The base station according to claim 16, wherein the specific DRX configuration comprises: Active and idle times, offsets, and transfer times.

19. The base station according to claim 16, wherein the at least one processor is configured to enable the base station to: configure the set of DRX configurations based on the SL positioning accuracy requirement and / or the SL positioning quality of service (QoS) requirement of the associated positioning method.

20. The base station of claim 16, wherein the at least one processor is configured to cause the base station to: Obtaining information about the activity time configuration of the group of UEs; and The information is sent to an initiator UE in the group of UEs.

Images