Discontinuous reception (DRX) based anchor user equipment (UE) selection for joint positioning session

Abstract

Techniques for wireless positioning are disclosed. In an aspect, a user equipment (UE) operating in a discontinuous reception (DRX) mode receives, from a location server, an anchor selection update message indicating that the UE has been selected as an anchor UE for a joint positioning session with one or more second UEs, wherein the UE is selected as the anchor UE based at least in part on a DRX active time of the UE being closer to a plurality of measurement occasions for the joint positioning session than a DRX active time of the one or more second UEs; performs, during one or more measurement occasions that overlap with the DRX active time of the UE, positioning measurements for the joint positioning session; and transmits, to the one or more second UEs, the positioning measurements, a position of the UE determined based on the positioning measurements, or both.

Description

Background Technology 1. Technical Field

[0002] All aspects of this disclosure relate to wireless communications.

[0003] 2. Relevant Technical Descriptions

[0004] Wireless communication systems have evolved through many generations, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data, wireless services with internet capabilities, and fourth-generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), and others.

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

[0006] In addition, leveraging 5G's increased data rates and reduced latency, vehicle-to-everything (V2X) communication technology is being implemented to support autonomous driving applications, such as wireless communication between vehicles, between vehicles and roadside infrastructure, and between vehicles and pedestrians. Summary of the Invention

[0007] The following is a simplified overview relating to one or more aspects disclosed herein. Therefore, this overview should not be considered an exhaustive overview relating to all conceived aspects, nor should it be considered to identify key or decisive elements relating to all conceived aspects or to depict the scope associated with any particular aspect. Thus, the sole purpose of the following overview is to present, in a concise form, certain concepts relating to one or more aspects involving the mechanisms disclosed herein, prior to the specific embodiments presented below.

[0008] In one aspect, a radio positioning method performed by a user equipment (UE) operating in discontinuous reception (DRX) mode includes: receiving an anchor selection update message from a location server, the anchor selection update message indicating that the UE has been selected as an anchor UE for a joint positioning session with one or more second UEs, wherein the UE is selected as the anchor UE based at least in part on a plurality of measurement times for the joint positioning session being closer than the DRX active times of the one or more second UEs; in response to receiving the anchor selection update message, performing positioning measurements for the joint positioning session during one or more of the plurality of measurement times overlapping with the DRX active time of the UE; and transmitting the positioning measurements, the location of the UE determined based on the positioning measurements, or both, to the one or more second UEs.

[0009] In one aspect, a positioning method performed by a location server includes: receiving multiple discontinuous reception (DRX) configurations of multiple user equipments (UEs) participating in a joint positioning session, each of the multiple DRX configurations indicating at least a DRX active time for the corresponding UE; selecting one of the multiple UEs as the anchor UE based at least in part on the fact that the DRX active time of the anchor UE for the joint positioning session is closer to multiple measurement times for the joint positioning session than the DRX active times of the remaining UEs among the multiple UEs; and transmitting an anchor selection update message to each of the multiple UEs, the anchor selection update message indicating that the anchor UE has been selected as the anchor UE for the joint positioning session.

[0010] In one aspect, a radio positioning method performed by a user equipment (UE) operating in discontinuous reception (DRX) mode includes: receiving an anchor selection update message from a location server, the anchor selection update message indicating that a peer UE has been selected from a plurality of UEs including the peer UE as an anchor UE for a joint positioning session, wherein the peer UE is selected as the anchor UE based at least in part on the fact that the DRX active timing of the peer UE is closer to a plurality of measurement timings for the joint positioning session than the DRX active timings of the remaining UEs among the plurality of UEs; and receiving from the peer UE positioning measurements performed by the peer UE for the joint positioning session, the location of the peer UE determined based on these positioning measurements, or both.

[0011] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive an anchor selection update message from a location server via the at least one transceiver, the anchor selection update message indicating that the UE has been selected as an anchor UE for a joint positioning session with one or more second UEs, wherein the UE is selected as the anchor UE based at least in part on the fact that the UE's DRX active timing is closer to a plurality of measurement timings for the joint positioning session than the DRX active timings of the one or more second UEs; in response to receiving the anchor selection update message, perform positioning measurements for the joint positioning session during one or more of the plurality of measurement timings overlapping with the UE's DRX active timing; and transmit the positioning measurements, the location of the UE determined based on the positioning measurements, or both, to the one or more second UEs via the at least one transceiver.

[0012] In one aspect, a location server includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive via the at least one transceiver multiple discontinuous reception (DRX) configurations of multiple user equipments (UEs) participating in a joint positioning session with each other, each of the multiple DRX configurations indicating at least a DRX active time for the corresponding UE; select one of the multiple UEs as the anchor UE based at least in part on the fact that the DRX active time of the anchor UE for the joint positioning session is closer to multiple measurement times for the joint positioning session than the DRX active times of the remaining UEs among the multiple UEs; and transmit via the at least one transceiver an anchor selection update message to each of the multiple UEs, the anchor selection update message indicating that the anchor UE has been selected as the anchor UE for the joint positioning session.

[0013] In one aspect, a user equipment (UE) includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, from a location server an anchor selection update message indicating that a peer UE has been selected from a plurality of UEs including the peer UE as an anchor UE for a joint location session, wherein the peer UE is selected as the anchor UE based at least in part on the fact that the peer UE's DRX active timing is closer to a plurality of measurement timings for the joint location session than the DRX active timings of the remaining UEs among the plurality of UEs; and receive, via the at least one transceiver, from the peer UE location measurements performed by the peer UE for the joint location session, the location of the peer UE determined based on these location measurements, or both.

[0014] In one aspect, a user equipment (UE) includes: a module for receiving an anchor selection update message from a location server, the anchor selection update message indicating that the UE has been selected as an anchor UE for a joint positioning session with one or more second UEs, wherein the UE is selected as the anchor UE based at least in part on a DRX active timing of the UE being closer to a plurality of measurement timings for the joint positioning session than the DRX active timings of the one or more second UEs; a module for performing positioning measurements for the joint positioning session during one or more of the plurality of measurement timings overlapping with the DRX active timing of the UE in response to receiving the anchor selection update message; and a module for transmitting the positioning measurements, a location of the UE determined based on the positioning measurements, or both, to the one or more second UEs.

[0015] In one aspect, a location server includes: a module for receiving a plurality of discontinuous reception (DRX) configurations of a plurality of user equipments (UEs) participating in a joint positioning session with each other, each of the plurality of DRX configurations indicating at least a DRX active time for the corresponding UE; a module for selecting one of the plurality of UEs as the anchor UE based at least in part on the fact that the DRX active time of the anchor UE for the joint positioning session is closer to a plurality of measurement times for the joint positioning session than the DRX active times of the remaining UEs among the plurality of UEs; and a module for transmitting an anchor selection update message to each of the plurality of UEs, the anchor selection update message indicating that the anchor UE has been selected as the anchor UE for the joint positioning session.

[0016] In one aspect, a user equipment (UE) includes: a module for receiving an anchor selection update message from a location server, the anchor selection update message indicating that a peer UE has been selected from a plurality of UEs including the peer UE as an anchor UE for a joint location session, wherein the peer UE is selected as the anchor UE based at least in part on the fact that the peer UE's DRX active timing is closer to a plurality of measurement timings for the joint location session than the DRX active timings of the remaining UEs among the plurality of UEs; and a module for receiving from the peer UE location measurements performed by the peer UE for the joint location session, the location of the peer UE determined based on these location measurements, or both.

[0017] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive an anchor selection update message from a location server, the anchor selection update message indicating that the UE has been selected as an anchor UE for a joint positioning session with one or more second UEs, wherein the UE is selected as the anchor UE based at least in part on the fact that the UE's DRX active timing is closer to a plurality of measurement timings for the joint positioning session than the DRX active timings of the one or more second UEs; in response to receiving the anchor selection update message, perform positioning measurements for the joint positioning session during one or more of the plurality of measurement timings that overlap with the UE's DRX active timing; and transmit the positioning measurements, the location of the UE determined based on the positioning measurements, or both, to the one or more second UEs.

[0018] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a location server, cause the location server to: receive multiple discontinuous reception (DRX) configurations of multiple user equipments (UEs) participating in a joint positioning session with each other, each of the multiple DRX configurations indicating at least a DRX active time for the corresponding UE; select one of the multiple UEs as the anchor UE based at least in part on the fact that the DRX active time of the anchor UE for the joint positioning session is closer to multiple measurement times for the joint positioning session than the DRX active times of the other UEs among the multiple UEs; and transmit an anchor selection update message to each of the multiple UEs, the anchor selection update message indicating that the anchor UE has been selected as the anchor UE for the joint positioning session.

[0019] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive an anchor selection update message from a location server, the anchor selection update message indicating that a peer UE has been selected from a plurality of UEs including the UE and the peer UE as an anchor UE for a joint positioning session, wherein the peer UE is selected as the anchor UE based at least in part on the fact that the peer UE's DRX active timing is closer to a plurality of measurement timings for the joint positioning session than the DRX active timings of the remaining UEs among the plurality of UEs; and receive from the peer UE positioning measurements performed by the peer UE for the joint positioning session, the location of the peer UE determined based on these positioning measurements, or both.

[0020] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed embodiments. Attached Figure Description

[0021] The accompanying drawings are provided to help describe various aspects of this disclosure, and are provided for illustrative purposes only and not to limit the scope of the aspects.

[0022] Figure 1 An example wireless communication system according to various aspects of this disclosure is shown.

[0023] Figure 2A and Figure 2B Example wireless network architectures according to various aspects of this disclosure are shown.

[0024] Figure 3A , Figure 3B and Figure 3C It is a simplified block diagram of several examples of components that can be used in user equipment (UE), base stations and network entities respectively, and configured to support communications as taught herein.

[0025] Figure 4 This is a diagram illustrating an example frame structure according to various aspects of this disclosure.

[0026] Figure 5 Examples of various positioning methods supported in the New Radio (NR) according to various aspects of this disclosure are shown.

[0027] Figure 6A Various scenarios of interest for side-link-only or combined Uu and side-link positioning according to various aspects of this disclosure are illustrated.

[0028] Figure 6B Additional scenarios of interest are illustrated for side-link-only or combined Uu and side-link positioning according to various aspects of this disclosure.

[0029] Figure 7This is a diagram illustrating an example sidelink ranging and positioning process according to various aspects of this disclosure.

[0030] Figures 8A to 8C An example discontinuous reception (DRX) configuration according to various aspects of this disclosure is shown.

[0031] Figure 9 This is a diagram illustrating an example joint / cooperative localization scenario according to various aspects of this disclosure.

[0032] Figure 10 This is a diagram illustrating example DRX configurations of different peer UEs participating in a joint positioning session according to various aspects of this disclosure.

[0033] Figure 11 An example joint positioning session is shown in which one of the UEs is selected as the anchor UE for the remaining UEs according to various aspects of this disclosure.

[0034] Figures 12 to 14 Example positioning methods according to various aspects of this disclosure are shown. Detailed Implementation

[0035] Aspects of this disclosure are provided in the following description and accompanying drawings of various examples provided for illustrative purposes. Alternative aspects may be devised without departing from the scope of this disclosure. Furthermore, well-known elements of this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

[0036] The terms “exemplary” and / or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and / or “example” is not necessarily to be construed as superior to or better than other aspects. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

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

[0038] Furthermore, numerous aspects are described in sequence according to actions to be performed by elements of, for example, a computing device. It will be appreciated that the various actions described herein can be performed by specific circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of both. Additionally, the sequence of actions described herein can be considered entirely embodied in any form of non-transitory computer-readable storage medium storing a corresponding set of computer instructions that, when executed, will cause or command the associated processor of the device to perform the functions described herein. Therefore, various aspects of this disclosure can be embodied in a variety of different forms, all of which are contemplated within the scope of the claimed subject matter. Furthermore, for each aspect described herein, the corresponding form of any such aspect can be described herein as, for example, "logic configured to perform the described actions".

[0039] As used herein, the terms “User Equipment” (UE), “Vehicle UE” (V-UE), “Pedestrian UE” (P-UE), and “Base Station” are not intended to be specific to or otherwise limited to any particular Radio Access Technology (RAT), unless otherwise stated. In general, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., vehicle onboard computer, vehicle navigation device, mobile phone, router, tablet computer, laptop computer, asset location device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” may be used interchangeably as “mobile device”, “access terminal” or “AT”, “client device”, “wireless device”, “subscriber device”, “subscriber terminal”, “subscriber station”, “user terminal” or UT, “mobile terminal”, “mobile station” or variations thereof.

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

