Response time-based management for SL positioning resources
By transmitting QoS configuration files and adjusting resource pool parameters in 5G NR side link positioning sessions, the problem of difficult response time and accuracy between UEs is solved, the efficiency and accuracy of positioning information are improved, and the efficiency of resource use is achieved. sex.
Patent Information
- Application Number
- CN202380035641.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-29
- Filing Date
- 2023-03-17
- Publication Date
- 2024-12-03
AI Technical Summary
In 5G NR wireless communication system, in a side link (SL) positioning session, user equipment (UE) finds difficulty meeting response time and accuracy requirements, resulting in the time and accuracy of positioning measurements that cannot effectively meet the desired requirements.
By delivering quality of service (QoS) profiles between UEs, determine whether the response time requirements are met, and adjust resource pool parameters according to the satisfaction, such as using dedicated positioning resource pools or competition-based resource pools, adjusting the sensing type and physical layer Send parameters to ensure the response time and accuracy of the positioning session.
It realizes meeting the response time and accuracy requirements in the 5G NR side link positioning session, improves the efficiency and accuracy of positioning information provision, and ensures resource usage efficiency and positioning accuracy among UEs.
Smart Images

Figure CN119072979A_ABST
Abstract
Description
[0001] Related Applications
[0002] This application claims the benefit of Greek Application No. 20220100354, filed on April 29, 2022, entitled “RESPONSE TIME BASED MANAGEMENTFOR SL POSITIONING RESOURCES,” which is assigned to the assignee of this application and is incorporated herein by reference in its entirety. Background Art 1. Technical Field
[0003] The present disclosure relates generally to the field of wireless communications, and more particularly to determining the location of a user equipment (UE) using radio frequency (RF) signals.
[0004] 2. Related technologies
[0005] In a data communication network, various positioning techniques may be used to determine the position of a mobile device (referred to herein as a UE). Some of these positioning techniques may involve determining distance and / or angle information of RF signals received by one or more other UEs that are communicatively coupled to the data communication network. In the fifth generation (5G) wireless standard referred to as New Radio (NR), direct communication between UEs (including the transmission of RF signals for positioning) may be referred to as a side link (SL). Positioning sessions between UEs may be conducted to perform positioning measurements using SL RF signals, and the UEs may coordinate such SL positioning sessions to ensure efficient use of bandwidth and other wireless resources. Summary of the invention
[0006] An example method for managing response time in a positioning session conducted between a first user equipment (UE) and a second UE via a side link (SL) according to the present disclosure may include: transmitting a first message including a quality of service (QoS) profile from the first UE to the second UE, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session. The method may also include receiving a second message from the second UE at the first UE, wherein the second message includes an indication of whether the second UE can meet the response time requirement. The method may also include determining, using the first UE, a resource pool parameter for the positioning session, wherein the resource pool parameter is based at least in part on the indication of whether the second UE can meet the response time requirement. The method may also include transmitting a third message including the resource pool parameter from the first UE to the second UE.
[0007] An example method of managing response time in a positioning session conducted between a first user equipment (UE) and a second UE via a side link (SL) according to the present disclosure may include: receiving, at the second UE, a first message from the first UE including a quality of service (QoS) profile, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session. The method may also include transmitting a second message from the second UE to the first UE, wherein the second message includes an indication of whether the second UE can meet the response time requirement. The method may also include receiving, at the second UE, from the first UE a third message including a resource pool parameter for the positioning session, wherein the resource pool parameter is based at least in part on the indication of whether the second UE can meet the response time requirement.
[0008] An example first UE for managing response time in a positioning session conducted via a side link (SL) between a first user equipment UE and a second UE according to the present disclosure may include: a transceiver, a memory, and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to transmit a first message including a quality of service (QoS) profile to the second UE via the transceiver, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session. The one or more processors may be further configured to: receive a second message from the second UE via the transceiver, wherein the second message includes an indication of whether the second UE can meet the response time requirement. The one or more processors may be further configured to: determine a resource pool parameter for the positioning session, wherein the resource pool parameter is at least partially based on the indication of whether the second UE can meet the response time requirement. The one or more processors may be further configured to transmit a third message including the resource pool parameter to the second UE via the transceiver.
[0009] An example second UE for managing response time in a positioning session conducted via a side link (SL) between a first user equipment (UE) and a second UE according to the present disclosure may include: a transceiver, a memory, and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to receive a first message including a quality of service (QoS) profile from the first UE via the transceiver, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session. The one or more processors may be further configured to: transmit a second message to the first UE via the transceiver, wherein the second message includes an indication of whether the second UE can meet the response time requirement. The one or more processors may be further configured to: receive a third message including a resource pool parameter for the positioning session from the first UE via the transceiver, wherein the resource pool parameter is at least partially based on the indication of whether the second UE can meet the response time requirement.
[0010] This Summary is neither intended to identify key features or essential features of the claimed subject matter nor is it intended to be used alone to determine the scope of the claimed subject matter. This subject matter should be understood by reference to appropriate portions of the entire specification of the present disclosure, any or all of the drawings, and each claim. The foregoing and other features and examples will be described in more detail in the following specification, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1 is a diagram of a positioning system according to an embodiment.
[0012] Figure 2 is a diagram of a fifth generation (5G) new radio (NR) positioning system, which illustrates a positioning system implemented within a 5G NR communication system (e.g., Figure 1 implementation scheme of a positioning system).
[0013] FIG. 3A to FIG. 3C is a simplified diagram of a scenario in which sidelink positioning may be used to determine the location of a target user equipment (UE).
[0014] Figure 4 is a call flow diagram illustrating establishment of a positioning session between a target UE and an anchor UE according to an embodiment.
[0015] Figure 5 is a call flow diagram illustrating a process that may be used to update parameters during a positioning session according to an embodiment.
[0016] Figure 6 is a call flow diagram illustrating another process that may be used to update positioning session parameters during a positioning session according to an embodiment.
[0017] Figure 7 is a flowchart of a method for managing response time in a positioning session between a first UE and a second UE via a SL according to an implementation scheme.
[0018] Figure 8 is a flowchart of another method of managing response time in a positioning session between a first UE and a second UE via a SL according to an embodiment.
[0019] Fig. 9 is a block diagram of an implementation of a UE that may be utilized in implementations as described herein.
[0020] Similar reference numerals in the various drawings indicate similar elements according to certain example implementations. In addition, multiple instances of an element can be indicated by adding a letter or hyphen and a second numeral after the first numeral of the element. For example, multiple instances of element 110 can be indicated as 110-1, 110-2, 110-3, etc. or 110a, 110b, 110c, etc. When only the first numeral is used to refer to such an element, any instance of the element should be understood (for example, element 110 in the previous example will refer to elements 110-1, 110-2 and 110-3 or to elements 110a, 110b and 110c). DETAILED DESCRIPTION
[0021] The following description is directed to certain specific implementations for the purpose of describing the innovative aspects of each embodiment. However, one of ordinary skill in the art will readily recognize that the teachings herein can be applied in a variety of different ways. The described specific implementations can be implemented in any device, system, or network capable of sending and receiving radio frequency (RF) signals according to any communication standard, such as any of the following: the Institute of Electrical and Electronics Engineers (IEEE) 802.15.4 standard for ultra-wideband (UWB), the IEEE 802.11 standard (including those identified as Technical standards), Standard, Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), GSM / General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Terrestrial Trunked Radio (TETRA), Wideband CDMA (W-CDMA), Evolution-Data Optimized (EV-DO), 1xEV-DO, EV-DO Revision A, EV-DO Revision B, High Rate Packet Data (HRPD), High Speed Packet Access (HSPA), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolved High Speed Packet Access (HSPA+), Long Term Evolution (LTE), Advanced Mobile Phone System (AMPS), or other known signals for communicating within a wireless, cellular or Internet of Things (IoT) network, such as a system utilizing 3G, 4G, 5G, 6G or further implementations thereof.
[0022] As used herein, "RF signals" include electromagnetic waves that transmit information through the space between a transmitter (or transmitting device) and a receiver (or receiving device). As used herein, a transmitter may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of each RF signal through multiple channels or paths, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal.
[0023] Additionally, unless otherwise noted, references to "reference signals," "positioning reference signals," "reference signals for positioning," and the like may be used to refer to signals used to locate user equipment (UE). As described in greater detail herein, such signals may include any of a variety of signal types, but may not necessarily be limited to positioning reference signals (PRS) as defined in relevant wireless standards.
[0024] The position determination of the UE may be based at least in part on measurements of signals sent and / or received by the UE via a sidelink (SL). In some cases, it may be desirable to perform these measurements within a desired time range (e.g., a "response time") and / or with a desired accuracy. However, given the available resources for performing these measurements in a SL positioning session, the UE may not be able to meet the time (and / or accuracy) requirements. The embodiments herein for providing response time-based management allow a UE (e.g., a target UE and / or an anchor UE) to adjust certain parameters that may enable the use of different resources, which in turn may allow the UE to meet the time (and / or accuracy) requirements. Additional details regarding such embodiments are provided after the discussion of related techniques.
[0025] Figure 1 is a simplified illustration of a positioning system 100 according to an embodiment, wherein a mobile device 105, a location server 160, and / or other components of the positioning system 100 can use the techniques provided herein to provide response time-based management of SL positioning resources for positioning of the mobile device 105. The techniques described herein can be implemented by one or more components of the positioning system 100. The positioning system 100 may include: a mobile device 105; one or more satellites 110 (also referred to as spacecraft (SV)) for a global navigation satellite system (GNSS) such as a global positioning system (GPS), GLONASS, Galileo, or BeiDou; a base station 120; an access point (AP) 130; a location server 160; a network 170; and an external client 180. In general, the positioning system 100 can estimate the location of the mobile device 105 based on RF signals received by and / or transmitted from the mobile device 105 and the known locations of other components (e.g., GNSS satellites 110, base stations 120, APs 130) that send and / or receive RF signals. Additional details about specific location estimation techniques are discussed below.
[0026] It should be noted that Figure 1Only a generalized illustration of the various components is provided, any or all of which may be utilized as appropriate, and each component may be repeated as needed. Specifically, although only one mobile device 105 is illustrated, it should be understood that many mobile devices (e.g., hundreds, thousands, millions, etc.) may utilize the positioning system 100. Similarly, the positioning system 100 may include more than one mobile device 105. Figure 1 100. The illustrated connections connecting the various components in the positioning system 100 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. In addition, the components may be rearranged, combined, separated, replaced and / or omitted according to the desired functionality. In some embodiments, for example, the external client 180 may be directly connected to the location server 160. Those of ordinary skill in the art will recognize many modifications to the illustrated components.
[0027] Depending on the desired functionality, network 170 may include any one of a variety of wireless and / or wired networks. Network 170 may, for example, include any combination of public and / or private networks, local area networks and / or wide area networks, etc. In addition, network 170 may utilize one or more wired and / or wireless communication technologies. In some embodiments, network 170 may include, for example, a cellular or another mobile network, a wireless local area network (WLAN), a wireless wide area network (WWAN), and / or the Internet. Examples of network 170 include long-term evolution (LTE) wireless networks, fifth-generation (5G) wireless networks (also referred to as new radio (NR) wireless networks or 5GNR wireless networks), Wi-Fi WLAN, and the Internet. LTE, 5G, and NR are wireless technologies defined or being defined by the Third Generation Partnership Project (3GPP). Network 170 may also include more than one network and / or more than one type of network. In a wireless cellular network (e.g., LTE or 5G), mobile device 105 may be referred to as user equipment (UE).
[0028] The base station 120 and the access point (AP) 130 are communicatively coupled to the network 170. In some embodiments, the base station 120 may be owned, maintained and / or operated by a cellular network provider and may employ any of a variety of wireless technologies, as described herein below. Depending on the technology of the network 170, the base station 120 may include a node B, an evolved node B (eNodeB or eNB), a transceiver base station (BTS), a radio base station (RBS), an NRNodeB (gNB), a next generation eNB (ng-eNB), etc. In the case where the network 170 is a 5G network, the base station 120 as a gNB or ng-eNB may be part of a next generation radio access network (NG-RAN) that may be connected to a 5G core network (5GC). In view of the open radio access network (O-RAN) and / or virtualized radio access network (V-RAN or vRAN) in 5G or higher generation networks, the functions performed by the base station 120 in earlier generation networks (e.g., 3G and 4G) may be separated into different functional components (e.g., radio unit (RU), distributed unit (DU), and central unit (CU)) and layers (e.g., L1 / L2 / L3), which may be executed on different devices at different locations connected, for example, via fronthaul, midhaul, and backhaul connections. As described herein, a "base station" (or ng-eNB, gNB, etc.) may include any or all of these functional components. For example, AP 130 may include a Wi-Fi AP or AP or an AP with cellular capabilities (e.g., 4G LTE and / or 5G NR). Thus, mobile device 105 can transmit and receive information with network connectivity devices (such as location server 160) by accessing network 170 via base station 120 using first communication link 133. Additionally or alternatively, because AP 130 can also be communicatively coupled with network 170, mobile device 105 can communicate with network connectivity and Internet connectivity devices (including location server 160) using second communication link 135 or via one or more other mobile devices 145.
[0029] As used herein, the term "base station" may generally refer to a single physical transmission point or multiple co-located physical transmission points that may be located at a base station 120. A transmit receive point (TRP) (also referred to as a transmit / receive point) corresponds to this type of transmission point, and the term "TRP" may be used interchangeably with the terms "gNB," "ng-eNB," and "base station" herein. In some cases, a base station 120 may include multiple TRPs—for example, where each TRP is associated with a different antenna or different antenna array of the base station 120. As used herein, the transmit function of a TRP may be performed using a transmit point (TP), and / or the receive function of a TRP may be performed by a receive point (RP), which may be physically separate or different from the TP. That is, a TRP may include both a TP and an RP. A physical transmission point may include an antenna array of a base station 120 (for example, as in a multiple-input multiple-output (MIMO) system and / or where the base station employs beamforming). The term "base station" may additionally refer to multiple non-co-located physical transmission points, which may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transmission medium) or a remote radio head (RRH) (a remote base station connected to a serving base station).
[0030] As used herein, the term "cell" may generally refer to a logical communication entity for communicating with base station 120, and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) for distinguishing neighboring cells operating via the same or different carriers. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types that may provide access for different types of devices (e.g., machine type communication (MTC), narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), or other protocols). In some cases, the term "cell" may refer to a portion (e.g., an area) of a geographic coverage area in which the logical entity operates.
[0031] Satellites 110 may be used to locate mobile device 105 in one or more ways. For example, satellites 110 (also referred to as space vehicles (SVs)) may be part of a global navigation satellite system (GNSS), such as a global positioning system (GPS), GLONASS, Galileo, or BeiDou. Positioning using RF signals from GNSS satellites may include measuring multiple GNSS signals at a GNSS receiver of mobile device 105 to perform code-based and / or carrier-based positioning, which may be highly accurate. Additionally or alternatively, satellites 110 may be used for non-terrestrial network (NTN) based positioning, where satellites 110 may be functionally operable as a TRP (or multiple TPs) of a network (e.g., an LTE and / or NR network) and may be communicatively coupled with network 170. In particular, reference signals (e.g., PRS) sent by satellites 110 for NTN based positioning may be similar to those sent by base stations 120 and may be coordinated by location server 160. In some embodiments, satellites 110 used for NTN based positioning may be different from those used for GNSS based positioning.
[0032] The location server 160 may include a server and / or other computing device configured to determine an estimated location of the mobile device 105 and / or provide data (e.g., “assistance data”) to the mobile device 105 to facilitate location measurement and / or location determination by the mobile device 105. According to some embodiments, the location server 160 may include a Home Secure User Plane Location (SUPL) Location Platform (H-SLP), which may support the SUPL User Plane (UP) positioning solution defined by the Open Mobile Alliance (OMA), and may support location services for the mobile device 105 based on subscription information for the mobile device 105 stored in the location server 160. In some embodiments, the location server 160 may include a Discovery SLP (D-SLP) or an Emergency SLP (E-SLP). The location server 160 may also include an Enhanced Serving Mobile Location Center (E-SMLC), which uses a Control Plane (CP) positioning solution to support positioning of the mobile device 105 for LTE radio access of the mobile device 105. The location server 160 may also include a location management function (LMF) that supports positioning of the mobile device 105 using a control plane (CP) positioning solution for NR or LTE radio access of the mobile device 105.
[0033] In the CP positioning solution, from the perspective of the network 170, the signaling for controlling and managing the positioning of the mobile device 105 can use existing network interfaces and protocols and be exchanged as signaling between the elements of the network 170 and with the mobile device 105. In the UP positioning solution, from the perspective of the network 170, the signaling for controlling and managing the positioning of the mobile device 105 can be exchanged between the location server 160 and the mobile device 105 as data (e.g., data transmitted using the Internet Protocol (IP) and / or the Transmission Control Protocol (TCP)).
[0034] As previously mentioned (and discussed in more detail below), the estimated position of the mobile device 105 can be based on measurements of RF signals transmitted from and / or received by the mobile device 105. Specifically, these measurements can provide information about the relative distances and / or angles of the mobile device 105 and one or more components in the positioning system 100 (e.g., GNSS satellites 110, APs 130, base stations 120). The estimated position of the mobile device 105 can be estimated geometrically (e.g., using multi-angle measurements and / or multilateration) based on the distance and / or angle measurements along with the known positions of the one or more components.
[0035] Although ground components such as AP 130 and base station 120 may be fixed, embodiments are not limited in this regard. Mobile components may be used. For example, in some embodiments, the location of mobile device 105 may be estimated based at least in part on measurements of RF signals 140 communicated between mobile device 105 and one or more other mobile devices 145 (the one or more other mobile devices may be mobile or fixed). As illustrated, the other mobile devices may include, for example, mobile phone 145-1, vehicle 145-2, static communication / positioning device 145-3, or other static and / or mobile devices capable of providing wireless signals for positioning mobile device 105, or combinations thereof. Wireless signals from mobile device 145 for positioning mobile device 105 may include using, for example, (including Bluetooth Low Energy (BLE)), IEEE 802.11x (e.g. ), ultra-wideband (UWB), IEEE 802.15x, or a combination thereof. The mobile device 145 may additionally or alternatively use non-RF wireless signals for positioning of the mobile device 105, such as infrared signals or other optical technologies.
[0036] Mobile devices 145 may include other mobile devices that are communicatively coupled to a cellular or other mobile network (e.g., network 170). When one or more other mobile devices 145 are used in the positioning determination of a particular mobile device 105, the mobile device 105 whose positioning is to be determined may be referred to as a "target mobile device" and each of the other mobile devices 145 used may be referred to as an "anchor mobile device". (In cellular / mobile broadband networks, the terms "anchor UE" and "target UE" may be used.) In order to make a positioning determination for a target mobile device, the corresponding positioning of the one or more anchor mobile devices may be known and / or determined jointly with the target mobile device. Direct communication between one or more other mobile devices 145 and mobile device 105 may include sidelinks and / or similar device-to-device (D2D) communication technologies. The sidelink defined by 3GPP is a form of D2D communication under cellular-based LTE and NR standards. UWB may be one such technology by which it can use measurements from one or more anchor devices (e.g., mobile devices 145) to facilitate the positioning of a target device (e.g., mobile device 105).
[0037] According to some embodiments, such as when the mobile device 105 includes and / or is incorporated into a vehicle, a form of D2D communication used by the mobile device 105 may include vehicle-to-everything (V2X) communication. V2X is a communication standard for vehicles to exchange information about the traffic environment with related entities. V2X may include vehicle-to-vehicle (V2V) communication between vehicles with V2X capabilities, vehicle-to-infrastructure (V2I) communication between vehicles and infrastructure-based equipment (commonly referred to as roadside units (RSUs)), vehicle-to-person (V2P) communication between vehicles and nearby people (pedestrians, cyclists and other road users), etc. In addition, V2X can use any of a variety of wireless RF communication technologies. For example, cellular V2X (CV2X) is a form of V2X that uses cellular-based communications in a direct communication mode defined by 3GPP, such as LTE (4G), NR (5G) and / or other cellular technologies. Figure 1The mobile device 105 illustrated in the figure may correspond to a component or device on a vehicle, RSU, or other V2X entity used to communicate V2X messages. In an embodiment in which V2X is used, the static communication / positioning device 145-3 (which may correspond to an RSU) and / or the vehicle 145-2 may therefore communicate with the mobile device 105 and may be used to determine the location of the mobile device 105 using techniques similar to those used by the base station 120 and / or AP 130 (e.g., using multi-angle and / or multilateration positioning). It may also be noted that according to some embodiments, the mobile device 145 (which may include a V2X device), the base station 120, and / or the AP 130 may be used together (e.g., in a WWAN positioning solution) to determine the location of the mobile device 105.
[0038] The estimated position of mobile device 105 may be used in various applications, such as to assist a user of mobile device 105 with direction finding or navigation or to assist another user (e.g., associated with external client 180) in locating mobile device 105. "Position" is also referred to herein as "position estimate," "estimated position," "position," "position estimation," "position determination," "estimated position," "position determination," or "determination." The process of determining a position may be referred to as "positioning," "position determination," "position determination," or the like. The position of mobile device 105 may include an absolute position of mobile device 105 (e.g., latitude and longitude, and possibly altitude) or a relative position of mobile device 105 (e.g., a position expressed as a distance north or south, east or west, and possibly above or below some other known fixed location (including, for example, the location of base station 120 or AP 130) or some other location (such as the location of mobile device 105 at some known previous time, or the location of mobile device 145 (e.g., another mobile device) at some known previous time). The location may be specified as a geodetic location including coordinates that may be absolute (e.g., latitude, longitude, and optionally altitude), relative (e.g., relative to some known absolute location), or local (e.g., X, Y, and optionally Z coordinates according to a coordinate system defined relative to a local area, such as a factory, warehouse, college campus, shopping mall, stadium, or convention center). The location may alternatively be a city location, and may then include one or more of a street address (e.g., including a country, state, county, city, road and / or street name or label, and / or road or street number) and / or a label or name of a place, a building, a portion of a building, a floor of a building, and / or a room within a building, etc. The location may also include an uncertainty or error indication, such as a horizontal and likely vertical distance that the location is expected to have error, or an indication of an area or volume (e.g., a circle or ellipse) within which the mobile device 105 is expected to be located with a certain confidence level (e.g., 95% confidence).
[0039] The external client 180 may be a web server or remote application that may have some association with the mobile device 105 (e.g., may be accessed by a user of the mobile device 105), or may be a server, application, or computer system that provides location services to some other user or users, which may include obtaining and providing the location of the mobile device 105 (e.g., to enable services such as friend or relative locating or child or pet location). Additionally or alternatively, the external client 180 may obtain the location of the mobile device 105 and provide it to emergency service providers, government agencies, etc.
[0040] Figure 2 A diagram of a 5G NR positioning system 200 is shown, illustrating an embodiment of a positioning system implementing 5G NR (which may correspond to at least a portion of a larger positioning system as described herein, such as Figure 1 Positioning system 100). The 5G NR positioning system 200 may be configured to determine the location of a user equipment (UE) 205 by using an access node to implement one or more positioning methods, and the access node may include NR Node B (gNB) 210-1 and 210-2 (collectively referred to as gNB 210 in this document), ng-eNB 214 and / or WLAN 216. The gNB 210 and / or ng-eNB 214 may correspond to a base station described elsewhere herein, and the WLAN 216 may correspond to one or more access points described elsewhere herein. Optionally, the 5G NR positioning system 200 may also be configured to determine the location of the UE 205 by using an LMF 220 (which may correspond to a location server described elsewhere herein) to implement one or more positioning methods. Here, the 5G NR positioning system 200 includes a UE 205, and components of a 5G NR network, including a next generation (NG) radio access network (RAN) (NG-RAN) 235 and a 5G core network (5GCN) 240. The 5G network may also be referred to as an NR network; the NG-RAN 235 may be referred to as a 5G RAN or an NR RAN; and the 5G CN 240 may be referred to as an NG core network.
[0041] The 5G NR positioning system 200 may also utilize information from satellites 207. As previously indicated, the satellites 207 may include GNSS satellites from a GNSS system such as the Global Positioning System (GPS) or a similar system such as GLONASS, Galileo, BeiDou, Indian Regional Navigation Satellite System (IRNSS). Additionally or alternatively, the satellites 207 may include NTN satellites that may be communicatively coupled with the LMF 220 and operable to serve as TRPs (or TPs) in the NG-RAN 235. As such, the satellites 207 may communicate with one or more gNBs 210.
[0042] It should be noted that Figure 2 Only a generalized illustration of the various components is provided, any or all of which may be utilized as appropriate, and each component may be repeated or omitted as desired. Specifically, although only one UE 205 is shown, it will be understood that many UEs (e.g., hundreds, thousands, millions, etc.) may utilize the 5G NR positioning system 200. Similarly, the 5G NR positioning system 200 may include a larger (or smaller) number of GNSS satellites 207, gNB 210, ng-eNB 214, wireless local area network (WLAN) 216, access and mobility management function (AMF) 215, external client 230, and / or other components. The connections shown connecting the various components in the 5G NR positioning system 200 include data and signaling connections, which may include additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. In addition, the components may be rearranged, combined, separated, replaced, and / or omitted according to the desired functionality.
[0043] UE 205 may include and / or be referred to as a device, a mobile device, a wireless device, a mobile terminal, a terminal, a mobile station (MS), a terminal (SET) enabled with secure user plane location (SUPL), or some other name. In addition, UE 205 may correspond to a cellular phone, a smart phone, a laptop computer, a tablet device, a personal data assistant (PDA), a navigation device, an Internet of Things (IoT) device, or some other portable or mobile device. Typically, although not necessarily, UE 205 may support the use of one or more radio access technologies (RATs) such as GSM, CDMA, W-CDMA, LTE, High Rate Packet Data (HRPD), IEEE802.11 Bluetooth, Worldwide Interoperability for Microwave Access (WiMAX TM), 5G NR (e.g., using NG-RAN 235 and 5GCN 240). UE 205 may also support wireless communications using WLAN 216, which (similar to one or more RATs as described elsewhere herein) may connect to other networks, such as the Internet. Using one or more of these RATs may allow UE 205 (e.g., via Figure 2 Elements of the 5G CN 240 not shown in the figure, or possibly via a Gateway Mobile Location Center (GMLC) 225) communicate with the external client 230 and / or allow the external client 230 (e.g., via GMLC225) to receive location information about the UE 205. Figure 2 The external client 230 may correspond to an external client as implemented in a 5G NR network or communicatively coupled with a 5G NR network.
[0044] UE 205 may include a single entity or may include multiple entities, such as in a personal area network in which a user may employ audio, video, and / or data I / O devices, and / or body sensors and separate wired or wireless modems. The estimate of the location of UE 205 may be referred to as location, location estimation, location determination, determination, orientation, orientation estimation, or orientation determination, and may conform to geodesy, thereby providing location coordinates (e.g., latitude and longitude) about UE 205, which may or may not include an altitude component (e.g., height above sea level; height above or below ground level, floor level, or basement level). Alternatively, the location of UE 205 may be expressed as a municipal location (e.g., a postal address or a designation of a certain point or smaller area in a building, such as a specific room or floor). The location of UE 205 may also be expressed as an area or volume (defined by geodesy or in municipal form) within which the UE 205 is expected to be located with a certain probability or confidence level (e.g., 67%, 95%, etc.). The position of the UE 205 may also be a relative position, including, for example, a distance and direction or relative X, Y (and Z) coordinates defined relative to some origin at a known location, which may be defined geodetically, in a municipal form, or by reference to a point, area, or volume indicated on a map, floor plan, or building plan. Unless otherwise indicated, the use of the term "position" in the description contained herein may include any of these variations. When calculating the position of the UE, local X, Y, and possibly Z coordinates are typically solved, and then the local coordinates are converted to absolute coordinates (e.g., with respect to latitude, longitude, and altitude above or below mean sea level) if necessary.
[0045] Figure 2The base stations in the NG-RAN 235 shown in FIG. 1 may correspond to base stations described elsewhere herein and may include gNBs 210. Pairs of gNBs 210 in the NG-RAN 235 may be connected to each other (e.g., as shown in FIG. 1 ). Figure 2 The communication interface between the base stations (gNB 210 and / or ng-eNB 214) may be referred to as an Xn interface 237. Access to the 5G network is provided to the UE 205 via wireless communication between the UE 205 and one or more gNBs 210, which may use 5G NR to provide wireless communication access to the 5G CN 240 on behalf of the UE 205. The wireless interface between the base station (gNB 210 and / or ng-eNB 214) and the UE 205 may be referred to as an Uu interface 239. 5G NR radio access may also be referred to as NR radio access or 5G radio access. Figure 2 , it is assumed that the serving gNB for UE 205 is gNB 210-1, but other gNBs (e.g., gNB 210-2) may act as serving gNBs if UE 205 moves to another location, or may act as secondary gNBs to provide additional throughput and bandwidth to UE 205.
[0046] Figure 2 The base stations in the NG-RAN 235 shown in the figure may additionally or alternatively include a next generation evolved Node B (also referred to as ng-eNB) 214. The ng-eNB 214 may be connected to one or more gNBs 210 in the NG-RAN 235—e.g., directly or indirectly via other gNBs 210 and / or other ng-eNBs. The ng-eNB 214 may provide LTE radio access and / or evolved LTE (eLTE) radio access to the UE 205. Figure 2Some of the gNBs 210 (e.g., gNB 210-2) and / or ng-eNBs 214 in the 5G CN 240 may be configured to function as positioning-only beacons that may transmit signals (e.g., positioning reference signals (PRS)) and / or may broadcast assistance data to assist in positioning the UE 205, but may not receive signals from the UE 205 or from other UEs. Some of the gNBs 210 (e.g., gNB 210-2 and / or another gNB not shown) and / or ng-eNBs 214 may be configured to function as detection-only nodes that may scan for signals containing, for example, PRS data, assistance data, or other location data. Such detection-only nodes may not transmit signals or data to the UE, but may transmit signals or data (relating to, for example, PRS, assistance data, or other location data) to other network entities (e.g., one or more components of the 5G CN 240, an external client 230, or a controller), which may receive and store the data or use the data to locate at least the UE 205. It should be noted that although in Figure 2 Only one ng-eNB 214 is shown in FIG, but some embodiments may include multiple ng-eNBs 214. Base stations (e.g., gNB 210 and / or ng-eNB 214) may communicate directly with each other via an Xn communication interface. Additionally or alternatively, the base station may communicate directly or indirectly with other components of the 5GNR positioning system 200 (such as LMF 220 and AMF 215).
[0047] The 5G NR positioning system 200 may also include one or more WLANs 216 that may be connected to a non-3GPP interworking function (N3IWF) 250 in the 5GCN 240 (e.g., in the case of an untrusted WLAN 216). For example, the WLAN 216 may support IEEE 802.11 Wi-Fi access for the UE 205 and may include one or more Wi-Fi APs (e.g., access points as described elsewhere herein). Here, the N3IWF 250 may be connected to other elements in the 5G CN 240, such as the AMF 215. In some embodiments, the WLAN 216 may support another RAT, such as Bluetooth. The N3IWF 250 may provide support for secure access of the UE 205 to other elements in the 5G CN 240 and / or may support interworking of one or more protocols used by the WLAN 216 and the UE 205 with one or more protocols used by other elements of the 5GCN 240 (such as the AMF 215). For example, the N3IWF 250 may support: IPSec tunnel establishment with the UE 205, termination of the IKEv2 / IPSec protocol with the UE 205, termination of the N2 and N3 interfaces with the 5G CN 240 for the control plane and the user plane, respectively, and relay of uplink (UL) and downlink (DL) control plane non-access stratum (NAS) signaling across the N1 interface between the UE 205 and the AMF 215. In some other embodiments, the WLAN 216 may be directly connected to elements in the 5G CN 240 (e.g., Figure 2 215) and not via the N3IWF 250. For example, a direct connection of the WLAN 216 to the 5GCN 240 may occur when the WLAN 216 is a trusted WLAN for the 5GCN 240 and may use a trusted WLAN interworking function (TWIF) ( Figure 2 It should be noted that although Figure 2 Only one WLAN 216 is shown in FIG. 2 , but some embodiments may include multiple WLANs 216 .
[0048] The access node may include any of a variety of network entities that enable communication between the UE 205 and the AMF 215. As mentioned, this may include a gNB 210, an ng-eNB 214, a WLAN 216, and / or other types of cellular base stations. However, an access node that provides the functionality described herein may additionally or alternatively include a cellular network entity that enables communication with the UE 205. Figure 2214, or WLAN 216.
[0049] In some embodiments, an access node (such as a gNB 210, ng-eNB 214, and / or WLAN 216) (alone or in combination with other components of the 5G NR positioning system 200) may be configured to: in response to receiving a request for location information from LMF 220, obtain a location measurement for an uplink (UL) signal received from UE 205 and / or obtain a DL location measurement from UE 205 for a downlink (DL) signal received by UE 205 from one or more access nodes. As mentioned, although Figure 2 The access nodes (gNB 210, ng-eNB 214, and WLAN 216) are depicted as being configured to communicate in accordance with 5G NR, LTE, and Wi-Fi communication protocols, respectively, but access nodes configured to communicate in accordance with other communication protocols may be used, such as, for example, a Node B using a Wideband Code Division Multiple Access (WCDMA) protocol for a Universal Mobile Telecommunications Service (UMTS) Terrestrial Radio Access Network (UTRAN), an eNB using an LTE protocol for an Evolved UTRAN (E-UTRAN), or an eNB using a LTE protocol for a WLAN. For example, in a 4G Evolved Packet System (EPS) that provides LTE wireless access to UE 205, the RAN may include an E-UTRAN, which may include base stations including eNBs that support LTE wireless access. The core network for the EPS may include an Evolved Packet Core (EPC). The EPS may then include the E-UTRAN plus the EPC, where Figure 2 , E-UTRAN corresponds to NG-RAN 235 and EPC corresponds to 5GCN 240. The methods and techniques described herein for obtaining the municipal location of UE 205 may be applicable to such other networks.
[0050] The gNB 210 and ng-eNB 214 may communicate with the AMF 215, which communicates with the LMF 220 for positioning functions. The AMF 215 may support the mobility of the UE 205, including cell changes and handovers of the UE 205 from an access node of a first RAT (e.g., a gNB 210, ng-eNB 214, or WLAN 216) to an access node of a second RAT. The AMF 215 may also be involved in supporting signaling connections with the UE 205 and possibly supporting data and voice bearers for the UE 205. The LMF 220 may support positioning the UE 205 using a CP positioning solution when the UE 205 accesses the NG-RAN 235 or the WLAN 216, and may support positioning procedures and methods, including UE-assisted / UE-based and / or network-based procedures / methods, such as Assisted GNSS (A-GNSS), Observed Time Difference of Arrival (OTDOA) (which may be referred to as Time Difference of Arrival (TDOA) in NR), Frequency Difference of Arrival (FDOA), Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DGNSS), Enhanced Cell ID (ECID), Angle of Arrival (AoA), Angle of Departure (AoD), WLAN positioning, Round Trip Signal Propagation Delay (RTT), Multi-Cell RTT, and / or other positioning procedures and methods. The LMF 220 may also process a location service request for the UE 205 received, for example, from the AMF 215 or from the GMLC 225. The LMF 220 may be connected to the AMF 215 and / or the GMLC 225. In some embodiments, the network (such as 5GCN 240) may additionally or alternatively implement other types of location support modules, such as an evolved serving mobile location center (E-SMLC) or a SUPL location platform (SLP). It should be noted that in some embodiments, at least a portion of the positioning functions (including determining the location of UE 205) can be performed at UE 205 (e.g., by measuring downlink PRS (DL-PRS) signals sent by wireless nodes (such as gNB 210, ng-eNB 214 and / or WLAN 216) and / or using assistance data provided to UE 205 by, for example, LMF 220).
[0051] The Gateway Mobile Location Center (GMLC) 225 may support location requests for the UE 205 received from the external client 230, and may forward such location requests to the AMF 215 for forwarding by the AMF 215 to the LMF 220. A location response (e.g., including a location estimate of the UE 205) from the LMF 220 may similarly be returned to the GMLC 225 directly or via the AMF 215, and the GMLC 225 may then return the location response (e.g., including the location estimate) to the external client 230.
[0052] A network exposure function (NEF) 245 may be included in the 5GCN 240. The NEF 245 may support secure exposure of capabilities and events regarding the 5GCN 240 and the UE 205 to the external client 230, which may therefore be referred to as an access function (AF) and may enable secure provisioning of information from the external client 230 to the 5GCN 240. The NEF 245 may connect to the AMF 215 and / or the GMLC 225 to obtain the location (e.g., municipal location) of the UE 205 and provide the location to the external client 230.
[0053] like Figure 2 As further illustrated in , LMF 220 may communicate with gNB 210 and / or with ng-eNB 214 using NR Positioning Protocol Annex (NRPPa) as defined in 3GPP Technical Specification (TS) 38.455. NRPPa messages may be passed between gNB 210 and LMF 220 and / or between ng-eNB 214 and LMF 220 via AMF 215. Figure 2 As further shown in , the LMF 220 and the UE 205 may communicate using the LTE Positioning Protocol (LPP) as defined in 3GPP TS 37.355. Here, LPP messages may be passed between the UE 205 and the LMF 220 via the AMF 215 and the serving gNB 210-1 or the serving ng-eNB 214 of the UE 205. For example, the LPP messages may be passed between the LMF 220 and the AMF 215 using messages for service-based operations (e.g., based on the Hypertext Transfer Protocol (HTTP)), and may be passed between the AMF 215 and the UE 205 using the 5G NAS protocol. The LPP protocol may be used to support positioning of the UE 205 using UE-assisted and / or UE-based positioning methods such as A-GNSS, RTK, TDOA, multi-cell RTT, AoD, and / or ECID. The NRPPa protocol may be used to support positioning of UE 205 using network-based positioning methods such as ECID, AoA, uplink TDOA (UL-TDOA) and / or may be used by LMF 220 to obtain location-related information from gNB 210 and / or ng-eNB 214, such as parameters defining DL-PRS transmissions from gNB 210 and / or ng-eNB 214.
[0054] In the case where the UE 205 accesses the WLAN 216, the LMF 220 may use NRPPa and / or LPP to obtain the location of the UE 205 in a manner similar to that just described for the UE 205 accessing the gNB 210 or ng-eNB 214. Thus, NRPPa messages may be passed between the WLAN 216 and the LMF 220 via the AMF 215 and the N3IWF 250 to support network-based positioning of the UE 205 and / or to pass other location information from the WLAN 216 to the LMF 220. Alternatively, NRPPa messages may be passed between the N3IWF 250 and the LMF 220 via the AMF 215 to support network-based positioning of the UE 205 based on location-related information and / or location measurements that are known or accessible to the N3IWF 250 and passed from the N3IWF 250 to the LMF 220 using NRPPa. Similarly, LPP and / or LPP messages may be communicated between UE 205 and LMF 220 via AMF 215, N3IWF 250, and serving WLAN 216 of UE 205 to support UE-assisted or UE-based positioning of UE 205 by LMF 220.
[0055] In the 5G NR positioning system 200, positioning methods may be classified as "UE-assisted" or "UE-based". This may depend on where the request to determine the position of the UE 205 originates. For example, if the request originates from the UE (e.g., from an application or "app" executed by the UE), the positioning method may be classified as UE-based. On the other hand, if the request originates from an external client 230, LMF 220, or other device or service within the 5G network, the positioning method may be classified as UE-assisted (or "network-based").
[0056] With UE-assisted positioning methods, UE 205 may obtain location measurements and transmit these measurements to a location server (e.g., LMF 220) for use in computing a location estimate for UE 205. For RAT-dependent positioning methods, the location measurements may include one or more of the following for one or more access points of gNB 210, ng-eNB 214, and / or WLAN 216: received signal strength indicator (RSSI), round trip signal propagation time (RTT), reference signal received power (RSRP), reference signal received quality (RSRQ), reference signal time difference (RSTD), time of arrival (TOA), AoA, receive time-transmit time difference (Rx-Tx), differential AoA (DAoA), AoD, or timing advance (TA). Additionally or alternatively, similar measurements may be made on sidelink signals sent by other UEs, which may be used as anchor points for positioning UE 205 if the positions of these other UEs are known. The position measurements may additionally or alternatively include measurements for a RAT-independent positioning method, such as GNSS (eg, GNSS pseudoranges with respect to GNSS satellites 207 , GNSS code phase, and / or GNSS carrier phase), WLAN, and the like.
[0057] Using the UE-based positioning method, UE 205 can obtain a position measurement (e.g., which can be the same or similar to the position measurement of the UE-assisted positioning method), and the position of UE 205 can be further calculated (e.g., with the aid of auxiliary data received from a location server such as LMF 220, SLP or broadcast by gNB 210, ng-eNB 214, or WLAN 216).
[0058] Using a network-based positioning method, one or more base stations (e.g., gNB 210 and / or ng-eNB 214), one or more APs (e.g., in WLAN 216), or N3IWF 250 can obtain location measurements (e.g., measurements of RSSI, RTT, RSRP, RSRQ, AOA, or TOA) of signals sent by UE 205, and / or can receive measurements obtained by UE 205 or, in the case of N3IWF250, by APs in WLAN 216, and can transmit these measurements to a location server (e.g., LMF 220) for use in calculating a position estimate for UE 205.
[0059] The positioning of UE 205 may also be classified as UL-based, DL-based, or DL-UL-based according to the type of signal used for positioning. For example, if the positioning is based only on signals received at UE 205 (e.g., from a base station or other UE), the positioning may be classified as DL-based. On the other hand, if the positioning is based only on signals sent by UE 205 (which may be received by, for example, a base station or other UE), the positioning may be classified as UL-based. DL-UL-based positioning includes positioning based on signals sent and received by UE 205, such as RTT-based positioning. Sidelink (SL)-assisted positioning includes signals communicated between UE 205 and one or more other UEs. According to some embodiments, the UL, DL, or DL-UL positioning described herein may be able to use SL signaling as a supplement or replacement for SL, DL, or DL-UL signaling.
[0060] Depending on the type of positioning (e.g., UL-based, DL-based, or DL-UL-based), the type of reference signal used may be different. For example, for DL-based positioning, these signals may include PRS (e.g., DL-PRS sent by a base station or SL-PRS sent by other UEs), which may be used for TDOA measurements, AoD measurements, and RTT measurements. Other reference signals that may be used for positioning (UL, DL, or DL-UL) may include: Sounding Reference Signal (SRS), Channel State Information Reference Signal (CSI-RS), Synchronization Signal (e.g., Synchronization Signal Block (SSB) Synchronization Signal (SS)), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Physical Sidelink Shared Channel (PSSCH), Demodulation Reference Signal (DMRS), etc. In addition, the reference signal may be sent in a Tx beam and / or received in an Rx beam (e.g., using beamforming techniques), which may affect angle measurements such as AoD and / or AoA.
[0061] FIG. 3A to FIG. 3C 3 is a simplified illustration of a scenario in which sidelink positioning may be used to determine the location of a target UE 305 according to some embodiments. One or more anchor UEs 310 may be used to transmit and / or receive reference signals via a sidelink. As shown, one or more base stations 320 (Uu interface) may also be used to determine positioning. However, it will be appreciated that the signals used for positioning of the UE 305 may vary depending on the desired functionality. More specifically, some types of positioning may utilize signals other than, for example, Figure 3A-3C Signals other than RTT / TDOA illustrated in .
[0062] Figure 3AThe diagram of illustrates a configuration in which positioning of a target UE 305 may include RTT and / or TDOA measurements between the target UE 305 and three base stations 320. In this configuration, the target UE 305 may be within the coverage of a DL and / or UL signal via a Uu connection with the base station 320. Additionally, an anchor UE 310 at a known location may be used to improve the position determination of the target UE 305 by providing an additional anchor. As illustrated, ranging may be performed between the target UE 305 and the anchor UE 310 by performing RTT measurements via a sidelink connection between the target UE 305 and the anchor UE 310.
[0063] Figure 3B The diagram of illustrates a configuration in which the positioning of the target UE 305 can be only sidelink (SL only) positioning / ranging. In this configuration, the target UE 305 can perform RTT measurements via a sidelink connection between multiple anchor UEs 310. In this example, the target UE 305 may not be in the UL coverage of the base station 320, and therefore each anchor UE 310 may report RTT measurement information to the network via a Uu connection between each anchor UE 310 and the base station 320. (In the case where the UE relays information between the remote UE and the base station, the UE may be referred to as a "relay" UE.) Such a scenario may exist when the target UE 305 has a weaker transmit power than the anchor UE 310 (for example, the target UE 305 includes a wearable device, and the anchor UE includes a larger cellular phone, an IOT device, etc.). In other scenarios in which the target UE 305 is within the UL coverage of the base station 320, the target UE 305 may report the RTT measurement directly to the base station 320. In some implementations, no base station 320 may be used, in which case one of the UEs (eg, one of the anchor UEs 310 or the target UE 305 ) may receive the RTT measurement information and determine the location of the target UE 305 .
[0064] Figure 3C 305. The diagram of exemplifies a configuration in which the positioning of the target UE 305 may include the target UE 305 and the anchor UE 310 receiving a reference signal (DL-PRS) from the base station 320 and the target UE 305 transmitting a reference signal (SL-PRS) to the anchor UE 310. The positioning of the target UE may be determined based on the known positions of the base station 320 and the anchor UE 310 and the time difference between the time when the anchor UE 310 receives the reference signal from the base station 320 and the time when the anchor UE 310 receives the reference signal from the target UE 305.
[0065] As previously discussed, sidelink positioning (e.g., SL-only positioning or Uu / SL positioning, such as FIG. 3A to FIG. 3CThe use of a resource pool (shown) for positioning may utilize a resource pool (RP-P) for positioning. The RP-P may be communicated to the UE via a sidelink configuration (e.g., using the techniques described below), and may specify a specific resource pool for sidelink reference signals in different scenarios. A resource pool includes a set of resources (e.g., frequency and time resources in an orthogonal frequency division multiplexing (OFDM) scheme used by 4G and 5G cellular technologies) that may be used to send RF signals via a sidelink for positioning. Each resource pool may also include a specific subcarrier spacing (SCS), a cyclic prefix (CP) type, a bandwidth (BW) (e.g., subcarriers, bandwidth portions, etc.), a time domain location (e.g., periodicity and slot offsets). The resource pool may include, for example, a Tx resource pool for "mode 1" sidelink positioning, where sidelink positioning is performed using one or more network-connected UEs, in which case the network-connected UEs may receive network-based resource allocations via a Uu interface with a base station (e.g., via downlink control information (DCI) or radio resource control (RRC)). Tx resource pools for "mode 2" sidelink positioning, where autonomous resource selection is performed by the UE in the absence of network-based resource allocation. The resource pools may also include Rx resource pools, which may be used in mode 1 or mode 2 sidelink positioning. Each RP-P configuration may be relayed via a physical sidelink control channel (PSCCH), which may retain one or more SL-PRS configurations. Each of the one or more SL-PRS configurations in the RP-P may include corresponding specific physical layer characteristics, such as the number of symbols, comb type, comb offset, number of subchannels, a certain channel size, and a starting resource block (RB). The RP-P configuration may also include sensing configuration, power control, and / or channel busy rate (CBR).
[0066] According to some embodiments, an exception RP-P may be specified and used in situations where it may not be expected or possible to perform side link positioning via an available resource pool of a non-exceptional RP-P for a side link. Such exceptions may include situations similar to situations that trigger the use of an exception resource pool for communication, such as situations where there may be physical layer problems before the UE completes and initiates a connection or during the handover of the UE. Like the non-exceptional RP-P for the side link, the exception RP-P for the side link may be configured or pre-configured and may be allocated or autonomously selected by the network (e.g., used in mode 1 or mode 2 side link positioning). In addition, according to some embodiments, the exception RP-P may be pre-configured, pre-loaded and / or hard-coded into UEs for different geographic regions or areas. For example, in the case of public safety, different countries may specify specific resources for the exception RP-P. The exception RP-P may be configured via a dedicated signaling (e.g., PC5) via the Uu interface and / or configured via a system information block (SIB). In some embodiments, the exception RP-P may be broadcast during the positioning session setup phase or discovery phase of the UE. Additionally or alternatively, resource reservation techniques may be used to assign or allocate exceptional RP-Ps.
[0067] There are two different approaches to allocating SL-PRS for use during a SL positioning session. The first approach includes semi-static configuration using pre-defined resources in a dedicated positioning resource pool (e.g., RP-P). The second approach includes dynamic configuration, where resource determination may be contention-based. When determining the resource periodicity for semi-static configuration, quality of service (QoS) parameters for positioning, such as response time (e.g., a specified delay budget for providing a position estimate), may be considered. For contention-based resource determination, current procedures provide little help to ensure that, for example, a positioning session is completed within a specified delay budget.
[0068] Embodiments address these and other issues by providing mechanisms that a target UE and an anchor UE can use to help ensure that the anchor UE can meet response time and / or other QoS parameters for a positioning session between the anchor UE and the target UE. These mechanisms include the use of QoS profiles and / or parameter adjustments by the target UE and / or the anchor UE. These mechanisms can be used during establishment of a positioning session between the target UE and the anchor UE, and / or can be used during the positioning session itself. Additional details are provided below.
[0069] Figure 4 4 is a call flow diagram illustrating a process 400 of establishing a positioning session between a target UE 410 and an anchor UE 420 according to an embodiment. (The target UE 410 and the anchor UE 420 may correspond to other places herein (including, for example, FIG. 3A to FIG. 3C) described above. Either or both of the target UE 410 and the anchor UE 420 may also generally correspond to Figure 2 User equipment 205 and / or Figure 1 )Here, the target UE 410 and the anchor UE 420 may perform a series of actions during the positioning session establishment 425 to prepare for the SL positioning session at box 430.
[0070] Here, process 400 may be initiated by target UE 410 and may include Figure 4 4, such as establishing a SL communication link, capability exchange, and / or other such common positioning establishment operations. The target UE 410 may initiate process 400 in response to a request for the location of the target UE 410 by the target UE 410 (e.g., by an application executed by the target UE 410), another device, or a network. In some cases, the target UE 410 may initiate positioning sessions with multiple anchor UEs, in which case process 400 may be replicated between the target UE 410 and each anchor UE.
[0071] During the positioning session establishment 425, the target UE 410 may provide a QoS profile to the anchor UE 420, as indicated by arrow 435. The QoS profile may include one or more QoS parameters for the positioning session, which may be based on the positioning requirements for the target UE 410. In general, the QoS profile may provide parameters related to the timing and / or accuracy requirements for the positioning session between the target UE 410 and the anchor UE 420.
[0072] For example, depending on the implementation, the QoS profile may specify a response time requirement, a horizontal accuracy requirement, a vertical accuracy requirement, a vertical coordinate request indicator, a speed request indicator, or a combination thereof. In this example, the response time requirement includes a deadline by which the anchor UE 420 is to provide positioning information (e.g., a final determination, but a first / early determination may also be specified). The horizontal accuracy requirement and the vertical accuracy requirement may include the maximum respective horizontal and vertical errors of the positioning information. The vertical coordinate request indicator and the speed request indicator may include Boolean values indicating whether the vertical coordinate or speed information is to be included in the positioning information provided by the anchor UE 420, respectively. In some implementations, the response time requirement may need to be met even if one or more of the accuracy requirements cannot be met.
[0073] At block 440, the anchor UE 420 may then determine whether it can meet the QoS profile requirements. For example, with respect to response time requirements, the anchor UE 420 may be involved in communications, other positioning sessions, and / or other engagements / operations that may limit the anchor UE's ability to provide positioning information within the response time. Thus, the anchor UE 420 may determine whether the QoS profile requirements can be met based at least in part on the capabilities (processing, bandwidth, etc.) of the anchor UE and other scheduling operations.
[0074] In response to the determination made at block 440, the anchor UE 420 may then provide an indication as to whether the QoS profile requirements may be met, as indicated at arrow 450. Depending on the desired functionality, the anchor UE 420 may provide an indication as to each QoS profile requirement (e.g., whether each QoS profile requirement may be met), or may provide an indication as to whether all QoS profile requirements may be met.
[0075] As indicated by block 460, the target UE 410 then determines resource pool parameters for the positioning session based on the indication provided by the anchor UE 420, which are then transmitted to the anchor UE 420, as indicated by arrow 470. These resource pool parameters may include, for example, the use of resources in a dedicated positioning resource pool (e.g., RP-P) and / or a contention-based pool, a sensing window positioning duration, a sensing type, or a combination thereof. According to some embodiments, the sensing type may include full sensing, partial sensing, or random selection, and the target UE 410 may also indicate some parameters to other anchor UEs participating in the positioning session. These parameters may include, for example, resource selection window / sensing parameters.
[0076] According to some embodiments, positioning session parameters (e.g., resource pool parameters) may be determined based on whether the anchor UE 420 is unable to meet one or more of the QoS profile requirements. Additionally or alternatively, the positioning session parameters may be adjusted during the positioning session if the anchor UE 420 determines that it is no longer able to meet one or more of the QoS profile requirements. More specifically, the determination of the resource pool parameters at block 460 may be based on an indication provided at arrow 450 during positioning session establishment 425, or the adjustment of the resource pool parameters may be made by the anchor UE 420 or the target UE 410 during the positioning session, such as Figure 5 and Figure 6 As shown, they will be discussed in more detail below.
[0077] Figure 5 4 is a call flow diagram illustrating a process 500 that may be used to update parameters during a positioning session according to an embodiment. Here, for example, the target UE 410 and the anchor UE 420 may have been in Figure 4Initial parameters are established in the manner shown in process 400 of , and a positioning session may be engaged. During the positioning session, anchor UE 420 may re-evaluate whether it can meet the response time provided by target UE 410 (e.g., as part of a QoS profile). This re-evaluation may occur periodically and / or may occur based on certain triggers (e.g., if available resources have changed due to other data / positioning efforts). At block 530, the anchor may determine (e.g., as a result of the re-evaluation) that the response time can be met for a longer period of time.
[0078] Thus, the anchor UE 420 may then provide an indication to the target UE 410 that the response time may be met longer, as indicated by arrow 540. According to some embodiments, the indication may include an indication of why the response time may be met longer, if feasible (e.g., full sensing takes too long, contention-based resources are not available, etc.) and / or an indication of updated resources that may be used.
[0079] After receiving the indication that the response time can be met longer, the target UE may then update the parameters for the positioning session, as indicated at block 550, and then provide the updated parameters to the anchor UE 420, as indicated at arrow 560. The updated parameters may be based at least in part on information provided by the anchor UE, if any, such as updated resource information, available bandwidth, etc. For operation in an unlicensed spectrum, the resource availability provided by the anchor UE 420 to the target UE 410 may also include a channel access success. The updated parameters may include, for example, a higher priority for the positioning session, a different resource selection strategy, a different physical (PHY) layer parameter configuration, or a combination thereof.
[0080] Different resource selection strategies may include, for example, changes in the type of sensing. For example, full sensing may be initially specified for a positioning session (e.g., as in Figure 4 470 ), but the UE may select partial or random sensing (the latter taking a different time than full sensing) based on the response time requirement and the elapsed time (e.g., if full sensing is no longer feasible in the remaining amount of time before the response time elapses).
[0081] Different PHY layer parameter configurations may include any of a variety of changes to the PHY layer transmissions used for the positioning session. For example, a transmission with a lower repetition factor (e.g., a lower repetition factor for a reference signal) and / or a smaller bandwidth may be selected to help meet response time constraints. For example, the anchor may not be able to ensure a 100 MHz channel for positioning, but may be able to ensure a 60 MHz channel. Similarly, the anchor UE may not be able to ensure four repetitions of the SL PRS, but may be able to ensure two repetitions. Other PHY layer transmission parameters may include the number of symbols used to transmit reference signal resources in an orthogonal frequency division multiplexing (OFDM) communication system, the number of reference signal resources in a resource set, and the like. Finally, based on Figure 5 In process 500, parameters of a SL positioning session between a target UE 410 and an anchor UE 420 may be initially estimated and / or subsequently adjusted (e.g., during the positioning session) to help ensure that the anchor UE 420 is able to meet response time requirements initially provided by the target UE 410 (e.g., as part of a QoS profile).
[0082] Figure 6 is a call flow diagram illustrating another process 600 that may be used to update positioning session parameters during a positioning session according to an embodiment. Figure 5 In the process 500, the target UE 410 and the anchor UE 420 may have Figure 4 Initial parameters are established in the manner shown in process 400 and a positioning session can be engaged. Figure 5 In contrast to process 500, anchor UE 420 may update the positioning session parameters. That is, after determining that the response time can no longer be met (as shown in block 630, similar to Figure 5 530), the anchor UE 420 may update the positioning parameters, as shown at block 650. The anchor UE 420 may then provide the updated parameters to the target UE 410, as shown by arrow 660.
[0083] Other aspects can be similar to Figure 5 For example, the anchor UE 420 may re-evaluate whether it can meet the response time provided by the target UE 410 at one or more times during the positioning session (e.g., periodically, based on certain triggers, etc.). The anchor UE 420 may then use the same information as previously provided about the target UE 410. Figure 5 The parameters for the positioning session may be updated using the same or similar considerations as described in process 500 of FIG. This may include updating priorities, resource selection strategies, PHY layer parameter configurations, or a combination thereof. For changes to the PHY layer transmit parameters, they may be indicated to the target UE 410 via a PSCCH or physical sidelink shared channel (PSSCH) message.
[0084] Figure 7 7 is a flow chart of a method 700 for managing response time in a positioning session between a first UE and a second UE via a SL according to an embodiment. Here, the first UE may correspond to a target UE, and the second UE may correspond to an anchor UE, such as Figures 4 to 6 The functionality of method 700 may reflect Figure 4 and Figure 5 Aspects of the process illustrated in . Figure 7 The components of the functions illustrated in one or more of the blocks shown in the figure may be performed by hardware and / or software components of the UE. Fig. 9 Example components of a UE are illustrated in FIG, and are described in more detail below.
[0085] At block 710, the functionality includes transmitting, from the first UE to the second UE, a first message including a quality of service (QoS) profile, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session. As previously indicated, the response time requirement may include a maximum delay (e.g., the delay may be about hundreds of milliseconds to several seconds, or greater) for providing positioning information (e.g., finalization). As indicated in the previously described embodiments, the QoS profile may include additional requirements. This may include, for example, a horizontal accuracy requirement, a vertical accuracy requirement, a vertical coordinate request indicator, a speed request indicator, or a combination thereof.
[0086] Means for performing the functions at block 710 may include bus 905, processor 910, wireless communication interface 930, sensor 940, memory 960, GNSS receiver 980, and / or other components of the UE, such as described in Fig. 9 Those exemplified in and described below.
[0087] At block 720, the functionality includes receiving, at the first UE, a second message from the second UE, wherein the second message includes an indication of whether the second UE can meet the response time requirement. As mentioned in the previously described embodiments, the receipt of the indication may occur in the positioning session establishment and / or during the positioning session itself. Thus, the indication may inform the first UE (e.g., the target UE) of what resource pool parameters to initially use for the positioning session and / or how the resource pool parameters should be adjusted during the positioning session. As previously described, items such as priority, sensing type, resource pool type, etc. may be selected based on whether the second UE (e.g., the anchor UE) can meet the response time requirement in the QoS profile.
[0088] Means for performing the functions at block 720 may include bus 905, processor 910, wireless communication interface 930, sensor 940, memory 960, GNSS receiver 980, and / or other components of the UE, such as described in Fig. 9 Those exemplified in and described below.
[0089] At block 730, the functionality includes determining, using the first UE, resource pool parameters for the positioning session, wherein the resource pool parameters are based at least in part on an indication of whether the second UE can meet the response time requirement. As mentioned in the above embodiments, the indication may be accompanied by other information, such as available bandwidth and / or other resources. In addition, as previously described, the resource pool parameters may include various parameters for conducting a positioning session. This may include, for example, a dedicated positioning resource pool, a contention-based pool, a sensing window positioning duration, a sensing type, or a combination thereof. According to some embodiments, the sensing type may include full sensing, partial sensing, or randomly selected sensing.
[0090] According to some embodiments, the indication of whether the second UE can meet the response time requirement may include an indication that the second UE cannot meet the response time requirement. In such embodiments, method 700 may also include: in response to the indication that the second UE cannot meet the response time requirement, using the first UE to determine a priority for the positioning session, wherein the priority is included in the resource pool parameters for the positioning session. Additionally or alternatively, method 700 may include: in response to the indication that the second UE cannot meet the response time requirement, using the first UE to determine randomly selected sensing as the sensing type for the positioning session, wherein the randomly selected sensing is included in the resource pool parameters for the positioning session. Additionally or alternatively, the method may also include, in response to the indication that the second UE cannot meet the response time requirement, using the first UE to determine a physical (PHY) layer transmission parameter, wherein the PHY layer transmission parameter is included in the resource pool parameters for the positioning session.
[0091] Means for performing the functions at block 730 may include bus 905, processor 910, wireless communication interface 930, sensor 940, memory 960, GNSS receiver 980, and / or other components of the UE, such as described in Fig. 9 Those exemplified in and described below.
[0092] At block 740, the functionality includes transmitting a third message including the resource pool parameters from the first UE to the second UE. This may inform the second UE (e.g., an anchor UE) of how the positioning session should proceed. Likewise, the parameters may be set prior to and / or during the positioning session. Thus, according to some embodiments of method 700, the second message may be received and the third message transmitted prior to the positioning session, or the second message may be received and the third message transmitted during the positioning session. Initially or alternatively, according to some embodiments, the positioning session may use a resource pool carrying SL-PRS, SL PSCCH, or both.
[0093] Means for performing the functions at block 740 may include bus 905, processor 910, wireless communication interface 930, sensor 940, memory 960, GNSS receiver 980, and / or other components of the UE, such as described in Fig. 9 Those exemplified in and described below.
[0094] Figure 8 8 is a flow chart of another method 800 of managing response time in a positioning session between a first UE and a second UE via a SL according to an embodiment. Similarly, the first UE may correspond to a target UE and the second UE may correspond to an anchor UE, such as Figures 4 to 6 The functionality of method 800 may reflect Figure 4 and Figure 6 Aspects of the process shown in . Figure 8 The components of the functions illustrated in one or more of the blocks shown in the figure may be performed by hardware and / or software components of the UE. Fig. 9 Example components of a UE are illustrated in FIG, and are described in more detail below.
[0095] At block 810, the functionality includes receiving, at a second UE, from a first UE, a first message including a quality of service (QoS) profile, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session. Likewise, the time requirement may include a maximum duration for providing positioning information (such as finalization). In some embodiments, the QoS profile may also include a horizontal accuracy requirement, a vertical accuracy requirement, a vertical coordinate request indicator, a speed request indicator, or a combination thereof.
[0096] Means for performing the functions at block 810 may include bus 905, processor 910, wireless communication interface 930, sensor 940, memory 960, GNSS receiver 980, and / or other components of the UE, such as described in Fig. 9 Those exemplified in and described below.
[0097] At block 820, the functionality includes transmitting a second message from the second UE to the first UE, wherein the second message includes an indication of whether the second UE can meet the response time requirement. This indication may be based on determining whether the second UE can meet the response time requirement, the determination being based on factors such as current commitment to other operations / processes (e.g., positioning and / or data), processing capabilities, communication capabilities, etc. Thus, according to some embodiments, method 800 may also include determining, using the second UE, that the second UE cannot meet the response time requirement.
[0098] like Figure 6As mentioned, the anchor UE (e.g., the second UE) can autonomously choose to perform certain operations and / or update certain parameters so as to meet the response time requirement. According to some embodiments, for example, method 800 may also include: in response to determining that the second UE cannot meet the response time requirement, using the second UE to determine a priority for the positioning session; using the second UE to determine randomly selected sensing as a sensing type for the positioning session; using the second UE to determine a physical (PHY) layer transmission parameter; or a combination thereof.
[0099] Means for performing the functions at block 820 may include bus 905, processor 910, wireless communication interface 930, sensor 940, memory 960, GNSS receiver 980, and / or other components of the UE, such as described in Fig. 9 Those exemplified in and described below.
[0100] At box 830, the function includes receiving a third message including resource pool parameters for the positioning session from the first UE at the second UE, wherein the resource pool parameters are based at least in part on an indication of whether the second UE can meet the response time requirement. As previously described, the resource pool parameters may include a dedicated positioning resource pool, a contention-based pool, a sensing window positioning duration, a sensing type, or a combination thereof. The sensing type may include full sensing, partial sensing, or randomly selected sensing. Similarly, method 800 may occur before or during the positioning session. Therefore, according to some embodiments, a second message may be transmitted to the positioning session and a third message may be received; or a second message may be transmitted during the positioning session and a third message may be received. Additionally or alternatively, the positioning session may use a resource pool carrying a SL positioning reference signal (SL-PRS), a SL physical sidelink control channel (PSCCH), or both.
[0101] Means for performing the functions at block 830 may include bus 905, processor 910, wireless communication interface 930, sensor 940, memory 960, GNSS receiver 980, and / or other components of the UE, such as described in Fig. 9 Those exemplified in and described below.
[0102] Fig. 9 is a block diagram of an embodiment of UE 900, which may be utilized as described herein above (e.g., in connection with the aforementioned figures). It should be noted that Fig. 9 It is intended only to provide a generalized illustration of the various components, any or all of which may be utilized as appropriate. In addition, the functionality of the UE discussed herein may be provided by Fig. 9 One or more of the illustrated hardware and / or software components execute.
[0103] UE 900 is shown as including hardware elements that may be electrically coupled via bus 905 (or may communicate in other ways as appropriate). These hardware elements may include a processor 910, which may include, but is not limited to, one or more general-purpose processors (e.g., application processors), one or more special-purpose processors (such as digital signal processor (DSP) chips, graphics acceleration processors, application-specific integrated circuits (ASICs), etc.), and / or other processing structures or components. Processor 910 may include one or more processing units, which may be housed in a single integrated circuit (IC) or multiple ICs. Fig. 9 As shown, some embodiments may have a separate DSP 920, depending on the desired functionality. Position determination and / or other determinations based on wireless communication may be provided in the processor 910 and / or the wireless communication interface 930 (discussed below). The UE 900 may also include: one or more input devices 970, which may include but are not limited to one or more keyboards, touch screens, touch pads, microphones, buttons, dials, switches, etc.; and one or more output devices 915, which may include but are not limited to one or more displays (e.g., touch screens), light emitting diodes (LEDs), speakers, etc.
[0104] UE 900 may also include a wireless communication interface 930, which may include but is not limited to a modem, a network card, an infrared communication device, a wireless communication device and / or a chipset (such as Device, IEEE 802.11 device, IEEE802.15.4 device, Wi-Fi device, WiMAX device, WAN device and / or various cellular devices, etc.), which can enable UE 900 to communicate with other devices as described in the above embodiments. The wireless communication interface 930 can allow the use of the TRP of the network, for example, via eNB, gNB, ng-eNB, access point, various base stations and / or other access node types, and / or other network components, computer systems, and / or any other electronic device communicatively coupled to the TRP to communicate (e.g., send and receive) data and signaling, as described herein. Communication can be performed via one or more wireless communication antennas 932 that transmit and / or receive wireless signals 934. According to some embodiments, the wireless communication antenna 932 may include multiple discrete antennas, antenna arrays, or any combination thereof. The antenna 932 may be able to use beams (e.g., Tx beams and Rx beams) to send and receive wireless signals. Beamforming can be performed using digital and / or analog beamforming techniques using corresponding digital and / or analog circuits. Wireless communication interface 930 may include such circuitry.
[0105] Depending on the desired functionality, the wireless communication interface 930 may include separate receivers and transmitters, or any combination of transceivers, transmitters, and / or receivers to communicate with base stations (e.g., ng-eNBs and gNBs) and other terrestrial transceivers (such as wireless devices and access points). The UE 900 may communicate with different data networks, which may include various network types. For example, one such network type may include a wireless wide area network (WWAN), which may be a code division multiple access (CDMA) network, a time division multiple access (TDMA) network, a frequency division multiple access (FDMA) network, an orthogonal frequency division multiple access (OFDMA) network, a single carrier frequency division multiple access (SC-FDMA) network, a WiMAX (IEEE 802.16) network, and the like. A CDMA network may implement one or more radio access technologies (RATs), such as Wideband Code Division Multiple Access (WCDMA) and so on. The IS-95, IS-2000, and / or IS-856 standards are included. A TDMA network may implement Global System for Mobile Communications (GSM), Digital Advanced Mobile Phone System (D-AMPS), or some other RAT. An OFDMA network may employ Long Term Evolution (LTE), Advanced LTE, Fifth Generation (5G) New Radio (NR), and the like. 5G NR, LTE, Advanced LTE, GSM, and WCDMA are described in documents from the Third Generation Partnership Project (3GPP). Described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). 3GPP and 3GPP2 documents are publicly available. A wireless local area network (WLAN) may also be an IEEE 802.11x network, and a wireless personal area network (WPAN) may be a Bluetooth network, IEEE 802.15x, or some other type of network. The techniques described herein may also be used for any combination of WWAN, WLAN, and / or WPAN.
[0106] The UE 900 may also include a sensor 940. The sensor 940 may include, but is not limited to, one or more inertial sensors and / or other sensors (e.g., accelerometers, gyroscopes, cameras, magnetometers, altimeters, microphones, proximity sensors, light sensors, barometers, etc.), some of which may be used to obtain position-related measurements and / or other information.
[0107] Embodiments of UE 900 may also include a global navigation satellite system (GNSS) receiver 980 that is capable of receiving signals 984 from one or more GNSS satellites using antenna 982 (which may be the same as antenna 932). Positioning based on GNSS signal measurements may be used to supplement and / or incorporate the techniques described herein. GNSS receiver 980 may use conventional techniques to extract the position of UE 900 from GNSS satellites of GNSS systems such as Global Positioning System (GPS), Galileo, GLONASS, Quasi-Zenith Satellite System (QZSS) covering Japan, IRNSS covering India, BeiDou Navigation Satellite System (BDS) covering China, etc. In addition, the GNSS receiver 980 may be used for various augmentation systems (e.g., satellite-based augmentation systems (SBAS)) that may be associated with or otherwise enabled for use with one or more global and / or regional navigation satellite systems, such as, for example, the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multifunction Satellite Augmentation System (MSAS), and the Geographic Augmentation Navigation System (GAGAN), among others.
[0108] It can be noted that although Fig. 9 980 is illustrated as a different component, but the embodiments are not limited to this. As used herein, the term "GNSS receiver" may include hardware and / or software components configured to obtain GNSS measurements (measurements from GNSS satellites). Therefore, in some embodiments, the GNSS receiver may include (as software) a measurement engine executed by one or more processors (such as processor 910, DSP 920 and / or a processor within wireless communication interface 930 (e.g., in a modem)). The GNSS receiver may also optionally include a positioning engine that can use the GNSS measurements from the measurement engine to determine the orientation of the GNSS receiver using an extended Kalman filter (EKF), weighted least squares (WLS), a hatch filter, a particle filter, etc. The positioning engine may also be executed by one or more processors such as processor 910 or DSP 920.
[0109] The UE 900 may also include and / or communicate with a memory 960. The memory 960 may include, but is not limited to, local and / or network accessible storage, disk drives, drive arrays, optical storage devices, solid-state storage devices such as random access memory (RAM) and / or read-only memory (ROM), which may be programmable, flash-updatable, and the like. Such storage devices may be configured to implement any suitable data storage, including but not limited to various file systems, database structures, and the like.
[0110] The memory 960 of the UE 900 may also include software elements ( Fig. 9 900 (and / or the processor 910 or DSP 920 within the UE 900). Then, in some embodiments, such codes and / or instructions can be used to configure and / or adapt a general-purpose computer (or other device) to perform one or more operations according to the described methods.
[0111] It will be apparent to those skilled in the art that substantial modifications may be made according to specific requirements. For example, customized hardware may also be used, and / or specific elements may be implemented in hardware, software (including portable software, such as applets, etc.), or both. In addition, connections to other computing devices such as network input / output devices may be employed.
[0112] With reference to the accompanying drawings, the components that may include memory may include non-transient machine-readable media. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any storage medium that participates in providing data that enables a machine to operate in a particular manner. In the embodiments provided above, various machine-readable media may be involved when providing instructions / codes to processors and / or other devices for execution. Additionally or alternatively, machine-readable media may be used to store and / or carry such instructions / codes. In many specific implementations, computer-readable media are physical and / or tangible storage media. Such media may take many forms, including but not limited to non-volatile media and volatile media. Common forms of computer-readable media include, for example: magnetic and / or optical media, any other physical media with hole patterns, RAM, programmable ROM (PROM), erasable PROM (EPROM), FLASH-EPROM, any other memory chip or memory box, or any other medium that can be used for computer-readable instructions and / or codes.
[0113] The methods, systems and devices discussed herein are examples. Various embodiments may omit, replace or add various processes or components as appropriate. For example, the features described for certain embodiments may be combined in various other embodiments. The different aspects and elements of the embodiments may be combined in a similar manner. The various components of the accompanying drawings provided herein may be embodied in hardware and / or software. In addition, technology may evolve, and therefore many elements are examples, which do not limit the scope of the present disclosure to those specific examples.
[0114] It has proven convenient at times, primarily for reasons of common usage, to refer to such signals as bits, information, values, elements, symbols, characters, variables, terms, numbers, digital symbols, and the like. It will be understood, however, that all of these or similar terms are to be associated with the appropriate physical quantities and are merely convenient labels. Unless expressly stated otherwise, as will be apparent from the above discussion, it will be understood that throughout this specification, discussions utilizing terms such as "processing," "computing," "calculating," "determining," "ascertaining," "identifying," "correlating," "measuring," "performing," and the like refer to the actions or processes of a particular device such as a special-purpose computer or similar special-purpose electronic computing device. Thus, in the context of this specification, a special-purpose computer or similar special-purpose electronic computing device is capable of manipulating or transforming signals, typically represented as physical, electronic, electrical, or magnetic quantities in a memory, register, or other information storage device, a transmitting device, or a display device of the special-purpose computer or similar special-purpose electronic computing device.
[0115] As used herein, the terms "and" and "or" may include various meanings that are also intended to depend at least in part on the context in which such terms are used. Generally, "or", if used in association with a list, such as A, B, or C, is intended to mean A, B, and C (inclusive meaning is used here) as well as A, B, or C (exclusive meaning is used here). In addition, as used herein, the term "one or more" may be used to describe any feature, structure, or characteristic in the singular, or may be used to describe a certain combination of features, structures, or characteristics. However, it should be noted that this is merely an illustrative example, and the subject matter claimed is not limited to this example. In addition, the term "at least one of", if used in association with a list, such as A, B, or C, may be interpreted to mean any combination of A, B, and / or C, such as A, AB, AA, AAB, AABBCCC, etc.
[0116] Several embodiments have been described, and various modifications, alternative configurations, and equivalents may be used without departing from the scope of the present disclosure. For example, the above elements may be components of a larger system, wherein other rules may take precedence over the application of the various embodiments or otherwise modify the application of the various embodiments. In addition, multiple steps may be performed before, during, or after considering the above elements. Accordingly, the above description does not limit the scope of the present disclosure.
[0117] In view of this description, embodiments may include different combinations of features. Specific implementation examples are described in the following numbered clauses:
[0118] Clause 1. A method for managing a communication between a first user equipment (UE) and a second UE via a side link
[0119] (SL) A method for locating response time in a session, the method comprising:
[0120] Transmitting a first message including a quality of service (QoS) profile from the first UE to the second UE, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session; receiving a second message from the second UE at the first UE, wherein the second message includes an indication of whether the second UE can meet the response time requirement; determining, using the first UE, resource pool parameters for the positioning session, wherein the resource pool parameters are based at least in part on the indication of whether the second UE can meet the response time requirement; and transmitting a third message including the resource pool parameters from the first UE to the second UE.
[0121] Clause 2. The method of clause 1, wherein the resource pool parameters include: a dedicated positioning resource pool, a contention-based pool, a sensing window positioning duration, a sensing type, or a combination thereof.
[0122] Clause 3. The method of clause 2, wherein the sensing type comprises: full sensing, partial sensing, or random selection sensing.
[0123] Clause 4. The method of any one of clauses 1 to 3, wherein the QoS profile further comprises: a horizontal accuracy requirement, a vertical accuracy requirement, a vertical coordinate request indicator, a speed request indicator, or a combination thereof.
[0124] Clause 5. A method according to any one of clauses 1 to 4, wherein the indication of whether the second UE can meet the response time requirement includes an indication that the second UE cannot meet the response time requirement.
[0125] Clause 6. The method according to Clause 5 also includes: in response to the indication that the second UE cannot meet the response time requirement, using the first UE to determine a priority for the positioning session, wherein the priority is included in the resource pool parameters for the positioning session.
[0126] Clause 7. The method according to any one of Clauses 5 to 6 further includes: in response to the indication that the second UE cannot meet the response time requirement, using the first UE to determine randomly selected sensing as the sensing type for the positioning session, wherein the randomly selected sensing is included in the resource pool parameters for the positioning session.
[0127] Clause 8. A method according to any one of clauses 5 to 7, further comprising: in response to the indication that the second UE cannot meet the response time requirement, determining, using the first UE, a physical (PHY) layer transmission parameter, wherein the PHY layer transmission parameter is included in the resource pool parameter for the positioning session. Clause 9. A method according to any one of clauses 1 to 8, wherein the second message is received and the third message is transmitted before the positioning session; or the second message is received and the third message is transmitted during the positioning session. Clause 10. A method according to any one of clauses 1 to 9, wherein the positioning session uses a resource pool carrying a SL positioning reference signal (SL-PRS), a SL physical sidelink control channel (PSCCH), or both.
[0128] Clause 11. A method of managing response time in a positioning session between a first user equipment (UE) and a second UE via a side link (SL), the method comprising:
[0129] receiving, at the second UE, from the first UE, a quality of service (QoS) signal
[0130] A first message of a QoS profile, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session; a second message is transmitted from the second UE to the first UE, wherein the second message includes an indication of whether the second UE can meet the response time requirement; and a third message is received from the first UE at the second UE including resource pool parameters for the positioning session, wherein the resource pool parameters are at least partially based on the indication of whether the second UE can meet the response time requirement.
[0131] Clause 12. The method of clause 11, wherein the resource pool parameters include: a dedicated positioning resource pool, a contention-based pool, a sensing window positioning duration, a sensing type, or a combination thereof.
[0132] Clause 13. The method of clause 12, wherein the sensing type comprises: full sensing, partial sensing, or random selection sensing.
[0133] Clause 14. The method of any one of clauses 11 to 13, wherein the QoS profile further comprises: a horizontal accuracy requirement, a vertical accuracy requirement, a vertical coordinate request indicator, a speed request indicator, or a combination thereof.
[0134] Clause 15. A method as described in any of clauses 11 to 14, further comprising determining, using the second UE, that the second UE cannot meet the response time requirement.
[0135] Clause 16. The method of clause 15, further comprising: in response to determining that the second UE cannot meet the response time requirement, determining a priority for the positioning session using the second UE.
[0136] Clause 17. A method according to any one of clauses 15 to 16, further comprising: in response to determining that the second UE cannot meet the response time requirement, determining, using the second UE, randomly selected sensing as the sensing type for the positioning session.
[0137] Clause 18. A method according to any one of clauses 15 to 17, further comprising: in response to determining that the second UE cannot meet the response time requirement, determining a physical (PHY) layer transmission parameter using the second UE.
[0138] Clause 19. The method of any of clauses 11 to 18, wherein the second message is transmitted to the positioning session and the third message is received; or the second message is transmitted and the third message is received during the positioning session.
[0139] Clause 20. A method according to any of clauses 11 to 19, wherein the positioning session uses a resource pool carrying a SL Positioning Reference Signal (SL-PRS), a SL Physical Sidelink Control Channel (PSCCH), or both.
[0140] Clause 21. A first user equipment (UE) for managing response time in a positioning session conducted between the first UE and a second UE via a side link (SL), the first UE comprising: a transceiver; a memory; and one or more processors, the one or more processors being communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: transmit a first message including a quality of service (QoS) profile to the second UE via the transceiver, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session; receive a second message from the second UE via the transceiver, wherein the second message includes an indication of whether the second UE can meet the response time requirement; determine a resource pool parameter for the positioning session, wherein the resource pool parameter is based at least in part on the indication of whether the second UE can meet the response time requirement; and transmit a third message including the resource pool parameter to the second UE via the transceiver. Clause 22. A first UE according to clause 21, wherein the one or more processors are configured to include in the resource pool parameter: a dedicated positioning resource pool, a contention-based pool, a sensing window positioning duration, a sensing type, or a combination thereof. Clause 23. A first UE according to any one of clauses 21 to 22, wherein the one or more processors are configured to include in the QoS profile: a horizontal accuracy requirement, a vertical accuracy requirement, a vertical coordinate request indicator, a speed request indicator, or a combination thereof.
[0141] Clause 24. A first UE according to any one of clauses 21 to 23, wherein the one or more processors are configured to determine a priority for the positioning session, wherein the priority is included in the resource pool parameters for the positioning session when the indication of whether the second UE can meet the response time requirement includes an indication that the second UE cannot meet the response time requirement. Clause 25. A first UE according to any one of clauses 21 to 24, wherein the one or more processors are configured to: determine random selection sensing as the sensing type for the positioning session when the indication of whether the second UE can meet the response time requirement includes an indication that the second UE cannot meet the response time requirement, and wherein the one or more processors are configured to include random selection sensing in the resource pool parameters for the positioning session. Clause 26. A second user equipment (UE), the second user equipment (UE) being configured to manage response time in a positioning session conducted between a first UE and the second UE via a side link (SL), the second UE comprising: a transceiver; a memory;
[0142] and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: receive, via the transceiver, from the first UE a first message including a quality of service (QoS) profile, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session; transmit, via the transceiver, to the first UE a second message, wherein the second message includes an indication of whether the second UE can meet the response time requirement; and receive, via the transceiver, from the first UE a third message including a resource pool parameter for the positioning session, wherein the resource pool parameter is based at least in part on the indication of whether the second UE can meet the response time requirement. Clause 27. A second UE according to clause 26, wherein the one or more processors are further configured to determine, using the second UE, that the second UE cannot meet the response time requirement.
[0143] Clause 28. A second UE according to any one of clauses 26 to 27, wherein the one or more processors are further configured to: in response to determining that the second UE cannot meet the response time requirement, determine a priority level for the positioning session. Clause 29. A second UE according to any one of clauses 26 to 28, wherein the one or more processors are further configured to: in response to determining that the second UE cannot meet the response time requirement, determine random selection sensing as the sensing type for the positioning session.
[0144] Clause 30. A second UE as described in any of clauses 26 to 29, wherein the one or more processors are further configured to: in response to determining that the second UE cannot meet the response time requirement, determine a physical (PHY) layer transmission parameter. Clause 31. An apparatus having means for performing a method as described in any of clauses 1 to 20.
[0145] Clause 32. A non-transitory computer-readable medium storing instructions comprising code for performing the method of any one of clauses 1 to 20.
Claims
1. A method for managing response time in a positioning session between a first user equipment (UE) and a second UE via a side link (SL), the method comprising: transmitting, from the first UE to the second UE, a first message including a quality of service (QoS) profile, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session; receiving, at the first UE, a second message from the second UE, wherein the second message includes an indication of whether the second UE can meet the response time requirement; determining, with the first UE, a resource pool parameter for the positioning session, wherein the resource pool parameter is based at least in part on the indication of whether the second UE can meet the response time requirement; and A third message including the resource pool parameters is transmitted from the first UE to the second UE.
2. The method according to claim 1, wherein the resource pool parameters include: Dedicated positioning resource pool, Competition-based pools, Sensing window positioning duration, Sensing type, or A combination of them.
3. The method according to claim 2, wherein the sensing type comprises: Fully sensing, Partial sensing, or Select the sensing randomly.
4. The method of claim 1, wherein the QoS profile further comprises: Horizontal accuracy requirements, Vertical accuracy requirements, Vertical coordinate request indicator, Speed Request Indicator, or A combination of them.
5. The method of claim 1, wherein the indication of whether the second UE can meet the response time requirement comprises an indication that the second UE cannot meet the response time requirement.
6. The method according to claim 5, further comprising: In response to the indication that the second UE cannot meet the response time requirement, determining, using the first UE, a priority for the positioning session, wherein the priority is included in the resource pool parameters for the positioning session.
7. The method according to claim 5, further comprising: In response to the indication that the second UE cannot meet the response time requirement, determining, with the first UE, randomly selected sensing as a sensing type for the positioning session, wherein the randomly selected sensing is included in the resource pool parameters for the positioning session.
8. The method according to claim 5, further comprising: In response to the indication that the second UE cannot meet the response time requirement, determining, with the first UE, a physical (PHY) layer transmit parameter, wherein the PHY layer transmit parameter is included in the resource pool parameter for the positioning session.
9. The method according to claim 1, wherein: receiving the second message and transmitting the third message before the positioning session; or The second message is received and the third message is transmitted during the positioning session.
10. The method of claim 1, wherein the positioning session uses a resource pool carrying a SL Positioning Reference Signal (SL-PRS), a SL Physical Sidelink Control Channel (PSCCH), or both.
11. A method of managing response time in a positioning session between a first user equipment (UE) and a second UE via a side link (SL), the method comprising: receiving, at the second UE, from the first UE, a first message including a quality of service (QoS) profile, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session; transmitting a second message from the second UE to the first UE, wherein the second message includes an indication of whether the second UE can meet the response time requirement; as well as A third message including a resource pool parameter for the positioning session is received at the second UE from the first UE, wherein the resource pool parameter is based at least in part on the indication of whether the second UE can meet the response time requirement.
12. The method according to claim 11, wherein the resource pool parameters include: Dedicated positioning resource pool, Competition-based pools, Sensing window positioning duration, Sensing type, or A combination of them.
13. The method of claim 12, wherein the sensing type comprises: Fully sensing, Partial sensing, or Select the sensing randomly.
14. The method of claim 11, wherein the QoS profile further comprises: Horizontal accuracy requirements, Vertical accuracy requirements, Vertical coordinate request indicator, Speed Request Indicator, or A combination of them.
15. The method of claim 11, further comprising determining, using the second UE, that the second UE cannot meet the response time requirement.
16. The method according to claim 15, further comprising: In response to determining that the second UE cannot meet the response time requirement, a priority for the positioning session is determined using the second UE.
17. The method according to claim 15, further comprising: In response to determining that the second UE cannot meet the response time requirement, randomly selected sensing is determined as a sensing type for the positioning session using the second UE.
18. The method according to claim 15, further comprising: In response to determining that the second UE cannot meet the response time requirement, a physical (PHY) layer transmission parameter is determined using the second UE.
19. The method of claim 11, wherein: transmitting the second message to the positioning session and receiving the third message; or The second message is transmitted and the third message is received during the positioning session.
20. The method of claim 11, wherein the positioning session uses a resource pool carrying a SL Positioning Reference Signal (SL-PRS), a SL Physical Sidelink Control Channel (PSCCH), or both.
21. A first user equipment UE, the first user equipment UE being configured to manage a response time in a positioning session between the first UE and a second UE via a side link (SL), the first UE comprising: Transceiver; Memory; and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: Transmitting, via the transceiver, to the second UE a quality of service (QoS) signal a first message of a profile, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session; receiving, via the transceiver, a second message from the second UE, wherein the second message includes an indication of whether the second UE can meet the response time requirement; determining a resource pool parameter for the positioning session, wherein the resource pool parameter is based at least in part on an indication of whether the second UE can meet the response time requirement; and A third message including the resource pool parameters is transmitted to the second UE via the transceiver.
22. The first UE of claim 21, wherein the one or more processors are configured to include in the resource pool parameters: Dedicated positioning resource pool, Competition-based pools, Sensing window positioning duration, Sensing type, or A combination of them.
23. The first UE of claim 21, wherein the one or more processors are configured to include in the QoS profile: Horizontal accuracy requirements, Vertical accuracy requirements, Vertical coordinate request indicator, Speed Request Indicator, or A combination of them.
24. The first UE of claim 21 , wherein the one or more processors are configured to determine a priority for the positioning session, wherein the priority is included in the resource pool parameter for the positioning session when the indication of whether the second UE can meet the response time requirement includes an indication that the second UE cannot meet the response time requirement.
25. The first UE according to claim 24, wherein the one or more processors are configured to: determine randomly selected sensing as the sensing type for the positioning session when the indication of whether the second UE can meet the response time requirement includes an indication that the second UE cannot meet the response time requirement, and wherein the one or more processors are configured to include randomly selected sensing in the resource pool parameters for the positioning session.
26. A second user equipment (UE), the second user equipment (UE) being configured to manage a response time in a positioning session between a first UE and the second UE via a side link (SL), the second UE comprising: Transceiver; Memory; and one or more processors communicatively coupled to the transceiver and the memory, wherein the one or more processors are configured to: receiving, via the transceiver, from the first UE a first message including a quality of service (QoS) profile, wherein the QoS profile includes a response time requirement for providing positioning information within the positioning session; transmitting, via the transceiver, a second message to the first UE, wherein the second message includes an indication of whether the second UE can meet the response time requirement; and A third message is received from the first UE via the transceiver including a resource pool parameter for the positioning session, wherein the resource pool parameter is based at least in part on the indication of whether the second UE can meet the response time requirement.
27. The second UE of claim 26, wherein the one or more processors are further configured to determine, using the second UE, that the second UE cannot meet the response time requirement.
28. The second UE of claim 27, wherein the one or more processors are further configured to: in response to determining that the second UE cannot meet the response time requirement, determine a priority level for the positioning session.
29. The second UE of claim 27, wherein the one or more processors are further configured to: in response to determining that the second UE cannot meet the response time requirement, determine randomly selected sensing as the sensing type for the positioning session.
30. The second UE of claim 27, wherein the one or more processors are further configured to determine a physical (PHY) layer transmission parameter in response to determining that the second UE cannot meet the response time requirement.
