Patent Description:
Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (<NUM>), a second-generation (<NUM>) digital wireless phone service (including interim <NUM> networks), a third-generation (<NUM>) high speed data, Internet-capable wireless service, and a fourth-generation (<NUM>) service (e.g., Long-Term Evolution (LTE), WiMax). There are presently many different types of wireless communication systems in use, including cellular and personal communications service (PCS) systems. Examples of known cellular systems include the cellular Analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), the Global System for Mobile access (GSM) variation of TDMA, etc..

A fifth generation (<NUM>) mobile standard calls for higher data transfer speeds, greater numbers of connections, and better coverage, among other improvements. The <NUM> standard (also referred to as "New Radio" or "NR"), according to the Next Generation Mobile Networks Alliance, is designed to provide data rates of several tens of megabits per second to each of tens of thousands of users, with <NUM> gigabit per second to tens of workers on an office floor. Several hundreds of thousands of simultaneous connections should be supported in order to support large sensor deployments. Consequently, the spectral efficiency of <NUM> mobile communications should be significantly enhanced compared to the current <NUM> / LTE standard. Furthermore, signaling efficiencies should be enhanced and latency should be substantially reduced compared to current standards.

<CIT> discloses a positioning method for determining a position of a terminal device. The method comprises sending one or more positioning signals between base stations and the terminal device during a transmission phase, and using measured arrival times of the positioning signals to triangulate a position of the terminal device, wherein during the transmission phase the terminal device is in an energy saving communication mode. An additional DRX mode, designated as a Positioning DRX or P-DRX is disclosed. The P-DRX is arranged so as to provide a UE wake-up period that coincides or overlaps with each positioning occasion.

The following presents a simplified summary relating to one or more aspects disclosed herein. Thus, the following summary should not be considered an extensive overview relating to all contemplated aspects, nor should the following summary be considered to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the following summary has the sole purpose to present certain concepts relating to one or more aspects relating to the mechanisms disclosed herein in a simplified form to precede the detailed description presented below.

As used herein, the terms "user equipment" (UE) and "base station" are not intended to be specific or otherwise limited to any particular radio access technology (RAT), unless otherwise noted. In general, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, tracking device, wearable (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communications network. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN). As used herein, the term "UE" may be referred to interchangeably as an "access terminal" or "AT," a "client device," a "wireless device," a "subscriber device," a "subscriber terminal," a "subscriber station," a "user terminal" or UT, a "mobile terminal," a "mobile station," or variations thereof. Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and/or the Internet are also possible for the UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on IEEE <NUM>, etc.) and so on.

A base station may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc. In addition, in some systems a base station may provide purely edge node signaling functions while in other systems it may provide additional control and/or network management functions. A communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send signals to UEs is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein the term traffic channel (TCH) can refer to either an UL / reverse or DL / forward traffic channel.

The term "base station" may refer to a single physical transmission-reception point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell of the base station. Where the term "base station" refers to multiple co-located physical TRPs, the physical TRPs may be an array of antennas (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) of the base station. Where the term "base station" refers to multiple non-co-located physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference RF signals the UE is measuring. Because a TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station are to be understood as referring to a particular TRP of the base station.

An "RF signal" comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, the receiver may receive multiple "RF signals" corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a "multipath" RF signal.

According to various aspects, <FIG> illustrates an exemplary wireless communications system <NUM>. The wireless communications system <NUM> (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations <NUM> and various UEs <NUM>. The base stations <NUM> may include macro cell base stations (high power cellular base stations) and/or small cell base stations (low power cellular base stations). In an aspect, the macro cell base station may include eNBs where the wireless communications system <NUM> corresponds to an LTE network, or gNBs where the wireless communications system <NUM> corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc..

The base stations <NUM> may collectively form a RAN and interface with a core network <NUM> (e.g., an evolved packet core (EPC) or next generation core (NGC)) through backhaul links <NUM>, and through the core network <NUM> to one or more location servers <NUM>. In addition to other functions, the base stations <NUM> may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations <NUM> may communicate with each other directly or indirectly (e.g., through the EPC / NGC) over backhaul links <NUM>, which may be wired or wireless.

In an aspect, one or more cells may be supported by a base station <NUM> in each coverage area <NUM>. A "cell" is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), and may be associated with an identifier (e.g., a physical cell identifier (PCI), a virtual cell identifier (VCI)) for distinguishing cells operating via the same or a different carrier frequency. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Because a cell is supported by a specific base station, the term "cell" may refer to either or both the logical communication entity and the base station that supports it, depending on the context. In some cases, the term "cell" may also refer to a geographic coverage area of a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication within some portion of geographic coverage areas <NUM>.

While neighboring macro cell base station <NUM> geographic coverage areas <NUM> may partially overlap (e.g., in a handover region), some of the geographic coverage areas <NUM> may be substantially overlapped by a larger geographic coverage area <NUM>. For example, a small cell base station <NUM>' may have a coverage area <NUM>' that substantially overlaps with the coverage area <NUM> of one or more macro cell base stations <NUM>. A network that includes both small cell and macro cell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).

The communication links <NUM> between the base stations <NUM> and the UEs <NUM> may include UL (also referred to as reverse link) transmissions from a UE <NUM> to a base station <NUM> and/or downlink (DL) (also referred to as forward link) transmissions from a base station <NUM> to a UE <NUM>. The communication links <NUM> may use MIMO antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links <NUM> may be through one or more carrier frequencies. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL).

