KR20240076845A - Sidelink positioning architecture for wireless communications - Google Patents

Abstract

Sidelink positioning for wireless communications currently includes the LoCation Services (LCS) architecture, PROximity based SErvices (ProSe) architecture, and Vehicle-to-Everything (V2X) architecture to include sidelink positioning during, for example, New Radio (NR) wireless communications. This can be achieved by extending the architecture. The existing architectural infrastructures of LCS, ProSe and V2X can be extended to include additional signaling and/or to incorporate communication of sidelink positioning information into existing signaling and/or between user equipment devices (UEs) as well. rather, it can be modified to modify existing signaling to carry commands between UEs and relevant network functions directly or via base stations where applicable.

Description

Sidelink positioning architecture for wireless communications

This application relates to wireless communications, including sidelink positioning in wireless communications.

Wireless communication systems are rapidly increasing in use. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. Many mobile devices (i.e., user equipment devices or UEs) now provide access to the Internet, email, text messaging, and navigation using the global positioning system (GPS), in addition to supporting phone calls. , you can run sophisticated applications that utilize these functions. Additionally, a number of different wireless communication technologies and standards exist. Some examples of wireless communication standards are GSM, UMTS (WCDMA, TDS-CDMA), LTE, LTE Advanced (LTE-A), HSPA, 3GPP2 CDMA2000 (e.g. 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 ( WLAN or Wi-Fi), IEEE 802.16 (WiMAX), BLUETOOTH ^TM , etc. The current telecommunications standard, which goes beyond the current International Mobile Telecommunications-Advanced (IMT-Advanced) standards, is called 5th generation mobile networks or 5th generation wireless systems, which are 3GPP NR (otherwise known as 5G-NR for 5G New Radio). or known as NR-5G, and also simply referred to as NR). NR, over LTE standards, offers higher capacity for a higher density of mobile broadband users, providing ultra-high device-to-device reliability, and massive machine-to-machine communications, as well as lower latency and lower battery life. Consumption is suggested.

One aspect of wireless communication systems, including NR cellular wireless communications, involves device-to-device communications, including sidelink communications, and device positioning during sidelink communications. Improvements in these areas are required.

In particular, embodiments of methods and procedures for effective and efficient device positioning for communication devices, e.g., during wireless communications, e.g., device-to-device or sidelink communications, are disclosed herein. It is presented in Embodiments herein are directed to wireless communication systems comprising at least wireless communication devices or user equipment devices (UEs) and/or base stations and/or access points (APs) that communicate with each other within the wireless communication systems. It is presented additionally.

To more accurately determine device positioning, ProSe, V2X and LCS architectures can be extended to accommodate sidelink device positioning. Accordingly, additional signaling may be added and/or existing signaling may be modified/enhanced to incorporate information and instructions for implementing sidelink positioning among multiple UEs.

For example, in some embodiments, the UE may be configured to transmit, in a NAS registration request message for the AMF of the core network, an indication that the UE supports sidelink positioning. The UE may subsequently receive, from the AMF, an indication of authorization for the UE to use sidelink positioning. In some cases, an indication that the UE is authorized to use sidelink positioning may be received in response to a decision by the AMF. In some cases, an indication of authorization for the UE to use sidelink positioning may be received in the NAS Registration Accept message.

As another example, in some embodiments, the UE may be configured to transmit in a ProSe sidelink discovery notification message an indication that the UE supports sidelink positioning. Sidelink positioning may then be subsequently used with the UE. For example, sidelink positioning may be used with the UE in response to a ProSe sidelink discovery notification message indicating that the UE supports sidelink positioning.

As a further example, in some embodiments, the UE may be configured to transmit in a ProSe sidelink discovery solicitation message an indication that the UE supports sidelink positioning. A UE may be configured to receive an indication from a neighboring UE that the other UE supports sidelink positioning. An indication that the neighboring UE supports sidelink positioning may be received in the ProSe Discovery Response message. Additionally, the UE may be configured to determine, in response to the indications, that the UE and the neighboring UE will use sidelink positioning between themselves.

As yet a further example, in some embodiments, the UE may be configured to transmit, via the V5 interface, a first indication that the UE supports sidelink positioning. The UE may be configured to receive a second indication, via the V5 interface, from a neighboring UE, such as neighboring UE 106, that the neighboring UE supports sidelink positioning. Additionally, the UE may be configured to determine, in response to the first indication and the second indication, that the UE and the neighboring UE will use sidelink positioning between them.

As another example, in some embodiments, the UE may be configured to transmit first information indicating the UE's sidelink positioning reference signal (PRS) capabilities. The UE may be configured to receive sidelink PRS configuration information for the UE. Additionally, the UE may be configured to transmit one or more sidelink PRSs according to sidelink PRS configuration information.

The techniques described herein can be used with many different types of devices, including but not limited to base stations, access points, cellular phones, portable media players, tablet computers, wearable devices, and various other computing devices. Note that they may be implemented within and/or used in conjunction with them.

The present disclosure is intended to provide a brief overview of some of the subject matter described herein. Accordingly, it will be understood that the features described above are examples only and should not be construed to limit the scope or spirit of the subject matter described herein in any way. Other features, aspects and advantages of the subject matter described herein will become apparent from the following detailed description, drawings and claims.

1 illustrates an example (and simplified) wireless communication system in accordance with some embodiments.
2 illustrates an example base station communicating with an example wireless user equipment (UE) device, according to some embodiments.
3 illustrates an example block diagram of a UE according to some embodiments.
4 illustrates an example block diagram of a base station according to some embodiments.
Figure 5 shows an example simplified block diagram illustrating cellular communications circuitry, according to some embodiments.
6 and 7 illustrate example flow diagrams for UE sidelink positioning based on LCS architecture, according to some embodiments.
8 illustrates an example flow diagram for sidelink positioning authorization in accordance with some embodiments.
9 illustrates an example flow diagram for UE discovery for sidelink positioning using a discovery notification message, according to some embodiments.
10 illustrates an example flow diagram for UE discovery for sidelink positioning using a discovery solicitation message, according to some embodiments.
11 illustrates an example block diagram of a call flow for sidelink positioning using a V5 interface, according to some embodiments.
Figure 12 illustrates a block diagram of an example of a call flow for sidelink positioning in wireless communications, according to some embodiments.
Although various modifications and alternative forms of the features described herein are possible, specific embodiments thereof are shown by way of example in the drawings and are described in detail herein. However, the drawings and detailed description thereof are not intended to be limited to the particular form disclosed; on the contrary, the intent is to make all modifications, equivalents, and modifications within the spirit and scope of the subject matter as defined by the appended claims. It should be understood that it is intended to cover and alternatives.

Abbreviations

Various abbreviations are used throughout this application. Definitions of the most prominently used abbreviations that may appear throughout this application are provided below:

5GMM: 5G 이동성 관리(5GS Mobility Management)

5GMM : 5GS Mobility Management

AF: Application Function

AMF: Access and Mobility Management Function

AMR: Adaptive Multi-Rate

AP: Access Point

APN: Access Point Name

APR: Applications Processor

BS : Base Station

BSSID: Basic Service Set Identifier

CBRS: Citizens Broadband Radio Service

CBSD: Citizens Broadband Radio Service Device

CCA: Clear Channel Assessment

CMR: Change Mode Request

CS: Circuit Switched

DL : Downlink (from BS to UE)

DMRS : Demodulation Reference Signal

DN : Data Network

DSDS : Dual SIM Dual Standby

DYN: Dynamic

EDCF: Enhanced Distributed Coordination Function

eSNPN: Equivalent Standalone Non-Public Network

ETSI: European Telecommunications Standards Institute

FDD : Frequency Division Duplexing

FT: Frame Type

GAA: General Authorized Access

GPRS: General Packet Radio Service

GSM : Global System for Mobile Communication

GTP: GPRS Tunneling Protocol

HPLMN: Home Public Land Mobile Network

IC: In Coverage

IMS: Internet Protocol Multimedia Subsystem

IOT: Internet of Things

IP: Internet Protocol

ITS: Intelligent Transportation Systems

LAN: Local Area Network

LBT: Signal detection before transmission (Listen Before Talk)

LCS: Location Services

LMF: Location Management Function

LPP: LTE Positioning Protocol

LQM: Link Quality Metric

LTE : Long Term Evolution

MCC : Mobile Country Code

MNO : Mobile Network Operator

MO-LR : Mobile Originated Location Request

MT-LR : Mobile-Terminated Location Request

NAS : Non-Access Stratum

NF : Network Function

NG-RAN : Next Generation Radio Access Network

NID : Network Identifier

NMF : Network Identifier Management Function

NPN : Non-Public (cellular) Network

NRF : Network Repository Function

NSI : Network Slice Instance

NSSAI : Network Slice Selection Assistance Information

OOC : out-of-coverage

PAL : Priority Access Licensee

PDCP: Packet Data Convergence Protocol

PDN: Packet Data Network

PDU: Protocol Data Unit

PGW: PDN Gateway

PLMN: Public Land Mobile Network

ProSe: Proximity Services

PRS: Positioning Reference Signal

PSCCH: Physical Sidelink Control Channel

PSFCH: Physical Sidelink Feedback Channel

PSSCH: Physical Sidelink Shared Channel

PSD: Power Spectral Density

PSS: Primary Synchronization Signal

PT: Payload Type

PTRS: Phase Tracking Reference Signal

QBSS: Quality of Service Enhanced Basic Service Set

QI: Quality Indicator

RA: Registration Accept

RAT: Radio Access Technology

RF : Radio Frequency

ROHC: Robust Header Compression

RR: Registration Request

RRC: Radio Resource Control

RSRP: Reference Signal Receive Power

RTP: Real-time Transport Protocol

RX : Reception/Receive

SAS : Spectrum Allocation Server

SD : Slice Descriptor

SI : System Information

SIB : System Information Block

SID: System Identification Number

SIM: Subscriber Identity Module

SGW: Serving Gateway

SMF: Session Management Function

SNPN: Standalone Non-Public Network

SSS: Secondary Synchronization Signal

SUPI: Subscription Permanent Identifier

TBS: Transport Block Size

TCP: Transmission Control Protocol

TDD : Time Division Duplexing

TDRA : Time Domain Resource Allocation

TPC : Transmit Power Control

TX : Transmission/Transmit

UAC : Unified Access Control

UDM : Unified Data Management

UDR : User Data Repository

UE : User Equipment

UI : User Input

