User device anchor capability display for sidelink-based positioning

Abstract

Techniques for wireless communications are disclosed. In one aspect, a first user equipment (UE) receives from a network entity a capability query message for a sidelink positioning procedure, the capability query message including at least a request for an indication of whether the first UE has a capability to provide a location of the first UE for the sidelink positioning procedure, and transmits to a network node a capability information message indicating one or more capabilities of the first UE to participate in the sidelink positioning procedure, the one or more capabilities of the first UE including at least an indication of whether the first UE has a capability to provide a location of the first UE for the sidelink positioning procedure.

Description

Technical Field

[0001] Aspects of the present disclosure generally relate to wireless communication, and more particularly to sidelink-based positioning.

Background Art

[0002] Wireless communication systems have evolved through various generations, including first-generation analog wireless telephone service (1G), second-generation (2G) digital wireless telephone service (including interim 2.5G and 2.75G networks), third-generation (3G) high-speed data, Internet-capable wireless service, and fourth-generation (4G) service (e.g., Long-Term Evolution (LTE) or WiMax). Currently, there are many different types of wireless communication systems in use, including cellular systems 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), Global System for Mobile Communications (GSM), etc.

[0003] The fifth-generation (5G) wireless standard, called New Radio (NR), among other improvements, is required to have higher data transfer speeds, a larger number of connections, and better coverage. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide a data rate of tens of megabits per second to each of tens of thousands of users and one gigabit per second to dozens of workers on an office floor. Hundreds of thousands of simultaneous connections should be supported to support large-scale sensor deployment. Therefore, the spectral efficiency of 5G mobile communication should be significantly extended compared to current 4G standards. Further, signaling efficiency should be extended and latency should be significantly reduced compared to current standards.

[0004] In particular, vehicle-to-everything (V2X) communication technologies are being implemented to support autonomous driving applications such as wireless communication between vehicles, between vehicles and roadside infrastructure, and between vehicles and pedestrians, taking advantage of 5G's increased data rates and reduced latency. [Overview of the project] [Means for solving the problem]

[0005] The following provides a simplified overview relating to one or more embodiments disclosed herein. Therefore, this overview should not be considered a broad overview relating to all intended embodiments, nor should it be considered to identify any major or significant elements relating to all intended embodiments, or to define the scope relating to any particular embodiment. Accordingly, the following overview has the sole purpose of providing, in a simplified form, some concepts relating to one or more embodiments relating to the mechanisms disclosed herein, prior to the detailed description presented below.

[0006] In one embodiment, a wireless communication method performed by a first user device (UE) includes the steps of: receiving a capability inquiry message for a sidelink positioning procedure from a network node, the capability inquiry message comprising at least a request for an indication of whether the first UE has the capability to provide the first UE's location for a sidelink positioning procedure; and transmitting a capability information message to the network node indicating one or more capabilities of the first UE to participate in a sidelink positioning procedure, the one or more capabilities of the first UE comprising at least an indication of whether the first UE has the capability to provide the first UE's location for a sidelink positioning procedure.

[0007] In one embodiment, a method of wireless communication performed by a network node includes the steps of: sending a capability inquiry message to a first user device (UE) for a sidelink positioning procedure, the capability inquiry message comprising at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure; and receiving a capability information message from the first UE indicating one or more capabilities of the first UE to participate in a sidelink positioning procedure, the one or more capabilities of the first UE comprising at least an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure.

[0008] In one embodiment, a first user device (UE) includes a memory and at least one processor communicatively coupled to the memory, wherein the memory and at least one processor are configured to receive capability inquiry messages for a sidelink positioning procedure from a network node, the capability inquiry message comprising at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure, and to transmit capability information messages to the network node indicating one or more capabilities of the first UE to participate in a sidelink positioning procedure, the one or more capabilities of the first UE comprising at least an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure.

[0009] In one embodiment, a network node includes a memory and at least one processor communicatively coupled to the memory, wherein the memory and at least one processor are configured to send capability inquiry messages to a first user equipment (UE) for a sidelink positioning procedure, the capability inquiry message comprising at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure, and to receive capability information messages from the first UE indicating one or more capabilities of the first UE to participate in a sidelink positioning procedure, the one or more capabilities of the first UE comprising at least an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure.

[0010] In one embodiment, a first user device (UE) includes means for receiving capability inquiry messages for a sidelink positioning procedure from a network node, the capability inquiry message comprising at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure, and means for transmitting capability information messages to the network node indicating one or more capabilities of the first UE to participate in a sidelink positioning procedure, the one or more capabilities of the first UE comprising at least an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure.

[0011] In one embodiment, a network node includes means for transmitting a capability inquiry message to a first user device (UE) for a sidelink positioning procedure, the capability inquiry message comprising at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure, and means for receiving a capability information message from the first UE indicating one or more capabilities of the first UE to participate in a sidelink positioning procedure, the one or more capabilities of the first UE comprising at least an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure.

[0012] In one embodiment, a non-temporary computer-readable medium storing computer-executable instructions includes at least one instruction instructing a first UE to receive a capability inquiry message from a network node, the capability inquiry message for a sidelink positioning procedure, the capability inquiry message for a sidelink positioning procedure, the capability inquiry message for a sidelink positioning procedure, the capability inquiry message for a first user device (UE), the capability of a first UE to provide the location of a first UE for a sidelink positioning procedure, and at least one instruction instructing a first UE to send a capability information message to a network node indicating one or more capabilities of the first UE to participate in a sidelink positioning procedure, the capability of a first UE to provide the location of a first UE for a sidelink positioning procedure, the capability inquiry message

[0013] In one embodiment, a non-temporary computer-readable medium storing computer-executable instructions includes at least one instruction instructing a network node to send a capability inquiry message to a first user device (UE), the capability inquiry message for a sidelink positioning procedure, the capability inquiry message for a sidelink positioning procedure, the capability inquiry message for a first UE, the capability inquiry message for a first UE, the capability inquiry message for a first UE, the capability inquiry message for a first UE, the capability inquiry message for a first UE, the capability inquiry message for a first UE, the capability inquiry message for a first UE, the capability inquiry message for a first UE, the capability inquiry message for a first UE, the capability inquiry message for a first UE, the capability inquiry message for a first UE, the capability inquiry message for a sidelink positioning procedure

[0014] Other purposes 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] The accompanying drawings are provided to aid in describing various aspects of this disclosure and are provided solely for the purpose of describing the aspects, not as an limitation of those aspects. [Brief explanation of the drawing]

[0016] [Figure 1] This figure shows an exemplary wireless communication system according to an aspect of the present disclosure. [Figure 2A] This figure shows an exemplary wireless network structure according to an aspect of the present disclosure. [Figure 2B] This figure shows an exemplary wireless network structure according to an aspect of the present disclosure. [Figure 3A] This is a simplified block diagram of some exemplary embodiments of a component that may be used in user equipment (UE) and may be configured to support communications as taught herein. [Figure 3B]This is a simplified block diagram of some exemplary embodiments of a component that may be used in a base station and may be configured to support communications as taught herein. [Figure 3C] This is a simplified block diagram of some exemplary embodiments of components that may be employed in a network entity and may be configured to support communications as taught herein. [Figure 4] This figure shows an example of a wireless communication system that supports unicast sidelink establishment according to the aspects of this disclosure. [Figure 5] This figure shows an exemplary sidelink ranging and positioning procedure according to an aspect of the present disclosure. [Figure 6] This figure shows an example of a network-managed sidelink ranging and positioning procedure according to the aspects of this disclosure. [Figure 7] This figure shows another example of a network-managed sidelink ranging and positioning procedure according to an aspect of this disclosure. [Figure 8] This figure shows exemplary positioning anchor capability information elements according to an aspect of the present disclosure. [Figure 9A] This figure shows exemplary information elements that may be exchanged between two UEs to request and provide the anchor capability status of the UEs, according to aspects of this disclosure. [Figure 9B] This figure shows exemplary information elements that may be exchanged between two UEs to request and provide the anchor capability status of the UEs, according to aspects of this disclosure. [Figure 10A] This figure shows exemplary information elements that may be exchanged between a UE and a network entity to request and provide the anchor capability status of the UE, according to aspects of this disclosure. [Figure 10B] This figure shows exemplary information elements that may be exchanged between a UE and a network entity to request and provide the anchor capability status of the UE, according to aspects of this disclosure. [Figure 11] This figure shows an exemplary method of wireless communication according to an aspect of the present disclosure. [Figure 12] A diagram illustrating an exemplary method of wireless communication according to an aspect of the present disclosure. [Figure 13] A simplified block diagram of various devices configured to support wireless communication operations as taught herein. [Figure 14] A simplified block diagram of various devices configured to support wireless communication operations as taught herein. [Figure 15] A simplified block diagram of various devices configured to support wireless communication operations as taught herein. [Figure 16] A simplified block diagram of various devices configured to support wireless communication operations as taught herein.

Best Mode for Carrying Out the Invention

[0017] In a sidelink positioning procedure (a positioning procedure for positioning one or more UEs based on wireless signals exchanged between multiple UEs, including the UE being positioned), at least one of the other UEs should be able to provide its location to the UE (to serve as an "anchor" for location determination) based on wireless signals exchanged with one or more other user devices (UEs) during the procedure. Similarly, when a network entity manages a sidelink positioning procedure among multiple UEs, a prerequisite for determining which UEs should participate in the sidelink positioning procedure is knowing which of the UEs, if any, can serve as an anchor. Therefore, having a mechanism for a UE to notify the network and / or other UEs whether it can serve as an anchor for a sidelink positioning procedure enables better positioning, unless the positioning procedure attempts against a UE that indicates it does not have the ability to serve as an anchor. This disclosure provides a signaling mechanism for a UE to notify the network (and / or other UEs) of its ability to serve as an anchor for a sidelink positioning procedure. The information transmitted may include parameters indicating the UE's ability to serve as an anchor, its location, the accuracy of its location, and its ability to perform side-link positioning calculations based on receiving wireless signal measurements from other UEs. In one or more examples, the information elements used to constitute these parameters may be incorporated into an existing message or as part of a new message specific to side-link positioning.

[0018] The mechanism of this disclosure enables a UE to provide the ability to serve as an anchor for a sidelink positioning procedure, and enables a network node (base station, location server, or another UE) to receive this ability. Thus, the mechanism of this disclosure enables better positioning, unless the positioning procedure attempts it against a UE that indicates it cannot serve as an anchor, thereby reducing unnecessary signaling.

[0019] Additional embodiments of this disclosure are provided in the following description and related drawings, which cover various examples provided for illustrative purposes. Alternative embodiments may be devised without departing from the scope of this disclosure. In addition, well-known elements of this disclosure are not described in detail or are omitted so as not to obscure relevant details of this disclosure.

[0020] The terms “exemplary” and / or “example” are used herein to mean “acting as an example, case, or illustration.” Any aspect described herein as “exemplary” and / or “example” should not necessarily be construed as being preferable or advantageous to any other aspect. Similarly, the term “aspects of the disclosure” does not require that all aspects of the disclosure include the features, advantages, or modes of operation described herein.

[0021] Those skilled in the art will understand that the information and signals described below may be represented using any of a variety of different techniques and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the following description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof, depending in part with the specific application, in part with the desired design, in part with the corresponding technique.

[0022] Furthermore, many embodiments are described, for example, with respect to sequences 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 being executed by one or more processors, or a combination of both. In addition, sequences of actions described herein may be considered to be fully embodied in any form of non-temporary computer-readable storage medium storing a corresponding set of computer instructions that, at runtime, will cause or instruct the relevant processors of the device to perform the functionality described herein. Thus, various embodiments of this disclosure may be embodied in several different forms, all of which are intended to fall within the scope of the claimed subject matter. In addition, 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 actions described.

[0023] As used herein, the terms “User Equipment” (UE), “Vehicle UE” (V-UE), “Pedestrian UE” (P-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 computer mounted in a vehicle, a vehicle navigation device, a mobile phone, a router, a tablet computer, a laptop computer, an asset locating device, a wearable (e.g., a smartwatch, smart glasses, an augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.). A UE may be mobile or (e.g., stationary for a certain period of time) and may communicate with a Radio Access Network (RAN). As used herein, the term "UE" may be interchangeably referred to as "mobile device," "access terminal" or "AT," "client device," "wireless device," "subscriber device," "subscriber terminal," "subscriber station," "user terminal" or "UT," "mobile terminal," "mobile station," or variations thereof.

[0024] A V-UE is a type of UE that may be any in-vehicle wireless communication device, such as a navigation system, warning system, head-up display (HUD), onboard computer, in-vehicle information system, autonomous driving system (ADS), or advanced driver-assistance system (ADAS). Alternatively, a V-UE may be a portable wireless communication device (e.g., a cell phone, tablet computer) carried by the driver or passenger in the vehicle. The term "V-UE" may refer to an in-vehicle wireless communication device or the vehicle itself, depending on the context. A P-UE is a type of UE that may be a portable wireless communication device carried by a pedestrian (i.e., a user who is not driving or riding in the vehicle). A Sidelink UE (SL-UE) is any type of UE capable of sidelink communication and may be a V-UE, P-UE, or another type of UE (e.g., an IoT device). Generally, UEs can communicate with the core network via the RAN, and through the core network, UEs may connect to external networks such as the Internet and other UEs. Naturally, other mechanisms are also possible for the UE to connect to the core network and / or the internet, such as via a wired access network, a wireless local area network (WLAN) network (for example, based on IEEE 802.11), and others.

[0025] A base station may operate according to one of several RATs (Network Address Terminals) through which it communicates with a UE, depending on the network in which the UE is deployed. These RATs may also be called access points (APs), network nodes, node Bs, advanced node Bs (eNBs), next-generation eNBs (ng-eNBs), or New Radio (NR) node Bs (also known as gNBs or g-node Bs). Base stations may be primarily used to support wireless access by UEs, including supporting data connectivity, voice connectivity, and / or signaling connectivity for supported UEs. In some systems, base stations may provide purely edge node signaling functionality, while in others, they may provide additional control and / or network management functionality. A communication link through which a UE can send signals to a base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). A communication link through which a base station can send signals to a UE is called a downlink (DL) channel 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 a UL / reverse traffic channel or a DL / forward traffic channel.