Receive beams may be spatially related. A spatial relation means that parameters for a transmit beam for a second reference signal can be derived from information about a receive beam for a first reference signal. For example, a UE may use a particular receive beam to receive a reference downlink reference signal (e.g., synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for sending an uplink reference signal (e.g., sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

In <NUM>, the frequency spectrum in which wireless nodes (e.g., base stations <NUM>/<NUM>, UEs <NUM>/<NUM>) operate is divided into multiple frequency ranges, FR1 (from <NUM> to <NUM>), FR2 (from <NUM> to <NUM>), FR3 (above <NUM>), and FR4 (between FR1 and FR2). In a multi-carrier system, such as <NUM>, one of the carrier frequencies is referred to as the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers" or "secondary serving cells" or "SCells. " In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by a UE <NUM>/<NUM> and the cell in which the UE <NUM>/<NUM> either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels, and may be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once the RRC connection is established between the UE <NUM> and the anchor carrier and that may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, those that are UE-specific may not be present in the secondary carrier, since both primary uplink and downlink carriers are typically UE-specific. This means that different UEs <NUM>/<NUM> in a cell may have different downlink primary carriers. The same is true for the uplink primary carriers. The network is able to change the primary carrier of any UE <NUM>/<NUM> at any time. This is done, for example, to balance the load on different carriers. Because a "serving cell" (whether a PCell or an SCell) corresponds to a carrier frequency / component carrier over which some base station is communicating, the term "cell," "serving cell," "component carrier," "carrier frequency," and the like can be used interchangeably.

The wireless communications system <NUM> may further include one or more UEs, such as UE <NUM>, that connects indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. In the example of <FIG>, UE <NUM> has a D2D P2P link <NUM> with one of the UEs <NUM> connected to one of the base stations <NUM> (e.g., through which UE <NUM> may indirectly obtain cellular connectivity) and a D2D P2P link <NUM> with WLAN STA <NUM> connected to the WLAN AP <NUM> (through which UE <NUM> may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links <NUM> and <NUM> may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, and so on.

The wireless communications system <NUM> may further include a UE <NUM> that may communicate with a macro cell base station <NUM> over a communication link <NUM> and/or the mmW base station <NUM> over a mmW communication link <NUM>. For example, the macro cell base station <NUM> may support a PCell and one or more SCells for the UE <NUM> and the mmW base station <NUM> may support one or more SCells for the UE <NUM>. In an aspect, the UE <NUM> may include a PRS-DRX interaction manager <NUM> that may enable the UE <NUM> to perform the UE operations described herein. Note that although only one UE in <FIG> is illustrated as having a PRS-DRX interaction manager <NUM>, any of the UEs in <FIG> may be configured to perform the UE operations described herein.

According to various aspects, <FIG> illustrates an example wireless network structure <NUM>. For example, an NGC <NUM> (also referred to as a "5GC") can be viewed functionally as control plane functions <NUM> (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane functions <NUM>, (e.g., UE gateway function, access to data networks, IP routing, etc.) which operate cooperatively to form the core network. User plane interface (NG-U) <NUM> and control plane interface (NG-C) <NUM> connect the gNB <NUM> to the NGC <NUM> and specifically to the control plane functions <NUM> and user plane functions <NUM>. In an additional configuration, an eNB <NUM> may also be connected to the NGC <NUM> via NG-C <NUM> to the control plane functions <NUM> and NG-U <NUM> to user plane functions <NUM>. Further, eNB <NUM> may directly communicate with gNB <NUM> via a backhaul connection <NUM>. In some configurations, the New RAN <NUM> may only have one or more gNBs <NUM>, while other configurations include one or more of both eNBs <NUM> and gNBs <NUM>. Either gNB <NUM> or eNB <NUM> may communicate with UEs <NUM> (e.g., any of the UEs depicted in <FIG>). Another optional aspect may include location server <NUM> (which may correspond to location server <NUM>), which may be in communication with the NGC <NUM> to provide location assistance for UEs <NUM>. The location server <NUM> can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server. The location server <NUM> can be configured to support one or more location services for UEs <NUM> that can connect to the location server <NUM> via the core network, NGC <NUM>, and/or via the Internet (not illustrated). Further, the location server <NUM> may be integrated into a component of the core network, or alternatively may be external to the core network.

According to various aspects, <FIG> illustrates another example wireless network structure <NUM>. For example, an NGC <NUM> (also referred to as a "5GC") can be viewed functionally as control plane functions, provided by an access and mobility management function (AMF) / user plane function (UPF) <NUM>, and user plane functions, provided by a session management function (SMF) <NUM>, which operate cooperatively to form the core network (i.e., NGC <NUM>). User plane interface <NUM> and control plane interface <NUM> connect the eNB <NUM> to the NGC <NUM> and specifically to SMF <NUM> and AMF/UPF <NUM>, respectively. In an additional configuration, a gNB <NUM> may also be connected to the NGC <NUM> via control plane interface <NUM> to AMF/UPF <NUM> and user plane interface <NUM> to SMF <NUM>. Further, eNB <NUM> may directly communicate with gNB <NUM> via the backhaul connection <NUM>, with or without gNB direct connectivity to the NGC <NUM>. In some configurations, the New RAN <NUM> may only have one or more gNBs <NUM>, while other configurations include one or more of both eNBs <NUM> and gNBs <NUM>. Either gNB <NUM> or eNB <NUM> may communicate with UEs <NUM> (e.g., any of the UEs depicted in <FIG>). The base stations of the New RAN <NUM> communicate with the AMF-side of the AMF/UPF <NUM> over the N2 interface and the UPF-side of the AMF/UPF <NUM> over the N3 interface.

The functions of the AMF include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between the UE <NUM> and the SMF <NUM>, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE <NUM> and the short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF also interacts with the authentication server function (AUSF) (not shown) and the UE <NUM>, and receives the intermediate key that was established as a result of the UE <NUM> authentication process. In the case of authentication based on a UMTS (universal mobile telecommunications system) subscriber identity module (USIM), the AMF retrieves the security material from the AUSF. The functions of the AMF also include security context management (SCM). The SCM receives a key from the SEAF that it uses to derive access-network specific keys. The functionality of the AMF also includes location services management for regulatory services, transport for location services messages between the UE <NUM> and the location management function (LMF) <NUM> (which may correspond to location server <NUM>), as well as between the New RAN <NUM> and the LMF <NUM>, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, and UE <NUM> mobility event notification. In addition, the AMF also supports functionalities for non-Third Generation Partnership Project (3GPP) access networks.

Functions of the UPF include acting as an anchor point for intra-/inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point of interconnect to the data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., UL/DL rate enforcement, reflective QoS marking in the DL), UL traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in the UL and DL, DL packet buffering and DL data notification triggering, and sending and forwarding of one or more "end markers" to the source RAN node.

The functions of the SMF <NUM> include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF to route traffic to the proper destination, control of part of policy enforcement and QoS, and downlink data notification. The interface over which the SMF <NUM> communicates with the AMF-side of the AMF/UPF <NUM> is referred to as the N11 interface.

Another optional aspect may include a LMF <NUM>, which may be in communication with the NGC <NUM> to provide location assistance for UEs <NUM>. The LMF <NUM> can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server. The LMF <NUM> can be configured to support one or more location services for UEs <NUM> that can connect to the LMF <NUM> via the core network, NGC <NUM>, and/or via the Internet (not illustrated).

<FIG>, <FIG>, and <FIG> illustrate several sample components (represented by corresponding blocks) that may be incorporated into a UE <NUM> (which may correspond to any of the UEs described herein), a base station <NUM> (which may correspond to any of the base stations described herein), and a network entity <NUM> (which may correspond to or embody any of the network functions described herein, including the location server <NUM> and the LMF <NUM>) to support the file transmission operations as taught herein. It will be appreciated that these components may be implemented in different types of apparatuses in different implementations (e.g., in an ASIC, in a system-on-chip (SoC), etc.). The illustrated components may also be incorporated into other apparatuses in a communication system. For example, other apparatuses in a system may include components similar to those described to provide similar functionality. Also, a given apparatus may contain one or more of the components. For example, an apparatus may include multiple transceiver components that enable the apparatus to operate on multiple carriers and/or communicate via different technologies.

The UE <NUM> and the base station <NUM> each include wireless wide area network (WWAN) transceiver <NUM> and <NUM>, respectively, configured to communicate via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, and/or the like. The WWAN transceivers <NUM> and <NUM> may be connected to one or more antennas <NUM> and <NUM>, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium of interest (e.g., some set of time/frequency resources in a particular frequency spectrum). The WWAN transceivers <NUM> and <NUM> may be variously configured for transmitting and encoding signals <NUM> and <NUM> (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals <NUM> and <NUM> (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the transceivers <NUM> and <NUM> include one or more transmitters <NUM> and <NUM>, respectively, for transmitting and encoding signals <NUM> and <NUM>, respectively, and one or more receivers <NUM> and <NUM>, respectively, for receiving and decoding signals <NUM> and <NUM>, respectively.

The UE <NUM> and the base station <NUM> also include, at least in some cases, wireless local area network (WLAN) transceivers <NUM> and <NUM>, respectively. The WLAN transceivers <NUM> and <NUM> may be connected to one or more antennas <NUM> and <NUM>, respectively, for communicating with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth®, etc.) over a wireless communication medium of interest. The WLAN transceivers <NUM> and <NUM> may be variously configured for transmitting and encoding signals <NUM> and <NUM> (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals <NUM> and <NUM> (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the transceivers <NUM> and <NUM> include one or more transmitters <NUM> and <NUM>, respectively, for transmitting and encoding signals <NUM> and <NUM>, respectively, and one or more receivers <NUM> and <NUM>, respectively, for receiving and decoding signals <NUM> and <NUM>, respectively.

Transceiver circuitry including a transmitter and a receiver may comprise an integrated device (e.g., embodied as a transmitter circuit and a receiver circuit of a single communication device) in some implementations, may comprise a separate transmitter device and a separate receiver device in some implementations, or may be embodied in other ways in other implementations. In an aspect, a transmitter may include or be coupled to a plurality of antennas (e.g., antennas <NUM>, <NUM>, and <NUM>), such as an antenna array, that permits the respective apparatus to perform transmit "beamforming," as described herein. Similarly, a receiver may include or be coupled to a plurality of antennas (e.g., antennas <NUM>, <NUM>, and <NUM>), such as an antenna array, that permits the respective apparatus to perform receive beamforming, as described herein. In an aspect, the transmitter and receiver may share the same plurality of antennas (e.g., antennas <NUM>, <NUM>, and <NUM>), such that the respective apparatus can only receive or transmit at a given time, not both at the same time. A wireless communication device (e.g., one or both of the transceivers <NUM> and <NUM> and/or <NUM> and <NUM>) of the apparatuses <NUM> and/or <NUM> may also comprise a network listen module (NLM) or the like for performing various measurements.

The apparatuses <NUM> and <NUM> also include, at least in some cases, satellite positioning systems (SPS) receivers <NUM> and <NUM>. The SPS receivers <NUM> and <NUM> may be connected to one or more antennas <NUM> and <NUM>, respectively, for receiving SPS signals <NUM> and <NUM>, respectively, such as global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. The SPS receivers <NUM> and <NUM> may comprise any suitable hardware and/or software for receiving and processing SPS signals <NUM> and <NUM>, respectively. The SPS receivers <NUM> and <NUM> request information and operations as appropriate from the other systems, and performs calculations necessary to determine the apparatus' <NUM> and <NUM> positions using measurements obtained by any suitable SPS algorithm.

The base station <NUM> and the network entity <NUM> each include at least one network interfaces <NUM> and <NUM> for communicating with other network entities. For example, the network interfaces <NUM> and <NUM> (e.g., one or more network access ports) may be configured to communicate with one or more network entities via a wire-based or wireless backhaul connection. In some aspects, the network interfaces <NUM> and <NUM> may be implemented as transceivers configured to support wire-based or wireless signal communication. This communication may involve, for example, sending and receiving: messages, parameters, or other types of information.

The apparatuses <NUM>, <NUM>, and <NUM> also include other components that may be used in conjunction with the operations as disclosed herein. The UE <NUM> includes processor circuitry implementing a processing system <NUM> for providing functionality relating to, for example, PRS and DRX interaction as disclosed herein and for providing other processing functionality. The base station <NUM> includes a processing system <NUM> for providing functionality relating to, for example, PRS and DRX interaction as disclosed herein and for providing other processing functionality. The network entity <NUM> includes a processing system <NUM> for providing functionality relating to, for example, PRS and DRX interaction as disclosed herein and for providing other processing functionality. In an aspect, the processing systems <NUM>, <NUM>, and <NUM> may include, for example, one or more general purpose processors, multi-core processors, ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGA), or other programmable logic devices or processing circuitry.

The apparatuses <NUM>, <NUM>, and <NUM> include memory circuitry implementing memory components <NUM>, <NUM>, and <NUM> (e.g., each including a memory device), respectively, for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, and so on). In some cases, the apparatuses <NUM>, <NUM>, and <NUM> may include PRS-DRX interaction managers <NUM>, <NUM>, and <NUM>, respectively. The PRS-DRX interaction managers <NUM>, <NUM>, and <NUM> may be hardware circuits that are part of or coupled to the processing systems <NUM>, <NUM>, and <NUM>, respectively, that, when executed, cause the apparatuses <NUM>, <NUM>, and <NUM> to perform the functionality described herein. In other aspects, the PRS-DRX interaction managers <NUM>, <NUM>, and <NUM> may be external to the processing systems <NUM>, <NUM>, and <NUM> (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the PRS-DRX interaction managers <NUM>, <NUM>, and <NUM> may be memory modules (as shown in <FIG>) stored in the memory components <NUM>, <NUM>, and <NUM>, respectively, that, when executed by the processing systems <NUM>, <NUM>, and <NUM> (e.g., or a modem processing system, another processing system, etc.), cause the apparatuses <NUM>, <NUM>, and <NUM> to perform the functionality described herein.

The UE <NUM> may include one or more sensors <NUM> coupled to the processing system <NUM> to provide movement and/or orientation information that is independent of motion data derived from signals received by the WWAN transceiver <NUM>, the WLAN transceiver <NUM>, and/or the SPS receiver <NUM>. By way of example, the sensor(s) <NUM> may include an accelerometer (e.g., a micro-electrical mechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric pressure altimeter), and/or any other type of movement detection sensor. Moreover, the sensor(s) <NUM> may include a plurality of different types of devices and combine their outputs in order to provide motion information. For example, the sensor(s) <NUM> may use a combination of a multi-axis accelerometer and orientation sensors to provide the ability to compute positions in 2D and/or 3D coordinate systems.

In addition, the UE <NUM> includes a user interface <NUM> for providing indications (e.g., audible and/or visual indications) to a user and/or for receiving user input (e.g., upon user actuation of a sensing device such a keypad, a touch screen, a microphone, and so on). Although not shown, the apparatuses <NUM> and <NUM> may also include user interfaces.

Referring to the processing system <NUM> in more detail, in the downlink, IP packets from the network entity <NUM> may be provided to the processing system <NUM>. The processing system <NUM> may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The processing system <NUM> may provide RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

The transmitter <NUM> and the receiver <NUM> may implement Layer-<NUM> functionality associated with various signal processing functions. Layer-<NUM>, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The transmitter <NUM> handles mapping to signal constellations 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)). Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. Each spatial stream may then be provided to one or more different antennas <NUM>. The transmitter <NUM> may modulate an RF carrier with a respective spatial stream for transmission.

At the UE <NUM>, the receiver <NUM> receives a signal through its respective antenna(s) <NUM>. The receiver <NUM> recovers information modulated onto an RF carrier and provides the information to the processing system <NUM>. The transmitter <NUM> and the receiver <NUM> implement Layer-<NUM> functionality associated with various signal processing functions. The receiver <NUM> may perform spatial processing on the information to recover any spatial streams destined for the UE <NUM>. If multiple spatial streams are destined for the UE <NUM>, they may be combined by the receiver <NUM> into a single OFDM symbol stream. The receiver <NUM> then converts the OFDM symbol stream from the time-domain to the frequency domain using a fast Fourier transform (FFT). These soft decisions may be based on channel estimates computed by a channel estimator. The data and control signals are then provided to the processing system <NUM>, which implements Layer-<NUM> and Layer-<NUM> functionality.

In the UL, the processing system <NUM> provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network. The processing system <NUM> is also responsible for error detection.

Similar to the functionality described in connection with the DL transmission by the base station <NUM>, the processing system <NUM> provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station <NUM> may be used by the transmitter <NUM> to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the transmitter <NUM> may be provided to different antenna(s) <NUM>. The transmitter <NUM> may modulate an RF carrier with a respective spatial stream for transmission.

The receiver <NUM> receives a signal through its respective antenna(s) <NUM>. The receiver <NUM> recovers information modulated onto an RF carrier and provides the information to the processing system <NUM>.

In the UL, the processing system <NUM> provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE <NUM>. IP packets from the processing system <NUM> may be provided to the core network. The processing system <NUM> is also responsible for error detection.

For convenience, the apparatuses <NUM>, <NUM>, and/or <NUM> are shown in <FIG> as including various components that may be configured according to the various examples described herein. It will be appreciated, however, that the illustrated blocks may have different functionality in different designs.

The various components of the apparatuses <NUM>, <NUM>, and <NUM> may communicate with each other over data buses <NUM>, <NUM>, and <NUM>, respectively. The components of <FIG> may be implemented in various ways. In some implementations, the components of <FIG> may be implemented in one or more circuits such as, for example, one or more processors and/or one or more ASICs (which may include one or more processors). Here, each circuit may use and/or incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality. For example, some or all of the functionality represented by blocks <NUM> to <NUM> may be implemented by processor and memory component(s) of the UE <NUM> (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Similarly, some or all of the functionality represented by blocks <NUM> to <NUM> may be implemented by processor and memory component(s) of the base station <NUM> (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Also, some or all of the functionality represented by blocks <NUM> to <NUM> may be implemented by processor and memory component(s) of the network entity <NUM> (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). For simplicity, various operations, acts, and/or functions are described herein as being performed "by a UE," "by a base station," "by a positioning entity," etc. However, as will be appreciated, such operations, acts, and/or functions may actually be performed by specific components or combinations of components of the UE, base station, positioning entity, etc., such as the processing systems <NUM>, <NUM>, <NUM>, the transceivers <NUM>, <NUM>, <NUM>, and <NUM>, the memory components <NUM>, <NUM>, and <NUM>, the PRS-DRX interaction managers <NUM>, <NUM>, and <NUM>, etc..

Time intervals of a communications resource in LTE or <NUM> NR may be organized according to radio frames. <FIG> is a diagram <NUM> illustrating an example of a DL frame structure, according to aspects of the disclosure. 4B is a diagram <NUM> illustrating an example of channels within the DL frame structure, according to aspects of the disclosure. Other wireless communications technologies may have a different frame structures and/or different channels.

LTE, and in some cases NR, utilizes OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. Unlike LTE, however, NR has an option to use OFDM on the uplink as well. For example, the spacing of the subcarriers may be <NUM> and the minimum resource allocation (resource block) may be <NUM> subcarriers (or <NUM>). Consequently, the nominal FFT size may be equal to <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> for system bandwidth of <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> megahertz (MHz), respectively. For example, a subband may cover <NUM> (i.e., <NUM> resource blocks), and there may be <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> subbands for system bandwidth of <NUM>, <NUM>, <NUM>, <NUM>, or <NUM>, respectively.

LTE supports a single numerology (subcarrier spacing, symbol length, etc.). In contrast NR may support multiple numerologies, for example, subcarrier spacing of <NUM>, <NUM>, <NUM>, <NUM> and <NUM> or greater may be available. Table <NUM> provided below lists some various parameters for different NR numerologies.

In the examples of <FIG> and <FIG>, a numerology of <NUM> is used. Thus, in the time domain, a frame (e.g., <NUM> milliseconds (ms)) is divided into <NUM> equally sized subframes of <NUM> each, and each subframe includes one time slot. In <FIG> and <FIG>, time is represented horizontally (e.g., on the X axis) with time increasing from left to right, while frequency is represented vertically (e.g., on the Y axis) with frequency increasing (or decreasing) from bottom to top.

A resource grid may be used to represent time slots, each time slot including one or more time concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the numerology of <FIG> and <FIG>, for a normal cyclic prefix, an RB may contain <NUM> consecutive subcarriers in the frequency domain and <NUM> consecutive symbols (for DL, OFDM symbols; for UL, SC-FDMA symbols) in the time domain, for a total of <NUM> REs. For an extended cyclic prefix, an RB may contain <NUM> consecutive subcarriers in the frequency domain and <NUM> consecutive symbols in the time domain, for a total of <NUM> REs.

As illustrated in <FIG>, some of the REs carry DL reference (pilot) signals (DL-RS) for channel estimation at the UE. The DL-RS may include demodulation reference signals (DMRS) and channel state information reference signals (CSI-RS), exemplary locations of which are labeled "R" in <FIG>.

<FIG> illustrates an example of various channels within a DL subframe of a frame. The physical downlink control channel (PDCCH) carries DL control information (DCI) within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. A primary synchronization signal (PSS) is used by a UE to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a PCI. Based on the PCI, the UE can determine the locations of the aforementioned DL-RS. The physical broadcast channel (PBCH), which carries an MIB, may be logically grouped with the PSS and SSS to form an SSB. The MIB provides a number of RBs in the DL system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as SIBs, and paging messages.

In some cases, the CSI-RS illustrated in <FIG> may be positioning reference signals (PRS). A collection of resource elements that are used for transmission of PRS is referred to as a "PRS resource. " The collection of resource elements can span multiple PRBs in the frequency domain and N (e.g., <NUM> or more) consecutive symbol(s) within a slot in the time domain. In a given OFDM symbol, a PRS resource occupies consecutive PRBs. A PRS resource is described by at least the following parameters: PRS resource identifier (ID), sequence ID, comb size-N, resource element offset in the frequency domain, starting slot and starting symbol, number of symbols per PRS resource (i.e., the duration of the PRS resource), and QCL information (e.g., QCL with other DL reference signals). Currently, one antenna port is supported. The comb size indicates the number of subcarriers in each symbol carrying PRS. For example, a combsize of comb-<NUM> means that every fourth subcarrier of a given symbol carries PRS.

A "PRS resource set" is a set of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID. In addition, the 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 may be associated with a particular TRP (identified by a cell ID) transmitted by an antenna panel of a base station. A PRS resource ID in a PRS resource set is associated with a single beam (and/or beam ID) transmitted from a single TRP (where a TRP may transmit one or more beams). That is, each PRS resource of a PRS resource set may be transmitted on a different beam, and as such, a "PRS resource," or simply "resource," can also be referred to as a "beam. " Note that this does not have any implications on whether the TRPs and the beams on which PRS are transmitted are known to the UE.

A "PRS instance" or "PRS occasion" is one instance of a periodically repeated time window (e.g., a group of one or more consecutive slots) where PRS are expected to be transmitted. A PRS occasion may also be referred to as a "PRS positioning occasion," a "PRS positioning instance, a "positioning occasion," "a positioning instance," or simply an "occasion" or "instance.

A base station may transmit radio frames (e.g., radio frames <NUM>), or other physical layer signaling sequences, supporting PRS according to frame configurations either similar to, or the same as that, shown in <FIG> (where the CSI-RS are PRS), which may be measured and used for a UE (e.g., any of the UEs described herein) position estimation. Other types of wireless nodes (e.g., a DAS, RRH, UE, AP, etc.) in a wireless communications network may also be configured to transmit PRS configured in a manner similar to (or the same as) that depicted in <FIG>.

PRS may be transmitted in special positioning subframes that are grouped into positioning occasions (or PRS occasions). As noted above, a PRS occasion is one instance of a periodically repeated time window (e.g., consecutive slot(s)) where PRS are expected to be transmitted. Each periodically repeated time window can include a group of one or more consecutive PRS occasions. Each PRS occasion can comprise a number NPRS of consecutive positioning subframes. The PRS positioning occasions for a cell supported by a base station may occur periodically at intervals, denoted by a number TPRS of milliseconds or slots. As an example, NPRS may equal <NUM> and TPRS may be greater than or equal to <NUM>. In some aspects, TPRS may be measured in terms of the number of slots between the start of consecutive positioning occasions. Multiple PRS occasions may be associated with the same PRS resource configuration, in which case, each such occasion is referred to as an "occasion of the PRS resource" or the like.

<FIG> illustrates an exemplary PRS configuration <NUM> for a cell supported by a wireless node (such as any of the base stations described herein). Again, PRS transmission for LTE is assumed in <FIG>, although the same or similar aspects of PRS transmission to those shown in and described for <FIG> may apply to NR and/or other wireless technologies. <FIG> shows how PRS positioning occasions are determined by a system frame number (SFN), a cell specific subframe offset (ΔPRS) <NUM>, and the PRS periodicity (TPRS) <NUM>. Typically, the cell specific PRS subframe configuration is defined by a "PRS Configuration Index" IPRS included in observed time difference of arrival (OTDOA) assistance data. The PRS periodicity (TPRS) <NUM> and the cell specific subframe offset (ΔPRS) are defined based on the PRS configuration index IPRS, as illustrated in Table <NUM> below.

A PRS configuration is defined with reference to the system frame number (SFN) of a cell that transmits PRS. PRS instances, for the first subframe of the NPRS downlink subframes comprising a first PRS positioning occasion, may satisfy: <MAT> where nf is the SFN with <NUM> ≤ nf ≤ <NUM>, ns is the slot number within the radio frame defined by nf with <NUM> ≤ ns ≤ <NUM>, TPRS is the PRS periodicity <NUM>, and ΔPRS is the cell-specific subframe offset <NUM>.

As shown in <FIG>, the cell specific subframe offset ΔPRS <NUM> may be defined in terms of the number of subframes transmitted starting from system frame number <NUM> (Slot 'Number <NUM>', marked as slot <NUM>) to the start of the first (subsequent) PRS positioning occasion. In the example in <FIG>, the number of consecutive positioning subframes (NPRS) in each of the consecutive PRS positioning occasions 418a, 418b, and 418c equals <NUM>. That is, each shaded block representing PRS positioning occasions 418a, 418b, and 418c represents four subframes.

In some aspects, when a UE receives a PRS configuration index IPRS in the OTDOA assistance data for a particular cell, the UE may determine the PRS periodicity TPRS <NUM> and PRS subframe offset ΔPRS using Table <NUM>. The UE may then determine the radio frame, subframe and slot when a PRS is scheduled in the cell (e.g., using equation (<NUM>)). The OTDOA assistance data may be determined by, for example, the location server <NUM>, and includes assistance data for a reference cell, and a number of neighbor cells supported by various wireless nodes.

Typically, PRS occasions from all cells in a network that use the same frequency are aligned in time and may have a fixed known time offset (e.g., cell-specific subframe offset <NUM>) relative to other cells in the network that use a different frequency. In SFN-synchronous networks all wireless nodes (e.g., base stations <NUM>) may be aligned on both frame boundary and system frame number. Therefore, in SFN-synchronous networks all cells supported by the various wireless nodes may use the same PRS configuration index for any particular frequency of PRS transmission. On the other hand, in SFN-asynchronous networks, the various wireless nodes may be aligned on a frame boundary, but not system frame number. Thus, in SFN-asynchronous networks the PRS configuration index for each cell may be configured separately by the network so that PRS occasions align in time.

A UE may determine the timing of the PRS occasions of the reference and neighbor cells for OTDOA positioning, if the UE <NUM> can obtain the cell timing (e.g., SFN) of at least one of the cells, e.g., the reference cell or a serving cell. The timing of the other cells may then be derived by the UE <NUM> based, for example, on the assumption that PRS occasions from different cells overlap.

For LTE systems, the sequence of subframes used to transmit PRS (e.g., for OTDOA positioning) may be characterized and defined by a number of parameters, as described previously, comprising: (i) a reserved block of bandwidth (BW), (ii) the configuration index IPRS, (iii) the duration NPRS, (iv) an optional muting pattern; and (v) a muting sequence periodicity TREP that can be implicitly included as part of the muting pattern in (iv) when present. In some cases, with a fairly low PRS duty cycle, NPRS = <NUM>, TPRS = <NUM> subframes (equivalent to <NUM>), and BW = <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or <NUM>. To increase the PRS duty cycle, the NPRS value can be increased to six (i.e., NPRS = <NUM>) and the bandwidth (BW) value can be increased to the system bandwidth (i.e., BW = LTE system bandwidth in the case of LTE). An expanded PRS with a larger NPRS (e.g., greater than six) and/or a shorter TPRS (e.g., less than <NUM>), up to the full duty cycle (i.e., NPRS = TPRS), may also be used in later versions of the LTE positioning protocol (LPP). A directional PRS may be configured as just described and may, for example, use a low PRS duty cycle (e.g., NPRS = <NUM>, TPRS = <NUM> subframes) or a high duty cycle.

A PRS may be transmitted with a constant power. A PRS can also be transmitted with zero power (i.e., muted). Muting, which turns off a regularly scheduled PRS transmission, may be useful when PRS signals between different cells overlap by occurring at the same or almost the same time. In this case, the PRS signals from some cells may be muted while PRS signals from other cells are transmitted (e.g., at a constant power). Muting may aid signal acquisition and time of arrival (TOA) and reference signal time difference (RSTD) measurement, by UEs, of PRS signals that are not muted (by avoiding interference from PRS signals that have been muted). Muting may be viewed as the non-transmission of a PRS for a given positioning occasion for a particular cell. Muting patterns (also referred to as muting sequences) may be signaled (e.g., using LPP) to a UE using bit strings. For example, in a bit string signaled to indicate a muting pattern, if a bit at position j is set to '<NUM>', then the UE may infer that the PRS is muted for a jth positioning occasion.

To further improve hearability of PRS, positioning subframes may be low-interference subframes that are transmitted without user data channels. As a result, in ideally synchronized networks, PRS may be interfered with by other cells' PRS with the same PRS pattern index (i.e., with the same frequency shift), but not from data transmissions. The frequency shift may be defined as a function of a PRS ID for a cell or other transmission point (TP) (denoted as <MAT>) or as a function of a physical cell identifier (PCI) (denoted as <MAT>) if no PRS ID is assigned, which results in an effective frequency re-use factor of six (<NUM>).

To also improve hearability of a PRS (e.g., when PRS bandwidth is limited, such as with only six resource blocks corresponding to <NUM> bandwidth), the frequency band for consecutive PRS positioning occasions (or consecutive PRS subframes) may be changed in a known and predictable manner via frequency hopping. In addition, a cell supported by a base station may support more than one PRS configuration, where each PRS configuration may comprise a distinct frequency offset (vshift), a distinct carrier frequency, a distinct bandwidth, a distinct code sequence, and/or a distinct sequence of PRS positioning occasions with a particular number of subframes (NPRS) per positioning occasion and a particular periodicity (TPRS). In some implementation, one or more of the PRS configurations supported in a cell may be for a directional PRS and may then have additional distinct characteristics, such as a distinct direction of transmission, a distinct range of horizontal angles, and/or a distinct range of vertical angles.

A PRS configuration, as described above, including the PRS transmission/muting schedule, is signaled to the UE to enable the UE to perform PRS positioning measurements. The UE is not expected to blindly perform detection of PRS configurations.

Note that the terms "positioning reference signal" and "PRS" may sometimes refer to specific reference signals that are used for positioning in LTE and NR systems. However, as used herein, unless otherwise indicated, the terms "positioning reference signal" and "PRS" refer to any type of reference signal that can be used for positioning, such as but not limited to, PRS signals in LTE and NR, navigation reference signals (NRS), tracking reference signals (TRS), cell-specific reference signals (CRS), CSI-RS, PSS, SSS, DMRS, sounding reference signals (SRS), etc..

Even when there is no traffic being transmitted from the network to a UE, the UE is expected to monitor every downlink subframe on the PDCCH. This means that the UE has to be "on," or active, all the time, even when there is no traffic, since the UE does not know exactly when the network will transmit data for it. However, being active all the time is a significant power drain for a UE.

To address this issue, a UE may implement discontinuous reception (DRX) and/or connected-mode discontinuous reception (CDRX) techniques. DRX and CDRX are mechanisms in which a UE goes into a "sleep" mode for a certain periods of time and "wakes up" for other periods of time. During the wake, or active, periods, the UE checks to see if there is any data coming from the network, and if there is not, goes back into sleep mode.

To implement DRX and CDRX, the UE and the network need to be synchronized. In a worst case scenario, the network may attempt to send some data to the UE while the UE is in sleep mode, and the UE may wake up when there is no data to be received. To prevent such scenarios, the UE and the network should have a well-defined agreement about when the UE can be in sleep mode and when the UE should be awake/active. This agreement is defined in, for example, 3GPP Technical Specification (TS) <NUM> for UEs in connected mode (CDRX), and 3GPP TS <NUM> for UEs in idle mode (DRX). Note that DRX includes CDRX, and thus, references to DRX refer to both DRX and CDRX, unless otherwise indicated.

The network (e.g., serving cell) can configure the UE with the DRX/CDRX timing using an RRC Connection Reconfiguration message (for CDRX) or an RRC Connection Setup message (for DRX). The network can signal the following DRX configuration parameters to the UE:.

<FIG> illustrate exemplary DRX configurations, according to aspects of the disclosure. <FIG> illustrates an exemplary DRX configuration 500A 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. <FIG> illustrates an exemplary DRX configuration 500B in which a long DRX cycle is configured and a PDCCH is received during an ON duration <NUM> of the second DRX cycle illustrated. Note that the ON duration <NUM> ends at time <NUM>. However, the time that the UE is awake/active (the "active time") is extended to time <NUM> based on the length of the DRX inactivity timer and the time at which the PDCCH is received. Specifically, when the PDDCH is received, the UE starts the DRX inactivity timer and stays in the active state until the expiration of that timer (which is reset each time a PDDCH is received during the active time).

<FIG> illustrates an exemplary DRX configuration 500C in which a long DRX cycle is configured and a PDCCH and a DRX command MAC control element (CE) are received during an ON duration <NUM> of the second DRX cycle illustrated. Note that the active time beginning during ON duration <NUM> would normally end at time <NUM> due to the reception of the PDCCH at time <NUM> and the subsequent expiration of the DRX inactivity timer at time <NUM>, as discussed above with reference to <FIG>. However, in the example of <FIG>, the active time is shortened to time <NUM> based on the time at which the DRX command MAC CE, which instructs the UE to terminate the DRX inactivity timer and the ON duration timer, is received.

In greater detail, the active time of a DRX cycle is the time during which the UE is considered to be monitoring the PDCCH. The active time may include the time during which the ON duration timer is running, the DRC 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, an uplink grant for a pending HARQ retransmission can occur and there is data in the corresponding HARQ buffer, or a PDCCH indicating a new transmission addressed to the cell radio network temporary identifier (C-RNTI) of the UE has not been received after successful reception of a random access response (RAR) for the preamble not selected by the UE. And, in the non-contention based random access (RA), after receiving the RAR, the UE should be in an active state until the PDCCH indicating new transmission addressed to the C-RNTI of the UE is received.

Referring now to accuracy criteria for positioning a UE, regulatory standards are considered as a minimum performance target for NR positioning studies. For regulatory use cases, the following standards are considered as minimum performance targets for NR positioning: (<NUM>) horizontal positioning error less than or equal to <NUM> meters (m) for <NUM>% of UEs, (<NUM>) vertical positioning error less than <NUM> for <NUM>% of UEs (sufficient for floor level vertical accuracy), and (<NUM>) end to end latency and time-to-first-fix (TTFF) of less than <NUM> seconds.

Additional positioning criteria based on commercial use cases can be used as input performance targets that are subject to further analysis in terms of performance/complexity tradeoffs in different evaluation scenarios. As a starting point for commercial use cases, the following criteria may be considered as performance targets for RAT-dependent solutions, and may be subject to further analysis in terms of performance/complexity tradeoffs for NR positioning radio-layer solutions: (<NUM>) horizontal positioning error less than <NUM> for <NUM>% of UEs in indoor deployment scenarios, (<NUM>) vertical positioning error less than <NUM> for <NUM>% of UEs in indoor deployment scenarios, (<NUM>) horizontal positioning error less than <NUM> for <NUM>% of UEs in outdoor deployments scenarios, (<NUM>) vertical positioning error less than <NUM> for <NUM>% of UEs in outdoor deployment scenarios, and (<NUM>) end to end latency of less than one second.

Note that the criteria listed above do not eliminate more or less demanding commercial use cases. In addition, an "indoor deployment" means that the UEs and base stations are deployed in an indoor environment. Similarly, an "outdoor deployment" means that the UEs and base stations are deployed in an outdoor environment. Further, it should be understood that no single positioning technology is required to meet all of the above criteria for every scenario.

Referring now to the interaction of reference signals (e.g., PRS) and DRX, there are various considerations. For NR, when it comes to CSI-RS for mobility, if the UE is configured with a DRX cycle, the UE is not expected to perform measurements of CSI-RS resources other than during the active time for measurements based on the parameter "CSI-RS-Resource-Mobility. " If the UE is configured with a DRX cycle, and the DRX cycle in use is larger than <NUM> (considered a very large DRX cycle), the UE may not expect that CSI-RS resources are available other than during the active time for measurements based on CSI-RS-Resource-Mobility. Otherwise, the UE may assume CSI-RS are available for measurements based on CSI-RS-Resource-Mobility.

For NR, regarding CSI acquisition and feedback, when DRX is configured, the UE provides a CSI report only if it is receiving at least one CSI-RS transmission occasion for channel measurement and CSI-RS and/or CSI interference measurement (CSI-IM) occasion for interference measurement in the DRX active time no later than a CSI reference resource, and drops (does not send) the report otherwise. If the UE is configured with a DRX cycle, the most recent CSI measurement occasion occurs in the DRX active time for CSI to be reported.

In contrast, for LTE, regarding PRS reception, all intra-frequency RSTD measurement criteria should apply without DRX as well as for any DRX and eDRX_CONN cycles specified in 3GPP TS <NUM> (which is publicly available and is incorporated herein by reference in its entirety). That is, the UE is expected to wake up and measure PRS outside the active DRX period if necessary. Any DRX may be configured at the UE when an LPP request arrives (LPP is not decodable by the base station), and the UE is expected to fulfil the criteria. To fulfil them, the UE may need to measure outside the active DRX, that is, when otherwise in an inactive, or sleep, mode. Otherwise, there may be a risk that PRS occasions always fall in DRX inactive periods.

As will be appreciated, using an NR CSI-RS reception scheme for PRS reception when operating in DRX mode could result in too few PRS measurements, and therefore, insufficient positioning accuracy. Using the LTE PRS reception scheme, however, would result in unnecessary power consumption. As such, there is a need for improved techniques for PRS reception while operating in DRX mode.

Accordingly, in the present disclosure, the serving base station and/or the UE can inform the location server (e.g., location server <NUM>, LMF <NUM>) of the assigned DRX configuration. The serving base station can inform the location server using NR positioning protocol type A (NRPPa), and/or the UE can inform the location serving using LPP (or the corresponding NR protocol). The assigned DRX configuration would be communicated to the location server in a new information element (IE) that would include the parameters in Table <NUM>. This IE may have the same format as the DRX-Configuration IE for RRC. The location server can then attempt to align the scheduled PRS resources with the UE's DRX active time so that positioning performance is not affected and low power consumption is achieved. In an aspect, whether or not the base station and/or the UE inform the location server of the DRX configuration may depend on whether or not the location server is part of the RAN (in some implementations, the location server is outside of the RAN and cannot communicate with components of the RAN). For example, for a location server that is not part of the RAN, this feature may not be supported, and vice versa.

If the location server is made aware of the DRX configuration, it can configure the UE according to various options. As a first option, the location server can configure the UE to measure PRS resources independent of the DRX configuration, or to meet the positioning performance request independent of the DRX configuration. In this case, as in LTE, the UE will wake up outside of the active DRX period as necessary to measure PRS resources to meet the requested positioning performance. As a second option, the location server can configure the UE to measure a selection of the PRS resources according to the DRX configuration (and up to UE implementation), or to meet a different set of, perhaps more relaxed, positioning performance criteria based on the amount of overlap of the DRX active times with the PRS resources.

In an aspect, the location server may configure the UE to measure PRS independently of, or based on, the DRX configuration with a <NUM>-bit field in the PRS-Information message of the LPP protocol. Another option is without an explicit configuration. If the UE sends the DRX configuration to the location server, then the understanding may be that the UE will measure a selection of PRS resources according to the signaled DRX configuration and associated performance requirements. If the base station informs the location server of the DRX configuration, then a field can be added in the PRS-Information message in LPP that allows the location server to inform the UE that the DRX configuration is known at the location server.

There may also be the same considerations for uplink reference signal (e.g., SRS) transmissions when DRX is configured. That is, the location server may configure the UE to transmit the uplink reference signals regardless of the DRX configuration, or to transmit the uplink reference signals with as much overlap with the DRX active times as is practicable. The location server can configure the UE using LPP.

If the location server is part of the RAN, it can configure the serving and neighboring base stations/cells of the UE to transmit their PRS occasions based on the UE's DRX configuration (a single UE for unicast PRS, or a group of UEs for multicast/broadcast PRS). In an aspect, this may be accomplished over additional NRPPa signaling between the location server and the base station(s).

A UE can handle an "overlap" between the occurrence of PRS resources and DRX active time in different ways. As a first option, if at least one PRS occasion of a given PRS resource is received within an ON duration (or within the active time) of the UE's DRX cycle, then the UE may be expected to receive the subsequent consecutive PRS occasions of that PRS resource that occur after the ON duration / active time. This is illustrated in <FIG>. As shown in <FIG>, an ON duration <NUM> of a UE's DRX cycle overlaps with the first two consecutive PRS occasions 620a and 620b ("OCC1" and "OCC2") of a given PRS resource ("PRS1"). As such, the UE is expected to remain active to receive the remaining consecutive PRS occasions 620c and 620d ("OCC3" and "OCC4") of the PRS resource (illustrated as active period <NUM>). It can then go back to sleep until the next ON duration <NUM>.

Note that in the example of <FIG>, no PDCCH is received during the ON duration <NUM>, and therefore, the UE remains active only long enough to receive the remaining PRS occasions 620c and 620d. Further, as discussed above with reference to <FIG>, groups of consecutive PRS occasions of a PRS resource may occur periodically (e.g., TPRS <NUM>). The UE is not expected to stay awake to receive every periodically occurring group of consecutive PRS occasions of the PRS resource, but rather, only the instance(s) (occasions 620a-d in the example of <FIG>) of the periodically occurring groups of consecutive PRS occasions of the PRS resource that overlap with an ON duration.

As a second option, if at least one occasion of a PRS resource of a PRS resource set is received within an ON duration (or within the active time) of the UE's DRX cycle, then the UE is expected to receive all PRS occasions of all PRS resources of the PRS resource set that occur after the ON duration / active time. This is illustrated in <FIG>. In the example of <FIG>, a PRS resource set <NUM> includes a first group of four consecutive PRS occasions 722a-d ("OCC1" to "OCC4") of a first PRS resource ("PRS1") and a second group of four consecutive PRS occasions 724a-d ("OCC1" to "OCC4") of a second, third, and fourth PRS resource ("PRS2," "PRS3," and "PRS4"). In an aspect, each of the different PRS resources (e.g., PRS1 to PRS4) may be transmitted on different downlink transmit beams.

In <FIG>, an ON duration <NUM> of a UE's DRX cycle overlaps with the first two consecutive PRS occasions 722a and 722b of the first PRS resource ("PRS1") of the PRS resource set <NUM>. As such, the UE is expected to remain active to receive the remaining PRS occasions of the PRS resources of the PRS resource set <NUM>, i.e., occasions 722c and 722d of the first PRS resource, occasions 724a and 724b of the second PRS resource, occasion 724c of the third PRS resource, and occasion 724d of the fourth PRS resource (illustrated as active period <NUM>). It can then go back to sleep until the next ON duration <NUM>.

Note that in the example of <FIG>, no PDCCH is received during the ON duration <NUM>, and therefore, the UE remains active only long enough to receive the remaining PRS occasions (occasions 722c to 724d) of the PRS resource set <NUM>. Further, PRS resource sets may be transmitted periodically. The UE is not expected to stay awake to receive every periodically occurring instance of the PRS resource set, but rather, only the instance (occasions 722a to 724d in the example of <FIG>) that overlaps with an ON duration.

As a third option for how the UE can handle an overlap between PRS and DRX active time, if at least one occasion of a PRS resource is received within an ON duration (or within the active time) of the UE's DRX cycle, then the UE is expected to receive all PRS resources inside the current slot and any subsequent slots that contain PRS resources up to a slot for which no PRS resource is configured to be received. This is illustrated in <FIG>. In the example of <FIG>, a first PRS resource set <NUM> includes a first group of four consecutive PRS occasions 824a-d and a second PRS resource set <NUM> includes a second group of four consecutive PRS occasions 824e-h. The first two occasions of each PRS resource set (i.e., occasions 824a, 824b, 824e, 824f) belong to a first PRS resource ("PRS1"), and the second two occasions of each PRS resource set (i.e., occasions 824c, 824d, <NUM>, <NUM>) belong to a second PRS resource ("PRS2"). Each occasion <NUM> may correspond to a slot (e.g., slot <NUM>). In an aspect, each of the different PRS resources may be transmitted on different downlink transmit beams.

In <FIG>, an ON duration <NUM> of a UE's DRX cycle overlaps with the first two consecutive PRS occasions 824a and 824b of the first PRS resource ("PRS1") of the PRS resource set <NUM>. As such, the UE is expected to remain active to receive all PRS resources in the current and subsequent occasions (here, slots) that contain PRS resources up to an occasion (slot) for which no PRS resource is configured to be received by the UE (illustrated as active period <NUM>). In the example of <FIG>, the subsequent occasions are occasions 824c-h, which, in contrast to <FIG>, belong to two different PRS resource sets instead of the same PRS resource set as in <FIG>.

Note that for the options described above, there may be two modes. First, the additional time that the UE remains active to receive PRS (beyond the usual DRX ON duration) can be counted as DRX active time, in which case the UE can receive other downlink transmissions, such as the PDCCH or PDSCH. Alternatively, the additional time would not be counted as active time, in which case, the UE would only process PRS, and would not monitor for the PDCCH. As used herein, the term "active period" encompasses both options, and therefore, an active period may be commensurate with DRX active time, or may be the DRX active time plus any additional time during which the UE is active only for the purpose of processing PRS.

As a fourth option for how the UE can handle an overlap between PRS and DRX active time, the UE may only be expected to process the PRS occasions that are fully inside an ON duration (or an active duration) of the UE's DRX cycle, similar to CSI-RS for mobility. This is illustrated in <FIG>. As shown in <FIG>, an ON duration <NUM> of a UE's DRX cycle overlaps with the first two consecutive PRS occasions 920a and 920b ("OCC1" and "OCC2") of a given PRS resource ("PRS1"). The UE is only expected to process the PRS occasions (occasions 920a and 920b) that are fully inside the ON duration <NUM> (illustrated as active period <NUM>). It can then go back to sleep until the next ON duration <NUM>.

In the fourth option, when the UE's DRX configuration affects the UE's processing of PRS resources (e.g., the UE cannot measure as many PRS occasions as needed for a requested positioning accuracy), the positioning performance criteria can be adjusted to ensure that a minimum number of PRS occasions are being received. For example, since the UE is likely not able to process all PRS occasions due to its DRX configuration, the location server expects a reduced positioning performance to better align with the number of PRS occasions the UE will be able to measure during its ON durations.

Any of the options described above with reference to <FIG> can also be conditioned on the length of time that the UE would be expected to measure (i.e., be in active time). For example, if, due to the options described above, the UE would be expected to stay active much longer than its configured ON duration or DRX inactivity timer (e.g., longer than some threshold), then the UE would not be expected to measure these PRS resources. Instead, the UE may be configured to extend its active time only up to some threshold.

The same considerations would also apply to uplink reference signal (e.g., SRS) transmissions when DRX is configured. For example, if the UE is configured to transmit SRS, but not all SRS occasions overlap with DRX ON durations, then the UE may only transmit the SRS that overlap with the ON durations according to the options described above with reference to downlink reception. That is, the UE may transmit some additional number of SRS beyond the ON duration, similar to the reception of additional PRS occasions in the first, second, and third options described above.

As a fifth option for how the UE can handle an overlap between PRS and DRX active time, for round-trip-time (RTT) positioning, two reference signal transmissions are needed. For a downlink RTT procedure (initiated by the base station), the base station sends a downlink reference signal (e.g., PRS) to the UE and receives an uplink reference signal (e.g., SRS) from the UE in response. The response from the UE may include the UE reception-to-transmission measurement (UERx-Tx), i.e., the time from when the UE receives the downlink reference signal to the time it transmits the uplink reference signal. Based on the transmission time of the downlink reference signal and the reception time of the uplink reference signal (i.e., the base station's transmission-to-reception measurement (BSTx-Rx)) and the UE's reception-to-transmission measurement, the base station can determine the RTT between itself and the UE, and thereby the distance between itself and the UE.

An RTT positioning procedure can also be initiated on the uplink (e.g., by the UE). In that case, the UE sends an uplink reference signal (e.g., SRS) to the base station and receives a downlink reference signal (e.g., PRS) from the base station in response. The response from the base station may include the base station reception-to-transmission measurement (BSRx-Tx). Based on the transmission time of the uplink reference signal and the reception time of the downlink reference signal (i.e., the UE's transmission-to-reception measurement (UETx-Rx)) and the base station's reception-to-transmission measurement, the UE (or the location server) can determine the RTT between itself and the base station, and thereby the distance between itself and the base station.

In either of these cases, when the UE is configured for DRX, if reception of a downlink PRS (for base station-initiated RTT) or transmission of an SRS (for UE-initiated RTT) falls within a DRX active time, then the UE is expected to stay in active time for the reception/transmission of the other associated downlink/uplink reference signal. This is illustrated in <FIG>. As shown in <FIG>, in a first example 1000A, an ON duration <NUM> of a UE's DRX cycle overlaps with a PRS <NUM> of a downlink RTT positioning procedure. As such, the UE is expected to stay in active time for the transmission of the associated SRS <NUM> (illustrated as time period <NUM>). In a second example 1000B, an ON duration <NUM> of a UE's DRX cycle overlaps with an SRS <NUM> of an uplink RTT positioning procedure. As such, the UE is expected to stay in active time for the reception of the associated PRS <NUM> (illustrated as time period <NUM>). The UE can then perform positioning measurements (e.g., ToA, angle of arrival (AoA)) of the received PRS <NUM>.

In an aspect, issues may arise as to whether PRS or data transmission/reception should be given higher priority due to the DRX configuration. Generally, DRX active time is designed for discontinuous reception of data while the UE is otherwise in some power saving mode, so it could be rather short in time, for example, <NUM> to <NUM>. If PRS are received when DRX is configured, there may be a collision of PRS with data on the same resources. In that case, the UE may be expected to prioritize the reception and processing of PRS. Otherwise, if DRX is not configured, the UE may prioritize the reception of data, or treat both of them with equal priority.

<FIG> illustrates an exemplary method <NUM> of wireless communication, according to aspects of the disclosure. In an aspect, the method <NUM> may be performed by a UE (e.g., any of the UEs described herein) operating in a DRX mode.

At <NUM>, the UE receives a DRX configuration from a serving cell. In an aspect, operation <NUM> may be performed by the WWAN transceiver <NUM>, the receiver(s) <NUM>, the processing system <NUM>, the memory component <NUM>, and/or the PRS-DRX interaction manager <NUM>, any or all of which may be considered as means for performing this operation.

At <NUM>, the UE receives at least one reference signal resource configuration for receiving or transmitting reference signals from or to a TRP. The UE may receive the reference signal resource configuration from a location server (e.g., location server <NUM> or LMF <NUM>), or it may be encapsulated in messages received through a base station, or through one or more intermediaries, etc. In an aspect, operation <NUM> may be performed by the WWAN transceiver <NUM>, the receiver(s) <NUM>, the processing system <NUM>, the memory component <NUM>, and/or the PRS-DRX interaction manager <NUM>, any or all of which may be considered as means for performing this operation.

At <NUM>, the UE determines, at least based on the DRX configuration and the at least one reference signal resource configuration, whether an overlap exists between at least one reference signal occasion of a plurality of reference signal occasions of the at least one reference signal resource configuration and an active time of the DRX configuration. In an aspect, the plurality of reference signal occasions comprises a plurality of consecutive slots in which the at least one reference signal resource configuration is scheduled. In an aspect, operation <NUM> may be performed by the WWAN transceiver <NUM>, the processing system <NUM>, the memory component <NUM>, and/or the PRS-DRX interaction manager <NUM>, any or all of which may be considered as means for performing this operation.

At <NUM>, the UE receives or transmits, from or to a TRP, at least based on a determined overlap (at <NUM>), at least a first reference signal (e.g., PRS if receiving or SRS if transmitting) in at least one reference signal occasion. In an aspect, operation <NUM> may be performed by the WWAN transceiver <NUM>, the receiver(s) <NUM>, the transmitter(s) <NUM>, the processing system <NUM>, the memory component <NUM>, and/or the PRS-DRX interaction manager <NUM>, any or all of which may be considered as means for performing this operation.

At <NUM>, the UE optionally receives or transmits, from or to the TRP, while remaining in an active state of the DRX configuration, at least based on the determined overlap, at least a second reference signal (e.g., PRS if receiving or SRS if transmitting) in the remaining reference signal occasions of the plurality of reference signal occasions after expiration of the active time. The UE can then perform positioning based on the first and second reference signals while in DRX mode. In an aspect, operation <NUM> may be performed by the WWAN transceiver <NUM>, the receiver(s) <NUM>, the transmitter(s) <NUM>, the processing system <NUM>, the memory component <NUM>, and/or the PRS-DRX interaction manager <NUM>, any or all of which may be considered as means for performing this operation.

<FIG> illustrates an exemplary method <NUM> of wireless communication, according to aspects of the disclosure. In an aspect, the method <NUM> may be performed by a location server, such as location server <NUM> or LMF <NUM>.

At <NUM>, the location server receives, from a UE (e.g., any of the UEs described herein) operating in a DRX mode or a base station (e.g., any of the base stations described herein) serving the UE, a configuration of the DRX mode. In an aspect, operation <NUM> may be performed by the network interface(s) <NUM>, the processing system <NUM>, the memory component <NUM>, and/or the PRS-DRX interaction manager <NUM>, any or all of which may be considered as means for performing this operation.

At <NUM>, the location server transmits, to a second base station (e.g., either the serving base station or a neighboring base station), a PRS configuration to use for transmission of PRS to the UE. In an aspect, operation <NUM> may be performed by the network interface(s) <NUM>, the processing system <NUM>, the memory component <NUM>, and/or the PRS-DRX interaction manager <NUM>, any or all of which may be considered as means for performing this operation.

The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, an FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The methods, sequences and/or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A 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 disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. The ASIC may reside in a user terminal (e.g., UE).

In one or more exemplary aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage 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 that can be accessed by a computer. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

Claim 1:
A method of wireless communication performed by a user equipment, UE, operating in a discontinuous reception, DRX, mode, comprising:
receiving (<NUM>) a DRX configuration from a serving cell;
receiving (<NUM>) at least one reference signal resource configuration for receiving or transmitting reference signals from or to a transmission-reception point, TRP; characterised by:
determining (<NUM>), at least based on the DRX configuration and the at least one reference signal resource configuration, whether an overlap exists between at least one reference signal occasion of a plurality of reference signal occasions of the at least one reference signal resource configuration and an active time of the DRX configuration, wherein the plurality of reference signal occasions comprises a plurality of consecutive slots in which the at least one reference signal resource configuration is scheduled; and
receiving or transmitting (<NUM>), from or to the TRP, at least based on a determined overlap, at least a first reference signal in the at least one reference signal occasion.