UL : Uplink (from UE to BS)

UMTS : Universal Mobile Telecommunication System

UPF : User Plane Function

URM : Universal Resources Management

URSP : UE Route Selection Policy

USIM : User Subscriber Identity Module

Wi-Fi: Wireless Local Area Network (WLAN) RAT based on IEEE 802.11 standards

WLAN: Wireless LAN

terms

The following is a description of terms that may appear in this application:

Memory media - Any of various types of memory devices or storage devices. The term “memory media” includes installation media, such as a CD-ROM, floppy disk, or tape device; Computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; Non-volatile memory such as flash, magnetic media, such as hard drives, or optical storage; It is intended to include registers, or other similar types of memory elements, etc. Memory media may also include other types of memory or combinations thereof. Additionally, the memory medium may be located on a first computer system on which the programs are executed, or may be located on a second, different computer system connected to the first computer system through a network, such as the Internet. In the latter case, the second computer system can provide program instructions to the first computer system for execution. The term “memory medium” may include two or more memory media that may reside in different locations, for example, different computer systems connected through a network. A memory medium may store program instructions (e.g., implemented as computer programs) that can be executed by one or more processors.

Carrier media - Memory media as described above, as well as physical transmission media such as buses, networks, and/or other physical transmission media that carry signals such as electrical, electromagnetic, or digital signals.

Programmable Hardware Element - Includes various hardware devices comprising a number of programmable functional blocks connected through programmable interconnects. Examples include Field Programmable Gate Arrays (FPGAs), Programmable Logic Devices (PLDs), Field Programmable Object Arrays (FPOAs), and Complex Includes PLDs (CPLDs). Programmable functional blocks can range from fine grained (combinational logic or lookup tables) to coarse grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as “reconfigurable logic.”

Computer system (or computer) - personal computer system (PC), mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA) ), any of various types of computing or processing systems, including television systems, grid computing systems, or other devices or combinations of devices. Broadly speaking, the term “computer system” can be broadly defined to encompass any device (or combination of devices) that has at least one processor that executes instructions from a memory medium.

User Equipment (UE) (or “UE device”) —any of various types of computer system devices that perform wireless communications. It is also referred to as wireless communication devices, many of which may be mobile and/or portable. Examples of UE devices include mobile phones or smartphones (e.g. iPhone™, Android™ based phones) and tablet computers such as iPad™, Samsung Galaxy™, etc., gaming devices (e.g. Sony PlayStation™, Microsoft XBox™) etc.), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPod™), laptops, wearable devices (e.g., smart watches, smart glasses), PDAs, portable Internet devices, Includes music players, data storage devices, or other handheld devices, unmanned aerial vehicles (eg, drones) and unmanned aerial vehicle controllers, etc. Various other types of devices may support Wi-Fi, or both cellular and Wi-Fi communication capabilities, for example through short-range radio access technology (SRAT) such as BLUETOOTH™, etc. Or, if it includes other wireless communication capabilities, it would fall into this category. Broadly speaking, the term “UE” or “UE device” can be broadly defined to encompass any electronic, computing, and/or telecommunications device (or combination of devices) capable of wireless communication, and is also portable/ It can be mobile.

Wireless device (or wireless communication device) - any of various types of computer system devices that perform wireless communications using WLAN communications, SRAT communications, Wi-Fi communications, etc. As used herein, the term “wireless device” may refer to a UE device as defined above, or a fixed device, such as a fixed wireless client or wireless base station. For example, a wireless device may be any type of wireless station in an 802.11 system, such as an access point (AP) or a client station (UE), or a cellular wireless access technology (e.g., a base station or cellular phone). For example, it can be a wireless station of any type of cellular communication system that communicates according to 5G NR, LTE, CDMA, GSM).

Communication device - Any of various types of computer systems or devices that perform communications, which may be wired or wireless. A communication device may be portable (or mobile) or may be stationary or fixed at a location. A wireless device is an example of a communication device. UE is another example of a communication device.

Base Station (BS) - The term "base station" has the full scope of its ordinary meaning and includes, at a minimum, a radio communication station installed in a fixed location and used for communication as part of a wireless telephone system or radio system.

Processor - refers to various elements (e.g., circuits) or combinations of elements capable of performing a function in a device, for example in a user equipment device or in a cellular network device. Processors may include, for example, general purpose processors and associated memory, portions of individual processor cores or circuits thereof, entire processor cores or processing circuit cores, processing circuit arrays or processor arrays, ASICs (application-specific integrated circuits). Circuits such as, programmable hardware elements such as field programmable gate arrays (FPGAs), as well as any of the various combinations of the above.

Channel - A medium used to convey information from a transmitter (transmitter) to a receiver. Since the characteristics of the term "channel" may differ across different wireless protocols, the term "channel" as used herein is intended to be used in a manner consistent with the standards of the type of device for which the term is used by reference. It should be noted that this may be taken into consideration. In some standards, channel widths can be variable (eg, depending on device capability, band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels may be 22 MHz wide, while Bluetooth channels may be 1 MHz wide. Different protocols and standards may include different definitions of channels. Moreover, some standards may define and use multiple types of channels, for example, different channels for uplink or downlink and/or different channels for different purposes such as data, control information, etc.

Band (or frequency band) - The term "band" has the full scope of its general meaning and includes at least a section of spectrum (eg, radio frequency spectrum) in which channels are used or set aside for the same purpose. Moreover, “frequency band” is used to refer to any interval in the frequency domain separated by lower and upper frequencies. The term may refer to a gap in a wireless band or some other spectrum. Wireless communication signals can occupy a range of frequencies, through which (or there) they are transmitted. Such frequency range is also referred to as the bandwidth of the signal. Therefore, bandwidth refers to the difference between upper and lower frequencies in a continuous band of frequencies. A frequency band may represent one communication channel, or it may be subdivided into multiple communication channels. The allocation of radio frequency ranges to different uses is a major function of radio spectrum allocation.

Wi-Fi - The term "Wi-Fi" has a full range of its own general meaning, at least, a wireless communication network serviced by wireless LAN (WLAN) access points and providing connectivity to the Internet through these access points. or RAT. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standards and are sold under the name “Wi-Fi”. Wi-Fi (WLAN) networks are different from cellular networks.

Automatically - an action or operation is performed on a computer system (e.g., software executed by a computer system) or device (e.g., circuitry, programmable hardware element) without user input directly specifying or performing the action or operation. , ASICs, etc.). Accordingly, the term “automatically” contrasts with an action that is manually performed or specified by a user, where the user provides input that directly causes the action to be performed. An automatic procedure may be initiated by input provided by the user, but subsequent actions that are performed “automatically” are not specified by the user, i.e., the user is not performed “manually” specifying each action to be performed. . For example, by allowing the user to select individual fields and provide input specifying information (e.g., by typing information, selecting check boxes, wireless communication device selections, etc.) Filling out a form means filling out the form manually, even if the computer system must update the form in response to user actions. A form may be filled out automatically by a computer system, wherein the computer system (e.g., software running on the computer system) parses the fields of the form and then fills out the form without any user input specifying responses to the fields. Please fill in . As indicated above, the user can invoke automatic filling out of the form, but does not participate in the actual filling out of the form (e.g., the user does not manually specify responses to the fields, but rather these are automatically is being completed). This specification provides various examples of actions being performed automatically in response to actions taken by the user.

Approximately - Refers to a value that is almost correct or exact. For example, “approximately” can refer to a value that is within 1 to 10 percent of the exact (or desired) value. However, it should be noted that the actual threshold (or tolerance) may be application dependent. For example, in some embodiments, “approximately” may mean within 0.1% of some specific or desired value, while in various other embodiments the threshold may be as desired or as specific to the application, for example. It may be 2%, 3%, 5%, etc., as required by .

Concurrent - Refers to parallel execution or performance of tasks, processes, or programs performed in an at least partially overlapping manner. For example, concurrency can be defined using "strong" or strict concurrency, where tasks are performed (at least partially) in parallel for individual computational elements, or when tasks are interleaved, e.g. It can be implemented using "weak concurrency" if performed by time multiplexing.

Station (STA) —The term “station” herein refers to any device that has the ability to communicate wirelessly, for example, by using the 802.11 protocol. The station may be a laptop, desktop PC, PDA, access point or Wi-Fi phone, or any type of device similar to a UE. STAs may be fixed, mobile, portable, or wearable. In general wireless networking terminology, station (STA) broadly encompasses any device with wireless communication capabilities, so the terms station (STA), wireless client (UE) and node (BS) are often used interchangeably. It is used.

Configured to - Various components may be described as being “configured to” perform a task or tasks. In such contexts, “configured to” is a broad description generally meaning “structured to” perform a task or tasks during operation. In this way, a component can be configured to perform a task even if the component is not currently performing that task (e.g., a set of electrical conductors can connect two modules even if one module is not connected to the other module). may be configured to electrically connect them). In some contexts, “configured to” may be a broad description of a structure that generally means “having circuitry to” perform a task or tasks during operation. In this way, a component may be configured to perform a task even when the component is not currently on. In general, the circuit unit forming a structure corresponding to “configured to” may include hardware circuits.

Transmission scheduling —refers to the scheduling of transmissions, such as wireless transmissions. In some implementations of cellular wireless communications, signal and data transmissions may be organized according to designated time units of specific duration over which the transmissions occur. As used herein, the term “slot” has the full scope of its ordinary meaning and refers, at a minimum, to the smallest (or minimum) unit of scheduling time in wireless communications. For example, in 3GPP LTE, transmissions are split into radio frames, each radio frame being of the same (time) duration (eg, 10 ms). A radio frame in 3GPP LTE may be further divided into a specified number (e.g., 10) of subframes, each subframe of equal duration, with the smallest (minimum) scheduling subframes. Specified in units or time units specified for transmission. Accordingly, in the 3GPP LTE example, a “subframe” can be considered an example of a “slot” as defined above. Similarly, the smallest (or minimum) scheduling time unit for 5G NR (or NR for short) transmissions is referred to as a “slot”. In different communication protocols, the smallest (or smallest) scheduling time unit may also be named differently.