[0026] 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, that physical TRP may 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, those physical TRPs may be the base station’s antenna array (for example, in a multi-input multiple-output (MIMO) system, or when the base station employs beamforming). When the term “base station” refers to multiple uncolocated physical TRPs, those physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium), or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, an uncollocated physical TRP may be a serving base station that receives measurement reports from the UE and adjacent base stations from which 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, when used herein, references to transmission from a base station or reception at a base station should be understood as referring to a specific TRP of the base station.

[0027] In some implementations supporting 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 RF 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 an RF signal to the UE) and / or a location measurement unit (for example, when receiving and measuring an RF signal from the UE).

[0028] An "RF signal" comprises an electromagnetic wave of a given frequency that transports 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 RF signal transmitted over different paths between the transmitter and receiver may be referred to as a "multipath" RF signal. As used herein, an RF signal may also be referred to as a "wireless signal" or simply a "signal" where the context makes it clear that the term "signal" refers to either a wireless signal or an RF signal.

[0029] Figure 1 shows an exemplary wireless communication system 100 according to an aspect of the present disclosure. The wireless communication system 100 (sometimes referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "BS") and various UEs 104. The base stations 102 may include 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 102 may include an eNB and / or ng-eNB corresponding to an LTE network in the wireless communication system 100, or a gNB corresponding to an NR network in the wireless communication system 100, or a combination of both, and the small cell base station may include femtocells, picocells, microcells, etc.

[0030] The base station 102 may collectively form a RAN and interface with a core network 174 (e.g., an Advanced Packet Core (EPC) or a 5G core (5GC)) via a backhaul link 122, and with one or more location servers 172 (e.g., a Location Management Function (LMF) or a Secure User Plane Location Platform (SLP)) via the core network 174. The location servers 172 may be part of the core network 174 or may be outside the core network 174. In addition to other functions, base stations 102 may perform functions related to one or more of the following: transferring user data, wireless 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, delivery for non-access stratum (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., via EPC / 5GC) via backhaul links 134, which may be wired or wireless.

[0031] 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 several frequency resources, e.g., carrier frequency, component carrier, carrier, band, etc.) and may be associated with an identifier (e.g., physical cell identifier (PCI), enhanced cell identifier (ECI), virtual cell identifier (VCI), cell global identifier (CGI), etc.) 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 specific base station, the term "cell" may, depending on the context, refer to a logical communication entity and one or both base stations that support it. In some cases, the term "cell" may also refer to a base station's geographical coverage area (e.g., a sector), insofar as carrier frequencies can be detected and used for communication within several parts of the geographical coverage area 110.

[0032] While adjacent to macrocell base stations 102, geographical coverage areas 110 may partially overlap (for example, within handover areas), and some of the geographical coverage areas 110 may be significantly overlapped by larger geographical coverage areas 110. For example, a small cell base station 102' (labeled "SC" instead of "small cell") may have a geographical coverage area 110' that significantly overlaps with the geographical coverage areas 110 of one or more macrocell base stations 102. A network containing both small cell base stations and macrocell base stations is sometimes called a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that can serve a restricted group called a closed subscriber group (CSG).

[0033] The communication link 120 between base station 102 and UE 104 may include uplink (also called reverse link) transmission from UE 104 to base station 102, and / or downlink (DL) (also called forward link) transmission from base station 102 to UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may operate through one or more carrier frequencies. Carrier allocation may be asymmetrical with respect to downlink and uplink (for example, more or fewer carriers may be allocated to downlink than uplink).

[0034] 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) or listen before talk (LBT) procedure before communication to determine whether the channel is available.

[0035] Small cell base station 102' may operate in licensed frequency spectrum and / or unlicensed frequency spectrum. When operating in unlicensed frequency spectrum, small cell base station 102' may employ LTE or NR technology and may use the same 5GHz unlicensed frequency spectrum used by WLAN AP150. Small cell base station 102' employing LTE / 5G in unlicensed frequency spectrum may expand coverage to the access network and / or increase the capacity of the access network. NR in unlicensed spectrum is sometimes referred to as NR-U. LTE in unlicensed spectrum is sometimes referred to as LTE-U, licensed assisted access (LAA), or MulteFire.

[0036] The wireless communication system 100 communicates with UE 182 and may further include a mmW base station 180 that can operate in millimeter-wave (mmW) frequencies and / or quasi-mmW frequencies. Extremely high frequency (EHF) is the RF portion of the electromagnetic spectrum. EHF ranges from 30 GHz to 300 GHz and has wavelengths between 1 millimeter and 10 millimeters. Radio waves in this band are sometimes called millimeter waves. Quasi-mmW may extend down to frequencies up to 3 GHz with a wavelength of 100 millimeters. The very high frequency (SHF) band, also called centimeter waves, extends between 3 GHz and 30 GHz. Communication using the mmW / quasi-mmW radio frequency bands has high path loss and relatively short distances. 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 distances. Furthermore, in alternative configurations, it will be understood that one or more base stations 102 may also transmit using mmW or quasi-mmW and beamforming. Therefore, it should be understood that the above examples are merely illustrative and should not be interpreted as limiting the various embodiments disclosed herein.

[0037] 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). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby bringing a faster and more powerful RF signal (in terms of data rate) to the receiving device. To change the directivity of an RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal in 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 points in different directions without actually moving the antennas. In detail, RF currents from the transmitters are fed to individual antennas with appropriate phase relationships so that the radio waves from separate antennas are added together to increase radiation in the desired direction, while suppressing radiation in undesirable directions.

[0038] A transmit beam can be quasi-co-located, meaning that to a receiver (e.g., a UE), the transmit beam appears to have the same parameters regardless of whether the transmit antenna of the network node itself is physically co-located. In NR, there are four types of quasi-co-location (QCL) relationships. In detail, a given type of QCL relationship means that several parameters of a second reference RF signal on a second beam can be derived from information about a source reference RF signal on the source beam. Thus, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, mean delay, and delay spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of a second reference RF signal transmitted on the 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 a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type D, the receiver can use the source reference RF signal to estimate the spatial receive parameters of a second reference RF signal transmitted on the same channel.

[0039] In receive beamforming, a receiver uses a received beam to amplify an RF signal detected on a given channel. For example, a receiver can increase the gain setting and / or adjust the phase setting of an antenna array in a particular direction to amplify an RF signal received from that direction (for example, to increase the gain level of such an RF signal). Therefore, when a receiver is said to beamform in a certain direction, it means that the beam gain in that direction is greater than the beam gain along other directions, or that the beam gain in that direction is the maximum compared to the beam gain of all other receive beams available to the receiver in that direction. This results in a stronger received signal intensity (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference + noise ratio (SINR), etc.) of the RF signal received from that direction.

[0040] Transmit and receive beams can have a spatial relationship. A spatial relationship means that parameters for a second beam (e.g., a transmit beam or a receive beam) for a second reference signal can be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam to send an uplink reference signal (e.g., a sounding reference signal (SRS)) to its base station, based on the parameters of the receive beam.

[0041] 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, the downlink beam is a transmit beam. However, if a UE forms a downlink beam, the downlink beam is a receive beam to receive 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, the uplink beam is an uplink receive beam, and if a UE forms an uplink beam, the uplink beam is an uplink transmit beam.

[0042] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands are designated as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that although a portion of FR1 is above 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar nomenclature issue can arise with respect to FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) designated as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0044] With the above aspects in mind, unless otherwise specified, terms such as "sub-6GHz" may broadly refer to frequencies that may be below 6GHz, within FR1, or include intermediate band frequencies, as used herein. Furthermore, unless otherwise specified, terms such as "millimeter wave" may broadly refer to frequencies that may include intermediate band frequencies, within FR2, FR4, FR4-a or FR4-1, and / or FR5, or within the EHF band, as used herein.

[0045] 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) used by the UE104 / 182 and the cell, where the 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 all common control channels and UE-specific control channels and may be a carrier in the 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 in the unlicensed frequencies. Since both the primary uplink carrier and primary downlink carrier are typically UE-specific, the secondary carrier only needs to contain the necessary signaling information and signals; for example, UE-specific signaling information and signals do not need to be present in the secondary carrier. This means that different UE104 / 182s within a cell may have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a “serving cell” (whether PCell or SCell) corresponds to a carrier frequency / component carrier through which several base stations are communicating, terms such as “cell,” “serving cell,” “component carrier,” and “carrier frequency” can be used interchangeably.

[0046] For example, still referring to Figure 1, one of the frequencies used by the macrocell base station 102 may be the anchor carrier (i.e., "PCell"), and the other frequencies used by the macrocell base station 102 and / or the mmW base station 180 may be the secondary carriers ("SCell"). Simultaneous transmission and / or reception of multiple carriers allows UE 104 / 182 to significantly increase its data transmission rate and / or data reception rate. For example, aggregated two 20MHz carriers in a multicarrier system would theoretically result in a doubling of the data rate (i.e., 40MHz) compared to what would be achieved with a single 20MHz carrier.

[0047] In the example in Figure 1, any of the illustrated UEs (shown in Figure 1 as a single UE 104 for simplicity) may receive signals 124 from one or more Earth-orbiting space vehicles (SVs) 112 (e.g., satellites). In one embodiment, the SVs 112 may be part of a satellite positioning system that the UEs 104 can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) arranged to enable a receiver (e.g., UE 104) to determine its location on or above the Earth, at least in part on positioning signals (e.g., signals 124) received from the transmitters. Such transmitters typically transmit signals marked with a set number of repeating pseudo-random noise (PN) codes. While usually located within the SVs 112, the transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. UE104 may include one or more dedicated receivers specifically designed to receive signals 124 for deriving geolocation information from SV112.

[0048] In satellite positioning systems, the use of signal 124 may be associated with use involving one or more global and / or regional navigation satellite systems, or may be otherwise enabled for such use, and may be augmented by various satellite-based augmentation systems (SBAS). For example, an SBAS may include augmentation systems that provide integrity information, differential corrections, etc., such as Wide Area Augmentation Systems (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunction Satellite Augmentation Systems (MSAS), Global Positioning System (GPS)-assisted Geoaugmented Navigation, or GPS and Geoaugmented Navigation Systems (GAGAN). Accordingly, the satellite positioning systems used herein may include any combination of one or more global and / or regional navigation satellites associated with one or more such satellite positioning systems.

[0049] In one embodiment, SV112 may, as an addition or alternative, be part of one or more non-terrestrial networks (NTN). In an NTN, SV112 is connected to an earth station (also called a ground station, NTN gateway, or gateway), which is then connected to an element in the 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in 5GC. This element then provides access to other elements in the 5G network, and ultimately to entities outside the 5G network, such as internet web servers and other user devices. In this way, UE104 may receive communication signals (e.g., signal 124) from SV112 in place of, or in addition to, communication signals from the terrestrial base station 102.

[0050] In particular, leveraging the increased data rates and reduced latency of NR, Vehicle-to-Everything (V2X) communication technology is being implemented to support intelligent transport system (ITS) applications such as wireless communication between vehicles (V2V), between vehicles and roadside infrastructure (V2I), and between vehicles and pedestrians (V2P). The goal is for vehicles to be able to sense their surroundings and communicate that information to other vehicles, infrastructure, and personal mobile devices. Such vehicle communication will enable improvements in safety, mobility, and the environment that current technologies cannot provide. When fully implemented, this technology is expected to reduce collisions between unimpeded vehicles by 80%.

[0051] Referring again to Figure 1, the wireless communication system 100 may include a number of V-UEs 160 that can communicate with a base station 102 via a communication link 120 (for example, using a Uu interface). The V-UEs 160 may also communicate directly with each other via a wireless sidelink 162, with a roadside access point 164 (also called a “roadside unit”) via a wireless sidelink 166, or with an SL-UE 106 via a wireless sidelink 168. A wireless sidelink (or simply a “sidelink”) is a conformance of a core-cellular (e.g., LTE, NR) standard that enables direct communication between two or more UEs without the need for communication to go through a base station. Sidelink communication may be unicast or multicast and may be used for device-to-device (D2D) medium sharing, V2V communication, V2X communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, etc.), emergency rescue applications, etc. One or more of the groups of V-UE160s utilizing sidelink communication may be within the geographical coverage area 110 of base station 102. Other V-UE160s in such groups may be outside the geographical coverage area 110 of base station 102, or otherwise may not be able to receive transmissions from base station 102. In some cases, groups of V-UE160s communicating via sidelink communication may utilize a one-to-many (1:M) system in which each V-UE160 transmits to any other V-UE160 in the group. In some cases, base station 102 facilitates the scheduling of resources for sidelink communication. In other cases, sidelink communication is performed between V-UE160s without the involvement of base station 102.