[0041] A base station may operate according to one of several RATs to communicate with a UE, depending on the network in which it is deployed, and is alternatively referred to as an Access Point (AP), Network Node, NodeB, Evolved NodeB (eNB), Next Generation eNB (ng-eNB), New Radio (NR) Node B (also known as gNB or gNodeB), etc. Base stations are primarily used to support the UE's radio access, including supporting the UE's data, voice, and / or signaling connections. In some systems, a base station may only provide edge node signaling functions, while in others, it may provide additional control and / or network management functions. The communication links through which a UE can signal to a base station are called uplink (UL) channels (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication links through which a base station can signal to a UE are called downlink (DL) or forward link channels (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term Traffic Channel (TCH) may refer to either the UL / reverse or DL / forward traffic channel.

[0042] The term "base station" can refer to a single physical transmit / receive point (TRP) or multiple physical TRPs that may be located in the same place or in different places. For example, when the term "base station" refers to a single physical TRP, the physical TRP may be the antenna of a base station corresponding to a cell (or several cell sectors) of the base station. When the term "base station" refers to multiple physical TRPs located in the same place, the physical TRP may be the antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple physical TRPs that are not located in the same place, the physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennas connected via a transmission medium to a common source) or a remote radio headend (RRH) (a remote base station connected to the serving base station). Alternatively, physical TRPs that are not located in the same place may be the serving base station from which the UE receives measurement reports and neighboring base stations from which the UE is measuring its reference radio frequency (RF) signal. As used in this article, a TRP is the point by which a base station transmits and receives wireless signals, so any mention of transmitting from or receiving at a base station should be understood as referring to a specific TRP of the base station.

[0043] In some specific implementations supporting UE positioning, the base station may not support the UE's radio access (e.g., it may not support the UE's data, voice, and / or signaling connections). Instead, it may transmit a reference RF signal to the UE for measurement by the UE, and / or receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of transmitting RF signals to the UE) and / or as a positioning measurement unit (e.g., in the case of receiving and measuring RF signals from the UE).

[0044] An "RF signal" refers to an electromagnetic wave of a given frequency that transmits information across the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver can be referred to as a "multipath" RF signal. As used herein, where the context clearly indicates that the term "signal" refers to a wireless signal or RF signal, an RF signal may also be referred to as a "wireless signal" or simply "signal".

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

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

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

[0048] Base station 102 can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells can be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used to communicate with a base station (e.g., on a frequency resource, referred to as a carrier frequency, component carrier, carrier, frequency band, etc.) and can be associated with an identifier (e.g., Physical Cell Identifier (PCI), Enhanced Cell Identifier (ECI), Virtual Cell Identifier (VCI), Cell Global Identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types that can provide access for different types of UEs (e.g., Machine Type Communication (MTC), Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types). Because a cell is supported by a specific base station, depending on the context, the term "cell" can refer to one or both of the logical communication entity and the base station that supports it. In some cases, the term "cell" can also refer to the geographic coverage area of ​​a base station (e.g., a sector), as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0049] While the geographic coverage areas 110 of adjacent macro cell base stations 102 may partially overlap (e.g., in handover areas), some of the geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macro cell base stations 102. A network that includes both small cell base stations and macro cell base stations can be referred to as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs) that can provide service to restricted groups referred to as closed subscriber groups (CSGs).

[0050] The communication link 120 between base station 102 and UE 104 may include uplink (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use MIMO antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may use one or more carrier frequencies. Carrier allocation may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated to the downlink compared to the uplink).

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

[0052] Small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell base station 102' can employ LTE or NR technology and use the same 5 GHz unlicensed spectrum as WLAN AP 150. Small cell base station 102' employing LTE / 5G in unlicensed spectrum can improve access network coverage and / or increase access network capacity. NR in unlicensed spectrum may be referred to as NR-U. LTE in unlicensed spectrum may be referred to as LTE-U, Licensed Assisted Access (LAA), or MulteFire.

[0053] The wireless communication system 100 may also include an mmW base station 180, which can operate in millimeter-wave (mmW) frequencies and / or near-mmW frequencies to communicate with the UE 182. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range from 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band are referred to as millimeter waves. Near-mmW can extend down to frequencies of 3 GHz with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW / near-mmW RF bands has high path loss and relatively short range. The mmW base station 180 and the UE 182 can utilize beamforming (transmit and / or receive) on the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, it will be understood that in alternative configurations, one or more base stations 102 may also use mmW or near-mmW and beamforming for transmission. Accordingly, it will be understood that the foregoing examples are merely illustrative and should not be construed as limiting the aspects disclosed herein.

[0054] Transmit beamforming is a technique used to focus RF signals in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). Using transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thus providing the receiving device with a faster (in terms of data rate) and stronger RF signal. To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an antenna array (called a "phased array" or "antenna array") that creates an RF beam that can be "manipulated" to be pointed in different directions without actually moving the antennas. Specifically, RF currents from the transmitters are fed to the individual antennas with the correct phase relationship, such that radio waves from the separate antennas are added together to increase radiation in the desired direction while canceling out radiation in undesired directions.

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

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

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

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

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

[0060] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G NR studies have designated the operating bands used for these IF bands as the frequency range name FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to IF band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been designated as the frequency range names FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0061] In light of the foregoing, unless otherwise stated, it should be understood that, as used herein, the term "sub-6GHz" and the like can broadly refer to frequencies less than 6GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

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

[0063] For example, still refer to Figure 1 One of the frequencies used by the macro cell base station 102 can be an anchor carrier (or "PCell"), and other frequencies used by the macro cell base station 102 and / or the mmW base station 180 can be secondary carriers ("SCell"). Simultaneous transmission and / or reception on multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, compared to the data rate obtained by a single 20MHz carrier, the aggregation of two 20MHz carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40MHz).

[0064] exist Figure 1 In the example shown, the UE (for simplicity, in) Figure 1Any UE (shown as a single UE 104) may receive signal 124 from one or more Earth-orbiting spacecraft (SV) 112 (e.g., satellites). In one aspect, SV 112 may be part of a satellite positioning system that allows UE 104 to use as an independent source of location information. A satellite positioning system typically includes a transmitter system (e.g., SV 112) positioned such that a receiver (e.g., UE 104) can determine its location on or above the Earth based at least in part on positioning signals (e.g., signal 124) received from the transmitter. Such a transmitter typically transmits a signal of repeating pseudo-random noise (PN) code marked with a predetermined number of chips. While typically located in SV 112, the transmitter may sometimes be located at a ground-based control station, base station 102, and / or other UE 104. UE 104 may include one or more dedicated receivers specifically designed to receive signal 124 in order to derive geographic location information from SV 112.

[0065] In a satellite positioning system, the use of signal 124 can be enhanced by various satellite-based augmentation systems (SBAS), which may be associated with or otherwise made capable of being used with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential correction, etc., such as Wide Area Augmentation System (WAAS), European Geosynchronous Navigation Coverage Service (EGNOS), Multifunctional Satellite Augmentation System (MSAS), GPS-assisted geographic augmentation navigation, or GPS and geographic augmentation navigation system (GAGAN), etc. Therefore, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with one or more such satellite positioning systems.

[0066] On one hand, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 connects to an earth station (also called a ground station, NTN gateway, or gateway), which in turn connects to elements in the 5G network, such as the modified base station 102 (without a ground antenna) or network nodes in a 5GC. This element, in turn, provides access to other elements in the 5G network and ultimately to entities outside the 5G network, such as internet web servers and other user equipment. Thus, UE 104 can receive communication signals (e.g., signal 124) from SV 112, either in place of or in addition to communication signals from ground station 102.

[0067] In addition, leveraging the increased data rate and reduced latency of NR, vehicle-to-everything (V2X) communication technology is being implemented to support Intelligent Transportation Systems (ITS) applications, such as wireless communication between vehicles (V2V), between vehicles and roadside infrastructure (V2I), and between vehicles and pedestrians (V2P). The goal is to enable vehicles to sense their surroundings and communicate that information to other vehicles, infrastructure, and personal mobile devices. This type of vehicle communication will achieve safety, mobility, and environmental improvements that current technologies cannot provide. Once fully realized, this technology is expected to reduce fault-free vehicle collisions by up to 80%.

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

[0069] On one hand, sidelinks 162, 166, and 168 can operate via a wireless communication medium of interest, which can be shared with other vehicles and / or infrastructure access points and other RATs for other wireless communications. "Medium" may include one or more time, frequency, and / or space communication resources (e.g., covering one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs.

[0070] In some respects, sidelinks 162, 166, and 168 may be cV2X links. First-generation cV2X has been standardized in LTE, and the next generation is expected to be defined in NR. cV2X is a cellular technology that also enables device-to-device communication. In the United States and Europe, cV2X is expected to operate in licensed ITS bands in the sub-6 GHz range. Other bands may be allocated in other countries. Thus, as a particular example, the medium of interest utilized by sidelinks 162, 166, and 168 may correspond to at least a portion of a licensed ITS band in the sub-6 GHz range. However, this disclosure is not limited to that band or cellular technology.

[0071] On one hand, sidelinks 162, 166, and 168 can be Dedicated Short-Range Communication (DSRC) links. DSRC is a one-way or two-way short-to-medium-range wireless communication protocol that uses the WAVE (Wave Access in Vehicle Environment) protocol (also known as IEEE 802.11p) for V2V, V2I, and V2P communications. IEEE 802.11p is an approved modification of the IEEE 802.11 standard and operates in the licensed ITS band of 5.9 GHz (5.85 GHz to 5.925 GHz) in the United States. In Europe, IEEE 802.11p operates in the ITSG5A band (5.875 MHz to 5.905 MHz). Other bands may be allocated in other countries. The V2V communications described above occur on a secure channel, which in the United States is typically a 10 MHz channel dedicated to security purposes. The remainder of the DSRC band (total bandwidth is 75MHz) is intended for other services of interest to drivers, such as road rules, toll collection, parking automation, etc. Therefore, as a specific example, the media of interest utilized by side links 162, 166, and 168 may correspond to at least a portion of the licensed ITS band at 5.9GHz.

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

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

[0074] Note that, although Figure 1 Only two UEs are shown as V-UEs (V-UE 160), but any UE shown (e.g., UE 104, 152, 182, 190) could be a V-UE. Furthermore, although only these V-UEs 160 and a single UE 104 have been shown as connected via a sidelink, Figure 1Any UE shown, whether V-UE, P-UE, etc., is capable of sidelink communication. Furthermore, although only UE 182 is described as capable of beamforming, any of the UEs shown (including V-UE 160) is capable of beamforming. When V-UE 160 is capable of beamforming, it can beamform towards each other (i.e., towards other V-UEs 160), towards RSU 164, towards other UEs (e.g., UEs 104, 152, 182, 190), etc. Therefore, in some cases, V-UE 160 can utilize beamforming on sidelinks 162, 166, and 168.

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

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

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

[0078] Figure 2B Another example wireless network architecture 250.5GC 260 is shown (which can correspond to...). Figure 2AThe 5GC 210 in the document can be functionally considered as a control plane function provided by the Access and Mobility Management Function (AMF) 264 and a user plane function provided by the User Plane Function (UPF) 262, which work together to form the core network (i.e., 5GC 260). The functions of the AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any UE described herein) and the Session Management Function (SMF) 266, transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between the UE 204 and the Short Message Service Function (SMSF) (not shown), and the Security Anchor Function (SEAF). The AMF 264 also interacts with the Authentication Server Function (AUSF) (not shown) and the UE 204, and receives an intermediate key established as a result of the UE 204's authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM) authentication, AMF 264 retrieves security material from AUSF. AMF 264 also includes Security Context Management (SCM). The SCM receives a key from SEAF, which it uses to derive access network-specific keys. AMF 264 also includes location service management for regulatory services, transmission of location service messages between UE 204 and Location Management Function (LMF) 270 (which acts as location server 230), transmission of location service messages between NG-RAN 220 and LMF 270, Evolved Packet System (EPS) bearer identifier allocation for EPS interoperability, and UE 204 mobility event notification. Furthermore, AMF 264 supports functions for non-3GPP (3rd Generation Partnership Project) access networks.

[0079] The functions of UPF 262 include: acting as an anchor point for intra / inter-RAT mobility (where applicable), acting as an external Protocol Data Unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic orientation), lawful eavesdropping (user plane collection), traffic usage reporting, user plane Quality of Service (QoS) processing (e.g., uplink / downlink rate enforcement, reflected QoS marking in the downlink), uplink traffic verification (Service Data Flow (SDF) to QoS flow mapping), transport-level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the transmission of location service messages between UE 204 and a location server (such as SLP 272) on the user plane.

[0080] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, service bootstrapping configuration at UPF 262 for routing services to the correct destination, partial control of policy enforcement and QoS, and downlink data notification. The interface used by SMF 266 to communicate with AMF 264 is called the N11 interface.

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

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

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

