Positioning measurement data

Abstract

This disclosure pertains to technologies for wireless communication. In one aspect, a first communication node (e.g., UE, BS, etc.) acquires one or more measurements associated with one or more PRSs (e.g., uplink PRS, downlink PRS, etc.). The first communication node populates one or more measurement values ​​into one or more measurement fields of a report based on these measurements. The first communication node identifies at least one unfilled measurement field associated with the report and sends a report to a second communication node related to an indication of the at least one unfilled measurement field. The second communication node (e.g., UE, BS, etc.) performs a location calculation function based on the report.

Description

Technical Field

[0001] This patent application claims the benefit of U.S. Provisional Application No. 62 / 966,522, filed on January 27, 2020, entitled “POSITIONING MEASUREMENT DATA,” which has been assigned to the assignee of this patent application and whose entire contents are expressly incorporated herein by reference.

[0002] The present invention relates generally to wireless communication. Prior Technology

[0003] Wireless communication systems have evolved through several generations, including first-generation analog wireless telephony (1G), second-generation (2G) digital wireless telephony (including the transitional 2.5G network), third-generation (3G) high-speed data, internet-enabled wireless services, and fourth-generation (4G) services (such as LTE or WiMax). Many different types of wireless communication systems are currently in use, including cellular and Personal Communication Services (PCS) systems. Examples of known cellular systems include Advanced Cellular Analog Telephone Systems (AMPS) and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), and GSM variants of TDMA.

[0004] The fifth-generation (5G) wireless standard, known as New Radio (NR), achieves higher data transmission speeds, greater connection capacity, and better coverage among other improvements. According to the Next Generation Mobile Networks Alliance (NGNA), the 5G standard aims to provide millions of bits per second (Mbps) of data to each of tens of thousands of users, and billions of Mbps to dozens of employees on an office floor. To support large-scale wireless sensor deployments, it should support hundreds of thousands of simultaneous connections. Therefore, 5G mobile communications should offer significantly improved spectral efficiency compared to the current 4G standard. Furthermore, signaling efficiency should be improved and latency drastically reduced compared to current standards. Summary of the Invention

[0005] The following is a simplified summary of the invention relating to one or more aspects disclosed herein. Therefore, this summary should not be considered a broad overview relating to all aspects considered, nor should it be considered as an attempt to identify key or essential elements relating to all aspects considered or to define the scope relating to any particular aspect. Accordingly, the sole purpose of this summary is to present, in a simplified form, some concepts relating to one or more aspects of the mechanisms disclosed herein, prior to the detailed description given below.

[0006] One aspect relates to a method of operating a first communication node, comprising obtaining one or more measurements associated with one or more positioning reference signals (PRS), populating a set of measurement values ​​into a set of measurement fields in a report based on the one or more measurements, identifying at least one unfilled measurement field associated with the report, and sending a report associated with an indication of the at least one unfilled measurement field to a second communication node.

[0007] On the other hand, a method for operating a second communication node is provided, comprising receiving a report from a first communication node, the report including a set of measurements filled in a corresponding set of measurement fields based on one or more measurements associated with one or more Position Reference Signals (PRS), receiving an indication of at least one unfilled measurement field associated with the report, and performing a location calculation function based on the report.

[0008] On the other hand, a first communication node is involved, including a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver. The at least one processor is configured to obtain one or more measurements associated with one or more positioning reference signals (PRS), populate a set of measurement values ​​into a set of measurement fields in a report based on the one or more measurements, identify at least one unfilled measurement field associated with the report, and send a report associated with an indication of the at least one unfilled measurement field to a second communication node.

[0009] On the other hand, a second communication node is involved, including a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver. The at least one processor is configured to receive a report from the first communication node, the report including a set of measurements filled in a corresponding set of measurement fields based on one or more measurements associated with one or more Position Reference Signals (PRS), receiving an indication of at least one unfilled measurement field associated with the report, and performing a location calculation function based on the report.

[0010] On the other hand, a first communication node is provided, comprising components for obtaining one or more measurements associated with one or more positioning reference signals (PRS), components for filling a set of measurement values ​​into a set of measurement fields in a report based on the one or more measurements, components for identifying at least one unfilled measurement field associated with the report, and components for sending a report associated with an indication of the at least one unfilled measurement field to a second communication node.

[0011] On the other hand, a second communication node is involved, including components for receiving a report from a first communication node, the report including a set of measurements filled in a corresponding set of measurement fields based on one or more measurements associated with one or more Position Reference Signals (PRS), components for receiving an indication of at least one unfilled measurement field associated with the report, and components for performing a location calculation function based on the report.

[0012] On the other hand, it relates to a non-transitory computer-readable medium storing computer-executable instructions, the computer-executable instructions including at least one instruction instructing a first communication node to obtain one or more measurements associated with one or more positioning reference signals (PRS), at least one instruction instructing the first communication node to populate a set of measurement values ​​into a set of measurement fields in a report based on the one or more measurements, at least one instruction instructing the first communication node to identify at least one unfilled measurement field associated with the report, and at least one instruction instructing the first communication node to send a report associated with an indication of the at least one unfilled measurement field to a second communication node.

[0013] On the other hand, it relates to a non-transitory computer-readable medium storing computer-executable instructions, including at least one instruction instructing a second communication node to receive a report from a first communication node, the report including a set of measurements filled in a corresponding set of measurement fields based on one or more measurements associated with one or more Position Reference Signals (PRS), at least one instruction instructing the second communication node to receive at least one unfilled measurement field associated with the report, and at least one instruction instructing the second communication node to perform a location calculation function based on the report.

[0014] Based on the diagrams and detailed description, other objects and advantages relating to the aspects disclosed herein will be apparent to those skilled in the art. Simple Explanation of the Diagram

[0015] The drawings are provided to help describe various aspects of the invention, and are provided merely to illustrate these aspects and not to limit them.

[0016] Figure 1 illustrates an exemplary wireless communication system according to various aspects.

[0017] Figures 2A and 2B show example wireless network structures according to various aspects.

[0018] Figures 3A to 3C are simplified block diagrams of several example aspects of components that can be implemented in a wireless communication node and configured to support the communications taught herein.

[0019] Figures 4A and 4B are schematic diagrams illustrating examples of a frame structure and a channel within the frame structure according to various aspects of the present invention.

[0020] Figure 5 shows an exemplary PRS configuration for a cell supported by a wireless node.

[0021] Figures 6 and 7 illustrate wireless communication methods according to various aspects of the present invention. Implementation

[0022] For illustrative purposes, various aspects of the invention are provided in the following description and related drawings with reference to various examples. Alternative aspects may be devised without departing from the scope of the invention. Furthermore, in order not to obscure relevant details of the invention, well-known elements of the invention will not be described in detail or will be omitted.

[0023] The terms "exemplary" and / or "example" as used herein 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 to other aspects. Similarly, the term "aspects of the invention" does not require that all aspects of the invention encompass the features, advantages, or modes of operation discussed.

[0024] Those skilled in the art will understand that the information and signals described below can be represented using any of a variety of different technologies and processes. For example, data, instructions, commands, information, signals, bits, symbols, and chips referenced in the following description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof, depending in part on the specific application, in part on the desired design, and in part on the appropriate technology, etc.

[0025] Furthermore, many aspects are described as sequences of actions performed by elements of, for example, computing devices. It will be appreciated that the various actions described herein can be performed by specific circuitry (e.g., application-specific integrated circuits (ASICs)), program instructions executed by one or more processors, or a combination of both. Additionally, it can be understood that one or more sequences of actions described herein can be fully implemented in any form of non-transitory computer-readable storage medium storing a corresponding set of computer instructions, which, when executed, will cause or instruct the relevant processor of the device to perform the functions described herein. Therefore, aspects of this disclosure can be implemented in many different forms, all of which are considered within the scope of the claimed subject matter. Furthermore, for each aspect described herein, any corresponding form of these aspects can be described herein as, for example, "logically configured" to perform the described actions.

