Beam shape reporting for positioning

Abstract

Disclosed are techniques for communication. In an aspect, gNB may report antenna configuration and table that maps antenna element(s) to phase shift and / or amplitude shift to a position estimation entity (PDE). The PDE may derive beam shape based on the reported information. In another aspect, gNB may report transformation information by which a first beam shape of a first beam is transformed into a second beam shape of a second beam. The PDF may derive the second beam shape of the second beam based in part upon the transformation information.

Description

[Technical Field]

[0001] The various aspects of this case are generally related to wireless communication. [Previous Technology]

[0002] Wireless communication systems have undergone several generations of development, including first-generation analog wireless telephony (1G), second-generation (2G) digital wireless telephony (including the mid-term 2.5G and 2.75G networks), third-generation (3G) high-speed data, network-connected wireless services, and fourth-generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). Today, many different types of wireless communication systems are in use, including cellular and Personal Communication Services (PCS) systems. Known examples of cellular systems include Cellular Analog Advanced Mobile Telephone Systems (AMPS) and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), etc.

[0003] The fifth-generation (5G) wireless standard, known as New Radio (NR), demands higher data transmission speeds, more connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide tens of megabits per second data rates to each of tens of thousands of users, and gigabits per second data rates to tens of thousands of employees in an office building. It should support hundreds of thousands of simultaneous connections to support large-scale sensor deployments. Therefore, the spectral efficiency of 5G mobile communications should be significantly improved compared to the current 4G standard. Furthermore, signal transmission efficiency should be improved and latency should be significantly reduced compared to the current standard. [Summary of the Invention]

[0004] The following is a simplified summary relating to one or more states disclosed herein. Therefore, this summary should not be considered a broad overview relating to all anticipated states, nor should it be considered an identification of key or important elements relating to all anticipated states or a delineation of categories associated with any particular state. Accordingly, the sole purpose of the following summary is to present, in a simplified form, certain concepts relating to one or more states related to the mechanisms disclosed herein before the detailed descriptions follow.

[0005] In one embodiment, a method of operating a base station includes the following steps: determining an antenna configuration associated with the base station; determining a table mapping each antenna element in the antenna element set associated with the antenna configuration to a phase shift, or amplitude shift, or a combination thereof; reporting the indication of the table to a positioning estimation entity; and reporting the indication of the antenna configuration to the positioning estimation entity.

[0006] In some formats, the table represents a set of antenna elements mapped to each antenna element, or a set of antenna elements mapped to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

[0007] In some configurations, the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0008] In some configurations, the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0009] In some configurations, the antenna spacing includes the vertical antenna spacing, the horizontal antenna spacing, or a combination thereof.

[0010] In some states, the table maps each of the antenna elements in the set to at least a phase shift.

[0011] In some configurations, the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0012] In some configurations, the table also indicates that at least one antenna element is associated with one or more Positioning Reference Signal (PRS) resources.

[0013] In some cases, the meter readings and antenna configuration readings are reported via a single measurement report, or the meter readings and antenna configuration readings are reported via multiple measurement reports.

[0014] In some cases, the table indication is reported via location auxiliary data, or the table indication is reported on demand.

[0015] In one state, a method for operating a positioning estimation entity includes the following steps: receiving from a base station an indication of an antenna configuration associated with the base station; receiving from the base station an indication of a table mapping each antenna element, which is a set of antenna elements and associated with the antenna configuration, to a phase shift, or amplitude shift, or a combination thereof; and determining beamform information of one or more antenna elements based on the indication of the antenna configuration and the indication of the table.

[0016] In some cases, the table indication is received via location auxiliary data, or the table indication is received on demand.

[0017] In some formats, the table represents a set of antenna elements mapped to each antenna element, or a set of antenna elements mapped to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

[0018] In some configurations, the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0019] In some configurations, the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0020] In some configurations, the antenna spacing includes the vertical antenna spacing, the horizontal antenna spacing, or a combination thereof.

[0021] In some states, the table maps each of the antenna elements in the set to at least a phase shift.

[0022] In some configurations, the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0023] In some configurations, the table also indicates that at least one antenna element is associated with one or more Positioning Reference Signal (PRS) resources.

[0024] In some cases, the meter readings and antenna configuration readings are reported via a single measurement report, or the meter readings and antenna configuration readings are reported via multiple measurement reports.

[0025] In one state, a method of operating a base station includes the following steps: determining a first beam shape of a first beam; determining a second beam shape of a second beam; determining transformation information of the first beam shape of the first beam being transformed into the second beam shape of the second beam; and reporting the transformation information to a positioning estimation entity.

[0026] In some states, transformation information includes rotation information, translation information, or a combination thereof.

[0027] In some configurations, the first and second beams are associated with the base station.

[0028] In some configurations, the first beam is associated with a base station and the second beam is associated with another base station.

[0029] In some configurations, the second beam is associated with a base station, and the first beam is associated with another base station.

[0030] In some configurations, the first beam is a reference beam associated with a known beam shape.

[0031] In some states, the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0032] In some cases, the method includes the step of receiving a template of beam shape from a positioning estimation entity, wherein transformation information is based in part on the template.

[0033] In some cases, the change information is reported via location auxiliary data, or the change information is reported on demand.

[0034] In one state, a method for locating and estimating an entity includes the following steps: receiving transformation information from a base station of a first beam shape of a first beam transformed into a second beam shape of a second beam; and determining the second beam shape of the second beam in part based on the transformation information.

[0035] In some states, the transformation information is received via location auxiliary data, or the transformation information is received on demand.

[0036] In some states, transformation information includes rotation information, translation information, or a combination thereof.

[0037] In some configurations, the first beam and the second beam are associated with the base station.

[0038] In some configurations, the first beam is associated with a base station and the second beam is associated with another base station.

[0039] In some configurations, the second beam is associated with a base station, and the first beam is associated with another base station.

[0040] In some configurations, the first beam is a reference beam associated with a known beam shape.

[0041] In some states, the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0042] In some cases, the method includes the step of transmitting a template of beam shape to a base station, wherein transformation information is partially based on the template.

[0043] In one embodiment, a base station includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine an antenna configuration associated with the base station; determine a table mapping each antenna element in an antenna element set associated with the antenna configuration to a phase shift, or amplitude shift, or a combination thereof; report an indication of the table to a positioning estimation entity; and report an indication of the antenna configuration to the positioning estimation entity.

[0044] In some formats, the table represents a set of antenna elements mapped to each antenna element, or a set of antenna elements mapped to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

[0045] In some configurations, the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0046] In some configurations, the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0047] In some configurations, the antenna spacing includes the vertical antenna spacing, the horizontal antenna spacing, or a combination thereof.

[0048] In some states, the table maps each of the antenna elements in the set to at least a phase shift.

[0049] In some states, the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0050] In some configurations, the table also indicates that at least one antenna element is associated with one or more Position Reference Signal (PRS) resources.

[0051] In some cases, the meter readings and antenna configuration readings are reported via a single measurement report, or the meter readings and antenna configuration readings are reported via multiple measurement reports.

[0052] In some cases, the table indication is reported via location auxiliary data, or the table indication is reported on demand.

[0053] In one embodiment, a positioning estimation entity includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive from a base station via the at least one transceiver an indication of an antenna configuration associated with the base station; receive from the base station via the at least one transceiver an indication of mapping each antenna element, which is grouped together with the antenna configuration, to a table of phase shifts, amplitude shifts, or combinations thereof; and determine beamform information of one or more antenna elements based on the indication of the antenna configuration and the indication of the table.

[0054] In some cases, the table indication is received via location auxiliary data, or the table indication is received on demand.

[0055] In some formats, the table represents a set of antenna elements mapped to each antenna element, or a set of antenna elements mapped to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

[0056] In some configurations, the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0057] In some configurations, the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0058] In some configurations, the antenna spacing includes the vertical antenna spacing, the horizontal antenna spacing, or a combination thereof.

[0059] In some states, the table maps each of the antenna elements in the antenna element set to at least a phase shift.

[0060] In some configurations, the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0061] In some configurations, the table also indicates that at least one antenna element is associated with one or more Positioning Reference Signal (PRS) resources.

[0062] In some cases, the meter readings and antenna configuration readings are reported via a single measurement report, or the meter readings and antenna configuration readings are reported via multiple measurement reports.

[0063] In one embodiment, a base station includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine a first beam shape of a first beam; determine a second beam shape of a second beam; determine transformation information of the first beam shape of the first beam being transformed into the second beam shape of the second beam; and report the transformation information to a positioning estimation entity.

[0064] In some states, transformation information includes rotation information, translation information, or a combination thereof.

[0065] In some configurations, the first beam and the second beam are associated with the base station.

[0066] In some configurations, the first beam is associated with a base station and the second beam is associated with another base station.

[0067] In some configurations, the second beam is associated with a base station, and the first beam is associated with another base station.

[0068] In some states, the first beam is a reference beam associated with a known beam shape.

[0069] In some states, the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0070] In some configurations, at least one processor is further configured to receive a template of beamform from a positioning estimation entity via at least one transceiver, wherein transformation information is based in part on the template.

[0071] In some cases, the change information is reported via location auxiliary data, or the change information is reported on demand.

[0072] In one state, a positioning estimation entity includes: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive from a base station via the at least one transceiver transformation information of a first beam shape of a first beam transformed into a second beam shape of a second beam; and determine the second beam shape of the second beam in part based on the transformation information.

[0073] In some states, the transformation information is received via location auxiliary data, or the transformation information is received on demand.

[0074] In some states, transformation information includes rotation information, translation information, or a combination thereof.

[0075] In some configurations, the first beam and the second beam are associated with the base station.

[0076] In some configurations, the first beam is associated with a base station and the second beam is associated with another base station.

[0077] In some configurations, the second beam is associated with a base station, and the first beam is associated with another base station.

[0078] In some configurations, the first beam is a reference beam associated with a known beam shape.

[0079] In some states, the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0080] In some configurations, at least one processor is further configured to transmit a beamform template to a base station via at least one transceiver, wherein transformation information is partially based on the template.

[0081] In one embodiment, a base station includes: components for determining an antenna configuration associated with the base station; components for determining a table that maps each antenna element in an antenna configuration to a phase shift, or amplitude shift, or a combination thereof; components for reporting an indication of the table to a positioning estimation entity; and components for reporting an indication of the antenna configuration to the positioning estimation entity.

[0082] In some forms, the table represents a set of antenna elements mapped to each antenna element, or a set of antenna elements mapped to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

[0083] In some configurations, the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0084] In some configurations, the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0085] In some configurations, the antenna spacing includes the vertical antenna spacing, the horizontal antenna spacing, or a combination thereof.

[0086] In some states, the table maps each of the antenna elements in the set to at least a phase shift.

[0087] In some configurations, the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0088] In some configurations, the table also indicates that at least one antenna element is associated with one or more Positioning Reference Signal (PRS) resources.

[0089] In some cases, the meter readings and antenna configuration readings are reported via a single measurement report, or the meter readings and antenna configuration readings are reported via multiple measurement reports.

[0090] In some cases, the table indication is reported via location auxiliary data, or the table indication is reported on demand.

[0091] In one embodiment, a positioning estimation entity includes: a component for receiving from a base station an indication of an antenna configuration associated with the base station; a component for receiving from the base station an indication of a table mapping each antenna element, which is a set of antenna elements and associated with the antenna configuration, to a phase shift, or amplitude shift, or a combination thereof; and a component for determining beamform information of one or more antenna elements based on the indication of the antenna configuration and the indication of the table.

[0092] In some cases, the table indication is received via location auxiliary data, or the table indication is received on demand.

[0093] In some forms, the table represents a set of antenna elements mapped to each antenna element, or a set of antenna elements mapped to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

[0094] In some configurations, the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0095] In some configurations, the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0096] In some configurations, the antenna spacing includes the vertical antenna spacing, the horizontal antenna spacing, or a combination thereof.

[0097] In some states, the table maps each of the antenna elements in the set to at least a phase shift.

[0098] In some states, the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0099] In some configurations, the table also indicates that at least one antenna element is associated with one or more Positioning Reference Signal (PRS) resources.

[0100] In some cases, the meter readings and antenna configuration readings are reported via a single measurement report, or the meter readings and antenna configuration readings are reported via multiple measurement reports.

[0101] In one state, a base station includes: a component for determining a first beam shape of a first beam; a component for determining a second beam shape of a second beam; a component for determining transformation information of the first beam shape of the first beam transformed into the second beam shape of the second beam; and a component for reporting the transformation information to a positioning estimation entity.

[0102] In some states, transformation information includes rotation information, translation information, or a combination thereof.

[0103] In some configurations, the first and second beams are associated with the base station.

[0104] In some configurations, the first beam is associated with a base station and the second beam is associated with another base station.

[0105] In some configurations, the second beam is associated with a base station, and the first beam is associated with another base station.

[0106] In some states, the first beam is a reference beam associated with a known beam shape.

[0107] In some states, the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0108] In some forms, the method includes: a component for receiving a template of beam shape from a positioning estimation entity, wherein transformation information is partially based on the template.

[0109] In some cases, change information is reported via location auxiliary data, or change information is reported on demand.

[0110] In one state, a positioning estimation entity includes: a component for receiving transformation information from a base station of a first beam shape of a first beam transformed therethrough into a second beam shape of a second beam; and a component for determining the second beam shape of the second beam in part based on the transformation information.

[0111] In some cases, the transformation information is received via location auxiliary data, or the transformation information is received on demand.

[0112] In some states, transformation information includes rotation information, translation information, or a combination thereof.

[0113] In some configurations, the first and second beams are associated with the base station.

[0114] In some configurations, the first beam is associated with a base station and the second beam is associated with another base station.

[0115] In some configurations, the second beam is associated with a base station, and the first beam is associated with another base station.

[0116] In some states, the first beam is a reference beam associated with a known beam shape.

[0117] In some states, the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0118] In some embodiments, the method includes: a component for transmitting a template of beam shape to a base station, wherein transformation information is partially based on the template.

[0119] In one embodiment, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a base station, cause the base station to: determine an antenna configuration associated with the base station; determine a table mapping each antenna element in the antenna element set and associated with the antenna configuration to a phase shift, or amplitude shift, or a combination thereof; report the table to a positioning estimation entity; and report the antenna configuration to the positioning estimation entity.

[0120] In some formats, the table represents a set of antenna elements mapped to each antenna element, or a set of antenna elements mapped to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

[0121] In some configurations, the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0122] In some configurations, the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0123] In some configurations, the antenna spacing includes the vertical antenna spacing, the horizontal antenna spacing, or a combination thereof.

[0124] In some states, the table maps each of the antenna elements in the set to at least a phase shift.

[0125] In some states, the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0126] In some configurations, the table also indicates that at least one antenna element is associated with one or more Positioning Reference Signal (PRS) resources.

[0127] In some cases, the meter readings and antenna configuration readings are reported via a single measurement report, or the meter readings and antenna configuration readings are reported via multiple measurement reports.

[0128] In some cases, the table indication is reported via location auxiliary data, or the table indication is reported on demand.