[0084] The functionality of the gNB 222 is divided among the gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions such as transmitting user data, mobility control, radio access network sharing, positioning, and session management, in addition to those functions specifically allocated to the gNB-DU 228. More specifically, the gNB-CU 226 generally manages the radio resource control (RRC), serving data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) of the gNB 222. The gNB-DU 228 is a logical node that generally manages the radio link control (RLC) and media access control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and a cell is supported by only one gNB-DU 228. The interface 232 between gNB-CU 226 and one or more gNB-DU 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of gNB 222 is typically managed by one or more independent gNB-RU 229s, which perform functions such as power amplification and signal transmission / reception. The interface between gNB-DU 228 and gNB-RU 229 is referred to as the "Fx" interface. Thus, UE 204 communicates with gNB-CU 226 via the RRC, SDAP, and PDCP layers, with gNB-DU 228 via the RLC and MAC layers, and with gNB-RU 229 via the PHY layer.

[0085] Figure 3A , Figure 3B and Figure 3CThe diagram shows a UE 302 (which may correspond to any UE described herein), a base station 304 (which may correspond to any base station described herein), and a network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of...). Figure 2A and Figure 2B Several example components (represented by corresponding boxes) in the NG-RAN 220 and / or 5GC 210 / 260 infrastructure (such as a private network) depicted herein support file transmission operations as taught herein. It will be understood that these components can be implemented in different specific implementations in different types of devices (e.g., in an ASIC, in a system-on-a-chip (SoC), etc.). The components shown can also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described as providing functionality. Furthermore, a given device may contain one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

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

[0087] In at least some cases, UE 302 and base station 304 each further include one or more short-range radio transceivers 320 and 360, respectively. The short-range radio transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide the capability to communicate over the wireless communication medium of interest via at least one designated RAT (e.g., WiFi, LTE-D, etc.). Modules (e.g., modules for transmitting, receiving, measuring, tuning, and blocking transmission, etc.) that enable communication between PC5, Dedicated Short Range Communication (DSRC), Wireless Access for Vehicle Environments (WAVE), Near Field Communication (NFC), etc.) and other network nodes (such as other UEs, access points, base stations, etc.). Short-range transceivers 320 and 360 can be configured in various ways to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.). Specifically, short-range transceivers 320 and 360 each include: one or more transmitters 324 and 364 for transmitting and encoding signals 328 and 368 respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368 respectively. As specific examples, the short-range wireless transceivers 320 and 360 can be WiFi transceivers, transceiver and / or Transceivers, NFC transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0088] In at least some cases, UE 302 and base station 304 also include satellite signal receivers 330 and 370. Satellite signal receivers 330 and 370 can be connected to one or more antennas 336 and 376, respectively, and can be provided with modules for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. When satellite signal receivers 330 and 370 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 can be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVC), Quasi-Zenith Satellite System (QZSS), etc. When satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, satellite positioning / communication signals 338 and 378 can be communication signals originating from a 5G network (e.g., carrying control and / or user data). Satellite signal receivers 330 and 370 may include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request appropriate information and operations from other systems, and, at least in some cases, perform calculations using measurements obtained by any suitable satellite positioning system algorithm to determine the locations of UE 302 and base station 304, respectively.

[0089] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, which provide modules (e.g., modules for transmitting, modules for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, base station 304 can use one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, network entity 306 can use one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or to communicate with other network entities 306 via one or more wired or wireless core network interfaces.

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

[0091] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360 in some embodiments, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some embodiments) can generally be characterized as "transceiver", "at least one transceiver", or "one or more transceivers". Thus, whether a particular transceiver is a wired or wireless transceiver can be inferred from the type of communication performed. For example, backhaul communication between network devices or servers typically involves signaling via a wired transceiver, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) typically involves signaling via a wireless transceiver.

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

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

[0094] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide modules for sensing or detecting motion and / or orientation information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. As an example, sensor 344 may include accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of motion detection sensor. Furthermore, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the ability to calculate position in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems.

[0095] Additionally, UE 302 includes a user interface 346 that provides modules for providing instructions to a user (e.g., audible and / or visual instructions) and / or for receiving user input (e.g., when the user actuates a sensing device (such as a keypad, touchscreen, microphone, etc.)). Although not shown, base station 304 and network entity 306 may also include user interfaces.

[0096] Referring more specifically to one or more processors 384, in the downlink, IP packets from network entity 306 can be provided to processor 384. One or more processors 384 can implement functions for the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. One or more processors 384 may provide: RRC layer functions associated with broadcasting system information (e.g., Master Information Block (MIB), System Information Block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with the transmission of upper-layer PDUs, error correction via Automatic Repeat Request (ARQ), concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel priority ordering.

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

[0098] At UE 302, receiver 312 receives signals via its corresponding antenna 316. Receiver 312 recovers the information modulated onto the RF carrier and provides this information to one or more processors 332. Transmitter 314 and receiver 312 implement Layer 1 functions associated with various signal processing functions. Receiver 312 can perform spatial processing on this information to recover any spatial stream destined for UE 302. If multiple spatial streams are destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. Symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the signal constellation points most likely to be transmitted by base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement layer 3 (L3) and layer (L2) 2 functions.

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

[0100] Similar to the functions described in conjunction with downlink transmissions performed by base station 304, one or more processors 332 provide: RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with upper-layer PDU transmission, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via Hybrid Automatic Repeat Request (HARQ), priority handling, and logical channel priority ordering.

[0101] The channel estimate derived by the channel estimator from the reference signal or feedback transmitted by the base station 304 can be used by the transmitter 314 to select an appropriate decoding and modulation scheme and facilitates spatial processing. The spatial stream generated by the transmitter 314 can be provided to different antennas 316. The transmitter 314 can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0102] Uplink transmissions are processed at base station 304 in a manner similar to that described in conjunction with the receiver function at UE 302. Receiver 352 receives signals via its respective antenna 356. Receiver 352 recovers the information modulated onto the RF carrier and provides this information to one or more processors 384.

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

[0104] For convenience, UE 302, base station 304 and / or network entity 306 are in Figure 3A , Figure 3B and Figure 3C The text is shown as including various components that can be configured according to the various examples described herein. However, it will be understood that the components shown may have different functionalities in different designs. In particular, Figures 3A to 3C Various components are optional in alternative configurations, and aspects include configurations that can vary due to design choices, cost, equipment usage, or other considerations. For example, in Figure 3A In certain cases, specific implementations of UE 302 may omit WWAN transceiver 310 (e.g., wearable devices, tablets, PCs, or laptops may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or short-range wireless transceiver 320 (e.g., cellular only), or satellite signal receiver 330, or sensor 344, etc. In another example, in Figure 3B In certain cases, specific implementations of base station 304 may omit WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or short-range wireless transceiver 360 (e.g., cellular only), or satellite receiver 370, etc. For the sake of brevity, examples of various alternative configurations are not provided herein, but will be readily understood by those skilled in the art.

[0105] The various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 334, 382, ​​and 392, respectively. In one aspect, data buses 334, 382, ​​and 392 can form or be part of the communication interfaces of UE 302, base station 304, and network entity 306, respectively. For example, when different logical entities are contained within the same device (e.g., gNB and location server functions integrated into the same base station 304), data buses 334, 382, ​​and 392 can provide communication between them.

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

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

[0108] Various frame structures can be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). Figure 4 Figure 400 illustrates an example frame structure according to various aspects of this disclosure. This frame structure can be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

[0109] LTE, and in some cases NR, utilizes OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR has the option to also use OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are often referred to as frequency modulation, frequency slots, etc. Each subcarrier can be used to modulate data. Generally, the modulated symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal FFT size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into multiple subbands. For example, a subband can cover 1.08MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25MHz, 2.5MHz, 5MHz, 10MHz, or 20MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively.

[0110] LTE supports a single set of parameters (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR can support multiple sets of parameters (μ), for example, subcarrier spacings of 15kHz (μ=0), 30kHz (μ=1), 60kHz (μ=2), 120kHz (μ=3), and 240kHz (μ=4) or larger can be available. Within each subcarrier spacing, there are 14 symbols per time slot. For a 15kHz SCS (μ=0), there is one time slot per subframe, 10 time slots per frame, a time slot duration of 1 millisecond (ms), a symbol duration of 66.7 microseconds (μs), and a maximum nominal system bandwidth (in MHz) of 4K FFT size is 50. For a 30kHz SCS (μ=1), there are two time slots per subframe, 20 time slots per frame, a time slot duration of 0.5ms, a symbol duration of 33.3μs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 60kHz SCS (μ=2), there are four time slots per subframe, 40 time slots per frame, a time slot duration of 0.25ms, a symbol duration of 16.7μs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 120kHz SCS (μ=3), there are eight time slots per subframe, 80 time slots per frame, a time slot duration of 0.125ms, a symbol duration of 8.33μs, and a maximum nominal system bandwidth (in MHz) of 4K FFT size. For a 240kHz SCS (μ=4), there are 16 time slots per subframe, 160 time slots per frame, a time slot duration of 0.0625ms, a symbol duration of 4.17μs, and a maximum nominal system bandwidth (in MHz) of 4KFFT size.

[0111] exist Figure 4 In the example, a parameter set of 15kHz is used. Therefore, in the time domain, a 10ms frame is divided into 10 equal-sized subframes, each 1ms in size, and each subframe includes one time slot. Figure 4 In this representation, time is shown horizontally (on the X-axis), with time increasing from left to right, while frequency is shown vertically (on the Y-axis), with frequency increasing (or decreasing) from bottom to top.

[0112] A resource grid can be used to represent time slots, each time slot comprising one or more concurrent resource blocks (RBs) (also known as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE can correspond to a symbol length in the time domain and a subcarrier in the frequency domain. Figure 4In the parameter set, for a normal cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, the RB can contain 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0113] Some REs may carry reference (pilot) signals (RS). These reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), probe reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication. Figure 4 An example location of the RE carrying the reference signal is shown (labeled "R").

[0114] The set of resource elements (REs) used for PRS transmission is called a "PRS resource". The resource element set can span multiple PRBs in the frequency domain and span "N" (such as one or more) consecutive symbols within a time slot in the time domain. In a given OFDM symbol in the time domain, the PRS resource occupies a coherent PRB in the frequency domain.

[0115] The transmission of PRS resources within a given PRB has a specific comb size (also known as "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / frequency modulation spacing) within each symbol of the PRS resource configuration. Specifically, for a comb size "N", the PRS is transmitted in every Nth subcarrier of a symbol in the PRB. For example, for comb-4, for each symbol of the PRS resource configuration, the RE corresponding to every fourth subcarrier (such as subcarriers 0, 4, 8) is used to transmit the PRS of the PRS resource. Currently, comb sizes for comb-2, comb-4, comb-6, and comb-12 are supported by DL-PRS. Figure 4 An example PRS resource configuration for Comb-4 (which spans four symbols) is shown. That is, the position of the shaded RE (marked as "R") indicates the PRS resource configuration for Comb-4.

[0116] Currently, DL-PRS resources can span 2, 4, 6, or 12 consecutive symbols within a single time slot using a full-frequency-domain interleaved mode. DL-PRS resources can be configured in any downlink or flexible (FL) symbol configured by a higher layer within a time slot. For all REs of a given DL-PRS resource, there may be a constant energy per resource element (EPRE). The following are the symbol-by-symbol frequency offsets for comb sizes 2, 4, 6, and 12 on 2, 4, 6, and 12 symbols. 2-symbol comb-2: {0, 1}; 4-symbol comb-2: {0, 1, 0, 1}; 6-symbol comb-2: {0, 1, 0, 1, 0, 1}; 12-symbol comb-2: {0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1}; 4-symbol comb-4: {0, 2, 1, 3} (as in...). Figure 4 (in the example); 12-code comb-4: {0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3}; 6-code comb-6: {0, 3, 1, 4, 2, 5}; 12-code comb-6: {0, 3, 1, 4, 2, 5, 0, 3, 1, 4, 2, 5}; and 12-code comb-12: {0, 6, 3, 9, 1, 7, 4, 10, 2, 8, 5, 11}.

[0117] A "PRS resource set" is a set of PRS resources used to transmit PRS signals, where each PRS resource has a PRS resource ID. Furthermore, PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and associated with a specific TRP (identified by a TRP ID). Additionally, PRS resources in a PRS resource set share the same periodicity, a common silent mode configuration, and the same repetition factor (such as "PRS-ResourceRepetitionFactor") across time slots. The periodicity is the time from the first repetition of the first PRS resource in the first PRS instance to the same first repetition of the same first PRS resource in the next PRS instance. The periodicity can have a length selected from the following: 2^μ*{4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} time slots, where μ = 0, 1, 2, 3. The repetition factor can have a length selected from {1, 2, 4, 6, 8, 16, 32} time slots.

[0118] In a PRS resource set, a PRS resource ID is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP can transmit one or more beams). That is, each PRS resource in a PRS resource set can transmit on a different beam, and therefore, a "PRS resource" (or simply "resource") can also be referred to as a "beam". It should be noted that this does not imply whether the UE is aware of the TRP and beam transmitting the PRS.

