Methods and devices for performing positioning when using dtx

Abstract

Disclosed are techniques for wireless communication. In an aspect, a user equipment, UE, sends (910), to a first entity comprising a base station, a location server or both, a request for DTX configuration information. The UE receives (920), from the first entity, DTX configuration information comprising a DTX configuration for at least one transmission / reception point, TRP, which may comprise a geosynchronous, GEO, cell. The UE performs (930) a positioning operation according to the DTX configuration.

Description

Qualcomm Ref. No.2303210WO POSITIONING REFERENCE SIGNAL (PRS) MEASUREMENT AND SIGNALING FOR CELL DISCONTINUOUS TRANSMISSION (DTX) IN NEW RADIO (NR) BACKGROUND OF THE DISCLOSURE Field of the Disclosure

[0001] Aspects of the disclosure relate generally to wireless communications. 2. Description of the Related Art

[0002] Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second-generation (2G) digital wireless phone service (including interim 2.5G and 2.75G networks), a third-generation (3G) high speed data, Internet-capable wireless service and a fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or 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 communications (GSM), etc. As used herein, the term “cell” refers to the geographic area served by a radio-frequency (RF) transmission point (TP) or a transmission / reception point (TRP). A cellular network may be comprised of many cells, which may or may not be geographically contiguous.

[0003] A fifth generation (5G) wireless standard, referred to as New Radio (NR), enables higher data transfer speeds, greater numbers of connections, and better coverage, among other improvements. The 5G standard, according to the Next Generation Mobile Networks Alliance, is designed to provide higher data rates as compared to previous standards, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements. These enhancements, as well as the use of higher frequency bands, advances in PRS processes and technology, and high-density deployments for 5G, enable highly accurate 5G-based positioning. QC2303210WOQualcomm Ref. No.2303210WO SUMMARY

[0004] 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.

[0005] In an aspect, a method of wireless communication performed by a user equipment (UE) includes sending, to a first entity comprising a base station, a location server, or both, a request for DTX configuration information; receiving, from the first entity, DTX configuration information comprising a DTX configuration for at least one transmission / reception point (TRP); and performing a positioning operation according to the DTX configuration information.

[0006] In an aspect, a method of wireless communication performed by a location server includes sending, to a base station, a request for DTX configuration information; and receiving, from the base station, DTX configuration information comprising a DTX configuration for at least one TRP.

[0007] In an aspect, a method of wireless communication performed by a base station includes receiving, from a first entity, a request for DTX configuration information; and sending, to the first entity, DTX configuration information comprising a DTX configuration for at least one TRP.

[0008] In an aspect, a method of wireless communication performed by a UE includes determining that a cell is operating according to a DTX configuration that is not known by the UE; determining the DTX configuration of the cell; and performing a positioning operation according to the DTX configuration.

[0009] In an aspect, a UE includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: send, to a first entity comprising a base station, a location server, or both, via the one or more transceivers, a request for DTX configuration information; receive, from the first entity via the one or more transceivers, DTX configuration information comprising a QC2303210WOQualcomm Ref. No.2303210WO DTX configuration for at least one TRP; and perform a positioning operation according to the DTX configuration information.

[0010] In an aspect, a location server (LS) includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: send, to a base station via the one or more transceivers, a request for DTX configuration information; and receive, from the base station via the one or more transceivers, DTX configuration information comprising a DTX configuration for at least one TRP.

[0011] In an aspect, a base station includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: receive, from a first entity via the one or more transceivers, a request for DTX configuration information; and send, to the first entity via the one or more transceivers, DTX configuration information comprising a DTX configuration for at least one TRP.

[0012] In an aspect, a UE includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: determine that a cell is operating according to a DTX configuration that is not known by the UE; determine the DTX configuration of the cell; and perform a positioning operation according to the DTX configuration.

[0013] 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 description. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects and not limitation thereof.

[0015] FIG. 1 illustrates an example wireless communications system, according to aspects of the disclosure.

[0016] FIGS.2A, 2B, and 2C illustrate example wireless network structures, according to aspects of the disclosure. QC2303210WOQualcomm Ref. No.2303210WO

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

[0018] FIG. 4A and FIG. 4B illustrate satellite communications using non-geosynchronous satellites and geosynchronous (GEO) satellites, respectively.

[0019] FIG. 5 is a signaling and event diagram illustrating signaling between a location server and a base station, according to aspects of the disclosure.

[0020] FIG.6 is a signaling and event diagram illustrating signaling between a UE and a location server, according to aspects of the disclosure.

[0021] FIG. 7 is a signaling and event diagram illustrating signaling between a UE and a base station, according to aspects of the disclosure.

[0022] FIG. 8A through FIG 8C are flowcharts illustrating portions of aa method that may be performed by a UE when the UE is aware that DTX is enabled for a GEO cell but does not know the exact configuration, according to aspects of the disclosure.

[0023] FIG. 9 is a flowchart of an example process, performed by a UE, associated with PRS measurement and signaling for cell DTX in NR, according to aspects of the disclosure.

[0024] FIG.10 is a flowchart of an example process, performed by a location server, associated with PRS measurement and signaling for cell DTX in NR, according to aspects of the disclosure.

[0025] FIG.11 is a flowchart of an example process, performed by a base station, associated with PRS measurement and signaling for cell DTX in NR, according to aspects of the disclosure.

[0026] FIG. 12 is a flowchart of another example process, performed by a UE, associated with PRS measurement and signaling for cell DTX in NR, according to aspects of the disclosure. DETAILED DESCRIPTION

[0027] Aspects of the disclosure are provided in the following description and related drawings directed to various examples provided for illustration purposes. Alternate aspects may be devised without departing from the scope of the disclosure. Additionally, well-known elements of the disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the disclosure. QC2303210WOQualcomm Ref. No.2303210WO

[0028] Disclosed are techniques for wireless communication, and in particular techniques handling DTX in GEO satellites with regards to positioning measurements and procedures. In an aspect, a user equipment (UE) may send, to a first entity comprising a base station, a location server, or both, a request for discontinuous transmission (DTX) configuration information. The UE may receive, from the first entity, DTX configuration information for at least one geosynchronous (GEO) cell. The UE may perform a positioning operation according to the DTX configuration.

[0029] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by informing a UE of the ON and OFF periods of both serving GEO cells and neighbor GEO cells, the UE can adjust its positioning behavior to take into account these OFF periods. In some examples, a GEO cell can modify its DTX OFF behavior to accommodate positioning UEs. In some examples, a location server can manage and coordinate DTX configurations for GEO cells, and provide DTX configuration information to UEs.

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

[0031] Those of skill in the art will appreciate that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description below may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, in part on the desired design, in part on the corresponding technology, etc.

[0032] Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein can be considered to be embodied entirely within any form of non- transitory computer-readable storage medium having stored therein a corresponding set QC2303210WOQualcomm Ref. No.2303210WO of computer instructions that, upon execution, would cause or instruct an associated processor of a device to perform the functionality described herein. Thus, the various aspects of the disclosure may be embodied in a number of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspects may be described herein as, for example, “logic configured to” perform the described action.

[0033] 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, consumer asset locating 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 device,” 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 the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.) and so on.

[0034] 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 next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be used primarily to support wireless access by UEs, including supporting data, voice, and / or signaling connections for the supported UEs. 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 QC2303210WOQualcomm Ref. No.2303210WO 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 uplink / reverse or downlink / forward traffic channel.

[0035] 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 (or several cell sectors) 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 radio frequency (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.

[0036] In some implementations that support positioning of UEs, a base station may not support wireless access by UEs (e.g., may not support data, voice, and / or signaling connections for UEs), but may instead transmit reference signals to UEs to be measured by the UEs, and / or may receive and measure signals transmitted by the UEs. Such a base station may be referred to as a positioning beacon (e.g., when transmitting signals to UEs) and / or as a location measurement unit (e.g., when receiving and measuring signals from UEs).

[0037] 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 QC2303210WOQualcomm Ref. No.2303210WO 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. As used herein, an RF signal may also be referred to as a “wireless signal” or simply a “signal” where it is clear from the context that the term “signal” refers to a wireless signal or an RF signal.

[0038] FIG.1 illustrates an example wireless communications system 100, according to aspects of the disclosure. The wireless communications 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. The base stations 102 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 stations may include eNBs and / or ng-eNBs where the wireless communications system 100 corresponds to an LTE network, or gNBs where the wireless communications system 100 corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

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

[0040] In addition to other functions, the base stations 102 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 QC2303210WOQualcomm Ref. No.2303210WO 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 102 may communicate with each other directly or indirectly (e.g., through the EPC / 5GC) over backhaul links 134, which may be wired or wireless.

[0041] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by a base station 102 in each geographic coverage area 110. 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), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) 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 of the logical communication entity and the base station that supports it, depending on the context. In addition, because a TRP is typically the physical transmission point of a cell, the terms “cell” and “TRP” may be used interchangeably. 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 110.

[0042] While neighboring macro cell base station 102 geographic coverage areas 110 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 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 area 110 of one or more macro cell base stations 102. A network that includes both small cell and macro cell base stations may be known as a heterogeneous network. A heterogeneous QC2303210WOQualcomm Ref. No.2303210WO network may also include home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).

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

[0044] The wireless communications system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in an unlicensed frequency spectrum, the WLAN STAs 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available.

[0045] The small cell base station 102' may operate in a licensed and / or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP 150. The small cell base station 102', employing LTE / 5G in an unlicensed frequency spectrum, may boost coverage to and / or increase capacity of the access network. NR in unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MULTEFIRE®.

[0046] The wireless communications system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW frequencies and / or near mmW frequencies in communication with a UE 182. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the QC2303210WOQualcomm Ref. No.2303210WO mmW / near mmW radio frequency band have high path loss and a relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) over a mmW communication link 184 to compensate for the extremely high path loss and short range. Further, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein.

[0047] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omni-directionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal for the receiving device(s). To change the directionality of the RF signal when transmitting, a network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal. For example, a network node may use an array of antennas (referred to as a “phased array” or an “antenna array”) that creates a beam of RF waves that can be “steered” to point in different directions, without actually moving the antennas. Specifically, the RF current from the transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions.

[0048] Transmit beams may be quasi-co-located, meaning that they appear to the receiver (e.g., a UE) as having the same parameters, regardless of whether or not the transmitting antennas of the network node themselves are physically co-located. In NR, there are four types of quasi-co-location (QCL) relations. Specifically, a QCL relation of a given type means that certain parameters about a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, 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 a 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 a second reference RF signal transmitted on the QC2303210WOQualcomm Ref. No.2303210WO 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 a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate the spatial receive parameter of a second reference RF signal transmitted on the same channel.

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

[0050] Transmit and receive beams may be spatially related. A spatial relation means that parameters for a second beam (e.g., a transmit or receive beam) for a second reference signal can be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a 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.

[0051] Note that a “downlink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. If the UE is forming the downlink beam, however, it is a receive beam to receive the downlink reference signal. Similarly, an “uplink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the uplink beam, it is an uplink receive beam, and if a UE is forming the uplink beam, it is an uplink transmit beam.

[0052] The electromagnetic spectrum is often subdivided, based on frequency / wavelength, into various classes, bands, channels, etc. In 5G NR two initial operating bands have been QC2303210WOQualcomm Ref. No.2303210WO identified as frequency range designations FR1 (410 MHz – 7.125 GHz) and FR2 (24.25 GHz – 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz – 300 GHz) which is identified by the INTERNATIONAL TELECOMMUNICATION UNION® as a “millimeter wave” band.

[0053] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz – 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend features of FR1 and / or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz – 71 GHz), FR4 (52.6 GHz – 114.25 GHz), and FR5 (114.25 GHz – 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0054] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band.