[0052] In one embodiment, sidelinks 162, 166, 168 may operate on a wireless communication medium, such wireless communication medium may be shared with other vehicles and / or infrastructure access points, as well as with other wireless communications between other RATs. The “medium” may consist of one or more time, frequency, and / or spatial communication resources (e.g., encompassing one or more channels across one or more carriers) relating to wireless communications between one or more transmitter / receiver pairs.

[0053] In one embodiment, side links 162, 166, and 168 may be cV2X links. The first generation of cV2X has been standardized in LTE, and the next generation is expected to be defined in NR. cV2X is a cellular technology that also enables device-to-device communication. In the United States and Europe, cV2X is expected to operate within the licensed ITS band in the sub-6 GHz range. Other countries may allocate different bands. Therefore, as a specific example, the target medium utilized by side links 162, 166, and 168 may correspond to at least a portion of the licensed ITS frequency band in the sub-6 GHz range. However, this disclosure is not limited to this frequency band or cellular technology.

[0054] In one embodiment, sidelinks 162, 166, and 168 may be dedicated short-range communications (DSRC) links. DSRC is a one-way or two-way, short-to-medium-range wireless communication protocol that uses the Wireless Access for Vehicular Environments (WAVE) protocol, also known as IEEE 802.11p, for V2V, V2I, and V2P communications. IEEE 802.11p is an approved amendment to the IEEE 802.11 standard and operates in the United States within the approved ITS band of 5.9 GHz (5.85–5.925 GHz). In Europe, IEEE 802.11p operates within the ITS G5A band (5.875–5.905 MHz). Other countries may be allocated different bands. The V2V communication briefly described above is generally conducted in the United States over the Safety Channel, a 10 MHz channel dedicated to safety purposes. The remainder of the DSRC band (with a total bandwidth of 75 MHz) is directed towards other driver-facing services such as road regulations, toll collection, and automated parking. Therefore, as a specific example, the target medium utilized by sidelinks 162, 166, and 168 may correspond to at least a portion of the 5.9 GHz authorized ITS frequency band.

[0055] Alternatively, the medium in question could correspond to at least a portion of the unlicensed frequency bands shared among various RATs. While different licensed frequency bands are reserved for some communication systems (for example, by government agencies such as the Federal Communications Commission (FCC) in the United States), these systems, particularly those employing small cell access points, have recently extended their operation to unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band, used by Wireless Local Area Network (WLAN) technology, most notably IEEE 802.11x WLAN technology commonly known as "Wi-Fi." Exemplary systems of this type include various variants such as CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, and single-carrier FDMA (SC-FDMA) systems.

[0056] Communication between V-UE160 is called V2V communication, communication between V-UE160 and one or more roadside access points 164 is called V2I communication, and communication between V-UE160 and one or more UE104 (where UE104 is P-UE) is called V2P communication. V2V communication between V-UE160 may include information about the V-UE160's position, speed, acceleration, direction of travel, and other vehicle data. V2I information received by V-UE160 from one or more roadside access points 164 may include, for example, road regulations, parking automation information, etc. V2P communication between V-UE160 and UE104 may include information about the V-UE160's position, speed, acceleration, and direction of travel, as well as the UE104's position, speed (for example, if UE104 is carried by a user on a bicycle), and direction of travel.

[0057] Figure 1 only shows two UEs as V-UEs (V-UE160) and one as an SL-UE (SL-UE106), but please note that any of the other illustrated UEs (e.g., UE104, 152, 182, 190) may also be V-UEs or SL-UEs. In addition, although only V-UE160 and a single SL-UE106 are shown as being connected via sidelinks, any of the UEs shown in Figure 1, regardless of whether they are V-UEs, P-UEs, etc., may be capable of sidelink communication and therefore could be examples of SL-UEs. Furthermore, although it was stated that only UE182 is beamforming capable, any of the illustrated UEs, including V-UE160 and SL-UE106, may be beamforming capable. If V-UE160 and SL-UE106 are capable of beamforming, they may beamform toward each other (i.e., toward the other V-UE160 and SL-UE106), toward roadside access point 164, toward other UEs (e.g., UE104, 106, 152, 182, 190), etc. Thus, in some cases, V-UE160 and SL-UE106 may utilize beamforming on side links 162, 166, and 168.

[0058] In one embodiment, the V-UE160 and SL-UE106 include a sidelink component 108 that enables the V-UE160 and SL-UE106 to perform the sidelink communication operation described herein. Although only the V-UE160 and SL-UE106 are shown to include the sidelink component 108, it should be noted that any of the UEs (and base stations supporting sidelink communication) in Figure 1 may include the sidelink communication 108.

[0059] The wireless communication system 100 may further include one or more UEs, such as UE190, which are indirectly connected to one or more communication networks via one or more D2D peer-to-peer (P2P) links. In the example in Figure 1, UE190 has a D2D P2P link 192 with SL-UE106 connected to one of the base stations 102 (through which UE190 can indirectly obtain cellular connectivity, for example), and a D2D P2P link 194 with WLAN STA152 connected to WLAN AP150 (through which UE190 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®. As another example, D2D P2P links 192 and 194 may be side links as described above with respect to side links 162, 166, and 168.

[0060] Figure 2A shows an exemplary wireless network structure 200. For example, 5GC210 (also called Next Generation Core (NGC)) may function as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.), working together to form the core network. User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect gNB222 to 5GC210, and more specifically to user plane functions 212 and control plane functions 214, respectively. 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 one or more gNB222s, while other configurations may include one or more of both ng-eNB224 and gNB222. Either (or both) of the gNB222 or ng-eNB224 may communicate with one or more UE204s (for example, any of the UEs described herein).

[0061] Another optional aspect may include a location server 230 that may communicate with 5GC210 to provide location assistance to 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), or alternatively, each corresponding to a single server. The location server 230 may be configured to support one or more location services for UE204 that can connect to the location server 230 via the core network 5GC210 and / or via the internet (not shown). Furthermore, the location server 230 may be integrated into the core network components, or alternatively, outside the core network (e.g., a third-party server such as an original equipment manufacturer (OEM) server or service server).

[0062] Figure 2B shows another exemplary wireless network structure 250. 5GC260 (which may correspond to 5GC210 in Figure 2A) can be functionally seen 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 together to form the core network (i.e., 5GC260). The functions of AMF264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UE204 (e.g., any of the UEs described herein) and the Session Management Function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access permission, transport for short message service (SMS) messages between the UE204 and the Short Message Service Function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF264 also interacts with the Authentication Server Function (AUSF) (not shown) and the UE204, and receives the intermediate key established as a result of the UE204 authentication process. In the case of authentication based on the UMTS (Universal Mobile Telecommunications System) Subscriber Identification Module (USIM), the AMF264 retrieves the security material from the AUSSF. The functionality of the AMF264 also includes Security Context Management (SCM). The SCM receives the key from the SEAF that the SCM uses to derive the access network specific key. The functionality of the AMF264 also includes location service management for regulatory services, transport for location service messages between the UE204 and the Location Management Function (LMF) 270 (acting as a location server 230), transport for location service messages between the NG-RAN 220 and the LMF270, EPS bearer identifier allocation for interacting with the Advanced Packet System (EPS), and UE204 mobility event notification.In addition, AMF264 also supports functionality for non-3GPP (Third Generation Partnership Project) ("3GPP" is a registered trademark) access networks.

[0063] The functions of UPF262 include (when applicable) acting as an anchor point for intra-RAT / inter-RAT mobility, acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), routing and forwarding packets, 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) processing for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking on the downlink), uplink traffic verification (mapping service data flows (SDFs) to QoS flows), transport-level packet marking on the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more “end 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.

[0064] 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, control of policy enforcement and QoS portions, and downlink data notification. The interface through which the SMF266 ​​communicates with the AMF264 is called the N11 interface.

[0065] 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 may correspond 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, whereas the LMF270 may communicate with the AMF264, NG-RAN220, and UE204 via the control plane (for example, using interfaces and protocols intended to transmit signaling messages rather than voice or data), while the SLP272 may 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 the Transmission Control Protocol (TCP) and / or IP).

[0066] The user plane interface 263 and the control plane interface 265 connect the 5GC260, specifically the UPF262 and AMF264, to one or more gNB222 and / or ng-eNB224 in the NG-RAN220, respectively. The interface between the gNB222 and / or ng-eNB224 and the AMF264 is called the "N2" interface, and the interface between the gNB222 and / or ng-eNB224 and the UPF262 is called the "N3" interface. The gNB222 and / or ng-eNB224 in the NG-RAN220 can communicate directly with each other via a backhaul connection 223 called the "Xn-C" interface. One or more of the gNB222 and / or ng-eNB224 can communicate with one or more UE204 via a wireless interface called the "Uu" interface.

[0067] The functionality of gNB222 is divided between the gNB Central Unit (gNB-CU) 226 and one or more gNB Distributed Units (gNB-DU) 228. The interface 232 between the gNB-CU 226 and one or more gNB-DU 228 is called the "F1" interface. The gNB-CU 226 is a logical node that includes base station functions such as transferring user data, mobility control, radio access network sharing, positioning, and session management, with the exception of those functions that are exclusively allocated to the gNB-DU 228. More specifically, the gNB-CU 226 hosts the radio resource control (RRC), service data conformance protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB222. The gNB-DU 228 is a logical node that hosts the radio link control (RLC), media access control (MAC), and physical (PHY) layer of the gNB222. Its operation is controlled by the gNB-CU 226. A single gNB-DU228 can support one or more cells, and a single cell can be supported by just one gNB-DU228. Therefore, the UE204 communicates with the gNB-CU226 via the RRC, SDAP, and PDCP layers, as well as with the gNB-DU228 via the RLC, MAC, and PHY layers.

[0068] Figures 3A, 3B, and 3C show several exemplary components (represented by corresponding blocks) that may be incorporated into a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including the location server 230 and LMF 270, or alternatively, a private network, which may be independent of the NG-RAN220 and / or 5GC210 / 260 infrastructure shown in Figures 2A and 2B) to support file transmission operations as taught herein. It will be understood that these components may be implemented in different types of devices in different implementation forms (e.g., in an ASIC, a system-on-a-chip (SoC), etc.). The illustrated components may also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar 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 via different technologies.

[0069] Each UE 302 and base station 304 includes one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, which provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, 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. Each WWAN transceiver 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 a target wireless communication medium (e.g., several sets of time / frequency resources in a particular frequency spectrum). The WWAN transceivers 310 and 350 may be configured in various ways, respectively, to transmit and encode signals 318 and 358 (e.g., messages, displays, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 318 and 358 (e.g., messages, displays, information, pilots, etc.). In detail, 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.

[0070] Each UE 302 and base station 304 also includes, at least in some cases, one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and may provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) 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 Communication (DSRC), Wireless Access for Vehicle Environments (WAVE), Near-Field Communication (NFC), etc.) on the wireless communication medium of interest. The short-range wireless transceivers 320 and 360 may be configured in various ways, respectively, to transmit and encode signals 328 and 368 (e.g., messages, displays, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 328 and 368 (e.g., messages, displays, information, pilots, etc.). In detail, the 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. For example, the 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-everything (V2X) transceivers.

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

[0072] Each base station 304 and network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for transmitting, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, base station 304 may employ one or more network transceivers 380 for communicating with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, network entity 306 may employ one or more network transceivers 390 for communicating with one or more base stations 304 via one or more wired or wireless backhaul links, or with other network entities 306 via one or more wired or wireless core network interfaces.

[0073] The transceiver may be configured to communicate over a wired or wireless link. Whether wired or wireless, the transceiver includes a transmitter circuit configuration (e.g., transmitters 314, 324, 354, 364) and a receiver circuit configuration (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., embodying the transmitter and receiver circuit configurations in a single device), in some implementations it may comprise separate transmitter and receiver circuit configurations, or in other implementations they may be embodied in other ways. The transmitter and receiver circuit configurations of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. A wireless transmitter circuit configuration (e.g., transmitters 314, 324, 354, 364) may include, or be coupled with, multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, enabling each device (e.g., UE 302, base station 304) to perform transmit beamforming. Similarly, a wireless receiver circuit configuration (e.g., receivers 312, 322, 352, 362) may include, or be coupled with, multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, enabling each device (e.g., UE 302, base station 304) to perform receive beamforming. In one embodiment, the transmitter and receiver circuit configurations may share multiple identical antennas (e.g., antennas 316, 326, 356, 366), such that each device can either receive or transmit only at a given time, but not both at the same time. Wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include network listening modules (NLMs) for performing various measurements.

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

[0075] UE302, base station 304, and network entity 306 also include other components that may be used in conjunction with the operations disclosed herein. UE302, base station 304, and network entity 306 each include one or more processors 332, 384, and 394, respectively, for providing, for example, functionality related to wireless communication and for providing other processing functionality. Thus, processors 332, 384, and 394 may provide processing means, such as means for determining, means for calculating, means for receiving, means for transmitting, and means for indicating. In one embodiment, processors 332, 384, and 394 may include, for example, one or more general-purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), other programmable logic devices or processing circuit configurations, or various combinations thereof.