Resources - The term “resource” has the full scope of its general meaning and can refer to frequency resources and time resources used during wireless communication. As used herein, a resource element (RE) refers to a specific amount or quantity of a resource. For example, in the context of time resources, a resource element may be a period of specific length. In the context of frequency resources, a resource element may be a specific frequency bandwidth, or a specific amount of frequency bandwidth that may be centered on a specific frequency. As one specific example, a resource element may be one symbol (a time resource, e.g., associated with a period of a certain length) per subcarrier (a frequency resource, which may be centered at a particular frequency, e.g., associated with a certain frequency bandwidth). It can refer to a resource unit of . A resource element group (REG) has the full scope of its general meaning and refers to at least a specified number of consecutive resource elements. In some implementations, a resource element group may not include resource elements reserved for reference signals. A control channel element (CCE) refers to a group of a specified number of consecutive REGs. A resource block (RB) refers to a specified number of resource elements consisting of a specified number of subcarriers per specified number of symbols. Each RB may contain a specified number of subcarriers. A resource block group (RBG) refers to a unit containing multiple RBs. The number of RBs in one RBG may vary depending on the system bandwidth.

Bandwidth Part (BWP) - The carrier bandwidth part (BWP) is a contiguous set of physical resource blocks selected from a contiguous subset of common resource blocks for a given numerology on a given carrier. For the downlink, the UE can use up to a specified number of carrier BWPs (e.g., 4 BWPs, according to some specifications), with one BWP per carrier active at a given time (according to some specifications). It can be configured. For the uplink, the UE may similarly be configured with up to a number (eg, four) of carrier BWPs, with one BWP per carrier active at any given time (according to some specifications). When a UE is configured with a supplemental uplink, the UE can connect up to a specified number (e.g., 4) of carrier BWPs in the supplemental uplink, with one carrier BWP active at a given time (according to some specifications). It can be additionally configured.

Multi-Cell Arrays - A master node is defined as a node (radio access node) that provides control plane connectivity to the core network in the case of multi-radio dual connectivity (MR-DC). The master node may be, for example, a master eNB (3GPP LTE) or a master gNB (3GPP NR). A secondary node is defined as a radio access node without any control plane connection to the core network, providing additional resources to the UE in the case of MR-DC. A master cell group (MCG) is defined as a group of serving cells associated with a master node, including a primary cell (PCell) and optionally one or more secondary cells (SCell). A secondary cell group (SCG) is defined as a special cell, i.e. a group of serving cells associated with a secondary node, including a primary cell (PSCell) of the SCG, and optionally one or more SCells. The UE may typically apply radio link monitoring to the PCell. If the UE is configured with an SCG, the UE may also apply radio link monitoring to the PSCell. Radio link monitoring generally applies to active BWPs and the UE is not required to monitor inactive BWPs. The PCell is used to initiate initial access, and the UE can communicate with the PCell and SCell via carrier aggregation (CA). The current calibrated capability means that the UE can receive and/or transmit to/from multiple cells. The UE is initially connected to a PCell, and one or more SCells can be configured for the UE once the UE is connected.

Core Network (CN) - The core network is defined as a part of the 3GPP system that is independent of the UEs' access technology (eg, radio access technology, or RAT). UEs may be connected to the core network via a radio access network, i.e. RAN, which may be RAT-specific.

For convenience of explanation, various components may be described as performing a task or tasks. Such descriptions should be construed as including the phrase “configured to”. Any reference to a component configured to perform one or more tasks may refer to that component under 35 U.S.C. It is expressly intended that the interpretation of § 112, paragraph 6 shall not apply.

1 and 2 - Exemplary communication systems

1 illustrates an example (and simplified) wireless communication system in accordance with some embodiments. Note that the system of Figure 1 is merely an example of a possible system and that embodiments may be implemented in any of a variety of systems as desired.

As shown, the example wireless communication system includes base stations 102A-102N, also referred to collectively as base station(s) 102 or base station 102. As shown in FIG. 1, base station 102A communicates with one or more user devices 106A-106N via a transmission medium. Each of the user devices may be referred to herein as a “user equipment (UE)” or a UE device. Accordingly, user devices 106A-106N are referred to as UEs or UE devices, and are also collectively referred to as UE(s) 106 or UE 106. Various of the UE devices may transmit reference signals according to various embodiments disclosed herein.

Base station 102A may be a base transceiver station (BTS) or a cell site, and may include hardware that enables wireless communication with UEs 106A through 106N. Base station 102A may also be connected to network 100 (e.g., a core network of a cellular service provider, a telecommunications network such as a public switched telephone network (PSTN), and/or the Internet, a neutral host, or It may be equipped to communicate with a variety of Citizens Broadband Radio Service (CBRS) deployments. Accordingly, base station 102A may facilitate communication between user devices 106 and/or between user devices 106 and network 100. In particular, cellular base station 102A may provide various telecommunication capabilities to UEs 106, such as voice, short message service (SMS), and/or data services. The communication area (or coverage area) of base station 106 may be referred to as a “cell.” Note that “cell” can also refer to the logical identity for a given wireless communication coverage area at a given frequency. Broadly speaking, any independent cellular wireless coverage area may be referred to as a “cell.” In such cases, the base station may be located at specific confluence points of the three cells. A base station, in this uniform topology, can serve three 120 degree beamwidth regions, referred to as cells. Additionally, in the case of carrier aggregation, small cells, relays, etc. may each represent a cell. Accordingly, especially in carrier aggregation, there may be primary cells and secondary cells that may serve at least partially overlapping coverage areas, but at different individual frequencies. For example, a base station can serve any number of cells, and cells served by a base station may or may not be co-located (eg, remote wireless heads). As also used herein, from the perspective of UEs, a base station can sometimes be considered to represent a network, as far as the UE's uplink and downlink communications are concerned. Accordingly, a UE that communicates with one or more base stations within a network may also be interpreted as a UE that communicates with the network, and may further be considered at least part of a UE that communicates on or through the network.

Base station(s) 102 and user devices 106 support GSM, UMTS (WCDMA), LTE, LTE-Advanced (LTE-A), LAA/LTE-U, 5G-NR (NR for short), 3GPP2 Using any of the various Radio Access Technologies (RAT), also referred to as wireless communication technologies or telecommunication standards, such as CDMA2000 (e.g. 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, WiMAX, etc. Can be configured to communicate via a transmission medium. Note that if base station 102A is implemented in the context of LTE, it may alternatively be referred to as 'eNodeB' or 'eNB'. Similarly, if base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as 'gNodeB' or 'gNB'. In some embodiments, base station 102 (e.g., an eNB in an LTE network or a gNB in an NR network) is connected to at least one UE having the capability to transmit reference signals, according to various embodiments disclosed herein. Can communicate. Depending on the given application or specific considerations, for convenience, some of the various different RATs may be functionally grouped according to overall defining characteristics. For example, all cellular RATs may collectively be considered to represent a first (type/type) RAT, while Wi-Fi communications may be considered to represent a second RAT. In other cases, individual cellular RATs may be considered individually as different RATs. For example, when distinguishing between cellular communications and Wi-Fi communications, “first RAT” may collectively refer to all cellular RATs under consideration, while “second RAT” refers to Wi-Fi. can do. Similarly, where applicable, different types of Wi-Fi communications (eg, greater than 2.4 GHz versus greater than 5 GHz) may be considered to correspond to different RATs. Moreover, cellular communications performed according to a given RAT (eg, LTE or NR) may be distinguished from each other based on the frequency spectrum over which these communications are performed. For example, LTE or NR communications may be performed not only over primary licensed spectrum, but also over secondary spectrum, such as unlicensed spectrum and/or spectrum allocated to private networks. Throughout, the use of various terms and expressions will always be clearly indicated with respect to and within the context of the various applications/embodiments under consideration.

As shown, base station 102A may also be connected to network 100 (e.g., a core network of a cellular service provider, a telecommunications network such as the Public Switched Telephone Network (PSTN), and/or the Internet, among various possibilities). Can be equipped to communicate. Accordingly, base station 102A may facilitate communication between user devices 106 and/or between user devices 106 and network 100. In particular, cellular base station 102A may provide various communication capabilities to UEs 106, such as voice, SMS and/or data services. UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using any or all of the 3GPP cellular communication standards (such as LTE or NR) or the 3GPP2 cellular communication standards (such as the CDMA2000 family of cellular communication standards). It can be configured. Accordingly, base station 102A, and other similar base stations (e.g., base stations 102B...102N) operating according to the same or a different cellular communication standard, may be provided as one or more networks of cells, which may provide one or more cellular communication standards. Standards enable the provision of continuous or near-continuous overlapping services to UEs 106 and similar devices across large geographic areas.

Accordingly, although base station 102A may serve as a “serving cell” for UEs 106A through 106N as illustrated in FIG. 1, each of the UE(s) 106 may also serve as a “neighbor”. may receive signals from one or more other cells (possibly provided by base stations 102B through 102N and/or any other base stations), which may be referred to as "cells" (and possibly one of the may be within communication range of more than one cell). Such cells may also facilitate communication between user devices 106 and/or between user devices 106 and the network 100. Such cells may include “macro” cells, “micro” cells, “pico” cells, and/or cells providing any of a variety of other granularity of service area size. For example, base stations 102A and 102B illustrated in FIG. 1 may be macro cells, while base station 102N may be a micro cell. Other configurations are also possible.

In some embodiments, base station 102A may be a next-generation base station, such as a 5G NR base station or “gNB.” In some embodiments, a gNB may be connected to a legacy Evolved Packet Core (EPC) network and/or to a NR core (NRC) network. Additionally, a gNB cell may include one or more transmission and reception points (TRP). Additionally, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

Additionally or alternatively, UE 106 may support WLAN, BLUETOOTH ^™ , BLUETOOTH™ Low-Energy, one or more global navigational satellite systems (GNSS) (e.g., GPS or GLONASS), one and/or more mobile television broadcast Can be configured to communicate using casting standards (e.g., ATSC-M/H or DVB-H), etc. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible. Moreover, UE 106 may also communicate with network 100 through one or more base stations, or through other devices, stations, or any appliances not explicitly shown but considered to be part of network 100. Can communicate. Accordingly, UE(s) 106 in communication with a network are considered to be part of the network and may interact with UE(s) 106 to conduct communications with UE(s) 106, and in some cases: may be interpreted as UE(s) 106 communicating with one or more network nodes that may affect at least some of the communication parameters and/or use of communication resources of the UE(s) 106.

As also illustrated in FIG. 1 , at least some of the UEs, e.g., UEs 106D and 106E, communicate with each other and a base station, e.g., via cellular communications, such as 3GPP LTE and/or 5G-NR communications. Vehicles communicating with (102) can be expressed. Additionally, UE 106F may represent a pedestrian that is communicating and/or interacting in a similar manner to the vehicles represented by UEs 106D and 106E. Various embodiments of vehicles communicating in the network illustrated in FIG. 1 are disclosed, for example, in the context of vehicle-to-everything (V2X) communications, particularly communications specified by certain versions of the 3GPP standard.

2 illustrates an example user equipment 106 (e.g., one of UEs 106A-106N) in communication with a base station 122 and an access point 112, according to some embodiments. UE 106 may have both cellular and non-cellular communication capabilities (e.g., BLUETOOTH™, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device. It can be a device that has it all. UE 106 may include a processor configured to execute program instructions stored in memory. UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or additionally, UE 106 may be configured to perform any of the method embodiments described herein, or any portion of any of the method embodiments described herein. It may include programmable hardware elements, such as an enable gate array (FPGA). UE 106 may be configured to communicate using any of a number of wireless communication protocols. For example, UE 106 may be configured to communicate using two or more of CDMA2000, LTE, LTE-A, NR, WLAN, or GNSS. Other combinations of wireless communication standards are also possible.

UE 106 may include one or more antennas for communicating using one or more wireless communication protocols (such as those previously mentioned above) according to one or more RAT standards. In some embodiments, UE 106 may share one or more portions of the receive chain and/or transmit chain between multiple wireless communication standards. The shared wireless communication device may include a single antenna or may include multiple antennas (e.g., for MIMO) to perform wireless communication. Alternatively, the UE 106 includes separate transmit and/or receive chains (e.g., including separate antennas and other wireless components) for each wireless communication protocol with which it is configured to communicate. can do. Alternatively, UE 106 may include one or more radios or wireless circuitry shared between multiple wireless communication protocols, and one or more radios used exclusively by a single wireless communication protocol. . For example, UE 106 may include wireless circuitry for communicating using either LTE or CDMA2000 1xRTT or NR, and separate wireless devices for communicating using Wi-Fi and BLUETOOTH ^™ , respectively. You can. Other configurations are also possible.

Figure 3 - Block diagram of an example UE

3 illustrates a block diagram of an example UE 106 according to some embodiments. As shown, UE 106 may include a system on chip (SOC) 300 that may include various elements/components for various purposes. For example, as shown, SOC 300 includes processor(s) 302 that can execute program instructions for UE 106, and processor(s) 302 that can perform graphics processing and provide display signals to display 360. It may include a display circuit unit 304 that can be displayed. Processor(s) 302 may also receive addresses from processor(s) 302 and store those addresses in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory). 310) and/or display circuitry 304, wireless circuitry 330, connector I/F 320. , and/or may be coupled to other circuits or devices, such as display 360. MMU 340 may be configured to perform memory protection and page table conversion or setup. In some embodiments, MMU 340 may be included as part of processor(s) 302.

As shown, SOC 300 may be coupled to various other circuits of UE 106. For example, UE 106 may include various types of memory (e.g., NAND flash 310), a connector interface 320 (e.g., for coupling to a computer system), and a display 360. ), and may include wireless communication circuitry (e.g., for LTE, LTE-A, NR, CDMA2000, BLUETOOTH ^™ , Wi-Fi, GPS, etc.). The UE device 106 may use at least one antenna (e.g., 335a) and possibly multiple antennas (e.g., antennas 335a, 335b) to perform wireless communications with base stations and/or other devices. ) may be included. Antennas 335a and 335b are shown as an example, and UE device 106 may include fewer or more antennas. Overall, one or more antennas are collectively referred to as antenna(s) 335. For example, UE device 106 may use antenna(s) 335 to perform wireless communications with the assistance of wireless circuitry 330. As mentioned above, a UE may be configured to communicate wirelessly using multiple wireless communication standards in some embodiments.