[0055] In a multi-carrier system, such as 5G, one of the carrier frequencies is referred to as the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and the remaining carrier frequencies are referred to as “secondary carriers” or “secondary serving cells” or “SCells.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by a UE 104 / 182 and the cell in which the UE 104 / 182 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 QC2303210WOQualcomm Ref. No.2303210WO 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 104 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 104 / 182 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 104 / 182 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.

[0056] For example, still referring to FIG. 1, one of the frequencies utilized by the macro cell base stations 102 may be an anchor carrier (or “PCell”) and other frequencies utilized by the macro cell base stations 102 and / or the mmW base station 180 may be secondary carriers (“SCells”). The simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz), compared to that attained by a single 20 MHz carrier.

[0057] The wireless communications system 100 may further include a UE 164 that may communicate with a macro cell base station 102 over a communication link 120 and / or the mmW base station 180 over a mmW communication link 184. For example, the macro cell base station 102 may support a PCell and one or more SCells for the UE 164 and the mmW base station 180 may support one or more SCells for the UE 164.

[0058] In some cases, the UE 164 and the UE 182 may be capable of sidelink communication. Sidelink-capable UEs (SL-UEs) may communicate with base stations 102 over communication links 120 using the Uu interface (i.e., the air interface between a UE and a base station). SL-UEs (e.g., UE 164, UE 182) may also communicate directly with each other over a wireless sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). A wireless sidelink (or just “sidelink”) is an adaptation of the core QC2303210WOQualcomm Ref. No.2303210WO cellular (e.g., LTE, NR) standard that allows direct communication between two or more UEs without the communication needing to go through a base station. Sidelink communication may be unicast or multicast, and may be used for device-to-device (D2D) media-sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, etc.), emergency rescue applications, etc. One or more of a group of SL- UEs utilizing sidelink communications may be within the geographic coverage area 110 of a base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of a base station 102 or be otherwise unable to receive transmissions from a base station 102. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1:M) system in which each SL-UE transmits to every other SL-UE in the group. In some cases, a base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are carried out between SL-UEs without the involvement of a base station 102.

[0059] In an aspect, the sidelink 160 may operate over a wireless communication medium of interest, which may be shared with other wireless communications between other vehicles and / or infrastructure access points, as well as other RATs. A “medium” may be composed of one or more time, frequency, and / or space communication resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs. In an aspect, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among various RATs. Although different licensed frequency bands have been reserved for certain communication systems (e.g., by a government entity such as the Federal Communications Commission (FCC) in the United States), these systems, in particular those employing small cell access points, have recently extended operation into unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies, most notably IEEE 802.11x WLAN technologies generally referred to as “Wi-Fi.” Example systems of this type include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and so on. QC2303210WOQualcomm Ref. No.2303210WO

[0060] Note that although FIG. 1 only illustrates two of the UEs as SL-UEs (i.e., UEs 164 and 182), any of the illustrated UEs may be SL-UEs. Further, although only UE 182 was described as being capable of beamforming, any of the illustrated UEs, including UE 164, may be capable of beamforming. Where SL-UEs are capable of beamforming, they may beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UEs 104), towards base stations (e.g., base stations 102, 180, small cell 102’, access point 150), etc. Thus, in some cases, UEs 164 and 182 may utilize beamforming over sidelink 160.

[0061] In the example of FIG.1, any of the illustrated UEs (shown in FIG.1 as a single UE 104 for simplicity) may receive signals 124 from one or more Earth orbiting space vehicles (SVs) 112 (e.g., satellites). In an aspect, the SVs 112 may be part of a satellite positioning system that a UE 104 can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable receivers (e.g., UEs 104) to determine their location on or above the Earth based, at least in part, on positioning signals (e.g., signals 124) received from the transmitters. Such a transmitter typically transmits a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SVs 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. A UE 104 may include one or more dedicated receivers specifically designed to receive signals 124 for deriving geo location information from the SVs 112.

[0062] In a satellite positioning system, the use of signals 124 can be augmented by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems. For example an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi- functional Satellite Augmentation System (MSAS), the Global Positioning System (GPS) Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and / or the like. Thus, as used herein, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

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

[0064] The wireless communications system 100 may further include one or more UEs, such as UE 190, that connects indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “sidelinks”). In the example of FIG. 1, UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to the WLAN AP 150 (through which UE 190 may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links 192 and 194 may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), WI-FI DIRECT®, BLUETOOTH®, and so on.

[0065] FIG.2A illustrates an example wireless network structure 200. For example, a 5GC 210 (also referred to as a Next Generation Core (NGC)) can be viewed functionally 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 function, access to data networks, IP routing, etc.) which operate cooperatively to form the core network. User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210 and specifically to the user plane functions 212 and control plane functions 214, respectively. In an additional configuration, an ng-eNB 224 may also be connected to the 5GC 210 via NG-C 215 to the control plane functions 214 and NG-U 213 to user plane functions 212. Further, ng-eNB 224 may directly communicate with gNB 222 via a backhaul connection 223. In some configurations, a 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 (or both) gNB 222 or ng-eNB 224 may communicate with one or more UEs 204 (e.g., any of the UEs described herein). QC2303210WOQualcomm Ref. No.2303210WO

[0066] Another optional aspect may include a location server 230, which may be in communication with the 5GC 210 to provide location assistance for UE(s) 204. The location server 230 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 230 can be configured to support one or more location services for UEs 204 that can connect to the location server 230 via the core network, 5GC 210, and / or via the Internet (not illustrated). Further, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network (e.g., a third party server, such as an original equipment manufacturer (OEM) server or service server).

[0067] FIG.2B illustrates another example wireless network structure 240. A 5GC 260 (which may correspond to 5GC 210 in FIG. 2A) can be viewed functionally as control plane functions, provided by an access and mobility management function (AMF) 264, and user plane functions, provided by a user plane function (UPF) 262, which operate cooperatively 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, transport for session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 204 and the short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives the intermediate key that was established as a result of the UE 204 authentication process. In the case of authentication based on a UMTS (universal mobile telecommunications system) subscriber identity module (USIM), the AMF 264 retrieves the security material from the AUSF. The functions of the AMF 264 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 264 also includes location services management for regulatory services, transport for location services messages between the UE 204 and a location management function (LMF) 270 (which acts as a location server 230), transport for location services messages between the NG-RAN 220 QC2303210WOQualcomm Ref. No.2303210WO and the LMF 270, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, and UE 204 mobility event notification. In addition, the AMF 264 also supports functionalities for non-3GPP® (Third Generation Partnership Project) access networks.

[0068] Functions of the UPF 262 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 a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., uplink / downlink rate enforcement, reflective 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 of one or more “end markers” to the source RAN node. The UPF 262 may also support transfer of location services messages over a user plane between the UE 204 and a location server, such as an SLP 272.

[0069] The functions of the SMF 266 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 262 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 266 communicates with the AMF 264 is referred to as the N11 interface.

[0070] Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260 to provide location assistance for UEs 204. The LMF 270 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 270 can be configured to support one or more location services for UEs 204 that can connect to the LMF 270 via the core network, 5GC 260, and / or via the Internet (not illustrated). The SLP 272 may support similar functions to the LMF 270, but whereas the LMF 270 may communicate with the AMF 264, NG-RAN 220, and UEs 204 over a control plane (e.g., using interfaces and protocols intended to convey signaling messages and not voice or data), the SLP 272 may communicate with UEs 204 and external clients QC2303210WOQualcomm Ref. No.2303210WO 20 (e.g., third-party server 274) over a user plane (e.g., using protocols intended to carry voice and / or data like the transmission control protocol (TCP) and / or IP).

[0071] Yet another optional aspect may include a third-party server 274, which may be in communication with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and / or the UPF 262), the NG-RAN 220, and / or the UE 204 to obtain location information (e.g., a location estimate) for the UE 204. As such, 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 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.

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

[0073] The functionality of a gNB 222 may be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DUs) 228, and one or more gNB radio units (gNB-RUs) 229. A gNB-CU 226 is a logical node that includes the base station functions of transferring user data, mobility control, radio access network sharing, positioning, session management, and the like, except for those functions allocated exclusively to the gNB-DU(s) 228. More specifically, the gNB-CU 226 generally host the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222. A gNB-DU 228 is a logical node that generally hosts the radio link control (RLC) and medium access control (MAC) layer of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and the one or more gNB-DUs 228 is referred to as the “F1” interface. The physical (PHY) layer functionality of a gNB 222 is generally QC2303210WOQualcomm Ref. No.2303210WO hosted by one or more standalone gNB-RUs 229 that perform functions such as power amplification and signal transmission / reception. The interface between a gNB-DU 228 and a gNB-RU 229 is referred to as the “Fx” interface. Thus, a UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, with a gNB-DU 228 via the RLC and MAC layers, and with a gNB-RU 229 via the PHY layer.

[0074] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, or a network equipment, such as a base station, or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), a transmit receive point (TRP), or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.

[0075] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU also can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0076] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN ALLIANCE®)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C- RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the QC2303210WOQualcomm Ref. No.2303210WO disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0077] FIG. 2C illustrates an example disaggregated base station architecture 250, according to aspects of the disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 259 via an E2 link, or a Non-Real Time (Non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) Framework 255, or both). A CU 280 may communicate with one or more DUs 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an F1 interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RUs 287 may communicate with respective UEs 204 via one or more radio frequency (RF) access links. In some implementations, the UE 204 may be simultaneously served by multiple RUs 287.

[0078] Each of the units, i.e., the CUs 280, the DUs 285, the RUs 287, as well as the Near-RT RICs 259, the Non-RT RICs 257 and the SMO Framework 255, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0079] In some aspects, the CU 280 may host one or more higher layer control functions. Such control functions can include RRC, PDCP, service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 280. The CU 280 may be configured to handle user plane functionality (i.e., Central Unit – User Plane (CU- UP)), control plane functionality (i.e., Central Unit – Control Plane (CU-CP)), or a QC2303210WOQualcomm Ref. No.2303210WO 23 combination thereof. In some implementations, the CU 280 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 280 can be implemented to communicate with the DU 285, as necessary, for network control and signaling.

[0080] The DU 285 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 287. In some aspects, the DU 285 may host one or more of a RLC layer, a MAC layer, and one or more high PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP®). In some aspects, the DU 285 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 285, or with the control functions hosted by the CU 280.

[0081] Lower-layer functionality can be implemented by one or more RUs 287. In some deployments, an RU 287, controlled by a DU 285, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 287 can be implemented to handle over the air (OTA) communication with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 287 can be controlled by the corresponding DU 285. In some scenarios, this configuration can enable the DU(s) 285 and the CU 280 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0082] The SMO Framework 255 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an O1 interface). For QC2303210WOQualcomm Ref. No.2303210WO 24 virtualized network elements, the SMO Framework 255 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs 280, DUs 285, RUs 287 and Near-RT RICs 259. In some implementations, the SMO Framework 255 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 261, via an O1 interface. Additionally, in some implementations, the SMO Framework 255 can communicate directly with one or more RUs 287 via an O1 interface. The SMO Framework 255 also may include a Non-RT RIC 257 configured to support functionality of the SMO Framework 255.

[0083] The Non-RT RIC 257 may be configured to include a logical function that enables non- real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 259. The Non-RT RIC 257 may be coupled to or communicate with (such as via an A1 interface) the Near- RT RIC 259. The Near-RT RIC 259 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 280, one or more DUs 285, or both, as well as an O-eNB, with the Near-RT RIC 259.

[0084] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 259, the Non-RT RIC 257 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 259 and may be received at the SMO Framework 255 or the Non-RT RIC 257 from non-network data sources or from network functions. In some examples, the Non-RT RIC 257 or the Near-RT RIC 259 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 257 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 255 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies).