[0076] The UE302, base station 304, and network entity 306 include memory circuit configurations that implement memories 340, 386, and 396, respectively (each including a memory device), for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memories 340, 386, and 396 may provide means for storing, retrieving, holding, etc. In some cases, the UE302, base station 304, and network entity 306 may include sidelink components 342, 388, and 398, respectively. The sidelink components 342, 388, and 398 may be hardware circuits that, when executed, cause the UE302, base station 304, and network entity 306 to perform the functionality described herein. In other embodiments, the sidelink components 342, 388, and 398 may be external to the processors 332, 384, and 394 (for example, they may be part of a modem processing system or integrated with another processing system). Alternatively, the sidelink components 342, 388, and 398 may be memory modules stored in memory 340, 386, and 396, respectively, which, when executed by the 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 the sidelink component 342, which may be part of, for example, one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3B shows possible locations for the sidelink component 388, which may be part of, for example, one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or it may be a standalone component.Figure 3C shows possible locations for the sidelink component 398, which may be part of, for example, one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or it may be a standalone component.

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

[0078] In addition, UE302 includes a user interface 346 that provides means for providing a display to the user (e.g., an audible display and / or a visual display) and / or for receiving user input (e.g., when a user activates a sensing device such as a keypad, touchscreen, or microphone). Although not shown, base stations 304 and network entities 306 may also include user interfaces.