[0129] In one embodiment, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a positioning estimation entity, cause the positioning estimation entity to: receive from a base station an instruction on an antenna configuration associated with the base station; receive from the base station an instruction on a table mapping each antenna element, which is a set of antenna elements and associated with the antenna configuration, to a phase shift, or amplitude shift, or a combination thereof; and determine beamform information of one or more antenna elements based on the instruction on the antenna configuration and the instruction on the table.

[0130] In some cases, the table indication is received via location auxiliary data, or the table indication is received on demand.

[0131] In some forms, the table represents a set of antenna elements mapped to each antenna element, or a set of antenna elements mapped to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

[0132] In some configurations, the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0133] In some configurations, the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0134] In some configurations, the antenna spacing includes the vertical antenna spacing, the horizontal antenna spacing, or a combination thereof.

[0135] In some states, the table maps each of the antenna elements in the set to at least a phase shift.

[0136] In some states, the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0137] In some configurations, the table also indicates that at least one antenna element is associated with one or more Positioning Reference Signal (PRS) resources.

[0138] In some cases, the meter readings and antenna configuration readings are reported via a single measurement report, or the meter readings and antenna configuration readings are reported via multiple measurement reports.

[0139] In one state, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a base station, cause the base station to: determine a first beam shape of a first beam; determine a second beam shape of a second beam; determine transformation information of the first beam shape of the first beam being transformed into the second beam shape of the second beam; and report the transformation information to a positioning estimation entity.

[0140] In some states, transformation information includes rotation information, translation information, or a combination thereof.

[0141] In some configurations, the first and second beams are associated with the base station.

[0142] In some configurations, the first beam is associated with a base station and the second beam is associated with another base station.

[0143] In some configurations, the second beam is associated with a base station, and the first beam is associated with another base station.

[0144] In some states, the first beam is a reference beam associated with a known beam shape.

[0145] In some states, the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0146] In some configurations, the instruction, when executed by the base station, further causes the base station to:

[0147] In some cases, the transformation information is reported via location auxiliary data, or the transformation information is reported on demand.

[0148] In one embodiment, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a positioning estimation entity, cause the positioning estimation entity to: receive transformation information from a base station of a first beam shape of a first beam transformed into a second beam shape of a second beam; and determine the second beam shape of the second beam in part based on the transformation information.

[0149] In some states, the transformation information is received via location auxiliary data, or the transformation information is received on demand.

[0150] In some states, transformation information includes rotation information, translation information, or a combination thereof.

[0151] In some configurations, the first and second beams are associated with the base station.

[0152] In some configurations, the first beam is associated with a base station and the second beam is associated with another base station.

[0153] In some configurations, the second beam is associated with a base station, and the first beam is associated with another base station.

[0154] In some states, the first beam is a reference beam associated with a known beam shape.

[0155] In some states, the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0156] In some states, the instruction, when executed by the positioning estimation entity, also causes the positioning estimation entity to:

[0157] Other objectives and advantages associated with the various forms disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description.

Implementation Method

[0171] For illustrative purposes, various forms of this invention are provided in the following description and related drawings for each example. Alternative forms may be designed without departing from the scope of this invention. Furthermore, well-known elements of this invention will not be described in detail or will be omitted so as not to obscure the relevant details of this invention.

[0172] As used herein, the terms “exemplary” and / or “example” mean “serving as an example, instance or illustration.” Any variant described herein as “exemplary” and / or “example” is not necessarily to be construed as being better or more advantageous than other variants. Similarly, the term “variables of this case” does not require that all variants of this case include the features, advantages or modes of operation discussed.

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

[0174] Furthermore, many of the states are described in terms of 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)), by program instructions executed by one or more processors, or by a combination of both. Furthermore, the sequences of actions described herein can be considered entirely embodied in any form of non-transitory computer-readable storage medium having a corresponding set of computer instructions stored therein, which, upon execution, will cause or instruct the associated processor of the device to perform the functionality described herein. Therefore, the various states of this application can be embodied in several different forms, all of which are contemplated within the scope of the claimed object. Additionally, for each state described herein, any corresponding form of such state can be described herein as, for example, "logically configured" to perform the described actions.

[0175] As used herein, unless otherwise indicated, 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 via a wireless communication network (e.g., mobile phone, router, tablet, laptop, consumer asset positioning 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” can be interchangeably referred to as “Access Terminal” or “AT”, “Client Equipment”, “Wireless Equipment”, “User Equipment”, “User Terminal”, “User Station”, “User Terminal” or “UT”, “Mobile Equipment”, “Mobile Terminal”, “Mobile Station”, or variations thereof. Typically, 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, it is also possible for a UE to connect to other entities on the core network and / or the Internet, such as via wired access networks, wireless local area network (WLAN) networks (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, etc.).

[0176] The base station may operate according to one of several RATs communicating with the UE, depending on the network in which it is deployed, and may be alternatively referred to as an access point (AP), network node, NodeB, evolved NodeB (eNB), next-generation eNB (ng-eNB), new radio (NR) Node B (also known as gNB or gNodeB), etc. The base station may primarily be used to support radio access by the UE, including supporting data, voice, and / or signaling connections for the supported UE. In some systems, the base station may purely 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 traffic 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 traffic channel, etc.). As used herein, the term Traffic Channel (TCH) can refer to the uplink / reverse traffic channel or the downlink / forward traffic channel.

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

[0178] In some implementations that support UE positioning, the base station may not support radio access by the UE (e.g., it may not support data, voice, and / or signal transmission connections to the UE), but may instead transmit reference signals to the UE for measurement by the UE, and / or receive and measure signals transmitted by the UE. This base station may be referred to as a positioning beacon (e.g., when transmitting signals to the UE) and / or as a location measurement unit (e.g., when receiving and measuring signals from the UE).

[0179] An "RF signal" includes electromagnetic waves of a given frequency that transmit information spatially between a transmitter and a receiver. As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals via multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal," where it is obvious from the context that the term "signal" refers to a wireless signal or an RF signal.

[0180] Figure 1 illustrates an exemplary wireless communication system 100 according to various embodiments of the present invention. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "BS") and various UEs 104. Base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one embodiment, a macrocell base station may include an eNB and / or ng-eNB in ​​which the wireless communication system 100 corresponds to an LTE network, or a gNB in ​​which the wireless communication system 100 corresponds to an NR network, or a combination of both, and a small cell base station may include femtocells, picocells, microcells, etc.

[0181] Base station 102 can collectively form a RAN and interface with core network 170 (e.g., Evolved Packet Core (EPC) or 5G Core (5GC)) via backhaul link 122, and access one or more location servers 172 (e.g., Location Management Function (LMF) or Secure User Plane Location (SUPL) Location Platform (SLP)) via core network 170. Location server 172 can be part of core network 170 or external to core network 170. Location server 172 can be integrated with base station 102. UE 104 can communicate directly or indirectly with location server 172. For example, UE 104 can communicate with location server 172 via base station 102 currently serving UE 104. UE 104 may also communicate with location server 172 via another path (such as via an application server (not shown)), via another network (such as via a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), etc.). For signaling purposes, communication between UE 104 and location server 172 may be represented as an indirect connection (e.g., via core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128). For clarity, intermediate nodes (if any) are omitted in the signaling diagram.

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

[0183] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for a corresponding geographic coverage area 110. In one scenario, one or more cells can be supported by base station 102 in each geographic coverage area 110. A "cell" is a logical communication entity used for communication with a base station (e.g., via some frequency resources referred to as carrier frequency, component carrier, carrier, frequency band, etc.) and can be associated with an identifier used to distinguish cells operating via the same or different carrier frequencies (e.g., physical cell identifier (PCI), enhanced cell identifier (ECI), virtual cell identifier (VCI), cell global identifier (CGI), etc.). In some cases, different cells can be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that can provide access for different types of UEs. Because cells are supported by specific base stations, the term "cell" can refer to one or both of the logical communication entity and the base station supporting the cell, depending on the context. Additionally, since a TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" are used interchangeably. In some cases, the term "cell" can also refer to the geographic coverage area of ​​a base station (e.g., a sector), provided that the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0184] Although the geographic coverage areas 110 of adjacent macrocell base stations 102 may partially overlap (e.g., in a delivery zone), some geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' (labeled as "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations can be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that can provide services to a restricted group called a Closed Subscriber Group (CSG).

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

[0186] 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 via a communication link 154 in unlicensed spectrum (e.g., 5 GHz). When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform an idle channel assessment (CCA) or listen-before-talk (LBT) procedure before communication to determine whether the channel is available.

[0187] The small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, the small cell base station 102' can employ LTE or NR technology and use the same 5 GHz unlicensed spectrum as used by the WLAN AP 150. By employing LTE / 5G in unlicensed spectrum, the small cell base station 102' can improve coverage to increase and / or increase the capacity of the access network. 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.

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

[0189] Transmission beamforming is a technique used to focus RF signals in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). Using transmission beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmission network node) and projects a stronger downlink RF signal in that specific direction, thereby providing the receiving device with a faster (in terms of data rate) and stronger RF signal. To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an antenna array (referred to as 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 individual antennas with the correct phase relationship, such that radio waves from the separate antennas are added together to increase radiation in the desired direction while canceling out radiation in undesired directions.

[0190] Transmitter beams can be quasi-co-located, meaning that these transmit beams 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-co-located (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters about 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 QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of the second reference RF signal transmitted on the same channel.

[0191] 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 particular direction to amplify the RF signal received from that direction (e.g., to increase its gain level). Therefore, when a receiver is said to be beamforming in a certain direction, this means that the beam gain in that direction is high relative to the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain of all other receive beams available to the receiver. 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.

[0192] The transmit beam and the receive beam can be spatially related. Spatial relationship means that the parameters of the second beam (e.g., the transmit beam or the receive beam) used for the second reference signal can be derived from information about the first beam (e.g., the receive beam or the transmit beam) used for 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. Subsequently, the UE can 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.

[0193] Note that a "downlink" beam can be either a transmission beam or a reception beam, depending on the entity forming the beam. For example, if a base station is forming a downlink beam to transmit a reference signal to the UE, the downlink beam is a transmission beam. However, if the UE is forming a downlink beam, the beam is a reception beam for receiving downlink reference signals. Similarly, an "uplink" beam can be either a transmission beam or a reception beam, depending on the entity forming the beam. For example, if a base station is forming an uplink beam, the beam is an uplink reception beam, and if the UE is forming an uplink beam, the beam is an uplink transmission beam.

[0194] In 5G, the spectrum in which wireless nodes (e.g., base stations 102 / 180, UE 104 / 182) operate 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). The mmW band typically includes the FR2, FR3, and FR4 frequency ranges. Therefore, the terms "mmW" and "FR2" or "FR3" or "FR4" are often used interchangeably.

[0195] In multi-carrier systems such as 5G, one of the carrier frequencies is referred to as the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers," "secondary serving cells," or "SCell." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by UE 104 / 182 and the cell, in which UE 104 / 182 performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier in a licensed frequency (however, not always). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured once an RRC connection is established between UE 104 and the anchor carrier, and can be used to provide additional radio resources. In some cases, the secondary carrier can be a carrier in 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 exist in the secondary carrier, since both 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 can be done to balance the load on different carriers. Because a "serving cell" (whether PCell or SCell) corresponds to a base station via the carrier frequency / component carrier it is communicating on, the terms "cell," "serving cell," "component carrier," and "carrier frequency" are used interchangeably.

[0196] For example, still referring to Figure 1, one of the frequencies utilized by macrocell base station 102 may be an anchor carrier (or "PCell"), and other frequencies utilized by macrocell base station 102 and / or mmW base station 180 may be subcarriers ("SCell"). Simultaneous transmission and / or reception on multiple carriers enables UE 104 / 182 to significantly improve its data transmission and / or reception rates. For example, compared to the data rate obtained by a single 20 MHz carrier, two aggregated 20 MHz carriers in a multicarrier system will theoretically double the data rate (i.e., 40 MHz).

[0197] The wireless communication system 100 may also include a UE 164, which can communicate with the macrocell base station 102 via the communication link 120 and / or with the mmW base station 180 via the mmW communication link 184. For example, the macrocell base station 102 may support PCells and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0198] In the example of Figure 1, any of the illustrated UEs (shown as a single UE 104 in Figure 1 for simplicity) can receive signal 124 from one or more Earth-orbiting spacecraft (SV) 112 (e.g., satellites). In one instance, SV 112 may be part of a satellite positioning system that UE 104 can use as an independent source of location information. The satellite positioning system typically includes a system of transmitters (e.g., SV 112) positioned such that a receiver (e.g., UE 104) can determine the location of such transmitters on or above the Earth based at least in part on positioning signals (e.g., signal 124) received from the transmitters. This transmitter typically transmits a signal marked with a set number of repeating pseudo-random noise (PN) codes. Although the transmitter is typically located in SV 112, it may sometimes also be located at a ground control station, base station 102, and / or other UEs 104. UE 104 may include one or more dedicated receivers that are specifically designed to receive signal 124 for obtaining geographic location information from SV 112.

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

[0200] In one configuration, additionally or alternatively, SV 112 may be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn connects to elements in the 5G network (such as a modified base station 102 (without a terrestrial antenna)) or network nodes in the 5GC. This element will then provide access to other elements in the 5G network and ultimately to entities outside the 5G network, such as internet web servers and other user equipment. In this manner, UE 104 may receive communication signals (e.g., signal 124) from SV 112, instead of or in addition to receiving communication signals from terrestrial base station 102.

[0201] 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 (referred to as "sidelinks"). In the example of Figure 1, UE 190 has: a D2D P2P link 192 connected to one of UEs 104 connected to one of base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity via this link); and a D2D P2P link 194 connected to a WLAN STA 152 connected to a WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity via this link). In one example, D2D P2P links 192 and 194 can be supported by any known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, etc.

[0202] Figure 2A illustrates an exemplary wireless network architecture 200. For example, the 5GC 210 (also referred to as the Next Generation Core (NGC)) can functionally be 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 work together to form the core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, and specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the ng-eNB 224 can also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Furthermore, the ng-eNB 224 can communicate directly with the gNB 222 via the backhaul connection 223. In some configurations, the next-generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both the ng-eNB 224 and the gNB 222. The gNB 222 or the ng-eNB 224 (or both) can communicate with one or more UEs 204 (e.g., any of the UEs described herein).

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

[0204] Figure 2B illustrates another exemplary wireless network structure 250. 5GC 260 (which may correspond to 5GC 210 in Figure 2A) can be functionally considered as control plane functions provided by Access and Mobility Management Function (AMF) 264 and user plane functions provided by User Plane Function (UPF) 262, which work together to form the core network (i.e., 5GC 260). The functions of AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transmission of Period Management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and Period Management Function (SMF) 266, transparent proxy service for routing SM messages, access authentication and access authorization, transmission of SMS service messages between UE 204 and SMS Service Function (SMSF) (not shown), and Security Anchor Functionality (SEAF). AMF 264 also interacts with the Authentication Server Function (AUSF) (not shown) and UE 204, and receives an intermediate key established as the result of UE 204's authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM)-based authentication, AMF 264 obtains security material from the AAUSF. AMF 264's functionality also includes Security Context Management (SCM). The SCM receives a key from SEAF, which is used to export a network-specific key for access. AMF 264's functionality also includes location service management for regulatory services, transmission of location service messages between UE 204 and Location Management Function (LMF) 270 (which acts as Location Server 230), transmission of location service messages between NG-RAN 220 and LMF 270, allocation of Evolved Packet System (EPS) bearer identifiers for interoperability with EPS, and notification of UE 204 mobility events. In addition, AMF 264 also supports functionality for non-3GPP (3rd Generation Partnership Project) access networks.