[0085] FIGS. 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated into a UE 302 (which may correspond to QC2303210WOQualcomm Ref. No.2303210WO any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270, or alternatively may be independent from the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in FIGS. 2A and 2B, such as a private network) to support the operations described 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.

[0086] The UE 302 and the base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) 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 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium of interest (e.g., some set of time / frequency resources in a particular frequency spectrum). The WWAN transceivers 310 and 350 may be variously configured for transmitting and encoding signals 318 and 358 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 318 and 358 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358, respectively.

[0087] The UE 302 and the base station 304 each also include, at least in some cases, one or more short-range wireless transceivers 320 and 360, respectively. The short-range QC2303210WOQualcomm Ref. No.2303210WO wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., Wi-Fi, LTE Direct, BLUETOOTH®, ZIGBEE®, Z-WAVE®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), ultra- wideband (UWB), etc.) over a wireless communication medium of interest. The short- range wireless transceivers 320 and 360 may be variously configured for transmitting and encoding signals 328 and 368 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 328 and 368 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 may be Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® and / or Z-WAVE® transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to- everything (V2X) transceivers.

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

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

[0090] A transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). A transceiver may be an integrated device (e.g., embodying transmitter circuitry and receiver circuitry in a single device) in some implementations, may comprise separate transmitter circuitry and separate receiver circuitry in some implementations, or may be embodied in other ways in other implementations. The transmitter circuitry and receiver circuitry of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) 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 a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (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 a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In an aspect, the transmitter circuitry and receiver circuitry may share the same plurality of antennas (e.g., antennas 316, 326, 356, 366), such that the respective apparatus can only QC2303210WOQualcomm Ref. No.2303210WO 28 receive or transmit at a given time, not both at the same time. A wireless transceiver (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listen module (NLM) or the like for performing various measurements.

[0091] As used herein, the various wireless transceivers (e.g., transceivers 310, 320, 350, and 360, and network transceivers 380 and 390 in some implementations) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may generally be characterized as “a transceiver,” “at least one transceiver,” or “one or more transceivers.” As such, whether a particular transceiver is a wired or wireless transceiver may be inferred from the type of communication performed. For example, backhaul communication between network devices or servers will generally relate to signaling via a wired transceiver, whereas wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) will generally relate to signaling via a wireless transceiver.

[0092] The UE 302, the base station 304, and the network entity 306 also include other components that may be used in conjunction with the operations as disclosed herein. The UE 302, the base station 304, and the network entity 306 include one or more processors 332, 384, and 394, respectively, for providing functionality relating to, for example, wireless communication, and for providing other processing functionality. The processors 332, 384, and 394 may therefore provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, means for indicating, etc. In an aspect, the 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, or various combinations thereof.

[0093] The UE 302, the base station 304, and the network entity 306 include memory circuitry implementing memories 340, 386, and 396 (e.g., each including a memory device), respectively, for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, and so on). The memories 340, 386, and 396 may therefore provide means for storing, means for retrieving, means for maintaining, etc. In some cases, the UE 302, the base station 304, and the network entity 306 may include positioning module 342, 388, and 398, respectively. The positioning module 342, 388, QC2303210WOQualcomm Ref. No.2303210WO and 398 may be hardware circuits that are part of or coupled to the processors 332, 384, and 394, respectively, that, when executed, cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. In other aspects, the positioning module 342, 388, and 398 may be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning module 342, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that, when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. FIG. 3A illustrates possible locations of the positioning module 342, which may be, for example, part of the one or more WWAN transceivers 310, the memory 340, the one or more processors 332, or any combination thereof, or may be a standalone component. FIG.3B illustrates possible locations of the positioning module 388, which may be, for example, part of the one or more WWAN transceivers 350, the memory 386, the one or more processors 384, or any combination thereof, or may be a standalone component. FIG.3C illustrates possible locations of the positioning module 398, which may be, for example, part of the one or more network transceivers 390, the memory 396, the one or more processors 394, or any combination thereof, or may be a standalone component.

[0094] The UE 302 may include one or more sensors 344 coupled to the one or more processors 332 to provide means for sensing or detecting movement and / or orientation information that is independent of motion data derived from signals received by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, and / or the satellite signal receiver 330. By way of example, the sensor(s) 344 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) 344 may include a plurality of different types of devices and combine their outputs in order to provide motion information. For example, the sensor(s) 344 may use a combination of a multi-axis accelerometer and orientation sensors to provide the ability to compute positions in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems. QC2303210WOQualcomm Ref. No.2303210WO

[0095] In addition, the UE 302 includes a user interface 346 providing means 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 base station 304 and the network entity 306 may also include user interfaces.

[0096] Referring to the one or more processors 384 in more detail, in the downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 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 one or more processors 384 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 PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0097] The transmitter 354 and the receiver 352 may implement Layer-1 (L1) functionality associated with various signal processing functions. Layer-1, 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 354 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)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division QC2303210WOQualcomm Ref. No.2303210WO 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. The OFDM symbol stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and / or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a respective spatial stream for transmission.

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

[0099] In the downlink, the one or more processors 332 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 one or more processors 332 are also responsible for error detection.

[0100] Similar to the functionality described in connection with the downlink transmission by the base station 304, the one or more processors 332 provides RRC layer functionality QC2303210WOQualcomm Ref. No.2303210WO 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.

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

[0102] The uplink transmission is processed at the base station 304 in a manner similar to that described in connection with the receiver function at the UE 302. The receiver 352 receives a signal through its respective antenna(s) 356. The receiver 352 recovers information modulated onto an RF carrier and provides the information to the one or more processors 384.

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

[0104] For convenience, the UE 302, the base station 304, and / or the network entity 306 are shown in FIGS.3A, 3B, and 3C as including various components that may be configured according to the various examples described herein. It will be appreciated, however, that the illustrated components may have different functionality in different designs. In particular, various components in FIGS. 3A to 3C are optional in alternative configurations and the various aspects include configurations that may vary due to design choice, costs, use of the device, or other considerations. For example, in case of FIG.3A, QC2303210WOQualcomm Ref. No.2303210WO a particular implementation of UE 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or personal computer (PC) or laptop may have Wi-Fi and / or BLUETOOTH® capability without cellular capability), or may omit the short- range wireless transceiver(s) 320 (e.g., cellular-only, etc.), or may omit the satellite signal receiver 330, or may omit the sensor(s) 344, and so on. In another example, in case of FIG. 3B, a particular implementation of the base station 304 may omit the WWAN transceiver(s) 350 (e.g., a Wi-Fi “hotspot” access point without cellular capability), or may omit the short-range wireless transceiver(s) 360 (e.g., cellular-only, etc.), or may omit the satellite signal receiver 370, and so on. For brevity, illustration of the various alternative configurations is not provided herein, but would be readily understandable to one skilled in the art.

[0105] The various components of the UE 302, the base station 304, and the network entity 306 may be communicatively coupled to each other over data buses 334, 382, and 392, respectively. In an aspect, the data buses 334, 382, and 392 may form, or be part of, a communication interface of the UE 302, the base station 304, and the network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 334, 382, and 392 may provide communication between them.