[0026] As used herein, unless otherwise stated, the terms “User Equipment” (UE) and “base station” are not intended to be specific to or otherwise limited to any particular Radio Access Technology (RAT). Generally, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., mobile phone, router, tablet computer, laptop computer, tracking device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a Radio Access Network (RAN). As used herein, the term “UE” may be interchangeably referred to as “access terminal” or “AT (access terminal),” “client equipment,” “wireless device,” “subscriber equipment,” “subscriber terminal,” “subscriber station,” “user terminal” or “UT,” “mobile terminal,” “mobile station,” or variations thereof. Generally, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks (such as the Internet) and other UEs. Of course, for the UE, it may also be other mechanisms to connect to the core network and / or the Internet, such as through wired access networks, wireless local area network (WLAN) networks (e.g., WLAN networks based on IEEE 802.11, etc.).

[0027] A base station can operate based on one of several RATs used to communicate with the UE, depending on the network in which it is deployed. The base station may be alternatively referred to as an Access Point (AP), Network Node, Node B, Evolved Node B (eNB), New Radio (NR) Node B (also known as gNB or gNodeB), etc. Additionally, in some systems, the base station may only provide edge node signaling functions, while in others it may provide additional control and / or network management functions. The communication link through which the UE signals to the base station is called an uplink (UL) channel (e.g., reverse flow channel, reverse control channel, access channel, etc.). The communication link through which the base station signals to the UE is called a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward flow channel, etc.). As used herein, the term flow channel (TCH) can refer to either the UL / reverse flow channel or the DL / forward flow channel.

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

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

[0030] Figure 1 illustrates an exemplary wireless communication system 100, depending on various aspects. The wireless communication system 100 (also referred to as a wireless wide area network (WWAN)) may include various base stations 102 and various UEs 104. 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 one aspect, macro cell base stations may include eNBs, in which the wireless communication system 100 corresponds to an LTE network, or may include gNBs, in which the wireless communication system 100 corresponds to an NR network, or may include a combination of both, and small cell base stations may include femtocells, picocells, microcells, etc.

[0031] Base stations 102 can collectively form a RAN and connect to a core network 170 (e.g., an evolved packet core (EPC) network or a next-generation core (NGC) network) via backhaul link 122, and to one or more location servers 172 via the core network 170. Among other functions, base stations 102 can perform one or more of the following: transmitting user data, radio channel encryption and decryption, integrity protection, header compression, movement control functions (e.g., handover, dual-connection), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Layer (NAS) messages, NAS node selection, synchronization, RAN sharing, Multimedia Broadcast Multicast Service (MBMS), user and device tracking, RAN Information Management (RIM), paging, location, and warning message delivery. Base stations 102 can communicate with each other directly or indirectly (e.g., via EPC / NGC) via backhaul link 134, which can be wired or wireless.

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

[0033] While the geographic coverage areas 110 of adjacent macrocell base stations 102 may partially overlap (e.g., in a junction area), some geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' may have a coverage area 110' that substantially overlaps with the coverage areas 110 of one or more macrocell base stations 102. A network containing small cell base stations and macrocell base stations may be referred to as a heterogeneous network. A heterogeneous network may also contain home eNBs (HeNBs) that can provide service to restricted groups referred to as Closed Subscriber Groups (CSGs).

[0034] The communication link 120 between base station 102 and UE 104 may include UL (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may transmit over one or more carrier frequencies. Carrier allocation may be asymmetrical relative to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL).

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

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

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

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

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

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

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

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

[0043] In 5G, the spectrum operated by radio nodes (e.g., base stations 102 / 180, UE 104 / 182) is divided into multiple frequency ranges: FR1 (from 450 to 6000 MHz), FR2 (from 24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In multi-carrier systems such as 5G, one carrier frequency is referred to as the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," while the remaining carrier frequencies are referred to as "secondary carriers," "secondary serving cells," or "SCell." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by UE 104 / 182, and the cell in which UE 104 / 182 performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all common control channels and UE-specific control channels and can be a carrier in a licensed frequency (but not always). A secondary carrier is a carrier operating on a second frequency (e.g., FR2). Once an RRC connection is established between UE 104 and the anchor carrier, the secondary carrier can be configured and used to provide additional radio resources. In some cases, the secondary carrier can be a carrier on an unlicensed frequency. The secondary carrier may contain only the necessary signaling information and signals; for example, UE-specific signaling information and signals may not be present in the secondary carrier because the primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. For example, this is done to balance the load on different carriers. Because a "serving cell" (whether PCell or SCell) corresponds to the carrier frequency / component carrier of some communicating base station, the terms "cell," "serving cell," "component carrier," and "carrier frequency" are used interchangeably.

[0044] For example, still referring to Figure 1, one of the frequencies used by macrocell base station 102 can be the anchor carrier (or "PCell"), while other frequencies used by macrocell base station 102 and / or millimeter-wave base station 180 can be secondary carriers ("SCell"). Simultaneous transmission and / or reception on multiple carriers allows UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, compared to a single 20 MHz carrier, two aggregated 20 MHz carriers in a multi-carrier system would theoretically double the data rate (i.e., 40 MHz).

[0045] The wireless communication system 100 may also include one or more UEs, such as UE 190, which are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. In the example of Figure 1, UE 190 has a D2D P2P link 192, through which one UE 104 is connected to one of the base stations 102 (e.g., UE 190 can indirectly obtain a cellular connection via the link), and has a D2D P2P link 194, through which a WLAN STA 152 is connected to a WLAN AP 150 (through which UE 190 can indirectly obtain a WLAN-based Internet connection). In one example, D2D P2P links 192 and 194 can be supported by any well-known D2D RAT, such as LTE-D, WiFi-D, Bluetooth®, etc.

[0046] The wireless communication system 100 may also include a UE 164, which can communicate with the macro cell base station 102 via communication link 120 and / or with the millimeter-wave base station 180 via millimeter-wave communication link 184. For example, the macro cell base station 102 can support one PCell and one or more SCells for the UE 164, while the millimeter-wave base station 180 can support one or more SCells for the UE 164.

[0047] Figure 2A illustrates an example wireless network architecture 200, depending on various aspects. For example, the NGC 210 (also referred to as "5GC") can be functionally considered as control plane functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane functions 212 (e.g., UE gateway functions, access to the data network, IP routing, etc.), which operate collaboratively to form the core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the NGC 210, specifically to the control plane functions 214 and 212. In another configuration, the eNB 224 can also connect to the NGC 210 via the NG-C 215 to the control plane function 214 and to the NG-U 213 to the user plane function 212. Furthermore, the eNB 224 can communicate directly with the gNB 222 via the backhaul connection 223. In some configurations, the new RAN 220 may have only one or more gNBs 222, while other configurations include both one or more eNBs 224 and one or more gNBs 222. Either gNB 222 or eNB 224 can communicate with UE 204 (e.g., any UE shown in Figure 1). Another optional aspect may include a location server 230, which can communicate with NGC 210 to provide location assistance to UE 204. The location server 230 may be implemented as multiple independent servers (e.g., physically independent servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or optionally, each location server 230 may correspond to a single server. The location server 230 may be configured to support one or more location services for UE 204, which UE 204 may connect to the location server 230 via the core network, NGC 210, and / or via the Internet (not shown). Furthermore, the location server 230 can be integrated into the core network components, or alternatively, it can be located outside the core network.

[0048] Depending on the aspects, Figure 2B illustrates another example wireless network architecture 250. For example, the NGC 260 (also referred to as "5GC") can be functionally viewed as a control plane function provided by the Access and Mobility Management Function (AMF) / User Plane Function (UPF) 264, and a user plane function provided by the Session Management Function (SMF) 262, which operate collaboratively to form the core network (i.e., NGC 260). The user plane interface 263 and the control plane interface 265 connect the gNB 224 to the NGC 260, and specifically to the SMF 262 and AMF / UPF 264. In an additional configuration, the gNB 222 can also be connected to the NGC 260 to the AMF / UPF 264 via the control plane interface 265, and to the user plane interface 263 to the SMF 262. Furthermore, eNB 224 can communicate with gNB 222 via backhaul connection 223, regardless of whether the gNB is directly connected to NGC 260. In some configurations, the new RAN 220 may have only one or more gNBs 222, while other configurations include both one or more eNBs 224 and one or more gNBs 222. Either gNB 222 or eNB 224 can communicate with UE 204 (e.g., any UE shown in Figure 1). The base station of the new RAN 220 communicates with the AMF side of AMF / UPF 264 via the N2 interface and with the UPF side of AMF / UPF 264 via the N3 interface.

[0049] The AMF's functions include registration management, connection management, reachability management, mobility management, lawful interception, conversation management (SM) message transmission between UE 204 and SMF 262, transparent proxy service for routing SM messages, access authentication and access authorization, short message service (SMS) message transmission between UE 204 and the Short Message Service Function (SMSF) (not shown), and the Secure Anchoring Function (SEAF). The AMF also interacts with the Authentication Server Function (AUSF) (not shown) and UE 204, and receives the intermediate key established as a result of the UE 204 authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM)-based authentication, the AMF extracts security material from the AUSF. The AMF's functions also include Secure Content Management (SCM). The SCM receives a key from the SEAF and uses it to obtain a network-specific access key. The AMF's functions also include location service management for regulatory services, transmission of location service messages between UE 204 and Location Management Function (LMF) 270 and between the new RAN 220 and LMF 270, allocation of EPS bearer identifiers for interaction with the Evolved Packet System (EPS), and notification of UE 204 mobility events. Additionally, the AMF supports functions for non-3GPP access networks.

[0050] The functions of UPF include serving as an anchor point for intra / inter-RAT mobility (where applicable), serving as an external Protocol Data Unit (PDU) dialogue point for interconnection with a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gate, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, user plane quality of service (QoS) processing (e.g., UL / DL rate enforcement, reflective QoS marking in DL), UL traffic verification (service data stream (SDF) to QoS stream mapping), transport-level packet marking in UL and DL, DL packet buffering and DL data notification triggering, and issuing and forwarding one or more "end markers" to the source RAN node.

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

[0052] Another optional aspect may include an LMF 270, which can communicate with the NGC 260 to provide location assistance to the UE 204. The LMF 270 can be implemented as multiple independent servers (e.g., physically independent servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each LMF 270 may correspond to a single server. The LMF 270 can be configured to support one or more location services for the UE 204, and these location servers can be connected to the LMF 270 via the core network, the NGC 260, and / or via the Internet (not shown).

[0053] Figures 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that can be incorporated into UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or implement any network functions described herein, including location server 230 and LMF 270) to support the file transfer operations taught herein. It will be understood that these components can be implemented in different types of devices in different implementations (e.g., in an ASIC, in a system-on-a-chip (SoC), etc.). The components shown can also be incorporated into other devices in a communication system. For example, other devices in the system may include components similar to those described to provide similar functionality. Furthermore, a given device may contain one or more components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0054] UE 302 and base station 304 each include Wireless Wide Area Network (WWAN) transceivers 310 and 350, respectively, configured to communicate via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, and / or the like. WWAN transceivers 310 and 350 may 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., eNB, gNB), via at least one designated RAT (e.g., NR, LTE, GSM, etc.), through a wireless communication medium of interest (e.g., a time set / frequency resource set in a specific spectrum). WWAN transceivers 310 and 350 may be configured differently to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.), respectively, and conversely, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.) according to a designated RAT. Specifically, transceivers 310 and 350 each include one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358 respectively, and each includes one or more receivers 312 and 352 for receiving and decoding signals 318 and 358 respectively.