[0205] The functions of UPF 262 include acting as an anchor point for intra-RAT / inter-RAT mobility (where applicable), acting as an external Protocol Data Unit (PDU) communication endpoint 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, quality of service (QoS) processing for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (Service Data Flow (SDF) to QoS flow mapping), transport-level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and the issuance and forwarding of one or more "end markers" to the source RAN node. UPF 262 can also support the transmission of location service messages between UE 204 and location servers (such as SLP 272) via the user plane.

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

[0207] Another alternative configuration may include an LMF 270, which can communicate with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 may be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The LMF 270 may be configured to support one or more location services for the UE 204, which may connect to the LMF 270 via the core network, the 5GC 260, and / or via the Internet (not shown). SLP 272 can support similar functions to LMF 270, but LMF 270 can communicate with AMF 264, NG-RAN 220 and UE 204 via the control plane (e.g., using interfaces and protocols that intend to transmit signals instead of voice or data), while SLP 272 can communicate with UE 204 and external clients (not shown in Figure 2B) via the user plane (e.g., using protocols that intend to carry voice and / or data such as Transmission Control Protocol (TCP) and / or IP).

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

[0209] The functionality of the gNB 222 is divided between the gNB Central Unit (gNB-CU) 226 and one or more gNB Distributed Units (gNB-DU) 228. The interface 232 between the gNB-CU 226 and one or more gNB-DU 228 is referred to as the "F1" interface. In addition to the functions specifically assigned to the gNB-DU 228, the gNB-CU 226 is a logical node that includes base station functions such as transmitting user data, mobility control, radio access network sharing, location, and communication period management. More specifically, the gNB-CU 226 hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) of the gNB 222. The gNB-DU 228 is a logical node that hosts the radio link control (RLC), media access control (MAC), and physical (PHY) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and a cell is supported by only one gNB-DU 228. Therefore, UE 204 communicates with gNB-CU 226 via RRC, SDAP and PDCP layers, and with gNB-DU 228 via RLC, MAC and PHY layers.

[0210] Figures 3A, 3B, and 3C illustrate several exemplary elements (represented by corresponding blocks) that can be incorporated into UE 302 (which may correspond to any of the UEs described herein), base station 304 (which may correspond to any of the base stations described herein), and network entity 306 (which may correspond to or embody any of the network functions described herein, including location server 230 and LMF 270, or alternatively, may be independent of the NG-RAN 220 and / or 5GC 210 / 260 infrastructure illustrated in Figures 2A and 2B, such as a private network) to support file transfer operations as taught herein. It will be understood that these elements 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 illustrated elements can also be incorporated into other devices in a communication system. For example, other devices in the system may include elements similar to those described herein to provide similar functionality. Similarly, a given device may contain one or more of these elements. For example, the device may include multiple transceiver elements that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0211] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, providing components (e.g., components for transmission, components for reception, components for measurement, components for tuning, components for suppressing transmission, etc.) for communication via one or more wireless communication networks (not shown) (such as NR networks, LTE networks, GSM networks, etc.). WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356 for communication 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.) via a wireless communication medium of interest (e.g., a time / frequency resource set in a specific spectrum). WWAN transceivers 310 and 350 can 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, boot signals, etc.) according to a specified RAT respectively. Specifically, WWAN transceivers 310 and 350 each include one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358 respectively, and each includes one or more receivers 312 and 352 for receiving and decoding signals 318 and 358 respectively.

[0212] In at least some cases, UE 302 and base station 304 also each include one or more short-range radio transceivers 320 and 360. The short-range radio transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and are provided with components (e.g., components for transmission, components for reception, components for measurement, components for tuning, components for suppressing transmission, etc.) for communicating with other network nodes (such as other UEs, access points, base stations, etc.) via a wireless communication medium of interest through at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth®, Zigbee®, Z-Wave®, PC5, Dedicated Short Range Communication (DSRC), Wireless Access to Vehicle Environment (WAVE), Near Field Communication (NFC), etc.). Short-range wireless 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, boot signals, etc.) respectively according to a specified RAT. Specifically, short-range wireless transceivers 320 and 360 each include one or more transmitters 324 and 364 for transmitting and encoding signals 328 and 368 respectively, and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368 respectively. As a specific example, short-range wireless transceivers 320 and 360 can be WiFi transceivers, Bluetooth® transceivers, Zigbee® and / or Z-Wave® transceivers, NFC transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

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

[0214] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, providing components (e.g., components for transmission, components for reception, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, base station 304 may use one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, network entity 306 may use one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or to communicate with other network entities 306 via one or more wired or wireless core network interfaces.

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

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

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

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

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

[0220] Additionally, UE 302 includes a user interface 346 that provides components for providing instructions to the user (e.g., auditory and / or visual instructions) and / or for receiving user input (e.g., after the user actuates sensing devices such as a keyboard, touchscreen, microphone, etc.). Although not illustrated, base station 304 and network entity 306 may also include user interfaces.

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

[0222] Transmitter 354 and receiver 352 can implement Layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, can include error detection on the transmission channel, forward error correction (FEC) decoding / decoding of the transmission 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 signal constellation based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). Subsequently, the decoded and modulated symbols can be separated into parallel streams. Each stream can then be mapped to an Orthogonal Frequency Division Multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot frequency) in the time and / or frequency domains, and subsequently combined using an Inverse Fast Fourier Transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM symbol stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from the channel estimator can be used to determine the decoding and modulation scheme, as well as for spatial processing. The channel estimates can be derived from the reference signal and / or channel status feedback transmitted by UE 302. Each spatial stream is then provided to one or more different antennas 356. Transmitter 354 can modulate an RF carrier with the corresponding spatial stream for transmission.

[0223] At UE 302, receiver 312 receives signals via its corresponding antenna 316. Receiver 312 recovers the information modulated onto the RF carrier and provides the information to one or more processors 332. Transmitter 314 and receiver 312 implement Layer 1 functionality associated with 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 destined for UE 302, these multiple spatial streams can be combined by receiver 312 into a single OFDM symbol stream. Subsequently, receiver 312 uses Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes separate OFDM symbol streams for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most likely signal cluster point transmitted by base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. Subsequently, the soft decision is decoded and deinterleaved to recover the data and control signals originally transmitted by base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332 that implement layer 3 (L3) and layer 2 (L2) functionality.

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

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

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

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

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

[0229] For convenience, UE 302, base station 304, and / or network entity 306 are illustrated in Figures 3A, 3B, and 3C as including various elements that can be configured according to the various instances described herein. However, it will be understood that the illustrated elements may have different functionalities in different designs. In particular, the various elements in Figures 3A through 3C are optional in alternative configurations, and each configuration includes configurations that may vary due to design choices, cost, device usage, or other considerations. For example, in the case of Figure 3A, a particular implementation of UE 302 may omit WWAN transceiver 310 (e.g., a wearable device, tablet, PC, or laptop may have Wi-Fi and / or Bluetooth capabilities but no cellular capabilities), or may omit short-range wireless transceiver 320 (e.g., cellular only, etc.), or may omit satellite signal receiver 330, or may omit sensor 344, etc. In another example, as shown in Figure 3B, a specific implementation of base station 304 may omit WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capability), or short-range wireless transceiver 360 (e.g., cellular only), or satellite receiver 370, and so on. For the sake of brevity, this document does not provide explanations of various alternative configurations, but they are readily understandable to those familiar with this technology.

[0230] Various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 334, 382, ​​and 392, respectively. In one configuration, data buses 334, 382, ​​and 392 can form or be part of the communication interface for UE 302, base station 304, and network entity 306, respectively. For example, when different logical entities are embodied in the same device (e.g., gNB and location server functionality combined into the same base station 304), data buses 334, 382, ​​and 392 can provide communication between these logical entities.

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

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

[0233] Various frame structures can be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). Figure 4 is a figure 400 illustrating various exemplary frame structures according to this invention. The frame structure can be a downlink or uplink frame structure. Other wireless communication technologies can have different frame structures and / or different channels.

[0234] LTE, and in some cases NR, utilizes OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option to use OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also collectively referred to as tone, bin, etc. Each subcarrier can be modulated with data. Typically, modulation symbols are transmitted using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing between subcarriers 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 subbands. For example, a subband 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 subbands, respectively.

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

[0236] In the example of Figure 4, a parameter set of 15 kHz was used. Therefore, in the time domain, a 10 ms frame is divided into 10 equal-sized sub-frames, each sub-frame being 1 ms long, and each sub-frame including a time slot. In Figure 4, the horizontal axis represents time (e.g., on the X-axis), increasing from left to right, while the vertical axis represents frequency (e.g., on the Y-axis), increasing (or decreasing) from bottom to top.

[0237] The resource grid can be used to represent time slots, each of which includes one or more concurrent time resource blocks (RBs) (also known as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE can correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the parameter set of Figure 4, for a nominal cyclic prefix, an RB can contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB can contain 12 consecutive subcarriers in the frequency domain and six 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.

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

[0239] Figure 5 is a diagram 500 illustrating various downlink channels within an exemplary downlink time slot. In Figure 5, the horizontal axis represents time (e.g., on the X-axis), increasing from left to right, while the vertical axis represents frequency (e.g., on the Y-axis), increasing (or decreasing) from bottom to top. In the example of Figure 5, a parameter set of 15 kHz is used. Therefore, in the time domain, the illustrated time slot length is one millisecond (ms), which is divided into 14 symbols.

[0240] In NR, the channel bandwidth or system bandwidth is divided into multiple bandwidth portions (BWPs). A BWP is a set of consecutive shared RBs selected from a consecutive subset of RBs for a given parameter set on a given carrier. Typically, up to four BWPs can be specified in both the downlink and uplink. That is, a UE can be configured with up to four BWPs in the downlink and up to four BWPs in the uplink. Only one BWP (uplink or downlink) is active at a given time, meaning that the UE may receive or transmit via only one BWP at a time. In the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it may or may not include the SSB.

[0241] Referring to Figure 5, the Primary Synchronization Signal (PSS) is used by the UE to determine the subframe / symbol timing and entity layer identification. The Secondary Synchronization Signal (SSS) is used by the UE 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 Primary Information Block (MIB) can be logically classified with the PSS and SSS to form an SSB (also known as SS / PBCH). The MIB provides several RBs in the downlink system bandwidth, as well as the System Frame Number (SFN). The Entity Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as the System Information Block (SIB)) that is not transmitted via the PBCH, and paging messages.

[0242] The physical downlink control channel (PDCCH) carries downlink control information (DCI) within one or more control channel elements (CCEs). Each CCE includes one or more RE group (REG) bundles (which can span multiple symbols in the time domain). Each REG bundle includes one or more REGs, and each REG corresponds to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The physical resource set used to carry the PDCCH / DCI is called a control resource set (CORESET) in NR. In NR, the PDCCH is limited to a single CORESET and is transmitted along with its own DMRS. This enables UE-specific beamforming for the PDCCH.

[0243] In the example of Figure 5, each BWP has one CORESET, and this CORESET spans three symbols in the time domain (although a CORESET may only have one or two symbols). Unlike the LTE control channel, which occupies the entire system bandwidth, in NR, the PDCCH channel is confined to a specific area (i.e., a CORESET) in the frequency domain. Therefore, the frequency components of the PDCCH shown in Figure 5 are illustrated as being smaller than a single BWP in the frequency domain. Note that although the illustrated CORESET is continuous in the frequency domain, the CORESET does not need to be continuous. Furthermore, a CORESET can span less than three symbols in the time domain.

[0244] The DCI within the PDCCH carries information about uplink resource allocation (persistent and non-persistent) and a description of downlink data transmitted to the UE, referred to as uplink allowance and downlink allowance, respectively. More specifically, the DCI indicates resources scheduled for downlink data channels (e.g., PDSCH) and uplink data channels (e.g., Entity Uplink Shared Channel (PUSCH)). Multiple (e.g., up to eight) DCIs can be configured in the PDCCH, and these DCIs can have one of several formats. For example, there are different DCI formats for uplink scheduling, for downlink scheduling, for uplink transmission power control (TPC), etc. The PDCCH can be transmitted by 1, 2, 4, 8, or 16 CCEs to accommodate different DCI payload sizes or decoding rates.

[0245] FIG6 is an exemplary PRS configuration illustrating, according to various embodiments of the present invention, two TRPs (labeled "TRP1" and "TRP2") operating in the same positioning frequency layer (labeled "Positioning Frequency Layer 1"). For positioning communication, the UE may be provided with supplementary information indicating the illustrated PRS configuration. In the example of FIG6, the first TRP ("TRP1") is associated (e.g., for transmission) with two PRS resource sets labeled "PRS Resource Set 1" and "PRS Resource Set 2", and the second TRP ("TRP2") is associated with one PRS resource set labeled "PRS Resource Set 3". Each PRS resource set includes at least two PRS resources. Specifically, the first PRS resource set ("PRS resource set 1") includes PRS resources labeled "PRS resource 1" and "PRS resource 2", the second PRS resource set ("PRS resource set 2") includes PRS resources labeled "PRS resource 3" and "PRS resource 4", and the third PRS resource set ("PRS resource set 3") includes PRS resources labeled "PRS resource 5" and "PRS resource 6".

[0246] NR supports several cellular network-based positioning technologies, including downlink-based, uplink-based, and downlink-and-uplink-based positioning methods. Downlink-based positioning methods include Observed Time Difference of Arrival (OTDOA) in LTE, Downlink Time Difference of Arrival (DL-TDOA) in NR, and Downlink Angle of Departure (DL-AoD) in NR. Figure 7 illustrates examples of various positioning methods according to this invention. In the OTDOA or DL-TDOA positioning procedure illustrated in scenario 710, the UE measures the difference between the time of arrival (ToA) of a received reference signal (e.g., a positioning reference signal (PRS)) from the base station; this is referred to as Reference Signal Time Difference (RSTD) or Time Difference of Arrival (TDOA) measurement, and reports it to the positioning entity. More specifically, the UE receives the identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations from auxiliary data. Subsequently, the UE measures the RSTD between the reference base station and each non-reference base station. Based on the known locations of the base stations involved and RSTD measurements, the location entity can estimate the location of the UE.

[0247] For the DL-AoD positioning illustrated in Scenario 720, the positioning entity uses beam reports from the UE, measured by the received signal strength of multiple downlink transmission beams, to determine the angle between the UE and the transmission base station. The positioning entity can then estimate the UE's position based on the determined angle and the known location of the transmission base station.

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

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

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