[0106] The components of FIGS.3A, 3B, and 3C may be implemented in various ways. In some implementations, the components of FIGS. 3A, 3B, and 3C 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 310 to 346 may be implemented by processor and memory component(s) of the UE 302 (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 350 to 388 may be implemented by processor and memory component(s) of the base station 304 (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 390 to 398 may be implemented by processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). For simplicity, various QC2303210WOQualcomm Ref. No.2303210WO operations, acts, and / or functions are described herein as being performed “by a UE,” “by a base station,” “by a network 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 302, base station 304, network entity 306, etc., such as the processors 332, 384, 394, the transceivers 310, 320, 350, and 360, the memories 340, 386, and 396, the positioning module 342, 388, and 398, etc.

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

[0108] FIG. 4A and FIG. 4B illustrate satellite communications using non-GEO and GEO satellites, respectively. Satellite access networks typically have radio cells that are much larger than radio cells for terrestrial access networks. Because low earth orbit (LEO) and medium earth orbit (MEO) satellites are not geosynchronous, the location of the radio cell changes over time as the LEO or MEO satellite orbits the earth.

[0109] This is illustrated in FIG.4A, which shows two LEO satellites, SV 400 and SV 402. SV 400 has a radio cell 404 and SV 402 has a radio cell 406, both of which change their respective geographical locations on the planet as the satellites orbit the planet. In the example shown in FIG. 4A, terrestrial UE 408 is currently not within any radio cell but UE 410 is within the radio cell 406 and thus can communicate with SV 402. After some time, however, as SV 402 continues its orbit around the planet, UE 410 will be out of the radio cell 406, and UE 408 will be within the radio cell 404 and will thus be able to communicate with SV 400.

[0110] For example, in the scenario where LEO and MEO radio cells are moving, given a cell diameter of 1000km and a satellite speed of 7.56km / s, a UE would be in coverage of a radio cell for 132.2 seconds (2.2 minute). FIG. 4A illustrates an example where radio coverage for UE 408 and UE 410 is not continuous because there is no satellite between SV 400 and SV 402 to provide such coverage. While UE 408 is between radio cell 404 and radio cell 406, UE 408 will be unreachable from the core network. If UE 408 is aware of when it is out of coverage and for how long it will be out of coverage, then the UE 408 QC2303210WOQualcomm Ref. No.2303210WO can save power by not attempting to connect to the satellite network during out-of- coverage periods. If a terrestrial network is available, the UE 408 may seek and join the terrestrial network. If no terrestrial network is available, the UE 408 may enter a power saving mode until it enters radio cell 404, for example. From the satellite side, if SV 400 determines that there are not UEs currently in its coverage area defined by radio cell 404, the SV 400 has the option to deactivate the radio cell 404, which would save the use of network resources and reduce the power consumption of SV 400, and to reactivate the radio cell 404 when it starts to cover a geographic area that does include UEs.

[0111] FIG. 4B illustrates an example in which a geosynchronous satellite, SV 412, provides a radio cell 414 that does not move (if SV 412 is geostationary) or does not move so much that terrestrial UE 416 ever leaves the coverage area (if SV 412 is geosynchronous but not geostationary), and which may be referred to hereinafter as a “GEO cell”. Even in this case, there are possible benefits to giving SV 412 the option to deactivate its radio cell 414. For example, during off hours (e.g., late night to early morning), the number of UEs that may be actively performing UL and DL transmissions (i.e., in RRC_CONNECTED mode) may be a small number, or even zero. In this scenario, the SV 412 may deactivate its radio cell 414, e.g., to save the use of network resources.

[0112] Network energy efficiency mechanisms can be used to save network resources during off hours. Currently in terrestrial networks (e.g., LTE, NR), the network may share coverage information and decide which cell(s) to turn off and which cell(s) to leave on. If a cell is turned off, the UE will have the option to go to other cells according to existing rules or methods (e.g., based on measurements, barring, handover, etc.). This will have no additional change in UE behavior.

[0113] A GEO cell can be assumed to be a permanently fixed cell, like a terrestrial network cell. If a cell is going to be turned off, the UE would need an indication of the ON / OFF periodicity or simply when the cell is going to be off and for how long. This information is typically indicated to a UE via system information or unicast RRC message or NAS message. However, in case of GEO cell coverage – i.e., provided by a satellite rather than a ground-based TRP – especially in remote areas (e.g., desert, ocean, etc.), there may not be any other options for a UE if a GEO cell is turned off. If the coverage is in a city, it is likely the UE would not have connected to the GEO cell in the first place. Therefore, UEs using a GEO cell are likely to be in remote areas. QC2303210WOQualcomm Ref. No.2303210WO

[0114] While there are potential benefits to turning a GEO cell off, conventional networks do not define mechanisms to do so. For example, a terrestrial serving cell may broadcast a parameter t-service-r17 in system information block (SIB) type 3 (SIB3) to let the UE know when the current cell coverage is stopped, but t-service-r17 is not currently defined to be applicable for GEO cells.

[0115] One approach is to provide a mechanism for providing a UE with an indication of GEO cell turn-off, including information that allows the UE to save power, while allowing mobile terminated (MT) paging to operate as intended. For example, a serving cell can broadcast a SIB type 32 (SIB32), to provide the UE with serving satellite and neighbor satellite information including the cell start time. Broadcast of SIB32 by a serving cell indicates to the UE that the cell supports discontinuous coverage and also indicates to the UE when current satellite coverage is stopped and when the UE should wake up to find the satellite coverage. Thus, in this approach, a GEO cell may broadcast t-service in SIB3, include a new parameter satelliteID-r17 in SIB type 31 (SIB31) to indicate the GEO cell to which t-service applies, and broadcast the service cell satellite ID (or both serving cell satellite ID and TLE ephemeris data) in SIB32. SIB32 also includes a new parameter t-serviceStart-r17, which indicates the GEO cell start time. In one option, during cell off time (from stop to cell start), the UE does not perform any IDLE mode task. In another option, during cell off time, the UE still performs IDLE mode tasks, but if the UE finds no serving cell signal, it assumes no PDCCH detection and continues to the next paging occasion, i.e., failure to detect a signal does not trigger a measurement and cell reselection procedure.

[0116] Like the conventional paging discontinuous reception (DRX) cycle, new, cell-specific DTX cycle information can be provided to all UEs within a cell. In one example, SIB3 can include additional parameters that define the DTX cycle, such as a start offset as a system frame number (SFN) value (dtxOffset); a DTX cycle length (dtxPagingCycle); and a DTX off period (dtxOff). An example of DTX cycle information added to SIB3 is shown below, with additions shown in bold font: SystemInformationBlockType3 ::= SEQUENCE {TimeOffsetUTC-r17 OPTIONAL -- Need OR DTX-Config ::= SEQUENCE { QC2303210WOQualcomm Ref. No.2303210WO}

[0117] Data communications requirements are flexible enough to accommodate the DTX technique described above, but positioning tasks may have different timing requirements than data communication. For example, positioning based on reference signal time delay (RSTD) measurements has a measurement period length requirement TRSTD,Total for some number ^ of positioning frequency layers (PFLs), which is defined as:andwhere: • i is the PFL index. • ^^^^^ோௌ,^is the carrier-specific scaling factor for PRS-based measurements. •^௫^^^^,^is the UE Rx beam sweeping factor (=1 for FR1 and =8 for FR2). •^^^ோ^^ௌ௧,^is the maximum number of DL PRS resources per slot. • ^^^,^^^ and^^ᇱare UE capabilities corresponding to durationOfPRS-Processing and maxNumOfDL-PRS-ResProcessedPerSlot. • ^^௩^^^^^^^ುೃೄ,^is the time duration of available PRS to be measured during ^^௩^^^^^^^ುೃೄ,^. •^^^^^^^(= 4) is the number of PRS RSTD samples. • T^^^^ୡ^,୧is periodicity of UE Rx-Tx time difference measurement in positioning frequency layer i:• T୧corresponds to durationOfPRS-ProcessingSymbolsInEveryTms.QC2303210WOQualcomm Ref. No.2303210WOleast common multiple between^^ோௌ,^and ^^^^^. • ^^^^^is the measurement gap periodicity. •^^ோௌ,iis the effective PRS periodicity with PRS muting.^^ோௌ,iൌ ^^^൫^^௨௧^^^, ^ή ^^^^ோ^ௌ,^൯ where ^ is the resource set index. If the PFLi has more than one DL PRS resource set with different PRS periodicities with muting, then^ כ^ோௌ, the least common m^ோௌ ௪^௧^ ^௨௧^^^^௨௧^^^ ^^^^ultiple of^^^^among DL PRS resource sets is used to derive T^ୖୗ,୧. •^^^^ோ^ௌis the periodicity of PRS resource sets given by the higher-layer parameter DL- PRS-Periodicity. • ^ is a scaling factor considering PRS muting; ^where^^^ோ௨ௌ௧^^^is the muting repetition factor.

[0118] Similar requirements are specified for other NR positioning measurements. Moreover, for the positioning tasks, a UE may need to get the downlink signals from multiple satellites. Also, there may be cases where a GEO satellite needs to support only positioning use cases (i.e., no data communication use cases). In these scenarios, there may not be an active user connected to the GEO cell, but the GEO cell still needs to be active just in case the UE is performing positioning functions.

[0119] This can create a dilemma: if there are no UEs needing to be in the RRC_CONNECTED state then it would be very costly, in terms of energy and use of spectrum, for an operator to keep the GEO cell on; but if the GEO cell is off, then remote UEs will are forced to search for a better cell, which may be very costly for UEs in terms of power consumption.

[0120] Thus, there would be a benefit for a UE that is only performing positioning tasks to be aware of when the serving GEO cell as well as neighboring GEO cells are on and off. Accordingly, techniques for handling DTX in GEO satellites with regards to positioning measurements and procedures are herein presented.

[0121] As described above, one option is to use information from SIB3, SIB31, and / or SIB32 to determine the ON and OFF period of the GEO cell. However, SIB3, SIB31, and SIB32 will not be able to provide information about neighbor satellites that may be participating in a positioning task. Also, positioning assistance data is very large in comparison to the radio resource management (RRM) neighbor cell list provided by mobility assistance QC2303210WOQualcomm Ref. No.2303210WO data; reading the SIBs before every positioning session and multiple times during the positioning session will have impact on the UE power. There are a number of ways to address this problem.

[0122] In some aspects, DTX of a GEO cell is not enabled for the positioning use cases (e.g., where there are positioning UEs, or UEs performing positioning tasks, being served by that GEO cell). In some aspects, the DTX mode is completely disabled, i.e., there is no OFF period. In some aspects, the DTX mode is enabled but the TRPs are still transmitting DL-PRS even during the OFF period.

[0123] Alternatively, DTX of a GEO cell is enabled even if positioning use cases are present, i.e., DL-PRS is not transmitted during the OFF periods, in which case the UE receives information about neighbor satellites. There are a number of ways that a UE can receive information about neighbor satellites:

[0124] In some aspects, a new positioning SIB (PosSIB) for enabling GEO cell DTX for positioning UEs is defined. In some aspects, the PosSIB contains all of the DTX information for neighbor cells, such that the UE need only decode the PosSIB to get all of the needed information. For brevity, this type of PosSIB is referred to herein as a “dedicated PosSIB”. In some aspects, the PosSIB contains neighbor cell information that isn’t already available in SIB3, SIB31, and SIB32, such that the UE must not only decode the PosSIB to get information about the neighbor cells but also decode RRM SIBs (e.g., SIB3, SIB31, and SIB32) to get information about the serving cell. For brevity, this type of PosSIB is referred to herein as a “differential PosSIB”.

[0125] In some aspects, a location server, such as a location management function (LMF), provides the ON / OFF information of each GEO satellite as part of assistance data, e.g., via a long term evolution (LTE) positioning protocol (LPP) message. Example parameters include, but are not limited to, a start offset in SFN (e.g., dtxOffset), a DTX cycle length (e.g., dtxPagingCycle), and a DTX off period (e.g., dtxOff), which may be a default configuration.

[0126] In some aspects, the assistance data may define two groups of GEO satellites, wherein a UE may presume that DTX is not enabled in GEO satellites in the first group, and the UE may presume that DTX is enabled in GEO satellites in the second group and that the UE needs additional information to measure the positioning signals from the GEO satellites in the second group. In some aspects, the UE may presume that any TRP for which the UE does not have DTX information will transmit DL-PRS signals according to the DL- QC2303210WOQualcomm Ref. No.2303210WO PRS configuration only. In some aspects, the assistance data may explicitly associate specific DTX data with multiple TRPs; in some aspects, DTX data associated with one TRP in a cell may be presumed to apply to all other TRPs listed in the same assistance data.

[0127] FIG. 5 is a signaling and event diagram illustrating signaling between a location server (LS) 172 and a base station (BS) 102, according to aspects of the disclosure. As shown in FIG. 5, at block 500, the LS 172 may request DTX information for a set of satellites. In some aspects, this may be implemented using a location server on-demand framework.

[0128] As further shown in FIG.5, at block 502, the BS 102 provides the requested information regarding DTX configurations. In some aspects, this response may include an indication that the DTX configurations are allowed to be changed or are not allowed to be changed.

[0129] As further shown in FIG. 5, at block 504, in the scenario where the DTX configurations are allowed to be changed, the LS 172 may suggest a change to one or more DTX configurations used by the BS 102. Examples of changes that the LS 172 make suggest include, but are not limited to, a change in offset, cycle period, ON or OFF duration, etc.

[0130] As further shown in FIG. 5, at block 506, the BS 102 may respond to the DTX configuration change request, e.g., to indicate whether the suggestion was accepted or rejected.

[0131] FIG. 6 is a signaling and event diagram illustrating signaling between a UE 104 and an LS 172, according to aspects of the disclosure. As shown in FIG.6, at block 600, the UE 104 may request DTX information from the LS 172.

[0132] As further shown in FIG.6, at block 602, the LS 172 may send a response to the request for DTX information to the UE 104. In some aspects, this response may specify DTX configuration information for the serving cell, for one or more neighbor cells, or a combination thereof.

[0133] As further shown in FIG. 6, at block 604, the UE 104 may request to use one or more DTX configurations for one or more satellites. In some aspects, the UE may request to activate or deactivate a DTX configuration of any cell, including GEO cells. In some aspects, the UE 104 may suggest a change to one or more of the DTX configurations.

[0134] As further shown in FIG. 6, at block 606, the LS 172 may send a response to the DTX configuration request. In some aspects, this response may indicate whether the request was accepted or rejected. For example, the LS 172 may indicate to the UE that its request QC2303210WOQualcomm Ref. No.2303210WO to use a particular DTX configuration was accepted or rejected. If rejected, the LS 172 may indicate to the UE another DTX configuration to use instead.

[0135] As further shown in FIG. 6, at block 608, the DTX information at the UE 104 may be updated dynamically, e.g., via radio resource control (RRC) configuration, assistance data from the LS 172. In this manner, the UE 104 may be kept up-to-date if a DTX configuration used by the serving cell or by a neighbor cell changes.

[0136] FIG. 7 is a signaling and event diagram illustrating signaling between a UE 104 and an BS 102, according to aspects of the disclosure. As shown in FIG.7, at block 700, the UE 104 may request DTX information from the BS 102.

[0137] As further shown in FIG.7, at block 702, the BS 102 may send a response to the request for DTX information to the UE 104. In some aspects, this response may specify DTX configuration information for the serving cell, for one or more neighbor cells, or a combination thereof.

[0138] As further shown in FIG. 7, at block 704, the UE 104 may request to use one or more DTX configurations for one or more satellites. In some aspects, the UE may request to activate or deactivate a DTX configuration of any cell, including GEO cells. In some aspects, the UE 104 may suggest a change to one or more of the DTX configurations.

[0139] As further shown in FIG. 7, at block 706, the BS 102 may send a response to the DTX configuration request. In some aspects, this response may indicate whether the request was accepted or rejected. For example, the BS 102 may indicate to the UE that its request to use a particular DTX configuration was accepted or rejected. If rejected, the BS 102 may indicate to the UE another DTX configuration to use instead.

[0140] As further shown in FIG. 7, at block 708, the DTX information at the UE 104 may be updated dynamically, e.g., via a medium access control (MAC) control element (CE), via downlink (DL) downlink control information (DCI), or via other means from the BS 102. In this manner, the UE 104 may be kept up-to-date if a DTX configuration used by the serving cell or by a neighbor cell changes.

[0141] In the scenario where a UE wants to perform a positioning task but all of the satellites (serving and neighbor) are in a DTX OFF condition, the UE will not be unable to perform that positioning task if the positioning measurement period does not take into account the DTX OFF timing. Thus, in some aspects, the positioning measurement period is defined to be longer if there are DL-PRS signals from any TRPs that have DTX enabled. QC2303210WOQualcomm Ref. No.2303210WO

[0142] In some aspects, the equations eq.1 and eq.2 for determining measurement period lengthTୗ^ୈ,^୭^ୟ୪, listed above, are modified to include the DTX time in the measurement periodcalculation. An example modification is shown below, with changes in bold font: •the least common multiple between the configured periodicities^^ோௌ,^and^^ோ^, ^^^^. •^^ோ^is the DRX cycle of the UE in the serving cell. • Tୈ்^is a DTX factor related to the DTX of the TRPs. Tୈ்^may correspond to the LCM of the T^ୈ்^wherein the T^ୈ்^is the DTX period configured for the jthTRP of the PFL.

[0143] In some aspects, a PFL may be associated with a single DTX configuration and may not be allowed to have different TRPs having different DTX configurations. For example, one TRP in a PFL may have a DTX period of 20ms while another TRP in the PFL may have a DTX period of 40ms. In this scenario, the location server may choose the LCM of 20ms and 40ms (i.e., 40ms) and indicate to the UE that it should measure every 40ms. That is, the DTX configuration given to the UE would indicate 40ms for all TRPs in the PFL.

[0144] It is noted that the techniques described herein can be applied not only to any satellite DTX cell but also to terrestrial network DTX cells (e.g., in the “green network” use case).

[0145] FIG. 8A through FIG 8C are flowcharts illustrating portions of aa method 800 that may be performed by a UE when the UE is aware that DTX is enabled for a GEO cell but does not know the exact configuration, according to aspects of the disclosure. When DTX is enabled, because the cell is not transmitting, the UE will have all noise in the channel energy response, causing the signal to noise ratio (SNR) to be very low. In conventional networks, the UE will remove this satellite from further measurement operations if the peak SNR is below some threshold. However, if the UE is aware that the satellite has DTX enabled but does not know the exact configuration, the UE may do one or more of the following.

[0146] As shown in FIG.4A, at block 802, the UE determines that the cell is operating according to a DTX configuration that is not known by the UE. For example, the UE may notice that the cell is not transmitting DL signals in places where such signals are expected. QC2303210WOQualcomm Ref. No.2303210WO

[0147] As further shown in FIG.4A, at block 804, the UE determines the DTX configuration of the cell. Examples of how this may be done are described in more detail in FIG.8B and FIG.8C.

[0148] As further shown in FIG. 4A, at block 806, the UE performs a positioning operation according to the now-determined DTX configuration.

[0149] FIG.8B illustrates one technique by which the UE may determine the DTX configuration of the cell, according to aspects of the disclosure. As shown in FIG.8B, at block 808, the UE may try to decode the satellite at random or UE-defined periodic intervals. As shown in FIG. 8B, at block 810, the UE may then analyze the results of the multiple decoding attempts to try to determine the timing and duration of the DTX ON mode. From that, the UE can then calculate other parameters such as the DTX offset and period timings.

[0150] FIG. 8C illustrates another technique by which the UE may determine the DTX configuration of the cell, according to aspects of the disclosure. FIG.8C shows a scenario in which the UE may participate in crowdsourcing of the DTX configuration. As shown in FIG. 8C, at block 812, the UE (and other UEs) may contribute information to a database, such as an over-the-top (OTT) crowdsourcing server, for example. The information collected may be analyzed by the server to determine information about the DTX configuration, such as its offset, periodicity, and ON and / or OFF durations, which then may be stored in the database. This information may then be shared with other UEs that request such information. For example, as shown in FIG. 8C, at block 814, the UE receives, from the database, the DTX configuration for the cell.

[0151] FIG. 9 is a flowchart of an example process 900 associated with PRS measurement and signaling for cell DTX in NR, according to aspects of the disclosure. In some implementations, one or more process blocks of FIG.9 may be performed by a UE (e.g., UE 104). In some implementations, one or more process blocks of FIG. 9 may be performed by another device or a group of devices separate from or including the UE. Additionally, or alternatively, one or more process blocks of FIG.9 may be performed by one or more components of UE 302, such as processor(s) 332, memory 340, WWAN transceiver(s) 310, short-range wireless transceiver(s) 320, satellite signal receiver 330, sensor(s) 344, user interface 346, and positioning module 342, any or all of which may be means for performing the operations of process 900.

[0152] As shown in FIG. 9, process 900 may include, at block 910, sending, to a first entity comprising a base station, a location server, or both, a request for DTX configuration QC2303210WOQualcomm Ref. No.2303210WO information. Means for performing the operation of block 910 may include the processor(s) 332, memory 340, or WWAN transceiver(s) 310 of the UE 302. For example, the UE 302 may send the request using the transmitter(s) 314.

[0153] As further shown in FIG. 9, process 900 may include, at block 920, receiving, from the first entity, DTX configuration information comprising a DTX configuration for at least one TRP. Means for performing the operation of block 920 may include the processor(s) 332, memory 340, or WWAN transceiver(s) 310 of the UE 302. For example, the UE 302 may receive the DTX configuration information using the receiver(s) 312.

[0154] As further shown in FIG. 9, process 900 may include, at block 930, performing a positioning operation according to the DTX configuration information. Means for performing the operation of block 930 may include the processor(s) 332, memory 340, or WWAN transceiver(s) 310 of the UE 302. For example, the UE 302 may perform a positioning operation according to the DTX configuration, using the transceiver(s) 310, the processor(s) 332, and the memory 340.

[0155] In some aspects, receiving the DTX configuration information comprises receiving a DTX configuration for at least one GEO cell.

[0156] In some aspects, receiving the DTX configuration information comprises receiving a positioning system information block (PosSIB) comprising a DTX configuration for at least one neighbor TRP.

[0157] In some aspects, the PosSIB further comprises a DTX configuration for the serving TRP.

[0158] In some aspects, process 900 includes receiving at least one non-positioning SIB comprising a DTX configuration for the serving TRP.

[0159] In some aspects, process 900 includes sending, to the first entity, a DTX configuration request, receiving, from the first entity, a response to the DTX configuration request, and changing the DTX configuration according to the response to the DTX configuration request.

[0160] In some aspects, the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX configuration, change a duration of the ON time of a DTX configuration, change a duration of the OFF time of a DTX configuration, or a combination thereof. QC2303210WOQualcomm Ref. No.2303210WO

[0161] In some aspects, process 900 includes receiving, from the first entity, a notification of a change to the DTX configuration for a TRP, and performing a positioning operation according to the change to the DTX configuration for the TRP.

[0162] In some aspects, the notification of the change of the DTX configuration for the TRP is received as assistance data, via a radio resource control (RRC) message, via a medium access control (MAC) control element (CE), via downlink (DL) downlink control information (DCI), via a long term evolution (LTE) positioning protocol (LPP) message, or via a combination thereof.

[0163] In some aspects, process 900 includes determining that the positioning operation comprises measuring downlink positioning reference signals from at least one TRP with DTX enabled, and increasing the length of a positioning measurement period based at least in part on a DTX period of the at least one TRP with DTX enabled.

[0164] Process 900 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in connection with one or more other processes described elsewhere herein. Although FIG.9 shows example blocks of process 900, in some implementations, process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG. 9. Additionally, or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0165] FIG.10 is a flowchart of an example process 1000 associated with PRS measurement and signaling for cell DTX in NR, according to aspects of the disclosure. In some implementations, one or more process blocks of FIG.10 may be performed by a location server (e.g., location server 172 or 230, LMF 270). In some implementations, one or more process blocks of FIG.10 may be performed by another device or a group of devices separate from or including the location server. Additionally, or alternatively, one or more process blocks of FIG. 10 may be performed by one or more components of network entity 306, such as processor(s) 394, memory 396, network transceiver(s) 390, and positioning module 398, any or all of which may be means for performing the operations of process 1000.

[0166] As shown in FIG.10, process 1000 may include, at block 1010, sending, to a base station, a request for DTX configuration information. Means for performing the operation of block 1010 may include the processor(s), memory, or transceiver(s) of any of the QC2303210WOQualcomm Ref. No.2303210WO apparatuses described herein. For example, the location server may send the request using the network transceiver(s) 390.

[0167] As further shown in FIG. 10, process 1000 may include, at block 1020, receiving, from the base station, DTX configuration information comprising a DTX configuration for at least one TRP. Means for performing the operation of block 1020 may include the processor(s), memory, or transceiver(s) of any of the apparatuses described herein. For example, the location server may receive the DTX configuration information using the network transceiver(s) 390.

[0168] In some aspects, receiving the DTX configuration information comprises receiving a DTX configuration for at least one GEO cell.

[0169] In some aspects, process 1000 includes sending, to the base station, a DTX configuration request, and receiving, from the base station, a response to the DTX configuration request.

[0170] In some aspects, the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX configuration, change a duration of the ON time of a DTX configuration, change a duration of the OFF time of a DTX configuration, or a combination thereof.

[0171] In some aspects, process 1000 includes receiving, from a UE, a request for DTX configuration information, and sending, to the UE, assistance data comprising the DTX configuration information.

[0172] In some aspects, process 1000 includes determining a change to the DTX configuration for a TRP, and sending, to the UE, a notification of the change of the DTX configuration for the TRP.

[0173] Process 1000 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in connection with one or more other processes described elsewhere herein. Although FIG. 10 shows example blocks of process 1000, in some implementations, process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG.10. Additionally, or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0174] FIG.11 is a flowchart of an example process 1100 associated with PRS measurement and signaling for cell DTX in NR, according to aspects of the disclosure. In some implementations, one or more process blocks of FIG. 11 may be performed by a base QC2303210WOQualcomm Ref. No.2303210WO station (e.g., base station 102). In some implementations, one or more process blocks of FIG. 11 may be performed by another device or a group of devices separate from or including the base station. Additionally, or alternatively, one or more process blocks of FIG. 11 may be performed by one or more components of BS 304, such as processor(s) 384, memory 386, WWAN transceiver(s) 350, short-range wireless transceiver(s) 360, satellite signal receiver 370, network transceiver(s) 380, and positioning module 388, any or all of which may be means for performing the operations of process 1100.