[0119] A “PRS instance” or “PRS timing” is an instance of a periodically repeating time window in which a PRS is expected to be emitted. A PRS timing may also be referred to as a “PRS positioning timing”, “PRS positioning instance”, “positioning timing”, “positioning instance”, “positioning repetition”, or simply “timing”, “instance”, or “repetition”.

[0120] A “Frequency Layer” (also simply “Frequency Layer”) is a collection of one or more PRS resource sets with identical values ​​for certain parameters across one or more TRPs. Specifically, the collection of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all parameter sets supported for the Physical Downlink Shared Channel (PDSCH) are also supported by the PRS), the same Point A, the same downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The Point A parameter uses the value of the parameter “ARFCN-ValueNR” (where “ARFCN” stands for “Absolute Radio Channel Number”) and is an identifier / code specifying a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth can have a granularity of 4 PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, up to four Frequency Layers have been defined, and up to two PRS resource sets can be configured per TRP per Frequency Layer.

[0121] The concept of a frequency layer is somewhat similar to that of component carriers and bandwidth portions (BWPs), but the difference is that component carriers and BWPs are used by a single base station (or macrocell base station and small cell base station) to transmit data channels, while a frequency layer is used by several (often three or more) base stations to transmit PRSs. A UE can indicate the number of frequency layers it can support when sending its positioning capabilities to the network (such as during an LTE Positioning Protocol (LPP) session). For example, a UE can indicate whether it can support one or four positioning frequency layers.

[0122] It should be noted that the terms "location reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "location reference signal" and "PRS" can also refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc., as defined in LTE and NR. Furthermore, the terms "location reference signal" and "PRS" can refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. If further distinction of the type of PRS is required, downlink positioning reference signals may be referred to as "DL-PRS," while uplink positioning reference signals (e.g., SRS, PTRS used for positioning) may be referred to as "UL-PRS." Additionally, for signals that can be transmitted in both the uplink and downlink (e.g., DMRS, PTRS), these signals may be prefixed with "UL" or "DL" to distinguish direction. For example, “UL-DMRS” can be distinguished from “DL-DMRS”.