[0251] To assist in the positioning operation, a location server (e.g., location server 230, LMF 270, SLP 272) may provide auxiliary data to the UE. For example, the auxiliary data may include identifiers of the base station (or the cell / TRP of the base station) from which it measures the reference signal, reference signal configuration parameters (e.g., the number of consecutive positioning sub-frames, the periodicity of the positioning sub-frames, muting sequences, frequency hopping sequences, reference signal identifiers, reference signal bandwidth, etc.), and / or other parameters applicable to a specific positioning method. Alternatively, the auxiliary data may be derived directly from the base station itself (e.g., in periodically broadcast management burden messages, etc.). In some cases, the UE may be able to detect neighboring network nodes itself without using auxiliary data.

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

[0253] Location estimation may be referred to by other names, such as location estimate, location, positioning, location point, etc. Location estimation may be geodetic and include coordinates (e.g., latitude, longitude, and possible altitude), or it may be urban and include street address, postal address, or another verbal description of the location. Location estimation may also be defined relative to another known location, or defined in absolute terms (e.g., using latitude, longitude, and possible altitude). Location estimation may include anticipated errors or uncertainties (e.g., by including an area or volume within which the location is expected to be included at a specified or preset confidence level).

[0254] Figure 8 is a diagram of a base station (BS) 802 (which may correspond to any of the base stations described herein) communicating with a UE 804 (which may correspond to any of the UEs described herein). Referring to Figure 8, the base station 802 may transmit beamforming signals to the UE 804 on one or more transmission beams 802a, 802b, 802c, 802d, 802e, 802f, 802g, 802h, each transmission beam having a beam identifier that can be used by the UE 804 to identify the corresponding beam. When the base station 802 is beamforming toward the UE 804 using a single antenna array (e.g., a single TRP / cell), the base station 802 may perform a "beam sweep" by transmitting the first beam 802a, then the beam 802b, and so on, until finally transmitting the beam 802h. Alternatively, base station 802 can transmit beams 802a-802h in a certain pattern, such as beam 802a, followed by beam 802h, followed by beam 802b, followed by beam 802g, and so on. In the case where base station 802 is using multiple antenna arrays (e.g., multiple TRPs / cells) to beamform toward UE 804, each antenna array can perform beam scanning of a subset of beams 802a-802h. Alternatively, each of beams 802a-802h can correspond to a single antenna or antenna array.

[0255] Figure 8 also illustrates the paths 812c, 812d, 812e, 812f, and 812g followed by beamforming signals transmitted on beams 802c, 802d, 802e, 802f, and 802g, respectively. Each path 812c, 812d, 812e, 812f, and 812g may correspond to a single "multipath," or each path may consist of a plurality of (a cluster of) "multipaths" due to the propagation characteristics of radio frequency (RF) signals through the environment. Note that although only the paths for beams 802c-802g are illustrated, this is for simplicity, and the signals transmitted on each of beams 802a-802h will follow a certain path. In the example shown, paths 812c, 812d, 812e, and 812f are straight lines, while path 812g is reflected by an obstacle 820 (e.g., a building, vehicle, terrain feature, etc.).

[0256] UE 804 may receive beamforming signals from base station 802 on one or more receive beams 804a, 804b, 804c, 804d. Note that, for simplicity, the beams illustrated in Figure 8 represent either transmit or receive beams, depending on which of base station 802 and UE 804 is transmitting and which is receiving. Therefore, UE 804 may also transmit beamforming signals to base station 802 on one or more of beams 804a-804d, and base station 802 may receive beamforming signals from UE 804 on one or more of beams 802a-802h.

[0257] In one state, base station 802 and UE 804 can perform beam training to align the transmission and reception beams of base station 802 and UE 804. For example, depending on environmental conditions and other factors, base station 802 and UE 804 can determine that the optimal transmission and reception beams are 802d and 804b, or 802e and 804c, respectively. The direction of the optimal transmission beam for base station 802 can be the same as or different from the direction of the optimal reception beam, and similarly, the direction of the optimal reception beam for UE 804 can be the same as or different from the direction of the optimal transmission beam. However, note that aligning the transmission and reception beams is not necessary for performing downlink angle of arrival (DL-AoD) or uplink angle of arrival (UL-AoA) positioning procedures.

[0258] To perform the DL-AoD positioning procedure, base station 802 may transmit reference signals (e.g., PRS, CRS, TRS, CSI-RS, PSS, SSS, etc.) to UE 804 from one or more of the beams 802a-802h, where each beam has a different transmission angle. The different transmission angles of the beams will result in different received signal strengths (e.g., RSRP, RSRQ, SINR, etc.) at UE 804. Specifically, the received signal strength of the transmission beams 802a-802h that are farther from the line-of-sight (LOS) path 810 between base station 802 and UE 804 will be lower than the received signal strength of the transmission beams 802a-802h that are closer to the LOS path 810.

[0259] In the example of Figure 8, if base station 802 transmits reference signals to UE 804 on beams 802c, 802d, 802e, 802f, and 802g, then transmission beam 802e is preferably aligned with LOS path 810, while transmission beams 802c, 802d, 802f, and 802g are not. Therefore, beam 802e is likely to have a higher received signal strength at UE 804 than beams 802c, 802d, 802f, and 802g. Note that reference signals transmitted on some beams (e.g., beams 802c and / or 802f) may not reach UE 804, or the energy reaching UE 804 from such beams may be so low that it may be undetectable or at least negligible.

[0260] UE 804 may report to base station 802 the received signal strength and optional associated measurement quality of each measured transmission beam 802c-802g, or alternatively, report the identification of the transmission beam with the highest received signal strength (beam 802e in the example of FIG8). Alternatively or additionally, if UE 804 is also busy locating communication periods with at least one base station 802 or multiple base stations 802 respectively using round-trip time (RTT) or time difference of arrival (TDOA), UE 804 may report the received transmission (Rx-Tx) time difference or reference signal time difference (RSTD) measurement (and optional associated measurement quality) to the serving base station 802 or other locating entity respectively. In any case, the locating entity (e.g., base station 802, location server, third-party client, UE 804, etc.) can estimate the angle from base station 802 to UE 804 as the AoD of the transmission beam with the highest received signal strength at UE 804, which is transmission beam 802e in this case.

[0261] In one scenario of DL-AoD-based positioning, with only one involved base station 802, base station 802 and UE 804 can perform a round-trip time (RTT) procedure to determine the distance between base station 802 and UE 804. Therefore, the positioning entity can determine both the direction to UE 804 (using DL-AoD positioning) and the distance to UE 804 (using RTT positioning) to estimate the location of UE 804. Note that, as shown in Figure 8, the AoD with the highest received signal strength is not necessarily located along the LOS path 810. However, this is assumed for DL-AoD-based positioning purposes.

[0262] In another form of DL-AoD-based positioning, when there are multiple involved base stations 802, each involved base station 802 can report the determined AoD or RSRP measurement from the corresponding base station 802 to the serving base station 802 to the UE 804. Subsequently, the serving base station 802 can report the AoD or RSRP measurement from the other involved base stations 802 to the positioning entity (e.g., the UE 804 for UE-based positioning or a location server for UE-assisted positioning). Using this information and knowledge of the geographic locations of the base stations 802, the positioning entity can estimate the location of the UE 804 as the intersection of the determined AoD. For a two-dimensional (2D) positioning solution, there should be at least two involved base stations 802, but as will be understood, the more base stations 802 involved in the positioning procedure, the more accurate the estimated location of the UE 804 will be.

[0263] To perform the UL-AoA positioning procedure, UE 804 transmits uplink reference signals (e.g., UL-PRS, SRS, DMRS, etc.) to base station 802 on one or more uplink transmission beams 804a-804d. Base station 802 receives the uplink reference signals on one or more uplink reception beams 802a-802h. Base station 802 determines the angle of the optimal reception beams 802a-802h for receiving one or more reference signals from UE 804, as the AoA from UE 804 to itself. Specifically, each of the reception beams 802a-802h will result in different received signal strengths (e.g., RSRP, RSRQ, SINR, etc.) of one or more reference signals at base station 802. Furthermore, the channel impulse response (AoA) of one or more reference signals of the received beams 802a-802h that are far from the actual LOS path between base station 802 and UE 804 will be less than that of one or more reference signals of the received beams 802a-802h that are closer to the LOS path. Similarly, the received signal strength of the received beams 802a-802h that are far from the LOS path will be lower than that of the received beams 802a-802h that are closer to the LOS path. Therefore, base station 802 identifies the received beams 802a-802h that result in the highest received signal strength and the strongest possible channel impulse response, and estimates the angle from itself to UE 804 as the AoA of the received beams 802a-802h. Note that, as with DL-AoD-based positioning, the AoA of the receiving beams 802a-802h that result in the highest received signal strength (and the strongest channel impulse response, if measured) is not necessarily located along the LOS path 810. However, for the purposes of UL-AoA-based positioning in FR2, this can be assumed.

[0264] Note that although UE 804 is illustrated as capable of beamforming, this is unnecessary for DL-AoD and UL-AoA positioning procedures. Instead, UE 804 can receive and transmit on an omnidirectional antenna.

[0265] When UE 804 is estimating its location (i.e., the UE is the location entity), it needs to obtain the geographic location of base station 802. UE 804 can obtain its location from, for example, base station 802 itself or a location server (e.g., location server 230, LMF 270, SLP 272). Knowing the distance to base station 802 (based on RTT or timing advance), the angle between base station 802 and UE 804 (based on the UL-AoA of the optimal receive beams 802a-802h), and the known geographic location of base station 802, UE 804 can estimate its location.

[0266] Alternatively, when a positioning entity (such as base station 802 or a location server) is estimating the location of UE 804, base station 802 reports the AoA of the received beams 802a-802h, which results in the highest received signal strength (and optionally the strongest channel impulse response) of the reference signal received from UE 804, or all received signal strengths and channel impulse responses for all received beams 802 (which allows the positioning entity to determine the optimal received beams 802a-802h). Base station 802 may additionally report the Rx-Tx time difference to UE 804. Subsequently, the positioning entity may estimate the location of UE 804 based on the distance from UE 804 to base station 802, the AoA of the identified received beams 802a-802h, and the known geographic location of base station 802.

[0267] A beam typically consists of a main lobe and several side lobes. The antenna aiming direction is the axis of maximum gain (maximum radiated power) of the directional antenna and is usually aligned with the main lobe (centered on it). The beam shape can typically correspond to the shape of the main lobe and can be used in both UE-assisted positioning estimation schemes and UE-based positioning estimation schemes. In some designs, for UE-assisted DL-AoD positioning estimation schemes, for PRS resource measurement and reporting purposes, one or more of the following can be used to enhance signal delivery to the UE, for example: l Option 1: The LMF can explicitly identify adjacent beams in the auxiliary data (AD); l Option 2: The LMF can transmit beam information in the AD in order of priority of PRS resources; l Option 3: The LMF includes aiming direction information for each PRS resource in the AD; or l Option 4: The LMF can transmit beam information in the AD using a subset of the indicated PRS resources.

[0268] In some designs, beam / antenna information (generally referred to herein as antenna configuration) may optionally be provided by the LMF to the gNB, for example: Option 5: The gNB reports the antenna configuration, including the number of antenna elements (vertical and horizontal), antenna spacing (horizontal increment dh and vertical increment dv), or more of these. It has also been considered for the LMF to further provide pre-encoder information for each PRS resource used for Discrete Fourier Transform (DFT) based beams (e.g., checking if the reported aiming direction is sufficient or if more information is needed), antenna element style information, panel / orientation related information, etc. Option 6: The gNB reports the mapping of angles and beam gain for each of the PRS resources. For this purpose, it has been considered for the gNB to further report representations of the mappings that can be reported, such as parametric functions of the approximate beam response, or gain / angle tables, beamwidth, intersections of multiple beams (angle, RSRP), etc.

[0269] In any of the options regarding gNB beam / antenna information, the gNB beam / antenna information may optionally be provided to the UE by the LMF (e.g., via AD) for UE-based DL-AoD.

[0270] In some designs, for DFT-based methods, reporting the aiming direction may be sufficient to allow the device to approach the beamform. For non-standard beamforms, the gNB can report a representation of the angles and beam gain in some form, as indicated in Option 6 above. However, this presents a significant administrative burden because for each beam, the angle space (e.g., 0-360 degrees) may need to be quantized, and the corresponding array gain may need to be provided. For example, if quantized with an accuracy of 5 degrees, the corresponding array gain may need to be provided in the range of {0-5, 5-10, ..., 355-360} degrees. In this case, the accuracy of the angle estimation will depend on the level of accuracy of the beam representation.

[0271] In practice, due to hardware limitations, analog beamforming uses a codebook that allows for a limited selection of beams. Each beam is obtained by applying phase and amplitude shifts to the signal at each radiating element. The number of possible phase shifts (and amplitude shifts) is finite and is described by a certain number of bits. For example, assuming 2 phase shifter bits, a resolution of ~90 degrees can be achieved.

[0272] The various forms in this case relate to reporting beamform information, or transformation information (e.g., relative to a reference beamform), to a positioning estimation entity via antenna element shifts (e.g., phase shifts and / or amplitude shifts) for a specific antenna element. The positioning estimation entity may optionally forward the beamform information to the UE (e.g., in the case of UE-based positioning estimation). Such forms can provide various technical advantages, such as facilitating the reporting of beamform information without significant administrative burden.

[0273] Figure 9 illustrates an exemplary process 900 of communication according to various forms of this case. In one form, process 900 may be performed by a BS (such as BS 304).

[0274] Referring to Figure 9, at 910, BS 304 (e.g., beamforming element 388, processor 394, etc.) determines the antenna configuration associated with the base station. In some designs, the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof. In some designs, the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof. In some designs, the antenna spacing includes the vertical antenna spacing (dv), the horizontal antenna spacing (dh), or a combination thereof. In some designs, the antenna configuration may include pre-encoder information for each PRS resource used for DFT-based beams (e.g., checking whether the reported aiming direction is sufficient or whether more information is needed), antenna element style information, panel / orientation related information, etc.

[0275] Referring to Figure 9, at 920, BS 304 (e.g., beamforming element 388, processor 394, etc.) determines to map each antenna element in the antenna element set, associated with the antenna configuration, to a table of phase shifts, or amplitude shifts, or combinations thereof. The table at 920 can be configured in various ways. For example, the table maps antenna element sets by each antenna element, or the table maps antenna element sets by each group of antenna elements associated with the same phase shift or the same amplitude shift, or combinations thereof (e.g., some antenna elements are mapped individually, while other antenna elements are mapped in groups).

[0276] Referring to Figure 9, at 930, the BS 304 (e.g., transmitter 314 or 324, network transceiver 380, etc.) indicates a reporting form to a location estimation entity (e.g., an LMF integrated at the BS 304, or a remote entity (such as network entity 306), or a remote location server, or a UE in the case of UE-based location estimation). In some designs, the BS 304 itself may correspond to a location estimation entity, where the reporting at 930 corresponds to internal data transfer between logical elements.

[0277] Referring to Figure 9, at 940, BS 304 (e.g., transmitter 314 or 324, network transceiver 380, etc.) reports an indication of antenna configuration to a location estimation entity (e.g., an LMF integrated at BS 304, or a remote entity (such as network entity 306), or a remote location server, or a UE in the case of UE-based location estimation). In some designs, BS 304 itself may correspond to a location estimation entity, where the reporting at 940 corresponds to internal data transfer between logical elements.