[0175] As shown in FIG. 11, process 1100 may include, at block 1110, receiving, from a first entity, a request for DTX configuration information. Means for performing the operation of block 1110 may include the processor(s) 384, memory 386, or WWAN transceiver(s) 350 of the BS 304. For example, the base station 304 may receive the request for DTX configuration information, using the receiver(s) 352 or the network transceiver(s) 380.

[0176] As further shown in FIG. 11, process 1100 may include, at block 1120, sending, to the first entity, DTX configuration information comprising a DTX configuration for at least one TRP. Means for performing the operation of block 1120 may include the processor(s) 384, memory 386, or WWAN transceiver(s) 350 of the BS 304. For example, the base station 304 may send the DTX configuration information, using the transmitter(s) 354 or the network transceiver(s) 380.

[0177] In some aspects, sending the DTX configuration information comprises sending a DTX configuration for at least one GEO cell.

[0178] In some aspects, sending the DTX configuration information comprises sending a positioning system information block (PosSIB) comprising a DTX configuration for at least one neighbor TRP.

[0179] In some aspects, the PosSIB further comprises a DTX configuration for the serving TRP.

[0180] In some aspects, process 1100 further includes sending at least one non-positioning SIB comprising a DTX configuration for the serving TRP.

[0181] In some aspects, process 1100 further includes receiving, from the first entity, a DTX configuration request, and sending, to the first entity, a response to the DTX configuration request.