[0055] In at least some cases, UE 302 and base station 304 also include wireless local area network (WLAN) transceivers 320 and 360, respectively. WLAN transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, to communicate with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth®, etc.) through a wireless communication medium of interest. WLAN transceivers 320 and 360 can be configured differently to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.), respectively, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.) according to a designated RAT. Specifically, transceivers 320 and 360 each include one or more transmitters 324 and 364 for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively.

[0056] Transceiver circuitry including a transmitter and a receiver may include, in some embodiments, an integrated device (e.g., transmitter and receiver circuitry implemented as a single communication device), in some embodiments, separate transmitter and receiver devices, or in other embodiments, it may be implemented in a different manner. In one aspect, the transmitter may include or be coupled to multiple antennas (e.g., antennas 316, 336, and 376), such as an antenna array, which allows the corresponding device to perform transmit "beamforming," as described herein. Similarly, the transmitter may include or be coupled to multiple antennas (e.g., antennas 316, 336, and 376), such as an antenna array, which allows the corresponding device to perform receive beamforming, as described herein. In another aspect, the transmitter and receiver may share the same multiple antennas (e.g., antennas 316, 336, and 376), such that the corresponding device can only receive or transmit at a given time, and cannot receive and transmit simultaneously. The wireless communication devices of devices 302 and / or 304 (e.g., one or both of transceivers 310 and 320 and / or 350 and 360) may also include network eavesdropping modules (NLMs) for performing various measurements.

[0057] In at least some cases, devices 302 and 304 also include Satellite Positioning System (SPS) receivers 330 and 370. SPS receivers 330 and 370 can be connected to one or more antennas 336 and 376, respectively, to receive SPS signals 338 and 378, such as Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. SPS receivers 330 and 370 can include any suitable hardware and / or software for receiving and processing SPS signals 338 and 378, respectively. SPS receivers 330 and 370 request appropriate information and operations from other systems and use measurements obtained through any suitable SPS algorithm to perform calculations necessary to determine the positions of devices 302 and 304.

[0058] Base station 304 and network entity 306 each include at least one network interface 380 and 390 for communicating with other network entities. For example, network interfaces 380 and 390 (e.g., one or more network access ports) may be configured to communicate with one or more network entities via a wired or wireless backhaul connection. In some aspects, network interfaces 380 and 390 may be implemented as transceivers configured to support wired or wireless signaling communication. Such communication may involve, for example, sending and receiving messages, parameters, or other types of information.

[0059] Apparatus 302, 304, and 306 also include other components that can be used in conjunction with the operations disclosed herein. UE 302 includes processor circuitry implementing processing system 332, which provides functions related to, for example, faulty base station (FBS) detection disclosed herein, and provides other processing functions. Base station 304 includes processing system 384, which provides functions related to, for example, FBS detection disclosed herein, and provides other processing functions. Network entity 306 includes processing system 394, which provides functions related to, for example, FBS detection disclosed herein, and provides other processing functions. In one aspect, processing systems 332, 384, and 394 may include, for example, one or more general-purpose processors, multi-core processors, ASICs, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), or other programmable logic devices or processing circuitry.

[0060] Devices 302, 304, and 306 include memory circuitry that implements memory components 340, 386, and 396 (e.g., each memory component includes a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). In some cases, devices 302, 304, and 306 may include PRS measurement modules 342 and 388, respectively. PRS measurement modules 342 and 388 may be part of or coupled to processing systems 332, 384, and 394, respectively, and when executed, cause devices 302, 304, and 306 to perform the functions described herein. Alternatively, PRS measurement modules 342 and 388 may be memory modules stored in memory components 340, 386, and 396 (as shown in Figures 3A to 3C), respectively, and when executed by processing systems 332, 384, and 394, cause devices 302, 304, and 306 to perform the functions described herein.

[0061] UE 302 may include one or more sensors 344 coupled to processing system 332 to provide motion and / or orientation information independent of motion data derived from signals received by WWAN transceiver 310, WLAN transceiver 320, and / or GPS receiver 330. For example, one or more sensors 344 may include accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of motion detection sensor. Furthermore, one or more sensors 344 may include various types of devices and combine their outputs to provide motion information. For example, one or more sensors 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the ability to calculate position in 2D and / or 3D coordinate systems.

[0062] Additionally, UE 302 includes a user interface 346 for providing instructions to the user (e.g., auditory and / or visual instructions) and / or for receiving user input (e.g., when the user activates a sensing device such as a keyboard, touchscreen, microphone, etc.). Although not shown, devices 304 and 306 may also include user interfaces.

[0063] To elaborate further on processing system 384, in the downlink, IP packets from network entity 306 can be provided to processing system 384. Processing system 384 can implement the functions of the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The processing system 384 can provide RRC layer functions related to broadcasting the following: system information (e.g., Master Information Block (MIB), System Information Block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), RAT mobility, and measurement configuration for UE measurement reports; PDCP layer functions related to the following: header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions related to the following: transmission of upper layer packet data units (PDUs), error correction via ARQ, sequencing, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions related to the following: mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0064] Transmitter 354 and receiver 352 can implement Layer-1 functions related to various signal processing functions. Layer-1, which includes the physical (PHY) layer, can include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. Transmitter 354 processes the mapping to the signal distribution map 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 encoded and modulated symbols can then be divided into parallel streams. Each stream is then mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying time-domain OFDM symbol streams. The OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from the channel estimator can be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimates can be derived from a reference signal and / or channel state feedback transmitted by the UE 302. Each spatial stream is then provided to one or more different antennas 356. The transmitter 354 can modulate the RF carrier with the corresponding spatial stream for transmission.