[0278] Figure 10 illustrates an exemplary process 1000 of communication according to various states of this case. In one state, process 1000 may be performed by a location estimation entity, such as UE 302 (e.g., for UE-based location estimation), or BS 304 (e.g., LMF integrated in RAN), or network entity 306 (e.g., LMF, location server, etc. integrated in core network elements).

[0279] Referring to Figure 10, at 1010, the positioning estimation entity (e.g., receiver 312 or 322 or 352 or 362, data bus 382, ​​beamforming element 342 or 388 or 398, etc.) receives an indication of the antenna configuration associated with the base station from the base station. In some designs, this includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof. In some designs, the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof. In some designs, the antenna spacing includes the vertical antenna spacing (dv), the horizontal antenna spacing (dh), or a combination thereof. In some designs, the antenna configuration may include pre-encoder information for each PRS resource used for DFT-based beams (e.g., checking whether the reported aiming direction is sufficient or whether more information is needed), antenna element style information, panel / orientation related information, etc. In some designs, BS 304 itself may correspond to the positioning estimation entity, where the reception at 1010 corresponds to internal data transfer between logic elements.

[0280] Referring to Figure 10, at 1020, the positioning estimation entity (e.g., receiver 312 or 322 or 352 or 362, data bus 382, ​​beamforming element 342 or 388 or 398, etc.) receives from the base station an indication that maps each antenna element in the antenna element set, associated with the antenna configuration, to a table of phase shifts, amplitude shifts, or combinations thereof. In some designs, the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof. In some designs, the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof. In some designs, the antenna spacing includes vertical antenna spacing (dv), horizontal antenna spacing (dh), or a combination thereof. In some designs, the antenna configuration may include pre-encoder information for each PRS resource used for DFT-based beams (e.g., checking whether the reported aiming direction is sufficient or whether more information is needed), antenna element style information, panel / orientation related information, etc. In some designs, BS 304 itself can correspond to a positioning estimation entity, where the reception of 1020 corresponds to internal data transfer between logic elements.

[0281] Referring to FIG10, at 1030, a location estimation entity (e.g., processor 332 or 384 or 394, beamforming element 342 or 388 or 398, etc.) determines the beamforming information of at least one antenna element based on an indication of antenna configuration and an indication of a table. In other designs (e.g., for a UE-based location estimation or a network entity for UE-assisted location estimation), the location estimation entity may incorporate the beamforming information into a location estimation procedure at the location estimation entity to output the location of a target UE, which can then be reported to the target UE or another entity.

[0282] Referring to Figures 9 and 10, in some designs, the table indication (e.g., which may be used to output beamform) is communicated via location assistance data (e.g., via broadcast). In this case, the location assistance data may be broadcast to the UE periodically with a relatively high administrative burden (e.g., via SIB). In other designs, the table indication is communicated on demand to the location estimation entity (e.g., LMF, UE, etc.) (e.g., to reduce administrative burden). In this case, the table indication may be provided based on the target quality of service (e.g., if a high target quality of service exists, the on-demand indication of the table is requested, and otherwise the request is skipped).

[0283] Referring to Figures 9 and 10, in some designs, the table maps antenna element sets to each antenna element, or maps antenna element sets to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof. In one instance, group-based mapping can be implemented to reduce administrative burden, particularly for large antenna arrays.

[0284] Referring to Figures 9 and 10, in some designs, the table maps each antenna element in the antenna element set to at least a phase shift. In some designs, the table maps at least one antenna element in the antenna element set to both a phase shift and an amplitude shift. In one instance, the phase shift mapping may be mandatory, while the amplitude shift may be optional.

[0285] Referring to Figures 9 and 10, in some designs, the table also indicates the association of at least one antenna element with one or more PRS resources. For example, different PRS resources may employ different beams. Therefore, the report via the table mapping can indicate the PRS resource to which the corresponding antenna element belongs.

[0286] Referring to Figures 9 and 10, in some designs, the meter indication and antenna configuration indication are reported via a single measurement report, or the meter indication and antenna configuration indication are reported via multiple (e.g., separate) measurement reports.

[0287] Figure 11 illustrates an exemplary process 1100 of communication according to various forms of this case. In one form, process 1100 may be performed by a BS (such as BS 304).

[0288] Referring to Figure 11, at 1110, BS 304 (e.g., beamforming element 388, processor 394, etc.) determines the first beam shape of the first beam. In some designs, the first beam may correspond to a reference beam associated with a known beam shape. In some designs, the first beam shape may be defined by a target direction, azimuth angle number boundary or range, elevation angle or altitude angle number or degree range, polynomial function, etc.

[0289] Referring to Figure 11, at 1120, BS 304 (e.g., beamforming element 388, processor 394, etc.) determines the second beam shape of the second beam. In some designs, the second beam shape can be defined by a target direction, azimuth angle number boundary or range, elevation angle or altitude angle number or degree range, polynomial function, etc.

[0290] Referring to Figure 11, at 1130, BS 304 (e.g., beamforming element 388, processor 394, etc.) determines the transformation information of the first beam shape of the first beam, which is transformed into the second beam shape of the second beam. Examples of the transformation information will be provided in more detail below.

[0291] Referring to Figure 11, at 1140, BS 304 (e.g., transmitter 314 or 324, network transceiver 380, etc.) reports change information to a location estimation entity (e.g., an LMF integrated at BS 304, or a remote entity (such as network entity 306), or a remote location server, or a UE in the case of UE-based location estimation). In some designs, BS 304 itself may correspond to a location estimation entity, where the reporting at 1140 corresponds to internal data transfer between logical elements.

[0292] Figure 12 illustrates an exemplary communication process 1200 according to various states of this case. In one state, process 1200 may be performed by a location estimation entity, such as UE 302 (e.g., for UE-based location estimation), or BS 304 (e.g., LMF integrated in RAN), or network entity 306 (e.g., LMF, location server, etc. integrated in core network elements).

[0293] Referring to FIG12, at 1210, a positioning estimation entity (e.g., receiver 312 or 322 or 352 or 362, data bus 382, ​​beamforming element 342 or 388 or 398, etc.) receives from the base station transformation information of a first beam shape of a first beam transformed into a second beam shape of a second beam. In some designs, BS 304 itself may correspond to the positioning estimation entity, where the reception at 1210 corresponds to internal data transfer between logic elements.

[0294] Referring to FIG12, at 1220, BS 304 (e.g., beamforming element 388, processor 394, etc.) determines the second beam shape of the second beam in part based on transformation information. In some designs (e.g., for a UE-based location estimation or for a network entity for UE-assisted location estimation), the location estimation entity may incorporate the second beam shape information of the second beam into the location estimation procedure at the location estimation entity to output the location of the target UE, which can then be reported to the target UE or another entity.

[0295] Referring to Figures 11 and 12, in some designs, transformation information (e.g., which can be used to generate beamform) is communicated via location assistance data (e.g., via broadcast). In this case, the location assistance data can be broadcast to the UE periodically with a relatively high administrative burden (e.g., via SIB). In other designs, transformation information is communicated to the positioning estimation entity (e.g., LMF, UE, etc.) on demand (e.g., to reduce administrative burden). In this case, transformation information can be provided based on the target quality of service (e.g., if a high target quality of service exists, transformation information is requested on demand, and otherwise the request is skipped).

[0296] Referring to Figures 11 and 12, in some designs, the transformation information includes rotation information, translation information, or a combination thereof. In the case of rotation, in one instance, two beams may be transmitted from the same TRP but pointing in different directions. In this case, rotation is sufficient to describe (or transform) a beam relative to the other beam. In the case of translation, in one instance, beam 1 is transmitted from TRP 1, and beam 2 is transmitted from TRP 2. In this case, in addition to potentially specifying rotation, translation can indicate the position of TRP 2 relative to TRP 1. For example, suppose the first beam (beam 1) and the second beam (beam 2) are associated with a base station (gNB1). In this case, beam 1 of gNB1 can be rotated (θ, φ) degrees in azimuth and elevation to become beam 2 for gNB1. In another instance, suppose the first beam (beam 1) and the second beam (beam 2) are associated with different base stations (gNB1 and gNB2). For example, the first beam is associated with a base station (gNB1), and the second beam is associated with another base station (gNB2). In this case, beam 1 of gNB1 can be rotated by (θ, φ) degrees in azimuth and elevation to become beam 1 for gNB2. Alternatively, the second beam is associated with a base station (gNB1), and the first beam is associated with another base station (gNB2). For example, in cases where the respective gNBs share a beamform, the reference beam and the "transformed" beam can be associated with different gNBs (e.g., the respective gNBs may be using the same codebook or typically different codebooks, where some beams from codebook 1 of gNB1 can be mapped to some beams from codebook 2 of gNB2).

[0297] Referring to Figures 11 and 12, in some designs as indicated above, the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof (e.g., see examples of (θ, φ) rotation or offset as indicated above).

[0298] Referring to Figures 11 and 12, in some designs, the positioning estimation entity can provide a template of beamform to the base station. For example, the template may include a set of reference beams (e.g., one or more) whose beamform is known or defined (e.g., via specified phase and amplitude bits). Subsequently, other beams may be defined by referencing a corresponding reference beam (e.g., rotation and / or translation relative to that corresponding reference beam). In this case, transformation information can be based on the template. In some designs, the template may be configured in the form of a codebook, such that the gNB can define the beams by specifying transformations (e.g., rotation and / or translation) relative to the reference beams.

[0299] As can be seen in the detailed description above, different features are grouped together in the examples. This manner of disclosure should not be construed as an intention for the exemplary clauses to have more features than those explicitly mentioned in each clause. Rather, the various forms in this case may include fewer features than those of the single exemplary clause disclosed. Therefore, the following clauses should be considered as incorporated into the description herein, where each clause may be considered a separate instance. Although each dependent clause may be referenced in the clause as a specific combination with one of the other clauses, the form of that dependent clause is not limited to that specific combination. It will be understood that other exemplary clauses may also include combinations of the form of a dependent clause with the subject matter of any other dependent or independent clause, or any feature combined with other dependent and independent clauses. The various forms disclosed herein expressly include such combinations unless expressly stated or it can be readily inferred that a particular combination is not intended (e.g., contradictory forms, such as limiting an element to be both an insulator and a conductor). Furthermore, the form of an intended clause may be included in any other independent clause, even if that clause does not directly depend on the independent clause.

[0300] The following numbered clauses describe examples of implementation methods:

[0301] Clause 1. A method of operating a base station, comprising the steps of: determining an antenna configuration associated with the base station; determining a table mapping each antenna element in the antenna element set, associated with the antenna configuration, to a phase shift, or amplitude shift, or a combination thereof; reporting an instruction to the table to a positioning estimation entity; and reporting an instruction to the antenna configuration to the positioning estimation entity.

[0302] Clause 2. The method of Clause 1, wherein the table maps each antenna element to a set of antenna elements, or wherein the table maps each group of antenna elements associated with the same phase shift or the same amplitude shift to a set of antenna elements, or a combination thereof.

[0303] Clause 3. The method according to any one of Clauses 1 to 2, wherein the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0304] Clause 4. The method according to Clause 3, wherein the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0305] Clause 5. The method according to any one of Clauses 3 to 4, wherein the antenna spacing includes vertical antenna spacing, horizontal antenna spacing or a combination thereof.

[0306] Clause 6. The method of any one of Clauses 1 to 5, wherein the table maps each of the antenna elements in the antenna element set to at least a phase shift.

[0307] Clause 7. The method of Clause 6, wherein the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0308] Article 8. The method of any one of Articles 1 to 7, wherein the indication of the table also specifies the association of at least one antenna element with one or more Positioning Reference Signal (PRS) resources.

[0309] Clause 9. The method of any one of Clauses 1 to 8, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

[0310] Article 10. The method of any one of Articles 1 to 9, wherein the indication of the table is reported via location auxiliary data, or wherein the indication of the table is reported on demand.

[0311] Clause 11. A method for operating a positioning estimation entity, comprising the steps of: receiving from a base station an indication of an antenna configuration associated with the base station; receiving from the base station an indication of a table mapping each antenna element, which is a set of antenna elements and associated with the antenna configuration, to a phase shift, or amplitude shift, or a combination thereof; and determining beamform information of one or more antenna elements based on the indication of the antenna configuration and the indication of the table.

[0312] Clause 12. The method of Clause 11, wherein the indication of the table is received via location auxiliary data, or wherein the indication of the table is received on demand.

[0313] Article 13. The method of any one of Articles 11 to 12, wherein the table maps antenna element sets to each antenna element, or wherein the table maps antenna element sets, or combinations thereof, to each group of antenna elements associated with the same phase shift or the same amplitude shift.

[0314] Clause 14. The method according to any one of Clauses 11 to 13, wherein the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0315] Clause 15. The method according to Clause 14, wherein the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0316] Article 16. The method according to any one of Articles 14 to 15, wherein the antenna spacing includes vertical antenna spacing, horizontal antenna spacing or a combination thereof.

[0317] Clause 17. The method of any one of Clauses 11 to 16, wherein the table maps each of the antenna elements in the antenna element set to at least a phase shift.

[0318] Clause 18. The method according to Clause 17, wherein the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0319] Clause 19. The method of any one of Clauses 11 to 18, wherein the indication of the table also specifies the association of at least one antenna element with one or more Positioning Reference Signal (PRS) resources.

[0320] Clause 20. The method of any one of Clauses 11 to 19, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

[0321] Clause 21. A method of operating a base station, comprising the steps of: determining a first beam shape of a first beam; determining a second beam shape of a second beam; determining transformation information of the first beam shape of the first beam being transformed into the second beam shape of the second beam; and reporting the transformation information to a positioning estimation entity.

[0322] Clause 22. The method according to Clause 21, wherein the transformation information includes rotation information, translation information or a combination thereof.

[0323] Article 23. The method of any one of Articles 21 to 22, wherein the first beam and the second beam are associated with the base station.

[0324] Article 24. The method of any one of Articles 21 to 23, wherein the first beam is associated with a base station and the second beam is associated with another base station.

[0325] Article 25. The method of any one of Articles 21 to 24, wherein the second beam is associated with a base station and the first beam is associated with another base station.

[0326] Article 26. The method of any one of Articles 21 to 25, wherein the first beam is a reference beam associated with a known beam shape.

[0327] Article 27. The method of any one of Articles 21 to 26, wherein the transformation information includes azimuth angle offset, elevation angle offset or a combination thereof.

[0328] Clause 28. The method according to any one of Clauses 21 to 27 also includes the step of receiving a template of beam shape from a positioning estimation entity, wherein transformation information is based in part on the template.

[0329] Article 29. The method of any one of Articles 21 to 28, wherein the change information is reported via location auxiliary data, or wherein the change information is reported on demand.

[0330] Clause 30. A method for operational positioning estimation of an entity, comprising the steps of: receiving from a base station transformation information of a first beam shape of a first beam transformed therethrough into a second beam shape of a second beam; and determining, in part, the second beam shape of the second beam based on the transformation information.