[0182] In some aspects, the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX configuration, change a duration QC2303210WOQualcomm Ref. No.2303210WO of the ON time of a DTX configuration, change a duration of the OFF time of a DTX configuration, or a combination thereof.

[0183] In some aspects, process 1100 further includes determining a change to the DTX configuration for a TRP, and sending, to the UE, a notification of the change to the DTX configuration for the TRP.

[0184] In some aspects, process 1100 further includes, while a DTX mode is active, either suppressing all transmissions by the TRP during DTX OFF time, or suppressing all transmissions by the TRP except transmissions of downlink positioning reference signals (DL-PRS) during DTX OFF time, according to the DTX configuration.

[0185] Process 1100 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in connection with one or more other processes described elsewhere herein. Although FIG. 11 shows example blocks of process 1100, in some implementations, process 1100 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG.11. Additionally, or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0186] FIG.12 is a flowchart of an example process 1200 associated with PRS measurement and signaling for cell DTX in NR, according to aspects of the disclosure. In some implementations, one or more process blocks of FIG.12 may be performed by a UE (e.g., UE 104). In some implementations, one or more process blocks of FIG. 12 may be performed by another device or a group of devices separate from or including the UE. Additionally, or alternatively, one or more process blocks of FIG. 12 may be performed by one or more components of UE 302, such as processor(s) 332, memory 340, WWAN transceiver(s) 310, short-range wireless transceiver(s) 320, satellite signal receiver 330, sensor(s) 344, user interface 346, and positioning module 342, any or all of which may be means for performing the operations of process 1200.

[0187] As shown in FIG.12, process 1200 may include, at block 1210, determining that a cell is operating according to a DTX configuration that is not known by the UE. Means for performing the operation of block 1210 may include the processor(s) 332, memory 340, or WWAN transceiver(s) 310 of the UE 302. For example, the UE 302 may determine that a cell is operating according to a DTX configuration that is not known by the UE by detecting that scheduled DL transmissions from the cell are not being received by the receiver(s) 312. QC2303210WOQualcomm Ref. No.2303210WO

[0188] As further shown in FIG. 12, process 1200 may include, at block 1220, determining the DTX configuration of the cell. Means for performing the operation of block 1220 may include the processor(s) 332, memory 340, or WWAN transceiver(s) 310 of the UE 302. For example, the UE 302 may determine the DTX configuration of the cell, using the WWAN transceiver(s) 310, the processor(s) 332, and the memory 340, as explained in more detail below.

[0189] As further shown in FIG. 12, process 1200 may include, at block 1230, performing a positioning operation according to the DTX configuration. Means for performing the operation of block 1230 may include the processor(s) 332, memory 340, or WWAN transceiver(s) 310 of the UE 302. For example, the UE 302 may perform a positioning operation according to the DTX configuration, using he WWAN transceiver(s) 310, the processor(s) 332, and the memory 340.

[0190] In some aspects, determining that the cell is operating according to a DTX configuration that is not known by the UE comprises determining that a GEO cell is operating according to a DTX configuration that is not known by the UE.

[0191] In some aspects, determining the DTX configuration of the cell comprises attempting to decode downlink transmissions from the cell at random intervals or according to a UE- defined periodic interval, and calculating the DTX configuration of the cell based on the results of the attempts to decode the downlink transmissions from the cell.

[0192] In some aspects, calculating the DTX configuration of the cell comprises calculating DTX ON time durations based on timings of successful attempts to decode downlink transmissions from the cell and calculating a DTX start timing offset and a DTX cycle period based on start and stop times of the DTX ON time durations.

[0193] In some aspects, calculating the DTX configuration of the cell based on results of attempts to decode downlink transmissions from the cell comprises providing the results of attempts to decode downlink transmissions from the cell to a database, and receiving, from the database, the DTX configuration of the cell.

[0194] In some aspects, the results of attempts to decode downlink transmissions from the cell are provided to the database via an over-the-top (OTT) signaling path.

[0195] In some aspects, the database is a crowdsourced database.

[0196] Process 1200 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in connection with one or more other processes described elsewhere herein. Although FIG. 12 shows example QC2303210WOQualcomm Ref. No.2303210WO blocks of process 1200, in some implementations, process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in FIG.12. Additionally, or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0197] In the detailed description above it can be seen that different features are grouped together in examples. This manner of disclosure should not be understood as an intention that the example clauses have more features than are explicitly mentioned in each clause. Rather, the various aspects of the disclosure may include fewer than all features of an individual example clause disclosed. Therefore, the following clauses should hereby be deemed to be incorporated in the description, wherein each clause by itself can stand as a separate example. Although each dependent clause can refer in the clauses to a specific combination with one of the other clauses, the aspect(s) of that dependent clause are not limited to the specific combination. It will be appreciated that other example clauses can also include a combination of the dependent clause aspect(s) with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations, unless it is explicitly expressed or can be readily inferred that a specific combination is not intended (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Furthermore, it is also intended that aspects of a clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0198] Implementation examples are described in the following numbered clauses:

[0199] Clause 1. A method of wireless communication performed by a user equipment (UE), the method comprising: sending, to a first entity comprising a base station, a location server, or both, a request for DTX configuration information; receiving, from the first entity, DTX configuration information comprising a DTX configuration for at least one transmission / reception point (TRP); and performing a positioning operation according to the DTX configuration information.

[0200] Clause 2. The method of clause 1, wherein receiving the DTX configuration information comprises receiving a DTX configuration for at least one geosynchronous (GEO) cell.

[0201] Clause 3. The method of any of clauses 1 to 2, wherein receiving the DTX configuration information comprises receiving a positioning system information block (PosSIB) comprising a DTX configuration for at least one neighbor TRP. QC2303210WOQualcomm Ref. No.2303210WO

[0202] Clause 4. The method of clause 3, wherein the PosSIB further comprises a DTX configuration for a serving TRP.

[0203] Clause 5. The method of any of clauses 3 to 4, further comprising receiving at least one non-positioning SIB comprising a DTX configuration for a serving TRP.

[0204] Clause 6. The method of any of clauses 1 to 5, further comprising: sending, to the first entity, a DTX configuration request; receiving, from the first entity, a response to the DTX configuration request; and changing a DTX configuration according to the response to the DTX configuration request.

[0205] Clause 7. The method of clause 6, wherein the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX configuration, change a duration of an ON time of a DTX configuration, change a duration of an OFF time of a DTX configuration, or a combination thereof.

[0206] Clause 8. The method of any of clauses 1 to 7, further comprising: receiving, from the first entity, a notification of a change to the DTX configuration for a TRP; and performing a positioning operation according to the change to the DTX configuration for the TRP.

[0207] Clause 9. The method of clause 8, wherein the notification of the change to the DTX configuration for the TRP is received as assistance data, via a radio resource control (RRC) message, via a medium access control (MAC) control element (CE), via downlink (DL) downlink control information (DCI), via a long term evolution (LTE) positioning protocol (LPP) message, or via a combination thereof.

[0208] Clause 10. The method of any of clauses 1 to 9, further comprising: determining that the positioning operation comprises measuring downlink positioning reference signals from at least one TRP with DTX enabled; and increasing a length of a positioning measurement period based at least in part on a DTX period of the at least one TRP with DTX enabled.

[0209] Clause 11. A method of wireless communication performed by a location server, the method comprising: sending, to a base station, a request for DTX configuration information; and receiving, from the base station, DTX configuration information comprising a DTX configuration for at least one transmission / reception point (TRP).

[0210] Clause 12. The method of clause 11, wherein receiving the DTX configuration information comprises receiving a DTX configuration for at least one geosynchronous (GEO) cell. QC2303210WOQualcomm Ref. No.2303210WO

[0211] Clause 13. The method of any of clauses 11 to 12, further comprising: sending, to the base station, a DTX configuration request; and receiving, from the base station, a response to the DTX configuration request.

[0212] Clause 14. The method of clause 13, wherein the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX configuration, change a duration of an ON time of a DTX configuration, change a duration of an OFF time of a DTX configuration, or a combination thereof.

[0213] Clause 15. The method of any of clauses 11 to 14, further comprising: receiving, from a user equipment (UE), a request for DTX configuration information; and sending, to the UE, assistance data comprising the DTX configuration information.

[0214] Clause 16. The method of clause 15, further comprising: determining a change to the DTX configuration for a TRP; and sending, to the UE, a notification of the change to the DTX configuration for the TRP.

[0215] Clause 17. A method of wireless communication performed by a base station, the method comprising: receiving, from a first entity, a request for DTX configuration information; and sending, to the first entity, DTX configuration information comprising a DTX configuration for at least one transmission / reception point (TRP).

[0216] Clause 18. The method of clause 17, wherein sending the DTX configuration information comprises sending a DTX configuration for at least one geosynchronous (GEO) cell.

[0217] Clause 19. The method of any of clauses 17 to 18, wherein sending the DTX configuration information comprises sending a positioning system information block (PosSIB) comprising a DTX configuration for at least one neighbor TRP.

[0218] Clause 20. The method of clause 19, wherein the PosSIB further comprises a DTX configuration for a serving TRP.

[0219] Clause 21. The method of any of clauses 19 to 20, further comprising sending at least one non-positioning SIB comprising a DTX configuration for a serving TRP.

[0220] Clause 22. The method of any of clauses 17 to 21, further comprising: receiving, from the first entity, a DTX configuration request; and sending, to the first entity, a response to the DTX configuration request.

[0221] Clause 23. The method of clause 22, wherein the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX QC2303210WOQualcomm Ref. No.2303210WO configuration, change a duration of an ON time of a DTX configuration, change a duration of an OFF time of a DTX configuration, or a combination thereof.

[0222] Clause 24. The method of any of clauses 17 to 23, further comprising: determining a change to the DTX configuration for a TRP; and sending, to a UE, a notification of the change to the DTX configuration for the TRP.

[0223] Clause 25. The method of any of clauses 17 to 24, further comprising, while a DTX mode is active, either suppressing all transmissions by the TRP during DTX OFF time or suppressing all transmissions by the TRP except transmissions of downlink positioning reference signals (DL-PRS) during DTX OFF time, according to the DTX configuration.

[0224] Clause 26. A method of wireless communication performed by a user equipment (UE), the method comprising: determining that a cell is operating according to a DTX configuration that is not known by the UE; determining the DTX configuration of the cell; and performing a positioning operation according to the DTX configuration.

[0225] Clause 27. The method of clause 26, wherein determining that the cell is operating according to a DTX configuration that is not known by the UE comprises determining that a geosynchronous (GEO) cell is operating according to a DTX configuration that is not known by the UE.

[0226] Clause 28. The method of any of clauses 26 to 27, wherein determining the DTX configuration of the cell comprises: attempting to decode downlink transmissions from the cell at random intervals or according to a UE-defined periodic interval; and calculating the DTX configuration of the cell based on results of the attempts to decode downlink transmissions from the cell.

[0227] Clause 29. The method of clause 28, wherein calculating the DTX configuration of the cell comprises calculating DTX ON time durations based on timings of successful attempts to decode downlink transmissions from the cell and calculating a DTX start timing offset and a DTX cycle period based on start and stop times of the DTX ON time durations.