As further described herein, the UE 106 (and/or the base station 102) may implement at least methods for the UE 106 to transmit reference signals in accordance with various embodiments disclosed herein. It may include hardware and software components for The processor(s) 302 of the UE device 106 may perform any of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). It can be configured to implement some or all of it. In other embodiments, processor(s) 302 may be configured as a programmable hardware element, such as a field programmable gate array (FPGA), or as an application specific integrated circuit (ASIC). Moreover, processor(s) 302 may include other components as shown in FIG. 3 to implement communication by UE 106 to transmit reference signals in accordance with various embodiments disclosed herein. Can be coupled to and/or interact with them. Specifically, processor(s) 302 may be coupled to other components as shown in FIG. 3 to facilitate UE 106 to communicate in a manner that attempts to optimize RAT selection and/ Or you can interact with them. Processor(s) 302 may also implement various other applications and/or end-user applications running on UE 106.

In some embodiments, wireless circuitry 330 may include separate controllers dedicated to controlling communications for various respective RATs and/or RAT standards. For example, as shown in FIG. 3, wireless circuitry 330 includes a Wi-Fi controller 356, a cellular controller (e.g., LTE and/or NR controller) 352, and a BLUETOOTH™ controller 354. and, according to at least some embodiments, one or more or all of these controllers may include respective integrated circuits (e.g., processor(s) 302) that communicate with each other and the SOC 300 (e.g., processor(s) 302). Briefly, it can be implemented as ICs or chips). For example, the Wi-Fi controller 356 may communicate with the cellular controller 352 over a cell-ISM link or a WCI interface, and/or the BLUETOOTH controller 354 may communicate with the cellular controller (352) over a cell-ISM link. 352), etc. Although three separate controllers are illustrated within wireless circuitry 330, other embodiments may utilize fewer or more similar controllers for a variety of different RATs and/or RAT standards that may be implemented in UE device 106. You can have them. For example, at least one example block diagram illustrating some embodiments of cellular controller 352 is shown in FIG. 5 and will be described further below.

Figure 4 - Block diagram of an exemplary base station.

Figure 4 illustrates a block diagram of an example base station 102 according to some embodiments. Note that the base station in Figure 4 is only one example of a possible base station. As shown, base station 102 may include processor(s) 404 that can execute program instructions for base station 102. Processor(s) 404 also receives addresses from processor(s) 404 and stores those addresses to locations within memory (e.g., memory 460 and read-only memory (ROM) 450). It may be coupled to a memory management unit (MMU) 440, which may be configured to convert, or to other circuits or devices.

Base station 102 may include at least one network port 470. Network port 470 may be coupled to a telephone network and configured to provide a plurality of devices, such as UE devices 106, access to the telephone network as described in FIGS. 1 and 2 above. . Network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, eg, a cellular service provider's core network. The core network may provide mobility-related services and/or other services to a plurality of devices, such as UE devices 106. In some cases, network port 470 may be coupled to a telephone network through a core network, and/or the core network may be used to provide telephone network connectivity (e.g., between different UE devices serviced by a cellular service provider). Network can be provided.

Base station 102 includes at least one antenna 434a and possibly multiple antennas (e.g., antennas 434a, 434b) to perform wireless communications with mobile devices and/or other devices. exemplified by ) may include. Antennas 434a and 434b are shown as an example, and base station 102 may include fewer or more antennas. Overall, one or more antennas, which may include antenna 434a and/or antenna 434b, are collectively referred to as antenna 434 or antenna(s) 434. Antenna(s) 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices 106 via wireless circuitry 430 . Antenna(s) 434 communicates with wireless communication device 430 through communication chain 432. Communication chain 432 may be a receive chain, a transmit chain, or both. Wireless circuitry 430 may be designed to communicate via a variety of wireless telecommunication standards, including but not limited to LTE, LTE-A, 5G-NR (NR), WCDMA, CDMA2000, etc. Processor(s) 404 of base station 102 may, for example, execute program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) to cause base station 102 to: Can be configured to implement any or all of the methods described herein for communicating with a UE device transmitting reference signals as disclosed. Alternatively, processor(s) 404 may be configured as programmable hardware element(s), such as a field programmable gate array (FPGA), or as an application specific integrated circuit (ASIC), or a combination thereof. For certain RATs, such as Wi-Fi, base station 102 may be designed as an access point (AP), in which case network port 470 may be connected to a wide area network and/or local area network(s). For example, it may include at least one Ethernet port, and the wireless communication device 430 may be designed to communicate according to the Wi-Fi standard. Base station 102 may operate according to various methods as disclosed herein to communicate with mobile devices transmitting reference signals in accordance with various embodiments disclosed herein.

Figure 5 - Exemplary cellular communications circuitry

FIG. 5 illustrates an example simplified block diagram illustrating a cellular controller 352 in accordance with some embodiments. The block diagram of cellular communications circuitry in Figure 5 is merely an example of a possible cellular communications circuit; Different RATs may include or be coupled to sufficient antennas to perform uplink activities using separate antennas, or fewer antennas that may be shared between multiple RATs, for example. Note that other circuits, such as ringed circuits, are also possible. According to some embodiments, cellular communications circuitry 352 may be included in a communications device, such as communications device 106 described above. As mentioned above, communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop), among other devices. , a laptop, or a portable computing device), a tablet, and/or a combination of devices.

Cellular communications circuitry 352 may be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 335a, 335b, and 336 as shown. In some embodiments, cellular communications circuitry 352 may include (e.g., communicatively; directly or indirectly) dedicated processors and/or wireless communications devices for multiple RATs. may include one or more receive chains (eg, a first receive chain for LTE and a second receive chain for 5G NR) that are coupled. For example, as shown in FIG. 5 , cellular communication circuitry 352 may include a first modem 510 and a second modem 520 . The first modem 510 may be configured for communication according to a first RAT, for example LTE or LTE-A, and the second modem 520 may be configured for communication according to a second RAT, for example 5G NR. It can be configured for communication according to:

As shown, first modem 510 may include one or more processors 512 and memory 516 in communication with the processors 512 . Modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuitry for transmitting and receiving wireless signals. For example, RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, receive circuitry 532 may communicate with downlink (DL) front end 550, which may include circuitry for receiving wireless signals via antenna 335a.

Similarly, second modem 520 may include one or more processors 522 and memory 526 in communication with processors 522 . Modem 520 may communicate with RF front end 540. The RF front end 540 may include circuitry for transmitting and receiving wireless signals. For example, RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, receive circuitry 542 may communicate with DL front end 560, which may include circuitry for receiving wireless signals via antenna 335b.