[0065] On UE 302, receiver 312 receives signals through its corresponding one or more antennas 316. Receiver 312 recovers the information modulated onto the RF carrier and provides this information to processing system 332. Transmitter 314 and receiver 312 can implement Layer 1 functions related to various signal processing functions. Receiver 312 can perform spatial processing on the information to recover any spatial stream destined for UE 302. If multiple spatial streams are specified for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. By determining the most probable signal distribution point transmitted by base station 304, the symbols on each subcarrier, as well as the reference signal, can be recovered and demodulated. These soft decisions can be based on channel estimates calculated by a channel estimator. Then, a soft decision is made to decode and deinterleave the data and control signals originally transmitted by base station 304 on the physical channel. The data and control signals are then provided to processing system 332, which implements Layer 3 and Layer 2 functions.

[0066] In the UL, processing system 332 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the core network. Processing system 332 is also responsible for error detection.

[0067] Similar to the functions of the base station 304 combined with DL transmission, the processing system 332 provides RRC layer functions related to: system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions related to header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions related to: transmission of upper-layer PDUs, error correction via ARQ, connection, segmentation and reassembly of RLC data PDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions related to: mapping between logical channels and transport channels, multiplexing MAC SDUs to transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel prioritization.

[0068] Transmitter 314 can use channel estimates derived from reference signals transmitted from base station 304 or feedback by a channel estimator to select appropriate coding and modulation schemes and facilitate spatial processing. Spatial streams generated by transmitter 314 can be provided to different antennas 316. Transmitter 314 can then use the corresponding spatial streams to modulate the RF carrier for transmission.

[0069] UL transmissions are processed at base station 304 in a manner similar to that described in conjunction with the receiver function on UE 302. Receiver 352 receives signals through its respective one or more antennas 356. Receiver 352 recovers the information modulated onto the RF carrier and provides that information to processing system 384.

[0070] In the UL, the processing system 384 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the UE 302. IP packets from the processing system 384 can be provided to the core network. The processing system 384 is also responsible for error detection.

[0071] For convenience, devices 302, 304, and / or 306 are shown in Figures 3A to 3C as containing various components that can be configured according to the various examples described herein. However, it will be understood that the blocks shown may have different functions in different designs.