[0228] Clause 30. The method of any of clauses 28 to 29, wherein calculating the DTX configuration of the cell based on results of attempts to decode downlink transmissions from the cell comprises: providing the results of attempts to decode downlink transmissions from the cell to a database; and receiving, from the database, the DTX configuration of the cell. QC2303210WOQualcomm Ref. No.2303210WO

[0229] Clause 31. The method of clause 30, wherein the results of attempts to decode downlink transmissions from the cell are provided to the database via an over-the-top (OTT) signaling path.

[0230] Clause 32. The method of any of clauses 30 to 31, wherein the database is a crowdsourced database.

[0231] Clause 33. A user equipment (UE), comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: send, to a first entity comprising a base station, a location server, or both, via the one or more transceivers, a request for DTX configuration information; receive, from the first entity via the one or more transceivers, DTX configuration information comprising a DTX configuration for at least one transmission / reception point (TRP); and perform a positioning operation according to the DTX configuration information.

[0232] Clause 34. The UE of clause 33, wherein, to receive the DTX configuration information, the one or more processors, either alone or in combination, are configured to receive a DTX configuration for at least one geosynchronous (GEO) cell.

[0233] Clause 35. The UE of any of clauses 33 to 34, wherein, to receive the DTX configuration information, the one or more processors, either alone or in combination, are configured to receive a positioning system information block (PosSIB) comprising a DTX configuration for at least one neighbor TRP.

[0234] Clause 36. The UE of clause 35, wherein the PosSIB further comprises a DTX configuration for a serving TRP.

[0235] Clause 37. The UE of any of clauses 35 to 36, wherein the one or more processors, either alone or in combination, are further configured to receive, via the one or more transceivers, at least one non-positioning SIB comprising a DTX configuration for a serving TRP.

[0236] Clause 38. The UE of any of clauses 33 to 37, wherein the one or more processors, either alone or in combination, are further configured to: send, to the first entity via the one or more transceivers, a DTX configuration request; receive, from the first entity via the one or more transceivers, a response to the DTX configuration request; and change a DTX configuration according to the response to the DTX configuration request. QC2303210WOQualcomm Ref. No.2303210WO

[0237] Clause 39. The UE of clause 38, wherein the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX configuration, change a duration of an ON time of a DTX configuration, change a duration of an OFF time of a DTX configuration, or a combination thereof.

[0238] Clause 40. The UE of any of clauses 33 to 39, wherein the one or more processors, either alone or in combination, are further configured to: receive, from the first entity via the one or more transceivers, a notification of a change to the DTX configuration for a TRP; and perform a positioning operation according to the change to the DTX configuration for the TRP.

[0239] Clause 41. The UE of clause 40, wherein the notification of the change to the DTX configuration for the TRP is received as assistance data, via a radio resource control (RRC) message, via a medium access control (MAC) control element (CE), via downlink (DL) downlink control information (DCI), via a long term evolution (LTE) positioning protocol (LPP) message, or via a combination thereof.

[0240] Clause 42. The UE of any of clauses 33 to 41, wherein the one or more processors, either alone or in combination, are further configured to: determine that the positioning operation comprises measuring downlink positioning reference signals from at least one TRP with DTX enabled; and increase a length of a positioning measurement period based at least in part on a DTX period of the at least one TRP with DTX enabled.

[0241] Clause 43. A location server (LS), comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: send, to a base station via the one or more transceivers, a request for DTX configuration information; and receive, from the base station via the one or more transceivers, DTX configuration information comprising a DTX configuration for at least one transmission / reception point (TRP).

[0242] Clause 44. The LS of clause 43, wherein, to receive the DTX configuration information, the one or more processors, either alone or in combination, are configured to receive a DTX configuration for at least one geosynchronous (GEO) cell.

[0243] Clause 45. The LS of any of clauses 43 to 44, wherein the one or more processors, either alone or in combination, are further configured to: send, to the base station via the one or QC2303210WOQualcomm Ref. No.2303210WO more transceivers, a DTX configuration request; and receive, from the base station via the one or more transceivers, a response to the DTX configuration request.

[0244] Clause 46. The LS of clause 45, wherein the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX configuration, change a duration of an ON time of a DTX configuration, change a duration of an OFF time of a DTX configuration, or a combination thereof.

[0245] Clause 47. The LS of any of clauses 43 to 46, wherein the one or more processors, either alone or in combination, are further configured to: receive, from a user equipment (UE) via the one or more transceivers, a request for DTX configuration information; and send, to the UE via the one or more transceivers, assistance data comprising the DTX configuration information.

[0246] Clause 48. The LS of clause 47, wherein the one or more processors, either alone or in combination, are further configured to: determine a change to the DTX configuration for a TRP; and send, to the UE via the one or more transceivers, a notification of the change to the DTX configuration for the TRP.

[0247] Clause 49. A base station (BS), comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: receive, from a first entity via the one or more transceivers, a request for DTX configuration information; and send, to the first entity via the one or more transceivers, DTX configuration information comprising a DTX configuration for at least one transmission / reception point (TRP).

[0248] Clause 50. The BS of clause 49, wherein, to send the DTX configuration information, the one or more processors, either alone or in combination, are configured to send a DTX configuration for at least one geosynchronous (GEO) cell.

[0249] Clause 51. The BS of any of clauses 49 to 50, wherein, to send the DTX configuration information, the one or more processors, either alone or in combination, are configured to send a positioning system information block (PosSIB) comprising a DTX configuration for at least one neighbor TRP.

[0250] Clause 52. The BS of clause 51, wherein the PosSIB further comprises a DTX configuration for a serving TRP. QC2303210WOQualcomm Ref. No.2303210WO

[0251] Clause 53. The BS of any of clauses 51 to 52, wherein the one or more processors, either alone or in combination, are further configured to send, via the one or more transceivers, at least one non-positioning SIB comprising a DTX configuration for a serving TRP.

[0252] Clause 54. The BS of any of clauses 49 to 53, wherein the one or more processors, either alone or in combination, are further configured to: receive, from the first entity via the one or more transceivers, a DTX configuration request; and send, to the first entity via the one or more transceivers, a response to the DTX configuration request.

[0253] Clause 55. The BS of clause 54, wherein the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX configuration, change a duration of an ON time of a DTX configuration, change a duration of an OFF time of a DTX configuration, or a combination thereof.

[0254] Clause 56. The BS of any of clauses 49 to 55, wherein the one or more processors, either alone or in combination, are further configured to: determine a change to the DTX configuration for a TRP; and send, to a user equipment (UE) via the one or more transceivers, a notification of the change to the DTX configuration for the TRP.

[0255] Clause 57. The BS of any of clauses 49 to 56, wherein the one or more processors, either alone or in combination, are further configured to, while a DTX mode is active, either suppress all transmissions by the TRP during DTX OFF time or suppress all transmissions by the TRP except transmissions of downlink positioning reference signals (DL-PRS) during DTX OFF time, according to the DTX configuration.

[0256] Clause 58. A user equipment (UE), comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: determine that a cell is operating according to a DTX configuration that is not known by the UE; determine the DTX configuration of the cell; and perform a positioning operation according to the DTX configuration.

[0257] Clause 59. The UE of clause 58, wherein, to determine that the cell is operating according to a DTX configuration that is not known by the UE, the one or more processors, either alone or in combination, are configured to determine that a geosynchronous (GEO) cell is operating according to a DTX configuration that is not known by the UE.

[0258] Clause 60. The UE of any of clauses 58 to 59, wherein, to determine the DTX configuration of the cell, the one or more processors, either alone or in combination, are QC2303210WOQualcomm Ref. No.2303210WO configured to: attempt to decode downlink transmissions from the cell at random intervals or according to a UE-defined periodic interval; and calculate the DTX configuration of the cell based on results of the attempts to decode downlink transmissions from the cell.

[0259] Clause 61. The UE of clause 60, wherein, to calculate the DTX configuration of the cell, the one or more processors, either alone or in combination, are configured to calculate DTX ON time durations based on timings of successful attempts to decode downlink transmissions from the cell and to calculate a DTX start timing offset and a DTX cycle period based on start and stop times of the DTX ON time durations.

[0260] Clause 62. The UE of any of clauses 60 to 61, wherein, to calculate the DTX configuration of the cell based on results of attempts to decode downlink transmissions from the cell, the one or more processors, either alone or in combination, are configured to: provide the results of attempts to decode downlink transmissions from the cell to a database; and receive, from the database, the DTX configuration of the cell.

[0261] Clause 63. The UE of clause 62, wherein the results of attempts to decode downlink transmissions from the cell are provided to the database via an over-the-top (OTT) signaling path.

[0262] Clause 64. The UE of any of clauses 62 to 63, wherein the database is a crowdsourced database.

[0263] Clause 65. An apparatus comprising a memory, a transceiver, and a processor communicatively coupled to the memory and the transceiver, the memory, the transceiver, and the processor configured to perform a method according to any of clauses 1 to 32.

[0264] Clause 66. An apparatus comprising means for performing a method according to any of clauses 1 to 32.

[0265] Clause 67. A non-transitory computer-readable medium storing computer-executable instructions, the computer-executable comprising at least one instruction for causing a computer or processor to perform a method according to any of clauses 1 to 32.

[0266] Those of skill in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. QC2303210WOQualcomm Ref. No.2303210WO

[0267] Further, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0268] 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 digital signal processor (DSP), an ASIC, a field-programable gate array (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 general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. 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.

[0269] 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. An example storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., QC2303210WOQualcomm Ref. No.2303210WO UE). In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

[0270] In one or more example aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. 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. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. 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. Combinations of the above should also be included within the scope of computer-readable media.

[0271] While the foregoing disclosure shows illustrative aspects of the disclosure, it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps and / or actions of the method claims in accordance with the aspects of the disclosure described herein need not be performed in any particular order. Furthermore, although elements of the disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. QC2303210WO

Claims

Qualcomm Ref. No.2303210WO CLAIMS What is claimed is:

1. A method of wireless communication performed by a user equipment (UE), the method comprising: sending, to a first entity comprising a base station, a location server, or both, a request for DTX configuration information; receiving, from the first entity, DTX configuration information comprising a DTX configuration for at least one transmission / reception point (TRP); and performing a positioning operation according to the DTX configuration information.

2. The method of claim 1, wherein receiving the DTX configuration information comprises receiving a DTX configuration for at least one geosynchronous (GEO) cell.

3. The method of claim 1, wherein receiving the DTX configuration information comprises receiving a positioning system information block (PosSIB) comprising a DTX configuration for at least one neighbor TRP.

4. The method of claim 3, wherein the PosSIB further comprises a DTX configuration for a serving TRP.

5. The method of claim 3, further comprising receiving at least one non-positioning SIB comprising a DTX configuration for a serving TRP.

6. The method of claim 1, further comprising: sending, to the first entity, a DTX configuration request; receiving, from the first entity, a response to the DTX configuration request; and changing a DTX configuration according to the response to the DTX configuration request.

7. The method of claim 6, wherein the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX QC2303210WOQualcomm Ref. No.2303210WO configuration, change a duration of an ON time of a DTX configuration, change a duration of an OFF time of a DTX configuration, or a combination thereof.

8. The method of claim 1, further comprising: receiving, from the first entity, a notification of a change to the DTX configuration for a TRP; and performing a positioning operation according to the change to the DTX configuration for the TRP.

9. The method of claim 8, wherein the notification of the change to the DTX configuration for the TRP is received as assistance data, via a radio resource control (RRC) message, via a medium access control (MAC) control element (CE), via downlink (DL) downlink control information (DCI), via a long term evolution (LTE) positioning protocol (LPP) message, or via a combination thereof.

10. The method of claim 1, further comprising: determining that the positioning operation comprises measuring downlink positioning reference signals from at least one TRP with DTX enabled; and increasing a length of a positioning measurement period based at least in part on a DTX period of the at least one TRP with DTX enabled.