In some embodiments, switch 570 may couple transmit circuitry 534 to uplink (UL) front end 572. Additionally, switch 570 may couple transmit circuitry 544 to UL front end 572. UL front end 572 may include circuitry for transmitting wireless signals via antenna 336. Accordingly, when cellular communications circuitry 352 receives instructions to transmit according to a first RAT (e.g., as supported via first modem 510), switch 570 ) may be switched to a first state allowing signals to be transmitted (e.g., via a transmit chain including transmit circuitry 534 and UL front end 572) according to the first RAT. Similarly, when cellular communications circuitry 352 receives instructions to transmit in accordance with a second RAT (e.g., as supported via second modem 520), switch 570 instructs the second modem (e.g., 520 may be switched to a second state allowing signals to be transmitted (e.g., via a transmit chain including transmit circuitry 544 and UL front end 572) according to the second RAT.

As described herein, first modem 510 and/or second modem 520 may include hardware and software components to implement any of the various features and techniques described herein. there is. Processors 512, 522 are configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). It can be. Alternatively (or additionally), processors 512, 522 may be configured as programmable hardware elements, such as a field programmable gate array (FPGA), or as an application specific integrated circuit (ASIC). Alternatively (or additionally), processors 512, 522, together with one or more of other components 530, 532, 534, 540, 542, 544, 550, 570, 572, 335, 336, It may be configured to implement some or all of the features described herein.

Additionally, as described herein, processors 512, 522 may include one or more components. Accordingly, processors 512 and 522 may include one or more integrated circuits (ICs) configured to perform the functions of processors 512 and 522. Additionally, each integrated circuit may include circuitry (eg, first circuitry, second circuitry, etc.) configured to perform the functions of the processors 512 and 522.

In some embodiments, cellular communications circuitry 352 may include only one transmit/receive chain. For example, cellular communications circuitry 352 may not include modem 520, RF front end 540, DL front end 560, and/or antenna 335b. As another example, cellular communications circuitry 352 may not include modem 510, RF front end 530, DL front end 550, and/or antenna 335a. In some embodiments, cellular communications circuitry 352 may also not include switch 570 and RF front end 530 or RF front end 540 may be connected to UL front end 572, e.g. You can communicate directly.

Device-to-device and sidelink communications

Device-to-device (D2D) communication refers to user equipment devices (UEs) communicating directly with each other without passing data through a base station (BS) or other higher level network infrastructure. D2D communication plays an important role in improving the coverage and transmission capacity of cellular communications. One example of D2D communication was provided above with respect to FIG. 1 , where UEs 106D and 106E may represent vehicles that communicate directly with each other. Various embodiments of vehicles communicating with each other as illustrated in FIG. 1 may be within the context of vehicle-to-everything (V2X) communications, encompassing D2D communications such as communications specified by certain versions of the 3GPP standard. D2D-enabled cellular networks can prepare D2D users to share spectrum resources in two different ways. In-band D2D communications may occur over licensed spectrum, while out-of-band D2D communications may occur over unlicensed spectrum. In-band D2D is divided into two categories: the underlay category, where D2D users share the same frequency resources used by cellular users, and the overlay category, where both network-based communications and D2D communications use orthogonal spectrum resources. It can be further divided into categories. With the increasing number of cellular users, accommodating all users within the limited available spectrum and provisioning wide bandwidths for high data rate applications such as online gaming, video sharing, etc. has become a challenge. One way to improve the energy efficiency of wireless networks involves the use of relay nodes or relay UEs. Instead of one long hop from one node to another, various UEs can operate as strategically placed/positioned relays to convert a single long hop into two or more shorter hops. Although the operation of relays is greatly affected by path loss models and environmental conditions, it has proven to be effective in reducing path loss and improving D2D communications.

D2D communication, such as cellular wireless communication, sidelink communication (also referred to as communication over a PC5 link, when PC5 link refers to a sidelink) refers to a communication mechanism between devices that does not pass through a base station, e.g. , it is not delivered through eNB/gNB. In other words, devices communicate with each other without requiring communication to be facilitated by a base station. It is in this sense that devices can be said to communicate directly with each other. Accommodation of such communication between devices (or between UEs/PUEs) involves a physical layer design featuring minimal design changes over previous implementations.

Side link positioning

Device positioning, eg, determining the position/geolocation of a mobile device, has become an essential part of wireless communications. Various protocols and services have been introduced to aid device positioning. For example, the radio resource location services (LCS) protocol (RRLP) has been used in cellular networks to exchange messages between a mobile device and a Serving Mobile Location Center (SMLC) to provide geolocation information (SMLC is typically It is a network element that resides in the base station controller and calculates the network-based location of mobile devices). Similarly, ProSe (Proximity Services) is a D2D technology that allows mobile devices to detect and communicate directly with each other. ProSe relies on sidelink communications for direct connectivity between devices and offers several distinct advantages, including better scalability, manageability, privacy, security, and battery-efficiency.

Sidelink positioning has been discussed for inclusion in the 3GPP standard and is likely to be incorporated in 3GPP Release 18 (Rel-18). The sidelink positioning function has the potential to support ranging (e.g., distance measurements between mobile devices or UEs communicating over the sidelink) and estimation of absolute coordinates (using sidelink signals from multiple UEs). there is. Although the topic has been discussed extensively, system (eg, architecture) aspects have not been described in detail.

Embodiments described herein include, but are not limited to, extensions/enhancements to the current LCS architecture incorporating sidelink positioning, extensions/enhancements to the ProSe architecture incorporating sidelink positioning, and/or extensions/enhancements to the V2X architecture. It relates to various aspects of the proposed non-limiting sidelink positioning architecture (SPA).

Sidelink positioning (e.g., as defined within the 3GPP standard) is expected to make provisions for sidelink positioning reference signals (sidelink PRSs) and corresponding sidelink PRS measurements. To provide adequate support for sidelink positioning, the following higher layer aspects of sidelink positioning may be considered:

Full message call flow;

is it;

discovery;

competency negotiation;

Sidelink ΠΡΣ transmit triggering; and/or

Measurement triggering.

Extension of ProSe architecture

3GPP standards (e.g., TS 23.304; Figure 4.2.1-2) provide an overview of the current ProSe architecture. Additionally, as detailed in 3GPP standards (e.g., TS 23.304; Figures 6.3.2.1-1 and 6.3.2.1-2), there are currently two signaling models for ProSe discovery, Model A and Model B. exists. According to Model A, a notifying UE transmits a notification message that can be monitored by one or more additional UEs to discover the notifying UE. According to Model B, a discovering UE may transmit a solicitation message that can be detected by one or more discovered UEs, and the discovered UEs may in turn transmit a response message to the discovering UE.

Various embodiments of extensions of the ProSe architecture for sidelink positioning can support UE-based positioning in both in-coverage and out-of-coverage modes. The authorization procedure to use sidelink positioning can be performed while in-coverage, and authorization is also valid when the UE is subsequently out-of-coverage.

An example call flow for sidelink positioning could be as follows, with proposed extensions to the ProSe architecture underlined below:

Authorization process (to use sidelink positioning):

o UEs that support sidelink positioning shall indicate this capability in the Non-Access Layer (NAS) Registration Request message for Access and Mobility Management Function (AMF) (e.g. in the “5GMM Capability Information Element” according to 3GPP TS 24.501) can, and one of the (currently) reserved bits is designated to indicate “sidelink positioning” capability ;

o If the UE is authorized to use sidelink positioning (based on its subscription), the AMF may indicate this authorization to the UE, e.g. in a NAS Registration Accept message ;

Discovery procedure (to discover candidate UEs for sidelink positioning):

o A ProSe discovery procedure with improved indication of/for sidelink positioning may be used; Both Model A and Model B ProSe discovery options may be supported;

o Model A:

(according to 3GPP TS 24.554) A UE sending a ProSe PC5 discovery notification message may indicate support for sidelink positioning in the message ;

The monitoring UE receiving the notification message learns that it (the monitoring UE) can use sidelink positioning with the UE (sending the discovery notification message);

o Model B:

UE1 (discoverer) may send a ProSe PC5 Discovery Solicitation message indicating support for sidelink positioning in the message ;

If UE2 (the discovered UE) supports sidelink positioning, UE2 (the discovered UE) may send a ProSe PC5 Discovery Response message indicating support for sidelink positioning ;

Hereby, both UE1 and UE2 determine that they can use sidelink positioning between them;

UE1 establishes PC5-RRC connection with UE2;

Capability Information Exchange:

o UE1 indicates its sidelink positioning capabilities and configuration (e.g. sidelink PRS bandwidth) in the UECapabilityEnquirySidelink information element (IE) sent to UE2;

o UE2 indicates its sidelink positioning capabilities and configuration (e.g. sidelink PRS bandwidth) in the UECapabilityInformationSidelink IE sent to UE1;

Measurements:

o UE1 requests UE2 to send a sidelink PRS using RRCReconfigurationSidelink IE;

o UE1 performs sidelink PRS measurements (with one or more UEs) and calculates its relative position with respect to one or more UEs.

The procedures defined above make it possible to estimate relative positioning (or ranging) between two or more UEs. To support absolute location (eg, coordinates), ranging with multiple UEs (eg, at least three UEs) with known coordinates may be used. At least two options for communicating UE coordinates can be defined as follows:

Uses PC5-RRC signaling and specific IEs, such as UECapabilityEnquirySidelink and UECapabilityInformationSidelink, to communicate coordinates;

Communicate coordinates using ProSe messages, such as ProSe Direct Link Modify Request/Accept and ProSe Direct Link Keepalive Request/Response IEs .

Extension of V2X architecture

3GPP standards (e.g., TS 23.287; Figure 4.2.1.1-1) provide an overview of the current V2X architecture. It should be noted that the V5 and V1 interfaces are not specified in the 3GPP standard (the V5 interface is defined by the European Telecommunications Standards Institute (ETSI), while the V1 interface is the reference point between the V2X application server and the V2X application server within the UE. am).

Various embodiments of extensions of the V2X architecture for sidelink positioning can support UE-based positioning in both in-coverage and out-of-coverage modes. The authorization procedure to use sidelink positioning can be performed while in-coverage, and authorization is also valid when the UE is subsequently out-of-coverage.

An example call flow for sidelink positioning could be as follows, with suggested extensions to the V2X architecture underlined below:

Authorization process (to use sidelink positioning):

o Option 1:

A UE supporting sidelink positioning indicates this capability in the NAS registration request message (e.g. according to TS 24.501) for AMF, e.g. in the "5GMM capability information element" (e.g. according to TS 24.501), where the (currently) reserve One of the bits may be designated to indicate “sidelink positioning” capability ;