[0331] Article 31. The method of Article 30, wherein the transformation information is received via location auxiliary data, or wherein the transformation information is received on demand.

[0332] Article 32. The method according to any one of Articles 30 to 31, wherein the transformation information includes rotation information, translation information or a combination thereof.

[0333] Article 33. The method of any one of Articles 30 to 32, wherein the first beam and the second beam are associated with the base station.

[0334] Article 34. The method of any one of Articles 30 to 33, wherein the first beam is associated with a base station and the second beam is associated with another base station.

[0335] Article 35. The method of any one of Articles 30 to 34, wherein the second beam is associated with a base station and the first beam is associated with another base station.

[0336] Article 36. The method of any one of Articles 30 to 35, wherein the first beam is a reference beam associated with a known beam shape.

[0337] Article 37. The method of any one of Articles 30 to 36, wherein the transformation information includes azimuth angle offset, elevation angle offset or a combination thereof.

[0338] Article 38. The method according to any one of Articles 30 to 37 also includes the following steps: transmitting a template of beam shape to the base station, wherein the transformation information is based in part on the template.

[0339] Clause 39. A base station comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine an antenna configuration associated with the base station; determine a table mapping each antenna element in an antenna configuration set to a phase shift, or amplitude shift, or a combination thereof; report an instruction to the table to a positioning estimation entity; and report an instruction to the antenna configuration to the positioning estimation entity.

[0340] Article 40. Base station pursuant to Article 39, wherein a table maps antenna element sets to each antenna element per day, or wherein a table maps antenna element sets, or combinations thereof, to each group of antenna elements associated with the same phase shift or the same amplitude shift.

[0341] Article 41. A base station under any of Articles 39 to 40, wherein the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0342] Clause 42. Base station pursuant to Clause 41, wherein the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0343] Article 43. A base station pursuant to any of Articles 41 to 42, wherein the antenna spacing includes vertical antenna spacing, horizontal antenna spacing, or a combination thereof.

[0344] Clause 44. A base station pursuant to any one of Clauses 39 to 43, wherein the table maps each of the antenna elements in the set to at least a phase shift.

[0345] Clause 45. Base station pursuant to Clause 44, wherein the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0346] Clause 46. A base station pursuant to any of Clauses 39 to 45, wherein the indication of the table also specifies the association of at least one antenna element with one or more Positioning Reference Signal (PRS) resources.

[0347] Clause 47. A base station pursuant to any of Clauses 39 to 46, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

[0348] Article 48. A base station pursuant to any of Articles 39 to 47, wherein the indication of the table is reported via location auxiliary data, or wherein the indication of the table is reported on demand.

[0349] Clause 49. A location estimation entity, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive from a base station via the at least one transceiver an indication of an antenna configuration associated with the base station; receive from the base station via the at least one transceiver an indication of mapping each antenna element, which is grouped together and associated with the antenna configuration, to a table of phase shifts, amplitude shifts, or combinations thereof; and determine beamform information of one or more antenna elements based on the indication of the antenna configuration and the indication of the table.

[0350] Article 50. A location estimation entity pursuant to Article 49, wherein the indication of the table is received via location auxiliary data, or wherein the indication of the table is received on demand.

[0351] Clause 51. A positioning estimation entity pursuant to any of Clauses 49 to 50, wherein a table maps antenna element sets to each antenna element, or wherein a table maps antenna element sets, or combinations thereof, to each group of antenna elements associated with the same phase shift or the same amplitude shift.

[0352] Clause 52. A location estimation entity according to any one of Clauses 49 to 51, wherein the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0353] Clause 53. The positioning estimation entity pursuant to Clause 52, wherein the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0354] Clause 54. A positioning estimation entity according to any one of Clauses 52 to 53, wherein the antenna spacing includes vertical antenna spacing, horizontal antenna spacing or a combination thereof.

[0355] Clause 55. A positioning estimation entity according to any one of Clauses 49 to 54, wherein the table maps each of the antenna elements in the antenna element set to at least a phase shift.

[0356] Clause 56. Positioning estimation entity according to Clause 55, wherein the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0357] Clause 57. A location estimation entity pursuant to any of Clauses 49 to 56, wherein the indication of the table also specifies the association of at least one antenna element with one or more location reference signal (PRS) resources.

[0358] Clause 58. A location estimation entity pursuant to any of Clauses 49 to 57, wherein the table indication and antenna configuration indication are reported via a single measurement report, or wherein the table indication and antenna configuration indication are reported via multiple measurement reports.

[0359] Clause 59. A base station comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: determine a first beam shape of a first beam; determine a second beam shape of a second beam; determine transformation information of the first beam shape of the first beam being transformed into the second beam shape of the second beam; and report the transformation information to a positioning estimation entity.

[0360] Article 60. Base station pursuant to Article 59, wherein transformation information includes rotation information, translation information or a combination thereof.

[0361] Article 61. A base station under any one of Articles 59 to 60, wherein the first beam and the second beam are associated with a base station.

[0362] Clause 62. A base station under any one of Clauses 59 to 61, wherein the first beam is associated with a base station and the second beam is associated with another base station.

[0363] Clause 63. A base station under any of Clauses 59 to 62, wherein the second beam is associated with a base station and the first beam is associated with another base station.

[0364] Clause 64. A base station pursuant to any of Clauses 59 to 63, wherein the first beam is a reference beam associated with a known beam shape.

[0365] Article 65. Base station pursuant to any of Articles 59 to 64, wherein the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0366] Clause 66. A base station according to any one of Clauses 59 to 65, wherein at least one processor is further configured to receive a template of beamform from a positioning estimation entity via at least one transceiver, wherein transformation information is based in part on the template.

[0367] Article 67. A base station pursuant to any of Articles 59 to 66, wherein change information is reported via location auxiliary data, or wherein change information is reported on demand.

[0368] Clause 68. A location estimation entity, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive from a base station via the at least one transceiver transformation information of a first beam shape of a first beam transformed therethrough into a second beam shape of a second beam; and determine a second beam shape of the second beam in part based on the transformation information.

[0369] Article 69. A location estimation entity pursuant to Article 68, wherein the transformation information is received via location auxiliary data, or wherein the transformation information is received on demand.

[0370] Article 70. A positioning estimation entity pursuant to any of Articles 68 to 69, wherein the transformation information includes rotation information, translation information, or a combination thereof.

[0371] Article 71. A location estimation entity according to any one of Articles 68 to 70, wherein the first beam and the second beam are associated with a base station.

[0372] Clause 72. A location estimation entity pursuant to any of Clauses 68 to 71, wherein the first beam is associated with a base station and the second beam is associated with another base station.

[0373] Clause 73. A location estimation entity pursuant to any of Clauses 68 to 72, wherein the second beam is associated with a base station and the first beam is associated with another base station.

[0374] Clause 74. A positioning estimation entity pursuant to any of Clauses 68 to 73, wherein the first beam is a reference beam associated with a known beam shape.

[0375] Clause 75. A positioning estimation entity pursuant to any of Clauses 68 to 74, wherein the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0376] Clause 76. A positioning estimation entity according to any one of Clauses 68 to 75, wherein at least one processor is further configured to: transmit a template of beamform to a base station via at least one transceiver, wherein transformation information is based in part on the template.

[0377] Clause 77. A base station comprising: means for determining an antenna configuration associated with the base station; means for determining a table mapping each antenna element of an antenna configuration to a phase shift, or amplitude shift, or a combination thereof; means for reporting an indication of the table to a positioning estimation entity; and means for reporting an indication of the antenna configuration to the positioning estimation entity.

[0378] Article 78. Base station pursuant to Article 77, wherein a table maps antenna element sets to each antenna element per day, or wherein a table maps antenna element sets, or combinations thereof, to each group of antenna elements associated with the same phase shift or the same amplitude shift.

[0379] Clause 79. A base station pursuant to any of Clauses 77 to 78, wherein the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0380] Clause 80. Base station pursuant to Clause 79, wherein the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0381] Article 81. A base station pursuant to any of Articles 79 to 80, wherein the antenna spacing includes vertical antenna spacing, horizontal antenna spacing or a combination thereof.

[0382] Article 82. A base station pursuant to any one of Articles 77 to 81, wherein the table maps each of the antenna elements in the set to at least a phase shift.

[0383] Clause 83. Base station pursuant to Clause 82, wherein the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0384] Clause 84. A base station pursuant to any of Clauses 77 to 83, wherein the indication of the table also specifies the association of at least one antenna element with one or more Positioning Reference Signal (PRS) resources.

[0385] Article 85. A base station pursuant to any of Articles 77 to 84, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

[0386] Article 86. A base station pursuant to any of Articles 77 to 85, wherein the indication of the table is reported via location auxiliary data, or wherein the indication of the table is reported on demand.

[0387] Clause 87. A positioning estimation entity comprising: means for receiving from a base station an indication of an antenna configuration associated with the base station; means for receiving from the base station an indication of a table mapping each antenna element, which is an aggregate of antenna elements and associated with the antenna configuration, to a phase shift, or amplitude shift, or a combination thereof; and means for determining beamform information of one or more antenna elements based on the indication of the antenna configuration and the indication of the table.

[0388] Article 88. A location estimation entity pursuant to Article 87, wherein the indication of the table is received via location auxiliary data, or wherein the indication of the table is received on demand.

[0389] Article 89. A positioning estimation entity pursuant to any one of Articles 87 to 88, wherein a table maps antenna element sets to each antenna element, or wherein a table maps antenna element sets, or combinations thereof, to each group of antenna elements associated with the same phase shift or the same amplitude shift.

[0390] Clause 90. A location estimation entity pursuant to any of Clauses 87 to 89, wherein the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0391] Article 91. The positioning estimation entity pursuant to Article 90, wherein the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0392] Article 92. A positioning estimation entity according to any one of Articles 90 to 91, wherein the antenna spacing includes vertical antenna spacing, horizontal antenna spacing or a combination thereof.

[0393] Clause 93. A positioning estimation entity according to any one of Clauses 87 to 92, wherein the table maps each of the antenna elements in the antenna element set to at least a phase shift.

[0394] Clause 94. Positioning estimation entity according to Clause 93, wherein the table maps at least one antenna element in the antenna element set to both phase shift and amplitude shift.

[0395] Clause 95. A location estimation entity pursuant to any of Clauses 87 to 94, wherein the indication of the table also specifies the association of at least one antenna element with one or more location reference signal (PRS) resources.

[0396] Clause 96. A location estimation entity pursuant to any of Clauses 87 to 95, wherein the table indication and the antenna configuration indication are reported via a single measurement report, or wherein the table indication and the antenna configuration indication are reported via multiple measurement reports.

[0397] Clause 97. A base station, comprising: a component for determining a first beam shape of a first beam; a component for determining a second beam shape of a second beam; a component for determining transformation information of the first beam shape of the first beam being transformed into the second beam shape of the second beam; and a component for reporting the transformation information to a positioning estimation entity.

[0398] Article 98. Base station pursuant to Article 97, wherein transformation information includes rotation information, translation information or a combination thereof.

[0399] Article 99. A base station under any one of Articles 97 to 98, wherein the first beam and the second beam are associated with the base station.

[0400] Clause 100. A base station under any one of Clauses 97 to 99, wherein the first beam is associated with a base station and the second beam is associated with another base station.

[0401] Article 101. A base station pursuant to any one of Articles 97 to 100, wherein the second beam is associated with a base station and the first beam is associated with another base station.

[0402] Article 102. A base station pursuant to any of Articles 97 to 101, wherein the first beam is a reference beam associated with a known beam shape.

[0403] Article 103. Base station pursuant to any of Articles 97 to 102, wherein the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0404] Clause 104. A base station pursuant to any one of Clauses 97 to 103 also includes: a component for receiving a template of beam shape from a positioning estimation entity, wherein transformation information is based in part on the template.

[0405] Article 105. A base station pursuant to any of Articles 97 to 104, wherein change information is reported via location auxiliary data, or wherein change information is reported on demand.

[0406] Clause 106. A positioning estimation entity, comprising: a component for receiving transformation information from a base station of a first beam shape of a first beam transformed therethrough into a second beam shape of a second beam; and a component for determining the second beam shape of the second beam in part based on the transformation information.

[0407] Article 107. A location estimation entity pursuant to Article 106, wherein the transformation information is received via location auxiliary data, or wherein the transformation information is received on demand.

[0408] Clause 108. A positioning estimation entity pursuant to any of Clauses 106 to 107, wherein the transformation information includes rotation information, translation information, or a combination thereof.

[0409] Article 109. A location estimation entity according to any one of Articles 106 to 108, wherein the first beam and the second beam are associated with a base station.

[0410] Article 110. A location estimation entity pursuant to any of Articles 106 to 109, wherein the first beam is associated with a base station and the second beam is associated with another base station.

[0411] Article 111. A location estimation entity according to any one of Articles 106 to 110, wherein the second beam is associated with a base station and the first beam is associated with another base station.

[0412] Clause 112. A positioning estimation entity pursuant to any of Clauses 106 to 111, wherein the first beam is a reference beam associated with a known beam shape.

[0413] Article 113. A positioning estimation entity pursuant to any of Articles 106 to 112, wherein the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0414] Clause 114. The positioning estimation entity pursuant to any one of Clauses 106 to 113 also includes: a component for transmitting a template of beamform to a base station, wherein the transformation information is based in part on the template.

[0415] Clause 115. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a base station, cause the base station to: determine an antenna configuration associated with the base station; determine a table mapping each antenna element in a set of antenna elements associated with the antenna configuration to a phase shift, or amplitude shift, or a combination thereof; report instructions to a positioning estimation entity to the table; and report instructions to a positioning estimation entity to the antenna configuration.

[0416] Clause 116. A non-transitory computer-readable medium pursuant to Clause 115, wherein a table maps a set of antenna elements to each antenna element, or a table maps a set of antenna elements, or a combination thereof, to each group of antenna elements associated with the same phase shift or the same amplitude shift.

[0417] Clause 117. A non-transitory computer-readable medium pursuant to any of Clauses 115 to 116, wherein the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0418] Clause 118. Non-transitory computer-readable media pursuant to Clause 117, wherein the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0419] Article 119. A non-transitory computer-readable medium pursuant to any of Articles 117 to 118, wherein the antenna spacing includes vertical antenna spacing, horizontal antenna spacing, or a combination thereof.

[0420] Clause 120. A non-transitory computer-readable medium pursuant to any one of Clauses 115 to 119, wherein the table maps each of the antenna elements in the set to at least a phase shift.

[0421] Clause 121. A non-transitory computer-readable medium pursuant to Clause 120, wherein a table maps at least one antenna element in an antenna element set to both phase shift and amplitude shift.

[0422] Clause 122. A non-transitory computer-readable medium pursuant to any of Clauses 115 to 121, wherein the indication of the table also specifies the association of at least one antenna element with one or more Positioning Reference Signal (PRS) resources.

[0423] Clause 123. A non-transitory computer-readable medium pursuant to any of Clauses 115 to 122, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

[0424] Article 124. A non-transitory computer-readable medium pursuant to any of Articles 115 to 123, wherein the instructions of the table are reported via location-assisted information or wherein the instructions of the table are reported on demand.