[0079] Referring more specifically to one or more processors 384, in the downlink, IP packets from network entity 306 may be served to processor 384. One or more processors 384 may implement functionality for the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Medium Access Control (MAC) layer. One or more processors 384 may provide RRC layer functionality 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 functionality related to header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality related to the transfer of upper-layer PDUs, error correction through automatic retransmission requests (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and sorting of RLC data PDUs; and MAC layer functionality related to mapping between logical channels and transport channels, scheduling information reporting, error correction, priority processing, and logical channel prioritization.

[0080] The transmitter 354 and receiver 352 may implement Layer 1 (L1) functionality 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 a signal constellation based on various modulation schemes (e.g., 2-phase shift keying (BPSK), 4-phase shift keying (QPSK), M-phase shift keying (M-PSK), M-phase quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then synthesized together using an inverse fast Fourier transform (IFFT) to generate a physical channel that carries a time-domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. Channel estimates may be derived from the reference signal and / or channel condition feedback transmitted by UE302. Each spatial stream may then be supplied to one or more different antennas 356. Transmitter 354 may modulate RF carriers using each spatial stream for transmission.

[0081] In UE302, the receiver 312 receives signals through its respective antenna 316. The receiver 312 reconstructs the information modulated on the RF carrier and provides this information to one or more processors 332. The transmitter 314 and receiver 312 perform Layer 1 functionality related to various signal processing functions. The receiver 312 may perform spatial processing on the information to reconstruct any spatial stream directed to UE302. Multiple spatial streams, if directed to UE302, can be combined by the receiver 312 into a single OFDM symbol stream. The 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 signal constellation point most likely to have been transmitted by the base station 304. These soft decisions may be based on channel estimates calculated by a channel estimator. The soft decision then decodes and deinterleaves the data and control signals initially transmitted by the base station 304 on the physical channel to recover them. The data and control signals are then provided to one or more processors 332 that implement Layer 3 (L3) and Layer 2 (L2) functionality.

[0082] In the uplink, one or more processors 332 demultiplex between the transport channel and the logical channel, reassemble packets, decode them, decompress the headers, and process control signals to reconstruct IP packets from the core network. One or more processing systems 332 are also responsible for error detection.

[0083] Similar to the functionality described for downlink transmission by base station 304, one or more processors 332 provide RRC layer functionality related to system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality related to header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality 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 sorting of RLC data PDUs; and MAC layer functionality 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 processing, and logical channel prioritization.

[0084] The channel estimate derived by the channel estimator from a reference signal or feedback transmitted by base station 304 may be used by transmitter 314 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by transmitter 314 may be supplied to different antennas 316. Transmitter 314 may modulate the RF carrier using each spatial stream for transmission.

[0085] Uplink transmissions are processed at base station 304 in a manner similar to that described for receiver functions in UE302. Receiver 352 receives the signal through its respective antenna 356. Receiver 352 reconstructs the information modulated on the RF carrier and provides this information to one or more processors 384.

[0086] In the uplink, one or more processors 384 demultiplex between the transport channel and the logical channel, reassemble packets, decode, decompress headers, and process control signals to reconstruct IP packets from the UE302. IP packets from one or more processors 384 can then be supplied to the core network. One or more processors 384 are also responsible for error detection.

[0087] For convenience, the UE302, base station 304, and / or network entity 306 are shown in Figures 3A, 3B, and 3C as including various components that may be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionalities in different designs. In detail, the various components in Figures 3A to 3C include configurations that are optional in alternative configurations, and the various embodiments may vary due to design choices, cost, device usage, or other considerations. For example, in the example of Figure 3A, a particular implementation of the UE302 may omit the WWAN transceiver 310 (e.g., a wearable device or tablet computer or PC or laptop may have Wi-Fi and / or Bluetooth capabilities without cellular capabilities), or the short-range wireless transceiver 320 (e.g., cellular only), or the satellite signal receiver 330, or the sensor 344, and so on. In another example, in the case of Figure 3B, a particular implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or the short-range wireless transceiver 360 (e.g., cellular only), or the satellite receiver 370, and so on. For the sake of brevity, examples of various alternative configurations are not provided herein, but should be readily apparent to those skilled in the art.

[0088] Various components of UE302, base station 304, and network entity 306 can be coupled to each other in a communicative manner via data buses 334, 382, ​​and 392, respectively. In one embodiment, data buses 334, 382, ​​and 392 can form or be part of a communication interface for UE302, base station 304, and network entity 306, respectively. For example, if various logical entities are embodied within the same device (e.g., gNB and location server functionality integrated within the same base station 304), data buses 334, 382, ​​and 392 can provide communication between them.

[0089] The components of Figures 3A, 3B, and 3C can be implemented in various ways. In some implementations, the components of Figures 3A, 3B, and 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-346 may be implemented by the processor and 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-388 may be implemented by the processor and 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 functionality represented by blocks 390-398 may be performed by the processor and memory components of network entity 306 (for example, by the execution of appropriate code and / or by the appropriate configuration of 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 will be understood, such operations, actions, and / or functions may actually be performed by specific components or combinations of components such as UE 302, base station 304, network entity 306, etc., including processors 332, 384, 394, transceivers 310, 320, 350, and 360, memories 340, 386, and 396, sidelink components 342, 388, and 398.

[0090] 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 5GC210 / 260). For example, network entity 306 may be a component of a private network that communicates with UE302 via base station 304, or it may be configured independently of base station 304 (e.g., via a non-cellular communication link such as WiFi).

[0091] Figure 4 shows an example of a wireless communication system 400 that supports the establishment of a wireless unicast sidelink according to an aspect of the present disclosure. In some examples, the wireless communication system 400 may implement aspects of wireless communication systems 100, 200, and 250. The wireless communication system 400 may include a first UE402 and a second UE404, which may be any example of the UEs described herein. Specifically, UE402 and 404 may correspond to V-UE160 in Figure 1, UE190 and UE104 in Figure 1 connected via D2D P2P link 192, or UE204 in Figures 2A and 2B.

[0092] In the example in Figure 4, UE402 may attempt to establish a unicast connection with UE404 via a sidelink, which may be a V2X sidelink between UE402 and UE404. Specifically, the sidelink connection to be established may correspond to sidelinks 162 and / or 168 in Figure 1. The sidelink connection may be established within an omnidirectional frequency range (e.g., FR1) and / or a mmW frequency range (e.g., FR2). In some cases, UE402 may be called the initiating UE that starts the sidelink connection procedure, and UE404 may be called the target UE that is targeted for the sidelink connection procedure by the initiating UE.

[0093] To establish a unicast connection, access layer (AS) parameters (a functional layer within the UMTS and LTE protocol stacks, and part of Layer 2, between the RAN and the UE responsible for transporting data over the wireless link and managing radio resources) may be configured and negotiated between UE402 and UE404. For example, transmit and receive capability matching may be negotiated between UE402 and UE404. Each UE may have different capabilities (e.g., transmit and receive, 64 quadrature amplitude modulation (QAM), transmit diversity, carrier aggregation (CA), supported communication frequency bands, etc.). In some cases, different services may be supported in the upper layers of the corresponding protocol stacks for UE402 and UE404. Additionally, a security association may be established between UE402 and UE404 for the unicast connection. Unicast traffic may benefit from link-level security protections (e.g., integrity protection). Security requirements may differ for different wireless communication systems. For example, V2X and Uu systems may have different security requirements (e.g., Uu security does not include confidentiality protection). Additionally, IP configuration (e.g., IP version, address, etc.) may be negotiated for the unicast connection between UE402 and UE404.

[0094] In some cases, UE404 may create a service announcement (e.g., a service capability message) for transmission over a cellular network (e.g., cV2X) to assist in establishing a sidelink connection. Traditionally, UE402 may identify and locate candidates for sidelink communication based on a broadcasted basic service message (BSM) that is decrypted by a nearby UE (e.g., UE404). The BSM may include location, security, and identification information for the corresponding UE, as well as vehicle information (e.g., speed, operation, size, etc.). However, in the case of different wireless communication systems (e.g., D2D or V2X communication), the discovery channel may not be configured to allow UE402 to discover the BSM. Therefore, service announcements (e.g., discovery signals) transmitted by UE404 and other nearby UEs may be higher-layer signals and may be broadcast (e.g., within an NR sidelink broadcast). In some cases, UE404 may include one or more parameters for itself in the service announcement, including connection parameters and / or capabilities it possesses. UE402 may then monitor for and receive broadcasted service announcements to identify possible UEs for the corresponding sidelink connection. In some cases, UE402 may identify possible UEs based on the capabilities each UE demonstrates in their respective service announcements.

[0095] A service announcement may include information to help UE402 (for example, or any initiating UE) identify the UE sending the service announcement (UE404 in the example in Figure 4). For example, a service announcement may include channel information from which direct communication requests may be sent. In some cases, the channel information may be RAT-specific (for example, specific to LTE or NR) and may include the resource pool from which UE402 sends communication requests. Additionally, a service announcement may include a specific destination address for the UE (for example, a Layer 2 destination address) if the destination address is different from the current address (for example, the address of the streaming provider or the UE sending the service announcement). A service announcement may also include a network layer or transport layer from which UE402 sends communication requests. For example, the network layer (also called "Layer 3" or "L3") or transport layer (also called "Layer 4" or "L4") may indicate the application's port number to the UE sending the service announcement. In some cases, if the signaling (e.g., PC5 signaling) directly carries a protocol (e.g., Real-Time Transport Protocol (RTP)) or provides a locally generated random protocol, IP addressing may not be required. Additionally, the service announcement may include the type of protocol for proof establishment and QoS-related parameters.

[0096] After identifying a possible sidelink connection target (UE404 in the example in Figure 4), the initiating UE (UE402 in the example in Figure 4) may send a connection request 415 to the identified target UE404. In some cases, the connection request 415 may be a first RRC message (e.g., an "RRCSetupRequest" message) sent by UE402 to request a unicast connection with UE404. For example, the unicast connection may utilize the PC5 interface for sidelink, and the connection request 415 may be an RRC connection setup request message. Additionally, UE402 may use a sidelink signaling radio bearer 405 to transport the connection request 415.

[0097] After receiving connection request 415, UE404 may decide whether to accept or reject the connection request 415. UE404 may base this decision on transmit / receive capabilities, the ability to accommodate a unicast connection over a sidelink, specific services indicated for the unicast connection, content to be transmitted over the unicast connection, or a combination thereof. For example, if UE402 wishes to use a first RAT to transmit or receive data, but UE404 does not support the first RAT, UE404 may reject connection request 415. Additionally or alternatively, UE404 may reject connection request 415 on the grounds that it cannot accommodate a unicast connection over a sidelink due to limited radio resources, scheduling issues, etc. Accordingly, UE404 may send an indication in connection response 420 indicating whether the request is accepted or rejected. Similar to UE402 and connection request 415, UE404 may use the sidelink signaling radio bearer 410 to transport the connection response 420. Additionally, the connection response 420 may be a second RRC message sent by UE404 in response to connection request 415 (for example, the "RRCResponse" message).

[0098] In some cases, sidelink signaling radio bearers 405 and 410 may be the same sidelink signaling radio bearer or may be separate sidelink signaling radio bearers. Therefore, the radio link control (RLC) layer acknowledged response mode (AM) may be used for sidelink signaling radio bearers 405 and 410. UEs supporting unicast connections may listen on the logical channels associated with the sidelink signaling radio bearers. In some cases, the AS layer (i.e., Layer 2) may pass information directly through RRC signaling (e.g., the control plane) rather than the V2X layer (e.g., the data plane).

[0099] If the connection response 420 indicates that UE404 has accepted the connection request 415, UE402 may then send a connection establishment 425 message on the sidelink signaling radio bearer 405 to indicate that the unicast connection setup is complete. In some cases, the connection establishment 425 may be a third RRC message (e.g., an "RRCSetupComplete" message). Each of the connection request 415, connection response 420, and connection establishment 425 may use basic capability when they are being transported from one UE to the other, enabling each UE to receive and decode the corresponding transmission (e.g., an RRC message).

[0100] Additionally, identifiers may be used for each of the connection request 415, connection response 420, and connection establishment 425. For example, the identifier may indicate which UE402 / 404 is sending which message and / or which UE402 / 404 the message is intended for. For physical (PHY) layer channels, the RRC signaling and any subsequent data transmissions may use the same identifier (e.g., Layer 2 ID). However, for logical channels, the identifiers may be different for the RRC signaling and for the data transmissions. For example, on a logical channel, the RRC signaling and data transmissions may be treated differently and may have different acknowledgment (ACK) feedback messaging. In some cases, physical layer ACKs may be used for RRC messaging to ensure that the corresponding messages are correctly sent and received.

[0101] To enable the negotiation of corresponding AS layer parameters for a unicast connection, one or more informational elements may be included in the connection request 415 and / or connection response 420 to UE402 and / or UE404, respectively. For example, UE402 and / or UE404 may include Packet Data Convergence Protocol (PDCP) parameters in the corresponding unicast connection setup message to set up the PDCP context for the unicast connection. In some cases, the PDCP context may indicate whether PDCP replication is used for the unicast connection. In addition, UE402 and / or UE404 may include RLC parameters when establishing a unicast connection to set up the RLC context for the unicast connection. For example, the RLC context may indicate whether AM (e.g., sort timer (t-sort) is used) or unacknowledged mode (UM) is used for the RLC layer of the unicast communication.

[0102] Additionally, UE402 and / or UE404 may include media access control (MAC) parameters to set up a MAC context for unicast connections. In some cases, the MAC context may enable resource selection algorithms, hybrid automatic retransmission request (HARQ) feedback schemes (e.g., ACK or negative ACK (NACK) feedback), parameters for HARQ feedback schemes, carrier aggregation, or combinations thereof for unicast connections. Additionally, UE402 and / or UE404 may include PHY layer parameters when establishing a unicast connection to set up a PHY layer context for the unicast connection. For example, the PHY layer context may indicate the transmit format (unless a transmit profile is included for each UE402 / 404) and radio resource configuration (e.g., bandwidth portion (BWP), numerology, etc.) for the unicast connection. These informational elements may be supported for different frequency range configurations (e.g., FR1 and FR2).

[0103] In some cases, a security context may also be established for the unicast connection (for example, after the connection establishment 425 message is sent). Before a security association (e.g., security context) is established between UE402 and UE404, the sidelink signaling radio bearers 405 and 410 may not be protected. After the security association is established, the sidelink signaling radio bearers 405 and 410 may be protected. Thus, the security context can enable secure data transmission over the unicast connection and the sidelink signaling radio bearers 405 and 410. In addition, IP layer parameters (e.g., link-local IPv4 or IPv6 addresses) may also be negotiated. In some cases, the IP layer parameters may be negotiated by a higher-layer control protocol that operates after RRC signaling is established (e.g., the unicast connection is established). As described above, UE404 may base its decision on whether to accept or reject connection request 415 for a specific service indicated for a unicast connection, and / or on the content to be transmitted over the unicast connection (e.g., higher-layer information). The specific service and / or content may also be indicated by a higher-layer control protocol that operates after RRC signaling has been established.

[0104] After the unicast connection is established, UE402 and UE404 may communicate using the unicast connection via sidelink 430, where sidelink data 435 is transmitted between the two UE402 and UE404. Sidelink 430 may correspond to sidelinks 162 and / or 168 in Figure 1. In some cases, the sidelink data 435 may include RRC messages transmitted between the two UE402 and UE404. To maintain this unicast connection over sidelink 430, UE402 and / or UE404 may send keep-alive messages (e.g., "RRCDirectLinkAlive" messages, fourth RRC messages, etc.). In some cases, keep-alive messages may be triggered periodically or on demand (e.g., event-triggered). Thus, triggering and sending keep-alive messages may be invoked by UE402 or by both UE402 and UE404. As an addition or alternative, MAC control elements (CEs) (for example, defined via sidelink 430) may be used to monitor the status of the unicast connection on sidelink 430 and maintain the connection. When the unicast connection is no longer needed (for example, when UE402 has moved far enough away from UE404), either UE402 and / or UE404 may initiate a release procedure to remove the unicast connection via sidelink 430. Thus, no subsequent RRC messages need to be sent between UE402 and UE404 over the unicast connection.

[0105] NR can support various sidelink ranging and positioning techniques. Sidelink-based ranging allows for the determination of the relative distance between a UE and its arbitrary absolute position, given that the absolute position of at least one associated UE is known. This technique is useful in situations where Global Navigation Satellite System (GNSS) positioning is degraded or unavailable (e.g., tunnels, urban valleys), and also improves the accuracy of distance and positioning when GNSS is available.

[0106] Sidelink-based ranging can be achieved via the broadcasting of positioning reference signals (PRS) from participating UEs (e.g., any UE capable of sidelink, V2X, V2V, etc.) and network entities (e.g., RSU, gNB, AP, etc.), followed by the exchange of measurement results based on the transmission and reception of PRS. Based on these measurement results, participants (UEs or network entities) can determine their distance to other participants. If at least one participant has precise knowledge of their location, the result of the ranging operation is a determination of the location of the other participants. If none of the participants have knowledge of their locations, the result is simply a determination of the distance between participants.

[0107] When a UE determines its location from a sidelink positioning procedure (also known as a sidelink ranging procedure, sidelink ranging session, sidelink ranging and positioning procedure, etc.), at least one participant in that procedure must have precise knowledge of that location in order to serve as an "anchor" for the location calculation (i.e., the "anchor" is a device with a known location that can be used to determine the location of a device with an unknown location). Similarly, when a network entity manages a sidelink positioning procedure (e.g., LME, RSU, gNB), a prerequisite for determining participants in the sidelink positioning procedure is knowing which UEs, if any, can serve as anchors. Therefore, having a mechanism for a UE to notify the network and / or other UEs whether it can serve as an anchor enables better sidelink positioning and reduces radio messaging / resource utilization by not initiating the procedure when a suitable anchor is not available.

[0108] Accordingly, this disclosure provides a signaling mechanism for a UE to notify the network (and / or other UEs) of its ability to serve as an anchor for a sidelink positioning procedure. A UE may determine whether it can serve as an anchor for a sidelink positioning procedure based on a variety of factors, including whether the UE has a known location, the accuracy of that location (for example, even if the UE has a known location, if the accuracy of that location falls below a threshold, the UE cannot serve as an anchor), the signal strength of messages received from other participating UEs (for example, weak signal strength may indicate that the UE is too far from other UEs to provide reliable anchoring services), the UE's battery level, and privacy settings (for example, if the UE provides anchoring services, it must share its location). The information transmitted may include the UE's ability to serve as an anchor, its location, the accuracy of its location, and its ability to perform sidelink positioning calculations based on receiving measurement results from other UEs. The information elements used to constitute these parameters may be incorporated into existing 3GPP signaling messages or as part of new messages specific to sidelink positioning.

[0109] Figure 5 shows an exemplary sidelink ranging and positioning procedure 500 according to an aspect of this disclosure. Sidelink ranging is determined from the transmit and receive times of PRS (a broadband reference signal defined in LTE and NR for positioning), and is based on calculating round-trip time (RTT) measurements between UEs. Each UE reports its RTT measurement results, along with its location (if known), to all other participating UEs. If UEs have no knowledge of or inaccurate knowledge of their locations, the RTT procedure yields an inter-UE distance between the relevant UEs. If UEs have accurate knowledge of their locations, the distance yields an absolute location. UE participation, PRS transmission, and subsequent RTT calculation are integrated by an initial three-way messaging handshake (PRS request, PRS response, and PRS acknowledgment) and a post-PRS message exchange to share measurement results after receiving the peer UE's PRS (post-PRS message).

[0110] Sidelink ranging and positioning procedure 500 (or session) begins in stage 505 with a broadcast of capability information by the relevant peer UE. As shown in Figure 5, one of the peer UEs, UE204-1 (for example, any of the sidelink-enabled UEs described herein), can be the anchor UE for sidelink ranging and positioning procedure 500, meaning it has a known location. Therefore, anchor UE204-1 includes in its capability message an indication that it can be the anchor for sidelink ranging and positioning procedure 500. The capability message may also include the location of anchor UE204-1, or this may be provided later. The other UE, UE204-2 (for example, any other UE among the sidelink-enabled UEs described herein), is the target UE, meaning it has an unknown or inaccurate location and is about to be located. Based on the fact that capability information indicating that anchor UE204-1 is an anchor UE is received from anchor UE204-1, target UE204-2 knows that it can determine its location by performing sidelink ranging and positioning procedure 500 using anchor UE204-1.

[0111] After the initial capability exchange, the relevant UE204s perform a three-way messaging handshake. In stage 510, anchor UE204-1 sends a PRS request (labeled "PRSrequest") to target UE204-2. In stage 515, target UE204-2 sends a PRS response (labeled "PRSresponse") to UE204-1. In stage 520, anchor UE204-1 sends a PRS acknowledgment to target UE204-2. At this point, the three-way messaging handshake is complete.

[0112] In stages 525 and 530, the related peer UE204s transmit PRSs to each other. The resources on which the PRSs are transmitted may be configured / allocated by the network (e.g., one of the UE204's serving base stations) or negotiated by the UE204s during the three-way messaging handshake. Anchor UE204-1 measures the transmit-receive (Tx-Rx) time difference between the transmit time of the PRS in stage 525 and the receive time of the PRS in stage 530. Target UE204-2 measures the receive-transmit (Tx-Rx) time difference between the receive time of the PRS in stage 525 and the transmit time of the PRS in stage 530.

[0113] In stages 535 and 540, peer UE204s exchange their respective time-difference measurement results in a post-PRS message (labeled "postPRS"). If anchor UE204-1 has not yet provided its location to target UE204-2, anchor UE204-1 does so at this point. Each UE204 can then determine the RTT between them based on the Tx-Rx and Rx-Tx time-difference measurement results (in particular, the difference between the Tx-Rx time-difference measurement result and the Rx-Tx time-difference measurement result). Based on the RTT measurement result and the speed of light, each UE204 can then estimate the distance (or range) between the two UE204s (in particular, half the value obtained by multiplying the RTT measurement result by the speed of light). Since target UE204-2 also has the absolute location (e.g., geographic coordinates) of anchor UE204-1, target UE204-2 can use its location and the distance to anchor UE204-1 to determine its own absolute location.

[0114] Figure 5 shows two UE204s, but note that a UE may use multiple UEs to perform, or attempt to perform, the sidelink ranging and positioning procedure 500.

[0115] A network (e.g., gNB, RSU, LMF) can manage sidelink positioning procedures by assigning anchor UEs (or multiple UEs) to the procedure based on capability exchange with participating UEs. Two types of network-managed sidelink ranging and positioning procedures exist, as shown in Figures 6 and 7. In Figure 6, the network selects the anchor UE, and the target UEs determine their own location based on the location of the anchor UE. In Figure 7, the network selects the anchor UE, the relevant UEs report their measurement results to the network, and the network determines the location of the target UE.

[0116] Figure 6 shows an example of a network-managed sidelink ranging and positioning procedure 600 according to an aspect of this disclosure. The network-managed sidelink ranging and positioning procedure 600 (or session) begins in step 610 with the exchange of capability information between the relevant peer UE 204 and gNB 222. As shown in Figure 6, one of the peer UEs, Anchor UE 204-1 (for example, any of the sidelink-enabled UEs described herein), includes in its capability message an indication that it can be the Anchor UE. The other UEs, UE 204-2 to UE 204-N (for example, any other UE of the sidelink-enabled UEs described herein), are target UEs.

[0117] Based on the capabilities received in stage 610, gNB222 determines that anchor UE204-1 can act as an anchor for the network-managed sidelink ranging and positioning procedure 600. gNB222 assigns anchor UE204-1 and UE204-2 to UE204-N to a sidelink positioning group and sends a PRS request (labeled "PRSrequest") to each of the relevant UE204s in stage 620. The PRS request may indicate the sidelink positioning group to which the peer UE204 has been assigned and the time and frequency resources on which the UE204 will transmit a PRS.

[0118] In step 630, peer UE204 sends PRS responses (labeled "PRSresponse1", "PRSresponse2", and "PRSresponseN") to each other, and in step 640, peer UE204 sends PRS to each other. In step 640, UE204 measures the Tx-Rx and Rx-Tx time differences of the transmitted and received PRS. For example, each UE204 may perform steps 525 and 530 with each other to determine the Tx-Rx and Rx-Tx time differences.

[0119] In stage 650, the UE204s report their respective time difference measurement results and / or their RTTs to each other in post-PRS messages (labeled "PostPRS1", "PostPRS2", and "PostPRSN"), as shown in stages 535 and 540 of Figure 5. If anchor UE204-1 has not yet provided its location to target UE204-2~204-N, anchor UE204-1 does so at this point. The peer UE204s can now determine the RTT and / or the distance between them. Based on the distance between the known locations of target UE204-2~UE204-N and anchor UE204-1, each target UE204-2~UE204-N can determine its location.

[0120] Figure 7 shows another example of a network-managed sidelink ranging and positioning procedure 700 according to an aspect of this disclosure. The network-managed sidelink ranging and positioning procedure 700 (or session) begins in step 710 with the exchange of capability information between the relevant peer UE 204 and gNB 222. As shown in Figure 7, one of the peer UEs, Anchor UE 204-1 (for example, any of the sidelink-enabled UEs described herein) includes in its capability message an indication that it can be the Anchor UE. The other UEs, UE 204-2 to UE 204-N (for example, any other UE of the sidelink-enabled UEs described herein) are target UEs.

[0121] Based on the capabilities received in stage 710, gNB222 determines that anchor UE204-1 can act as an anchor for the network-managed sidelink ranging and positioning procedure 700. gNB222 assigns anchor UE204-1 and target UE204-2 to UE204-N to a sidelink positioning group and sends a PRS request ("PRSrequest") to each of the relevant UE204s in stage 720. The PRS request may indicate the sidelink positioning group to which the peer UE204 has been assigned and the time and frequency resources on which the UE204 will transmit a PRS.

[0122] In step 730, each peer UE204 sends PRS responses (labeled "PRSresponse1", "PRSresponse2", and "PRSresponseN") to the gNB222. In step 740, the peer UE204s send PRSs to each other. In step 740, the UE204s measure the Tx-Rx and Rx-Tx time differences of the transmitted and received PRSs. For example, each UE204 may perform steps 525 and 530 with each other to determine the Tx-Rx and Rx-Tx time differences.

[0123] At stage 750, the UE204s report their respective time difference measurements, their RTTs, and / or relative distances between them to the gNB222 in post-PRS messages (labeled "PostPRS1", "PostPRS2", and "PostPRSN"). If anchor UE204-1 has not yet provided its location to the gNB222, it does so at this point. The gNB222 or LMF270 can now determine the RTT or distance between the UE204s if it has not been provided by the UE204s. Based on the distance between the known locations of the UE204s and anchor UE204-1, the gNB222 or LMF270 can determine the locations of target UE204-2 to UE204-N.

[0124] A UE may signal its ability to serve as an anchor UE for a sidelink positioning procedure using various information elements (for example, as in steps 505, 610, and 710 in Figures 5, 6, and 7). Figure 8 shows an exemplary positioning anchor capability information element 800 according to an aspect of this disclosure. In the example in Figure 8, the positioning anchor capability information element 800 is named "sl-PositionAnchorCapability," but as understood, this is merely an example. The positioning anchor capability information element 800 may be an RRC information element exchanged between a UE and a base station or between two UEs. The positioning anchor capability information element 800 may include the following fields:

[0125] [Table 1]

[0126] Figures 9A and 9B illustrate exemplary information elements that may be exchanged between two UEs to request and provide the anchor capability status of a UE, according to aspects of this disclosure. As shown in Figure 9A, the first UE (labeled "UE1") and the second UE (labeled "UE2") perform capability exchange procedure 900, which may be the capability exchange procedure performed in step 505 of Figure 5.

[0127] In the first stage of capability exchange procedure 900, the first UE receives a capability inquiry message 910 (for example, a "UECapabilityEnquirySidelink" message) from the second UE. The capability inquiry message 910 includes a "UECapabilityEnquirySidelink" information element which contains at least one "UECapabilityEnquirySidelink-IEs-r16" information element. The "UECapabilityEnquirySidelink-IEs-r16" information element includes an "sl-PositionAnchorCapabilityStatus" field which points to an "sl-PositionAnchorCapability" information element (for example, a positioning anchor capability information element 800). The "sl-PositionAnchorCapability" information element requests an indication 912 of whether the UE is capable of being an anchor for the sidelink positioning procedure.

[0128] In the second stage of capability exchange procedure 900, the first UE responds to the capability inquiry message with a capability information message 930 (for example, the "UECapabilityInformationSidelink" message). The capability information message 930 includes a "UECapabilityInformationSidelink" information element which contains at least one "UECapabilityInformationSidelink-IEs-r16" information element. The "UECapabilityInformationSidelink-IEs-r16" information element includes an "sl-PositionAnchorCapabilityStatus" field which points to an "sl-PositionAnchorCapability" information element (for example, the positioning anchor capability information element 800). The "sl-PositionAnchorCapability" information element indicates whether the UE can be an anchor for the sidelink positioning procedure (this is an indication of possibility 932).

[0129] Figures 9A and 9B show that the "sl-PositionAnchorCapabilityStatus" field and the "sl-PositionAnchorCapability" information element are added to an existing RRC message. However, it should be noted that, as you may understand, these fields and information elements may instead be provided within a new RRC message.

[0130] Figures 10A and 10B illustrate exemplary information elements that may be exchanged between a UE and a network entity to request and provide the anchor capability status of the UE, according to aspects of this disclosure. As shown in Figure 10A, the UE and the network entity (labeled "NW") perform capability exchange procedure 1000, which may be the capability exchange procedure performed in steps 610 and 710 of Figures 6 and 7.

[0131] In the first stage of capability exchange procedure 1000, the UE receives capability inquiry messages 1010 (e.g., "UECapabilityEnquiry" messages) from network entities (e.g., base stations, location servers). The capability inquiry message 1010 may contain various "UECapabilityEnquiry" information elements. The "UECapabilityEnquiry-v1610-IEs" information element contains a "sl-PositionAnchorCapabilityStatus" field that points to the "sl-PositionAnchorCapability" information element (e.g., positioning anchor capability information element 800). The "sl-PositionAnchorCapability" information element requests an indication 1012 of whether the UE is capable of being an anchor for a sidelink positioning procedure.

[0132] In the second stage of capability exchange procedure 1000, the UE responds to the capability inquiry message with a capability information message 1030 (for example, a "UECapabilityInformation" message). The capability information message 1030 includes a "UECapabilityInformation" information element which may include at least one "UECapabilityInformation-IEs-r16" information element. The "UECapabilityInformation-IEs-r16" information element may include an "sl-PositionAnchorCapabilityStatus" field which points to an "sl-PositionAnchorCapability" information element (for example, a positioning anchor capability information element 800). The "sl-PositionAnchorCapability" information element indicates whether the UE is capable of being an anchor for a sidelink positioning procedure (this is an indication 1032).

[0133] Figures 10A and 10B show that the "sl-PositionAnchorCapabilityStatus" field and the "sl-PositionAnchorCapability" information element are added to the existing "UECapabilityEnquiry" and "UECapabilityInformation" RRC messages. However, it should be noted that these fields and information elements may instead be added to the existing "UEInformationRequest" and "UEInformationReponse" RRC messages. Alternatively, these fields and information elements may be provided in a new RRC message instead.

[0134] Figure 11 shows an exemplary method 1100 of wireless communication according to an aspect of the present disclosure. In one aspect, method 1100 may be performed by a first UE (for example, any of the UEs described herein).

[0135] In 1110, the first UE receives a capability inquiry message for the sidelink positioning procedure (e.g., a “UECapabilityEnquirySidelink” or “UECapabilityEnquiry” message) from a network node (e.g., a base station, location server, anchor UE), the capability inquiry message includes at least a request for indication of whether the first UE has the capability to provide the location of the first UE (i.e., serving as an anchor) for the sidelink positioning procedure (e.g., via the “sl-PositionAnchorCapability” information element). In one embodiment, operation 1110 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or sidelink components 342, any or all of which may be considered means for performing this operation.

[0136] In 1120, the first UE sends a capability information message (e.g., a “UECapabilityInformationSidelink” or “UECapabilityInformation” message) to a network node indicating one or more capabilities of the first UE to participate in the sidelink positioning procedure, the one or more capabilities of the first UE including at least an indication of whether the first UE has the ability to provide the location of the first UE to the sidelink positioning procedure (e.g., via the “sl-PositionAnchorCapability” information element). In one embodiment, operation 1120 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or sidelink components 342, any or all of which may be considered means for performing this operation.

[0137] Figure 12 shows an exemplary method 1200 of wireless communication according to an aspect of the present disclosure. In one aspect, method 1200 may be performed by a network node (for example, one of the base stations, UEs, or location servers described herein).

[0138] In 1210, the network node sends a capability inquiry message for the sidelink positioning procedure (e.g., a “UECapabilityEnquirySidelink” or “UECapabilityEnquiry” message) to a first UE (e.g., any of the UEs described herein), the capability inquiry message includes a request for indication of whether the first UE has the capability to provide the location of the first UE for the sidelink positioning procedure (e.g., via the “sl-PositionAnchorCapability” information element). In one embodiment, if the network node is a UE (e.g., a target UE), operation 1210 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or sidelink components 342, any or all of which may be considered means for performing this operation. In one embodiment, if the network node is a base station, operation 1210 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or sidelink components 388, any or all of which may be considered means for performing this operation. In one embodiment, if the network node is a location server, operation 1210 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or sidelink components 398, any or all of which may be considered means for performing this operation.

[0139] In 1220, the network node receives capability information messages from the first UE (e.g., "UECapabilityInformationSidelink" or "UECapabilityInformation" messages) indicating one or more capabilities of the first UE to participate in the sidelink positioning procedure, and one or more capabilities of the first UE include at least an indication of whether the first UE has the ability to provide the location of the first UE for the sidelink positioning procedure (e.g., via the "sl-PositionAnchorCapability" information element). In one embodiment, if the network node is a UE (e.g., a target UE), operation 1220 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or sidelink components 342, any or all of which may be considered means for performing this operation. In one embodiment, if the network node is a base station, operation 1220 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or sidelink components 388, any or all of which may be considered means for performing this operation. In one embodiment, if the network node is a location server, operation 1220 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or sidelink components 398, any or all of which may be considered means for performing this operation.

[0140] As should be understood, methods 1100 and 1200 enable the first UE to provide the ability to act as an anchor for a sidelink positioning procedure, and enable a network node (base station, location server, or another UE) to receive it. This enables better sidelink positioning and reduces radio messaging / resource utilization by not initiating the procedure when a suitable anchor is not available.

[0141] Figure 13 shows an exemplary user device 1300 according to an aspect of the present disclosure. The user device 1300 may include a memory 1310, a communication device 1320, and at least one processor 1330. The memory 1310, the communication device 1320, and at least one processor 1330 may be coupled to each other on a data bus 1340. In one aspect, the memory 1310 may correspond to a memory 340 and / or a sidelink component 342, the communication device 1320 may correspond to one or more WWAN transceivers 310 and / or sidelink components 342, and at least one processor 1330 may correspond to one or more processors 332 and / or sidelink components 342.

[0142] In one embodiment, the memory 1310 and at least one processor 1330 may be configured to receive capability inquiry messages from a network node for a sidelink positioning procedure, the capability inquiry message comprising at least a request for indication of whether user equipment 1300 is capable of providing the location of a first UE for a sidelink positioning procedure, and to transmit capability information messages to the network node indicating one or more capabilities of user equipment 1300 to participate in a sidelink positioning procedure, the one or more capabilities of user equipment 1300 comprising at least an indication of whether user equipment 1300 is capable of providing the location of a first UE for a sidelink positioning procedure.

[0143] Figure 14 shows an exemplary network node 1400 according to an aspect of the present disclosure. The network node 1400 may include a memory 1410, a communication device 1420, and at least one processor 1430. The memory 1410, the communication device 1420, and at least one processor 1430 may be coupled to each other on a data bus 1440. In one embodiment, depending on whether the network node 1400 is a UE, a base station, or a location server, the memory 1410 may correspond to memories 340, 386, or 396 and / or sidelink components 342, 388, or 398; the communication device 1420 may correspond to one or more transceivers 310, 350, or 390 and / or sidelink components 342, 388, or 398; and at least one processor 1430 may correspond to one or more processors 332, 384, or 394 and / or sidelink components 342, 388, or 398.

[0144] In one embodiment, the memory 1410 and at least one processor 1430 may be configured to send a capability inquiry message to a first UE for a sidelink positioning procedure, the capability inquiry message comprising at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure, and to receive a capability information message from the first UE indicating one or more capabilities of the first UE to participate in a sidelink positioning procedure, the one or more capabilities of the first UE comprising at least an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure.

[0145] Figure 15 shows an exemplary user device 1500 represented as a series of interrelated functional modules. The user device 1500 may include a receiving module 1510 and a transmitting module 1520. In one embodiment, the receiving module 1510 may correspond to one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or sidelink components 342, and the transmitting module 1520 may correspond to one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or sidelink components 342.

[0146] Figure 16 shows an exemplary network node 1600, represented as a series of interrelated functional modules. The network node 1600 may include a module 1610 for transmitting and a module 1620 for receiving. In one embodiment, depending on whether the network node 1600 is a UE, a base station, or a location server, the transmitting module 1610 may correspond to one or more transceivers 310, 350, or 390, one or more processors 332, 384, or 394, memory 340, 386, or 396 and / or sidelink components 342, 388, or 398, and the receiving module 1620 may correspond to one or more transceivers 310, 350, or 390, one or more processors 332, 384, or 394, memory 340, 386, or 396 and / or sidelink components 342, 388, or 398.

[0147] The functions of the modules in Figures 15 and 16 can be implemented in various ways that are not inconsistent with the teachings herein. In some designs, the functions of these modules can be implemented as one or more electrical components. In some designs, the functions of these blocks can be implemented as a processing system including one or more processor components. In some designs, the functions of these modules can be implemented, for example, using at least a portion of one or more integrated circuits (e.g., ASICs). As described herein, an integrated circuit may include a processor, software, other related components, or any combination thereof. Thus, the functions of different modules can be implemented, for example, as different subsets of integrated circuits, as different subsets of a set of software modules, or a combination thereof. It will also be understood that a given subset (e.g., of integrated circuits and / or a set of software modules) can provide at least a portion of the functions for two or more modules.

[0148] Furthermore, the components and functions represented by Figures 15 and 16, as well as other components and functions described herein, can be implemented using any suitable means. Such means may also be implemented, at least in part, using the corresponding structures taught herein. For example, the components described above, along with the “module for” components in Figures 15 and 16, may also correspond to similarly designated “means for” functions. Thus, in some embodiments, one or more of such means may be implemented using one or more processor components, integrated circuits, or other suitable structures as taught herein.

[0149] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips, which may be referenced 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.

[0150] Furthermore, those skilled in the art will understand that various exemplary logic blocks, modules, circuits, and algorithmic steps described in relation to the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly demonstrate this hardware and software compatibility, various exemplary components, blocks, modules, circuits, and steps are described above in general terms with respect to their functionality. Whether such functionality is implemented as hardware or as software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each specific application, but such implementation decisions should not be construed as causing a departure from the scope of this disclosure.

[0151] The various exemplary logic blocks, modules, and circuits described in relation to the embodiments disclosed herein may be implemented or run 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. The 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 in conjunction with a DSP core, or any other such configuration.

[0152] The methods, sequences, and / or algorithms described in relation to the embodiments disclosed herein may be embodied in hardware directly, 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 with 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 in the user terminal as separate components.

[0153] In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted via computer-readable media as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any media that facilitate the transfer of computer programs from one location to another. Storage media may be any available media accessible 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 a medium. Disk and disc, as used herein, include compact disc (CD), laserdisc (disc), optical disc, digital versatile disc (disc) (DVD), floppy disk (disk), and Blu-ray (disc), where a disk typically reproduces data magnetically and a disc optically reproduces data using a laser. Combinations of the above should also be included within the scope of computer-readable media.

[0154] 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 any particular 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.

[0155] In embodiments for carrying out the above invention, it can be understood that various features are grouped together in the examples. This manner of disclosure should not be understood as an intention that the exemplary clauses have more features than are explicitly stated in each clause. Rather, the various embodiments of this disclosure may contain fewer features than all features of the individual exemplary clauses disclosed. Accordingly, the following clauses should be considered by this specification as being incorporated into this description, and each clause may be valid on its own as a separate example. Each dependent clause may refer in itself to a specific combination with one of the other clauses, but the embodiments of that dependent clause are not limited to that specific combination. It will be understood that the other exemplary clauses may also include combinations of dependent clause embodiments with the subject matter of any other dependent clause or independent clause, or any combination of features with other dependent clauses and independent clauses. The various embodiments disclosed herein explicitly include these combinations unless it is explicitly stated or easily inferred that a particular combination is not intended (for example, in contradictory embodiments such as defining an element as both an insulator and a conductor). Furthermore, even if a clause is not directly subordinate to an independent clause, it is intended that the form of the clause may be included in any other independent clause.

[0156] Implementation examples are described in the following numbered sections.

[0157] Clause 1. A method of wireless communication performed by a first user device (UE), comprising the steps of: receiving a capability inquiry message for a sidelink positioning procedure from a network node, the capability inquiry message comprising at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure; and transmitting a capability information message to the network node indicating one or more capabilities of the first UE to participate in a sidelink positioning procedure, the one or more capabilities of the first UE comprising at least an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure.

[0158] Clause 2. The method according to Clause 1, wherein the capability inquiry message is a first radio resource control (RRC) message, a first medium access control element (MAC-CE), a first sidelink control information (SCI), or a first long-term evolution (LTE) positioning protocol (LPP) message, and the capability information message is a second RRC message, a second MAC-CE, a second SCI, or a second LPP message.

[0159] Clause 3. The method described in any one of Clauses 1 to 2, wherein the indication of whether the first UE has the ability to provide the location of the first UE for the sidelink positioning procedure is a Boolean value.

[0160] Clause 4. The method of any one of Clauses 1 to 3, including an indication of whether one or more capabilities of the First UE have the capability to provide position calculations for a sidelink positioning procedure based on received location measurement result information.

[0161] Clause 5. The method of Clause 4, further comprising the step of determining the location of a second UE based at least in part on the location of a first UE and the measurement results of a positioning reference signal received from a second UE.

[0162] Clause 6. The method described in any one of Clauses 4 to 5, wherein the indication of whether the first UE has the ability to provide position calculations for the sidelink positioning procedure is a Boolean value.

[0163] Clause 7. The method of any one of Clauses 1 to 6, further comprising the steps of receiving a request for the location of the first UE from a network node, based on an indication that the first UE has the ability to provide the location of the first UE for a sidelink positioning procedure, and transmitting the location of the first UE to the network node.

[0164] Clause 8. The method described in any one of Clauses 1 to 7, wherein one or more capabilities of the First UE include the location coordinates of the First UE.

[0165] Clause 9. The method described in any one of Clauses 1 through 8, wherein the network node is the third UE.

[0166] Clause 10. The method according to Clause 9, wherein the capability inquiry message includes a “UECapabilityEnquirySidelink” information element (IE), and the capability information message includes a “UECapabilityInformationSidelink” IE.

[0167] Clause 11. The method of Clause 10, wherein the indication of whether the first UE has the ability to provide the location of the first UE for the sidelink positioning procedure includes the "PositionAnchorCapabilityStatus" field in the "UECapabilityEnquirySidelink" IE, the "UECapabilityInformationSidelink" IE, or both.

[0168] Clause 12. The method described in any one of Clauses 1 through 8, wherein the network node is a base station or a location server serving the first UE.

[0169] Clause 13. The method according to Clause 12, wherein the capability inquiry message includes "UECapabilityEnquiry" IE and the capability information message includes "UECapabilityInformation" IE.

[0170] Clause 14. The method of Clause 13, wherein the indication of whether the first UE has the ability to provide the location of the first UE for the sidelink positioning procedure includes the "PositionAnchorCapabilityStatus" field in the "UECapabilityEnquiry" IE, the "UECapabilityInformation" IE, or both.

[0171] Clause 15. A method of wireless communication performed by a network node, comprising the steps of: transmitting a capability inquiry message to a first user equipment (UE) for a sidelink positioning procedure, the capability inquiry message comprising at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure; and receiving a capability information message from the first UE indicating one or more capabilities of the first UE, the one or more capabilities of the first UE comprising at least an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure.

[0172] Clause 16. The method of Clause 15, further comprising the steps of sending a request for the location of the first UE to the first UE based on an indication that the first UE has the ability to provide the location of the first UE for a sidelink positioning procedure, and receiving the location of the first UE from the first UE.

[0173] Clause 17. The method described in any one of Clauses 15 to 16, wherein one or more capabilities of the First UE include the location coordinates of the First UE.

[0174] Clause 18. The method of any one of Clauses 15 to 17, further comprising the step of determining the location of a second UE based at least in part on the location of a first UE and the measurement results of a positioning reference signal received from a second UE.

[0175] Clause 19. The method described in Clause 18, wherein the network node is the second UE.

[0176] Clause 20. The method according to any one of Clauses 15 to 19, wherein the capability inquiry message is a first radio resource control (RRC) message, a first medium access control element (MAC-CE), a first sidelink control information (SCI), or a first long-term evolution (LTE) positioning protocol (LPP) message, and the capability information message is a second RRC message, a second MAC-CE, a second SCI, or a second LPP message.

[0177] Clause 21. The method described in any one of Clauses 15 to 20, including an indication of whether one or more capabilities of the First UE have the capability to provide position calculations for a sidelink positioning procedure based on received location measurement result information.

[0178] Clause 22. The method described in any one of Clauses 15 to 18, 20 and 21, wherein the network node is a base station or a location server serving the first UE.

[0179] Clause 23. A first user device (UE) comprising a memory and at least one processor communicatively coupled to the memory, wherein the memory and at least one processor are configured to receive capability inquiry messages for a sidelink positioning procedure from a network node, the capability inquiry messages comprising at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure, and to transmit capability information messages to the network node indicating one or more capabilities of the first UE to participate in a sidelink positioning procedure, the one or more capabilities of the first UE comprising at least an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure.

[0180] Clause 24. A UE as described in Clause 23, wherein the capability inquiry message is a first Radio Resource Control (RRC) message, a first Medium Access Control Element (MAC-CE), a first Sidelink Control Information (SCI), or a first Long-Term Evolution (LTE) Positioning Protocol (LPP) message, and the capability information message is a second RRC message, a second MAC-CE, a second SCI, or a second LPP message.

[0181] Clause 25. A UE described in any one of Clauses 23 to 24, whose indication of whether the First UE has the ability to provide the location of the First UE for the Sidelink positioning procedure is a Boolean value.

[0182] Clause 26. One or more capabilities of the First UE, including an indication of whether the First UE has the capability to provide position calculations for a sidelink positioning procedure based on received location measurement result information, as described in any one of Clauses 23 to 25.

[0183] Clause 27. The UE described in Clause 26, further configured to determine the location of the second UE based at least in part on the location of the first UE and the result of a measurement of a positioning reference signal received from the second UE.

[0184] Clause 28. A UE described in any one of Clauses 26 to 27, where the indication of whether the first UE has the ability to provide position calculations for the sidelink positioning procedure is a Boolean value.

[0185] Clause 29. A UE described in any one of Clauses 23 to 28, further configured to receive requests for the location of the first UE from a network node and transmit the location of the first UE to a network node, based on an indication of whether the first UE has the ability to provide the location of the first UE for a sidelink positioning procedure that the first UE has the ability to provide the location of the first UE for a sidelink positioning procedure.

[0186] Clause 30. One or more capabilities of the First UE include the location coordinates of the First UE, as described in any one of Clauses 23 to 29.

[0187] Clause 31. A UE described in any one of Clauses 23 to 30, whose network node is a third UE.

[0188] Clause 32. A UE as described in Clause 31, wherein the capability inquiry message includes a “UECapabilityEnquirySidelink” information element (IE), and the capability information message includes a “UECapabilityInformationSidelink” IE.

[0189] Clause 33. The UE described in Clause 32, which includes a "PositionAnchorCapabilityStatus" field in the "UECapabilityEnquirySidelink" IE, "UECapabilityInformationSidelink" IE, or both, indicating whether the First UE has the ability to provide the location of the First UE for a sidelink positioning procedure.

[0190] Clause 34. A UE described in any one of Clauses 23 to 30, where the network node is a base station or a location server serving the first UE.

[0191] Clause 35. A UE as described in Clause 34, whose capability inquiry message includes "UECapabilityEnquiry" IE and whose capability information message includes "UECapabilityInformation" IE.

[0192] Clause 36. A UE described in Clause 35, which includes a "PositionAnchorCapabilityStatus" field in the "UECapabilityEnquiry" IE, "UECapabilityInformation" IE, or both, indicating whether the First UE has the ability to provide the location of the First UE for the Sidelink positioning procedure.

[0193] Clause 37. Network node, comprising memory and at least one processor communicatively coupled to the memory, wherein the memory and at least one processor are configured to transmit capability inquiry messages to a first user equipment (UE) for a sidelink positioning procedure, the capability inquiry messages comprising at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure, and to receive capability information messages from the first UE indicating one or more capabilities of the first UE to participate in a sidelink positioning procedure, the one or more capabilities of the first UE comprising at least an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure.

[0194] Clause 38. A network node as described in Clause 37, further configured to send a request for the location of the first UE to the first UE and receive the location of the first UE from the first UE, based on an indication of whether the first UE has the ability to provide the location of the first UE for a sidelink positioning procedure that the first UE has the ability to provide the location of the first UE for a sidelink positioning procedure.

[0195] Clause 39. One or more capabilities of the First UE include the network nodes described in any one of Clauses 37 to 38, including the location coordinates of the First UE.

[0196] Clause 40. A network node according to any one of Clauses 37 to 39, further configured to determine the location of a second UE based at least in part on the location of a first UE and the result of a measurement of a positioning reference signal received from a second UE.

[0197] Clause 41. A network node as described in Clause 40, where the network node is the second UE.

[0198] Clause 42. A network node as described in any one of Clauses 37 to 41, wherein the capability inquiry message is a first Radio Resource Control (RRC) message, a first Medium Access Control Element (MAC-CE), a first Sidelink Control Information (SCI), or a first Long-Term Evolution (LTE) Positioning Protocol (LPP) message, and the capability information message is a second RRC message, a second MAC-CE, a second SCI, or a second LPP message.

[0199] Clause 43. Network nodes as described in any one of Clauses 37 to 42, including an indication of whether one or more capabilities of the First UE have the capability to provide position calculations for a sidelink positioning procedure based on received location measurement result information.

[0200] Clause 44. A network node described in any one of Clauses 37 to 40, 42, and 43, where the network node is a base station or a location server serving the first UE.

[0201] Clause 45. Means for receiving capability inquiry messages for a sidelink positioning procedure from a network node, the capability inquiry message comprising at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure; and means for transmitting capability information messages to the network node indicating one or more capabilities of the first UE to participate in a sidelink positioning procedure, the first user equipment (UE) comprising at least an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure.

[0202] Clause 46. A UE as described in Clause 45, wherein the capability inquiry message is a first Radio Resource Control (RRC) message, a first Medium Access Control Element (MAC-CE), a first Sidelink Control Information (SCI), or a first Long-Term Evolution (LTE) Positioning Protocol (LPP) message, and the capability information message is a second RRC message, a second MAC-CE, a second SCI, or a second LPP message.

[0203] Clause 47. A UE described in any one of Clauses 45 to 46, whose indication of whether the First UE has the ability to provide the location of the First UE for the Sidelink positioning procedure is a Boolean value.

[0204] Clause 48. One or more capabilities of the First UE, including an indication of whether the First UE has the capability to provide position calculations for a sidelink positioning procedure based on received location measurement result information, as described in any one of Clauses 45 to 47.

[0205] Clause 49. The UE described in Clause 48, further comprising means for determining the location of a second UE based at least in part on the location of a first UE and the measurement results of a positioning reference signal received from a second UE.

[0206] Clause 50. A UE described in any one of Clauses 48 to 49, where the indication of whether the first UE has the ability to provide position calculations for the sidelink positioning procedure is a Boolean value.

[0207] Clause 51. A UE described in any one of Clauses 45 to 50, further comprising means for receiving requests for the location of the first UE from a network node, and means for transmitting the location of the first UE to a network node, based on an indication that the first UE has the ability to provide the location of the first UE for a sidelink positioning procedure.

[0208] Clause 52. One or more capabilities of the First UE include the location coordinates of the First UE, as described in any one of Clauses 45 to 51.

[0209] Clause 53. A UE described in any one of Clauses 45 to 52, wherein the network node is a third UE.

[0210] Clause 54. A UE as described in Clause 53, wherein the capability inquiry message includes a “UECapabilityEnquirySidelink” information element (IE), and the capability information message includes a “UECapabilityInformationSidelink” IE.

[0211] Clause 55. The UE described in Clause 54, which includes a “PositionAnchorCapabilityStatus” field in the “UECapabilityEnquirySidelink” IE, “UECapabilityInformationSidelink” IE, or both, indicating whether the First UE has the ability to provide the location of the First UE for a sidelink positioning procedure.

[0212] Clause 56. A UE described in any one of Clauses 45 to 52, where the network node is a base station or a location server serving the first UE.

[0213] Clause 57. A UE as described in Clause 56, whose capability inquiry message includes "UECapabilityEnquiry" IE and whose capability information message includes "UECapabilityInformation" IE.

[0214] Clause 58. The UE described in Clause 57, which includes a “PositionAnchorCapabilityStatus” field in the “UECapabilityEnquiry” IE, “UECapabilityInformation” IE, or both, indicating whether the First UE has the ability to provide the Location of the First UE for the Sidelink Positioning Procedure.

[0215] Article 59. A means for transmitting a capability inquiry message to a first user device (UE) for a sidelink positioning procedure, the capability inquiry message comprising at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure; and a means for receiving a capability information message from the first UE indicating one or more capabilities of the first UE to participate in a sidelink positioning procedure, the one or more capabilities of the first UE comprising at least an indication of whether the first UE has the capability to provide the location of the first UE for a sidelink positioning procedure, network node.

[0216] Clause 60. The network node described in Clause 59, further comprising means for transmitting a request for the location of the first UE to the first UE, based on an indication that the first UE has the ability to provide the location of the first UE for a sidelink positioning procedure, and means for receiving the location of the first UE from the first UE.

[0217] Clause 61. One or more capabilities of the First UE include the network nodes described in any one of Clauses 59 to 60, including the location coordinates of the First UE.

[0218] Clause 62. A network node according to any one of Clauses 59 to 61, further comprising means for determining the location of a second UE based at least in part on the location of a first UE and the results of measurements of a positioning reference signal received from a second UE.

[0219] Clause 63. A network node as described in Clause 62, where the network node is the second UE.

[0220] Clause 64. A network node as described in any one of Clauses 59 to 63, wherein the capability inquiry message is a first Radio Resource Control (RRC) message, a first Medium Access Control Element (MAC-CE), a first Sidelink Control Information (SCI), or a first Long-Term Evolution (LTE) Positioning Protocol (LPP) message, and the capability information message is a second RRC message, a second MAC-CE, a second SCI, or a second LPP message.

[0221] Clause 65. One or more capabilities of the First UE include an indication of whether the First UE has the capability to provide position calculations for a sidelink positioning procedure based on received location measurement result information, as described in any one of Clauses 59 to 64 of the network node.

[0222] Clause 66. A network node as described in any one of Clauses 59 to 62, 64 and 65, where the network node is a base station or a location server serving the first UE.

[0223] Clause 67. 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 a procedure as described in any one of Clauses 1 to 66. [Explanation of Symbols]

[0224] 100 Wireless Communication Systems 102 Base station 102' Small Cell (SC) 104 User Equipment (UE) 106 Sidelink UE (SL-UE) 108 Side Link Components 110 Geographic Coverage Areas 110' Geographic Coverage Area 112 Space Vehicles (SV) 120 Communication Links 122 Backhaul Link 124 SPS signals 134 Backhaul Link 150 Wireless Local Area Network (WLAN) Access Point (AP) 152 Wireless Local Area Network (WLAN) Station (STA) 154 Communication Links 160 Vehicle UE (V-UE) 162 Wireless Sidelink 164 Roadside Access Points 166 Wireless Sidelink 168 Wireless Sidelink 172 Location Server 174 Core Network 180 mmW base station 182 User Equipment (UE) 184 mmW communication link 190 User Equipment (UE) 192 D2D P2P Link 194 D2D P2P Links 200 Wireless Network Structures 200 Wireless Communication Systems 204 User Equipment (UE) 204-1 Anchor UE 204-2 Target UE 204-N Target UE 210 5G Core (5GC) 212 User Plane Features 213 User Plane Interface (NG-U) 214 Control Plane Functions 215 Control Plane Interface (NG-C) 220 Next Generation RAN (NG-RAN) 222 gNB 223 Backhaul connection 224 Next generation eNB (ng-eNB) 226 gNB Central Unit (gNB-CU) 228 gNB distributed units (gNB-DU) 230 Location Servers 232 Interfaces 250 Wireless Network Structures 250 Wireless Communication Systems 260 5GC 262 User Plane Function (UPF) 263 User Plane Interface 264 Access and Mobility Management Function (AMF) 265 Control Plane Interface 266 Session Management Function (SMF) 270 Location Management Function (LMF) 272 Secure User Plane Location (SUPL) Location Platform (SLP) 302 UE 304 base station 306 Network Entity 310 Wireless Wide Area Network (WWAN) Transceiver 312 Receiver 314 Transmitter 316 Antenna 318 Signal 320 Short-distance wire restaurant Seaba 322 Receiver 324 Transmitter 326 Antenna 328 signal 330 Satellite signal receiver 332 processors 334 Data Bus 336 Antenna 338 Satellite positioning / communication signals 340 memory 342 Side Link Components 344 Sensors 346 User Interface 350 WWAN Transceiver 352 Receiver 354 Transmitter 356 Antenna 358 Signal 360 Short-distance wire restaurant Seaba 362 Receiver 364 Transmitter 366 Antenna 368 signal 370 Satellite signal receiver 376 Antenna 378 Satellite positioning / communication signals 380 Network Transceivers 382 Databus 384 processors 386 memory 388 Side Link Components 390 Network Transceivers 392 Data Bus 394 processors 396 memory 398 Side Link Components 400 Wireless Communication Systems 402 First UE 404 Second UE 405 Sidelink Signaling Radio Bearer 410 Sidelink Signaling Radio Bearer 415 Connection Request 420 Connection Response 425 Connection established 430 Sidelink 435 Sidelink Data 500 Sidelink ranging and positioning procedure 505 levels 510 levels 515 levels 520 levels 525 levels 530 levels 535 levels 540 levels 600 Network-Managed Sidelink Ranging and Positioning Procedures 610 levels 620 levels 630 levels 640 levels 650 levels 700 Network-Managed Sidelink Ranging and Positioning Procedure 710 levels 720 levels 730 levels 740 levels 750 levels 800 Positioning Anchor Capability Information Elements 900 Capacity Exchange Procedure 910 Capability Inquiry Message 912 display 930 Capability Information Message 932 displays 1000 Ability Exchange Procedure 1010 Capability Inquiry Message 1012 display 1030 Ability Information Message 1032 displays 1300 User Equipment 1310 memory 1320 Communication Devices 1330 processor 1340 Data Bus 1400 network nodes 1410 memory 1420 Communication Devices 1430 Processor 1440 Data Bus 1500 User Equipment 1510 Module for receiving 1520 Module for transmission 1600 network nodes 1610 Module for transmission 1620 Module for receiving

Claims

1. A wireless communication method for sidelink-based positioning performed by a first user device (UE), Steps include receiving a capability inquiry message from a second UE for a sidelink positioning procedure, wherein the capability inquiry message includes at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for the sidelink positioning procedure, A step of sending a capability information message to the second UE indicating one or more capabilities of the first UE to participate in the sidelink positioning procedure, wherein the one or more capabilities of the first UE include at least an indication of whether the first UE has the capability to provide the location of the first UE for the sidelink positioning procedure. A method that includes this.

2. The method according to claim 1, wherein the one or more capabilities of the first UE include an indication of whether the first UE has the capability to provide a position calculation for the sidelink positioning procedure based on received location measurement result information.

3. The steps include receiving a request for the location of the first UE from the second UE, based on the indication that the first UE has the capability to provide the location of the first UE for the sidelink positioning procedure, The method according to claim 1, further comprising the step of transmitting the location of the first UE to the second UE.

4. The method according to claim 1, wherein the one or more capabilities of the first UE include the location coordinates of the first UE.

5. A wireless communication method for sidelink-based positioning performed by a second user device (UE), A step of sending a capability inquiry message to a first UE for a sidelink positioning procedure, wherein the capability inquiry message includes at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for the sidelink positioning procedure, A step of receiving capability information messages from the first UE indicating one or more capabilities of the first UE to participate in the sidelink positioning procedure, wherein the one or more capabilities of the first UE include at least an indication of whether the first UE has the capability to provide the location of the first UE for the sidelink positioning procedure. A method that includes this.

6. The steps include transmitting a request for the location of the first UE to the first UE, based on the indication that the first UE has the capability to provide the location of the first UE for the sidelink positioning procedure, The method according to claim 5, further comprising the step of receiving the location of the first UE from the first UE.

7. The method according to claim 5, wherein the one or more capabilities of the first UE include the location coordinates of the first UE.

8. The method according to claim 5, wherein the one or more capabilities of the first UE include an indication of whether the first UE has the capability to provide a position calculation for the sidelink positioning procedure based on received location measurement result information.

9. A first user device (UE) for sidelink-based positioning, Memory and The memory includes at least one processor that is communicatively coupled to the memory, and the memory and the at least one processor are Receiving a capability inquiry message for a sidelink positioning procedure from a second UE, wherein the capability inquiry message includes at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for the sidelink positioning procedure, Sending capability information messages to the second UE indicating one or more capabilities of the first UE to participate in the sidelink positioning procedure, wherein the one or more capabilities of the first UE include at least an indication of whether the first UE has the capability to provide the first UE's location for the sidelink positioning procedure. A first UE configured to perform the following.

10. The capability inquiry message is a first radio resource control (RRC) message, a first media access control element (MAC-CE), a first sidelink control information (SCI), or a first long-term evolution (LTE) positioning protocol (LPP) message. The first UE according to claim 9, wherein the capability information message is a second RRC message, a second MAC-CE, a second SCI, or a second LPP message.

11. The first UE according to claim 9, wherein the indication of whether the first UE has the ability to provide the location of the first UE for the sidelink positioning procedure is a Boolean value.

12. The one or more capabilities of the first UE include an indication of whether the first UE has the ability to provide a position calculation for the sidelink positioning procedure based on received location measurement result information, The memory and the at least one processor, The system is further configured to determine the location of the second UE, at least in part, based on the location of the first UE and the measurement result of a positioning reference signal received from the second UE. The first UE according to claim 9, wherein the indication of whether the first UE has the ability to provide position calculations for the sidelink positioning procedure is a Boolean value.

13. The memory and the at least one processor, The indication that the first UE has the capability to provide the location of the first UE for the sidelink positioning procedure is based on the first UE having the capability to provide the location of the first UE for the sidelink positioning procedure, and the second UE receives a request for the location of the first UE. The first UE according to claim 9, further configured to transmit the location of the first UE to the second UE.

14. The first UE according to claim 9, wherein the one or more capabilities of the first UE include the location coordinates of the first UE.

15. A second user device (UE) for sidelink-based positioning, Memory and The memory includes at least one processor that is communicatively coupled to the memory, and the memory and the at least one processor are Sending a capability inquiry message for a sidelink positioning procedure to a first user device (UE), wherein the capability inquiry message includes at least a request for an indication of whether the first UE has the capability to provide the location of the first UE for the sidelink positioning procedure, Receiving capability information messages from the first UE indicating one or more capabilities of the first UE to participate in the sidelink positioning procedure, wherein the one or more capabilities of the first UE include at least an indication of whether the first UE has the capability to provide the first UE's location for the sidelink positioning procedure. A second UE configured to perform the following actions.

Images