11. A method of wireless communication performed by a location server, the method comprising: sending, to a base station, a request for DTX configuration information; and receiving, from the base station, DTX configuration information comprising a DTX configuration for at least one transmission / reception point (TRP).

12. The method of claim 11, wherein receiving the DTX configuration information comprises receiving a DTX configuration for at least one geosynchronous (GEO) cell.

13. The method of claim 11, further comprising: sending, to the base station, a DTX configuration request; and receiving, from the base station, a response to the DTX configuration request. QC2303210WOQualcomm Ref. No.2303210WO 14. The method of claim 13, wherein the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX configuration, change a duration of an ON time of a DTX configuration, change a duration of an OFF time of a DTX configuration, or a combination thereof.

15. The method of claim 11, further comprising: receiving, from a user equipment (UE), a request for DTX configuration information; and sending, to the UE, assistance data comprising the DTX configuration information.

16. The method of claim 15, further comprising: determining a change to the DTX configuration for a TRP; and sending, to the UE, a notification of the change to the DTX configuration for the TRP.

17. A method of wireless communication performed by a base station, the method comprising: receiving, from a first entity, a request for DTX configuration information; and sending, to the first entity, DTX configuration information comprising a DTX configuration for at least one transmission / reception point (TRP).

18. The method of claim 17, wherein sending the DTX configuration information comprises sending a DTX configuration for at least one geosynchronous (GEO) cell.

19. The method of claim 17, wherein sending the DTX configuration information comprises sending a positioning system information block (PosSIB) comprising a DTX configuration for at least one neighbor TRP.

20. The method of claim 19, wherein the PosSIB further comprises a DTX configuration for a serving TRP. QC2303210WOQualcomm Ref. No.2303210WO 21. The method of claim 19, further comprising sending at least one non-positioning SIB comprising a DTX configuration for a serving TRP.

22. The method of claim 17, further comprising: receiving, from the first entity, a DTX configuration request; and sending, to the first entity, a response to the DTX configuration request.

23. The method of claim 22, wherein the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX configuration, change a duration of an ON time of a DTX configuration, change a duration of an OFF time of a DTX configuration, or a combination thereof.

24. The method of claim 17, further comprising: determining a change to the DTX configuration for a TRP; and sending, to a UE, a notification of the change to the DTX configuration for the TRP.

25. The method of claim 17, further comprising, while a DTX mode is active, either suppressing all transmissions by the TRP during DTX OFF time or suppressing all transmissions by the TRP except transmissions of downlink positioning reference signals (DL-PRS) during DTX OFF time, according to the DTX configuration.

26. A method of wireless communication performed by a user equipment (UE), the method comprising: determining that a cell is operating according to a DTX configuration that is not known by the UE; determining the DTX configuration of the cell; and performing a positioning operation according to the DTX configuration.

27. The method of claim 26, wherein determining that the cell is operating according to a DTX configuration that is not known by the UE comprises determining QC2303210WOQualcomm Ref. No.2303210WO that a geosynchronous (GEO) cell is operating according to a DTX configuration that is not known by the UE.

28. The method of claim 26, wherein determining the DTX configuration of the cell comprises: attempting to decode downlink transmissions from the cell at random intervals or according to a UE-defined periodic interval; and calculating the DTX configuration of the cell based on results of the attempts to decode downlink transmissions from the cell.

29. The method of claim 28, wherein calculating the DTX configuration of the cell comprises calculating DTX ON time durations based on timings of successful attempts to decode downlink transmissions from the cell and calculating a DTX start timing offset and a DTX cycle period based on start and stop times of the DTX ON time durations.

30. The method of claim 28, wherein calculating the DTX configuration of the cell based on results of attempts to decode downlink transmissions from the cell comprises: providing the results of attempts to decode downlink transmissions from the cell to a database; and receiving, from the database, the DTX configuration of the cell.

31. The method of claim 30, wherein the results of attempts to decode downlink transmissions from the cell are provided to the database via an over-the-top (OTT) signaling path.

32. The method of claim 30, wherein the database is a crowdsourced database.

33. A user equipment (UE), comprising: one or more memories; one or more transceivers; and QC2303210WOQualcomm Ref. No.2303210WO one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: send, to a first entity comprising a base station, a location server, or both, via the one or more transceivers, a request for DTX configuration information; receive, from the first entity via the one or more transceivers, DTX configuration information comprising a DTX configuration for at least one transmission / reception point (TRP); and perform a positioning operation according to the DTX configuration information.

34. The UE of claim 33, wherein, to receive the DTX configuration information, the one or more processors, either alone or in combination, are configured to receive a DTX configuration for at least one geosynchronous (GEO) cell.

35. The UE of claim 33, wherein, to receive the DTX configuration information, the one or more processors, either alone or in combination, are configured to receive a positioning system information block (PosSIB) comprising a DTX configuration for at least one neighbor TRP.

36. The UE of claim 35, wherein the PosSIB further comprises a DTX configuration for a serving TRP.

37. The UE of claim 35, wherein the one or more processors, either alone or in combination, are further configured to receive, via the one or more transceivers, at least one non-positioning SIB comprising a DTX configuration for a serving TRP.

38. The UE of claim 33, wherein the one or more processors, either alone or in combination, are further configured to: send, to the first entity via the one or more transceivers, a DTX configuration request; receive, from the first entity via the one or more transceivers, a response to the DTX configuration request; and QC2303210WOQualcomm Ref. No.2303210WO change a DTX configuration according to the response to the DTX configuration request.

39. The UE of claim 38, wherein the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX configuration, change a duration of an ON time of a DTX configuration, change a duration of an OFF time of a DTX configuration, or a combination thereof.

40. The UE of claim 33, wherein the one or more processors, either alone or in combination, are further configured to: receive, from the first entity via the one or more transceivers, a notification of a change to the DTX configuration for a TRP; and perform a positioning operation according to the change to the DTX configuration for the TRP.

41. The UE of claim 40, wherein the notification of the change to the DTX configuration for the TRP is received as assistance data, via a radio resource control (RRC) message, via a medium access control (MAC) control element (CE), via downlink (DL) downlink control information (DCI), via a long term evolution (LTE) positioning protocol (LPP) message, or via a combination thereof.

42. The UE of claim 33, wherein the one or more processors, either alone or in combination, are further configured to: determine that the positioning operation comprises measuring downlink positioning reference signals from at least one TRP with DTX enabled; and increase a length of a positioning measurement period based at least in part on a DTX period of the at least one TRP with DTX enabled.

43. A location server (LS), comprising: one or more memories; one or more transceivers; and QC2303210WOQualcomm Ref. No.2303210WO one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: send, to a base station via the one or more transceivers, a request for DTX configuration information; and receive, from the base station via the one or more transceivers, DTX configuration information comprising a DTX configuration for at least one transmission / reception point (TRP).

44. The LS of claim 43, wherein, to receive the DTX configuration information, the one or more processors, either alone or in combination, are configured to receive a DTX configuration for at least one geosynchronous (GEO) cell.

45. The LS of claim 43, wherein the one or more processors, either alone or in combination, are further configured to: send, to the base station via the one or more transceivers, a DTX configuration request; and receive, from the base station via the one or more transceivers, a response to the DTX configuration request.

46. The LS of claim 45, wherein the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX configuration, change a duration of an ON time of a DTX configuration, change a duration of an OFF time of a DTX configuration, or a combination thereof.

47. The LS of claim 43, wherein the one or more processors, either alone or in combination, are further configured to: receive, from a user equipment (UE) via the one or more transceivers, a request for DTX configuration information; and send, to the UE via the one or more transceivers, assistance data comprising the DTX configuration information. QC2303210WOQualcomm Ref. No.2303210WO 48. The LS of claim 47, wherein the one or more processors, either alone or in combination, are further configured to: determine a change to the DTX configuration for a TRP; and send, to the UE via the one or more transceivers, a notification of the change to the DTX configuration for the TRP.

49. A base station (BS), comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: receive, from a first entity via the one or more transceivers, a request for DTX configuration information; and send, to the first entity via the one or more transceivers, DTX configuration information comprising a DTX configuration for at least one transmission / reception point (TRP).

50. The BS of claim 49, wherein, to send the DTX configuration information, the one or more processors, either alone or in combination, are configured to send a DTX configuration for at least one geosynchronous (GEO) cell.

51. The BS of claim 49, wherein, to send the DTX configuration information, the one or more processors, either alone or in combination, are configured to send a positioning system information block (PosSIB) comprising a DTX configuration for at least one neighbor TRP.

52. The BS of claim 51, wherein the PosSIB further comprises a DTX configuration for a serving TRP.

53. The BS of claim 51, wherein the one or more processors, either alone or in combination, are further configured to send, via the one or more transceivers, at least one non-positioning SIB comprising a DTX configuration for a serving TRP. QC2303210WOQualcomm Ref. No.2303210WO 54. The BS of claim 49, wherein the one or more processors, either alone or in combination, are further configured to: receive, from the first entity via the one or more transceivers, a DTX configuration request; and send, to the first entity via the one or more transceivers, a response to the DTX configuration request.

55. The BS of claim 54, wherein the DTX configuration request comprises a request to activate a DTX configuration, deactivate a DTX configuration, change a start timing offset of a DTX configuration, change a duration of a period of a DTX configuration, change a duration of an ON time of a DTX configuration, change a duration of an OFF time of a DTX configuration, or a combination thereof.

56. The BS of claim 49, wherein the one or more processors, either alone or in combination, are further configured to: determine a change to the DTX configuration for a TRP; and send, to a user equipment (UE) via the one or more transceivers, a notification of the change to the DTX configuration for the TRP.

57. The BS of claim 49, wherein the one or more processors, either alone or in combination, are further configured to, while a DTX mode is active, either suppress all transmissions by the TRP during DTX OFF time or suppress all transmissions by the TRP except transmissions of downlink positioning reference signals (DL-PRS) during DTX OFF time, according to the DTX configuration.

58. A user equipment (UE), comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: QC2303210WOQualcomm Ref. No.2303210WO determine that a cell is operating according to a DTX configuration that is not known by the UE; determine the DTX configuration of the cell; and perform a positioning operation according to the DTX configuration.

59. The UE of claim 58, wherein, to determine that the cell is operating according to a DTX configuration that is not known by the UE, the one or more processors, either alone or in combination, are configured to determine that a geosynchronous (GEO) cell is operating according to a DTX configuration that is not known by the UE.

60. The UE of claim 58, wherein, to determine the DTX configuration of the cell, the one or more processors, either alone or in combination, are configured to: attempt to decode downlink transmissions from the cell at random intervals or according to a UE-defined periodic interval; and calculate the DTX configuration of the cell based on results of the attempts to decode downlink transmissions from the cell.

61. The UE of claim 60, wherein, to calculate the DTX configuration of the cell, the one or more processors, either alone or in combination, are configured to calculate DTX ON time durations based on timings of successful attempts to decode downlink transmissions from the cell and to calculate a DTX start timing offset and a DTX cycle period based on start and stop times of the DTX ON time durations.

62. The UE of claim 60, wherein, to calculate the DTX configuration of the cell based on results of attempts to decode downlink transmissions from the cell, the one or more processors, either alone or in combination, are configured to: provide the results of attempts to decode downlink transmissions from the cell to a database; and receive, from the database, the DTX configuration of the cell.

63. The UE of claim 62, wherein the results of attempts to decode downlink transmissions from the cell are provided to the database via an over-the-top (OTT) signaling path. QC2303210WOQualcomm Ref. No.2303210WO 64. The UE of claim 62, wherein the database is a crowdsourced database. QC2303210WO

Images