[0425] Clause 125. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a positioning estimation entity, cause the positioning estimation entity to: receive from a base station an instruction on an antenna configuration associated with the base station; receive from the base station an instruction on a table mapping each antenna element, which is a set of antenna elements and associated with the antenna configuration, to a phase shift, or amplitude shift, or a combination thereof; and determine beamform information of one or more antenna elements based on the instruction on the antenna configuration and the instruction on the table.

[0426] Article 126. Non-transitory computer-readable media pursuant to Article 125, wherein the instructions of the table are received via location auxiliary data, or wherein the instructions of the table are received on demand.

[0427] Clause 127. A non-transitory computer-readable medium pursuant to any of Clauses 125 to 126, wherein a table maps a set of antenna elements to each antenna element, or a table maps a set of antenna elements, or a combination thereof, to each group of antenna elements associated with the same phase shift or the same amplitude shift.

[0428] Clause 128. A non-transitory computer-readable medium pursuant to any of Clauses 125 to 127, wherein the antenna configuration includes the number of antenna elements in the antenna element set, the antenna spacing associated with the antenna element set, or a combination thereof.

[0429] Clause 129. Non-transitory computer-readable media pursuant to Clause 128, wherein the number of antenna elements includes the number of vertical antenna elements, the number of horizontal antenna elements, or a combination thereof.

[0430] Clause 130. A non-transitory computer-readable medium pursuant to any of Clauses 128 to 129, wherein the antenna spacing includes vertical antenna spacing, horizontal antenna spacing, or a combination thereof.

[0431] Clause 131. A non-transitory computer-readable medium pursuant to any one of Clauses 125 to 130, wherein the table maps each of the antenna elements in the set to at least a phase shift.

[0432] Clause 132. A non-transitory computer-readable medium pursuant to Clause 131, wherein a table maps at least one antenna element in an antenna element set to both phase shift and amplitude shift.

[0433] Clause 133. A non-transitory computer-readable medium pursuant to any of Clauses 125 to 132, wherein the indication of the table also specifies the association of at least one antenna element with one or more Positioning Reference Signal (PRS) resources.

[0434] Clause 134. A non-transitory computer-readable medium pursuant to any of Clauses 125 to 133, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

[0435] Clause 135. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a base station, cause the base station to: determine a first beam shape of a first beam; determine a second beam shape of a second beam; determine transformation information of the first beam shape of the first beam being transformed into the second beam shape of the second beam; and report the transformation information to a positioning estimation entity.

[0436] Clause 136. Non-transitory computer-readable media pursuant to Clause 135, wherein transformation information includes rotation information, translation information, or a combination thereof.

[0437] Clause 137. Non-transitory computer-readable media pursuant to any of Clauses 135 to 136, wherein the first beam and the second beam are associated with a base station.

[0438] Clause 138. A non-transitory computer-readable medium pursuant to any of Clauses 135 to 137, wherein a first beam is associated with a base station and a second beam is associated with another base station.

[0439] Clause 139. A non-transitory computer-readable medium pursuant to any of Clauses 135 to 138, wherein the second beam is associated with a base station and the first beam is associated with another base station.

[0440] Clause 140. A non-transitory computer-readable medium pursuant to any of Clauses 135 to 139, wherein the first beam is a reference beam associated with a known beam shape.

[0441] Article 141. A non-transitory computer-readable medium pursuant to any of Articles 135 to 140, wherein the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0442] Clause 142. The non-transitory computer-readable medium pursuant to any of Clauses 135 to 141 also includes: instructions which, when performed by the base station, further cause the base station to perform the following operations: receive a template of beamform from a positioning estimation entity, wherein the transformation information is based in part on the template.

[0443] Clause 143. A non-transitory computer-readable medium pursuant to any of Clauses 135 to 142, wherein change information is reported via location-aided data or wherein change information is reported on demand.

[0444] Clause 144. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a positioning estimation entity, cause the positioning estimation entity to: receive transformation information from a base station of a first beam shape of a first beam transformed therethrough into a second beam shape of a second beam; and determine, in part based on the transformation information, a second beam shape of the second beam.

[0445] Article 145. Non-transitory computer-readable media pursuant to Article 144, wherein the transformation information is received via location-aided information or wherein the transformation information is received on demand.

[0446] Article 146. A non-transitory computer-readable medium pursuant to any of Articles 144 to 145, wherein transformation information includes rotation information, translation information, or a combination thereof.

[0447] Article 147. Non-transitory computer-readable media pursuant to any one of Articles 144 to 146, wherein the first beam and the second beam are associated with a base station.

[0448] Clause 148. A non-transitory computer-readable medium pursuant to any of Clauses 144 to 147, wherein a first beam is associated with a base station and a second beam is associated with another base station.

[0449] Clause 149. A non-transitory computer-readable medium pursuant to any of Clauses 144 to 148, wherein the second beam is associated with a base station and the first beam is associated with another base station.

[0450] Clause 150. A non-transitory computer-readable medium pursuant to any of Clauses 144 to 149, wherein the first beam is a reference beam associated with a known beam shape.

[0451] Clause 151. A non-transitory computer-readable medium pursuant to any of Clauses 144 to 150, wherein the transformation information includes azimuth angle offset, elevation angle offset, or a combination thereof.

[0452] Clause 152. The non-transitory computer-readable medium pursuant to any of Clauses 144 to 151 also includes: instructions which, when performed by the positioning estimation entity, also cause the positioning estimation entity to perform the following operations: transmit a template of beamform to the base station, wherein the transformation information is based in part on the template.

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

[0454] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and algorithm steps described herein in conjunction with the various forms disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various illustrative elements, blocks, modules, circuits, and steps have been generally described above in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in varying ways for each specific application, but such implementation decisions should not be construed as leading outside the scope of this work.

[0455] The various illustrative logic blocks, modules, and circuits described herein can be implemented or executed using a general-purpose processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device, individual gate or transistor logic, individual hardware element, or any combination thereof, designed to perform the functions described herein. The general-purpose processor can be a microprocessor, but alternatively, the processor can be any conventional processor, controller, microcontroller, or state machine. The 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 incorporating a DSP core, or any other such configuration.

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

[0457] In one or more exemplary embodiments, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, such functionality may be stored as one or more instructions or code on or transmitted via a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, and communication media includes any media that facilitates the transfer of computer programs from one place to another. Storage media may be any available media that can be accessed by a computer. For example, and not as a limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, magnetic disk storage 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 that can be accessed by a computer. Similarly, 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 (such as infrared, radio, and microwave), then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) are all included in the definition of media. As used herein, magnetic disks and optical disks include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where magnetic disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0458] Although the foregoing disclosure illustrates an illustrative form of this case, it should be noted that various changes and modifications may be made herein without departing from the scope of this case as defined by the appended claims. The functions, steps, and / or actions of the method claims of the various forms of this case described herein need not be performed in any particular order. Furthermore, although elements of this case may be described or claimed in the singular, the plural form is also considered unless expressly stated to be limited to the singular. [Simplified Explanation of the Diagram]

[0158] The accompanying drawings are provided to help describe the various aspects of this case, and the drawings are provided only to illustrate the various aspects, not to limit them.

[0159] Figure 1 illustrates an exemplary wireless communication system according to various aspects of this case.

[0160] Figures 2A and 2B illustrate exemplary wireless network structures according to various forms of this case.

[0161] Figures 3A, 3B and 3C are simplified block diagrams of several sampled states of elements that can be adopted in user equipment (UE), base station and network entity respectively and configured to support communications as taught herein.

[0162] Figure 4 is a diagram illustrating an exemplary frame structure according to various states of this case.

[0163] Figure 5 is a diagram illustrating various downlink channels in a slot for an exemplary downlink according to the various states of this case.

[0164] Figure 6 is a diagram illustrating an exemplary downlink positioning reference signal (DL-PRS) configuration for two transmit receiver points (TRPs) operating in the same positioning frequency layer, according to various forms of this case.

[0165] Figure 7 illustrates examples of various positioning methods supported in the new radio (NR) according to the various types of this case.

[0166] Figure 8 is a diagram illustrating an exemplary base station communicating with an exemplary UE according to various forms of this case.

[0167] Figure 9 illustrates an exemplary process of communication according to various forms of this case.

[0168] Figure 10 illustrates an exemplary process of communication according to various forms of this case.

[0169] Figure 11 illustrates an exemplary process of communication according to various forms of this case.

[0170] Figure 12 illustrates an exemplary process of communication according to various forms of this case. [Biomaterial Storage]

[0460] Domestic storage information (please note in order of storage institution, date, and number): None. International storage information (please note in order of storage country, institution, date, and number): None.

Claims

1. A method of operating a base station, comprising the steps of: determining an antenna configuration associated with the base station; determining a table that maps each antenna element in an antenna element set associated with the antenna configuration to a phase shift, or a span shift, or a combination thereof; reporting an indication of the table to a positioning estimation entity; and reporting an indication of the antenna configuration to the positioning estimation entity.

2. The method according to claim 1, wherein the table maps the antenna element set to each antenna element, or wherein the table maps the antenna element set to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

3. The method of claim 1, wherein the antenna configuration includes a number of antenna elements in the antenna element set, an antenna spacing associated with the antenna element set, or a combination thereof.

4. The method according to claim 3, wherein the number of antenna elements includes a number of vertical antenna elements, a number of horizontal antenna elements, or a combination thereof.

5. The method according to claim 3, wherein the antenna spacing includes a vertical antenna spacing, a horizontal antenna spacing, or a combination thereof.

6. The method according to claim 1, wherein the table maps each antenna element of the antenna element set to at least the phase shift.

7. The method according to claim 6, wherein the table maps at least one antenna element in the antenna element set to both the phase shift and the amplitude shift.

8. The method according to claim 1, wherein the indication of the table also specifies an association between at least one antenna element and one or more Positioning Reference Signal (PRS) resources.

9. The method according to claim 1, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

10. The method according to claim 1, wherein the indication of the table is reported via location auxiliary data, or wherein the indication of the table is reported on demand.

11. A method of operating a positioning estimation entity, comprising the steps of: receiving from a base station an indication of an antenna configuration associated with the base station; receiving from the base station an indication of a table mapping each antenna element in an antenna element set associated with the antenna configuration to a phase shift, or a span shift, or a combination thereof; and determining beamform information of one or more antenna elements based on the indication of the antenna configuration and the indication of the table.

12. The method according to request item 11, wherein the indication of the table is received via location auxiliary data, or wherein the indication of the table is received on demand.

13. The method of claim 11, wherein the table maps the antenna element set to each antenna element, or wherein the table maps the antenna element set to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

14. The method of claim 11, wherein the antenna configuration includes a number of antenna elements in the antenna element set, an antenna spacing associated with the antenna element set, or a combination thereof.

15. The method according to claim 14, wherein the number of antenna elements includes a number of vertical antenna elements, a number of horizontal antenna elements, or a combination thereof.

16. The method according to claim 14, wherein the antenna spacing includes a vertical antenna spacing, a horizontal antenna spacing, or a combination thereof.

17. The method of claim 11, wherein the table maps each of the antenna elements in the antenna element set to at least the phase shift.

18. The method according to claim 17, wherein the table maps at least one antenna element in the antenna element set to both the phase shift and the amplitude shift.

19. The method according to claim 11, wherein the indication of the table also specifies an association between at least one antenna element and one or more Positioning Reference Signal (PRS) resources.

20. The method according to claim 11, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

21. A method of operating a base station, comprising the steps of: determining a first beam shape of a first beam; determining a second beam shape of a second beam; determining transformation information of the first beam shape of the first beam being transformed into the second beam shape of the second beam; and reporting the transformation information to a positioning estimation entity.

22. The method according to claim 21, wherein the transformation information includes rotation information, translation information, or a combination thereof.

23. The method of request item 21, wherein the first beam and the second beam are associated with the base station.

24. The method of claim 21, wherein the first beam is associated with the base station and the second beam is associated with another base station.

25. The method of claim 21, wherein the second beam is associated with the base station and the first beam is associated with another base station.

26. The method of claim 21, wherein the first beam is a reference beam associated with a known beam shape.

27. The method according to request 21, wherein the transformation information includes a azimuth angle offset, an elevation angle offset, or a combination thereof.

28. The method according to claim 21 also includes the following steps: receiving a template of beam shape from the positioning estimation entity, wherein the transformation information is partially based on the template.

29. The method according to claim 21, wherein the transformation information is reported via location auxiliary data, or wherein the transformation information is reported on demand.

30. A method of operating a location estimation entity, comprising the steps of: receiving from a base station transformation information of a first beam shape of a first beam transformed therethrough into a second beam shape of a second beam; and determining the second beam shape of the second beam in part based on the transformation information.

31. The method according to request 30, wherein the transformation information is received via location auxiliary data, or wherein the transformation information is received on demand.

32. The method according to claim 30, wherein the transformation information includes rotation information, translation information, or a combination thereof.

33. The method according to claim 30, wherein the first beam and the second beam are associated with the base station.

34. The method of claim 30, wherein the first beam is associated with the base station and the second beam is associated with another base station.

35. The method of claim 30, wherein the second beam is associated with the base station and the first beam is associated with another base station.

36. The method of claim 30, wherein the first beam is a reference beam associated with a known beam shape.

37. The method according to request 30, wherein the transformation information includes a azimuth angle offset, an elevation angle offset, or a combination thereof.

38. The method according to claim 30 also includes the following steps: transmitting a template of beamform to the base station, wherein the transformation information is partially based on the template.

39. A base station, comprising: One 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: determine an antenna configuration associated with the base station; determine a table mapping each antenna element in an antenna element set associated with the antenna configuration to a phase shift, a span shift, or a combination thereof; report an indication of the table to a location estimation entity; and report an indication of the antenna configuration to the location estimation entity.

40. The base station according to claim 39, wherein the table maps the antenna element set to each antenna element per day, or wherein the table maps the antenna element set to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

41. The base station according to claim 39, wherein the antenna configuration includes a number of antenna elements in the antenna element set, an antenna spacing associated with the antenna element set, or a combination thereof.

42. The base station according to claim 41, wherein the number of antenna elements includes a number of vertical antenna elements, a number of horizontal antenna elements, or a combination thereof.

43. The base station according to claim 41, wherein the antenna spacing includes vertical antenna spacing, horizontal antenna spacing, or a combination thereof.

44. The base station according to claim 39, wherein the table maps each of the antenna elements in the antenna element set to at least the phase shift.

45. A base station according to claim 44, wherein the table maps at least one antenna element in the antenna element set to both the phase shift and the amplitude shift.

46. ​​The base station according to claim 39, wherein the indication in the table also specifies an association between at least one antenna element and one or more Positioning Reference Signal (PRS) resources.

47. The base station according to claim 39, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

48. The base station pursuant to request item 39, wherein the indication in the table is reported via location auxiliary data, or wherein the indication in the table is reported on demand.

49. A location estimation entity, comprising: One memory; At least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor being configured to: receive, via the at least one transceiver, an indication of an antenna configuration associated with the base station from a base station; receive, via the at least one transceiver, an indication of a table mapping each antenna element of an antenna configuration to a phase shift, a span shift, or a combination thereof from the base station; and determine beamform information of one or more antenna elements based on the indication of the antenna configuration and the indication of the table.