[0072] Various components of devices 302, 304, and 306 can communicate with each other via data buses 334, 382, ​​and 392, respectively. The components of Figures 3A to 3C can be implemented in various ways. In some embodiments, the components of Figures 3A to 3C can be implemented in one or more circuits, such as one or more processors and / or one or more ASICs (which may contain 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 that function. For example, some or all of the functions represented by blocks 310 to 346 can be implemented by the processor of UE 302 and one or more memory components (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functions represented by blocks 350 to 388 can be implemented by the processor of base station 304 and one or more memory components (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Furthermore, some or all of the functions represented by blocks 390 to 396 can be implemented by the processor and one or more memory components of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). For simplicity, this document describes various operations, actions, and / or functions as being performed by "UE", "base station", "location entity", etc. However, it is understood that such operations, actions, and / or functions can actually be performed by specific components or combinations of components of the UE, base station, location entity, etc., such as processing systems 332, 384, 394, transceivers 310, 320, 350, and 360, memory components 340, 386, and 396, PRS measurement modules 342 and 388, etc.

[0073] Figure 4A is a schematic diagram 400 illustrating an example of a DL frame structure according to various aspects of the present invention. Figure 4B is a schematic diagram 430 illustrating an example of a channel within a DL frame structure according to various aspects of the present invention. Other wireless communication technologies may have different frame structures and / or different channels.

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

[0075] LTE supports a single set of parameters (numerology) (subcarrier spacing, symbol length, etc.). In contrast, NR can support multiple sets of parameters, for example, subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 204 kHz or greater. Table 1 below lists some of the different parameters for different NR parameter sets. Subcarrier spacing (kHz) Symbols / Time Slots Time slot / subframe Time slot / frame Time slot (ms) Symbol duration (µs) Maximum nominal system bandwidth (MHz) with 4K FFT size 15 14 1 10 1 66.7 50 30 14 2 20 0.5 33.3 100 60 14 4 40 0.25 16.7 100 120 14 8 80 0.125 8.33 400 240 14 16 160 0.0625 4.17 800 [surface] [1]

[0076] In the examples of Figures 4A and 4B, a parameter set of 15 kHz was used. Therefore, in the time domain, a frame (e.g., 10 ms) is divided into 10 equal-sized subframes, each 1 ms long, and each subframe contains one time slot. In Figures 4A and 4B, the time axis is represented horizontally from left to right (e.g., on the X-axis), while the frequency axis is represented vertically from bottom to top (e.g., on the Y-axis).

[0077] Resource lattices can be used to represent time slots, each containing one or more time-parallel resource blocks (RBs) in the frequency domain (also known as physical RBs (PRBs)). Resource lattices are further divided into multiple resource elements (REs). An RE can correspond to a symbol length in the time domain and a subcarrier in the frequency domain. In the parameter sets of Figures 4A and 4B, for a regular cyclic prefix, an RB can contain 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain (for DL, OFDM symbols; for UL, SC-FDMA symbols), for a total of 84 REs. For an extended cyclic prefix, an RB can contain 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0078] As shown in Figure 4A, some REs carry DL reference (pilot) signals (DL-RS) for channel estimation on the UE. The DL-RS may include demodulation reference signals (DMRS) and channel state information reference signals (CSI-RS), and exemplary locations are marked "R" in Figure 4A.

[0079] Figure 4B illustrates examples of various channels within a DL subframe of a frame. The Physical Downlink Control Channel (PDCCH) carries DL Link Control Information (DCI) within one or more Control Channel Elements (CCEs). Each CCE contains nine RE Groups (REGs), and each REG contains four consecutive REs in an OFDM symbol. The DCI carries information about UL resource allocation (persistent and non-persistent) and a description of the DL data sent to the UE. Multiple (e.g., up to eight) DCIs can be configured in the PDCCH, and these DCIs can have one of several formats. For example, different DCI formats are used for UL scheduling, non-MIMO DL scheduling, MIMO DL scheduling, and UL power control.

[0080] The UE uses the Primary Synchronization Signal (PSS) to determine subframe / symbol timing and entity layer identification. The UE uses the Secondary Synchronization Signal (SSS) to determine the entity layer cell identification group number and radio frame timing. Based on the entity layer identification and entity layer cell identification group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the aforementioned DL-RS. The Entity Broadcast Channel (PBCH) carrying the MIB can be logically packetized with the PSS and SSS to form an SSB (also known as SS / PBCH). The MIB provides multiple RBs and one system frame number (SFN) within the DL system bandwidth. The Entity Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (e.g., System Information Block (SIB)), and paging messages.

[0081] In some cases, the DL RS shown in Figure 4A can be a Positioning Reference Signal (PRS). Figure 5 shows an exemplary PRS configuration 500 for a cell supported by a radio node (e.g., base station 102). Figure 5 illustrates how PRS positioning is determined by the system frame number (SFN), cell-specific subframe offset (… )552 and PRS cycle ( The configuration is determined by 520. Typically, cell-specific PRS subframe configurations are determined by the "PRS Configuration Index". To define this, the index is included in the observed time difference of arrival (OTDOA) ancillary data. PRS period ( )520 and cell-specific subframe offset ( The PRS configuration index IPRS is defined as shown in Table 2 below. [PRS] [Configuration Index] [ I , ] [ PRS , ] [PRS] [cycle] [ T , ] [ PRS , ] [(subframe)] [PRS] [Subframe offset Δ] [ PRS , ] [(subframe)] 0–159 160 160–479 320 480–1119 640 1120–2399 1280 2400–2404 5 2405–2414 10 2415–2434 20 2435–2474 40 2475–2554 80 2555-4095 Reserved [surface] [2]

[0082] The PRS configuration is defined with reference to the SFN of the cell transmitting the PRS. For the first subframe of the NPRS downlink subframe that includes the first PRS positioning scenario, the PRS instance can satisfy: = 0, in It is 0 ≤ SFN ≤ 1023 It is composed of 0≤ ≤19 The defined time slot number within the wireless frame, It is the PRS cycle 520, and It is a cell-specific subframe offset of 552.

[0083] As shown in Figure 5, the cell-specific subframe offset 552 can be defined according to the number of subframes transmitted from system frame number 0 (slot "0", marked as slot 550) to the start of the first (continuous) PRS positioning instance. In the example of Figure 5, the continuous positioning subframes in each consecutive PRS positioning instance 518a, 518b, and 518c ( The number of shadow blocks is 4. That is, each shadow block representing PRS positioning scenarios 518a, 518b, and 518c represents four subframes.

[0084] In some respects, when the UE receives the PRS configuration index in the OTDOA auxiliary data of a specific cell... At that time, the UE can use Table 2 to determine the PRS period. 520 and PRS subframe offset Then, when scheduling PRS in a cell, the UE can determine the radio frame, subframe, and time slot (e.g., using equation (1)). The OTDOA auxiliary data can be determined by, for example, a location server (e.g., location server 230, LMF 270) and includes auxiliary data for reference cells and multiple neighboring cells supported by various base stations.

[0085] Typically, PRS events from all cells using the same frequency in the network are time-aligned and can have a fixed, known time offset relative to other cells using different frequencies in the network (e.g., a cell-specific subframe offset of 552). In an SFN-synchronous network, all radio nodes (e.g., base station 102) can be aligned on both frame boundaries and system frame numbers. Therefore, in an SFN-synchronous network, all cells supported by various radio nodes can use the same PRS configuration index for PRS transmissions at any given frequency. On the other hand, in an SFN-asynchronous network, various radio nodes can be aligned on frame boundaries but not on system frame numbers. Therefore, in an SFN-asynchronous network, the PRS configuration index for each cell can be configured separately by the network so that PRS events can be aligned in a timely manner.

[0086] If the UE can obtain the cell timing (e.g., SFN) of at least one cell (e.g., a reference cell or serving cell), the UE can determine the timing of the PRS scenarios for the reference cell and neighboring cells used for OTDOA positioning. Then, the timing of other cells can be derived by the UE based on, for example, the assumption that PRS scenarios from different cells overlap.

[0087] 3GPP Rel.16 introduces various aspects of NR positioning aimed at improving the positioning accuracy of positioning schemes. These schemes involve one or more measurements associated with one or more UL PRS or DL ​​PRS (e.g., higher bandwidth (BW), FR2 beam scanning, angle-based measurements such as angle of arrival (AoA) and angle of transmission (AoD) measurements, multi-cell round-trip time (RTT) measurements, etc.). If reducing latency is a priority, UE-based positioning techniques are typically used (e.g., DL-only techniques without UL location measurement reports). However, if latency is not an issue, UE-assisted positioning techniques can be used, which report data measured by the UE to network entities (e.g., location server 230, LMF 270, etc.). The latency associated with UE-assisted positioning techniques can be reduced by implementing LMF in the RAN.

[0088] Layer 3 (L3) signaling (such as RRC or Location Protocol (LPP)) is typically used to transmit reports including location-based information related to UE-assisted positioning technologies. Compared to Layer 1 (L1 or PHY layer) signaling or Layer 2 (L2 or MAC layer) signaling, L3 signaling is associated with relatively high latency (e.g., latency greater than 100 ms). In some cases, lower latency (e.g., less than 100 ms, less than 10 ms, etc.) is desired for location-based reporting between the UE and RAN. In such cases, L3 signaling may not be able to achieve these lower latency levels.

[0089] Embodiments of the present invention relate to location reporting aspects that improve over-the-air transmission efficiency. The various location reporting aspects described below can utilize L1, L2, or L3 signaling.

[0090] Figure 6 illustrates an exemplary procedure 600 for wireless communication according to various aspects of this disclosure. In one aspect, procedure 600 may be executed by a first communication node. In some embodiments, the first communication may correspond to a UE (e.g., in the case where the UE is measuring one or more DL PRS and reporting to the base station) or a BS (e.g., in the case where the BS is measuring one or more UL PRS and reporting to the UE).

[0091] At 610, the first communication node acquires one or more measurements related to one or more PRSs (e.g., one or more UL PRSs, one or more DL PRSs, etc.). As will be discussed in more detail below, one or more measurements may be acquired directly (e.g., via direct measurement at the first communication node) or indirectly (e.g., via an external entity that performs one or more measurements and then relays the measurement data to the first communication node). In one aspect, operation 610 may be performed by one or more receivers 312, WWAN transceiver 310, processing system 332, memory 340, PRS measurement module 342, one or more sensors 344, one or more receivers 352, WWAN transceiver 350, processing system 384, memory 386, PRS measurement module 388, etc.

[0092] At 620, the first communication node populates a set of measurement values ​​into a set of measurement fields in the report based on one or more measurements. In one example, the set of measurement values ​​to be populated into the measurement field set can be selected based on various factors and / or on one or more sub-report concatenation rules, which will be described in more detail below. These factors include specific measurement quality (e.g., if a specific measurement meets a threshold confidence or accuracy, then that measurement is populated into the corresponding field in the report). In one aspect, operation 620 can be performed by processing system 332, memory 340, PRS measurement module 342, processing system 384, memory 386, PRS measurement module 388, etc.

[0093] At 630, the first communication node identifies at least one unfilled measurement field associated with the report. In one example, the at least one unfilled measurement field can be "blank" (e.g., filled with dummy data or a predetermined sequence of bits, which would be recognized by the second communication node as an implicit unfilled state of the field). In an alternative example, at least one unfilled measurement field can be omitted entirely (as opposed to filling with non-measurement bits). In some designs, the identification of at least one unfilled measurement field can be based on various factors, such as specific measurement quality (e.g., if a specific measurement does not meet a threshold confidence or accuracy, the corresponding field of that unfilled measurement field is left in the report), and / or based on one or more sub-reporting sequence rules, which will be described in more detail below. In one aspect, operation 630 can be performed by processing system 332, memory 340, PRS measurement module 342, processing system 384, memory 386, PRS measurement module 388, etc.

[0094] At 640, the first communication node sends a report to the second communication node related to an indication that at least one measurement field is not filled. In some designs, the report itself is configured to provide an indication (e.g., via a bit configuration of the report specifying a particular report format, or by setting a particular report field to a predefined bit configuration to convey which fields are not filled with measurement data, i.e., "blank," etc.). In other designs, the indication that at least one measurement field is not filled can be sent separately from the report. In one aspect, operation 640 can be performed by one or more transmitters 314, WWAN transceiver 310, processing system 332, memory 340, PRS measurement module 342, one or more transmitters 354, WWAN transceiver 350, processing system 384, memory 386, PRS measurement module 388, etc.

[0095] Figure 7 illustrates an exemplary procedure 700 for wireless communication according to various aspects of the present invention. In one aspect, procedure 700 may be executed by a second communication node. In some embodiments, the second communication may correspond to a UE (e.g., in the case where the BS is measuring one or more UL PRS and reporting to the UE, or in the case where the UE is measuring one or more DL PRS and reporting to a side link (SL) UE performing location calculation functions on behalf of the UE) or a BS (e.g., in the case where the UE is measuring one or more DL PRS and reporting to the BS).

[0096] At 710, the second communication node receives a report from the first communication node, which includes a set of measurement values ​​filled in a corresponding measurement field set based on one or more measurements associated with one or more PRS. For example, operation 710 may correspond to receiving a report sent in operation 640 as described above with reference to FIG6. In one aspect, operation 710 may be performed by one or more receivers 312, WWAN transceiver 310, processing system 332, memory 340, PRS measurement module 342, one or more transceivers 352, WWAN transceiver 350, processing system 384, memory 386, PRS measurement module 388, etc.

[0097] At 720, the second communication node receives an indication of at least one unfilled measurement field associated with the report. As described above regarding operation 640, in some designs, the report itself is configured to provide an indication (e.g., by specifying a bit configuration or index for a particular report format, or by setting a specific report field to a predetermined bit configuration to convey which fields are not filled with measurement data, i.e., "blank," etc.). In other designs, the indication of at least one unfilled measurement field may be received separately from the report. In one aspect, operation 720 may be performed by one or more receivers 312, WWAN transceiver 310, processing system 332, memory 340, PRS measurement module 342, one or more transceivers 352, WWAN transceiver 350, processing system 384, memory 386, PRS measurement module 388, etc.

[0098] At 730, the second communication node performs a location calculation function (e.g., LMF) based on the report. On the other hand, operation 720 can be performed by processing system 332, memory 340, processing system 384, memory 386, etc.

[0099] Referring to Figures 6 and 7, in some designs, the reports at 640 and 710 can correspond to L1 signaling (e.g., uplink control information (UCI) communication or downlink control information (DCI) communication), L2 signaling (e.g., MAC command unit (CE)), or L3 signaling (e.g., RRC / LPP signaling, as used in some existing systems for transmitting reports related to PRS).

[0100] Referring to Figures 6 and 7, the set of measurements may be associated with one or more of the following: Time Difference of Arrival (TDOA) measurement, Reference Signal Received Power (RSRP) measurement, Angle of Arrival (AoA) measurement, Angle of Transmission (AoD) measurement, Motion Status measurement, Track measurement, Report Quality Indicator, Receive-Transmit (Rx-Tx) measurement (e.g., to facilitate Round-Trip Time (RTT) calculation) or any combination thereof.

[0101] Referring to Figures 6 and 7, in some designs, the reports at 640 and 710 can be generated according to at least one sub-report sequence rule, wherein the reports at 640 and 710 are generated as a sequence of measurement information from multiple sub-reports. In one example, at least one sub-report sequence rule includes one or more of the following: • Sequentially concatenate measurement information from multiple sub-reports (e.g., RSRP measurement information) on a per-cell (or per-TRP) basis. • Sequentially link measurement information from multiple sub-reports (e.g., a single TOA measurement using PRS pasted across cells), which are common sub-reports in multiple cells associated with the same Transmitter-Receiver Point (TRP). • Sequentially link measurement information from multiple sub-reports related to multiple PRS (e.g., from the same cell or TRP, from different cells or TRPs, etc.). • Sequentially link measurement information from multiple sub-reports related to the disparate measurement type (e.g., TDOA, AoA, etc.). • Sequentially link measurement information from multiple sub-reports related to different TRPs. • Sequentially connect measurement information from multiple sub-reports (e.g., different periods, such as aperiodic (A) sub-reports, semi-persistent (SP) reports, periodic (P) reports, etc.) that are related to different report transmission triggers. • Sequentially concatenate the UE's local measurement information (e.g., motion status, trajectory, mobility information, etc.). • Based on a sequence order based on one or more criteria, connect measurement information from multiple sub-reports (e.g., higher priority measurement information ranked earlier in the report relative to lower priority measurement information). • Based on measurement type, sequence measurement information from multiple sub-reports is linked together, so that only measurement information from one measurement type (e.g., RSRP only, AoA only, etc.) is sequentially linked to the report. • Grouping measurement information from multiple sub-reports by measurement type allows for sequential linking of measurement information from only one measurement type group (e.g., only RSRP and AoA, any measurement type other than RSRP, etc.) to the report. • Any combination of the above items.

[0102] For example, the processing of at least one sub-report sequential rule can correspond to operations 620 to 630, such that the measurement information sequentially linked to the report corresponds to the set of measurement values ​​filled into the measurement field set, while the measurement information not sequentially linked to the report corresponds to at least one unfilled measurement field.

[0103] Referring to Figures 6 and 7, in some designs, the multiple sub-reports of measurement information in the reports at 640 and 710 may include measurement information related to a single cell, measurement information related to multiple cells, measurement information related to at least one side link, or any combination thereof.

[0104] Referring to Figures 6 and 7, in some designs, the report at 640 and 710 may include measurement information related to two or more measurement types (e.g., RSRP and AoA). In some designs, portions of the measurement information from one or more measurements related to at least one cell are omitted from the report (e.g., measurement information that overlaps with other measurements in the report and / or measurement information related to low confidence levels or low accuracy, etc.).

[0105] Referring to Figures 6 and 7, in some designs, the reports at 640 and 710 can have a fixed size. In other designs, the reports at 640 and 710 can have a variable size, depending on the amount of measurement information sequentially linked to the report (e.g., scaling with the amount of measurement information sequentially linked to the report). In some designs, different sets of sub-report types can be sequentially linked separately from each other, such that each set of sub-report types is encoded differently. For example, a first set of sub-report type sequences may include TDOA sub-reports, and a second set of sub-report type sequences may include RSRP sub-reports. In one example, a specific grouping of sub-report types that are co-coded and sequentially linked together may be based on one or more of the sub-report sequence rules described above. In one example, a first set of sub-report type sequences may have a pre-configured size (e.g., similar to CSI Part 1), while a second set of sub-report type sequences may have a variable or dynamic size (e.g., similar to CSI Part 2).

[0106] Referring to Figures 6 and 7, in some designs, the encoding and concatenation of reports can be performed in any order. In one example, encoding can be performed after all concatenations. In an L1-specific example, subreports can be grouped, then concatenated, sent to separate encoders, and the encoded output can then be multiplexed onto the L1 channel.

[0107] Referring to Figures 6 and 7, as described above, unfilled measurement fields can be included in the report, but can be "blank" (e.g., filled with dummy data or a predefined sequence of bits, which will be recognized by the second communication node as an implicit unfilled state of the field). For example, dummy data can be a string of 0s, a string of 1s, or some other sequence of bits configured to be recognized as actual measurement data that does not correspond to the relevant measurement field. In an alternative example, at least one unfilled measurement field can be omitted entirely (as opposed to filling with non-measurement bits).

[0108] In some designs, the first unfilled measurement field associated with the report can be blank, while the second unfilled measurement field associated with the report can be omitted. In some designs, the decision to leave unfilled measurement fields blank or omit them from the report can be based on the size of the unfilled measurement fields (e.g., leaving unfilled measurement fields smaller than a size threshold blank and omitting blank unfilled measurement fields with a size not smaller than a size threshold).

[0109] In some designs, the indications at operations 640 and 720 can expressly identify at least one unfilled measurement field. For example, this express indication could correspond to at least one unfilled measurement field within a report that is set to a predefined bit configuration (e.g., blank). In another example, the indication identifies one of multiple report formats, each associated with a different combination of measurement fields, where the identified report format is associated with at least one unfilled measurement field. Therefore, an index value identifying one or more unfilled fields in the report (i.e., the express indication of those fields) can be transmitted. In some designs, two or more of the multiple report formats are associated with different report sizes (e.g., specifically, a report format with fewer filled measurement fields is typically smaller than a report format with more filled measurement fields, unless there is a significant difference in field size).

[0110] In other designs, the indications at operations 640 and 720 can implicitly identify at least one unfilled measurement field. For example, this implicit indication can identify one of several report formats, each associated with a different combination of measurement fields, where the identified report format is associated with a set of filled measurement fields. Therefore, an index value identifying one or more filled fields in the report (i.e., an implicit indication of one or more unfilled fields) can be transmitted. In some designs, two or more report formats are associated with different report sizes (e.g., specifically, a report format with fewer filled measurement fields is typically smaller than a report format with more filled measurement fields, unless there is a significant difference in field size).

[0111] Referring to Figures 6 and 7, in some designs, the reports at 640 and 710 may include independent measurements of at least one specific measurement. As used herein, an independent measurement is an absolute or independent value, unrelated to another measurement. In some designs, for at least one specific measurement, the reports at 640 and 710 may include differential measurements relative to independent measurements included in the report or in different reports. For example, a specific type of measurement may be performed for multiple cells. In this case, for example, an independent measurement from one of the multiple cells may be paired with differential measurements from one or more other cells in the same report. In another example, a specific type of measurement (e.g., a trajectory) may be tracked over time. In this case, for example, the differential measurement may be relative to (e.g., directly relative, or indirectly relative via one or more "intermediate" differential measurements) an independent measurement obtained earlier in time. Even if an independent measurement is earlier in time relative to a differential measurement, the earlier independent measurement may be part of an earlier report or even part of the same report at 640 and 710. In another example, differential measurements can be relative to independent measurements of the same type in the same report (e.g., an independent RSRP measurement with one or more differential RSRP measurements relative to that independent RSRP measurement, regardless of whether the RSRP measurement is related to the same signal, the same time, etc.).

[0112] Referring to Figures 6 and 7, in some designs, within the content of a differential reporting scheme, independent measurements associated with one or more differential measurements may correspond to maximum or minimum values ​​(e.g., earliest delay, strongest path, etc.). Furthermore, when multiple measurements are reported for the same measurement type, in some designs, these measurements can be sorted in the report according to a defined sorting order. For example, if multiple differential measurements are sorted together in the report, they may be implicitly associated with the same reference independent measurement. Alternatively, independent measurements may be implicitly indicated by the report's structure. Alternatively, independent measurements associated with one or more differential measurements may be explicitly indicated in the report.

[0113] While some examples of reports at 640 and 710 are provided with reference to L1-specific aspects, reports at 620 and 710 can also be implemented via L2 signaling (e.g., MAC-CE) or L3 signaling (e.g., RRC / LLP signaling) as described above. In L2 (MAC-CE), there is no separate coding as in the L1 case (e.g., CSI Parts 1-2). However, code block (CB) / code block group (CBG) partitioning still exists, which can be considered a form of separate coding (e.g., this partitioning is decoupled from the information content of the related packets). In this case, an indication can be used to transmit reports at 640 and 710, specifying which CBGs carry which specific MAC-CEs. In L3 (e.g., RRC / LLP), RRC / LPP signaling can be configured similarly to existing standards, except that an indication of at least one unfilled measurement field is transmitted to increase the transmission efficiency of RRC / LPP signaling and / or to control which measurement data is transmitted via such signaling (e.g., via blanking, etc.).

[0114] While some examples of reports at 640 and 710 are provided, where the first communication node corresponds to the UE and the second communication node corresponds to the BS, in other designs, the communication node can correspond to the BS and the second communication node can correspond to the UE. For example, a UE-based positioning scheme can be enhanced by having the BS (or RAN) transmit measurement information to the UE via reports at 640 and 710 (e.g., the eNB reports Rx-Tx to the UE to allow the UE to calculate its RTT-based location). Such reports can also contain measurement information related to multiple cells and / or sidelink UEs (e.g., the serving cell collects measured and / or calculated locations from these external devices and then relays this information to the UE via reports at 640 and 710). In L1-specific examples, a new DCI format can be defined to transmit reports at 640 and 710, allowing the reports to be monitored via an existing RNTI or a new positioning-specific RNTI (e.g., which may be defined in the standard). When the BS is the first communication node, there is no need to apply "separate coding" (e.g., different coding for different sequence report groups) (e.g., for MAC-CE, CBG can be used for DL ​​MAC-CE similar to UL MAC-CE as described above, and for DCI, a multi-stage DCI method can be used).

[0115] Referring to Figure 6, in some designs, the second communication node can correspond to the SL UE that acts as a relay for the base station.

[0116] Referring to Figures 6 and 7, in some designs, the first communication node can be a UE attempting to determine its location, while the second communication node can correspond to an SL UE performing location calculation functions on behalf of the UE (e.g., so that the BS or WWAN does not need to be part of a fixed location). In this case, in one example, MAC-CE or DL ​​L1 side link control information (SCI) (instead of DCI) can be used for reporting at 640 and 710 (instead of the UL L1 method described above). For example, this approach can help avoid implementing a new decoder on the SL UE for the "UCI over PUSCH / PUCCH" transmission type. A similar approach is followed in 3GPP Rel.16 V2X (using MAC-CE) SLs.

[0117] Those skilled in the art will understand that various different processes and techniques can be used to represent information and signals. For example, the data, instructions, commands, information, signals, bits, symbols, and chips cited throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0118] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and algorithmic steps related to the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this hardware-software interchangeability, the various illustrative components, blocks, modules, circuits, and steps have been broadly described above in terms of functionality. Whether this functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in different ways for each specific application, but these implementation decisions should not be construed as departing from the scope of the invention.

[0119] The various illustrative logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein can be implemented or performed using general-purpose processors, DSPs, ASICs, FPGAs or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but optionally, it can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.

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

[0121] In one or more exemplary aspects, the described functionality can be implemented using hardware, software, firmware, or any combination thereof. If implemented in software, these functions can be stored or transmitted as one or more instructions or code onto a computer-readable medium. Computer-readable media includes computer storage media and communication media, with communication media including any media that facilitates the transfer of computer programs from one place to another. Storage media can be any available media accessible to a computer. For example, and not limitingly, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk memory, magnetic disk memory or other magnetic storage devices, or any other media that can be used to carry or store desired program code in the form of instructions or data structures and is accessible to a computer. Furthermore, any connection is properly referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (e.g., infrared, radio, and microwave), then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (e.g., infrared, radio, and microwave) are all included in the definition of media. As used herein, disk and disc include optical discs (CDs), laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs, wherein a disk typically reproduces data magnetically, while a disc reproduces data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0122] Although the foregoing disclosure illustrates illustrative aspects of the invention, it should be noted that various changes and modifications may be made herein without departing from the scope of the invention as defined by the appended patent applications. The functions, steps, and / or actions of the method claims according to the aspects of the invention described herein do not need to be performed in any particular order. Furthermore, although elements of the invention may be described or claimed in the singular, the plural form is also considered unless explicitly limited to the singular.

[0123] 100: Wireless Communication System 102:Base station 102': Small-scale community base station 104: User Equipment (UE) 110': Coverage area 110: Coverage Area 120: Communication Link 120: Communication Link 122: Backhaul Link 134: Backhaul Link 150: Wireless Local Area Network (WLAN) Access Point (AP) 152: WLAN Station (STA) 154: Communication Link 164:UE 170: Core Network 172: Location Server 180: Millimeter wave (mmW) base station 182:UE 184: Millimeter-wave communication link 184: Millimeter-wave communication link 190:UE 192: Device-to-device (D2D) and peer-to-peer (P2P) links 194: D2D P2P Link 200: Wireless Network Architecture 204:UE 210: Next-Generation Core (NGC) 212: User plane functionality 213: User-defined interface (NG-U) 214: Control Plane Functions 215: Control Plane Interface (NG-C) 220: New Radio Access Network (NEW RAN) 222: New Radio (NR) Node B (gNB) 223: Return Connection 224: Evolved node B (eNB) 230: Location Server 250: Wireless Network Structure 260:NGC 262: Conversation Management Function (SMF) 263: User Interface 264: User Plane Function (UPF) 265: Control Plane Interface 270: Location Management Function (LMF) 302:UE 304:Base station 306: Network Entity 310: Transceiver 312: Receiver 314: Transmitter 316: Antenna 318: Signal 320: Transceiver 322: Receiver 324: Transmitter 326: Antenna 328: Signal 330: SPS Receiver 332: Processing System 334: Data Bus 336: Antenna 338: Satellite Positioning System (SPS) signal 340: Memory Components 342: Positioning Reference Signal (PRS) Measurement Module 344: Sensor 346: User Interface 350: Transceiver 352: Receiver 354: Transmitter 356: Antenna 358: Signal 360: Transceiver 362: Receiver 364: Transmitter 366: Antenna 368: Signal 370: SPS Receiver 376: Antenna 378: SPS signal 380: Network Interface 382: Data Bus 384: Processing System 386: Memory Components 388: PRS Measurement Module 390: Network Interface 392: Data Bus 394: Processing System 396: Memory Components 400: Figure 430: Figure 500:PRS Configuration 518a: PRS positioning occasions 518b: PRS positioning scenarios 518c: PRS positioning occasions 520: PRS period (T_PRS) 550: Time Slot 552: Cell-specific subframe offset (Δ_PRS) 600: Program 610: Steps 620: Steps 630: Steps 640: Steps 700: Program 710: Steps 720: Steps 730: Steps

Claims

1. A method for operating a first communication node, comprising: Obtain one or more measurements associated with one or more Position Reference Signals (PRS); populate the measurement value set into the measurement field set of the report based on the one or more measurements; identify at least one unpopulated measurement field associated with the report; And sending a report to a second communication node related to an indication of the at least one unfilled measurement field, wherein the indication corresponds to the at least one unfilled measurement field set to a predefined bit configuration in the report, or wherein the indication identifies one of a plurality of report formats, each report format being associated with a different combination of measurement fields, and the identified report format being associated with the at least one unfilled measurement field.

2. The method according to request item 1, wherein, At least one unfilled measurement field is left blank in the report or is completely omitted from the report.

3. The method according to request item 1, wherein, This instruction explicitly identifies the at least one unfilled measurement field.

4. The method according to request item 1, wherein, This indication corresponds to at least one unfilled measurement field that is configured as the predefined bit within the report.

5. The method according to request item 1, wherein, This indication implicitly identifies at least one unfilled measurement field.

6. The method according to request item 1, wherein, This instruction identifies the specific report format among the plurality of report formats.

7. The method according to claim 6, wherein, Two or more of these report formats are associated with different report sizes.

8. The method according to request item 1, wherein, The set of measurements is associated with a single cell, or it is associated with a plurality of cells.

9. The method according to claim 1, wherein, This set of measurements includes independent measurements.

10. The method according to claim 1, wherein, This set of measurements includes differential measurements relative to independent measurements included in this report or in different reports.

11. The method according to claim 1, wherein, The report is sent via L1 signaling, L2 signaling, or L3 signaling.

12. The method according to request item 1, wherein, The first communication node corresponds to a user equipment (UE), or the first communication node corresponds to a network element.

13. The method according to request item 1, wherein, The second communication node corresponds to a user equipment (UE), or the second communication node corresponds to a network element, or the second communication node corresponds to a sidelink UE that performs the location calculation function on behalf of another UE.

14. A method for operating a second communication node, comprising: Receive a report from a first communication node, the report comprising a set of measurements filled in a corresponding set of measurement fields based on one or more measurements associated with one or more Position Reference Signals (PRS); receive an indication of at least one unfilled measurement field associated with the report; and perform a location calculation function based on the report, wherein the indication corresponds to the at least one unfilled measurement field set to a predefined bit configuration within the report, or wherein the indication identifies one of a plurality of report formats, each report format being associated with a different combination of measurement fields, and the identified report format being associated with the at least one unfilled measurement field.

15. The method according to claim 14, wherein, At least one unfilled measurement field is left blank in the report or is completely omitted from the report.

16. The method according to claim 14, wherein, This instruction explicitly identifies the at least one unfilled measurement field.

17. The method according to claim 14, wherein, This indication corresponds to at least one unfilled measurement field that is configured as the predefined bit within the report.

18. The method according to claim 14, wherein, This indication implicitly identifies at least one unfilled measurement field.

19. The method according to claim 14, wherein, This instruction identifies the specific report format among the plurality of report formats.

20. The method according to claim 19, wherein, Two or more of these report formats are associated with different report sizes.

21. The method according to claim 14, wherein, The set of measurements is associated with a single cell, or it is associated with a plurality of cells.

22. The method according to claim 14, wherein, This set of measurements includes independent measurements.

23. The method according to claim 14, wherein, This set of measurements includes differential measurements relative to independent measurements included in this report or in different reports.

24. The method according to claim 14, wherein, The report is received via L1 signaling, L2 signaling, or L3 signaling.

25. The method according to claim 14, wherein, The first communication node corresponds to a user equipment (UE), or the first communication node corresponds to a network element.

26. The method according to claim 14, wherein, The second communication node corresponds to a user equipment (UE), or the second communication node corresponds to a network element.

27. A first communication node, comprising: Memory; At least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: acquire one or more measurements associated with one or more Position Reference Signals (PRS); populate a set of measurement values ​​into a set of measurement fields in a report based on the one or more measurements; and identify at least one unpopulated measurement field associated with the report; And sending a report to a second communication node related to an indication of the at least one unfilled measurement field, wherein the indication corresponds to the at least one unfilled measurement field set to a predefined bit configuration in the report, or wherein the indication identifies one of a plurality of report formats, each report format being associated with a different combination of measurement fields, and the identified report format being associated with the at least one unfilled measurement field.

28. The first communication node according to claim 27, wherein, The first communication node corresponds to a user equipment (UE), or the first communication node corresponds to a network element.

29. The first communication node according to claim 27, wherein, The second communication node corresponds to a user equipment (UE), or the second communication node corresponds to a network element, or the second communication node corresponds to a sidelink UE that performs the location calculation function on behalf of another UE.

30. A second communication node, comprising: Memory; At least one transceiver; The system also includes at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive a report from a first communication node, the report including a set of measurements filled in a corresponding set of measurement fields based on one or more measurements associated with one or more Position Reference Signals (PRS); receive an indication of at least one unfilled measurement field associated with the report; and perform a location calculation function based on the report, wherein the indication corresponds to the at least one unfilled measurement field set to a predefined bit configuration within the report, or wherein the indication identifies one of a plurality of report formats, each report format being associated with a different combination of measurement fields, and the identified report format being associated with the at least one unfilled measurement field.

31. The second communication node according to claim 30, wherein, The first communication node corresponds to a user equipment (UE), or the first communication node corresponds to a network element.

32. The second communication node according to claim 30, wherein, The second communication node corresponds to a user equipment (UE), or the second communication node corresponds to a network element.

33. A first communication node, comprising: A component used to obtain one or more measurements associated with one or more positioning reference signals (PRS); A component for filling a set of measurement values ​​into a set of measurement fields in a report based on the one or more measurements; a component for identifying at least one unfilled measurement field associated with the report; and a component for sending the report associated with an indication of the at least one unfilled measurement field to a second communication node, wherein the indication corresponds to the at least one unfilled measurement field set to a predefined bit configuration within the report, or wherein the indication identifies one of a plurality of report formats, each report format being associated with a different combination of measurement fields, and the identified report format being associated with the at least one unfilled measurement field.

34. The first communication node according to claim 33, wherein, The first communication node corresponds to a user equipment (UE), or the first communication node corresponds to a network element.

35. The first communication node according to claim 33, wherein, The second communication node corresponds to a user equipment (UE), or the second communication node corresponds to a network element, or the second communication node corresponds to a sidelink UE that performs the location calculation function on behalf of another UE.

36. A second communication node, comprising: The components include: a component for receiving a report from a first communication node, the report comprising a set of measurements filled in a corresponding set of measurement fields based on one or more measurements associated with one or more Position Reference Signals (PRS); a component for receiving an indication of at least one unfilled measurement field associated with the report; and a component for performing a location calculation function based on the report, wherein the indication corresponds to the at least one unfilled measurement field configured as a predefined bit within the report, or wherein the indication identifies one of a plurality of report formats, each report format being associated with a different combination of measurement fields, and the identified report format being associated with the at least one unfilled measurement field.

37. The second communication node according to claim 36, wherein, The first communication node corresponds to a user equipment (UE), or the first communication node corresponds to a network element.

38. The second communication node according to claim 36, wherein, The second communication node corresponds to a user equipment (UE), or the second communication node corresponds to a network element.

39. A non-transitory computer-readable medium storing at least one computer-executable instruction, the computer-executable instruction comprising: At least one instruction instructs a first communication node to obtain one or more measurements associated with one or more Position Reference Signals (PRS); at least one instruction instructs the first communication node to populate a set of measurement values ​​into a set of measurement fields in a report based on the one or more measurements; at least one instruction instructs the first communication node to identify at least one unfilled measurement field associated with the report; and at least one instruction instructs the first communication node to send the report to a second communication node associated with an indication of the at least one unfilled measurement field, wherein the indication corresponds to the at least one unfilled measurement field set to a predefined bit configuration within the report, or wherein the indication identifies one of a plurality of report formats, each report format being associated with a different combination of measurement fields, and the identified report format being associated with the at least one unfilled measurement field.

40. The non-transitory computer-readable medium according to claim 39, wherein, The first communication node corresponds to a user equipment (UE), or the first communication node corresponds to a network element.

41. The non-transitory computer-readable medium according to claim 39, wherein, The second communication node corresponds to a user equipment (UE), or the second communication node corresponds to a network element, or the second communication node corresponds to a sidelink UE that performs the location calculation function on behalf of another UE.

42. A non-transitory computer-readable medium storing at least one computer-executable instruction, the computer-executable instruction comprising: At least one instruction instructing a second communication node to receive a report from a first communication node, the report including a set of measurements filled in a corresponding set of measurement fields based on one or more measurements associated with one or more Position Reference Signals (PRS); at least one instruction instructing the second communication node to receive an indication of at least one unfilled measurement field associated with the report; and at least one instruction instructing the second communication node to perform a location calculation function based on the report, wherein the indication corresponds to the at least one unfilled measurement field set to a predefined bit configuration within the report, or wherein the indication identifies one of a plurality of report formats, each report format being associated with a different combination of measurement fields, and the identified report format being associated with the at least one unfilled measurement field.

43. The non-transitory computer-readable medium according to claim 42, wherein, The first communication node corresponds to a user equipment (UE), or the first communication node corresponds to a network element.

44. The non-transitory computer-readable medium according to claim 42, wherein, The second communication node corresponds to a user equipment (UE), or the second communication node corresponds to a network element.

Images