If the UE is authorized to use sidelink positioning (based on its subscription), the AMF may indicate this to the UE in the NAS Registration Accept message ;

o Option 2:

Represents sidelink positioning capabilities by V2X application servers via V1 reference points (outside the scope of 3GPP standards);

Discovery procedure (to discover candidate UEs for sidelink positioning via V5 interface ):

o The V2X application protocol can be used over the V5 interface (e.g., ETSI Intelligent Transport System, ITS, protocol) to transmit information indicating UE sidelink positioning capabilities ;

o Option 1 - Society of Automotive Engineers International Basic Safety Messages may be used ;

o Option 2 - ETSI ITS Collaborative Awareness Basic Service (ETSI EN 302 637-2) may be used .

o UE1 establishes PC5-RRC connection with UE2;

o Capability Information Exchange:

UE1 indicates its sidelink positioning capabilities and configuration (eg sidelink PRS bandwidth) in the UECapabilityEnquirySidelink IE sent to UE2;

UE2 indicates its sidelink positioning capabilities and configuration (eg sidelink PRS bandwidth) in the UECapabilityInformationSidelink IE sent to UE1;

o Measurements:

UE1 requests UE2 to send a sidelink PRS using RRCReconfigurationSidelink IE;

UE1 performs sidelink PRS measurements (with one or more UEs) and calculates its relative position with respect to one or more UEs.

Since both SAE and ETSI ITS V2X application protocols already support the transmission of absolute coordinates (e.g., reference point IE of the ETSI ITS Cooperative Awareness Base Service as disclosed in ETSI EN 302 637-2), ranging and absolute Both location estimates can be supported.

Extension of LCS architecture

3GPP standards (e.g., TS 23.273; Figure 4.2.2-1) provide an overview of the current LCS architecture. Additionally, 3GPP standards (e.g., TS 23.273; Figure 6.1.2-1) describe the Mobile End Location Request (MT-LR) procedure, which includes a UE positioning sub-procedure.

Various embodiments of the extension of the LCS architecture for sidelink positioning may introduce updated UE positioning sub-procedures and support UE-based positioning in in-coverage mode. However, in certain cases, some out-of-coverage scenario(s) with UE-based positioning may be supported.

1st approach

When both UEs participating in sidelink positioning are in-coverage, an extension of the LCS architecture can incorporate UE-type roadside units (RSUs) that transmit sidelink PRSs. An example call flow for sidelink positioning is illustrated in Figure 6 and can operate as follows with the proposed extensions to the LCS architecture underlined below. For example, it should be noted that “NRPPa” refers to “NR Positioning Protocol A”, as disclosed in 3GPP specifications (e.g., TS 38.455).

At 620, a location management function, such as LMF 609, may perform NRPPa transmit receive point (TRP) capability transfer information exchange with one or more base stations and/or TRPs, such as base stations 102a-d. The NRPPa TRP capability transfer information exchange may carry and/or exchange sidelink positioning reference signal (PRS) capability information between the LMF and TRPs. Additionally, at 622, LMF 609 may perform LTE Positioning Protocol (LPP) capability transfer with a UE, such as UE 106. The LPP capability transfer may carry and/or include sidelink PRS capability information, e.g., LMF 609 may exchange sidelink PRS capability information with UE 106. Additionally, LMF 609 may transmit a NRPPa positioning information request 624 to base station 102a. NRPPa positioning information request 624 may include (and/or convey) a request for sidelink PRS configuration, such as bandwidth, for example. At 626, base station 102a may determine resources for UE 106, such as uplink sounding reference signal (SRS) resources and/or sidelink PRS resources. Base station 102a may transmit UE PRS configuration 628 to UE 106. The UE PRS configuration message 628 may be a radio resource control (RRC) sidelink PRS configuration message. The UE PRS configuration message 628 may include resources for the sidelink PRS and/or an indication of resources. Additionally, base station 102a may transmit a NRPPa positioning information response 630 to LMF 609. NRPPa Positioning Information Response 630 may include and/or carry/indicate information regarding sidelink PRS configuration, such as bandwidth. Additionally, LMF 609 may transmit a NRPPa Positioning Activation Request 632 to base station 102a. NRPPa Positioning Activation Request 632 may include and/or return/indicate a request to initiate sidelink PRS transmission. Base station 102a may then send a PRS activation message 634 to UE 106. The PRS Activation message 634 may be a Medium Access Control (MAC) Control Element (CE) that may indicate activation of a sidelink PRS transmission. At 636, UE 106 may perform sidelink measurements. For example, UE 106 may exchange (e.g., transmit and/or receive) sidelink PRSs with one or more neighboring UEs and/or other sidelink devices, such as RSUs. UE 106 may report measurement results to LMF 609, for example, based on the exchange of sidelink PRSs. In some cases, UE 106 may perform sidelink measurements in a similar manner to measurements performed in the context of a call flow described above for extensions of the ProSe architecture. Additionally, if and/or when network-based UE-assisted positioning is supported, the UE(s) may report sidelink PRS measurements to the LMF, for example using LPP. LMF 609 may transmit a NRPPa positioning deactivation request 638 to base station 102a. NRPPa Positioning Deactivation Request 638 may deactivate and/or be used to deactivate sidelink PRS transmissions at the UE. In some cases, for example, when NRPPa Positioning Deactivation Request 638 is not used to deactivate sidelink PRS transmissions at the UE, base station 102a may send a PRS signal to indicate/indicate deactivation of sidelink PRS transmissions. A deactivation message 640 may be transmitted to the UE. In some cases, PRS deactivation message 640 may be a MAC CE indicating deactivation of sidelink PRS transmissions.

In some cases, the example call flow for sidelink positioning illustrated in Figure 6 may correspond to the call flow as defined in the LCS architecture with the extensions to the LCS architecture underlined below.

Step 1 (corresponding to LPP capability transfer 622) - LTE Positioning Protocol (LPP) capability transfer - may carry sidelink PRS capability information ;

Step 2 (corresponding to message 624) - NRPPa Positioning Information Request - may return a request for sidelink PRS configuration (e.g., bandwidth) ;

Step 3a (corresponding to message 628) - RRC Sidelink PRS Configuration Message ;

Step 4 (corresponding to message 630) - NRPPa Positioning Information Response - may return information regarding sidelink PRS configuration (e.g., bandwidth);

Step 5a (corresponding to message 632) - NRPPa Positioning Activation Request - may return a request to initiate sidelink PRS transmission ;

Step 5b (corresponding to message 634) - Enable MAC CE Sidelink PRS Transmission ;

Following step 5c (e.g., corresponding to SL measurements 636), UEs may perform sidelink measurements (in a similar manner to measurements performed in the context of a call flow described above for extensions of the ProSe architecture). has exist ; Additionally, if network-based UE-assisted positioning is supported, UEs can use LPP to report sidelink PRS measurements to the Location Management Function (LMF) ;

Step 9 (corresponds to message 638) - Disable NRPPa Positioning - Optional: Can be used to disable UE sidelink PRS transmission, in which case step 10 below can be performed subsequently ;

Step 10 (corresponding to message 640) - Optional: If step 9 is performed, disable MAC CE sidelink PRS transmission (e.g., a command to disable transmission of sidelink PRSs) message .

Second approach

In contrast to the first approach, according to the second approach, the LMF communicates with the UE via a base station (e.g. gNB; via NRPPa and RRC/MAC CEs as detailed above for the first approach) Can communicate directly with the UE (e.g., via LPP). Specifically, steps 2-5 described above (e.g., corresponding to signaling 624-634 from FIG. 6) utilize the enhancement of the LPP RequestLocationInformation to carry sidelink PRS configuration and activation indications (information) to configure the LPP. It can be implemented using

For example, Figure 7 illustrates another example flow diagram for UE sidelink positioning based on an LCS architecture, according to some embodiments. At 720, a location management function, such as LMF 609, may perform NRPPa transmit receive point (TRP) capability transfer information exchange with one or more base stations and/or TRPs, such as base stations 102a-d. The NRPPa TRP capability transfer information exchange may carry and/or exchange sidelink positioning reference signal (PRS) capability information between the LMF and TRPs. Additionally, at 722, LMF 609 may perform LTE Positioning Protocol (LPP) capability transfer with a UE, such as UE 106. The LPP capability transfer may carry and/or include sidelink PRS capability information, e.g., LMF 609 may exchange sidelink PRS capability information with UE 106. Additionally, LMF 609 may send a positioning information request 724 to UE 106. Positioning information request 724 may include (and/or return) a request for sidelink PRS configuration, e.g., bandwidth, e.g., positioning information request 724 may include sidelink PRS configuration and activation indication (information). It may be and/or include an LPP RequestLocationInformation that returns a . The UE 106 may determine resources, such as uplink sounding reference signal (SRS) resources and/or sidelink PRS resources, based on information in the positioning information request 724. Additionally, LMF 609 may send a positioning activation request 726 to UE 106. Positioning Activation Request 726 may include and/or return/indicate a request to initiate sidelink PRS transmission. At 730, UE 106 may perform sidelink measurements. For example, UE 106 may exchange (e.g., transmit and/or receive) sidelink PRSs with one or more neighboring UEs and/or other sidelink devices, such as RSUs. UE 106 may report measurement results to LMF 609, for example, based on the exchange of sidelink PRSs. In some examples, UE 106 may perform sidelink measurements in a manner similar to measurements performed in the context of a call flow described above for extensions of the ProSe architecture. Additionally, if and/or when network-based UE-assisted positioning is supported, the UE(s) may report sidelink PRS measurements to the LMF, for example using LPP. LMF 609 may transmit a NRPPa positioning deactivation request 732 to base station 102a. NRPPa Positioning Deactivation Request 732 may deactivate and/or be used to deactivate sidelink PRS transmissions at the UE. In some cases, for example, when NRPPa Positioning Deactivation Request 732 is not used to deactivate sidelink PRS transmissions at UE 106, base station 102a indicates/instructs deactivation of sidelink PRS transmissions. To do this, a PRS deactivation message 734 can be transmitted to the UE. In some cases, PRS deactivation message 734 may be a MAC CE indicating deactivation of sidelink PRS transmissions.

Third approach