[0123] NR supports several cellular network-based (also known as Uu-based) positioning technologies, including downlink-based positioning methods, uplink-based positioning methods, and positioning methods based on both downlink and uplink. Downlink-based positioning methods include: Observed Time Difference of Arrival (OTDOA) in LTE, Downlink Time Difference of Arrival (DL-TDOA) in NR, and Downlink Angle of Departure (DL-AoD) in NR. Figure 5 Examples of various positioning methods according to aspects of this disclosure are shown. In OTDOA or DL-TDOA positioning, as shown in scenario 510, the UE measures the difference between the times of arrival (ToA) of a reference signal (e.g., a positioning reference signal (PRS)) received from a base station (referred to as Reference Signal Time Difference (RSTD) or Time Difference of Arrival (TDOA) measurement) and reports these differences to a positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in auxiliary data. The UE then measures the RSTD between the reference base station and each non-reference base station. Based on the known locations of the base stations involved and the RSTD measurement, a positioning entity (e.g., a UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the UE's location.

[0124] For DL-AoD positioning as shown in Scenario 520, the positioning entity uses beam reports from the UE regarding received signal strength measurements of multiple downlink transmit beams to determine the angle between the UE and the transmitting base station. The positioning entity can then estimate the UE's location based on the determined angle and the known location of the transmitting base station.

[0125] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but it is based on an uplink reference signal (e.g., a probe reference signal (SRS)) transmitted by the UE. For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from the UE on one or more uplink receive beams. The positioning entity uses the signal strength measurement and the angle of the receive beam to determine the angle between the UE and the base stations. Based on the determined angle and the known location of the base stations, the positioning entity can then estimate the location of the UE.

[0126] Downlink and uplink-based positioning methods include Enhanced Cell ID (E-CID) positioning and Multiple Round-Trip Time (RTT) positioning (also known as "Multi-Cell RTT" and "Multi-RTT"). During RTT, a first entity (e.g., a base station or a UE) transmits a first RTT-related signal (e.g., PRS or SRS) to a second entity (e.g., a UE or a base station), and the second entity transmits a second RTT-related signal (e.g., SRS or PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is called the received-to-transmit (Rx-Tx) time difference. The Rx-Tx time difference measurement can be performed or adjusted to include only the time difference between the nearest subframe boundary of the received signal and the transmitted signal. Two entities can then send their Rx-Tx time difference measurements to a location server (e.g., LMF 270), which calculates the round-trip time (i.e., RTT) between the two entities based on these two Rx-Tx time difference measurements (e.g., calculated as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity can send its Rx-Tx time difference measurement to another entity, which then calculates the RTT. The distance between the two entities can be determined based on the RTT and a known signal speed (e.g., the speed of light). For multi-RTT positioning, as shown in scenario 530, a first entity (e.g., a UE or base station) performs an RTT positioning process with multiple second entities (e.g., multiple base stations or UEs) to enable the location of the first entity to be determined (e.g., using polygonal measurements) based on the distance to the second entities and the known location of the second entities. RTT and multi-RTT methods can be combined with other positioning technologies (such as UL-AoA and DL-AoD) to improve location accuracy, as shown in scenario 540.

[0127] The E-CID positioning method is based on Radio Resource Management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and the identifiers, estimated timings, and signal strengths of detected neighboring base stations. The UE's location is then estimated based on this information and the known locations of the base stations.

[0128] To assist in the positioning operation, a location server (e.g., location server 230, LMF 270, SLP 272) may provide auxiliary data to the UE. For example, auxiliary data may include: the identifier of the base station (or the cell / TRP of the base station) from which the reference signal is measured, reference signal configuration parameters (e.g., the number of consecutive positioning subframes, the periodicity of the positioning subframes, the silence sequence, the frequency hopping sequence, the reference signal identifier, the reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, auxiliary data may be derived directly from the base station itself (e.g., in periodically broadcast overhead messages, etc.). In some cases, the UE may be able to detect neighboring network nodes without using auxiliary data.

[0129] In OTDOA or DL-TDOA positioning procedures, auxiliary data may also include the expected RSTD value and associated uncertainty, or a search window around the expected RSTD. In some cases, the expected RSTD value may range from + / - 500 microseconds (μs). In some cases, when any resources used for positioning measurements are in FR1, the uncertainty of the expected RSTD may range from + / - 32 μs. In other cases, when all resources used for positioning measurements are in FR2, the uncertainty of the expected RSTD may range from + / - 8 μs.

[0130] Location estimates can be referred to by other names, such as location estimation, location, positioning, location locking, locking, etc. Location estimates can be geodetic and include coordinates (e.g., latitude, longitude, and possible elevation), or they can be municipal and include street addresses, postal addresses, or some other verbal description of the location. Location estimates can be further defined relative to some other known location or in absolute terms (e.g., using latitude, longitude, and possible elevation). Location estimates can include expected errors or uncertainties (e.g., by including the area or volume that the location is expected to be included within at a specified or default confidence level).

[0131] NR also supports or implements various sidelink positioning technologies. Figure 6AVarious scenarios of interest for sidelink-only or combined Uu and sidelink positioning according to aspects of this disclosure are illustrated. In scenario 610, at least one peer UE with a known location can improve the Uu-based positioning of a target UE (e.g., multiple RTT, DL-TDOA, etc.) by providing additional anchor points (e.g., using a sidelink (SL-RTT)). In scenario 620, a low-end (e.g., low-capacity or "RedCap") target UE can obtain assistance from a high-end UE to determine its location using, for example, a sidelink positioning and ranging process with the high-end UE. Compared to the low-end UE, the high-end UE may have more capabilities, such as more sensors, a faster processor, more memory, more antenna elements, higher transmission power capabilities, access to additional frequency bands, or any combination thereof. In scenario 630, a relay UE (e.g., with a known location) participates in the positioning estimation of a remote UE without performing uplink PRS transmissions via the Uu interface. Scenario 640 illustrates joint positioning of multiple UEs. Specifically, in scenario 640, by utilizing constraints from nearby UEs, two UEs with unknown locations can be jointly located under non-line-of-sight (NLOS) conditions.

[0132] Figure 6B Additional scenarios of interest are illustrated for sidelink-only or combined Uu and sidelink positioning according to various aspects of this disclosure. In scenario 650, a UE used for public safety (e.g., by police, firefighters, etc.) may perform peer-to-peer (P2P) positioning and ranging for public safety and other purposes. For example, in scenario 650, a public safety UE may be outside the network coverage area and sidelink positioning technology may be used to determine the location or relative distance and relative positioning between public safety UEs. Similarly, scenario 660 illustrates multiple UEs outside the coverage area and the use of sidelink positioning technology (such as SL-RTT) to determine the location or relative distance and relative positioning.

[0133] Figure 7An example sidelink ranging and positioning procedure 700 according to various aspects of this disclosure is illustrated. The sidelink ranging and positioning procedure 700 may also be referred to as a sidelink RTT positioning procedure. Sidelink ranging is based on calculating inter-UE RTT measurements, such as those determined from the transmission and reception times of the PRS (a wideband reference signal defined for positioning in LTE and NR). Each UE reports its RTT measurement along with its location (if known) to all other participating UEs. For UEs that do not know their location at all or do not know it accurately, the RTT procedure generates an inter-UE distance between the involved UEs. For UEs that know their location accurately, the ranging generates an absolute location. UE participation, PRS transmission, and subsequent RTT calculation are coordinated by an initial three-way message handshake (PRS request, PRS response, and PRS acknowledgment) and a post-PRS message exchange (post-PRS message) for sharing measurements after receiving the PRS from a peer UE.

[0134] The sidelink ranging and positioning process 700 (or session) begins at stage 705 with capability information broadcast by the involved peer UE. For example... Figure 7 As shown, one of the peer UEs, UE 204-1 (e.g., any UE with sidelink capability described herein), is capable of acting as an anchor UE for the sidelink ranging and positioning procedure 700, meaning that the location of this UE is known. Therefore, anchor UE 204-1 includes in its capability message an indication that it is capable of acting as an anchor UE for the sidelink ranging and positioning procedure 700. The capability message may also include the location of anchor UE 204-1, or that location may be provided later. Another UE, UE 204-2 (e.g., any other UE with sidelink capability described herein), is the target UE, meaning that the location of this UE is unknown or inaccurate and that this UE is attempting to be located. Based on the capability information received from anchor UE 204-1 indicating that anchor UE 204-1 is the anchor UE, target UE 204-2 knows that it will be able to determine its location based on performing the sidelink ranging and positioning procedure 700 with anchor UE 204-1.

[0135] Following the initial capability exchange, the involved UE 204 performs a three-way message handshake. At phase 710, anchor UE 204-1 sends a PRS request (marked "PRSrequest") to target UE 204-2. At phase 715, target UE 204-2 sends a PRS response (marked "PRSresponse") to anchor UE 204-1. At phase 720, anchor UE 204-1 sends a PRS acknowledgment to target UE 204-2. At this point, the three-way message handshake is complete.

[0136] At stages 725 and 730, the involved peer UEs 204 transmit PRS to each other. The resources for transmitting PRS can be configured / allocated by the network (e.g., the serving base station of one of these UEs 204) or negotiated by these UEs 204 during the three-way message handshake. Anchor UE 204-1 measures the transmit-to-receive (Tx-Rx) time difference between the PRS transmission time at stage 725 and the PRS reception time at stage 730. Target UE 204-2 measures the receive-to-transmit (Rx-Tx) time difference between the PRS reception time at stage 725 and the PRS transmission time at stage 730.

[0137] At stages 735 and 740, peer UE 204 exchanges their respective time difference measurements in a postPRS message (labeled "postPRS"). If anchor UE 204-1 has not yet provided its location to target UE 204-2, it does so at this time. Each UE 204 is then able to determine the RTT between each UE 204 based on the Tx-Rx and Rx-Tx time difference measurements (specifically, the difference between the Tx-Rx and Rx-Tx time difference measurements). Based on the RTT measurements and the speed of light, each UE 204 can then estimate the distance (or range) between the two UEs 204 (specifically, the RTT measurement multiplied by half the speed of light). Since target UE 204-2 also has the absolute location (e.g., geographic coordinates) of anchor UE 204-1, target UE 204-2 can use that location and the distance to anchor UE 204-1 to determine its own absolute location.

[0138] Note that, although Figure 7 Two UEs 204 are shown, but the UE can perform or attempt to perform sidelink ranging and positioning procedures 700 with multiple UEs.

[0139] Even when no traffic is being transmitted from the network to the UE, the UE is expected to monitor every downlink subframe on the Physical Downlink Control Channel (PDCCH). This means that even when there is no traffic, the UE must remain "on" or active because it cannot know exactly when the network will transmit data to it. However, being constantly active consumes a considerable amount of power for the UE.

[0140] To address this issue, the UE can implement Discontinuous Reception (DRX) and / or Connected Mode Discontinuous Reception (CDRX) technologies. DRX and CDRX are mechanisms by which the UE enters a "sleep" mode for a scheduled time period and "wakes up" for other time periods. During a wake-up or active period, the UE checks for any data from the network, and if no data is received, it returns to sleep mode.

[0141] To implement DRX and CDRX, the UE and network need to be synchronized. In the worst-case scenario, the network might attempt to send data to the UE while it is in sleep mode, and the UE might wake up when there is no data to receive. To prevent such scenarios, the UE and network should have a well-defined agreement regarding when the UE can be in sleep mode and when it should wake up / be active. This agreement has been standardized in various technical specifications. Note that DRX includes CDRX, and therefore, references to DRX refer to both DRX and CDRX unless otherwise indicated.

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

[0143] Figures 8A to 8C Example DRX configurations based on various aspects of this disclosure are shown. Figure 8A An example DRX configuration 800A is shown, in which a long DRX cycle (the time from the start of one on-duration to the start of the next on-duration) is configured and no PDCCH is received during the cycle. Figure 8BAn example DRX configuration 800B is shown, in which a long DRX cycle is configured and a PDCCH is received during the on-duration 810 of the second DRX cycle shown. It should be noted that the on-duration 810 ends at time 812. However, based on the length of the DRX inactive timer and the time the PDCCH is received, the UE wake-up / active time (“active time”) is extended to time 814. Specifically, when a PDCCH is received, the UE starts a DRX inactive timer and remains in an active state until the timer expires (the timer is reset each time a PDCCH is received during the active time).

[0144] Figure 8C An example DRX configuration 800C is shown, in which a long DRX cycle is configured and a PDCCH and DRX command MAC control element (MAC-CE) are received during the on-duration 820 of the second DRX cycle shown. It should be noted that since the PDCCH is received at time 822 and the DRX inactive timer subsequently expires at time 824, the active time that begins during the on-duration 820 will normally end at time 824, as referenced above. Figure 8B The subject of discussion. However, in Figure 8C In the example, based on the time when the DRX command MAC CE, which instructs the UE to terminate the DRX inactive timer and start the duration timer, is received, the active time is shortened to time 826.

[0145] More specifically, the active time of the DRX cycle is the period during which the UE is considered to be monitoring the PDCCH. The active time may include the following periods: the start duration timer is running, the DRX inactivity timer is running, the DRX retransmission timer is running, the MAC contention resolution timer is running, a scheduling request has been sent on the Physical Uplink Control Channel (PUCCH) and is pending, uplink granting for pending HARQ retransmissions may occur and data exists in the corresponding HARQ buffer, or a new transmission indicating the Cell Radio Network Temporary Identifier (C-RNTI) addressed to the UE has not been received after successfully receiving a Random Access Response (RAR) with a preamble not selected by the UE. Furthermore, in contention-based random access, after receiving the RAR, the UE should be active until a new transmission indicating the C-RNTI addressed to the UE is received.

[0146] Note that a UE may have a Uu DRX configuration for communicating with its serving base station and a sidelink DRX configuration for sidelink communication with one or more other UEs. The reference to “DRX” in this document refers to either or both of the Uu and sidelink DRX configurations unless the context explicitly expects one or the other.

[0147] In NR, it is typically assumed that the location of each UE is calculated independently at a location server (UE-assisted positioning), or that each UE calculates its own location (UE-based positioning). This disclosure explores the concept of joint positioning for a group of UEs, where measurements are used to jointly assess the location of each UE in the group. Alternatively, in most sidelink positioning scenarios, the service of a UE whose location is known with relatively high accuracy is used as the anchor node. In this case, relative location is an exception where none of the UEs knows their absolute location. The case of utilizing the service of a UE whose location is unknown can also be considered, but the UE can perform measurements as part of the joint positioning process.

[0148] As an existing joint positioning technology, a "free-rider mode" has been introduced, in which the target UE transmits measurements from nearby source UEs as its own. As another existing joint positioning technology, a "shared mode" has been introduced, in which the measurement task is split across multiple UEs and coordinated by a location server.

[0149] Previous work on ride-sharing and carpooling modes involved use cases where all UEs were very close to each other and ultimately obtained the same location estimate. This meant that one of them needed to perform localization, and the other UEs could share the localization results. In such scenarios, one UE is the anchor UE, and the other UEs are the target UEs.

[0150] This disclosure discusses certain aspects of selecting anchor UEs. Figure 9 Figure 900 illustrates an example joint / cooperative localization scenario according to various aspects of this disclosure. Figure 9 In the example, there are three peer UEs within the gNB's coverage area, labeled "UE1", "UE2", and "UE3". Dashed lines indicate the possible links between various nodes. For example, a UE can measure the downlink PRS from the gNB via the link between the gNB and the UE, and a UE can measure the sidelink PRS via the link between UEs. If the anchor UE's measurements / location are known, the location of other UEs can be calculated using minimal measurements. That is, each UE does not need to perform all PRS measurements. Instead, some UEs can borrow measurements from nearby UEs (e.g., at least one anchor UE) and use sidelink measurements. Therefore, the question is how to select the anchor UE to perform the location measurements.

[0151] Figure 10Figure 1000 illustrates example DRX configurations of different peer UEs participating in a joint positioning session according to various aspects of this disclosure. Figure 10 In the example, three UEs labeled "UE1", "UE2", and "UE3" are operating in DRX mode. Each box represents the DRX active time and is separated by the DRX cycle length. Furthermore, each UE has received the same auxiliary data for the joint positioning session, meaning they are expected to measure the same PRS. The arrows indicate the scheduled PRS to be measured.

[0152] Because all UEs are independent and have their own International Mobile Subscriber Identity (IMSI) value, their DRX cycle length and DRX cycle start time may differ, such as... Figure 10 As shown. This provides the opportunity to select the UE with the optimal DRX configuration for a given auxiliary data. The optimal DRX configuration is one where the UE's PRS measurement is close to the point where the UE wakes up to receive a paging message and performs RRM measurements for cell management. In the example shown, it is advantageous for either UE1 or UE3 to perform the PRS measurement.

[0153] As a first technique described herein, a location server (e.g., LMF 270) may select an anchor UE. In this case, the location server requests the Uu and sidelink DRX configurations of all UEs in the joint positioning session. Note that this request may be directed to the UE itself; alternatively, if the identities of the UEs in the group are known, the serving AMF may provide this information. The location server may then select an anchor UE (or multiple anchor UEs) and notify that UE (or those UEs) that it has been selected as an anchor UE. The selected UE then performs downlink PRS measurements and reports the measurements to the other UEs in the group (for UE-based positioning) or to the location server (for UE-assisted positioning).

[0154] As a second technique, additional information can be used to select the anchor UE. For example, the location server can also consider the battery status of the UE involved, the type and capabilities of the UE, the bandwidth portion (BWP) configured for the UE, etc. For example, in an industrial environment, some UEs have higher capabilities (e.g., robots), while some UEs have lower capabilities (e.g., sensors, actuators, etc.). In such scenarios, selecting a UE with higher capabilities may be beneficial because it allows for the execution of more measurements with better resolution.

[0155] As a third technology, the UE can request a new DRX configuration (e.g., DRX length) from the gNB to align the location measurement timing with the DRX active timing (or simply DRX timing). For example, the UE can request to increase or decrease the DRX cycle length. Alternatively, the location server can suggest a new DRX configuration for the UE to align with PRS transmissions to the gNB or AMF.

[0156] As a fourth technology, a DRX group can be created for a set of peer UEs, and all UEs can be configured to share Uu and sidelink DRX configurations. In the most general sense, "shared" can mean that there is a set of overlapping time slots (or other time periods) in which each UE (or a large subset of UEs) is active. For example, the first UE (denoted as "UE1") may have Uu DRX active periods from time slot 0 to time slot 10, the second UE (denoted as "UE2") may have Uu DRX active periods from time slot 5 to time slot 10, and the third UE (denoted as "UE3") may have Uu DRX active periods from time slot 3 to time slot 8. Therefore, each UE is active from time slot 5 to time slot 8. As another example, UE1, UE2, and UE3 can be configured to have sidelink DRX active periods from time slot 11 to time slot 15.

[0157] This shared DRX configuration is closely aligned with the PRS configuration and can accommodate sidelink communication within the group. Sidelink DRX configurations and sidelink resource pool configurations can also be considered. In each aspect, the location server (e.g., LMF 270) coordinates with the serving AMF to generate grouped and matched DRX configurations.

[0158] Since all UEs measure the same or similar PRS instances, the benefits of the above techniques include improved power savings and enhanced location measurement quality at all UEs. More specifically, measuring the PRS of individual UEs for other UEs only works if the UEs involved are very close to each other. To obtain a good estimate of the individual location of each UE, it is best to measure the PRS of all UEs. However, this location is also calculated jointly by taking into account sidelink measurements, which improves the overall quality compared to location per UE.

[0159] Figure 11 An example joint positioning session 1100 is shown, in which one of the UEs is selected as the anchor UE for the remaining UEs according to various aspects of this disclosure. Figure 11In the example, three peer UEs, 204-1, 204-2, and 204-3, labeled "UE1", "UE2", and "UE3" respectively, are close enough to each other that they have been selected to participate in the joint positioning session 1100. For example, the LMF270 may select UE 204 based on UE 204 being served by the same cell or beam of gNB 222. Alternatively, the LMF 270 may select UE 204 based on UE 204 being in a sidelink group.

[0160] At 1105, the joint positioning session 1100 begins. At 1110, each UE 204 sends a DRX configuration update message to the LMF 270, indicating its corresponding Uu and / or sidelink DRX cycle, depending on its configured content. Each UE 204 may send its corresponding DRX configuration update message via one or more LPP messages. At 1115, the LMF 270 selects the UE 204 with the best DRX cycle, which is UE 204-1 in this case. (Refer to the above.) Figure 10 As described, the optimal DRX cycle is the DRX cycle that most closely matches the periodicity of the positioning timing (also known as the PRS timing or measurement timing) and / or the DRX timing (specifically, the DRX active time) that is closest to the positioning timing.

[0161] At 1120, LMF 270 sends an anchor selection update message to each of UEs 204, indicating that UE 204-1 has been selected as the anchor UE for joint positioning session 1100. This anchor selection update message can be an LPP message. At 1125, UE 204-1 performs positioning measurements for joint positioning session 1100. For example, joint positioning session 1100 can be a Uu-based positioning session (e.g., multi-RTT, DL-TDOA, etc.) and / or a sidelink-based positioning session (e.g., SL-RTT, SL-TDOA, etc.).

[0162] At 1130, UE 204-1 sends its measurement report to LMF 270. This measurement report may be included in one or more LPP messages and includes measurements of the DL-PRS and / or SL-PRS taken by UE 204-1. At 1135, LMF 270 sends a location report to UE 204-1 to indicate UE 204-1's location (as calculated based on the measurements in the measurement report). At 1140, UE 204-1 shares its location with other UEs (UE 204-2 and UE 204-3). UE 204-2 and 204-3 may then adopt this location as their own location, or, for example, perform an SL-RTT procedure with UE 204-1 to further refine their own location.

[0163] Figure 12 An example wireless positioning method 1200 according to various aspects of this disclosure is illustrated. In one aspect, method 1200 can be performed by a UE operating in DRX mode (e.g., any UE described herein).

[0164] At 1210, the UE receives an anchor selection update message from the location server, indicating that the UE has been selected as the anchor UE for a joint location session with one or more second UEs, wherein the selection is based at least in part on the fact that the UE's DRX active timing is closer to multiple measurement timings for the joint location session than the DRX active timings of the one or more second UEs. In one aspect, operation 1210 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, any or all of which may be considered as modules for performing the operation.

[0165] At 1220, in response to receiving the anchor selection update message, the UE performs a location measurement for the joint positioning session during one or more of the plurality of measurement times that overlap with the UE's DRX active time. In one aspect, operation 1220 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, any or all of which may be considered as modules for performing the operation.

[0166] At 1230, the UE transmits these positioning measurements, the location of the UE determined based on these positioning measurements, or both, to the one or more second UEs. In one aspect, operation 1230 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, any or all of which may be considered as modules for performing the operation.

[0167] Figure 13 An example location method 1300 according to various aspects of this disclosure is shown. In one aspect, method 1300 may be performed by a location server (e.g., LMF 270).

[0168] At 1310, the location server receives multiple DRX configurations from multiple UEs (e.g., any UE described herein) participating in a joint location session with each other, each DRX configuration indicating at least a DRX active time for the corresponding UE. In one aspect, operation 1310 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or location components 398, any or all of which may be considered as modules for performing the operation.

[0169] At 1320, the location server selects one of the plurality of UEs as the anchor UE based at least in part on the fact that the DRX active timing of the anchor UE for the joint location session is closer to a plurality of measurement timings for the joint location session than the DRX active timing of the remaining UEs among the plurality of UEs. In one aspect, operation 1320 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning components 398, any or all of which may be considered as modules for performing the operation.

[0170] At 1330, the location server transmits an anchor selection update message to each of the plurality of UEs, the anchor selection update message indicating that the anchor UE has been selected as the anchor UE for the joint location session. In one aspect, operation 1330 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or location components 398, any or all of these components may be considered as modules for performing the operation.

[0171] Figure 14 An example wireless positioning method 1400 according to various aspects of this disclosure is illustrated. In one aspect, method 1400 can be performed by a UE operating in DRX mode (e.g., any UE described herein).

[0172] At 1410, the UE receives an anchor selection update message from the location server, indicating that the peer UE has been selected as the anchor UE for a joint location session from among a plurality of UEs including the UE and the peer UE, wherein the peer UE is selected as the anchor UE at least in part based on the fact that the peer UE's DRX active timing is closer to a plurality of measurement timings for the joint location session than the DRX active timings of the remaining UEs among the plurality of UEs. In one aspect, operation 1410 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or location components 342, any or all of which may be considered as modules for performing the operation.

[0173] At 1420, the UE receives from the peer UE a positioning measurement performed by the peer UE for the joint positioning session, the location of the peer UE determined based on these positioning measurements, or both. In one aspect, operation 1420 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning components 342, any or all of which may be considered as modules for performing the operation.

[0174] As will be understood, the technical advantages of methods 1200 to 1400 are improved power savings for all involved UEs and improved positioning measurement quality.

[0175] As can be seen in the specific implementation described above, different features are grouped together in the examples. This manner of disclosure should not be construed as an intention to include more features in the example clauses than are expressly mentioned in each clause. Rather, aspects of this disclosure may include fewer features than those in the individual example clauses disclosed. Therefore, the following clauses should be regarded accordingly as included in the specification, wherein each clause may be considered as a separate example. Although each dependent clause may refer in the clause to a particular combination with one of the other clauses, the aspect of the dependent clause is not limited to that particular combination. It will be understood that other example clauses may also include combinations of aspects of a dependent clause with the subject matter of any other dependent or independent clauses, or combinations of any feature with other dependent and independent clauses. The aspects disclosed herein expressly include these combinations unless expressly stated or readily inferred that a particular combination is not expected (e.g., contradictory aspects, such as defining an element as both an insulator and a conductor). Furthermore, it is contemplated that aspects of a clause may be included in any other independent clause, even if that clause does not directly depend on the independent clause.

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

[0177] Clause 1. A radio positioning method performed by a user equipment (UE) operating in discontinuous reception (DRX) mode, comprising: receiving an anchor selection update message from a location server, the anchor selection update message indicating that the UE has been selected as an anchor UE for a joint positioning session with one or more second UEs, wherein the UE is selected as the anchor UE based at least in part on a DRX active timing of the UE being closer to a plurality of measurement timings for the joint positioning session than a DRX active timing of the one or more second UEs; in response to receiving the anchor selection update message, performing positioning measurements for the joint positioning session during one or more of the plurality of measurement timings overlapping with a DRX active timing of the UE; and transmitting the positioning measurements, a location of the UE determined based on the positioning measurements, or both, to the one or more second UEs.

[0178] Clause 2. The method according to Clause 1 further includes: transmitting a measurement report to the location server, the measurement report including the positioning measurement; and receiving a positioning report from the location server, the positioning report including at least the location of the UE.

[0179] Clause 3. The method according to any one of Clauses 1 to 2 further includes: determining the location of the UE.

[0180] Clause 4. The method according to any one of Clauses 1 to 3, wherein the UE is selected as the anchor UE based at least in part on the battery state, UE type, capability, bandwidth portion (BWP) or any combination thereof of the one or more second UEs.

[0181] Clause 5. The method according to any one of Clauses 1 to 4 further comprises: transmitting a request to a base station serving the UE for at least a new DRX cycle length, wherein the new DRX cycle length aligns the DRX active timing with the plurality of measurement timings.

[0182] Clause 6. The method according to any one of Clauses 1 to 5 further includes: receiving a first DRX configuration from a base station serving the UE, wherein the first DRX configuration is shared for the second DRX configuration of the one or more second UEs.

[0183] Clause 7. The method according to Clause 6, wherein the first DRX configuration is shared for the second DRX configuration of the one or more second UEs, including that the DRX active timing of the first DRX configuration and the DRX active timing of the second DRX configuration at least partially overlap.

[0184] Clause 8. The method according to any one of Clauses 6 to 7, wherein the first DRX configuration includes a Uu DRX configuration and a sidelink DRX configuration.

[0185] Clause 9. The method according to any one of Clauses 1 to 8 further comprises: transmitting a DRX configuration update message to a location server, the DRX configuration update message indicating the DRX configuration of the UE, the DRX configuration indicating the DRX active timing of the UE.

[0186] Clause 10. The method according to Clause 9 further includes: receiving a request for the DRX configuration from the location server.

[0187] Clause 11. A positioning method performed by a location server, comprising: receiving a plurality of discontinuous reception (DRX) configurations of a plurality of user equipments (UEs) participating in a joint positioning session with each other, each of the plurality of DRX configurations indicating at least a DRX active moment for the corresponding UE; selecting one of the plurality of UEs as an anchor UE for the joint positioning session, the selection being at least in part based on the fact that the DRX active moment for the anchor UE is closer to a plurality of measurement moments for the joint positioning session than the DRX active moments for the remaining UEs in the plurality of UEs; and transmitting an anchor selection update message to each of the plurality of UEs, the anchor selection update message indicating that the anchor UE has been selected as the anchor UE for the joint positioning session.

[0188] Clause 12. The method according to Clause 11, wherein: the plurality of DRX configurations are received from the plurality of UEs, or the plurality of DRX configurations are received from an Access and Mobility Management Function (AMF) serving the plurality of UEs.

[0189] Clause 13. The method according to any one of Clauses 11 to 12 further comprises: receiving a measurement report from the anchor UE, the measurement report including positioning measurements performed by the anchor UE for the joint positioning session; determining the location of the anchor UE based on the positioning measurements; and transmitting a positioning report to the anchor UE, the positioning report including at least the location of the anchor UE.

[0190] Clause 14. The method according to any one of Clauses 11 to 13, wherein the anchor UE is further selected as the anchor UE based at least in part on the anchor UE's battery state, UE type, capability, bandwidth portion (BWP), or any combination thereof compared with the battery state, UE type, capability, bandwidth portion (BWP), or any combination thereof of the remaining UEs among the plurality of UEs.

[0191] Clause 15. The method according to any one of Clauses 11 to 14 further comprises: transmitting a request for at least a new DRX cycle length for the anchor UE, wherein the new DRX cycle length aligns the DRX active timing of the anchor UE with the plurality of measurement timings.

[0192] Clause 16. The method according to Clause 15, wherein the request is sent to: the serving base station of the anchor UE, or the AMF serving the anchor UE.

[0193] Clause 17. The method according to any one of Clauses 11 to 16 further comprises: transmitting to an AMF serving the plurality of UEs a recommendation to group the plurality of UEs into DRX groups and to configure a shared DRX configuration for all UEs in the plurality of UEs; and transmitting to the AMF recommended DRX parameters for the shared DRX configuration, wherein the recommended DRX parameters cause the DRX activity timing of the plurality of UEs to at least partially overlap with the plurality of measurement timings.

[0194] Clause 18. The method described in Clause 17, wherein the shared DRX configuration includes a Uu DRX configuration and a sidelink DRX configuration.

[0195] Clause 19. The method according to any one of Clauses 11 to 18 further includes: receiving a plurality of DRX configuration update messages from the plurality of UEs, the plurality of DRX configuration update messages indicating a plurality of DRX configurations of the plurality of UEs.

[0196] Clause 20. The method according to Clause 19 further includes: transmitting multiple requests to the plurality of UEs for the plurality of DRX configurations.

[0197] Clause 21. A radio positioning method performed by a user equipment (UE) operating in discontinuous reception (DRX) mode, comprising: receiving an anchor selection update message from a location server, the anchor selection update message indicating that a peer UE has been selected from a plurality of UEs including the peer UE as an anchor UE for a joint positioning session, wherein the peer UE is selected as the anchor UE based at least in part on a DRX active timing of the peer UE being closer to a plurality of measurement timings for the joint positioning session than a DRX active timing of the remaining UEs among the plurality of UEs; and receiving from the peer UE a positioning measurement performed by the peer UE for the joint positioning session, a location of the peer UE determined based on the positioning measurement, or both.

[0198] Clause 22. The method according to Clause 21 further includes: using the location of the peer UE as the location of the UE.

[0199] Clause 23. The method according to any one of Clauses 21 to 22 further includes: determining the location of the UE based on the positioning measurement.

[0200] Clause 24. The method according to any one of Clauses 21 to 23 further comprises: transmitting a DRX configuration update message to a location server, the DRX configuration update message indicating the DRX configuration of the UE, the DRX configuration indicating the DRX active timing of the UE.

[0201] Clause 25. The method according to Clause 24 further includes: receiving a request for the DRX configuration from the location server.

[0202] Clause 26. A user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, from a location server an anchor selection update message indicating that the UE has been selected as an anchor UE for a joint positioning session with one or more second UEs, wherein the UE is selected as the anchor UE based at least in part on a DRX active timing of the UE being closer to a plurality of measurement timings for the joint positioning session than a DRX active timing of the one or more second UEs; in response to receiving the anchor selection update message, perform positioning measurements for the joint positioning session during one or more of the plurality of measurement timings overlapping with the DRX active timing of the UE; and transmit, via the at least one transceiver, the positioning measurements, a location of the UE determined based on the positioning measurements, or both, to the one or more second UEs.

[0203] Clause 27. The UE according to Clause 26, wherein the at least one processor is further configured to: transmit a measurement report to the location server via the at least one transceiver, the measurement report including the positioning measurement; and receive a positioning report from the location server via the at least one transceiver, the positioning report including at least the location of the UE.

[0204] Clause 28. The UE according to any one of Clauses 26 to 27, wherein the at least one processor is further configured to: determine the location of the UE.

[0205] Clause 29. The UE pursuant to any one of Clauses 26 to 28, wherein the UE is selected as the anchor UE based at least in part on the battery state, UE type, capability, bandwidth portion (BWP), or any combination thereof of the one or more second UEs.

[0206] Clause 30. The UE according to any one of Clauses 26 to 29, wherein the at least one processor is further configured to: transmit a request for at least a new DRX cycle length to a base station serving the UE via the at least one transceiver, wherein the new DRX cycle length aligns the DRX active timing with the plurality of measurement timings.

[0207] Clause 31. The UE according to any one of Clauses 26 to 30, wherein the at least one processor is further configured to: receive a first DRX configuration from a base station serving the UE via the at least one transceiver, wherein the first DRX configuration is shared for the second DRX configuration of the one or more second UEs.

[0208] Clause 32. The UE as described in Clause 31, wherein the first DRX configuration is shared for the second DRX configuration of the one or more second UEs, including that the DRX active timing of the first DRX configuration and the DRX active timing of the second DRX configuration at least partially overlap.

[0209] Clause 33. The UE pursuant to any one of Clauses 31 to 32, wherein the first DRX configuration includes a Uu DRX configuration and a sidelink DRX configuration.

[0210] Clause 34. The UE according to any one of Clauses 26 to 33, wherein the at least one processor is further configured to: transmit a DRX configuration update message to a location server via the at least one transceiver, the DRX configuration update message indicating the DRX configuration of the UE, the DRX configuration indicating the DRX active timing of the UE.

[0211] Clause 35. The UE according to Clause 34, wherein the at least one processor is further configured to: receive a request for DRX configuration from the location server via the at least one transceiver.

[0212] Clause 36. A location server comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, a plurality of discontinuous reception (DRX) configurations of a plurality of user equipments (UEs) participating in a joint location session with each other, each of the plurality of DRX configurations indicating at least a DRX active moment for the corresponding UE; select one of the plurality of UEs as an anchor UE for the joint location session, the selection being at least in part based on the anchor UE's DRX active moment being closer to a plurality of measurement moments for the joint location session than the DRX active moments of the remaining UEs among the plurality of UEs; and transmit an anchor selection update message to each of the plurality of UEs via the at least one transceiver, the anchor selection update message indicating that the anchor UE has been selected as the anchor UE for the joint location session.

[0213] Clause 37. The location server as described in Clause 36, wherein: the plurality of DRX configurations are received from the plurality of UEs, or from the Access and Mobility Management Function (AMF) serving the plurality of UEs.

[0214] Clause 38. A location server according to any one of Clauses 36 to 37, wherein the at least one processor is further configured to: receive a measurement report from the anchor UE via the at least one transceiver, the measurement report including a location measurement performed by the anchor UE for the joint location session; determine the location of the anchor UE based on the location measurement; and transmit a location report to the anchor UE via the at least one transceiver, the location report including at least the location of the anchor UE.

[0215] Clause 39. A location server pursuant to any one of Clauses 36 to 38, wherein the anchor UE is further selected as the anchor UE based at least in part on the anchor UE's battery state, UE type, capability, bandwidth portion (BWP), or any combination thereof compared with the battery state, UE type, capability, bandwidth portion (BWP), or any combination thereof of the remaining UEs among the plurality of UEs.

[0216] Clause 40. A location server according to any one of Clauses 36 to 39, wherein the at least one processor is further configured to: transmit a request for at least a new DRX cycle length for the anchor UE via the at least one transceiver, wherein the new DRX cycle length aligns the DRX active timing of the anchor UE with the plurality of measurement timings.

[0217] Clause 41. The location server as described in Clause 40, wherein the request is sent to: the serving base station of the anchor UE, or the AMF serving the anchor UE.

[0218] Clause 42. A location server according to any one of Clauses 36 to 41, wherein the at least one processor is further configured to: transmit via the at least one transceiver to an AMF serving the plurality of UEs a recommendation to group the plurality of UEs into DRX groups and configure a shared DRX configuration for all UEs in the plurality of UEs; and transmit via the at least one transceiver to the AMF recommended DRX parameters for the shared DRX configuration, wherein the recommended DRX parameters cause the DRX activity timing of the plurality of UEs to at least partially overlap with the plurality of measurement timings.

[0219] Clause 43. The location server as described in Clause 42, wherein the shared DRX configuration includes a Uu DRX configuration and a sidelink DRX configuration.

[0220] Clause 44. A location server according to any one of Clauses 36 to 43, wherein the at least one processor is further configured to: receive a plurality of DRX configuration update messages from the plurality of UEs via the at least one transceiver, the plurality of DRX configuration update messages indicating a plurality of DRX configurations of the plurality of UEs.

[0221] Clause 45. The location server pursuant to Clause 44, wherein the at least one processor is further configured to: transmit multiple requests for the multiple DRX configurations to the multiple UEs via the at least one transceiver.

[0222] Clause 46. A user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, from a location server an anchor selection update message indicating that a peer UE has been selected from a plurality of UEs including the peer UE as an anchor UE for a joint location session, wherein the peer UE is selected as the anchor UE based at least in part on the fact that the DRX activity timing of the peer UE is closer to a plurality of measurement timings for the joint location session than the DRX activity timings of the remaining UEs among the plurality of UEs; and receive, via the at least one transceiver, from the peer UE a location measurement performed by the peer UE for the joint location session, a location of the peer UE determined based on the location measurement, or both.

[0223] Clause 47. The UE according to Clause 46, wherein the at least one processor is further configured to: adopt the location of the peer UE as the location of the UE.

[0224] Clause 48. The UE according to any one of Clauses 46 to 47, wherein the at least one processor is further configured to determine the location of the UE based on the positioning measurement.

[0225] Clause 49. The UE according to any one of Clauses 46 to 48, wherein the at least one processor is further configured to: transmit a DRX configuration update message to a location server via the at least one transceiver, the DRX configuration update message indicating the DRX configuration of the UE, the DRX configuration indicating the DRX active timing of the UE.

[0226] Clause 50. The UE according to Clause 49, wherein the at least one processor is further configured to: receive a request for DRX configuration from the location server via the at least one transceiver.

[0227] Clause 51. A user equipment (UE) comprising: a module for receiving an anchor selection update message from a location server, the anchor selection update message indicating that the UE has been selected as an anchor UE for a joint positioning session with one or more second UEs, wherein the UE is selected as the anchor UE based at least in part on a DRX active timing of the UE being closer to a plurality of measurement timings for the joint positioning session than a DRX active timing of the one or more second UEs; a module for performing positioning measurements for the joint positioning session during one or more of the plurality of measurement timings overlapping with the DRX active timing of the UE, in response to receiving the anchor selection update message; and a module for transmitting the positioning measurements, a location of the UE determined based on the positioning measurements, or both, to the one or more second UEs.

[0228] Clause 52. The UE according to Clause 51 further includes: a module for transmitting a measurement report to the location server, the measurement report including the positioning measurement; and a module for receiving a positioning report from the location server, the positioning report including at least the location of the UE.

[0229] Clause 53. The UE according to any one of Clauses 51 to 52 further includes: a module for determining the location of the UE.

[0230] Clause 54. The UE pursuant to any one of Clauses 51 to 53, wherein the UE is selected as the anchor UE based at least in part on the battery state, UE type, capability, bandwidth portion (BWP), or any combination thereof of the one or more second UEs.

[0231] Clause 55. The UE according to any one of Clauses 51 to 54 further includes: a module for transmitting a request for at least a new DRX cycle length to a base station serving the UE, wherein the new DRX cycle length aligns the DRX active timing with the plurality of measurement timings.

[0232] Clause 56. The UE according to any one of Clauses 51 to 55 further includes: a module for receiving a first DRX configuration from a base station serving the UE, wherein the first DRX configuration is shared for the second DRX configuration of the one or more second UEs.

[0233] Clause 57. The UE as described in Clause 56, wherein the first DRX configuration is shared for the second DRX configuration of the one or more second UEs, including that the DRX active timing of the first DRX configuration and the DRX active timing of the second DRX configuration at least partially overlap.

[0234] Clause 58. The UE pursuant to any one of Clauses 56 to 57, wherein the first DRX configuration includes a Uu DRX configuration and a sidelink DRX configuration.

[0235] Clause 59. The UE according to any one of Clauses 51 to 58 further includes: a module for transmitting a DRX configuration update message to a location server, the DRX configuration update message indicating the DRX configuration of the UE, the DRX configuration indicating the DRX active timing of the UE.

[0236] Clause 60. The UE as described in Clause 59 further includes: a module for receiving a request for the DRX configuration from the location server.

[0237] Clause 61. A location server comprising: a module for receiving a plurality of discontinuous reception (DRX) configurations of a plurality of user equipments (UEs) participating in a joint location session, each of the plurality of DRX configurations indicating at least a DRX active moment for the corresponding UE; means for selecting one of the plurality of UEs as an anchor UE for the joint location session, the selection being at least in part based on the anchor UE's DRX active moment being closer to a plurality of measurement moments for the joint location session than the DRX active moments of the remaining UEs in the plurality of UEs; and a module for transmitting an anchor selection update message to each of the plurality of UEs, the anchor selection update message indicating that the anchor UE has been selected as the anchor UE for the joint location session.

[0238] Clause 62. The location server as described in Clause 61, wherein: the plurality of DRX configurations are received from the plurality of UEs, or from the Access and Mobility Management Function (AMF) serving the plurality of UEs.

[0239] Clause 63. The location server according to any one of Clauses 61 to 62 further comprises: a module for receiving a measurement report from the anchor UE, the measurement report including a location measurement performed by the anchor UE for the joint location session; a module for determining the location of the anchor UE based on the location measurement; and a module for transmitting a location report to the anchor UE, the location report including at least the location of the anchor UE.

[0240] Clause 64. A location server pursuant to any one of Clauses 61 to 63, wherein the anchor UE is further selected as the anchor UE based at least in part on the anchor UE's battery state, UE type, capability, bandwidth portion (BWP), or any combination thereof compared with the battery state, UE type, capability, bandwidth portion (BWP), or any combination thereof of the remaining UEs among the plurality of UEs.

[0241] Clause 65. The location server according to any one of Clauses 61 to 64 further includes: a module for transmitting a request for at least a new DRX cycle length for the anchor UE, wherein the new DRX cycle length aligns the DRX active timing of the anchor UE with the plurality of measurement timings.

[0242] Clause 66. The location server as described in Clause 65, wherein the request is sent to: the serving base station of the anchor UE, or the AMF serving the anchor UE.

[0243] Clause 67. The location server according to any one of Clauses 61 to 66 further comprises: a module for transmitting to an AMF serving the plurality of UEs a recommendation to group the plurality of UEs into DRX groups and configure a shared DRX configuration for all UEs in the plurality of UEs; and a module for transmitting to the AMF recommended DRX parameters for the shared DRX configuration, wherein the recommended DRX parameters cause the DRX activity timing of the plurality of UEs to at least partially overlap with the plurality of measurement timings.

[0244] Clause 68. The location server as described in Clause 67, wherein the shared DRX configuration includes a Uu DRX configuration and a sidelink DRX configuration.

[0245] Clause 69. The location server according to any one of Clauses 61 to 68 further includes: a module for receiving a plurality of DRX configuration update messages from the plurality of UEs, the plurality of DRX configuration update messages indicating a plurality of DRX configurations of the plurality of UEs.

[0246] Clause 70. The location server as described in Clause 69 further includes: a module for transmitting multiple requests for the multiple DRX configurations to the multiple UEs.

[0247] Clause 71. A user equipment (UE) comprising: a module for receiving an anchor selection update message from a location server, the anchor selection update message indicating that a peer UE has been selected from a plurality of UEs including the peer UE as an anchor UE for a joint location session, wherein the peer UE is selected as the anchor UE based at least in part on a DRX active timing of the peer UE being closer to a plurality of measurement timings for the joint location session than a DRX active timing of the remaining UEs among the plurality of UEs; and a module for receiving from the peer UE a location measurement performed by the peer UE for the joint location session, a location of the peer UE determined based on the location measurement, or both.

[0248] Clause 72. The UE according to Clause 71 further includes: a module for using the location of the peer UE as the location of the UE.

[0249] Clause 73. The UE according to any one of Clauses 71 to 72 further includes: a module for determining the location of the UE based on the positioning measurement.

[0250] Clause 74. The UE according to any one of Clauses 71 to 73 further includes: a module for transmitting a DRX configuration update message to a location server, the DRX configuration update message indicating the DRX configuration of the UE, the DRX configuration indicating the DRX active timing of the UE.

[0251] Clause 75. The UE according to Clause 74 further includes: a module for receiving a request for the DRX configuration from the location server.

[0252] Clause 76. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive an anchor selection update message from a location server, the anchor selection update message indicating that the UE has been selected as an anchor UE for a joint positioning session with one or more second UEs, wherein the UE is selected as the anchor UE based at least in part on the fact that a DRX active timing of the UE is closer to a plurality of measurement timings for the joint positioning session than a DRX active timing of the one or more second UEs; in response to receiving the anchor selection update message, perform positioning measurements for the joint positioning session during one or more of the plurality of measurement timings overlapping with the DRX active timing of the UE; and transmit the positioning measurements, a location of the UE determined based on the positioning measurements, or both, to the one or more second UEs.

[0253] Clause 77. The non-transitory computer-readable medium according to Clause 76 further includes computer-executable instructions that, when executed by the UE, cause the UE to: transmit a measurement report to the location server, the measurement report including the positioning measurement; and receive a positioning report from the location server, the positioning report including at least the location of the UE.

[0254] Clause 78. The non-transitory computer-readable medium according to any one of Clauses 76 to 77 further includes computer-executable instructions that, when executed by the UE, cause the UE to: determine the location of the UE.

[0255] Clause 79. A non-transitory computer-readable medium pursuant to any one of Clauses 76 to 78, wherein the UE is selected as the anchor UE based at least in part on the battery state, UE type, capability, bandwidth portion (BWP), or any combination thereof of the one or more second UEs.

[0256] Clause 80. The non-transitory computer-readable medium according to any one of Clauses 76 to 79 further includes computer-executable instructions that, when executed by the UE, cause the UE to: transmit a request to a base station serving the UE for at least a new DRX cycle length, wherein the new DRX cycle length aligns the DRX activation timing with the plurality of measurement timings.

[0257] Clause 81. The non-transitory computer-readable medium according to any one of Clauses 76 to 80 further includes computer-executable instructions that, when executed by the UE, cause the UE to: receive a first DRX configuration from a base station serving the UE, wherein the first DRX configuration is shared for second DRX configurations of the one or more second UEs.

[0258] Clause 82. The non-transitory computer-readable medium pursuant to Clause 81, wherein the first DRX configuration is shared for the second DRX configuration of the one or more second UEs, including that the DRX active timing of the first DRX configuration and the DRX active timing of the second DRX configuration at least partially overlap.

[0259] Clause 83. A nontransitory computer-readable medium according to any one of Clauses 81 to 82, wherein the first DRX configuration includes a Uu DRX configuration and a sidelink DRX configuration.

[0260] Clause 84. The non-transitory computer-readable medium according to any one of Clauses 76 to 83 further includes computer-executable instructions that, when executed by the UE, cause the UE to: transmit a DRX configuration update message to a location server, the DRX configuration update message indicating the DRX configuration of the UE, the DRX configuration indicating the DRX active timing of the UE.

[0261] Clause 85. The non-transitory computer-readable medium according to Clause 84 further includes computer-executable instructions that, when executed by the UE, cause the UE to: receive a request for the DRX configuration from the location server.

[0262] Clause 86. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a location server, cause the location server to: receive a plurality of discontinuous reception (DRX) configurations of a plurality of user equipments (UEs) participating in a joint positioning session with each other, each of the plurality of DRX configurations indicating at least a DRX active time for the corresponding UE; select one of the plurality of UEs as the anchor UE based at least in part on the fact that the DRX active time of the anchor UE for the joint positioning session is closer to a plurality of measurement times for the joint positioning session than the DRX active times of the remaining UEs among the plurality of UEs; and transmit an anchor selection update message to each of the plurality of UEs, the anchor selection update message indicating that the anchor UE has been selected as the anchor UE for the joint positioning session.

[0263] Clause 87. The non-transitory computer-readable medium as described in Clause 86, wherein: the plurality of DRX configurations are received from the plurality of UEs, or from an Access and Mobility Management Function (AMF) serving the plurality of UEs.

[0264] Clause 88. The non-transitory computer-readable medium according to any one of Clauses 86 to 87 further includes computer-executable instructions, which, when executed by the location server, cause the location server to: receive a measurement report from the anchor UE, the measurement report including positioning measurements performed by the anchor UE for the joint positioning session; determine the location of the anchor UE based on the positioning measurements; and transmit a positioning report to the anchor UE, the positioning report including at least the location of the anchor UE.

[0265] Clause 89. A non-transitory computer-readable medium pursuant to any one of Clauses 86 to 88, wherein the anchor UE is further selected as the anchor UE based at least in part on the anchor UE's battery state, UE type, capability, bandwidth portion (BWP), or any combination thereof compared with the battery state, UE type, capability, bandwidth portion (BWP), or any combination thereof of the remaining UEs among the plurality of UEs.

[0266] Clause 90. The non-transitory computer-readable medium according to any one of Clauses 86 to 89 further includes computer-executable instructions that, when executed by the location server, cause the location server to: issue a request for at least a new DRX cycle length for the anchor UE, wherein the new DRX cycle length aligns the DRX active timing of the anchor UE with the plurality of measurement timings.

[0267] Clause 91. A non-transitory computer-readable medium as described in Clause 90, wherein the request is sent to: the serving base station of the anchor UE, or an AMF serving the anchor UE.

[0268] Clause 92. The non-transitory computer-readable medium according to any one of Clauses 86 to 91 further includes computer-executable instructions, which, when executed by the location server, cause the location server to: transmit to an AMF serving the plurality of UEs a recommendation to group the plurality of UEs into DRX groups and configure a shared DRX configuration for all UEs in the plurality of UEs; and transmit to the AMF recommended DRX parameters for the shared DRX configuration, wherein the recommended DRX parameters cause the DRX activity timing of the plurality of UEs to at least partially overlap with the plurality of measurement timings.

[0269] Clause 93. The non-transitory computer-readable medium as described in Clause 92, wherein the shared DRX configuration includes a UuDRX configuration and a sidelink DRX configuration.

[0270] Clause 94. The non-transitory computer-readable medium according to any one of Clauses 86 to 93 further includes computer-executable instructions that, when executed by the location server, cause the location server to: receive a plurality of DRX configuration update messages from the plurality of UEs, the plurality of DRX configuration update messages indicating a plurality of DRX configurations of the plurality of UEs.

[0271] Clause 95. The non-transitory computer-readable medium according to Clause 94 further includes computer-executable instructions that, when executed by the location server, cause the location server to: transmit multiple requests for the multiple DRX configurations to the multiple UEs.

[0272] Clause 96. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: receive an anchor selection update message from a location server, the anchor selection update message indicating that a peer UE has been selected from a plurality of UEs including the UE and the peer UE as an anchor UE for a joint positioning session, wherein the peer UE is selected as the anchor UE based at least in part on the fact that the DRX activity timing of the peer UE is closer to a plurality of measurement timings for the joint positioning session than the DRX activity timings of the remaining UEs among the plurality of UEs; and receive from the peer UE a positioning measurement performed by the peer UE for the joint positioning session, a location of the peer UE determined based on the positioning measurement, or both.

[0273] Clause 97. The non-transitory computer-readable medium according to Clause 96 further includes computer-executable instructions that, when executed by the UE, cause the UE to: adopt the location of the peer UE as the location of the UE.

[0274] Clause 98. The non-transitory computer-readable medium according to any one of Clauses 96 to 97 further includes computer-executable instructions that, when executed by the UE, cause the UE to: determine the location of the UE based on the positioning measurement.

[0275] Clause 99. The non-transitory computer-readable medium according to any one of Clauses 96 to 98 further includes computer-executable instructions that, when executed by the UE, cause the UE to: transmit a DRX configuration update message to a location server, the DRX configuration update message indicating the DRX configuration of the UE, the DRX configuration indicating the DRX active timing of the UE.

[0276] Clause 100. The non-transitory computer-readable medium according to Clause 99 further includes computer-executable instructions that, when executed by the UE, cause the UE to: receive a request for the DRX configuration from the location server.

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

[0278] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described in general terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be construed as departing from the scope of this disclosure.

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

[0280] The methods, sequences, and / or algorithms described in conjunction with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or a combination of both. The software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. Example storage media are coupled to a processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integral with the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., a UE). Alternatively, the processor and storage medium may reside as discrete components in the user terminal.

[0281] In one or more examples, the functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored as one or more instructions or code on or transmitted over a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. A storage medium may be any available medium accessible to a computer. By way of example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection is appropriately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of a medium. The disks and optical discs used in this article include: compact optical discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of these should also be included within the scope of computer-readable media.

[0282] While the foregoing disclosure illustrates exemplary aspects of this disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of this disclosure as defined by the appended claims. Furthermore, the functions, steps, and / or actions of the method claims according to the aspects of this disclosure described herein need not be performed in any particular order. Moreover, although elements of this disclosure may be described or claimed in the singular, pluralism is also contemplated unless expressly stated as singular.

Claims

1. A radio positioning method performed by a user equipment (UE) operating in discontinuous reception (DRX) mode, comprising: The anchor selection update message is received from the location server, indicating that the UE has been selected as the anchor UE for a joint location session with one or more second UEs, wherein the UE is selected as the anchor UE based at least in part on the fact that the DRX active timing of the UE is closer to a plurality of measurement timings for the joint location session than the DRX active timing of the one or more second UEs. In response to receiving the anchor selection update message, during one or more of the plurality of measurement times that overlap with the DRX active time of the UE, a location measurement is performed for the joint positioning session; as well as Transmit the positioning measurement, the location of the UE determined based on the positioning measurement, or both, to the one or more second UEs.

2. The method according to claim 1, further comprising: A measurement report is transmitted to the location server, the measurement report including the positioning measurement; as well as The location report is received from the location server, and the location report includes at least the location of the UE.

3. The method according to claim 1, further comprising: Determine the location of the UE.

4. The method of claim 1, wherein the UE is selected as the anchor UE based at least in part on the battery state, UE type, capability, bandwidth portion (BWP) or any combination thereof of the one or more second UEs.

5. The method according to claim 1, further comprising: A request for at least a new DRX cycle length is sent to the base station serving the UE, wherein the new DRX cycle length aligns the DRX active timing with the plurality of measurement timings.

6. The method according to claim 1, further comprising: A first DRX configuration is received from a base station serving the UE, wherein the first DRX configuration is shared for the second DRX configuration of the one or more second UEs.

7. The method of claim 6, wherein the first DRX configuration is shared for the second DRX configuration of the one or more second UEs, including that the DRX active timing of the first DRX configuration and the DRX active timing of the second DRX configuration at least partially overlap.

8. The method of claim 6, wherein the first DRX configuration includes a Uu DRX configuration and a sidelink DRX configuration.

9. The method according to claim 1, further comprising: A DRX configuration update message is sent to the location server. The DRX configuration update message indicates the DRX configuration of the UE, and the DRX configuration indicates the DRX active time of the UE.

10. The method of claim 9, further comprising: Receive a request for the DRX configuration from the location server.

11. A location method performed by a location server, comprising: Receive multiple discontinuous reception (DRX) configurations of multiple user equipment (UEs) participating in a joint positioning session with each other, each of the multiple DRX configurations indicating at least a DRX active time of the corresponding UE; One of the plurality of UEs is selected as the anchor UE for the joint location session, the selection being at least in part based on the fact that the DRX active timing for the anchor UE is closer to a plurality of measurement timings for the joint location session than the DRX active timings for the other UEs in the plurality of UEs. as well as An anchor selection update message is transmitted to each of the plurality of UEs, the anchor selection update message indicating that the anchor UE has been selected as the anchor UE for the joint location session.

12. The method according to claim 11, wherein: Receive the multiple DRX configurations from the multiple UEs, or The multiple DRX configurations are received from the Access and Mobility Management Function (AMF) serving the multiple UEs.

13. The method of claim 11, further comprising: Receive a measurement report from the anchor UE, the measurement report including positioning measurements performed by the anchor UE for the joint positioning session; The location of the anchor UE is determined based on the positioning measurement; and A location report is transmitted to the anchor UE, the location report including at least the location of the anchor UE.

14. The method of claim 11, wherein the anchor UE is further selected as the anchor UE based at least in part on the anchor UE's battery state, UE type, capability, bandwidth portion (BWP), or any combination thereof compared with the battery state, UE type, capability, bandwidth portion (BWP), or any combination thereof of the remaining UEs among the plurality of UEs.

15. The method of claim 11, further comprising: A request is sent to the anchor UE for at least a new DRX cycle length, wherein the new DRX cycle length aligns the DRX active timing of the anchor UE with the plurality of measurement timings.

16. The method of claim 15, wherein the request is sent to: The serving base station of the anchor UE, or The AMF that serves the anchor UE.

17. The method of claim 11, further comprising: Transmit a recommendation to the AMF serving the plurality of UEs to group the plurality of UEs into DRX groups and to configure all UEs in the plurality of UEs to share the DRX configuration; as well as The AMF transmits recommended DRX parameters for the shared DRX configuration, wherein the recommended DRX parameters cause the DRX activity timing of the plurality of UEs to at least partially overlap with the plurality of measurement timings.

18. The method of claim 17, wherein the shared DRX configuration includes a Uu DRX configuration and a sidelink DRX configuration.

19. The method of claim 11, further comprising: Multiple DRX configuration update messages are received from the multiple UEs, and the multiple DRX configuration update messages indicate multiple DRX configurations of the multiple UEs.

20. The method of claim 19, further comprising: Multiple requests for the multiple DRX configurations are sent to the multiple UEs.

21. A radio positioning method performed by a user equipment (UE) operating in discontinuous reception (DRX) mode, comprising: The anchor selection update message is received from the location server, indicating that the peer UE has been selected as the anchor UE for a joint location session from a plurality of UEs including the UE and the peer UE, wherein the peer UE is selected as the anchor UE at least in part based on the fact that the DRX active timing of the peer UE is closer to a plurality of measurement timings for the joint location session than the DRX active timing of the remaining UEs among the plurality of UEs. as well as Receive from the peer UE a location measurement performed by the peer UE for the joint location session, the location of the peer UE determined based on the location measurement, or both.

22. The method of claim 21, further comprising: The location of the peer UE is used as the location of the UE.

23. The method of claim 21, further comprising: The location of the UE is determined based on the positioning measurement.

24. The method of claim 21, further comprising: A DRX configuration update message is sent to the location server. The DRX configuration update message indicates the DRX configuration of the UE, and the DRX configuration indicates the DRX active time of the UE.

25. The method of claim 24, further comprising: Receive a request for the DRX configuration from the location server.

26. A user equipment (UE), comprising: Memory; At least one transceiver; and At least one processor, communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: The UE receives an anchor selection update message from a location server via the at least one transceiver. The anchor selection update message indicates that the UE has been selected as the anchor UE for a joint location session with one or more second UEs, wherein the UE is selected as the anchor UE based at least in part on the fact that the DRX active timing of the UE is closer to a plurality of measurement timings for the joint location session than the DRX active timing of the one or more second UEs. In response to receiving the anchor selection update message, during one or more of the plurality of measurement times that overlap with the DRX active time of the UE, a location measurement is performed for the joint positioning session; as well as The positioning measurement, the location of the UE determined based on the positioning measurement, or both are transmitted to the one or more second UEs via the at least one transceiver.

27. The UE of claim 26, wherein the UE is selected as the anchor UE based at least in part on the battery state, UE type, capability, bandwidth portion (BWP) or any combination thereof of the one or more second UEs.

28. The UE of claim 26, wherein the at least one processor is further configured to: The at least one transceiver transmits a request for at least a new DRX cycle length to the base station serving the UE, wherein the new DRX cycle length aligns the DRX active timing with the plurality of measurement timings.

29. The UE of claim 26, wherein the at least one processor is further configured to: A first DRX configuration is received from a base station serving the UE via the at least one transceiver, wherein the first DRX configuration is shared for the second DRX configuration of the one or more second UEs.

30. The UE of claim 26, wherein the at least one processor is further configured to: The UE transmits a DRX configuration update message to the location server via the at least one transceiver. The DRX configuration update message indicates the DRX configuration of the UE and the DRX configuration indicates the DRX active time of the UE.

Images