50. The location estimation entity according to request item 49, wherein the indication of the table is received via location auxiliary data, or wherein the indication of the table is received on demand.

51. The positioning estimation entity according to claim 49, wherein the table maps the antenna element set to each antenna element, or wherein the table maps the antenna element set to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

52. The positioning estimation entity according to claim 49, wherein the antenna configuration includes a number of antenna elements in the antenna element set, an antenna spacing associated with the antenna element set, or a combination thereof.

53. The positioning estimation entity according to claim 52, wherein the number of antenna elements includes a number of vertical antenna elements, a number of horizontal antenna elements, or a combination thereof.

54. The positioning estimation entity according to claim 52, wherein the antenna spacing includes vertical antenna spacing, horizontal antenna spacing, or a combination thereof.

55. The positioning estimation entity according to claim 49, wherein the table maps each antenna element of the antenna element set to at least the phase shift.

56. The positioning estimation entity according to claim 55, wherein the table maps at least one antenna element in the antenna element set to both the phase shift and the amplitude shift.

57. The positioning estimation entity according to claim 49, wherein the indication of the table also specifies an association between at least one antenna element and one or more positioning reference signal (PRS) resources.

58. The positioning estimation entity according to claim 49, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

59. A base station, comprising: One 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: determine a first beam shape of a first beam; determine a second beam shape of a second beam; determine transformation information of the first beam shape of the first beam via which it is transformed into the second beam shape of the second beam; and report the transformation information to a positioning estimation entity.

60. The base station according to request item 59, wherein the transformation information includes rotation information, translation information, or a combination thereof.

61. The base station according to request item 59, wherein the first beam and the second beam are associated with the base station.

62. The base station according to request item 59, wherein the first beam is associated with the base station and the second beam is associated with another base station.

63. The base station according to claim 59, wherein the second beam is associated with the base station and the first beam is associated with another base station.

64. The base station according to request item 59, wherein the first beam is a reference beam associated with a known beam shape.

65. The base station according to request item 59, wherein the transformation information includes an azimuth angle offset, an elevation angle offset, or a combination thereof.

66. The base station according to claim 59, wherein the at least one processor is further configured to: receive a template of beamform from the positioning estimation entity via the at least one transceiver, wherein the transformation information is partially based on the template.

67. The base station according to request item 59, wherein the change information is reported via location auxiliary data, or wherein the change information is reported on demand.

68. A location estimation entity, comprising: One memory; At least one transceiver; The system 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 from a base station via the at least one transceiver information of transformation information of a first beam shape of a first beam transformed into a second beam shape of a second beam; and determine the second beam shape of the second beam in part based on the transformation information.

69. The positioning estimation entity according to request item 68, wherein the transformation information is received via location auxiliary data, or wherein the transformation information is received on demand.

70. The positioning estimation entity according to request item 68, wherein the transformation information includes rotation information, translation information, or a combination thereof.

71. The location estimation entity according to request item 68, wherein the first beam and the second beam are associated with the base station.

72. The location estimation entity according to request item 68, wherein the first beam is associated with the base station and the second beam is associated with another base station.

73. The location estimation entity according to request item 68, wherein the second beam is associated with the base station and the first beam is associated with another base station.

74. The positioning estimation entity according to request item 68, wherein the first beam is a reference beam associated with a known beam shape.

75. The positioning estimation entity according to request item 68, wherein the transformation information includes a azimuth angle offset, an elevation angle offset, or a combination thereof.

76. The positioning estimation entity according to claim 68, wherein the at least one processor is further configured to: transmit a template of beamform to the base station via the at least one transceiver, wherein the transformation information is partially based on the template.

77. A base station, comprising: Components used to determine the configuration of an antenna associated with the base station; A component for determining a table that maps each antenna element in an antenna element set associated with the antenna configuration to a phase shift, a span shift, or a combination thereof; a component for reporting an indication of the table to a positioning estimation entity; and a component for reporting an indication of the antenna configuration to the positioning estimation entity.

78. The base station according to claim 77, wherein the table maps the antenna element set to each antenna element per day, or wherein the table maps the antenna element set to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

79. The base station according to claim 77, wherein the antenna configuration includes a number of antenna elements in the antenna element set, an antenna spacing associated with the antenna element set, or a combination thereof.

80. The base station according to claim 79, wherein the number of antenna elements includes a number of vertical antenna elements, a number of horizontal antenna elements, or a combination thereof.

81. The base station according to claim 79, wherein the antenna spacing includes vertical antenna spacing, horizontal antenna spacing, or a combination thereof.

82. The base station according to claim 77, wherein the table maps each of the antenna elements in the antenna element set to at least the phase shift.

83. The base station according to claim 82, wherein the table maps at least one antenna element in the antenna element set to both the phase shift and the amplitude shift.

84. The base station according to claim 77, wherein the indication of the table also specifies an association between at least one antenna element and one or more Positioning Reference Signal (PRS) resources.

85. The base station pursuant to claim 77, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

86. The base station pursuant to request item 77, wherein the indication in the table is reported via location auxiliary data, or wherein the indication in the table is reported on demand.

87. A location estimation entity, comprising: A component for receiving an indication of an antenna configuration associated with a base station from a base station; A component for receiving from the base station an indication of a table that maps each antenna element, which is an array of antenna elements and associated with the antenna configuration, to a phase shift, a beam shift, or a combination thereof; and a component for determining beamform information of one or more antenna elements based on the indication of the antenna configuration and the indication of the table.

88. The location estimation entity according to request item 87, wherein the indication of the table is received via location auxiliary data, or wherein the indication of the table is received on demand.

89. The positioning estimation entity according to claim 87, wherein the table maps the antenna element set to each antenna element, or wherein the table maps the antenna element set to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

90. The positioning estimation entity according to claim 87, wherein the antenna configuration includes a number of antenna elements in the antenna element set, an antenna spacing associated with the antenna element set, or a combination thereof.

91. The positioning estimation entity according to claim 90, wherein the number of antenna elements includes a number of vertical antenna elements, a number of horizontal antenna elements, or a combination thereof.

92. The positioning estimation entity according to claim 90, wherein the antenna spacing includes vertical antenna spacing, horizontal antenna spacing, or a combination thereof.

93. The positioning estimation entity according to claim 87, wherein the table maps each antenna element of the antenna element set to at least the phase shift.

94. The positioning estimation entity according to claim 93, wherein the table maps at least one antenna element in the antenna element set to both the phase shift and the amplitude shift.

95. The positioning estimation entity according to claim 87, wherein the indication of the table also specifies an association between at least one antenna element and one or more positioning reference signal (PRS) resources.

96. The positioning estimation entity according to claim 87, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

97. A base station, comprising: A component used to determine the shape of a first beam; A component used to determine the shape of a second beam; A component for determining transformation information of the first beam shape of the first beam through which it is transformed into the second beam shape of the second beam; and a component for reporting the transformation information to a positioning estimation entity.

98. The base station according to request 97, wherein the transformation information includes rotation information, translation information, or a combination thereof.

99. The base station according to request item 97, wherein the first beam and the second beam are associated with the base station.

100. The base station according to request item 97, wherein the first beam is associated with the base station and the second beam is associated with another base station.

101. The base station according to request item 97, wherein the second beam is associated with the base station and the first beam is associated with another base station.

102. The base station according to request item 97, wherein the first beam is a reference beam associated with a known beam shape.

103. The base station according to request item 97, wherein the transformation information includes an azimuth angle offset, an elevation angle offset, or a combination thereof.

104. The base station pursuant to request item 97 also includes: A component for receiving a template of beam shape from the positioning estimation entity, wherein the transformation information is partially based on the template.

105. The base station according to request item 97, wherein the change information is reported via location auxiliary data, or wherein the change information is reported on demand.

106. A location estimation entity, comprising: A component for receiving transformation information from a base station of a first beam shape of a first beam and transforming it into a second beam shape of a second beam. And a component for determining the shape of the second beam in part based on the transformation information.

107. The positioning estimation entity according to request item 106, wherein the transformation information is received via location auxiliary data, or wherein the transformation information is received on demand.

108. The positioning estimation entity according to request item 106, wherein the transformation information includes rotation information, translation information, or a combination thereof.

109. The location estimation entity according to request item 106, wherein the first beam and the second beam are associated with the base station.

110. The location estimation entity according to request item 106, wherein the first beam is associated with the base station and the second beam is associated with another base station.

111. The location estimation entity according to request item 106, wherein the second beam is associated with the base station and the first beam is associated with another base station.

112. The positioning estimation entity according to request item 106, wherein the first beam is a reference beam associated with a known beam shape.

113. The positioning estimation entity according to request item 106, wherein the transformation information includes a azimuth angle offset, an elevation angle offset, or a combination thereof.

114. The location estimation entity according to request item 106 also includes: A component used to transmit a template of beam shape to the base station, wherein the transformation information is partially based on the template.

115. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a base station, cause the base station to: determine an antenna configuration associated with the base station; determine a table mapping each antenna element in an antenna element set associated with the antenna configuration to a phase shift, a span shift, or a combination thereof; report an indication of the table to a positioning estimation entity; and report an indication of the antenna configuration to the positioning estimation entity.

116. A non-transitory computer-readable medium according to claim 115, wherein the table maps the antenna element set to each antenna element, or wherein the table maps the antenna element set to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

117. The non-transitory computer-readable medium according to claim 115, wherein the antenna configuration includes a number of antenna elements in the antenna element set, an antenna spacing associated with the antenna element set, or a combination thereof.

118. The non-transitory computer-readable medium according to claim 117, wherein the number of antenna elements includes a number of vertical antenna elements, a number of horizontal antenna elements, or a combination thereof.

119. The non-transitory computer-readable medium according to claim 117, wherein the antenna spacing includes a vertical antenna spacing, a horizontal antenna spacing, or a combination thereof.

120. A non-transitory computer-readable medium according to claim 115, wherein the table maps each of the antenna elements in the antenna element set to at least the phase shift.

121. A non-transitory computer-readable medium according to claim 120, wherein the table maps at least one antenna element in the antenna element set to both the phase shift and the amplitude shift.

122. The non-transitory computer-readable medium pursuant to claim 115, wherein the indication of the table also specifies an association between at least one antenna element and one or more Positioning Reference Signal (PRS) resources.

123. The non-transitory computer-readable medium according to claim 115, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

124. The non-transitory computer-readable medium pursuant to request item 115, wherein the indication of the table is reported via location-aided data, or wherein the indication of the table is reported on demand.

125. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a positioning estimation entity, cause the positioning estimation entity to: receive from a base station an indication of an antenna configuration associated with the base station; receive from the base station an indication of a table mapping each antenna element in an antenna configuration to a phase shift, a beam shift, or a combination thereof; and determine beamform information of one or more antenna elements based on the indication of the antenna configuration and the indication of the table.

126. The non-transitory computer-readable medium pursuant to request item 125, wherein the instruction of the table is received via location auxiliary data, or wherein the instruction of the table is received on demand.

127. A non-transitory computer-readable medium according to claim 125, wherein the table maps the antenna element set to each antenna element, or wherein the table maps the antenna element set to each group of antenna elements associated with the same phase shift or the same amplitude shift, or a combination thereof.

128. The non-transitory computer-readable medium according to claim 125, wherein the antenna configuration includes a number of antenna elements in the antenna element set, an antenna spacing associated with the antenna element set, or a combination thereof.

129. The non-transitory computer-readable medium according to claim 128, wherein the number of antenna elements includes a number of vertical antenna elements, a number of horizontal antenna elements, or a combination thereof.

130. The non-transitory computer-readable medium according to claim 128, wherein the antenna spacing includes a vertical antenna spacing, a horizontal antenna spacing, or a combination thereof.

131. A non-transitory computer-readable medium according to claim 125, wherein the table maps each of the antenna elements in the antenna element set to at least the phase shift.

132. A non-transitory computer-readable medium according to claim 131, wherein the table maps at least one antenna element in the antenna element set to both the phase shift and the amplitude shift.

133. The non-transitory computer-readable medium pursuant to claim 125, wherein the indication of the table also specifies an association between at least one antenna element and one or more Positioning Reference Signal (PRS) resources.

134. The non-transitory computer-readable medium according to claim 125, wherein the indication of the table and the indication of the antenna configuration are reported via a single measurement report, or wherein the indication of the table and the indication of the antenna configuration are reported via multiple measurement reports.

135. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a base station, cause the base station to: determine a first beam shape of a first beam; determine a second beam shape of a second beam; determine transformation information of the first beam shape of the first beam transformed into the second beam shape of the second beam; and report the transformation information to a positioning estimation entity.

136. The non-transitory computer-readable medium pursuant to claim 135, wherein the transformation information includes rotation information, translation information, or a combination thereof.

137. The non-transitory computer-readable medium pursuant to request item 135, wherein the first beam and the second beam are associated with the base station.

138. The non-transitory computer-readable medium pursuant to request item 135, wherein the first beam is associated with the base station and the second beam is associated with another base station.

139. The non-transitory computer-readable medium pursuant to request item 135, wherein the second beam is associated with the base station and the first beam is associated with another base station.

140. The non-transitory computer-readable medium according to claim 135, wherein the first beam is a reference beam associated with a known beamform.

141. The non-transitory computer-readable medium pursuant to request item 135, wherein the transformation information includes an azimuth angle offset, an elevation angle offset, or a combination thereof.

142. The non-transitory computer-readable media pursuant to claim 135 also includes: When executed by a base station, the instruction further causes the base station to perform the following operations: receive a template of beam shape from the positioning estimation entity, wherein the transformation information is partially based on the template.

143. The non-transitory computer-readable medium pursuant to request item 135, wherein the change information is reported via location-aided data, or wherein the change information is reported on demand.

144. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a positioning estimation entity, cause the positioning estimation entity to: receive transformation information from a base station of a first beam shape of a first beam transformed therethrough into a second beam shape of a second beam; and determine the second beam shape of the second beam in part based on the transformation information.

145. The non-transitory computer-readable medium pursuant to request item 144, wherein the transformation information is received via location auxiliary data, or wherein the transformation information is received on demand.

146. The non-transitory computer-readable medium pursuant to claim 144, wherein the transformation information includes rotation information, translation information, or a combination thereof.

147. The non-transitory computer-readable medium pursuant to request item 144, wherein the first beam and the second beam are associated with the base station.

148. The non-transitory computer-readable medium pursuant to request item 144, wherein the first beam is associated with the base station and the second beam is associated with another base station.

149. The non-transitory computer-readable medium pursuant to request item 144, wherein the second beam is associated with the base station and the first beam is associated with another base station.

150. The non-transitory computer-readable medium according to request 144, wherein the first beam is a reference beam associated with a known beamform.

151. The non-transitory computer-readable medium pursuant to request item 144, wherein the transformation information includes an azimuth angle offset, an elevation angle offset, or a combination thereof.

152. The non-transitory computer-readable media pursuant to claim 144 also includes: When executed by a positioning estimation entity, the positioning estimation entity is further instructed to perform the following operations: transmit a template of beamform to the base station, wherein the transformation information is partially based on the template.

Images