The first approach detailed above is intended for in-coverage devices. For out-of-coverage devices that may not be able to communicate with the LMF, a deferred MT-LR (and potentially MO-LR) LCS procedure may be used. When the UE is in-coverage, the LCS client can initiate a deferred LCS procedure, indicating an event when location measurements need to be performed (e.g., when UE1, the first UE, approaches UE2, the second UE). there is. The third approach is for use with UE-based positioning, and the deferred MT-LR procedure can also be used with the first and second approaches detailed above.

Example call flows

Figure 8 illustrates an example block diagram of a call flow for sidelink positioning authorization, according to some embodiments. The call flow shown in FIG. 8 may be used with any of the systems, methods, or devices shown in the figures, among other devices. In various embodiments, some of the call flow elements shown may be performed simultaneously, in a different order than shown, or may be omitted. Additional call flows may also be performed as desired. As shown, the call flow may operate as follows.

At 802, a UE, such as UE 106, may transmit an indication that the UE supports sidelink positioning in a NAS registration request message for the access mobility and management function (AMF) of the core network. An indication that the UE supports sidelink positioning may be included in the 5G Mobility Management (5GMM) Capability Information Element (IE). In some cases, the 5GMM capability IE may include a bit designated to indicate sidelink positioning capability.

At 804, the UE may subsequently receive, from the AMF, an indication of authorization for the UE to use sidelink positioning. In some cases, an indication that the UE is authorized to use sidelink positioning may be received in response to a decision by the AMF. In some cases, an indication of authorization for the UE to use sidelink positioning may be received in the NAS Registration Accept message.

9 illustrates a block diagram of an example of a call flow for sidelink positioning using a discovery notification message, according to some embodiments. The call flow shown in FIG. 9 may be used with any of the systems, methods, or devices shown in the figures, among other devices. In various embodiments, some of the call flow elements shown may be performed simultaneously, in a different order than shown, or may be omitted. Additional call flows may also be performed as desired. As shown, the call flow may operate as follows.

At 902, a UE, such as UE 106, may transmit an indication that the UE supports sidelink positioning in a ProSe Sidelink Discovery Notification message.

At 904, sidelink positioning may subsequently be used with the UE. For example, sidelink positioning may be used with the UE in response to a ProSe sidelink discovery notification message indicating that the UE supports sidelink positioning.

Figure 10 illustrates a block diagram of an example of a call flow for sidelink positioning using a discovery solicitation message, according to some embodiments. The call flow shown in FIG. 10 may be used with any of the systems, methods, or devices shown in the figures, among other devices. In various embodiments, some of the call flow elements shown may be performed simultaneously, in a different order than shown, or may be omitted. Additional call flows may also be performed as desired. As shown, the call flow may operate as follows.

At 1002, a UE, such as UE 106, may transmit in a ProSe Sidelink Discovery Solicitation message an indication that the UE supports sidelink positioning.

At 1004, a UE may receive an indication from a neighboring UE, such as neighboring UE 106, in a ProSe Discovery Response message that another UE supports sidelink positioning. An indication that the neighboring UE supports sidelink positioning may be received in the ProSe Discovery Response message.

At 1006, the UE and the neighboring UE may, in response to the indications, determine that the UE and the neighboring UE will use sidelink positioning between them.

In some cases, a UE may establish a sidelink radio resource control (RRC) connection with a neighboring UE, such as in response to determining that the UE and the neighboring UE will use sidelink positioning between themselves. In some cases, the UE may transmit first information about the UE's sidelink positioning configuration and capabilities to a neighboring UE and receive, from the neighboring UE, second information about the neighboring UE's sidelink positioning configuration and capabilities. You can. The first information may be included in the UECapabilityEnquirySidelink information element (IE). The second information may be included in UECapabilityInformationSidelink IE. In some cases, a UE may request a neighboring UE to transmit a sidelink positioning reference signal (PRS). Additionally, the UE may perform sidelink PRS measurements based at least in part on the transmitted PRS and calculate the UE's relative position with respect to at least a neighboring UE. The relative position may be based at least in part on sidelink PRS measurements. In some cases, the UE may communicate coordinates corresponding to the UE's absolute position via one or more of sidelink radio resource control signaling or ProSe messages. In some cases, the coordinates are one of the CapabilityEnquirySidelink Information Element (IE), UECapabilityInformationSidelink IE, ProSe Direct Link Modification Request IE, ProSe Direct Link Modification Accept IE, ProSe Direct Link Keepalive Request IE, and/or ProSe Direct Link Keepalive Response IE. It can be included in one.

11 illustrates an example block diagram of a call flow for sidelink positioning using a V5 interface, according to some embodiments. The call flow shown in FIG. 11 may be used with any of the systems, methods, or devices shown in the figures, among other devices. In various embodiments, some of the call flow elements shown may be performed simultaneously, in a different order than shown, or may be omitted. Additional call flows may also be performed as desired. As shown, the call flow may operate as follows.

At 1102, a UE, such as UE 106, may transmit a first indication over the V5 interface that the UE supports sidelink positioning. In some cases, the first indication may be transmitted in and/or via a Society of Automotive Engineers (SAE) basic safety message. In some cases, the first indication may be transmitted in and/or via the European Telecommunications Standards Institute Intelligent Transport System Collaborative Awareness Basic Service message.

At 1104, the UE may receive a second indication, via the V5 interface, from a neighboring UE, such as neighboring UE 106, that the neighboring UE supports sidelink positioning. In some cases, the second indication may be transmitted in and/or via the SAE basic safety message. In some cases, the second indication may be received in and/or via a European Telecommunications Standards Institute Intelligent Transport System Collaborative Awareness Basic Service message.

At 1106, the UE, in response to the first indication and the second indication, may determine that the UE and the neighboring UE will use sidelink positioning between them.

In some cases, a UE may establish a sidelink radio resource control (RRC) connection with a neighboring UE, such as in response to determining that the UE and the neighboring UE will use sidelink positioning between themselves.

In some cases, a UE may transmit first information about the UE's sidelink positioning configuration and capabilities to a neighboring UE. Additionally, the UE may receive, from a neighboring UE, second information regarding the neighboring UE's sidelink positioning configuration and capabilities. Additionally, the UE may request neighboring UEs to transmit a sidelink positioning reference signal (PRS) using the RRC reconfiguration sidelink information element. Additionally, the UE may perform sidelink PRS measurements based at least in part on the transmitted PRS, such as calculating a relative position of the UE with respect to at least a neighboring UE based at least in part on the sidelink PRS measurements.

Figure 12 illustrates a block diagram of an example of a call flow for sidelink positioning in wireless communications, according to some embodiments. The call flow shown in FIG. 12 may be used with any of the systems, methods, or devices shown in the figures, among other devices. In various embodiments, some of the call flow elements shown may be performed simultaneously, in a different order than shown, or may be omitted. Additional call flows may also be performed as desired. As shown, the call flow may operate as follows.

At 1202, a UE, such as UE 106, may transmit first information indicating the UE's sidelink positioning reference signal (PRS) capabilities. In some cases, the UE may transmit first information in a Long Term Evolution (LTE) Positioning Protocol (LPP) communication.

At 1204, the UE may receive sidelink PRS configuration information for the UE. Sidelink PRS configuration information may be received in response to the UE transmitting first information. Sidelink PRS configuration information may be received in at least one of a radio resource control (RRC) sidelink PRS configuration message and/or LPP communication.

At 1206, the UE may transmit one or more sidelink PRSs according to sidelink PRS configuration information.

In some cases, the UE may receive sidelink PRS transmission activation via at least one of a medium access control (MAC) control element (CE) and/or LPP communication. Additionally, the UE may transmit one or more sidelink PRSs at least in part in response to receiving sidelink PRS transmission activation. In some cases, sidelink PRS transmission activation may be received at the MAC CE based at least in part on information regarding the UE's sidelink PRS configuration carried in a New Radio Positioning Protocol A (NRPPa) Positioning Information Response message. In such cases, the UE may receive sidelink PRS transmission activation at the MAC CE in response, at least in part, to an NRPPa Positioning Activation Request returning a request to initiate sidelink PRS transmission.

In some cases, the UE may receive sidelink PRS configuration information in an RRC sidelink PRS configuration message at least in part in response to an NRPPa information request carrying a request for sidelink PRS configuration.

In some examples, a UE may perform sidelink PRS measurements of sidelink PRSs transmitted by other UEs (eg, by neighboring UEs). In these cases, the UE may report sidelink PRS measurements to the Location Management Function (LMF) using and/or via LPP.

In some cases, the UE may receive a command in the MAC CE to deactivate sidelink PRS transmissions. In such cases, the UE may stop transmitting one or more PRSs at least partially in response to receiving the command.

In some cases, the UE may transmit an indication that the UE supports sidelink positioning in a Network Access Layer (NAS) Registration Request message for the Access Mobility and Management Function (AMF) of the core network. An indication that the UE supports sidelink positioning may be included in the 5G Mobility Management (5GMM) Capability Information Element (IE). In some cases, the 5GMM capability IE may include a bit designated to indicate sidelink positioning capability. Additionally, the UE may subsequently receive, from the AMF, an indication of authorization for the UE to use sidelink positioning. In some cases, an indication that the UE is authorized to use sidelink positioning may be received in response to a decision by the AMF. In some cases, an indication of authorization for the UE to use sidelink positioning may be received in the NAS Registration Accept message.

In some cases, the UE may transmit an indication in the ProSe Sidelink Discovery Notification message that the UE supports sidelink positioning. Additionally, sidelink positioning may subsequently be used with the UE. For example, sidelink positioning may be used with the UE in response to a ProSe sidelink discovery notification message indicating that the UE supports sidelink positioning.

In some cases, the UE may transmit an indication in the ProSe Sidelink Discovery Solicitation message that the UE supports sidelink positioning. Additionally, a UE may receive an indication from a neighboring UE, such as neighboring UE 106, in a ProSe Discovery Response message that another UE supports sidelink positioning. An indication that the neighboring UE supports sidelink positioning may be received in the ProSe Discovery Response message. Additionally, the UE and the neighboring UE may, in response to the indications, determine that the UE and the neighboring UE will use sidelink positioning between themselves. In some cases, a UE may establish a sidelink radio resource control (RRC) connection with a neighboring UE, such as in response to determining that the UE and the neighboring UE will use sidelink positioning between themselves. In some cases, the UE may transmit first information about the UE's sidelink positioning configuration and capabilities to a neighboring UE and receive, from the neighboring UE, second information about the neighboring UE's sidelink positioning configuration and capabilities. You can. The first information may be included in the UECapabilityEnquirySidelink information element (IE). The second information may be included in UECapabilityInformationSidelink IE. In some cases, a UE may request a neighboring UE to transmit a sidelink positioning reference signal (PRS). Additionally, the UE may perform sidelink PRS measurements based at least in part on the transmitted PRS and calculate the UE's relative position with respect to at least a neighboring UE. The relative position may be based at least in part on sidelink PRS measurements. In some cases, the UE may communicate coordinates corresponding to the UE's absolute position via one or more of sidelink radio resource control signaling or ProSe messages. In some cases, the coordinates are one of the CapabilityEnquirySidelink Information Element (IE), UECapabilityInformationSidelink IE, ProSe Direct Link Modification Request IE, ProSe Direct Link Modification Accept IE, ProSe Direct Link Keepalive Request IE, and/or ProSe Direct Link Keepalive Response IE. It can be included in one.

