Positioning reference signal configuration for measurement sharing via side link
The configuration of PRS with unique identifiers for sidelink measurement sharing addresses the 5G efficiency and latency challenges, enhancing spectral and signaling efficiency for multiple UEs.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- QUALCOMM INC
- Filing Date
- 2022-02-02
- Publication Date
- 2026-04-20
AI Technical Summary
The 5G wireless standard requires improvements in spectral efficiency, signaling efficiency, and reduced latency, particularly in supporting a large number of connections and high data transfer speeds for diverse wireless communication systems.
A method for configuring positioning reference signals (PRS) with unique identifiers to facilitate efficient measurement sharing via sidelink communication, enabling UEs to identify relevant PRS resources for positioning operations.
Enhances spectral and signaling efficiency while reducing latency by optimizing PRS resource management for multiple UEs, supporting hundreds of thousands of simultaneous connections and high data rates.
Smart Images

Figure 0007848229000007 
Figure 0007848229000008 
Figure 0007848229000009
Abstract
Description
Technical Field
[0001] Cross - reference to Related Applications
[0001] This application claims the priority of Greek Patent Application No. 20210100207, filed on March 30, 2021, entitled "POSITIONING REFERENCE SIGNAL CONFIGURATION FOR MEASUREMENT SHARING VIA SIDELINK", which was assigned to the assignee of this application and is hereby incorporated by reference in its entirety.
[0002]
[0002] Aspects of the present disclosure generally relate to wireless communication.
Background Art
[0003]
[0003] Wireless communication systems have evolved through various generations, including the first - generation analog wireless telephone service (1G), second - generation (2G) digital wireless telephone service (including intermediate 2.5G and 2.75G networks), third - generation (3G) high - speed data, Internet - enabled wireless services, and fourth - generation (4G) services (e.g., Long - Term Evolution (LTE (registered trademark)) or WiMax (registered trademark)). Currently, there are many different types of wireless communication systems in use, including cellular and personal communication service (PCS) systems. Examples of known cellular systems include the Cellular Analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), and Global System for Mobile Communications (GSM (registered trademark)).
[0004]
[0004] The fifth-generation (5G) wireless standard, also known as New Radio (NR), requires improvements such as higher data transfer speeds, a greater number of connections, and better coverage. The 5G standard by the Next Generation Mobile Network Alliance is designed to provide tens of megabits per second of data rates to each of tens of thousands of users and 1 gigabit per second of data rates to dozens of workers on an office floor. Hundreds of thousands of simultaneous connections should be supported to support large sensor deployments. Therefore, the spectral efficiency of 5G mobile communications should be significantly expanded compared to the current 4G standard. Furthermore, signaling efficiency should be expanded and latency should be significantly reduced compared to the current standard. [Overview of the project]
[0005]
[0005] The following provides a simplified overview relating to one or more embodiments disclosed herein. Therefore, the following overview should not be considered a broad overview relating to all intended embodiments, nor should it be considered to identify important or significant elements relating to all intended embodiments or to define the scope relating to a particular embodiment. Accordingly, the following overview has the sole purpose of presenting, in a simplified form, some concepts relating to one or more embodiments relating to the mechanisms disclosed herein, prior to embodiments for carrying out the invention presented below.
[0006]
[0006] In one embodiment, a method of wireless communication performed by a user device (UE) includes receiving from a network node a PRS configuration that defines or indicates a plurality of positioning reference signal (PRS) resources having unique identifiers, and the plurality of PRS resources performing positioning operations according to a PRS configuration comprising a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs serviced by a location server to identify the relevant PRS resource.
[0007]
[0007] In one embodiment, a method of wireless communication performed by a network node includes determining a plurality of PRS resources having unique identifiers, and sending to a UE at least one PRS configuration that defines or indicates the first set, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs served by the location server to identify the PRS resources in which the PRS resources are related.
[0008]
[0008] In one embodiment, the UE includes memory, a communication interface, and at least one processor communicably coupled to the memory and the communication interface, wherein the at least one processor is configured to receive from a network node via the communication interface at least one PRS configuration that defines or indicates a plurality of PRS resources having unique identifiers, and the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs serviced by the location server to identify the relevant PRS resource, and to perform positioning operations according to at least one PRS configuration.
[0009]
[0009] In one embodiment, a network node includes memory, a communication interface, and at least one processor communicably coupled to the memory and the communication interface, wherein the at least one processor is configured to determine a plurality of PRS resources having unique identifiers, and to cause the communication interface to send to the UEs at least one PRS configuration that defines or indicates the first set, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs served by the location server to identify the related PRS resources.
[0010]
[0010] In one embodiment, the UE includes means for receiving from a network node at least one PRS configuration that defines or indicates a plurality of PRS resources having unique identifiers, and means for performing positioning operations according to at least one PRS configuration, the plurality of PRS resources comprising a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs served by the location server to identify the relevant PRS resources.
[0011]
[0011] In one embodiment, a network node includes means for determining a plurality of PRS resources having unique identifiers, and means for sending to a UE at least one PRS configuration that defines or indicates the first set, comprising a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs served by the location server to identify the related PRS resources.
[0012]
[0012] In one embodiment, a non-temporary computer-readable medium for storing computer-executable instructions, the computer-executable instructions, when executed by a UE, cause the UE to: receive from a network node a PRS configuration that defines or indicates a plurality of PRS resources having unique identifiers; and perform positioning operations according to a PRS configuration comprising a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs serviced by a location server to identify the PRS resources in question.
[0013]
[0013] In one embodiment, a non-temporary computer-readable medium for storing computer executable instructions, the computer executable instructions, when executed by a network node, cause the network node to determine a plurality of PRS resources having unique identifiers, and to send to the UE at least one PRS configuration that defines or indicates the first set, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, where each of the one or more PRS resources in the first set is mapped to an associated identifier used by all UEs served by the location server to identify the associated PRS resources.
[0014]
[0014] Other objectives and advantages relating to the embodiments disclosed herein will become apparent to those skilled in the art based on the accompanying drawings and embodiments for carrying out the invention.
[0015]
[0015] The accompanying drawings are provided to aid in describing various aspects of the present disclosure and are provided merely as examples of aspects, not as an limitation of aspects. [Brief explanation of the drawing]
[0016] [Figure 1]
[0016] A diagram illustrating an exemplary wireless communication system according to an aspect of the present disclosure. [Figure 2A]
[0017] A diagram illustrating an exemplary wireless network structure according to an aspect of this disclosure. [Figure 2B] A diagram illustrating an exemplary wireless network structure according to an aspect of this disclosure. [Figure 3A]
[0018] Simplified block diagrams of several exemplary embodiments of components that may be employed in a user equipment (UE) and configured to support the communications taught herein. [Figure 3B] Simplified block diagrams of several exemplary embodiments of components that may be employed in a base station and configured to support the communications taught herein. [Figure 3C] Simplified block diagrams of several exemplary embodiments of components that may be employed in a network entity and configured to support the communications taught herein. [Figure 4A]
[0019] A diagram illustrating an exemplary frame structure and channels within the frame structure according to aspects of this disclosure. [Figure 4B] A diagram illustrating an exemplary frame structure and channels within the frame structure according to aspects of this disclosure. [Figure 4C] A diagram illustrating an exemplary frame structure and channels within the frame structure according to aspects of this disclosure. [Figure 4D] A diagram illustrating an exemplary frame structure and channels within the frame structure according to aspects of this disclosure. [Figure 5]
[0020] A diagram showing a conventional radio resource control (RRC) configuration for DL-PRS. [Figure 6]
[0021] A diagram showing a conventional telecommunications network. [Figure 7A]
[0022] A diagram illustrating a network operating according to various aspects of this disclosure. [Figure 7B] A diagram illustrating a network operating according to various aspects of this disclosure. [Figure 8]
[0023] Flowchart of an exemplary process performed by a UE related to PRS configuration for measurement sharing via sidelink according to some aspects. [Figure 9]
[0024] Flowchart of an exemplary process performed by a network node related to PRS configuration for measurement sharing via sidelink according to some aspects.
BRIEF DESCRIPTION OF THE DRAWINGS
[0017]
[0025] Aspects of the present disclosure are provided in the following description and the related drawings directed to various examples provided for illustration. Alternative aspects may be devised without departing from the scope of the present disclosure. Further, well-known elements of the present disclosure may not be described in detail or may be omitted so as not to obscure the relevant details of the present disclosure.
[0018]
[0026] The words “exemplary” and / or “example” are used herein to mean “an example, instance, or illustration”. Any aspect described herein as “exemplary” and / or “example” should not necessarily be construed as preferred or advantageous over other aspects. Similarly, the term “aspect of the present disclosure” does not require that all aspects of the present disclosure include the described features, advantages, or modes of operation.
[0019]
[0027] Those skilled in the art will appreciate that the information and signals described below may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the following description may be represented, in part, according to a particular application example, in part, according to a desired design, in part, according to the corresponding technology, etc., by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.
[0020]
[0028] Furthermore, many embodiments are described, for example, with respect to a set of actions to be performed by elements of a computing device. It will be recognized that the various actions described herein may be performed by a particular circuit (e.g., an application-specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or a combination of both. Furthermore, the set of actions described herein may be considered to be performed as a whole in any form of non-temporary computer-readable storage medium storing, at runtime, a corresponding set of computer instructions that cause or instruct the relevant processors of the device to perform the functions described herein. Thus, the various embodiments of this disclosure may be implemented in several different forms, all of which are intended to fall within the scope of the claimed subject matter. Furthermore, for each of the embodiments described herein, any corresponding form of such embodiment may be described herein, for example, as “logic configured to perform” the described actions.
[0021]
[0029] As used herein, 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), unless otherwise noted. Generally, a UE may be any wireless communication device used by a user to communicate over a wireless communication network (e.g., a mobile phone, router, tablet computer, laptop computer, consumer asset tracking device, wearable (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 may be mobile or (e.g., at some time) stationary and may communicate with a Radio Access Network (RAN). As used herein, the terms “UE” may be interchangeably referred to as “Access Terminal” or “AT,” “Client Device,” “Wireless Device,” “Subscriber Device,” “Subscriber Terminal,” “Subscriber Station,” “User Terminal” or “UT,” “Mobile Device,” “Mobile Terminal,” “Mobile Station,” or variations thereof. Generally, a UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks such as the Internet and other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as via wired access networks, wireless local area network (WLAN) networks (for example, based on the IEEE 802.11 specification, etc.).
[0022]
[0030] A base station may operate according to one of several RATs communicating with a UE, depending on the network in which it is deployed, and may alternatively be called an access point (AP), network node, node B, advanced node B (eNB), next-generation eNB (ng-eNB), or new radio (NR) node B (also called gNB or g node B). Base stations may be used primarily to support wireless access by UEs, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, a base station may provide purely edge node signaling functionality, while in others it may provide additional control and / or network management functionality. The communication link through which a UE can signal to a base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which a base station can signal to a 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) may refer to either an uplink / reverse traffic channel or a downlink / forward traffic channel.
[0023]
[0031] The term “base station” can refer to a single physical transmit / receive point (TRP), or to multiple physical TRPs, which may or may not be colocated. For example, when the term “base station” refers to a single physical TRP, the physical TRP could be the base station’s antennas corresponding to the base station’s cells (or several cell sectors). When the term “base station” refers to multiple colocated physical TRPs, the physical TRPs could be an array of antennas at the base station (for example, in a multi-input multiple-output (MIMO) system, or if the base station employs beamforming). When the term “base station” refers to multiple uncolocated physical TRPs, the physical TRPs could be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, uncolocated physical TRPs could be a serving base station receiving measurement reports from a UE and a neighbor base station where the UE is measuring its reference radio frequency (RF) signal. Since a TRP is the point from which a base station transmits and receives wireless signals, references to transmission from a base station or reception at a base station used herein should be understood to refer to a specific TRP of the base station.
[0024]
[0032] In some implementations that support UE positioning, a base station may not support wireless access by the UE (for example, it may not support data, voice, and / or signaling connections for the UE), but instead may transmit a reference signal to the UE to be measured by the UE, and / or receive and measure signals transmitted by the UE. Such a base station may be called a positioning beacon (for example, when transmitting a signal to the UE) and / or a location measurement unit (for example, when receiving and measuring a signal from the UE).
[0025]
[0033] An "RF signal" comprises electromagnetic waves of a given frequency that transport information through the space between a transmitter and a receiver. A transmitter used herein may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver is sometimes called a "multipath" RF signal.
[0026]
[0034] Figure 1 shows an exemplary wireless communication system 100 according to an aspect of the present disclosure. The wireless communication system 100 (sometimes called a wireless wide area network (WWAN)) may include various base stations 102 (marked "BS") and various UEs 104. The 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 aspect, the macrocell base station may include an eNB and / or ng-eNB that the wireless communication system 100 corresponds to an LTE network, or a gNB that the wireless communication system 100 corresponds to an NR network, or a combination of both, and the small cell base station may include femtocells, picocells, microcells, etc.
[0027]
[0035] The base stations 102 collectively form a RAN and interface with the core network 170 (e.g., an Advanced Packet Core (EPC) or a 5G core (5GC)) through a backhaul link 122, and may interface with one or more location servers 172 (e.g., a Location Management Function (LMF) or a Secure User Plane Location (SUPL) Location Platform (SLP)) through the core network 170. The (one or more) location servers 172 may be part of the core network 170 or may be outside the core network 170. In addition to other functions, base stations 102 may perform functions related to the transfer of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access layer (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracing, RAN information management (RIM), paging, positioning, and delivery of warning messages. Base stations 102 may communicate with each other directly or indirectly (e.g., through EPC / 5GC) via backhaul links 134, which may be wired or wireless.
[0028]
[0036] Base station 102 can communicate wirelessly with UE 104. Each base station 102 can provide communication coverage to its respective geographical coverage area 110. In one embodiment, one or more cells may be supported by base stations 102 in each geographical coverage area 110. A “cell” is a logical communication entity used for communication with a base station (over some frequency resource, such as carrier frequency, component carrier, carrier, or band), and may be associated with an identifier (e.g., a physical cell identifier (PCI), a virtual cell identifier (VCI), or a cell global identifier (CGI)) to distinguish cells operating over the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communications (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access to different types of UEs. Since a cell is supported by a particular base station, the term “cell” may, depending on the context, refer to either or both the logical communication entity and the base station that supports it. In some cases, the term “cell” may also refer to the geographical coverage area (e.g., sector) of a base station, insofar as the carrier frequency can be detected and used for communications within some portion of the geographical coverage area 110.
[0029]
[0037] The geographical coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (for example, in the handover area), but some of the geographical coverage areas 110 may be considerably overlapped by larger geographical coverage areas 110. For example, a small cell (SC) base station 102' may have a geographical coverage area 110' that considerably overlaps with the geographical coverage areas 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be known as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that can serve a limited group known as a limited subscriber group (CSG).
[0030]
[0038] The communication link 120 between base station 102 and UE 104 may include uplink transmissions from UE 104 to base station 102 (also called a reverse link) and / or downlink transmissions from base station 102 to UE 104 (also called a forward link). The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be traversed by one or more carrier frequencies. Carrier allocation may be asymmetric with respect to downlinks and uplinks (for example, more or fewer carriers may be allocated to the downlink than to the uplink).
[0031]
[0039] The wireless communication system 100 may further include a WLAN access point (AP) 150 communicating with a wireless local area network (WLAN) station (STA) 152 via a communication link 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in an unlicensed frequency spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform a clear channel assessment (CCA) procedure or a listen-before-talk (LBT) procedure before communication to determine whether the channel is available.
[0032]
[0040] Small cell base station 102' may operate in licensed and / or unlicensed frequency spectrums. When operating in an unlicensed frequency spectrum, small cell base station 102' may employ LTE or NR technology and use the same 5GHz unlicensed frequency spectrum used by WLAN AP150. Small cell base station 102' employing LTE / 5G in an unlicensed frequency spectrum may boost coverage to the access network and / or increase the capacity of the access network. NR in an unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, License-Assisted Access (LAA), or MulteFire.
[0033]
[0041] The wireless communication system 100 may further include a millimeter-wave (mmW) base station 180 that communicates with UE 182 and may operate in millimeter-wave (mmW) and / or near-mmW frequencies. Extremely high frequency (EHF) is a part of RF 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 are sometimes called millimeter waves. Near-mmW can extend down to frequencies of 3 GHz with wavelengths of 100 mm. The very high frequency (SHF) band, also called centimeter waves, extends between 3 GHz and 30 GHz. Communication using the mmW / near-mmW radio frequency bands has high path loss and relatively short range. The mmW base station 180 and UE 182 may utilize beamforming (transmit and / or receive) via the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, in alternative configurations, it will be understood that one or more base stations 102 may also transmit using mmW or near-mmW and beamforming. Accordingly, it will be understood that the above description is merely illustrative and should not be construed as limiting the various embodiments disclosed herein.
[0034]
[0042] Transmit beamforming is a technique for focusing 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). In transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster and stronger RF signal (in terms of data rate) to one or more receiving devices. To change the directionality of an RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters broadcasting the RF signal. For example, the network node may use an array of antennas (called a "phased array" or "antenna array") that can create beams of RF waves that can be "steered" to point in different directions without actually moving the antennas. Specifically, the RF current from the transmitter is supplied to individual antennas with the appropriate phase relationship so that the radio waves from separate antennas are added together to increase radiation in the desired direction, while canceling out and suppressing radiation in undesirable directions.
[0035]
[0043] Transmit beams can be pseudo-collocated, meaning that the transmit beam appears to the receiver (e.g., UE) to have the same parameters regardless of whether the network node's transmit antenna itself is physically collocated. In NR, there are four types of pseudo-collocation (QCL) relationships. In particular, a given type of QCL relationship means that several parameters of the target reference RF signal on the target beam can be derived from information about the source reference RF signal on the source beam. 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, mean delay, and delay spread of the target 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 target 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 mean delay of the target 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 target reference RF signal transmitted on the same channel.
[0036]
[0044] In receive beamforming, a receiver uses a received beam to amplify an RF signal detected on a given channel. For example, a receiver may increase the gain setting of an antenna array in a particular direction and / or adjust the phase setting to amplify an RF signal received from that direction (e.g., increase its gain level). Therefore, when a receiver is said to beamform in a certain direction, it means that the beam gain in that direction is higher than the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal intensity (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.
[0037]
[0045] Received beams can be spatially related. Spatial relationships mean that parameters for a transmit beam for a second reference signal can be derived from information about the received beam for a first reference signal. For example, a UE may use a specific receive beam to receive one or more reference downlink reference signals from a base station (e.g., positioning reference signal (PRS), tracking reference signal (TRS), phase tracking reference signal (PTRS), cell-specific reference signal (CRS), channel status information reference signal (CSI-RS), primary synchronization signal (PSS), secondary synchronization signal (SSS), synchronization signal block (SSB), etc.). The UE can then, based on the parameters of the received beam, form a transmit beam to send one or more uplink reference signals to its base station (e.g., uplink positioning reference signal (UL-PRS), sounding reference signal (SRS), demodulation reference signal (DMRS), PTRS, etc.).
[0038]
[0046] It should be noted that a “downlink” beam can be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station forms a downlink beam to transmit a reference signal to a UE, then the downlink beam is a transmit beam. However, if a UE forms a downlink beam, then it is a receive beam for receiving a downlink reference signal. Similarly, an “uplink” beam can be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station forms an uplink beam, then it is an uplink receive beam, and if a UE forms an uplink beam, then it is an uplink transmit beam.
[0039]
[0047] In 5G, the frequency spectrum on which wireless nodes (e.g., base stations 102 / 180, UE104 / 182) operate is divided into several frequency ranges: FR1 (450 to 6000 MHz), FR2 (24250 to 52600 MHz), FR3 (above 52600 MHz), and FR4 (between FR1 and FR2). In multi-carrier systems such as 5G, one of the carrier frequencies is called the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," while the remaining carrier frequencies are called "secondary carriers," "secondary serving cells," or "SCells." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by UE104 / 182 and the cell on which UE104 / 182 either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries the control channel common to all UEs and unique to each UE, and may be a carrier on licensed frequencies (though this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once an RRC connection is established between the UE104 and the anchor carrier and may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier on unlicensed frequencies. The secondary carrier may contain only the necessary signaling information and signals, and since both the primary uplink and primary downlink carriers are typically UE-specific, the UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UE104 / 182s in a cell may have different downlink primary carriers. The same is true for uplink primary carriers. The network can change the primary carrier of any UE104 / 182 at any time. This is done, for example, to distribute the load across different carriers.Since a "serving cell" (whether PCell or SCell) corresponds to the carrier frequency / component carrier through which some base station communicates, terms such as "cell," "serving cell," "component carrier," and "carrier frequency" can be used interchangeably.
[0040]
[0048] For example, still referring to Figure 1, one of the frequencies utilized by the macrocell base station 102 could be the anchor carrier (or "PCell"), and the other frequencies utilized by the macrocell base station 102 and / or the mmW base station 180 could be the secondary carriers ("SCell"). Simultaneous transmission and / or reception of multiple carriers allows UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20MHz aggregated carriers in a multicarrier system would theoretically lead to a doubling of the data rate (i.e., 40MHz) compared to what would be achieved with a single 20MHz carrier.
[0041]
[0049] The wireless communication system 100 may further include a UE 164 that can communicate with a macrocell base station 102 via a communication link 120 and / or with an mmW base station 180 via an mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.
[0042]
[0050] In the example in Figure 1, one or more Earth Orbiting Satellite Positioning System (SPS) space vehicles (SV) 112 (e.g., satellites) may be used as an independent source of location information for any of the illustrated UEs (shown in Figure 1 as a single UE 104 for simplicity). UE 104 may include one or more dedicated SPS receivers specifically designed to receive SPS signals 124 for deriving geolocation information from SV 112. SPS generally includes a system of transmitters arranged to enable a receiver (e.g., UE 104) to determine the receiver's location on or above the Earth based at least in part on signals (e.g., SPS signals 124) received from a transmitter (e.g., SV 112). Such transmitters generally transmit signals marked with a set number of repeating pseudo-random noise (PN) codes. While generally located within SV 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UE 104s.
[0043]
[0051] The use of SPS signal 124 can be augmented by various satellite-based augmentation systems (SBAS) that are associated with or can be enabled for use with one or more global and / or regional navigation satellite systems. For example, an SBAS may include (one or more) augmentation systems that provide integrity information, differential corrections, etc., such as a Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multi-functional Satellite Augmentation System (MSAS), or GPS-Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN). Therefore, as used herein, SPS may include one or more global and / or regional navigation satellite systems and / or any combination of augmentation systems, and SPS signals may include SPS signals, SPS-like signals, and / or other signals associated with one or more such SPS systems.
[0044]
[0052] The wireless communication system 100 may further 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 (called “sidelinks”). In the example in Figure 1, UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of base stations 102 (through which UE 190 can indirectly obtain cellular connectivity), and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (through which UE 190 can indirectly obtain WLAN-based internet connectivity). In one example, D2D P2P links 192 and 194 may be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct® (WiFi®-D), or Bluetooth®.
[0045]
[0053] Figure 2A shows an exemplary wireless network structure 200. For example, 5GC210 (also called Next Generation Core (NGC)) can be functionally considered as control plane functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.) working collaboratively to form the core network. User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect gNB222 to 5GC210, in particular to control plane functions 214 and user plane functions 212. In an additional configuration, ng-eNB224 may also be connected to 5GC210 via NG-C215 to control plane functions 214 and NG-U213 to user plane functions 212. Furthermore, ng-eNB224 may communicate directly with gNB222 via backhaul connection 223. In some configurations, the next-generation RAN (NG-RAN) 220 may have only one or more gNB222s, while other configurations may include one or more of both ng-eNB224s and gNB222s. Either a gNB222 or an ng-eNB224 may communicate with a UE204 (for example, one of the UEs shown in Figure 1). Another optional embodiment may include a location server 230, which may communicate with a 5GC210 to provide location assistance to the UE204. The location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.) or alternatively, each corresponding to a single server. The location server 230 may be configured to support one or more location services for a UE204 that can connect to the location server 230 via the core network, the 5GC210, and / or the internet (not shown).Furthermore, the location server 230 may be integrated into the core network components or, alternatively, located outside the core network (e.g., a third-party server such as an original equipment manufacturer (OEM) server or service server).
[0046]
[0054] Figure 2B shows another exemplary wireless network structure 250. 5GC260 (which may correspond to 5GC210 in Figure 2A) can functionally be considered as control plane functions provided by the Access and Mobility Management Function (AMF) 264 and user plane functions provided by the User Plane Function (UPF) 262, working collaboratively to form the core network (i.e., 5GC260). The user plane interface 263 and the control plane interface 265 connect ng-eNB224 to 5GC260, specifically to UPF262 and AMF264, respectively. In an additional configuration, gNB222 may also be connected to 5GC260 via the control plane interface 265 to AMF264 and the user plane interface 263 to UPF262. Furthermore, ng-eNB224 may communicate directly with gNB222 via the backhaul connection 223, with or without gNB direct connectivity to 5GC260. In some configurations, the new RAN220 may have only one or more gNB222s, while other configurations may include one or more of both ng-eNB224 and gNB222. Either the gNB222 or the ng-eNB224 may communicate with the UE204 (for example, any of the UEs shown in Figure 1). The base station of the NG-RAN220 communicates with the AMF264 via the N2 interface and with the UPF262 via the N3 interface.
[0047]
[0055] The functions of AMF264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between UE204 and Session Management Function (SMF)266, transparent proxy service for routing SM messages, access authentication and access permission, transport for short message service (SMS) messages between UE204 and Short Message Service Function (SMSF) (not shown), and security anchor function (SEAF). AMF264 also interacts with Authentication Server Function (AUSF) (not shown) and UE204 and receives intermediate keys established as a result of the UE204 authentication process. In the case of authentication based on UMTS (Universal Mobile Telecommunications System) Subscriber Identification Module (USIM), AMF264 retrieves security materials from AUSF. The functions of AMF264 also include security context management (SCM). SCM receives keys from SEAF that it uses to derive access network-specific keys. The AMF264's functionality also includes location service management for regulatory services, transport for location service messages between UE204 and LMF270 (acting as location server 230), transport for location service messages between NG-RAN220 and LMF270, EPS bearer identifier allocation for interaction with Advanced Packet Systems (EPS), and UE204 mobility event notification. Furthermore, the AMF264 also supports functionality for non-3GPP® (Third Generation Partnership Project) access networks.
[0048]
[0056] The functions of UPF262 include acting as an anchor point for intra-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking on the downlink), uplink traffic verification (service data flow (SDF) vs. QoS flow mapping), transport level packet marking on the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more “termination markers” to the source RAN node. UPF262 may also support the forwarding of location service messages over the user plane between UE204 and location servers such as SLP272.
[0049]
[0057] The functions of the SMF266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering in the UPF262 for routing traffic to appropriate destinations, policy enforcement and some QoS control, and downlink data notification. The interface through which the SMF266 communicates with the AMF264 is called the N11 interface.
[0050]
[0058] Another optional embodiment may include an LMF270 that may communicate with 5GC260 to provide location assistance to UE204. LMF270 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.) or alternatively, each corresponding to a single server. LMF270 may be configured to support one or more location services for UE204 that can connect to LMF270 via the core network, 5GC260, and / or via the internet (not shown). The SLP272 may support similar functionality to the LMF270, however, the LMF270 can communicate with the AMF264, NG-RAN220, and UE204 on the control plane (for example, using interfaces and protocols intended to transmit signaling messages rather than voice or data), while the SLP272 can communicate with the UE204 and external clients (not shown in Figure 2B) via the user plane (for example, using protocols intended to carry voice and / or data, such as Transmission Control Protocol (TCP) and / or IP).
[0051]
[0059] Figures 3A, 3B, and 3C show several exemplary components (represented by corresponding blocks) that may 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 perform any of the network functions described herein, including location server 230 and LMF 270, or alternatively, may be unrelated to the NG-RAN220 and / or 5GC210 / 260 infrastructure shown in Figures 2A and 2B, such as a private network) to support the file transmission operations taught herein. It will be understood that these components may be implemented in different types of devices in different implementation forms (e.g., in ASICs, in system-on-chip (SoCs), etc.). The illustrated components may also be incorporated into other devices in the communication system. For example, other devices in the system may include similar components to those described to provide similar functionality. Also, a given device may include one or more of the components. For example, the device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate using different technologies.
[0052]
[0060] UE 302 and base station 304 each include at least one wireless wide area network (WWAN) transceiver 310 and 350, respectively, and provide means (e.g., means for transmitting, means for receiving, means for measuring, means for adjusting, means for refraining from transmitting, etc.) for communicating over one or more wireless communication networks (not shown), such as an NR network, an LTE network, or a GSM network. The WWAN transceivers 310 and 350 may be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes such as other UEs, access points, base stations (e.g., eNBs, gNBs) over at least one designated RAT (e.g., NR, LTE, GSM, etc.) over the wireless communication medium (e.g., some set of time / frequency resources in a particular frequency spectrum). The WWAN transceivers 310 and 350 can be configured in various ways, respectively, to transmit and encode signals 318 and 358 (e.g., messages, instructions, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 318 and 358 (e.g., messages, instructions, information, pilots, etc.). In particular, the WWAN transceivers 310 and 350 each include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, and one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358.
[0053]
[0061] UE 302 and base station 304 also each include, in at least some cases, at least one short-range wireless transceiver 320 and 360, respectively. The short-range wireless transceivers 320 and 360 are each connected to one or more antennas 326 and 366 and may provide means for communicating with other network nodes such as other UEs, access points, and base stations via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth, Zigbee®, Z-Wave®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communications (NFC), etc.) on the wireless communication medium (e.g., means for transmitting, means for receiving, means for measuring, means for adjusting, means for refraining from transmitting, etc.). Short-range wireless transceivers 320 and 360 can be configured in various ways, respectively, to transmit and encode signals 328 and 368 (e.g., messages, instructions, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 328 and 368 (e.g., messages, instructions, information, pilots, etc.), respectively. In particular, short-range wireless transceivers 320 and 360 each include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368. As a specific example, short-range wireless transceivers 320 and 360 may be WiFi transceivers, Bluetooth transceivers, Zigbee and / or Z-Wave transceivers, NFC transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-anything (V2X) transceivers.
[0054]
[0062] A transceiver circuit comprising at least one transmitter and at least one receiver may, in some implementations, comprise an integrated device (for example, implemented as transmitter and receiver circuits of a single communication device), in some implementations comprise a separate transmitter device and a separate receiver device, or in other implementations it may be implemented in other ways. In one embodiment, the transmitter may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, enabling each device to perform transmit "beamforming". Similarly, the receiver may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, enabling each device to perform receive beamforming. In one embodiment, the transmitter and receiver may share the same plurality of antennas (e.g., antennas 316, 326, 356, 366), so that each device can perform either receive or transmit only at a given time, rather than both receiving and transmitting simultaneously. The wireless communication devices of UE302 and / or base station 304 (e.g., transceivers 310 and 320 and / or one or both of 350 and 360) may also include a network listening module (NLM) for performing various measurements.
[0055]
[0063] UE302 and base station 304 also include, in at least some cases, satellite positioning system (SPS) receivers 330 and 370. SPS receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and / or measuring SPS signals 338 and 378, respectively, such as Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, Beidou signals, India's Regional Navigation Satellite System (NAVIC), and Quasi-Zenith Satellite System (QZSS). SPS receivers 330 and 370 may each have any suitable hardware and / or software for receiving and processing SPS signals 338 and 378. SPS receivers 330 and 370 may, as appropriate, request information and operations from other systems and perform calculations necessary to determine the positions of UE302 and base station 304 using measurements obtained by any suitable SPS algorithm.
[0056]
[0064] Each base station 304 and network entity 306 includes at least one network interface 380 and 390, respectively, providing means for communicating with other network entities (e.g., means for transmitting, means for receiving, etc.). For example, network interfaces 380 and 390 (e.g., one or more network access ports) may be configured to communicate with one or more network entities via wire-based or wireless backhaul connections. In some embodiments, network interfaces 380 and 390 may be implemented as transceivers configured to support wire-based or wireless signaling communication. This communication may involve sending and receiving, for example, messages, parameters, and / or other types of information.
[0057]
[0065] In one embodiment, at least one WWAN transceiver 310 and / or at least one short-range wireless transceiver 320 may form a (wireless) communication interface of UE 302. Similarly, at least one WWAN transceiver 350, at least one short-range wireless transceiver 360, and / or at least one network interface 380 may form a (wireless) communication interface of base station 304. Similarly, at least one network interface 390 may form a (wireless) communication interface of network entity 306. Various wireless transceivers (e.g., transceivers 310, 320, 350, and 360) and wired transceivers (e.g., network interfaces 380 and 390) may generally be characterized as at least one transceiver, or alternatively, as at least one communication interface. Therefore, whether a particular transceiver or communication interface relates to a wired or wireless transceiver or communication interface can be inferred from the type of communication being performed (for example, backhaul communication between network devices or servers generally involves signaling via at least one wired transceiver).
[0058]
[0066] The UE 302, the base station 304, and the network entity 306 also include other components that may be used in conjunction with the operations disclosed herein. The UE 302, the base station 304, and the network entity 306 each include at least one processor 332, 384, and 394, for example, to provide functions related to wireless communication and to provide other processing functions. The processors 332, 384, and 394 may therefore provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, and means for indicating. In one embodiment, the processors 332, 384, and 394 may include, for example, at least one general-purpose processor, a multi-core processor, a central processing unit (CPU), an ASIC, a digital signal processor (DSP), a field-programmable gate array (FPGA), other programmable logic devices or processing circuits, or various combinations thereof.
[0059]
[0067] The UE302, base station 304, and network entity 306 include memory circuits that implement memory components 340, 386, and 396, respectively (for example, each including a memory device), to maintain information (e.g., information indicating reserved resources, thresholds, parameters, etc.). The memory components 340, 386, and 396 can therefore provide means for storing, retrieving, maintaining, etc. In some cases, the UE302, base station 304, and network entity 306 may include positioning modules 342, 388, and 398, respectively. The positioning modules 342, 388, and 398 may be hardware circuits that, when executed, cause the UE302, base station 304, and network entity 306 to perform the functions described herein, either as part of or coupled to processors 332, 384, and 394, respectively. In other embodiments, positioning modules 342, 388, and 398 may be external to processors 332, 384, and 394 (e.g., as part of a modem processing system, integrated with another processing system, etc.). Alternatively, positioning modules 342, 388, and 398 may be memory modules stored in memory components 340, 386, and 396, respectively, which, when executed by processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, base station 304, and network entity 306 to perform the functions described herein. Figure 3A shows possible locations for positioning module 342, which may be part of, for example, at least one WWAN transceiver 310, memory component 340, at least one processor 332, or any combination thereof, or may be a standalone component. Figure 3B shows possible locations for the positioning module 388, which may be part of, for example, at least one WWAN transceiver 350, a memory component 386, at least one processor 384, or any combination thereof, or it may be a standalone component.Figure 3C shows possible locations for the positioning module 398, which may be, for example, part of at least one network interface 390, a memory component 396, at least one processor 394, or any combination thereof, or may be a standalone component.
[0060]
[0068] The UE302 may include one or more sensors 344 coupled to at least one processor 332 to provide means for sensing or detecting motion and / or orientation information that is independent of motion data derived from signals received by at least one WWAN transceiver 310, at least one short-range wireless transceiver 320, and / or SPS receiver 330. For example, the (one or more) sensors 344 may include an accelerometer (e.g., a microelectromechanical system (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), and / or any other type of motion detection sensor. Furthermore, the (one or more) sensors 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, the (one or more) sensors 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate position in a 2D and / or 3D coordinate system.
[0061]
[0069] Furthermore, UE302 includes a user interface 346 that provides means for providing instructions to the user (e.g., audible and / or visual instructions) and / or means for receiving user input (e.g., when a sensing device such as a keypad, touchscreen, or microphone is activated). Although not shown, base stations 304 and network entities 306 may also include user interfaces.
[0062]
[0070] Referring more specifically to at least one processor 384, in the downlink, IP packets from network entity 306 may be served to at least one processor 384. At least one processor 384 may implement functions for the RRC layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. At least one processor 384 may provide RRC layer functions related to broadcasting system information (e.g., Master Information Block (MIB), System Information Block (SIB)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functions related to header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions related to the transfer of upper layer PDUs, error correction via automatic retransmission requests (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions related to mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.
[0063]
[0071] The transmitter 354 and receiver 352 may implement Layer 1 (L1) functions related to various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., two-phase-shift keying (BPSK), four-phase-shift keying (QPSK), M-phase-shift keying (M-PSK), multi-level quadrature amplitude modulation (M-QAM)). Coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier to generate a physical channel that carries a time-domain OFDM symbol stream, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then synthesized with each other using an inverse fast Fourier transform (IFFT). The OFDM symbol stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator can be used to determine the coding and modulation scheme, as well as for spatial processing. Channel estimates can be derived from the reference signal and / or channel state feedback transmitted by UE302. Each spatial stream can then be supplied to one or more different antennas 356. Transmitter 354 can modulate RF carriers on each spatial stream for transmission.
[0064]
[0072] In UE302, receiver 312 receives signals through its respective (one or more) antennas 316. Receiver 312 reconstructs the information modulated on the RF carrier and provides this information to at least one processor 332. Transmitter 314 and receiver 312 implement Layer 1 functions related to various signal processing functions. Receiver 312 may perform spatial processing on the information to reconstruct the spatial streams destined for UE302. If multiple spatial streams are destined for UE302, they can be combined into a single OFDM symbol stream by receiver 312. Receiver 312 then uses a Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal has a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are reconstructed and demodulated by determining the most likely signal constellation point transmitted by base station 304. These soft decisions are obtained based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals initially transmitted by base station 304 on the physical channel. The data and control signals are then provided to at least one processor 332 implementing Layer 3 (L3) and Layer 2 (L2) functions.
[0065]
[0073] In the uplink, at least one processor 332 provides demultiplexing between the transport channel and logical channel, packet reassembly, decoding, header reconstruction, and control signal processing to reconstruct IP packets from the core network. At least one processor 332 is also responsible for error detection.
[0066]
[0074] Similar to the functions described with respect to downlink transmission by base station 304, at least one processor 332 provides RRC layer functions related to system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions related to header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions related to the transfer 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 functions related to mapping between logical channels and transport channels, multiplexing MAC SDUs onto transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via hybrid automatic retransmission requests (HARQs), priority handling, and logical channel prioritization.
[0067]
[0075] The channel estimate derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 may be used by the transmitter 314 to select an appropriate coding and modulation scheme and to enable spatial processing. The spatial stream generated by the transmitter 314 may be supplied to (one or more) different antennas 316. The transmitter 314 may modulate the RF carrier in each spatial stream for transmission.
[0068]
[0076] Uplink transmission is processed at base station 304 in a manner similar to that described with respect to the receiver function in UE302. Receiver 352 receives the signal through its respective (one or more) antennas 356. Receiver 352 reconstructs the information modulated on the RF carrier and provides that information to at least one processor 384.
[0069]
[0077] In the uplink, at least one processor 384 provides demultiplexing between the transport channel and logical channel, packet reassembly, decoding, header reconstruction, and control signal processing to reconstruct IP packets from the UE302. IP packets from at least one processor 384 can be supplied to the core network. At least one processor 384 is also responsible for error detection.
[0070]
[0078] For convenience, the UE302, base station 304, and / or network entity 306 are shown in Figures 3A–3C as including various components that may be configured according to the various examples described herein. However, it should be understood that the illustrated blocks may have different functions in different designs.
[0071]
[0079] Various components of UE302, base station 304, and network entity 306 can communicate with each other via data buses 334, 382, and 392, respectively. In one embodiment, data buses 334, 382, and 392 may form or be part of the communication interfaces of UE302, base station 304, and network entity 306, respectively. For example, if different logical entities are implemented in the same device (e.g., gNB functionality and location server functionality integrated into the same base station 304), data buses 334, 382, and 392 may provide communication between them.
[0072]
[0080] The components in Figures 3A to 3C can be implemented in various ways. In some implementations, the components in Figures 3A to 3C can be implemented in one or more circuits, such as one or more processors and / or one or more ASICs (which may include one or more processors). Here, each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality. For example, some or all of the functionality represented by blocks 310 to 346 can be implemented by the processor and (one or more) memory components of UE302 (for example, by the execution of appropriate code and / or by the appropriate configuration of the processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 can be implemented by the processor and (one or more) memory components of base station 304 (for example, by the execution of appropriate code and / or by the appropriate configuration of the processor components). Furthermore, some or all of the functions represented by blocks 390-398 may be implemented by the processor and (one or more) memory components of the network entity 306 (for example, by the execution of appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed “by the UE,” “by the base station,” “by the network entity,” etc. However, as should be understood, such operations, actions, and / or functions may actually be performed by specific components or combinations of components such as the UE 302, base station 304, and network entity 306, including processors 332, 384, 394, transceivers 310, 320, 350, and 360, memory components 340, 386, and 396, positioning modules 342, 388, and 398.
[0073]
[0081] In some designs, network entity 306 may be implemented as a core network component. In other designs, network entity 306 may be separate from the network operator or operation of the cellular network infrastructure (e.g., NG RAN220 and / or 5GC 210 / 260). For example, network entity 306 may be a component of a private network that can be configured to communicate with UE 302 via base station 304 or independently of base station 304 (e.g., via a non-cellular communication link such as WiFi).
[0074]
[0082] Figures 4A to 4D show exemplary frame structures and channels within a frame structure according to embodiments of this disclosure. Various frame structures may be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). Figure 4A is Figure 400, showing an example of a downlink frame structure according to embodiments of this disclosure. Figure 4B is Figure 430, showing an example of channels within a downlink frame structure according to embodiments of this disclosure. Figure 4C is Figure 450, showing an example of an uplink frame structure according to embodiments of this disclosure. Figure 4D is Figure 480, showing an example of channels within an uplink frame structure according to embodiments of this disclosure. Other wireless communication technologies may have different frame structures and / or different channels.
[0075]
[0083] LTE, and in some cases NR, utilize OFDM on the downlink and Single Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR has the option to use OFDM on the uplink as well. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, commonly called tones or bins. Each subcarrier can be modulated with data. Generally, the modulation symbol is transmitted in the frequency domain in OFDM and in the time domain in SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kilohertz (kHz), and the minimum resource allocation (resource block) can be 12 subcarriers (or 180 kHz). Therefore, the nominal FFT sizes can be equal to 128, 256, 512, 1024, or 2048 for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth can also be divided into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there can be one, two, four, eight, or sixteen subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.
[0076]
[0084] LTE supports a single numerology (subcarrier interval (SCS), symbol length, etc.). In contrast, NR can support multiple numerologies (μ), for example, subcarrier intervals of 15kHz (μ=0), 30kHz (μ=1), 60kHz (μ=2), 120kHz (μ=3), and 240kHz (μ=4), or larger, may be available. Each subcarrier interval has 14 symbols per slot. For a 15kHz SCS (μ=0), there is one slot per subframe, 10 slots per frame, a slot duration of 1 millisecond (ms), a symbol duration of 66.7 microseconds (μs), and a maximum nominal system bandwidth (in MHz) of 50 with a 4K FFT size. For a 30kHz SCS (μ=1), there are 2 slots per subframe and 20 slots per frame, with a slot duration of 0.5ms, a symbol duration of 33.3μs, and a maximum nominal system bandwidth (in MHz) of 100 with a 4K FFT size. For a 60kHz SCS (μ=2), there are 4 slots per subframe and 40 slots per frame, with a slot duration of 0.25ms, a symbol duration of 16.7μs, and a maximum nominal system bandwidth (in MHz) of 200 with a 4K FFT size. For a 120kHz SCS (μ=3), there are 8 slots per subframe and 80 slots per frame, with a slot duration of 0.125ms, a symbol duration of 8.33μs, and a maximum nominal system bandwidth (in MHz) of 400 with a 4K FFT size. For a 240kHz SCS (μ=4), there are 16 slots per subframe and 160 slots per frame, with a slot duration of 0.0625ms, a symbol duration of 4.17μs, and a maximum nominal system bandwidth (in MHz) of 800 with a 4K FFT size.
[0077]
[0085] In the examples in Figures 4A to 4D, a 15kHz numerology is used. Thus, in the time domain, a 10ms frame is divided into 10 equally sized subframes, each 1ms long, with each subframe containing one time slot. In Figures 4A to 4D, time is represented horizontally (on the X-axis), increasing from left to right, while frequency is represented vertically (on the Y-axis), increasing (or decreasing) from bottom to top.
[0078]
[0086] A resource grid may be used to represent a time slot, and each time slot contains one or more time-parallel resource blocks (RBs) (also called physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the numerology of Figures 4A to 4D, for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and 7 consecutive symbols in the time domain for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and 6 consecutive symbols in the time domain for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.
[0079]
[0087] Some of the REs carry downlink reference (pilot) signals (DL-RS). DL-RS may include PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, etc. Figure 4A shows an exemplary location of an RE carrying a PRS (marked "R").
[0080]
[0088] The set of resource elements (REs) used for PRS transmission is called a "PRS resource." This set of resource elements can span multiple PRBs in the frequency domain and "N" consecutive symbols (such as one or more) within a slot in the time domain. For a given OFDM symbol in the time domain, the PRS resource occupies consecutive PRBs in the frequency domain.
[0081]
[0089] The transmission of a PRS resource within a given PRB has a specific comb size (also called "comb density"). The comb size "N" represents the subcarrier interval (or frequency / tone interval) within each symbol of the PRS resource configuration. Specifically, for a comb size "N", the PRS is transmitted in every N subcarrier of the symbols in the PRB. For example, for comb 4, for each symbol of the PRS resource configuration, the RE corresponding to every 4th subcarrier (such as subcarriers 0, 4, 8) is used to transmit the PRS of the PRS resource. Currently, comb sizes 2, 4, 6, and 12 are supported for DL-PRS. Figure 4A shows an exemplary PRS resource configuration for comb 6 (spanning six symbols). That is, the locations of the shaded REs (marked "R") indicate the comb 6 PRS resource configuration.
[0082]
[0090] Currently, DL-PRS resources can extend to 2, 4, 6, or 12 consecutive symbols within a slot having a fully frequency-domain staggered pattern. DL-PRS resources can be configured in any upper-layer configured downlink or flexible (FL) symbols within a slot. There can be a constant resource element unit energy (EPRE) for all REs of a given DL-PRS resource. The following are the inter-symbol frequency offsets for comb sizes 2, 4, 6, and 12 across 2, 4, 6, and 12 symbols. Comb 2 with 2 symbols: {0,1}, Comb 2 with 4 symbols: {0,1,0,1}, Comb 2 with 6 symbols: {0,1,0,1,0,1}, Comb 2 with 12 symbols: {0,1,0,1,0,1,0,1,0,1}, Comb 4 with 4 symbols: {0,2,1,3}, Comb 4 with 12 symbols: {0,2,1,3,0,2,1,3,0,2,1,3}, Comb 6 with 6 symbols: {0,3,1,4,2,5}, Comb 6 with 12 symbols: {0,3,1,4,2,5,0,3,1,4,2,5}, and Comb 12 with 12 symbols: {0,6,3,9,1,7,4,10,2,8,5,11}.
[0083]
[0091] A "PRS resource set" is a set of PRS resources used for transmitting PRS signals, where each PRS resource has a PRS resource ID. Furthermore, PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by its PRS resource set ID and associated with a specific TRP (identified by its TRP ID). Furthermore, PRS resources in a PRS resource set have the same periodicity, a common muting pattern configuration, and the same repetition factor (such as "PRS-ResourceRepetitionFactor") across slots. Periodicity is the time from the first repetition of the first PRS resource in the first PRS instance to the same first repetition of the same first PRS resource in the next PRS instance. The periodicity can have lengths selected from 2^μ*{4,5,8,10,16,20,32,40,64,80,160,320,640,1280,2560,5120,10240} slots, where μ=0,1,2,3. The iteration coefficient can have lengths selected from {1,2,4,6,8,16,32} slots.
[0084]
[0092] A PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP may transmit one or more beams). That is, each PRS resource in a PRS resource set may be transmitted on a different beam, and therefore, "PRS resource" or simply "resource" may also be referred to as "beam." Note that this does not imply in any way whether the TRP and the beam on which the PRS is transmitted are known to the UE.
[0085]
[0093] A "PRS instance" or "PRS occasion" is one instance of a periodically repeating time window (such as a group of one or more consecutive slots) in which PRS is expected to be sent. A PRS occasion may also be called a "PRS positioning occasion," "PRS positioning instance," "positioning occasion," "positioning instance," "positioning iteration," or simply "occasion," "instance," or "iteration."
[0086]
[0094] A "positioning frequency layer" (also simply called a "frequency layer") is a collection of one or more PRS resource sets across one or more TRPs having the same values for several parameters. More specifically, a collection of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning all numerologies supported for PDSCH are also supported for PRS), the same point A, the same value for downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The point A parameter takes the value of the parameter "ARFCN-ValueNR" ("ARFCN" stands for "Absolute Radio Frequency Channel Number") and is an identifier / code that specifies a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth can have a granularity of four PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs. Currently, up to four frequency layers are defined, and up to two PRS resource sets may be configured per TRP per frequency layer.
[0087]
[0095] The concept of frequency layers is somewhat similar to the concepts of component carriers and bandwidth portions (BWPs), but differs in that component carriers and BWPs are used by a single base station (or macrocell and smallcell base stations) to transmit data channels, while frequency layers are used by several (usually three or more) base stations to transmit PRSs. When a UE sends its positioning capability to the network, such as during an LTE positioning protocol (LPP) session, it may indicate the number of frequency layers it can support. For example, a UE may indicate whether it can support one or four positioning frequency layers.
[0088]
[0096] Figure 4B shows an example of various channels within a downlink slot of a radio frame. In NR, the channel bandwidth or system bandwidth is divided into multiple BWPs. A BWP is a contiguous set of PRBs selected from a contiguous subset of common RBs for a given numerology on a given carrier. Generally, up to four BWPs can be specified on the downlink and uplink. That is, a UE can consist of up to four BWPs on the downlink and up to four BWPs on the uplink. At a given time, only one BWP (uplink or downlink) can be active, meaning that the UE can receive or transmit on only one BWP at a time. On 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.
[0089]
[0097] Referring to Figure 4B, the primary synchronization signal (PSS) is used by the UE to determine the subframe / symbol timing and physical layer identification information. The secondary synchronization signal (SSS) is used by the UE to determine the physical layer cell identification information group number and radio frame timing. Based on the physical layer identification information and physical layer cell identification information group number, the UE can determine the PCI. Based on the PCI, the UE can determine the location of the DL-RS described above. Physical broadcast channels (PBCHs) carrying MIBs can be logically grouped using PSS and SSS to form an SSB (also called SS / PBCH). The MIB provides the number of RBs in the downlink system bandwidth and the system frame number (SFN). Physical downlink shared channels (PDSCHs) carry user data, broadcast system information not transmitted through PBCHs such as system information blocks (SIBs), and paging messages.
[0090]
[0098] A physical downlink control channel (PDCCH) carries downlink control information (DCI) within one or more control channel elements (CCEs), each CCE containing one or more RE group (REG) bundles (which may span multiple symbols in the time domain), each REG bundle containing one or more REGs, each REG corresponding to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The set of physical resources used to carry the PDCCH / DCI is called the control resource set (CORESET) in NR. In NR, the PDCCH is limited to a single CORESET and transmitted with its own DMRS. This enables UE-specific beamforming for the PDCCH.
[0091]
[0099] In the example in Figure 4B, there is one CORESET for each BWP, and the CORESET spans three symbols in the time domain (although it could be only one or two symbols). Unlike the LTE control channel, which occupies the entire system bandwidth, in NR, the PDCCH channel is localized into its own region in the frequency domain (i.e., a CORESET). Therefore, the frequency components of the PDCCH shown in Figure 4B are shown as smaller than a single BWP in the frequency domain. Note that the illustrated CORESET is contiguous in the frequency domain, but it does not need to be. Furthermore, a CORESET can span fewer than three symbols in the time domain.
[0092]
[0100] Within a PDCCH, DCIs carry information about uplink resource allocation (persistent and non-persistent), referred to as uplink authorization and downlink authorization, and a description of the downlink data to be sent to the UE. More specifically, DCIs indicate the resources scheduled for downlink data channels (e.g., PDSCH) and uplink data channels (e.g., PUSCH). Multiple (e.g., up to eight) DCIs may be configured in a PDCCH, and these DCIs may have one of several formats. For example, there are different DCI formats for uplink scheduling, downlink scheduling, uplink transmit power control (TPC), etc. A PDCCH may be transported by one, two, four, eight, or sixteen CCEs to accommodate different DCI payload sizes or coding rates.
[0093]
[0101] As shown in Figure 4C, some of the REs (labeled "R") carry DMRS for channel estimation at the receiver (e.g., base station, another UE). The UE may further transmit SRS, for example, in the last symbol of a slot. The SRS may have a comb structure, and the UE may transmit SRS on one of the combs. In the example in Figure 4C, the illustrated SRS is comb 2 across one symbol. The SRS may be used by the base station to obtain channel state information (CSI) for each UE. The CSI describes how the RF signal propagates from the UE to the base station and represents the combined effects of scattering, fading, and power attenuation with distance. Systems use the SRS for resource scheduling, link adaptation, large-scale MIMO, beam management, etc.
[0094]
[0102] Currently, SRS resources can consist of one, two, four, eight, or twelve consecutive symbols within a slot with a comb size of Com 2, Com 4, or Com 8. The following are the frequency offsets between symbols for currently supported SRS comb patterns. Comb 2 with 1 symbol: {0}, Comb 2 with 2 symbols: {0,1}, Comb 2 with 4 symbols: {0,1,0,1}, Comb 4 with 4 symbols: {0,2,1,3}, Comb 4 with 8 symbols: {0,2,1,3,0,2,1,3}, Comb 4 with 12 symbols: {0,2,1,3,0,2,1,3,0,2,1,3}, Comb 8 with 4 symbols: {0,4,2,6}, Comb 8 with 8 symbols: {0,4,2,6,1,5,3,7}, and Comb 8 with 12 symbols: {0,4,2,6,1,5,3,7,0,4,2,6}.
[0095]
[0103] A set of resource elements used for SRS transmission is called an "SRS resource" and can be identified by the parameter "SRS-ResourceId". A set of resource elements can span multiple PRBs in the frequency domain and N (e.g., one or more) consecutive symbols within a slot in the time domain. In a given OFDM symbol, the SRS resource occupies consecutive PRBs. An "SRS resource set" is a set of SRS resources used for transmitting an SRS signal and is identified by the SRS resource set ID ("SRS-ResourceSetId").
[0096]
[0104] Generally, a UE transmits SRS to enable a receiving base station (either a serving base station or a neighboring base station) to measure channel quality between the UE and the base station. However, SRS can also be specifically configured as uplink positioning reference signals for uplink-based positioning procedures, such as uplink time difference-to-arrival (UL-TDOA), round-trip time (RTT), and uplink angle of arrival (UL-AoA). As used herein, the term “SRS” may refer to an SRS configured for channel quality measurement or an SRS configured for positioning purposes. When it is necessary to distinguish between the two types of SRS, the former may be referred herein as “SRS-for-communication” and / or the latter as “SRS-for-positioning.”
[0097]
[0105] Several extensions to the previous definition of SRS have been proposed for SRS for positioning (also called "UL-PRS"), including new staggered patterns within SRS resources (except single symbol / comb 2), new comb types for SRS, new sequences for SRS, a higher number of SRS resource sets per component carrier, and a higher number of SRS resources per component carrier. Furthermore, the parameters "SpatialRelationInfo" and "PathLossReference" should be configured based on a downlink reference signal or SSB from a neighboring TRP. Also, one SRS resource may be transmitted outside of an active BWP, and one SRS resource may extend across multiple component carriers. Additionally, SRS may be configured in an RRC connected state and transmitted only within an active BWP. Furthermore, there may be frequency hopping, no repetition factor, a single antenna port, and new lengths for SRS (e.g., 8 and 12 symbols). Also, there may be open-loop power control and no closed-loop power control, and comb 8 (i.e., SRS transmitted in every 8th subcarrier in the same symbol) may be used. Finally, a UE can transmit from multiple SRS resources for UL-AoA through the same transmit beam. All of these are features added to the current SRS framework, and they are configured through RRC upper-layer signaling (and potentially triggered or activated through MAC control elements (CE) or DCI).
[0098]
[0106] Figure 4D shows an example of various channels within an uplink slot of a frame according to an aspect of this disclosure. A random access channel (RACH), also called a physical random access channel (PRACH), may be in one or more slots within a frame based on a PRACH configuration. A PRACH may contain six consecutive RB pairs within a slot. The PRACH allows the UE to perform initial system access and achieve uplink synchronization. A physical uplink control channel (PUCCH) may be located on the edge of the uplink system bandwidth. The PUCCH carries uplink control information (UCI), such as scheduling requests, CSI reports, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. A physical uplink shared channel (PUSCH) may carry data and may be further used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.
[0099]
[0107] It should be noted that the terms “positioning reference signal” and “PRS” generally refer to the specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms “positioning reference signal” and “PRS” may also refer to any type of reference signal that can be used for positioning, including but not limited to PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, and UL-PRS as defined in LTE and NR. Furthermore, the terms “positioning reference signal” and “PRS” may refer to downlink or uplink positioning reference signals unless otherwise indicated by the context. Where further distinction between types of PRS is necessary, downlink positioning reference signals may be called “DL-PRS,” and uplink positioning reference signals (e.g., SRS, PTRS for positioning) may be called “UL-PRS.” Furthermore, for signals that can be transmitted on both uplink and downlink (e.g., DMRS, PTRS), those signals may be prefixed with “UL” or “DL” to distinguish direction. For example, "UL-DMRS" can be distinguished from "DL-DMRS".
[0100]
[0108] Figure 5 shows a conventional radio resource control (RRC) configuration for DL-PRS. Frequency layer 500 is defined with respect to subcarrier spacing (SCS), "pointA" (a common reference point for all resource grids in the frequency domain, the center of subcarrier 0 of the common resource block 0 of the lowest resource grid, and which can be outside the carrier BW), cyclic prefix (CP), and initial physical resource block (PRB).
[0101]
[0109] An example information element (IE) that defines support data (AD) for each transmit / receive point (TRP) is shown below. This IE specifies the support data and DL-PRS positioning frequency layer for each frequency.
[0102]
number
[0103]
[0110] An example IE defining DL-PRS frequency layer 500 is shown below.
[0104]
number
[0105]
[0111] An example IE (Internet Explorer) that defines DL-PRS support data is shown below. This IE specifies the DL-PRS configuration.
[0106]
number
[0107]
[0112] An example IE defining a DL-PRS configuration is shown below. This IE specifies a list of one or more DL-PRS resource sets.
[0108]
number
[0109]
[0113] The PRS resource set 502 roughly allocates the time and frequency of the PRS block and includes duration, iteration coefficient, resource gap, muting, offset, and other parameters, defined in terms of slots rather than symbols. An exemplary IE defining the PRS resource set 502 is shown below.
[0110]
number
[0111]
[0114] Each PRS resource set 502 may contain up to 64 PRS resources 504. PRS resources 504 are defined with respect to slots and symbols using parameters such as symbol offsets, resource element offsets, and pseudo-collocations (QCL). An exemplary IE defining a PRS resource 504 is shown below.
[0112]
number
[0113]
[0115] When a pair of UEs establish a sidelink (SL) communication channel, the UEs are relatively close to each other and may therefore have similar channel conditions and locations. Thus, positioning measurements performed by one UE may be the same as, or similar to, those performed by the other UE. In these situations, PRS measurements performed by one UE of the SL pair will likely yield the same results as PRS measurements performed by the other UE of that SL pair, making it unnecessary for both UEs to perform PRS measurements. Having one UE perform the PRS measurements and share the results with the other UE offers clear benefits, including reduced PRS processing overhead and power consumption for the UE receiving the PRS results from the other UE and therefore not having to perform the PRS measurements themselves. Another potential benefit is that sharing PRS measurements between UEs involved in SL communication with each other can improve positioning accuracy and reduce PRS beam management overhead from both the UE and network sides. However, this is difficult to implement in conventional networks.
[0114]
[0116] Figure 6 shows a conventional telecommunications network 600, including a base TRP 602 serving a first UE 604 and a second UE 606. Each UE is provided with a PRS configuration that defines one or more TRPs for each frequency layer (FL), and for each TRP, at least one PRS resource set, each PRS resource set having at least one PRS resource. Each PRS resource has a PRS-ID, which is a combination of a TRP ID, a PRS resource set ID, and a PRS resource ID. In this example, the PRS ID is a tuple {TRP ID, PRS resource set ID, PRS resource ID}.
[0115]
[0117] One technical issue with the current network specification is that it does not require a unique mapping between PRS IDs and specific reference signals across all UEs. In the example shown in Figure 6, UE604 has two PRS resources, identified by the tuples "{1,1,1}" and "{1,1,2}", respectively. PRS resource "{1,1,1}" corresponds to beam 608 transmitted by base station 602, and PRS resource "{1,1,2}" corresponds to beam 610 transmitted by base station 602. UE606 also has two PRS resources, similarly identified by the tuples "{1,1,1}" and "{1,1,2}", respectively, but these tuples point to beams 612 and 614, rather than beams 608 and 610. The problem is that if UE604 shares its PRS measurement for beam B with UE606, the PRS measurement will be associated with PRS ID "{1,1,2}", i.e., beam 610. However, since UE606 uses the same PRS ID, i.e., "{1,1,2}", to identify beam 614, UE606 will incorrectly assume that the PRS measurement is associated with beam 614. In other words, while a TRP ID can uniquely identify a TRP, PRS resource set IDs and PRS resource IDs are assigned arbitrarily. This means that PRS ID "{1,1,2}" for UE604 does not necessarily mean the same beam as PRS ID "{1,1,2}" for UE606.
[0116]
[0118] Due to this mapping ambiguity, when one UE receives a measurement of a PRS resource from another UE, for example, there is no way to guarantee that the two UEs are pointing to the same beam. Even worse, a UE receiving a measurement associated with a particular PRS ID may mistakenly assume that the same PRS ID used by another UE is pointing to the same beam. This ambiguity makes the sharing of positioning measurements between UEs hazardous. Thus, current communication networks experience a technical drawback in that the sharing of positioning measurements between UEs is either unacceptably dangerous or impossible.
[0117]
[0119] To address these technical challenges, techniques for designing PRS configurations that enable measurement sharing via sidelink communication are presented. In some embodiments, the PRS configuration is conceptually divided into two subsets: a set of PRS resources with global identifiers and a set of PRS resources with dedicated identifiers.
[0118]
[0120] When a PRS resource has a global identifier, this means that multiple UEs will use the same identifier to refer to that PRS resource. A PRS resource with a global identifier is sometimes called a global PRS resource, and it is sometimes said that its identifier is consistent across multiple UEs. A set of PRS resources with global identifiers is sometimes called a set of global PRS resources, or for brevity, a "global set." In a set of PRS resources with global identifiers, it is sometimes said that each PRS resource is uniquely identified across multiple UEs. The part of the PRS configuration that defines a global PRS resource is sometimes called the global part of the PRS configuration.
[0119]
[0121] When a PRS resource has a unique identifier, this means that one UE may use a certain identifier to refer to that PRS resource, while another UE may use a different identifier to refer to the same resource; in other words, different UEs may use different identifiers to refer to the same PRS resource. The reverse is also true: in one UE, a particular unique identifier may refer to a PRS resource, while in another UE, the same unique identifier may refer to a completely different PRS resource. A PRS resource with a unique identifier is sometimes called a unique PRS resource, and it is sometimes said that its identifier is specific to a particular UE. A set of PRS resources with unique identifiers is sometimes called a set of unique PRS resources, or for brevity, a "unique set." In a set of PRS resources with unique identifiers, each PRS resource is sometimes said to be uniquely identified for a single UE, but not uniquely identified across multiple UEs. The part of the PRS configuration that defines a unique PRS resource is sometimes called the unique part of the PRS configuration.
[0120]
[0122] From a network perspective, in some embodiments, the LMF may provide each UE with a global PRS configuration and a dedicated PRS configuration. In some embodiments, the dedicated PRS configuration may add resources to the global PRS configuration, modify resources in the global PRS configuration, or remove resources from the global PRS configuration. From a UE perspective, in some embodiments, when a UE shares PRS measurements with a neighboring UE, the UE shares only the measurements that are in the global PRS configuration and not modified by the dedicated PRS configuration.
[0121]
[0123] Figures 7A and 7B show a network 700 operating according to various aspects of the present disclosure. In the examples shown in Figures 7A and 7B, the network 700 includes a base station 702 that serves a first UE 704 and a second UE 706 and communicates with an LMF 708. The LMF 708 provided each UE with a PRS configuration including a global portion and a dedicated portion. For both UE 704 and UE 706, the global portion of the PRS configuration identifies two PRS resources, namely beam 710 and beam 7122. For UE 704, the dedicated portion of the PRS configuration identifies beam 714 and beam 716, and for UE 706, the dedicated portion of the PRS configuration identifies beam 718 and beam 720. In the examples shown in Figures 7A and 7B, beams 710 and 712 are broader, general-purpose PRS beams, while beams 714-720 are narrower beams, which may provide better angle-based location accuracy for each UE; however, this embodiment is illustrative and not limiting.
[0122]
[0124] In the examples shown in Figures 7A and 7B, the PRS configuration follows a hierarchy: TRP => PRS resource set => PRS resource. In the example shown in Figure 7A, the distinction between global and dedicated occurs above the TRP level in the hierarchy, while in the example shown in Figure 7B, the distinction between global and dedicated occurs below the TRP level in the hierarchy. In other embodiments, the global / dedicated distinction may occur at other levels within the hierarchy.
[0123]
[0125] In some embodiments, the LMF may provide each UE with two PRS configurations, namely a global PRS configuration and a dedicated PRS configuration. In some embodiments, the LMF may provide each UE with a single PRS configuration that includes a global portion and a dedicated portion. In some embodiments, the LMF may provide each UE with multiple PRS configurations, each PRS configuration including a portion of the global PRS configuration or a portion of the dedicated PRS configuration.
[0124]
[0126] The relationship between global PRS resources and dedicated PRS resources may be implementation-specific, but not limited to, being configured statically or dynamically. In some embodiments, PRS resources identified in the dedicated portion may supplement PRS resources identified in the global portion; for example, a UE may use all PRS resources from both portions. In some embodiments, resources identified in the dedicated portion may override or replace PRS resources identified in the global portion, for example, according to a mapping between dedicated PRS configurations and global PRS configurations. This mapping may be explicit, for example, a UE may be instructed to replace a particular global PRS resource with a particular dedicated PRS resource (for example, as part of a dedicated PRS resource definition), or this mapping may be implicit, for example, a UE may be instructed or configured to replace or substitute a global PRS resource with any dedicated PRS resource that is quasi-collocated (QCL) with a particular global PRS resource or has a specified spatial relationship with a particular global PRS resource. In some aspects, the LMF may later modify, update, or change which global PRS resources are replaced by dedicated PRS resources, which dedicated PRS resources replace global PRS resources, or any combination thereof.
[0125]
[0127] For example, in Figures 7A and 7B, UE704 may be configured to use beams 714 and 716 instead of beams 710 and 712, and UE706 may be configured to use beam 710 but replace beam 712 with beams 718 and 720, where beams 718 and 720 point in the same approximate direction as beam 712 but are narrower, which makes beams 718 and 720 better for angle-based positioning. In another example, UE704 may be configured to use both global and dedicated PRS configurations to use, for example, beams 710, 712, 714, and 716. In some embodiments, the UE may adjust its own configuration. For example, in some embodiments, the UE may be provided with more PRS configurations that its hardware or processing power can support, in which case the UE may have the option to select a subset of global and dedicated parts according to some metric or requirement. In some aspects, the LMF may later modify, update, or change its global portion, dedicated portion, or both.
[0126]
[0128] In Figures 7A and 7B, the first UE704 and the second UE706 can swap or use PRS measurements from the global portion of the PRS configuration, since the PRS identified as "{1,1,1}" in the global portion of the PRS configuration will always point to beam 710, for example, and the PRS identified as "{1,1,2}" in the global portion of the PRS configuration will always point to beam 712. In contrast, the PRS identified as "{1,2,1}" in the dedicated configuration of UE704 and the PRS identified as "{1,2,1}" in the dedicated configuration of UE706 may point to different beams (and in this example, different beams, namely beam 714 and beam 718, respectively). Thus, in some embodiments, UEs involved in SL communication may be constrained to share only PRS measurements from the global portion of the PRS configuration. In another embodiment, the UE may compare measurements taken using a dedicated PRS configuration with measurements taken using a global PRS configuration in order to determine whether there is a correlation between dedicated PRS resources and global PRS resources. If there is a correlation, the UE may share the PRS measurements taken using the dedicated PRS resources, but may label, identify, or map those measurements to a global PRS resource. For example, the UE may share and label a measurement taken using a dedicated PRS resource as if it were a measurement taken using a global PRS resource. In Figures 7A and 7B, for example, UE1 may report a measurement taken using a dedicated PRS resource 714 or dedicated PRS resource 716 as a measurement taken using a global PRS resource 710.
[0127]
[0129] The techniques described herein avoid ambiguity regarding the beams involved in the measurements and enable a variety of advantageous use cases. For low positioning accuracy requirements, e.g., positioning accuracy of about 1 meter (m), in some embodiments, the UE offloads part of its PRS receiving / transmitting tasks to a neighboring UE and directly incorporates the neighbor's measurements to determine its location. For high positioning accuracy requirements, e.g., positioning accuracy of about 1 centimeter (cm), in some embodiments, the UE must perform the measurements itself to minimize measurement errors, but the neighboring UE's measurements are shared as supporting data.
[0128]
[0130] Figure 8 is a flowchart of an exemplary process 800 related to a PRS configuration for measurement sharing via a side link, in several embodiments. In some implementations, one or more process blocks in Figure 8 may be implemented by a UE (e.g., UE 104). In some implementations, one or more process blocks in Figure 8 may be implemented by another device, or a group of devices separate from or including the User Equipment (UE). Additionally or alternatively, one or more process blocks in Figure 8 may be implemented by one or more components of UE 302, such as at least one processor 332, memory 340, at least one WWAN transceiver 310, at least one short-range wireless transceiver 320, SPS receiver 330, (one or more) positioning modules 342, and / or user interface 346, any or all of which may be considered means for implementing this operation.
[0129]
[0131] As shown in Figure 8, process 800 may include receiving from a network node at least one PRS configuration that defines or indicates a plurality of PRS resources having unique identifiers, the plurality of PRS resources comprising a first set of one or more PRS resources, where each PRS resource in the first set is mapped to an identifier that is consistent across two or more UEs, and a second set of one or more PRS resources, where each PRS resource in the second set is mapped to an identifier that is specific to the UE and is not consistent across two or more UEs (block 810). Means for carrying out the operation in block 810 may include at least one WWAN transceiver 350 and at least one processor 384 of UE 304. For example, UE 304 may receive at least one PRS configuration via (one or more) receivers 352.
[0130]
[0132] As further shown in Figure 8, process 800 may include performing positioning operations according to the PRS configuration (block 820). Means for performing the operations in block 820 may include at least one WWAN transceiver 350 and at least one processor 384 of UE304. For example, at least one processor 384 of UE304 may instruct (one or more) receivers 352 to perform measurements of PRS resources identified by the PRS configuration. In some embodiments, at least one processor 384 of UE304 may instruct (one or more) transmitters 354 to transmit measurement results to another entity, calculate an estimated location based on the measurement results, instruct (one or more) transmitters 354 to transmit the estimated location to another entity, or a combination thereof.
[0131]
[0133] In some embodiments, each of a plurality of PRS resources is associated with a frequency layer (FL), a transmit / receive point (TRP), a set of PRS resources, or a combination thereof. In some embodiments, receiving at least one PRS configuration comprises receiving a first set of one or more PRS resources in a first PRS configuration and receiving a second set of one or more PRS resources in a second PRS configuration. In some embodiments, receiving a first PRS configuration comprises receiving a first PRS configuration via broadcast, multicast, or unicast transmission. In some embodiments, receiving a second PRS configuration comprises receiving a second PRS configuration via unicast or multicast transmission. In some embodiments, receiving at least one PRS configuration comprises receiving at least a first portion of a first set of one or more PRS resources and at least a first portion of a second set of one or more PRS resources in a first PRS configuration and receiving a second portion of a first set of one or more PRS resources, a second portion of a second set of one or more PRS resources, or a combination thereof in a second PRS configuration.
[0132]
[0134] In some embodiments, process 800 includes replacing at least one PRS resource in a first set with at least one PRS resource in a second set. In some embodiments, process 800 includes receiving an explicit mapping from a network node, wherein the replacement of at least one PRS resource in a first set with at least one PRS resource in a second set is carried out in accordance with the explicit mapping; receiving a set of mapping rules from a network node, wherein the replacement of at least one PRS resource in a first set with at least one PRS resource in a second set is carried out in accordance with a mapping derived from the set of mapping rules; or a combination thereof.
[0133]
[0135] As further shown in Figure 8, process 800 includes receiving a request from a second UE to share positioning information (block 830), sharing positioning information with the second UE relating to at least one PRS resource in a first set of one or more PRS resources, and not sharing positioning information relating to PRS resources in the second set, except that positioning information relating to PRS resources in the second set that replace PRS resources in the first set may be shared (block 840). Means for carrying out operations in blocks 830 and 840 may include at least one WWAN transceiver 350 and at least one processor 384 of UE 304. For example, one or more receivers 312 of UE 304 may receive a request to share positioning information, and at least one processor 332 may cause one or more transmitters 314 to transmit to the requesting UE positioning information relating to one or more PRS resources in the first set. In some embodiments, receiving a request to share positioning information comprises receiving the request via sidelink (SL) communication, and sharing positioning information with a second UE related to at least one PRS resource in a first set of one or more PRS resources comprises sharing positioning information via SL communication, or a combination thereof. In some embodiments, sharing positioning information with a second UE related to at least one PRS resource in a first set of one or more PRS resources comprises sending positioning information to the second UE related to at least one of the one or more PRS resources in the second set, receiving positioning information from the second UE related to at least one of the one or more PRS resources in the first set, or a combination thereof.
[0134]
[0136] Process 800 may include additional embodiments, such as any single embodiment or any combination of embodiments relating to one or more other processes described below and / or elsewhere in this specification. Figure 8 shows an exemplary block of Process 800, but in some embodiments, Process 800 may include additional blocks, fewer blocks, different blocks, or blocks configured differently, in addition to those shown in Figure 8. As an addition or alternative, two or more blocks of Process 800 may be carried out in parallel.
[0135]
[0137] Figure 9 is a flowchart of an exemplary process 900 relating to a PRS configuration for measurement sharing via sidelinks in several embodiments. In some embodiments, one or more process blocks in Figure 9 may be implemented by a network node (e.g., base station 102, location server 172, etc.). In some embodiments, one or more process blocks in Figure 9 may be implemented by a separate device or group of devices, either separate from or including the network node. Additionally or alternatively, one or more process blocks in Figure 9 may be implemented by one or more components of base station 304, such as at least one processor 384, memory 386, at least one WWAN transceiver 350, at least one short-range wireless transceiver 360, SPS receiver 370, at least one network interface 380, and / or (one or more) positioning modules 388, any or all of which may be considered means for implementing this operation. Alternatively, one or more process blocks in Figure 9 may be implemented by one or more components of the network node 306, such as at least one processor 394, memory 396, at least one network interface 390, and / or (one or more) positioning modules 398, any or all of which may be considered means for implementing this operation.
[0136]
[0138] As shown in Figure 9, process 900 may include determining a plurality of PRS resources having unique identifiers, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, each PRS resource in the first set is mapped to an identifier consistent across two or more UEs, and a second set of one or more PRS resources, each PRS resource in the second set is mapped to an identifier specific to a UE and not consistent across two or more UEs (block 910). Means for performing operations in block 910 may include at least one processor 394 of network node 306. For example, at least one processor 394 of network node 306 may determine the first set and the second set of PRS resources. In some embodiments, each of the plurality of PRS resources is associated with a frequency layer (FL), a transmit / receive point (TRP), a set of PRS resources, or a combination thereof.
[0137]
[0139] As further shown in Figure 9, process 900 may include sending the UE at least one PRS configuration that identifies or defines a first set and a second set (block 920). Means for carrying out the operation in block 920 may include at least one processor 394 and at least one network interface 390 of the network node 306. For example, at least one processor 394 of the network node 306 may instruct at least one network interface 390 to send the UE at least one PRS configuration that identifies or defines a first set and a second set, as described above. In some embodiments, sending at least one PRS configuration comprises sending a first set of one or more PRS resources in a first PRS configuration and sending a second set of one or more PRS resources in a second PRS configuration. In some embodiments, sending the first PRS configuration comprises sending the first PRS configuration via broadcast, multicast, or unicast transmission. In some embodiments, sending a second PRS configuration comprises sending the second PRS configuration via unicast or multicast transmission. In some embodiments, sending at least one PRS configuration comprises sending at least a first portion of a first set of one or more PRS resources and at least a first portion of a second set of one or more PRS resources in a first PRS configuration, and sending a second portion of a first set of one or more PRS resources, a second portion of a second set of one or more PRS resources, or a combination thereof in a second PRS configuration. In some embodiments, process 900 includes sending to the UE an explicit mapping for replacing at least one PRS resource in the first set with at least one PRS resource in the second set, a set of mapping rules for replacing at least one PRS resource in the first set with at least one PRS resource in the second set, or a combination thereof.
[0138]
[0140] Process 900 may include additional embodiments, such as any single embodiment or any combination of embodiments relating to one or more other processes described below and / or elsewhere in this specification. Figure 9 shows an exemplary block of Process 900, but in some implementations, Process 900 may include additional blocks, fewer blocks, different blocks, or blocks configured differently, in addition to those shown in Figure 9. As an addition or alternative, two or more blocks of Process 900 may be performed in parallel.
[0139]
[0141] As should be understood, the technical advantage of the technique presented herein is that dividing PRS resources into a global set, each with members uniquely identified using identifiers typically used by all UEs, avoids ambiguity regarding which PRS resources the shared information is associated with. Since all UEs use the same unique identifier for the same PRS resources in the global set, UEs can share location information on sidelinks without ambiguity, for example, UEs do not need an intermediary to match or map a dedicated identifier used by one UE to a dedicated identifier used by another UE.
[0140]
[0142] The detailed explanation above shows that different features are grouped together in the examples. This format of disclosure should not be understood as an intention that the exemplary clauses have more features than those explicitly stated in each clause. Rather, the various aspects of this disclosure may contain fewer features than all features of the individual exemplary clauses disclosed. Accordingly, the following clauses should be considered incorporated herein, and each clause may exist as a separate example by itself. Each dependent clause may, in the clause, refer to a specific combination with one of the other clauses, but the (one or more) aspects of that dependent clause are not limited to a specific combination. It will be understood that other exemplary clauses may also include combinations of (one or more) dependent clause aspects with the subject matter of any other dependent or independent clause, or any combination of features with other dependent and independent clauses. The various aspects disclosed herein explicitly include certain combinations (for example, contradictory aspects such as defining an element as both an insulator and a conductor) unless it is explicitly stated or easily inferred that such combinations are not intended. Furthermore, it is also intended that the form of the clause may be included in any other independent clause, even if that clause is not directly subordinate to that independent clause.
[0141]
[0143] Implementation examples are described in the following numbered sections.
[0142]
[0144] Clause 1. A method of wireless communication performed by a user device (UE), the method comprising: receiving from a network node a PRS configuration that defines or indicates a plurality of positioning reference signal (PRS) resources having unique identifiers; and the plurality of PRS resources performing positioning operations according to a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs serviced by a location server to identify the relevant PRS resources.
[0143]
[0145] Clause 2. The method according to Clause 1, wherein for each of one or more PRS resources in the first set, the associated identifier is used by all UEs served by one or more additional location servers to identify the associated PRS resource.
[0144]
[0146] Clause 3. The method described in any of Clauses 1 to 2, wherein each of the multiple PRS resources relates to a frequency layer (FL), transmit / receive point (TRP), PRS resource set, or a combination thereof.
[0145]
[0147] Clause 4. The method of any one of Clauses 1 to 3, wherein receiving at least one PRS configuration comprises receiving at least one PRS configuration via broadcast, multicast, or unicast transmission.
[0146]
[0148] Clause 5. The method of any one of Clauses 1 to 4, further comprising receiving a request from a second UE to share positioning information, sharing with the second UE positioning information relating to at least one PRS resource in a first set of one or more PRS resources, and not sharing positioning information relating to a PRS resource not in the first set of one or more PRS resources.
[0147]
[0149] The method of Clause 6, wherein receiving a request to share positioning information comprises receiving a request via sidelink (SL) communication, and sharing positioning information with a second UE relating to at least one PRS resource in a first set of one or more PRS resources comprises sharing positioning information via SL communication, or a combination thereof.
[0148]
[0150] Clause 7. The method of any one of Clauses 5 to 6, wherein sharing positioning information with a second UE relating to at least one PRS resource in a first set of one or more PRS resources comprises sending positioning information relating to at least one PRS resource in a first set of one or more PRS resources to the second UE, receiving positioning information relating to at least one PRS resource in a first set of one or more PRS resources from the second UE, or a combination thereof.
[0149]
[0151] Clause 8. The method of any one of Clauses 1 to 7, wherein the multiple PRS resources further comprise a second set of one or more PRS resources, wherein each of the one or more PRS resources in the second set is mapped to a relevant identifier that is specific to the UE and not used by all UEs served by the location server, in order to identify the relevant PRS resource.
[0150]
[0152] Clause 9. The method according to Clause 8, wherein receiving at least one PRS configuration comprises receiving a first set of one or more PRS resources in a first PRS configuration and receiving a second set of one or more PRS resources in a second PRS configuration.
[0151]
[0153] Clause 10. The method of Clause 9, wherein receiving a second PRS configuration comprises receiving a second PRS configuration via unicast or multicast transmission.
[0152]
[0154] Clause 11. The method according to any one of Clauses 8 to 10, wherein receiving at least one PRS configuration comprises receiving at least a first portion of a first set of one or more PRS resources and at least a first portion of a second set of one or more PRS resources in a first PRS configuration, and receiving a second portion of a first set of one or more PRS resources, a second portion of a second set of one or more PRS resources, or a combination thereof in a second PRS configuration.
[0153]
[0155] Clause 12. The method of any one of Clauses 8 to 11, further comprising replacing at least one PRS resource in the first set with at least one PRS resource in the second set.
[0154]
[0156] Clause 13. The method of Clause 12, further comprising: receiving an explicit mapping from a network node, wherein the replacement of at least one PRS resource in a first set with at least one PRS resource in a second set is carried out in accordance with the explicit mapping; receiving a set of mapping rules from a network node, wherein the replacement of at least one PRS resource in a first set with at least one PRS resource in a second set is carried out in accordance with a mapping derived from the set of mapping rules; or a combination thereof.
[0155]
[0157] Clause 14. A method of wireless communication performed by a network node, the method comprising determining a plurality of PRS resources having unique identifiers, and sending to a UE at least one PRS configuration that defines or indicates the first set, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs served by a location server to identify the relevant PRS resources.
[0156]
[0158] Clause 15. The method of Clause 14, wherein for each of one or more PRS resources in the first set, the associated identifier is used by all UEs served by one or more additional location servers to identify the associated PRS resource.
[0157]
[0159] Clause 16. The method described in any of Clauses 14 to 15, wherein each of the multiple PRS resources relates to a frequency layer (FL), transmit / receive point (TRP), PRS resource set, or a combination thereof.
[0158]
[0160] Clause 17. The method of any one of Clauses 14 to 16, wherein sending at least one PRS configuration comprises sending at least one PRS configuration via broadcast, multicast, or unicast transmission.
[0159]
[0161] Clause 18. The method of any of Clauses 14 to 17, wherein the plurality of PRS resources further comprises a second set of one or more PRS resources, wherein each of the one or more PRS resources in the second set is mapped to a relevant identifier which is specific to the UE and not used by all UEs served by the location server, in order to identify the relevant PRS resource.
[0160]
[0162] Clause 19. The method according to Clause 18, wherein sending at least one PRS configuration comprises sending a first set of one or more PRS resources in a first PRS configuration and sending a second set of one or more PRS resources in a second PRS configuration.
[0161]
[0163] Clause 20. The method of Clause 19, wherein sending the second PRS configuration comprises sending the second PRS configuration via unicast or multicast transmission.
[0162]
[0164] Clause 21. The method according to any one of Clauses 18 to 20, wherein sending at least one PRS configuration comprises sending at least a first portion of a first set of one or more PRS resources and at least a first portion of a second set of one or more PRS resources in a first PRS configuration, and sending a second portion of a first set of one or more PRS resources, a second portion of a second set of one or more PRS resources, or a combination thereof in a second PRS configuration.
[0163]
[0165] The method of Clause 21, further comprising sending to Clause 22.UE an explicit mapping for replacing at least one PRS resource in a first set with at least one PRS resource in a second set, a set of mapping rules for replacing at least one PRS resource in a first set with at least one PRS resource in a second set, or a combination thereof.
[0164]
[0166] Clause 23. An apparatus comprising memory, a communication interface, and at least one processor communicatively coupled to the memory and the communication interface, wherein the memory, the communication interface, and at least one processor are configured to perform the method described in any of Clauses 1 to 22.
[0165]
[0167] Clause 24. An apparatus comprising means for carrying out the method described in any of Clauses 1 to 22.
[0166]
[0168] Clause 25. A non-temporary computer-readable medium for storing computer-executable instructions, wherein the computer-executable instructions comprise at least one instruction causing a computer or processor to perform the method described in any of Clauses 1 to 22.
[0167]
[0169] Those skilled in the art will understand that information and signals can be represented using any of the various different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description can be represented by voltage, electric current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.
[0168]
[0170] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, circuits, and algorithmic steps described in relation to the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly demonstrate this hardware-software compatibility, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their function. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functions in various ways for each specific application, but such decisions should not be construed as resulting in a departure from the scope of this disclosure.
[0169]
[0171] The various exemplary logic blocks, modules, and circuits described in relation to the embodiments disclosed herein may be implemented or carried out using general-purpose processors, digital signal processors (DSPs), ASICs, field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, or any other such configuration.
[0170]
[0172] The methods, sequences, and / or algorithms described in relation to the embodiments disclosed herein may be implemented directly in hardware, in software modules executed by a processor, or in a combination of both. The software modules may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM®), registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., a UE). Alternatively, the processor and storage medium may reside as separate components in a user terminal.
[0171]
[0173] In one or more exemplary embodiments, the described functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted via computer-readable media as one or more instructions or codes. Computer-readable media include both computer storage media and computer communication media, including any media that enables the transfer of computer programs from one location to another. Storage media can be any available media that can be accessed by a computer. Such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk 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. Any connection is also appropriately 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 technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of media. As used herein, disk and disc include compact disc (CD), laserdisc (disc), optical disc (disc), digital versatile disc (disc) (DVD), floppy disk (disc), and Blu-ray (disc), where disk typically reproduces data magnetically and disc optically reproduces data by laser. Any combination of the above should also be included within the scope of computer-readable media.
[0172]
[0174] While the above disclosures illustrate exemplary aspects of the Disclosure, it should be noted that various changes and modifications can be made herein without departing from the scope of the Disclosure as defined by the appended claims. The functions, steps, and / or actions of the method claims in the aspects of the Disclosure described herein do not need to be performed in a specific order. Furthermore, while elements of the Disclosure may be described or claimed in the singular, the plural is intended unless explicitly stated to limit them to the singular. The invention described in the original claims of this application is listed below. [C1] A method of wireless communication performed by a user device (UE), wherein the method is: Receiving from a network node at least one PRS configuration that defines or indicates a plurality of positioning reference signal (PRS) resources having unique identifiers, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to an associated identifier used by all UEs served by the location server to identify the associated PRS resources. Perform positioning operations according to at least one PRS configuration as described above. A method that includes [a certain feature]. [C2] The method of C1, wherein for each of the one or more PRS resources in the first set, the associated identifier is used by all UEs served by one or more additional location servers to identify the associated PRS resource. [C3] The method according to C1, wherein each of the plurality of PRS resources is associated with a frequency layer (FL), a transmit / receive point (TRP), a PRS resource set, or a combination thereof. [C4] The method of C1, wherein receiving the at least one PRS configuration comprises receiving the at least one PRS configuration via broadcast, multicast, or unicast transmission. [C5] Receiving a request from the second UE to share positioning information, The second UE shares positioning information related to at least one PRS resource within the first set of one or more PRS resources, and does not share positioning information related to a PRS resource that is not within the first set of one or more PRS resources. A method of C1 that further includes the following: [C6] The method of C5, wherein receiving the request for sharing positioning information comprises receiving the request via sidelink (SL) communication, and sharing the positioning information with the second UE relating to at least one PRS resource in the first set of one or more PRS resources comprises sharing the positioning information via SL communication, or a combination thereof. [C7] Sharing the positioning information with the second UE is related to at least one PRS resource within the first set of one or more PRS resources. Sending positioning information to the second UE relating to at least one PRS resource within the first set of one or more PRS resources, Receiving positioning information from the second UE relating to one or more PRS resources in the first set, or a combination thereof A method of C5 comprising the same as described above. [C8] The method of C1, wherein the plurality of PRS resources further comprises a second set of one or more PRS resources, wherein each of the one or more PRS resources in the second set is mapped to an associated identifier that is specific to the UE and not used by all UEs served by the location server, in order to identify the associated PRS resource. [C9] The method according to C8, wherein receiving the at least one PRS configuration comprises receiving the first set of one or more PRS resources in a first PRS configuration and receiving the second set of one or more PRS resources in a second PRS configuration. [C10] The method of C9, wherein receiving the second PRS configuration comprises receiving the second PRS configuration via unicast or multicast transmission. [C11] Receiving the aforementioned at least one PRS configuration, Receiving at least a first portion of the first set of one or more PRS resources and at least a first portion of the second set of one or more PRS resources in the first PRS configuration, Receiving, in a second PRS configuration, a second part of the first set of one or more PRS resources, a second part of the second set of one or more PRS resources, or a combination thereof. A method of C8 comprising the same as described above. [C12] Replacing at least one PRS resource in the first set with at least one PRS resource in the second set. A method using C8 that further includes these features. [C13] Receiving an explicit mapping from a network node, wherein the replacement of at least one PRS resource in the first set with at least one PRS resource in the second set is performed in accordance with the explicit mapping. The network node receives a set of mapping rules, wherein at least one PRS resource in the first set is replaced with at least one PRS resource in the second set, in accordance with the mapping derived from the set of mapping rules. or a combination thereof A method for C12 that further includes the following features. [C14] A method of wireless communication performed by a network node, wherein the method is Determining a plurality of PRS resources having unique identifiers, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs served by the location server to identify the related PRS resources. Sending the UE at least one PRS configuration that defines or indicates the aforementioned first set A method that includes [a certain feature]. [C15] The method according to C14, wherein for each of the one or more PRS resources in the first set, the associated identifier is used by all UEs served by one or more additional location servers to identify the associated PRS resource. [C16] The method according to C14, wherein each of the plurality of PRS resources is associated with a frequency layer (FL), a transmit / receive point (TRP), a PRS resource set, or a combination thereof. [C17] The method according to C14, wherein sending the at least one PRS configuration comprises sending the at least one PRS configuration via broadcast, multicast, or unicast transmission. [C18] The method according to C14, wherein the plurality of PRS resources further comprises a second set of one or more PRS resources, wherein each of the one or more PRS resources in the second set is mapped to an associated identifier that is specific to the UE and not used by all UEs served by the location server, in order to identify the associated PRS resource. [C19] The method according to C18, wherein sending the at least one PRS configuration comprises sending the first set of one or more PRS resources in a first PRS configuration and sending the second set of one or more PRS resources in a second PRS configuration. [C20] The method according to C19, wherein sending the second PRS configuration comprises sending the second PRS configuration via unicast or multicast transmission. [C21] Sending the aforementioned at least one PRS configuration is Sending at least a first portion of the first set of one or more PRS resources and at least a first portion of the second set of one or more PRS resources in the first PRS configuration, Sending one or more PRS resources in a second PRS configuration, a second part of the first set of PRS resources, a second part of the second set of PRS resources, or a combination thereof. A method of C18 comprising the same equipment. [C22] Sending the UE an explicit mapping to replace at least one PRS resource in the first set with at least one PRS resource in the second set, a set of mapping rules to replace at least one PRS resource in the first set with at least one PRS resource in the second set, or a combination thereof. A method for C21 that further incorporates these features. [C23] Memory and Communication interface, The memory and at least one processor that is communicatively coupled to the communication interface A user device (UE) comprising, wherein the at least one processor is The communication interface receives from a network node at least one PRS configuration that defines or indicates a plurality of positioning reference signal (PRS) resources having a unique identifier, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs served by the location server to identify the related PRS resources. Perform positioning operations according to at least one PRS configuration as described above. User equipment (UE) configured to perform the following actions. [C24] The UE described in C23, wherein for each of the one or more PRS resources in the first set, the associated identifier is used by all UEs served by one or more additional location servers to identify the associated PRS resource. [C25] Each of the aforementioned PRS resources relates to a frequency layer (FL), a transmit / receive point (TRP), a PRS resource set, or a combination thereof, as described in C23. [C26] The UE according to C23, wherein the at least one processor is configured to receive the at least one PRS configuration, the at least one processor is configured to receive the at least one PRS configuration via broadcast, multicast, or unicast transmission. [C27] The aforementioned at least one processor, The communication interface receives a request from the second UE to share positioning information, The second UE shares positioning information related to at least one PRS resource within the first set of one or more PRS resources, and does not share positioning information related to a PRS resource that is not within the first set of one or more PRS resources. The UE described in C23 is further configured to perform the following actions. [C28] The UE according to C27, wherein receiving the request to share positioning information comprises receiving the request via sidelink (SL) communication, and sharing the positioning information with the second UE relating to at least one PRS resource in the first set of one or more PRS resources comprises sharing the positioning information via SL communication, or a combination thereof. [C29] The at least one processor is configured to share the positioning information with the second UE, relating to at least one PRS resource in the first set of one or more PRS resources, The communication interface causes the second UE to send positioning information related to at least one PRS resource within the first set of one or more PRS resources. Receiving positioning information from the second UE via the communication interface, relating to one or more PRS resources in the first set, and at least one PRS resource in the first set. or a combination thereof A UE as described in C27, comprising being configured to perform the following actions. [C30] The UE according to C23, wherein the plurality of PRS resources further comprises a second set of one or more PRS resources, wherein each of the one or more PRS resources in the second set is mapped to a relevant identifier that is specific to the UE and not used by all UEs served by the location server, in order to identify the relevant PRS resource. [C31] The UE according to C30, wherein the at least one processor is configured to receive the at least one PRS configuration, the at least one processor is configured to receive the first set of one or more PRS resources in a first PRS configuration and the second set of one or more PRS resources in a second PRS configuration. [C32] The UE according to C31, wherein the at least one processor is configured to receive the second PRS configuration, and the at least one processor is configured to receive the second PRS configuration via unicast or multicast transmission. [C33] The fact that the at least one processor is configured to receive the at least one PRS configuration means that the at least one processor is configured The communication interface receives, at least a first portion of the first set of one or more PRS resources in the first PRS configuration, and at least a first portion of the second set of one or more PRS resources. The communication interface receives, via the aforementioned communication interface, a second portion of the first set of one or more PRS resources in a second PRS configuration, a second portion of the second set of one or more PRS resources, or a combination thereof. A UE as described in C30, which is configured to perform the following actions. [C34] The aforementioned at least one processor, Replacing at least one PRS resource in the first set with at least one PRS resource in the second set. The UE described in C30 is further configured to perform the following actions. [C35] The aforementioned at least one processor is The explicit mapping is received from the network node via the communication interface, wherein the replacement of at least one PRS resource in the first set with at least one PRS resource in the second set is performed in accordance with the explicit mapping. The network node receives a set of mapping rules via the communication interface, wherein the replacement of at least one PRS resource in the first set with at least one PRS resource in the second set is performed according to the mapping derived from the set of mapping rules. or a combination thereof The UE described in C34 is further configured to perform the following actions. [C36] Memory and Communication interface, The memory and at least one processor that is communicatively coupled to the communication interface A network node comprising, wherein the at least one processor is Determining a plurality of PRS resources having unique identifiers, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs served by the location server to identify the related PRS resources. The UE is instructed by the communication interface to send at least one PRS configuration that defines or indicates the first set. A network node configured to perform the following actions. [C37] The network node described in C36, wherein for each of the one or more PRS resources in the first set, the associated identifier is used by all UEs served by one or more additional location servers to identify the associated PRS resource. [C38] A network node as described in C36, where each of the aforementioned PRS resources is associated with a frequency layer (FL), a transmit / receive point (TRP), a PRS resource set, or a combination thereof. [C39] The network node according to C36, wherein the at least one processor is configured to cause the communication interface to send the at least one PRS configuration, or the at least one processor is configured to cause the communication interface to send the at least one PRS configuration via broadcast, multicast, or unicast transmission. [C40] The network node described in C36, wherein the plurality of PRS resources further comprises a second set of one or more PRS resources, wherein each of the one or more PRS resources in the second set is mapped to a relevant identifier that is specific to the UE and not used by all UEs served by the location server, in order to identify the relevant PRS resource. [C41] The network node according to C40, wherein the at least one processor is configured to cause the communication interface to send the at least one PRS configuration, and the at least one processor is configured to cause the communication interface to send the first set of one or more PRS resources in a first PRS configuration and the second set of one or more PRS resources in a second PRS configuration. [C42] The network node according to C41, wherein the at least one processor is configured to cause the communication interface to send the second PRS configuration, or the at least one processor is configured to cause the communication interface to send the second PRS configuration via unicast or multicast transmission. [C43] The at least one processor is configured to cause the communication interface to send the at least one PRS configuration, The communication interface is made to send at least a first portion of the first set of one or more PRS resources and at least a first portion of the second set of one or more PRS resources in the first PRS configuration. The communication interface is made to send one or more PRS resources in the second PRS configuration, a second portion of the first set, a second portion of the second set of one or more PRS resources, or a combination thereof. A network node according to C40, which is configured to cause the communication interface to perform the above. [C44] The aforementioned at least one processor, The UE is instructed to send the communication interface an explicit mapping to replace at least one PRS resource in the first set with at least one PRS resource in the second set, a set of mapping rules to replace at least one PRS resource in the first set with at least one PRS resource in the second set, or a combination thereof. A network node as described in C43, further configured to perform the following actions. [C45] Means for receiving from a network node a PRS configuration that defines or indicates a plurality of positioning reference signal (PRS) resources having unique identifiers, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to an associated identifier used by all UEs served by the location server to identify the associated PRS resources. Means for performing positioning operations according to the at least one PRS configuration described above, User equipment (UE) equipped with these features. [C46] Means for determining a plurality of PRS resources having unique identifiers, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs served by the location server to identify the related PRS resources. Means for sending to the UE at least one PRS configuration that defines or indicates the first set A network node equipped with these features. [C47] A non-temporary computer-readable medium for storing computer-executable instructions, wherein the computer-executable instructions, when executed by user equipment (UE), Receiving from a network node at least one PRS configuration that defines or indicates a plurality of positioning reference signal (PRS) resources having unique identifiers, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to an associated identifier used by all UEs served by the location server to identify the associated PRS resources. Perform positioning operations according to at least one PRS configuration as described above. A non-temporary computer-readable medium that causes the aforementioned UE to perform the action. [C48] A non-temporary computer-readable medium for storing computer-executable instructions, wherein the computer-executable instructions, when executed by a network node, Determining a plurality of PRS resources having unique identifiers, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs served by the location server to identify the related PRS resources. Sending the UE at least one PRS configuration that defines or indicates the aforementioned first set A non-temporary computer-readable medium that causes the network node to perform the aforementioned action.
Claims
1. A method of wireless communication performed by a user device (UE), wherein the method is: Receiving from a network node at least one PRS configuration that defines or indicates a plurality of positioning reference signal (PRS) resources having unique identifiers, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to an associated identifier used by all UEs served by the location server to identify the associated PRS resources. The positioning operation is performed according to the aforementioned at least one PRS configuration. Equipped with, The plurality of PRS resources further comprises a second set of one or more PRS resources, wherein each of the one or more PRS resources in the second set is mapped to a relevant identifier that is specific to the UE and not used by all UEs served by the location server, in order to identify the associated PRS resource. method.
2. The method according to claim 1, wherein for each of the one or more PRS resources in the first set, the associated identifier is used by all UEs served by one or more additional location servers to identify the associated PRS resource.
3. The method according to claim 1, wherein each of the plurality of PRS resources is associated with a frequency layer (FL), a transmit / receive point (TRP), a PRS resource set, or a combination thereof.
4. Receiving a request from the second UE to share positioning information, The second UE shares positioning information related to at least one PRS resource within the first set of one or more PRS resources, and does not share positioning information related to a PRS resource that is not within the first set of one or more PRS resources. The method according to claim 1, further comprising:
5. The method according to claim 4, wherein receiving the request for sharing positioning information comprises receiving the request via sidelink (SL) communication, and sharing the positioning information with the second UE relating to at least one PRS resource in the first set of one or more PRS resources comprises sharing the positioning information via SL communication, or a combination thereof.
6. Sharing the positioning information with the second UE is related to at least one PRS resource within the first set of one or more PRS resources. Sending positioning information to the second UE relating to at least one PRS resource within the first set of one or more PRS resources, Receiving positioning information from the second UE relating to at least one PRS resource within the first set of one or more PRS resources, or a combination thereof The method according to claim 4, comprising:
7. Receiving the aforementioned at least one PRS configuration, Receiving at least a first portion of the first set of one or more PRS resources and at least a first portion of the second set of one or more PRS resources in the first PRS configuration, Receiving a second portion of the first set of one or more PRS resources, a second portion of the second set of one or more PRS resources, or a combination thereof, in a second PRS configuration. The method according to claim 1, comprising:
8. Replacing at least one PRS resource in the first set with at least one PRS resource in the second set. Furthermore, Optional, Receiving an explicit mapping from a network node, wherein the replacement of at least one PRS resource in the first set with at least one PRS resource in the second set is performed in accordance with the explicit mapping. The network node receives a set of mapping rules, wherein at least one PRS resource in the first set is replaced with at least one PRS resource in the second set, in accordance with the mapping derived from the set of mapping rules. or a combination thereof The method according to claim 1, further comprising:
9. A method of wireless communication performed by a network node, wherein the method is Determining a plurality of PRS resources having unique identifiers, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs served by the location server to identify the related PRS resources. Sending to the UE at least one PRS configuration that defines or indicates the first set, Equipped with, The plurality of PRS resources further comprises a second set of one or more PRS resources, wherein each of the one or more PRS resources in the second set is mapped to a relevant identifier that is specific to the UE and not used by all UEs served by the location server, in order to identify the associated PRS resource. method.
10. Memory and Communication interface, The memory and at least one processor that is communicatively coupled to the communication interface A user device (UE) comprising, wherein the at least one processor is The communication interface receives from a network node at least one PRS configuration that defines or indicates a plurality of positioning reference signal (PRS) resources having a unique identifier, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs served by the location server to identify the associated PRS resource. The positioning operation is performed according to the aforementioned at least one PRS configuration. It is configured to do the following: The plurality of PRS resources further comprises a second set of one or more PRS resources, wherein each of the one or more PRS resources in the second set is mapped to a relevant identifier that is specific to the UE and not used by all UEs served by the location server, in order to identify the associated PRS resource. User equipment (UE).
11. The UE according to claim 10, further configured to carry out the method described in any one of claims 2 to 8.
12. Memory and Communication interface, The memory and at least one processor that is communicatively coupled to the communication interface A network node comprising, wherein the at least one processor is Determining a plurality of PRS resources having unique identifiers, wherein the plurality of PRS resources comprises a first set of one or more PRS resources, wherein each of the one or more PRS resources in the first set is mapped to a relevant identifier used by all UEs served by the location server to identify the related PRS resources. The UE is instructed by the communication interface to send at least one PRS configuration that defines or indicates the first set. Configured to perform, The plurality of PRS resources further comprises a second set of one or more PRS resources, wherein each of the one or more PRS resources in the second set is mapped to a relevant identifier that is specific to the UE and not used by all UEs served by the location server, in order to identify the associated PRS resource. Network node.
13. A non-temporary computer-readable medium for storing computer-executable instructions, wherein the computer-executable instructions, when executed by a user device (UE), cause the UE to perform the method according to any one of claims 1 to 8.
14. A non-temporary computer-readable medium for storing computer-executable instructions, wherein the computer-executable instructions, when executed by a network node, cause the network node to perform the method according to claim 9.
Citation Information
Patent Citations
Location information in communication networks
JP2018528644A
Method and apparatus for measuring a position in a wireless communication network
US20200351618A1
Beam based positioning measurements and measurement reporting
WO2020071992A1