In some cases, the UE may transmit a first indication over the V5 interface that the UE supports sidelink positioning. In some cases, the first indication may be transmitted in and/or via a Society of Automotive Engineers (SAE) basic safety message. In some cases, the first indication may be transmitted in and/or via the European Telecommunications Standards Institute Intelligent Transport System Collaborative Awareness Basic Service message. The UE may receive a second indication, via the V5 interface, from a neighboring UE, such as neighboring UE 106, that the neighboring UE supports sidelink positioning. In some cases, the second indication may be transmitted in and/or via the SAE basic safety message. In some cases, the second indication may be received in and/or via a European Telecommunications Standards Institute Intelligent Transport System Collaborative Awareness Basic Service message. Additionally, the UE may, in response to the first indication and the second indication, determine that the UE and the neighboring UE will use sidelink positioning between them. In some cases, a UE may establish a sidelink radio resource control (RRC) connection with a neighboring UE, such as in response to determining that the UE and the neighboring UE will use sidelink positioning between themselves. In some cases, a UE may transmit first information about the UE's sidelink positioning configuration and capabilities to a neighboring UE. Additionally, the UE may receive, from a neighboring UE, second information regarding the neighboring UE's sidelink positioning configuration and capabilities. Additionally, the UE may request neighboring UEs to transmit a sidelink positioning reference signal (PRS) using the RRC reconfiguration sidelink information element. Additionally, the UE may perform sidelink PRS measurements based at least in part on the transmitted PRS, such as calculating a relative position of the UE with respect to at least a neighboring UE based at least in part on the sidelink PRS measurements.

It is well understood that use of personally identifiable information should be subject to generally recognized privacy policies and practices that meet or exceed industry or government requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and processed to minimize the risks of unintended or unauthorized access or use, and the nature of the authorized use should be clearly indicated to users.

Embodiments of the invention may be implemented in any of a variety of forms. For example, in some embodiments, the invention may be implemented as a computer-implemented method, a computer-readable memory medium, or a computer system. In other embodiments, the invention may be realized using one or more custom-designed hardware devices, such as ASICs. In other embodiments, the invention may be realized using one or more programmable hardware elements, such as FPGAs.

In some embodiments, a non-transitory computer-readable memory medium (e.g., a non-transitory memory element) may be configured to store program instructions and/or data, where the program instructions are executed by a computer system. Once done, cause the computer system to perform a method, e.g., any of the method embodiments described herein, or any combination of method embodiments described herein, or any method embodiments described herein. perform any subset of any of the following, or any combination of such subsets.

In some embodiments, a device (e.g., a UE) may be configured to include a processor (or set of processors) and a memory medium (or memory element), where the memory medium stores program instructions, and the processor configured to read and execute program instructions from a memory medium, wherein the program instructions include any of the various method embodiments described herein (or any combination of the method embodiments described herein, or is executable to implement any subset of any of the method embodiments described in, or any combination of such subsets. The device may be realized in any of a variety of forms.

Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be construed to encompass all such variations and modifications.

Claims (20)

As a user equipment device (UE),
at least one antenna;
at least one radio, wherein the at least one radio is configured to perform cellular communications using at least one radio access technology (RAT); and
one or more processors coupled to the at least one wireless communication device, wherein the one or more processors and the at least one wireless communication device are configured to perform communications,
The one or more processors allow the UE to:
transmit first information indicating a sidelink positioning reference signal (PRS) capability of the UE;
receive sidelink PRS configuration information for the UE, wherein the sidelink PRS configuration information for the UE is received in response to transmission of the first information;
A UE configured to transmit one or more sidelink PRSs according to the sidelink PRS configuration information. According to paragraph 1,
The sidelink PRS configuration information for the UE is:
Radio Resource Control (RRC) sidelink PRS configuration message; or
A UE, received via at least one of Long Term Evolution (LTE) Positioning Protocol (LPP) communications. According to paragraph 1,
The one or more processors allow the UE to:
A UE further configured to receive sidelink PRS transmission activation, wherein the one or more sidelink PRSs are transmitted at least in part in response to receiving the sidelink PRS transmission activation. According to paragraph 3,
Activating the sidelink PRS transmission,
Media Access Control (MAC) Control Element (CE); or
A UE, received via at least one of Long Term Evolution (LTE) Positioning Protocol (LPP) communications. According to paragraph 3,
The sidelink PRS transmission activation is based at least in part on information regarding the sidelink PRS configuration of the UE carried in a New Radio Positioning Protocol A (NRPPa) Positioning Information Response message to a medium access control (MAC) control element (CE). Received from UE. According to clause 5,
The one or more processors allow the UE to:
UE further configured to receive activation of the sidelink PRS transmission at the MAC CE in response at least in part to an NRPPa positioning activation request returning a request to initiate sidelink PRS transmission. According to paragraph 1,
The sidelink PRS configuration information for the UE is in a radio resource control (RRC) sidelink PRS configuration message in response, at least in part, to a New Radio Positioning Protocol A (NRPPa) information request carrying a request for sidelink PRS configuration. Received, UE. According to paragraph 1,
The one or more processors:
perform sidelink PRS measurements of sidelink PRSs transmitted by other UEs;
The UE is further configured to report the sidelink PRS measurements to a location management function (LMF) using Long Term Evolution (LTE) Positioning Protocol (LPP) based communication. According to paragraph 1,
The one or more processors allow the UE to:
At a medium access control (MAC) control element (CE), receive a command to disable sidelink PRS transmissions;
UE further configured to stop transmitting the one or more PRSs at least in part in response to receiving the command. According to paragraph 1,
UE, wherein the first information is transmitted in Long Term Evolution (LTE) Positioning Protocol (LPP) communication. As a device,
Memory; and
At least one processor in communication with the memory,
The at least one processor generates instructions to transmit first information indicating sidelink positioning reference signal (PRS) capability;
Radio Resource Control (RRC) sidelink PRS configuration message; or
In response to transmission of the first information via at least one of Long Term Evolution (LTE) Positioning Protocol (LPP) communications, receive sidelink PRS configuration information associated with the device;
An apparatus configured to generate instructions for transmitting one or more sidelink PRSs according to the sidelink PRS configuration information. According to clause 11,
The at least one processor,
Generate instructions for sending an indication of support for sidelink positioning to an access and mobility management function (AMF) in a non-access layer (NAS) registration request message;
and receive, from the AMF, an indication of authorization to use sidelink positioning based on a determination that use of sidelink positioning is authorized, the indication being received via a NAS registration acceptance message. According to clause 12,
The indication of support for sidelink positioning is included in a 5G Mobility Management (5GMM) capability information element (IE), wherein the 5GMM capability IE includes bits designated to indicate sidelink positioning capability. According to clause 11,
The at least one processor,
The apparatus further configured to generate instructions for transmitting an indication of support for sidelink positioning in a Proximity Services (ProSe) sidelink discovery notification message. A method for sidelink positioning in wireless communications, comprising:
A user equipment device (UE),
Transmitting first information indicating sidelink positioning reference signal (PRS) capability of the UE;
Receiving sidelink PRS configuration information for the UE, wherein the sidelink PRS configuration information for the UE is received in response to transmission of the first information; and
Transmitting one or more sidelink PRSs according to the sidelink PRS configuration information. According to clause 15,
The UE,
Transmitting, in a Proximity Services (ProSe) sidelink discovery solicitation message, a first indication that the UE supports sidelink positioning;
In response from a neighboring UE, receiving a second indication via a ProSe Discovery Response message that the neighboring UE supports sidelink positioning;
In response to the first indication and the second indication, determining to use sidelink positioning with the neighboring UE; and
The method further comprising exchanging sidelink positioning configuration and capabilities with the neighboring UE via UECapabilityEnquirySidelink information elements (IEs). According to clause 16,
The UE,
requesting the neighboring UE to transmit a sidelink positioning reference signal (PRS);
performing sidelink PRS measurements based at least in part on the transmitted PRS;
calculating a relative position of the UE relative to at least the second UE based at least in part on the sidelink PRS measurements; and
Communicating coordinates corresponding to the absolute position of the UE through one or more of sidelink radio resource control signaling or ProSe messages, the coordinates comprising:
CapabilityEnquirySidelink Information Element (IE);
UECapabilityInformationSidelink IE;
ProSe Direct Link Modification Request IE;
ProSe Direct Link Edit Accept IE;
ProSe Direct Link Keepalive Request IE; or
A method included in at least one of the ProSe direct link keepalive response IE. According to clause 15,
The UE,
Via the V5 interface, support for sidelink positioning via at least one of the Society of Automotive Engineers (SAE) basic safety messages or the European Telecommunications Standards Institute Intelligent Transport Systems cooperative awareness basic service messages. transmitting a first indication of;
Receiving, from a neighboring UE via the V5 interface, a second indication that the neighboring UE supports sidelink positioning via at least one of a SAE basic safety message or a European Telecommunications Standards Association Intelligent Transport Systems Collaboration Awareness basic service message;
In response to the first indication and the second indication, determining to use sidelink positioning with the neighboring UE; and
The method further comprising establishing a sidelink radio resource control (RRC) connection with the neighboring UE in response to the decision to use sidelink positioning with the neighboring UE. According to clause 18,
The UE,
The method further comprising exchanging sidelink positioning configuration and capabilities with the neighboring UE. According to clause 19,
The UE,
requesting the neighboring UE to transmit a sidelink PRS using a radio resource control (RRC) reconfiguration sidelink information element;
performing sidelink PRS measurements based at least in part on the transmitted PRS; and
Based at least in part on the sidelink PRS measurements, calculating a relative position of the UE at least relative to the neighboring UE.

Images