Dynamic updating of quality of service parameters during ongoing new radio positioning session

Abstract

A user equipment (e.g., a mobile device) can receive a location request message from a server (e.g., a location management function), where the location request message identifies a plurality of quality of service parameters for a Long Term Evolution Positioning Protocol (LPP) positioning session. In at least one embodiment, the user equipment receives a selection of one or more quality of service parameters for the LPP positioning session. In at least one embodiment, the user equipment can configure the user equipment in accordance with the one or more selected quality of service parameters. In at least one embodiment, the user equipment can generate a location response message in accordance with the selected QoS parameters. The user equipment can transmit the location response message to the server. The UE can select the QoS parameters during communication with the server and / or a second UE via sidelink communication.

Description

Background Technology

[0001] Long Term Evolution (LTE) Location Protocol (LPP) technology is used to determine the location of mobile electronic devices (referred to herein as User Equipment (UE)). Location information can be provided to a server or another UE. LPP technology provides the location technology with the option to select one or more Quality of Service (QoS) parameters. Under the current procedure, selecting one or more QoS parameters requires restarting the location session. Restarting the location session results in latency. Summary of the Invention

[0002] According to some implementations, a method may include: receiving a location request message from a server, wherein the location request message identifies a plurality of Quality of Service (QoS) parameters of an LPP location session; receiving a selection of one or more QoS parameters of the LPP location session; configuring a user equipment based on the one or more selected QoS parameters; generating a location response message; and sending the location response message to the server.

[0003] An example method for dynamically configuring one or more Quality of Service (QoS) parameters during a location session at a User Equipment (UE) according to this disclosure includes: receiving a location request message from a network entity, wherein the location request message identifies one or more QoS parameters selectable for the location session. The method further includes: obtaining the selection of one or more QoS parameters for the location session. The method further includes: sending a location response message to the network entity, wherein the location response message is generated at least in part based on the selected QoS parameters and indicates a configuration of the UE made according to the one or more selected QoS parameters.

[0004] An example method for dynamically configuring one or more Quality of Service (QoS) parameters during a location session at a network entity, according to this disclosure, includes: sending a location request message from the network entity to a user equipment (UE), wherein the location request message identifies one or more QoS parameters selectable for the location session. The method further includes: obtaining the selection of one or more QoS parameters for the location session. The method also includes: receiving a location response message to the network entity, wherein the location response message is generated at least in part based on the selected QoS parameters and indicates a configuration of the UE made according to the one or more selected QoS parameters.

[0005] An example user equipment (UE) according to this disclosure for dynamically configuring one or more Quality of Service (QoS) parameters during a location session includes: 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 location request message from a network entity via the transceiver, wherein the location request message identifies one or more QoS parameters selectable for the location session. The one or more processing units are further configured to: obtain the selection of one or more QoS parameters for the location session. The one or more processing units are further configured to: send a location response message to a network entity via the transceiver, wherein the location response message is generated at least in part based on the selected QoS parameters and indicates a configuration of the UE made according to the one or more selected QoS parameters.

[0006] An example network entity according to this disclosure for dynamically configuring one or more Quality of Service (QoS) parameters during a location session includes: 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: send a location request message from the network entity to a user equipment (UE) via the transceiver, wherein the location request message identifies one or more QoS parameters selectable for the location session. The one or more processing units are further configured to: obtain the selection of one or more QoS parameters for the location session. The one or more processing units are further configured to: receive a location response message to the network entity via the transceiver, wherein the location response message: is generated at least in part based on the selected QoS parameters and indicates a configuration of the UE made according to the one or more selected QoS parameters.

[0007] An example apparatus according to this disclosure for dynamically configuring one or more Quality of Service (QoS) parameters during a location session includes: a means for receiving a location request message from a network entity, wherein the location request message identifies one or more QoS parameters selectable for the location session. The apparatus further includes: a means for obtaining the selection of one or more QoS parameters for the location session. The apparatus further includes: a means for sending a location response message to the network entity, wherein the location response message is generated at least in part based on the selected QoS parameters and indicates a configuration of a user equipment (UE) based on the one or more selected QoS parameters.

[0008] An example apparatus according to this disclosure for dynamically configuring one or more Quality of Service (QoS) parameters during a location session includes: a device for sending a location request message from a network entity to a user equipment (UE), wherein the location request message identifies one or more QoS parameters selectable for the location session. The apparatus further includes: a device for obtaining the selection of one or more QoS parameters for the location session. The apparatus further includes: a device for receiving a location response message to a network entity, wherein the location response message is generated at least in part based on the selected QoS parameters and indicates a configuration of the UE made according to the one or more selected QoS parameters.

[0009] According to this disclosure, an example non-transitory computer-readable medium stores instructions for dynamically configuring one or more Quality of Service (QoS) parameters during a location session. The instructions include: code for receiving a location request message from a network entity, wherein the location request message identifies one or more QoS parameters selectable for the location session. The instructions also include: code for obtaining the selection of one or more QoS parameters for the location session. Furthermore, the instructions include: code for sending a location response message to the network entity, wherein the location response message is generated at least in part based on the selected QoS parameters and indicates a configuration of a user equipment (UE) based on the one or more selected QoS parameters.

[0010] According to this disclosure, an example non-transitory computer-readable medium stores instructions for dynamically configuring one or more Quality of Service (QoS) parameters during a location session. The instructions include: code for sending a location request message from a network entity to a user equipment (UE), wherein the location request message identifies one or more QoS parameters selectable for the location session. The instructions also include: code for obtaining the selection of one or more QoS parameters for the location session. Furthermore, the instructions include: code for receiving a location response message to a network entity, wherein the location response message is generated at least in part based on the selected QoS parameters and indicates a configuration of the UE made according to the one or more selected QoS parameters.

[0011] These and other embodiments will be described in detail below. For example, other embodiments relate to systems, devices, and computer-readable media associated with the methods described herein.

[0012] This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used in isolation to define the scope of the claimed subject matter. This subject matter should be understood by referring to the appropriate portions of the entire specification, any or all of the accompanying drawings, and each claim. The foregoing, as well as other features and examples, will be described in more detail in the appended specification, claims, and drawings. Attached Figure Description

[0013] Figure 1 This is a simplified diagram of a positioning system according to an embodiment of the present disclosure.

[0014] Figure 2 This is a diagram of an example communication system that can utilize a 5G network to determine the location of a mobile device according to an embodiment.

[0015] Figure 3 This illustrates a simplified example of information exchange during an LPP location session.

[0016] Figure 4 This shows an example of information exchange during a dynamic LPP location session.

[0017] Figure 5 This shows a second example of information exchange in a dynamic LPP location session.

[0018] Figure 6 This illustrates a third example of information exchange in a dynamic LPP location session according to an embodiment.

[0019] Figure 7 This is a flowchart illustrating a method for dynamically configuring a UE for an LPP location session according to an embodiment.

[0020] Figure 8 This is a flowchart illustrating a method for dynamically configuring a server for an LPP location session, based on an embodiment.

[0021] Figure 9 This is a block diagram of an embodiment of a user equipment (UE) device.

[0022] Figure 10 This is a block diagram of an embodiment of a computer system (e.g., a server).

[0023] Figure 11 This is a block diagram of an embodiment of a base station.

[0024] According to specific example embodiments, similar reference numerals and symbols in the various figures indicate similar elements. Furthermore, multiple instances of an element can be indicated by adding a letter or hyphen after the first digit of the element, followed by a second digit. For example, multiple instances of element 110 can be indicated as 110-1, 110-2, 110-3, etc., or as 110a, 110b, 110c, etc. When such an element is indicated by only the first digit, it should be understood that any instance of the element (e.g., element 110 in the aforementioned examples would indicate elements 110-1, 110-2, and 110-3, or elements 110a, 110b, and 110c) Detailed Implementation

[0025] The following detailed description of exemplary embodiments is with reference to the accompanying drawings. The same reference numerals in different drawings may identify the same or similar elements.

[0026] Several illustrative embodiments will now be described with reference to the accompanying drawings, which form part of this document. While specific embodiments that may implement one or more aspects of this disclosure are described below, other embodiments may be used and various modifications may be made without departing from the scope of this disclosure.

[0027] As used herein, an "RF signal" includes electromagnetic waves that transmit information through space between a transmitter (or transmitting device) and a receiver (or receiving device). As used herein, a transmitter may send a single "RF signal" or multiple "RF signals" to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal. The same transmitted RF signal on different paths between the transmitter and receiver can be referred to as a "multipath" RF signal.

[0028] Figure 1 This is a simplified diagram of a positioning system 100 according to an embodiment, wherein the UE 105, location server 160, and / or other components of the positioning system 100 may use the techniques provided herein to determine the estimated location of the UE 105. The techniques described herein may be implemented by one or more components of the positioning system 100. The positioning system 100 may include: the UE 105; one or more Global Navigation Satellite System (GNSS) satellites (such as GPS, GLONASS, Galileo, or BeiDou) 110 (also referred to as spacecraft (SV)); a base station 120; an access point (AP) 130; a location server 160; a network 170; and an external client 180. Generally, the positioning system 100 may estimate the location of the UE 105 based on RF signals received by and / or transmitted from the UE 105 and the known locations of other components transmitting and / or receiving RF signals (e.g., GNSS satellites 110, base station 120, AP 130). Figure 2 Let's discuss additional details about specific location estimation techniques.

[0029] It should be noted that Figure 1 Only a general description of the various components is provided, any or all of which can be appropriately utilized, and each of which can be reused as necessary. Specifically, although only one UE 105 is shown, it is understood that many UEs (e.g., hundreds, thousands, millions, etc.) can utilize positioning system 100. Similarly, positioning system 100 may include more than Figure 1The diagram shows a greater or lesser number of base stations 120 and / or access points 130. The connections shown for the various components in the positioning system 100 include data and signaling connections that may have additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality. For example, in some embodiments, an external client 180 may connect directly to the location server 160. Those skilled in the art will recognize numerous modifications to the illustrated components.

[0030] Depending on the desired functionality, network 170 may include any of a variety of wireless and / or wired networks. For example, network 170 may include any combination of public and / or private networks, local and / or wide area networks, etc. Furthermore, network 170 may utilize one or more wired and / or wireless communication technologies. For example, in some embodiments, network 170 may include cellular or other mobile networks, wireless local area networks (WLANs), wireless wide area networks (WWANs), and / or the Internet. Examples of network 170 include Long Term Evolution (LTE) wireless networks, fifth-generation (5G) wireless networks (also known as New Radio (NR) wireless networks or 5G NR wireless networks), Wi-Fi WLANs, and the Internet. LTE, 5G, and NR are wireless technologies defined or being defined by the 3rd Generation Partnership Project (3GPP). Network 170 may also include more than one network and / or more than one type of network.

[0031] Base station 120 and access point (AP) 130 are communicatively coupled to network 170. In some embodiments, base station 120 may be owned, maintained, and / or operated by a cellular network provider and may employ any of the various wireless technologies described below. Depending on the technology of network 170, base station 120 may include a Node B, evolved Node B (eNodeB or eNB), base transceiver station (BTS), radio base station (RBS), NR NodeB (gNB), next-generation eNB (ng-eNB), etc. Base station 120, as a gNB or ng-eNB, may be part of a next-generation radio access network (NG-RAN), which may connect to a 5G core network (5GC) if network 170 is a 5G network. For example, AP 130 may include a Wi-Fi AP or AP. Therefore, by accessing the network 170 via base station 120 using the first communication link 133, UE 105 can send and receive information with network-connected devices (such as location server 160). Additionally or alternatively, because AP 130 can also be communicatively coupled to network 170, UE 105 can use the second communication link 135 to communicate with network-connected and Internet-connected devices (including location server 160).

[0032] As used herein, the term "base station" may refer generally to a single physical transmitting point or multiple co-located physical transmitting points that may be located at base station 120. A transmit / receive point (TRP) (also referred to as a transmit / receive point) corresponds to this type of transmitting point, and the term "TRP" may be used interchangeably with the terms "gNB," "ng-eNB," and "base station." In some cases, base station 120 may include multiple TRPs, for example, each TRP being associated with a different antenna or a different antenna array of base station 120. A physical transmitting point may include the antenna array of base station 120 (e.g., as in a multiple-input multiple-output (MIMO) system and / or in the case of beamforming at the base station). The term "base station" may also refer to multiple non-co-located physical transmitting points, which may be a distributed antenna system (DAS) (a network of spatially separated antennas connected via a transmission medium to a common source) or a remote radio head (RRH) (a remote base station connected to a serving base station).

[0033] As used herein, the term "cell" can refer generally to a logical communication entity used to communicate with base station 120 and can be associated with identifiers (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)) used to distinguish adjacent cells operating via the same or different carriers. In some examples, an operator may support multiple cells, and different cells may be configured based on different protocol types (e.g., Machine-Type Communication (MTC), Narrowband Internet of Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or others) that provide access to different types of devices. In some cases, the term "cell" may refer to a portion of a geographic coverage area (e.g., a sector) on which a logical entity operates.

[0034] Location server 160 may include servers and / or other computing devices configured to determine the estimated location of UE 105 and / or provide data (e.g., “auxiliary data”) to UE 105 to facilitate location measurement and / or location determination of UE 105. According to some embodiments, location server 160 may include a Home Secure User Plane Location (SUPL) location platform (H-SLP) that can support SUPL user plane (UP) location solutions defined by the Open Mobility Alliance (OMA) and can support location services for UE 105 based on subscription information of UE 105 stored in location server 160. In some embodiments, location server 160 may include a Discovery SLP (D-SLP) or an Emergency SLP (E-SLP). Location server 160 may also include an Enhanced Services Mobile Location Center (E-SMLC) that supports the positioning of UE 105 using a control plane (CP) location solution for LTE radio access of UE 105. Location server 160 may also include location management function (LMF), which uses a control plane (CP) location solution for NR or LTE radio access of UE 105 to support the positioning of UE 105.

[0035] In the CP location solution, from the perspective of network 170, signaling for controlling and managing the location of UE 105 can be exchanged as signaling between units of network 170 and with UE 105 using existing network interfaces and protocols. In the UP location solution, from the perspective of network 170, signaling for controlling and managing the location of UE 105 can be exchanged as data (e.g., data transmitted using Internet Protocol (IP) and / or Transmit Control Protocol (TCP)) between location server 160 and UE 105.

[0036] As previously described (and discussed in more detail below), the estimated location of UE 105 may be based on measurements of RF signals transmitted from and / or received by UE 105. Specifically, these measurements may provide information about the relative distance and / or angle between UE 105 and one or more components in positioning system 100 (e.g., GNSS satellite 110, AP 130, base station 120). The estimated location of UE 105 may be geometrically estimated based on distance and / or angle measurements and the known location of one or more components (e.g., using multiangulation and / or multilateration).

[0037] While ground components (such as AP 130 and base station 120) may be fixed, the embodiments are not so limited. Mobile components may be used. For example, in some embodiments, the location of UE 105 may be estimated at least in part based on measurements of RF signals 140 transmitted between UE 105, which may be mobile or fixed, and one or more other UEs 145. When one or more other UEs 145 are used for the location determination of a particular UE 105, the UE 105 to be located may be referred to as the “target UE,” and each of the one or more other UEs 145 used may be referred to as the “anchor UE.” For the location determination of the target UE, the corresponding locations of the one or more anchor UEs may be known and / or determined jointly with the target UE. Direct communication between one or more other UEs 145 and UE 105 may include sidelink and / or similar device-to-device (D2D) communication technologies. Sidelink, as defined by 3GPP, is a form of D2D communication under cellular-based LTE and NR standards.

[0038] The estimated location of UE 105 can be used for various applications, such as assisting the user of UE 105 in direction finding or navigation, or assisting (e.g., in the location of another user associated with external client 180) in locating UE 105. In this document, "location" is also referred to as "location estimation," "estimated location," "position," "location," "location estimation," "location fixed," "estimated location," "location fixed," or "fixed." The process of determining location can be referred to as "location," "location determination," "location determination," etc. The location of UE 105 can include the absolute location of UE 105 (e.g., longitude and latitude and possible altitude) or the relative location of UE 105 (e.g., a location expressed as a distance north or south, east or west from some other known fixed location or some other location (such as the location of UE 105) at a known prior time, and a distance that may be higher or lower than it). Location can be specified as a geodetic location including coordinates, which can be absolute (e.g., latitude, longitude, and optional altitude), relative (e.g., relative to some known absolute location), or local (e.g., X, Y, and optional Z coordinates according to a coordinate system defined relative to a local area, such as a factory, warehouse, university campus, shopping mall, stadium, or conference center). Location can be a town location and can then include street addresses (e.g., names or labels including country, state, county, city, road, and / or street, and / or road or street numbers), and / or labels or names of places, buildings, parts of buildings, floors of buildings, and / or rooms within buildings. Location can also include indications of uncertainty or error, such as the horizontal and possible vertical distances where the location is expected to have errors, or an indication of the area or volume (e.g., a circle or ellipse) that UE105 is expected to be located in with a certain confidence level (e.g., 95% confidence).

[0039] External client 180 may be a web server or remote application that is associated with UE 105 in some way (e.g., accessible to the user of UE 105), or it may be a server, application, or computer system that provides location services to other users, which may include obtaining and providing the location of UE 105 (e.g., to enable services such as a friend or relative finder or a child or pet location service). Additionally or alternatively, external client 180 may obtain the location of UE 105 and provide it to emergency service providers, government agencies, etc.

[0040] As previously mentioned, the example positioning system 100 can use wireless communication networks, such as LTE-based or 5G NR-based networks. Figure 2A diagram illustrating an embodiment of a 5G NR positioning system (e.g., positioning system 100) is shown. The 5G NR positioning system 200 can be configured to use access nodes 210, 214, 216 (which may correspond to...) Figure 1 The 5G NR positioning system 200 implements one or more positioning methods to determine the location of the UE 105 using a base station 120 and an access point 130 (optionally) and an LMF 220 (which may correspond to a location server 160). Here, the 5G NR positioning system 200 includes the UE 105 and components of a 5G NR network including a next-generation (NG) radio access network (RAN) (NG-RAN) 235 and a 5G core network (5G CN) 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 NR RAN; and the 5G CN 240 may be referred to as an NG core network. The 5G NR positioning system 200 may also utilize information from GNSS satellites 110 from GNSS systems such as the Global Positioning System (GPS) or similar systems (e.g., GLONASS, Galileo, BeiDou, Indian Regional Navigation Satellite System (IRNSS)). Additional components of the 5G NR positioning system 200 will be described below. The 5G NR positioning system 200 may include additional or replaceable components.

[0041] It should be noted that Figure 2 This description provides only a general overview of the various components, any or all of which may be appropriately utilized, and each of which may be reused or omitted as necessary. Specifically, although only one UE 105 is shown, it is 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 110, gNB 210, ng-eNB 214, wireless local area network (WLAN) 216, access and mobility management functions (AMF) 215, external clients 230, and / or other components. The connections shown linking the various components in the 5G NR positioning system 200 include data and signaling connections that may have additional (intermediate) components, direct or indirect physical and / or wireless connections, and / or additional networks. Furthermore, components may be rearranged, combined, separated, replaced, and / or omitted depending on the desired functionality.

[0042] UE 105 may include and / or be referred to as a device, mobile device, wireless device, mobile terminal, terminal, mobile station (MS), terminal (SET) implementing Secure User Plane Location (SUPL), or some other name. Furthermore, UE 105 may correspond to a mobile phone, smartphone, laptop, tablet, personal data assistant (PDA), navigation device, Internet of Things (IoT) device, or some other portable or mobile device. Typically (though not always), UE 105 may support one or more Radio Access Technologies (RATs) such as GSM, CDMA, W-CDMA, LTE, High-Speed ​​Packet Data (HRPD), IEEE 802.11, etc. Bluetooth, WiMAX global microwave access interoperability TM Wireless communication such as 5G NR (e.g., using NG-RAN 235 and 5G CN240) is also supported. UE 105 can also support wireless communication using (similar to one or more RATs, and as previously referenced). Figure 1 (As indicated) WLAN 216 can connect to other networks (such as the Internet) for wireless communication. Using one or more of these RATs can allow UE 105 (e.g., via...) Figure 2 The 5G CN 240 (not shown) unit, or possibly via Gateway Mobile Location Center (GMLC) 225, communicates with external client 230 and / or allows external client 230 (e.g., via GMLC 225) to receive location information about UE 105. Figure 2 The external client 230 can correspond to, for example, being implemented in a 5G NR network or communicatively coupled to a 5G NR network. Figure 1 External client 180.

[0043] In a personal area network, such as one where users can employ audio, video, and / or data I / O devices and / or body sensors, as well as separate wired or wireless modems, UE 105 may include a single entity or may include multiple entities. The estimation of the location of UE 105 may be referred to as location, location estimate, location fixed, fixed, positioning, location estimation, or location fixed, and may be geodetic, providing the location coordinates of UE 105 (e.g., latitude and longitude), which may or may not include an altitude component (e.g., altitude above sea level, depth above or below ground level, floor level, or basement level). Alternatively, the location of UE 105 may be represented as a town location (e.g., as a postal address or designation of points or small areas within a building, such as a specific room or floor). The location of UE 105 may also be represented as an area or volume (by geodetic surveying or defined in town form) in which UE 105 is expected to be located with some probability or confidence level (e.g., 67%, 95%, etc.). The location of the UE 105 can also be a relative location, including, for example, distance and direction defined relative to an origin at a known location, or relative to X, Y (and Z) coordinates, wherein the known location can be defined geodeticly, in urban terms, or by a point, area, or volume indicated on a reference map, plan, or architectural drawing. In this description, unless otherwise indicated, the use of the term “location” can include any of these variations. When calculating the location of the UE, local X, Y, and possibly Z coordinates are typically obtained, and then, if necessary, the local coordinates are converted to absolute coordinates (e.g., latitude, longitude, and altitude above or below mean sea level).

[0044] Figure 2 The base station shown in NG-RAN 235 can correspond to Figure 1 The base station 120 in the NG-RAN 235 includes a transmit / receive point (TRP) and may include NR NodeBs (gNBs) 210-1 and 210-2 (collectively referred to herein as gNB 210) and / or the antennas of the gNBs. The gNB 210 pairs in the NG-RAN 235 can be connected to each other (e.g., as shown in the image). Figure 2The connection may be direct or indirect via other gNBs 210. The communication interface between the base stations (gNB 210 and / or ng-eNB 214) may be referred to as the Xn interface 237. Access to the 5G network is provided to the UE 105 via wireless communication between the UE 105 and one or more gNBs 210, wherein one or more gNBs 210 may use 5G NR to provide wireless communication access to the 5GCN 240 on behalf of the UE 105. The radio interface between the base stations (gNB 210 and / or ng-eNB 214) and the UE 105 may be referred to as the Uu interface 239. 5G NR radio access may also be referred to as NR radio access or 5G radio access. Figure 2 In this context, the serving gNB of UE 105 is assumed to be gNB210-1, although if UE 105 moves to another location, other gNBs (e.g., gNB 210-2) may serve as serving gNBs or may serve as secondary gNBs to provide additional throughput and bandwidth to UE 105.

[0045] Figure 2 The base station in the NG-RAN 235 shown may also include, or alternatively include, a next-generation evolved NodeB, also known as an ng-eNB, 214. The ng-eNB 214 may be connected (e.g., directly or indirectly via other gNBs 210 and / or other ng-eNBs) to one or more gNBs 210 in the NG-RAN 235. The ng-eNB 214 may provide LTE radio access and / or evolved LTE (eLTE) radio access to the UE 105. Figure 2 Some gNB 210s (e.g., gNB 210-2) and / or ng-eNB 214s can be configured to act as positioning-only beacons, which can transmit signals (e.g., positioning reference signals (PRS)) and / or broadcast auxiliary data to assist the positioning of UE 105, but may not receive signals from UE 105 or from other UEs. It should be noted that although... Figure 2 Only one ng-eNB 214 is shown, but some embodiments may include multiple ng-eNBs 214. Base stations 210 and 214 can communicate directly with each other via the Xn communication interface. Additionally or alternatively, base stations 210 and 214 can communicate directly or indirectly with other components of the 5G NR positioning system 200, such as LMF 220 and AMF 215.

[0046] The 5G NR positioning system 200 may also include one or more WLANs 216, which can (e.g., in the case of untrusted WLANs 216) connect to the non-3GPP interoperability function (N3IWF) 250 in the 5G CN 240. For example, WLAN 216 may support IEEE 802.11 Wi-Fi access for UE 105 and may include one or more Wi-Fi APs (e.g., Figure 1 (AP130). Here, the N3IWF250 can connect to other units in the 5G CN 240, such as the AMF 215. In some embodiments, the WLAN 216 can support another RAT, such as Bluetooth. The N3IWF 250 can provide support for secure access from the UE 105 to other units in the 5G CN 240, and / or can support interoperability between one or more protocols used by the WLAN 216 and the UE 105 and one or more protocols used by other units of the 5G CN 240 (such as the AMF 215). For example, the N3IWF 250 can support the establishment of an IPSec tunnel with the UE 105, the termination of the IKEv2 / IPSec protocol with the UE 105, the corresponding termination of the control plane and user plane to the N2 and N3 interfaces of the 5G CN 240, and the relay of uplink (UL) and downlink (DL) control plane non-access stratum (NAS) signaling between the UE 105 and the AMF 215 via the N1 interface. In some other embodiments, WLAN 216 can be directly connected to a unit in 5G CN 240 (e.g., Figure 2 The AMF 215 (shown by the dashed line) is used without going through the N3IWF 250. For example, if WLAN 216 is a trusted WLAN of 5G CN 240, a direct connection between WLAN 216 and 5G CN 240 can occur, and a Trusted WLAN Interoperability (TWIF) function, which can be an element within WLAN 216, can be used. Figure 2 (Not shown) to achieve this. It should be noted that, although... Figure 2 Only one WLAN 216 is shown, but some embodiments may include multiple WLANs 216.

[0047] The access node may include any of various network entities that enable communication between UE 105 and AMF 215. This may include gNB 210, ng-eNB 214, WLAN 216, and / or other types of cellular base stations. However, the access node providing the functionality described herein may additionally or alternatively include entities that implement communication with... Figure 2The entity communicating with any of the various RATs (which may include non-cellular technologies) not shown. Therefore, the term "access node" as used in the embodiments described below may include, but is not limited to, gNB 210, ng-eNB 214, or WLAN 216.

[0048] In some embodiments, an access node (such as gNB 210, ng-eNB 214, or WLAN 216, either alone or in combination with other components of the 5G NR positioning system 200) can be configured to: in response to a request to receive location information from LMF 220, obtain location measurements of uplink (UL) signals received from UE 105, and / or obtain downlink (DL) location measurements from UE 105, which are obtained by UE 105 for DL ​​signals received by UE 105 from one or more access nodes. As previously stated, although Figure 2 Access nodes 210, 214, and 216 are depicted configured to communicate according to 5G NR, LTE, and Wi-Fi communication protocols, respectively. However, access nodes configured to communicate according to other communication protocols can be used, such as a Node B using the Wideband Code Division Multiple Access (WCDMA) protocol for Universal Mobile Telecommunications Services (UMTS) Terrestrial Radio Access Network (UTRAN), an eNB using the LTE protocol for Evolved UTRAN (E-UTRAN), or a Bluetooth protocol for WLAN. Beacon. For example, in a 4G Evolved Packet System (EPS) providing LTE radio access to UE 105, the RAN may include an E-UTRAN, which may include base stations with eNBs supporting LTE radio access. The core network for the EPS may include an Evolved Packet Core (EPC). The EPS may then include an E-UTRAN plus an EPC, where the E-UTRAN corresponds to NG-RAN 235 and the EPC corresponds to Figure 2 The method and techniques described herein for obtaining the town location of UE 105 can be applied to other such networks.

[0049] The gNB 210 and ng-eNB 214 can communicate with the AMF 215, which in turn communicates with the LMF 220 for positioning functions. The AMF 215 can support the mobility of UE 105, including cell changes and handovers from access nodes 210, 214, or 216 of the first RAT to access nodes 210, 214, or 216 of the second RAT. The AMF 215 can also participate in supporting signaling connections to UE 105 and possible data and voice bearers for UE 105. When UE 105 accesses NG-RAN 235 or WLAN 216, LMF 220 can use the CP location solution to support UE 105's positioning, and can 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 called Time Difference of Arrival (TDOA) in NR), Real-Time Kinematics (RTK), Precise Point Positioning (PPP), Differential GNSS (DDNSS), Enhanced Cell ID (ECID), Angle of Arrival (AoA), Angle of Departure (AoD), WLAN positioning, Round-Trip Propagation Delay (RTT), Multi-Cell RTT, and / or other positioning procedures and methods. LMF 220 can also handle location service requests from UE 105, such as those received from AMF 215 or GMLC 225. LMF 220 can connect to AMF 215 and / or GMLC 225. In some embodiments, networks such as 5GCN 240 may additionally or alternatively implement other types of location support modules, such as Evolved Services Mobile Location Center (E-SMLC) or SUPL Location Platform (SLP). It should be noted that in some embodiments, at least some positioning functions (including the determination of the location of UE 105) may be performed at UE 105 (e.g., by measuring downlink PRS (DL-PRS) signals transmitted by radio nodes such as gNB 210, ng-eNB 214, and / or WLAN 216, and / or by using auxiliary data provided to UE 105 (e.g., by LMF 220).

[0050] Gateway Mobile Location Center (GMLC) 225 can support location requests from UE 105 received from external client 230 and can forward such location requests to AMF 215, which in turn forwards them to LMF 220. Location responses from LMF 220 (e.g., containing location estimates for UE 105) can similarly be returned to GMLC 225, either directly or via AMF 215, and then GMLC 225 can return the location response (e.g., containing location estimates) to external client 230.

[0051] Network Exposure Function (NEF) 245 can be included in 5G CN 240. NEF 245 can support the secure exposure of capabilities and events related to 5G CN 240 and UE 105 to an external client 230; this can be referred to as an Access Function (AF), and it enables the secure provision of information from the external client 230 to 5G CN 240. NEF 245 can connect to AMF 215 and / or GMLC 225 to obtain the location of UE 105 (e.g., town location) and provide this location to the external client 230.

[0052] like Figure 2 As further shown, the LMF 220 can use the NR Positioning Protocol Annex (NRPPa) defined in 3GPP Technical Specification (TS) 38.445 to communicate with the gNB 210 and / or the ng-eNB 214. NRPPa messages can be transmitted between the gNB 210 and LMF 220 and / or between the ng-eNB 214 and LMF 220 via the AMF 215. Figure 2 As further shown, the LMF220 and UE 105 can communicate using the LTE Positioning Protocol (LPP) defined in 3GPP TS 37.355. Here, LPP messages can be transmitted between UE 105 and the LMF 220 via the AMF 215 and the serving gNB 210-1 or serving ng-eNB 214 for UE 105. For example, LPP messages can be transmitted between the LMF 220 and AMF 215 using service-based operations (e.g., based on Hypertext Transfer Protocol (HTTP)), and can also be transmitted between the AMF 215 and UE 105 using the 5G NAS protocol. The LPP protocol can be used to support positioning of UE 105 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 can be used to support the location of UE 105 using network-based location methods (such as ECID, AoA, uplink TDOA (UL-TDOA)), and / or can be used by LMF 220 to obtain location-related information from gNB 210 and / or ng-eNB 214, such as defining parameters of DL-PRS transmissions from gNB 210 and / or ng-eNB 214.

[0053] When UE 105 accesses WLAN 216, LMF 220 can obtain the location of UE 105 using NRPPa and / or LPP in a manner similar to that described above when UE 105 accesses gNB 210 or ng-eNB 214. Therefore, NRPPa messages can be transmitted between WLAN 216 and LMF 220 via AMF 215 and N3IWF 250 to support network-based positioning of UE 105 and / or to transmit other location information from WLAN 216 to LMF 220. Alternatively, NRPPa messages can be transmitted between N3IWF 250 and LMF 220 via AMF 215 to support network-based positioning of UE 105 based on location-related information and / or location measurements transmitted from N3IWF 250 to LMF 220 using NRPPa, which is known or accessible to N3IWF 250. Similarly, LPP and / or LPP messages can be transmitted between UE 105 and LMF 220 via AMF 215, N3IWF 250 and the service WLAN 216 for UE 105 to support UE-assisted or UE-based positioning of UE 105 by LMF 220.

[0054] In the 5G NR positioning system 200, the positioning method can be categorized as "UE-assisted" or "UE-based." This may depend on where the request to determine the location of UE 105 originates. For example, if the request originates from the UE (e.g., from an application or "app" executed by the UE), the positioning method can be classified as UE-based. On the other hand, if the request originates from an external client or other devices or services within the AF230, LMF 220, or 5G network, the positioning method can be classified as UE-assisted (or "network-based").

[0055] Using a UE-assisted positioning method, UE 105 can obtain location measurements and send them to a location server (e.g., LMF 220) to calculate a location estimate for UE 105. For RAT-dependent positioning methods, location measurements may include one or more of the following for one or more access points: Received Signal Strength Indicator (RSSI), Round-Trip Time (RTT), Reference Received Power (RSRP), Reference Received Quality (RSRQ), Reference Time Difference (RSTD), Time of Arrival (TOA), AoA, Receive Time Transmission Time Difference (Rx-Tx), Differential AoA (DAoA), AoD, or Timing Advancement (TA). Additionally or alternatively, similar measurements may be performed on sidelink signals transmitted by other UEs, which, if their locations are known, can serve as anchor points for the positioning of UE 105. Location measurements may also include, or alternatively, measurements using location methods independent of RAT (such as GNSS (e.g., GNSS pseudorange, GNSS code phase, and / or GNSS carrier phase of GNSS satellite 110), WLAN, etc.).

[0056] Using a UE-based positioning method, UE 105 can obtain location measurements (e.g., which may be the same as or similar to location measurements from a UE-assisted positioning method), and can also calculate the location of UE 105 (e.g., by means of auxiliary data received from a location server such as LMF220, SLP, or broadcast by gNB 210, ng-eNB 214, or WLAN 216).

[0057] 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., RSSI, RTT, RSRP, RSRQ, AoA, or TOA) of signals transmitted by UE 105, and / or, in the case of N3IWF 250, can receive measurements obtained by UE 105 or by APs in WLAN 216, and can send the measurements to a location server (e.g., LMF 220) to calculate the location estimate of UE 105.

[0058] Depending on the type of signal used for positioning, the positioning of UE 105 can also be classified as UL-based, DL-based, or DL-UL-based. For example, if positioning is based solely on signals received by UE 105 (e.g., from a base station or other UEs), positioning can be classified as DL-based. On the other hand, if positioning is based solely on signals transmitted by UE 105 (e.g., which can be received by a base station or other UEs), positioning can be classified as UL-based. DL-UL-based positioning includes positioning based on signals transmitted and received by UE 105, such as RTT-based positioning. Sidelink (SL) assisted positioning includes signals transmitted between UE 105 and one or more other UEs. According to some embodiments, the UL, DL, or DL-UL positioning described herein can use SL signaling as a supplement to or replacement of SL, DL, or DL-UL signaling.

[0059] Depending on the type of positioning (e.g., UL-based, DL-based, or DL-UL-based), the type of reference signal used can vary. For example, for DL-based positioning, these signals may include PRS (e.g., DL-PRS transmitted by the base station or SL-PRS transmitted by other UEs), which can be used for TDOA, AoD, and RTT measurements. Other reference signals that can be used for positioning (UL, DL, or DL-UL) may include probe reference signals (SRS), channel state information reference signals (CSI-RS), synchronization signals (e.g., synchronization signal block (SSB) synchronization signal (SS)), physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), physical side-link shared channel (PSSCH), demodulation reference signals (DMRS), etc. Furthermore, reference signals may be transmitted in a Tx beam and / or received in an Rx beam (e.g., using beamforming techniques), which may affect angle measurements such as AoD or AoA.

[0060] The information provided to the LMF220 by the gNB 210 and / or ng-eNB 214 using the New Radio Positioning Protocol (NRPPa) may include location coordinates and timing and configuration information for PRS transmissions. The LMF 220 may then provide some or all of this information to the UE 105 as supplementary data in the LPP message via the NG-RAN 235 and 5G CN 240.

[0061] Depending on the intended function, the LPP message sent from LMF 220 to UE 105 can instruct UE 105 to do any of a variety of things. For example, the LPP message can contain instructions to enable UE 105 to obtain measurements of GNSS (or A-GNSS), WLAN, OTDOA, and / or ECID (or some other positioning method). In the case of OTDOA, the LPP message can instruct UE 105 to obtain one or more measurements (e.g., Reference Signal Time Difference (RSTD) measurements) of PRS signals transmitted within a specific cell supported by a specific gNB 210 and / or ng-eNB 214 (or supported by some other type of base station such as eNB or Wi-FiAP). RSTD measurements can include the time difference between the arrival of a signal (e.g., a PRS signal) transmitted or broadcast by one gNB 210 and a similar signal transmitted by another gNB 210 at UE 105. UE 105 can send measurements back to LMF 220 via service gNB 210-1 (or service ng-eNB214) and AMF215 in an LPP message (e.g., within a 5G NAS message).

[0062] As noted, although the communication system 200 is described as involving 5G technology, the communication system 200 can be implemented to support other communication technologies, such as GSM, WCDMA, LTE, etc., for supporting and interacting with mobile devices such as UE 105 (e.g., to perform voice, data, location, and other functions). In some such embodiments, the 5G CN 240 can be configured to control different air interfaces. For example, in some embodiments, NG-RAN 235 and 5G CN 240 can be replaced by other RANs and other core networks. For example, in EPS, NG-RAN 235 can be replaced by E-UTRAN containing eNBs, and 5G CN 240 can be replaced by EPC containing a Mobility Management Entity (MME) to replace AMF 115, an E-SMLC to replace LMF 220, and a GMLC similar to GMLC 225. In such EPS, the E-SMLC can use LPPa instead of NRPPa to send and receive location information from the eNBs in the E-UTRAN, and LPP can be used to support the location of UE 105. In these other embodiments, the general location process and methods for UE 105 can be supported in a manner similar to that described herein for 5G networks, except that the functions and processes described herein for gNB210, ng-eNB 214, AMF 215 and LMF 220 can be applied in some cases to other network elements, such as eNB, Wi-Fi AP, MME and E-SMLC.

[0063] To support specific positioning methods (such as OTDOA and transmission or PRS or other signals used for positioning of UE 105), base stations can be synchronized. In a synchronized network, the transmission timing of gNB 210 can be synchronized so that each gNB 210 has the same transmission timing as each other gNB 210 to achieve high accuracy, for example, 50 nanoseconds or less. Alternatively, gNB 210 can be synchronized at the radio frame or subframe level so that each gNB 210 transmits radio frames or subframes for the same duration as each other gNB 210 (e.g., such that the time at which each gNB 210 begins and finishes transmitting radio frames or subframes is almost exactly the same as each other gNB 210), but not necessarily maintaining the same count or numbering for radio frames or subframes. For example, while one gNB210 transmits a subframe or radio frame with a count or number of zero (which may be the first radio frame or subframe in a periodic repeating sequence of radio frames or subframes), another gNB210 may transmit radio frames or subframes with different numbers or counts (such as one, ten, one hundred, etc.).

[0064] Synchronization of the transmission timing of the ng-eNB 214 in NG-RAN 235 can be supported in a manner similar to that of the gNB 210, although the ng-eNB 214 may not always be synchronized with the gNB 210 because the ng-eNB 214 may typically use a different frequency than the gNB 210 (to avoid interference). Synchronization between the gNB 210 and the ng-eNB 214 can be achieved by using a GPS or GNSS receiver in each gNB 210 and ng-eNB 214, or by other means such as using the IEEE 1588 Precision Time Protocol.

[0065] Figure 3 This illustrates a simplified information exchange during an LPP location session. LPP sessions are used between a location server and a target device to obtain location-related measurements or location estimates, or to transmit auxiliary data. A single LPP session is used to support a single location request (e.g., for a single Mobile Terminal Location Request (MT-LR), Mobile Initiated Location Request (MO-LR), or Network Induced Location Request (NI-LR)). Multiple LPP sessions can be used between the same endpoints to support multiple different location requests (as required by TS 23.271).

[0066] Each LPP session consists of one or more LPP transactions, and each LPP transaction performs a single operation (capability exchange, auxiliary data transmission, or location information transmission). In E-UTRAN and NG-RAN, LPP transactions are implemented as LPP procedures.

[0067] The initiator of an LPP session can initiate the first LPP transaction, but subsequent transactions can be initiated by any endpoint. LPP transactions within a session can occur consecutively or in parallel. LPP transactions are indicated at the LPP protocol layer with transaction IDs to associate messages with each other (e.g., requests and responses).

[0068] The LPP process does not require it to occur in any fixed order, in order to provide greater flexibility in positioning. Therefore, the UE can request auxiliary data at any time to comply with previous location measurement requests from the LMF; if the location results from previous requests are insufficient to meet the requested QoS, the LMF can initiate more than one location information request (e.g., measurement or location estimation); and, if not yet executed, the target device can transmit capability information to the server at any time.

[0069] Although LPP allows for flexibility, it is expected that the process will generally occur in the following order: (1) capability transfer, (2) auxiliary data transfer, and (3) location information (measurement and / or location estimation) transfer.

[0070] Using the procedures defined in this specification, the positioning process in NG-RAN is modeled as a transaction of the LPP protocol. The process consists of individual operations of the following types: positioning capability exchange, auxiliary data transmission, location information (positioning measurement and / or positioning estimation) transmission, error handling, or abort.

[0071] During a location session, for example, the UE has received a "Request Location" message and should send back a "Provide Location" message.

[0072] like Figure 3 As shown in 310, the server (e.g., LMF 220) sends a RequestLocationInformation message to the target (e.g., UE 105). The RequestLocationInformation message can indicate the type of location information required. In various embodiments, the RequestLocationInformation message can indicate one or more QoS parameters of the requested location information.

[0073] In step 320, UE105 sends a ProvideLocationInformation message to LMF 220 to transmit location information. The transmitted location information should match, or be a subset of, the location information requested in step 310, unless LMF 220 explicitly allows additional location information. If step 330 does not occur, this message can set endTransaction IE to TRUE.

[0074] If the request is made in step 320, the target sends an additional ProvideLocationInformation message to the server to transmit location information. The transmitted location information should match, or be a subset of, the location information requested in step 310, unless LMF 220 explicitly permits additional location information. The final message may include an endTransaction IE set to TRUE.

[0075] In such Figure 3 During the location session shown, QoS parameters can be updated before each LPP location session. If UE 105 is configured to update QoS parameters, the LPP location session needs to be restarted. Restarting introduces unwanted latency into the location system.

[0076] During an LPP positioning session, certain situations may require higher accuracy. For example, an autonomous vehicle may need to navigate from a residential street into a congested parking lot. Parking lots may require higher horizontal accuracy to precisely maneuver the vehicle into a parking space. Higher accuracy may require more processing demands, radio receiver resources, or power resources. Other situations may exist where the UE 105 is entering a power-saving mode and, during this mode, QoS parameters cannot be met. Dynamic LPP positioning sessions allow users to adjust one or more QoS parameters without the inherent latency of starting a new LPP positioning session and reconfiguring everything.

[0077] Figure 4 This illustrates an example information exchange during a dynamic LPP location session. UE 105 can send updated UE capabilities, or it can send UE capabilities that have expired due to timers, or UE capabilities that may differ over different durations of the location session. LMF 220 can send updated "Request Location" and / or updated "Auxiliary Data". All of this can be done before UE 105 is expected to send back a new / additional / updated "Provide Location" response message.

[0078] In a dynamic LPP positioning session, the UE can be configured to meet updated QoS capabilities during the LPP positioning session. The LPP positioning session does not require a restart, thus saving any latency required for a restart. In 410, the LMF 220 can send a location request message to the UE 105 to request location information. This location request message can indicate the type of location information required and provide (1) an option for one or more associated QoS parameters to be used for the positioning session or (2) no QoS parameter indication. Some embodiments may include a third option, wherein the location request message includes notification that QoS parameters can be adjusted during the LPP positioning session, without indicating one or more associated QoS parameters.

[0079] For option (1), LMF 220 may indicate QoS parameters that may be adjusted during the LPP location session. In addition to QoS parameters, some embodiments may allow LMF 220 to optionally enumerate one or more possible values ​​for one or more QoS parameters. For example, LMF 220 may include the QoS parameter responseTime in the location request message sent at 410, and may also indicate that the value of the QoS parameter can be selected from a set of items: {100ms, 1 second, 10 seconds}. Subsequently, LMF 220 may send another message to UE 105 indicating that the value 100ms is selected (e.g., the selection indication at 415 discussed below). By indicating QoS parameters and (optionally) one or more values ​​of one or more QoS parameters, embodiments allow UE 105 to budget its processing and power resources accordingly.

[0080] Under option (2), the QoS parameters are set for the LPP location session, and there is no option to adjust them during the LPP location session.

[0081] UE 105 can receive messages from a server (e.g., LMF 220). In 415, as... Figure 2 The server or serving gNB 220 shown can send a first message indicating the selection of one or more QoS parameters. Alternatively, the server (e.g., LMF 220) or serving gNB can configure entirely new QoS requests. QoS determination can occur with Download Control Information (DCI) or with Media Access Control (MAC) commands (low-layer reports). In 420, UE 105 can send a response message to the server (e.g., LMF 220) including requested location information based on the updated QoS parameters. In 425, UE 105 can receive a second message indicating the selection of one or more QoS parameters. The QoS parameters can be the same as those selected in the first message. For example, the server can request increased horizontal accuracy in dense parking areas, and at a later point in time (e.g., when the vehicle is on a highway), the server can request decreased horizontal accuracy to conserve system resources because high accuracy is no longer needed on the highway compared to parking areas. In some embodiments, the second message can indicate the selection of parameters different from those in the first message. In step 435, UE 105 can send a response message including the requested location information to the server (e.g., LMF 220) based on the updated QoS parameters. In step 440, UE 105 can continue to send the requested location information.

[0082] UE 105 can be configured with multiple values ​​for the following QoS parameters: horizontalAccuracy, verticalCoordinateRequest, verticalAccuracy, responseTime, velocityRequest, timeNB, horizontalAccuracyExt, and / or verticalAccuracyExt. These parameters are examples and are not limiting. Additional QoS parameters not listed can be configured during a dynamic positioning session. In the case of measurement, assuming the measurement is the only source of error, some subfields can be applied to the location estimate that can be obtained by the server from the measurement provided by the target device. Depending on the desired functionality, QoS parameters may include multiple subfields. The following paragraphs provide a description of the parameters.

[0083] The HorizontalAccuracy parameter indicates the maximum horizontal error of the location estimate at the indicated confidence level. “Accuracy” can correspond to the coding uncertainty defined in TS 23.032

[15] , and “confidence level” can correspond to the confidence level defined in TS23.032

[15] .

[0084] The VerticalCoordinateRequest parameter indicates whether the vertical coordinate is required (TRUE) or not (FALSE).

[0085] The VerticalAccuracy parameter indicates the maximum vertical error of the position estimate at the specified confidence level and applies only when vertical coordinates are requested. “Accuracy” may correspond to the coding uncertainty height defined in TS 23.032

[15] and “Confidence” may correspond to the confidence level defined in TS 23.032

[15] .

[0086] The `responseTime` parameter indicates the maximum response time measured between receiving the `RequestLocationInformation` and sending the `ProvideLocationInformation`. If the unit field is not present, it is given in integer seconds between 1 and 128. If the unit field is present, the maximum response time is given in units of 10 seconds between 10 seconds and 1280 seconds. If the `periodicalReporting` IE is included in `CommonIEsRequestLocationInformation`, this field should not be included by the location server and should be ignored by the target device (if included).

[0087] The `responseTimeEarlyFix` parameter indicates the maximum response time measured between receiving the `RequestLocationInformation` and sending a `ProvideLocationInformation` containing early location measurements or early location estimates. If the unit field is not present, it is given in integer seconds between 1 and 128. If the unit field is present, the maximum response time is given in 10-second units between 10 and 1280 seconds. When this IE is included, the target should send a `ProvideLocationInformation` (or more than one `ProvideLocationInformation` if the location information cannot be contained in a single message) containing early location information according to the `responseTimeEarlyFix` IE, and a subsequent `ProvideLocationInformation` (or more than one `ProvideLocationInformation` if the location information cannot be contained in a single message) containing final location information according to the `time` IE. If the early location information is unavailable when the time value in the `responseTimeEarlyFix` IE expires, the target may omit sending the `ProvideLocationInformation`. The server should set the responseTimeEarlyFix IE to a value less than the time IE. If the responseTimeEarlyFix IE value is not less than the time IE value, the target should ignore it. The responseTimeEarlyFix parameter unit indicates the unit of the responseTimeEarlyFix field and the time. The enumerated value "10 seconds" corresponds to a resolution of 10 seconds. If this field does not exist, the unit / resolution is 1 second.

[0088] The velocityRequest parameter indicates whether a speed (or a speed-related measurement) is requested (TRUE) or not requested (FALSE).

[0089] If the CommonIEsRequestLocationInformation includes a periodicalReporting IE or a responseTime IE, this field should not be included by the location server and should be ignored by the target device (if included). For periodic reporting, dynamically adjusting QoS may be more important because LPP location sessions can continue until termination (e.g., without discrete end times). During initial configuration, the system can indicate potential QoS configuration restrictions that can be requested during an LPP location session.

[0090] The `timeNB` parameter indicates the maximum response time measured between receiving the `RequestLocationInformation` and sending the `ProvideLocationInformation`. If the unit field is not present, it is given in integer seconds between 1 and 512. If the unit field is present, the maximum response time is given in units of 10 seconds between 10 seconds and 5120 seconds.

[0091] The `responseTimeEarlyFixNB` parameter indicates the maximum response time measured between receiving the `RequestLocationInformation` and sending a `ProvideLocationInformation` containing early location measurements or early location estimates. If the unit field is not present, it is given in integer seconds between 1 and 512. If the unit field is present, the maximum response time is given in 10-second units between 10 and 5120 seconds. When this IE is included, the target should send a `ProvideLocationInformation` containing early location information (or more than one `ProvideLocationInformation` if the location information cannot be contained in a single message) according to the `responseTimeEarlyFixNB` IE, and a subsequent `ProvideLocationInformation` containing final location information (or more than one `ProvideLocationInformation` if the location information cannot be contained in a single message) according to the `timeNB` IE. If the early location information is unavailable when the time value in the `responseTimeEarlyFixNB` IE expires, the target should omit sending the `ProvideLocationInformation`. The server should set responseTimeEarlyFixNBIE to a value less than timeNBIE. If the value of responseTimeEarlyFixNBIE is not less than the value of timeNBIE, the target should ignore it.

[0092] The `unitNB` parameter indicates the units for the `timeNB` and `responseTimeEarlyFixNB` fields. The enumeration value 'ten seconds' corresponds to a resolution of 10 seconds. If this field does not exist, the unit / resolution is 1 second.

[0093] The `horizontalAccuracyExt` parameter indicates the maximum horizontal error of the location estimate at the indicated confidence level. "accuracyExt" corresponds to the high accuracy uncertainty defined in TS 23.032

[15] , and "confidence level" corresponds to the confidence level defined in TS 23.032

[15] . If the `horizontalAccuracy` field is included in the QoS, it should not be included by the location server and should be ignored by the target device.

[0094] The `verticalAccuracyExt` parameter indicates the maximum vertical error of the location estimate at the indicated confidence level and applies only when vertical coordinates are requested. "AccuracyExt" corresponds to the coded high-accuracy uncertainty defined in TS 23.032

[15] , and "confidence level" corresponds to the confidence level defined in TS 23.032

[15] . If the `verticalAccuracyExt` field is included in the QoS, it should not be included by the location server and should be ignored by the target device.

[0095] The target device should strive to meet all QoS requirements, but if some QoS requirements cannot be met, a response indicating that not all QoS requirements are met is permitted. The only exceptions are time and timeNB, which should always be satisfied, even if it means disqualifying other QoS requirements.

[0096] Target devices supporting NB-IoT access should support responseTimeNB IE. Target devices supporting HA GNSS should support the HorizontalAccuracyExt, VerticalAccuracyEx, and unit fields. Target devices supporting both NB-IoT access and HA GNSS should support the unitNB field.

[0097] Having multiple values ​​(or multiple QoS containers) for QoS parameters may only apply to periodic location sessions (periodicalReporting is ON) or when reportAmount is set to "unlimited / indeterminate".

[0098] The target device (e.g., UE 105) can obtain all QoS requirements as much as possible, but if some QoS requirements cannot be met, the target device can return a response indicating that not all QoS requirements are met. For example, if LMF 220 selects a horizontal accuracy of 5 meters, and due to system or signal resources, only a horizontal accuracy of 10 meters is possible, the system can provide location data with a horizontal accuracy of 10 meters. In various embodiments, the only exception can be time and timeNB, which can be satisfied even if it means that other QoS requirements are not met.

[0099] Figure 5 The second example information exchange in a dynamic LPP location session is shown. Similarly, the target device (e.g., UE 105) can obtain all QoS requirements as much as possible, but if some QoS requirements cannot be met, the target device can return a response that does not meet all QoS requirements. The only exceptions are time and timeNB, which can be satisfied, even if this means disqualifying other QoS requirements. QoS parameters can include, for example: horizontalAccuracy, verticalCoordinateRequest, verticalAccuracy, responseTime, velocityRequest, timeNB, horizontalAccuracyExt, and / or verticalAccuracyExt, which can include information as described above.

[0100] In step 510, UE 105 may receive messages from a server (e.g., LMF 220). In step 515, UE 105 may send a first message to LMF 220 indicating a set of one or more requested QoS parameters. In various embodiments, the server (i.e., LMF 220) may select QoS parameters based on the one or more requested QoS parameters indicated by UE 105 in the message set in step 515, and may also include the selection in a response message to UE 105 (not shown), which may occur with Download Control Information (DCI) or with Media Access Control (MAC) Command Element (CE) command (low-layer report). In various embodiments, DCI-type requests may occur within the same time slot or half a millisecond. In various embodiments, changes to the Media Access Control Command Element (MAC-CE) may take 3 milliseconds. Either request may be much faster than the time required to establish a new LPP positioning session (e.g., 100 milliseconds). In step 520, UE 105 may send a response message including the requested location information to the server (e.g., LMF 220) based on the updated QoS parameters. In step 525, UE 105 may send a second message indicating a new set of one or more requested QoS parameters. These QoS parameters may be the same as those selected in the first message. For example, the server may request an increase in horizontal accuracy for densely parked areas, and at a later point in time (e.g., when vehicles are on a highway), the server may request a decrease in horizontal accuracy to conserve system resources, since high accuracy is no longer needed on the highway compared to parking areas. In some embodiments, the second message may indicate a different selection of parameters than the first message. In step 530, UE 105 may send a response message including the requested location information to the server (e.g., LMF 220) based on the updated QoS parameters. In step 535, UE 105 may continue sending the requested location information.

[0101] Knowing the location of a terminal, such as a cellular phone, is typically desired. For example, in the case of an emergency service call, a Location Services (LCS) client may want to know the location of the terminal or provide services to the terminal's user, such as navigation assistance or direction finding. In this document, the terms "location" and "positioning" are synonymous and can be used interchangeably. In OTDOA-based positioning, a mobile station can measure the time difference of signals received from multiple base stations. Because the positions of the base stations are known, the observed time differences can be used to calculate the terminal's location. To further aid in location determination, a Positioning Reference Signal (PRS) is typically provided by the base station (BS) to improve OTDOA positioning performance. The measured time difference of arrival of the PRS measured from a reference cell (e.g., the serving cell) and one or more neighboring cells is called the Reference Signal Time Difference (RSTD). By using RSTD measurements, the absolute or relative transmission times of each cell, and the known positions of the BS physical transmit antenna elements of the reference cell and neighboring cells, the UE's position can be calculated.

[0102] Technologies supporting reliable and high-speed data services include Orthogonal Frequency Division Multiplexing (OFDM) and Multiple-Input Multiple-Output (MIMO). An OFDM system converts cascaded received symbols into N parallel symbols (N is a natural number) and transmits these N parallel symbols on their respective N subcarriers. These subcarriers maintain orthogonality in the frequency domain. MIMO technology can be used to improve the efficiency of data transmission and reception by employing multiple transmit and receive antennas. MIMO techniques include spatial multiplexing, transmit diversity, and beamforming. The MIMO channel matrix, based on the number of receive and transmit antennas, can be decomposed into several independent channels. Each independent channel is called a layer or stream. The number of layers is called the rank.

[0103] A transceiver capable of sending PRS information can be configured to assign different Physical Antenna Port (PAP) identifiers (IDs) to each of the multiple Physical Transmit Antenna Elements serving a single cell; and to generate multiple PRS sequences, each PRS sequence corresponding to a different Physical Transmit Antenna Element among the multiple Physical Transmit Antenna Elements, wherein each PRS sequence has a corresponding frequency shift based at least in part on the corresponding PAP ID(h) of the corresponding Physical Transmit Antenna Element. Therefore, the PRS is divided into different frequency layers. Each frequency layer can have one or more associated QoS parameters. UE 105 can request different QoS parameters for different Position Reference Signal (PRS) frequency layers.

[0104] Figure 6 This illustrates a third example of information exchange in a dynamic LPP location session. Figure 6The illustrated example information exchange may include device-to-device (D2D) communication between multiple user equipment (UE) devices 105-1, 105-2. Device-to-device (D2D) communication is expected to play a significant role in future cellular networks because it promises ultra-low latency communication between users. D2D communication may include ranging sessions between devices. QoS parameters of the ranging session can be adjusted during the ranging session.

[0105] By using D2D communication, large amounts of data can be rapidly transferred between mobile devices over short distances. D2D communication can efficiently support local data services through unicast, multicast, and broadcast transmissions. Example applications include the following projects: information sharing, data and compute transfer, coverage extension, and machine-to-machine (M2M) communication.

[0106] Compared to traditional cellular channels, UEs can utilize D2D links to transmit files, audio, and video at higher data rates and lower energy consumption. These links facilitate streaming services such as Google Chromecast and IPTV by forming clusters and multicasting data within them. They also support other short-range services, such as public safety. D2D links can operate unimpeded in disaster-stricken areas where all BS (Browser and Server) systems are down.

[0107] Data and computation transfer can be achieved using a device with a strong internet connection, which can act as a hotspot for data transfer / caching from the BS to it, and other devices can download data from this device using the D2D link. UEs with limited processing power or low energy budgets can also use the D2D link to offload computationally intensive tasks to nearby UEs with greater capabilities.

[0108] In coverage extension, (e.g., at the cell edge or in disaster-stricken areas) UEs may encounter poor signal quality when connecting to a base station. However, a UE closer to the base station with a better link can act as its relay. Relays can be used to extend cellular service coverage and enable multi-hop communication.

[0109] Another method to improve receiver signal strength is through multiple parallel path relays, each consisting of cooperating devices. These techniques can be referred to as cooperative diversity techniques.

[0110] Machine-to-machine (M2M) communication is an implementation technology for the Internet of Things (IoT). It involves autonomous connectivity and communication between a wide range of devices, from embedded low-power devices to powerful, compute-intensive devices. Device-to-device (D2D) connections can be used to establish M2M communication in the IoT because they offer ultra-low latency and corresponding real-time responses. One specific application is vehicle-to-vehicle (V2V) communication, where D2D links can be used to quickly share information and efficiently transfer traffic between neighboring vehicles. They can also be used for vehicle-to-infrastructure and vehicle-to-pedestrian communication.

[0111] Base stations or gNBs connected to the Evolved Packet Core (EPC) and named in 3GPP can communicate directly with the UE using cellular communication. Alternatively, the UE can communicate via a direct D2D link. In terms of channel architecture, a direct link between two UEs is called a sidelink, which can operate via frequency division duplex or time division duplex. Upon startup, the UE first synchronizes with the gNB or other UEs.

[0112] exist Figure 6 In configuration 610, a server (e.g., LMF 220) can send a message to each of user units (UEs) 105-1 and 105-2. This message may include configuration information for a positioning session between UEs 105-1 and 105-2. For example, the server (e.g., LMF 220) may identify UEs 105-1 and 105-2 as vehicles. The server may set QoS (e.g., horizontal accuracy of 1 meter per 10 milliseconds) for ranging between UEs 105-1 and 105-2.

[0113] In 610, the first UE 105-1 can receive a message requesting location information from the second UE 105-2. Alternatively, in 610, the second UE 105-2 can receive a message requesting location information from the first UE 105-1. This message can be transmitted via a side link.

[0114] In various embodiments, at 615, the second UE 105-2 may send a first message to the first UE 105-1 indicating the selection of one or more QoS parameters. Alternatively, the first UE 105-1 may send a message to the second UE 105-2 indicating the selection of one or more QoS parameters. For example, the second UE 105-2 may request higher horizontal accuracy, such as half-meter accuracy. Therefore, the message would include a request for adjusting for higher horizontal accuracy.

[0115] In step 620, the first UE 105-1 can send a response message including requested location information to the second user equipment UE 105-2 based on updated QoS parameters. Alternatively, the second UE 105-2 can send a response message including requested location information to the first UE 105-1 based on updated QoS parameters. The response message can be sent via a side link.

[0116] In 630, the first UE 105-1 can receive a second message from the second UE 105-2 indicating the selection of one or more QoS parameters. The QoS parameters may be the same as those selected in the first message. For example, the server may request an increase in horizontal accuracy for dense parking areas, and at a later point in time (e.g., when vehicles are on a highway), the server may request a decrease in horizontal accuracy to conserve system resources, since high accuracy is no longer needed on the highway compared to parking areas. In some embodiments, the second message may indicate the selection of parameters different from those in the first message. Alternatively, in 630, the second UE 105-2 can receive a second message from the first UE 105-1 indicating the selection of one or more QoS parameters.

[0117] In 635, the first UE 105-1 can send a second response message including requested location information to the second UE 105-2 based on updated QoS parameters. Alternatively, the second UE 105-2 can send a second response message including requested location information to the first UE 105-1 based on updated QoS parameters.

[0118] In 640, the first UE 105-1 can continue to send the requested location information to the second UE 105-2. Alternatively, in 640, the second UE 105-2 can continue to send the requested location information to the first UE 105-1.

[0119] Figure 7 This is a flowchart of an example process 700 of a technique for dynamically configuring one or more Quality of Service (QoS) parameters during a location session performed at a user equipment, according to an embodiment. In various embodiments, the location session may be an LTE Location Protocol (LPP) location session. In some embodiments, Figure 7 One or more process blocks can be executed by UE 105. In some implementations, Figure 7 One or more process frames can be executed by another device or a group of devices that are separate from or include UE 105. Example components of UE 105 are shown in... Figure 9 As shown in the figure, and discussed below.

[0120] In 710, process 700 may include receiving a location request message from a network entity. The network entity may be a server (e.g., such as...). Figure 2 As shown in LMF 220), the location request message identifies multiple QoS parameters of the location session. As described above, for example, UE 105 (e.g., using processor 910, memory 960, input device 970, output device 915, communication interface 930, GNSS receiver 980, GNSS antenna 982, etc.) can obtain data from a server (e.g.). Figure 2 The network entity (LMF 220) shown receives a location request message. (See previous reference...) Figure 6 As described, the network entity may also include another user equipment. In some implementations, the location request message identifies multiple QoS parameters for the location session. Example QoS parameters are as described above.

[0121] In 720, process 700 may include obtaining the selection of one or more QoS parameters for a positioning session. As described above, for example, UE 105 (e.g., using processor 910, memory 960, input device 970, output device 915, communication interface 930, GNSS receiver 980, GNSS antenna 982, etc.) may receive the selection of one or more QoS parameters for a positioning session. A network entity (e.g., LMF 220) may receive service requests from some external clients that are positioning requests for a specific use case (e.g., an E911 call). In terms of accuracy, an E911 call has relatively low requirements (e.g., horizontal accuracy of 50 meters), while the accuracy or latency requirements may be different if the request is for business requirements (or specific applications, such as Google Maps). LMF 220 may receive multiple requests, each associated with a different QoS. LMF 220 may then configure multiple such QoS. Alternatively, an app (or client) requiring a specific QoS may be present at UE 105. Then, UE 105 can request specific QoS based on these internal requests.

[0122] Process 700 may include using at least one of downlink control information (DCI) and MAC-CE commands to determine one or more QoS parameters for a location session.

[0123] As previously described, one or more QoS parameters may include one or more enumerated values ​​(or multiple QoS containers) that can be selected during a location session. According to some embodiments, having multiple values ​​for the QoS parameters can be suitable for periodic location sessions. For example, periodic reporting can occur when periodicReporting is ON, or when reportingAmount is set to “unlimited / indeterminate”.

[0124] One or more QoS parameters can specify layer-specific QoS parameters for one or more frequency layers of the Positioning Reference Signal (PRS).

[0125] In 730, process 700 may include: sending a location response message to a network entity, wherein the location response message: (i) is generated at least in part based on selected QoS parameters, and (ii) indicates the UE's configuration, which is made based on one or more selected QoS parameters. For example, the UE may receive a QoS selection from the network entity (as shown in the box in 720), and may then perform measurements to attempt to satisfy the updated QoS parameters. For example, UE 105 may process more PRS resources per TRP, or process more sets per TRP, or request a different configuration of the measurement interval to attempt to satisfy the updated QoS parameters. UE 105 may activate additional sensors (e.g., if QoS requires vertical accuracy, it may activate a barometer, or request the use of an angle-based approach to attempt to derive vertical accuracy). For example, if a reduced response time is requested, the UE may dedicate more computational resources to processing PRS resources more quickly. As described above, for example, UE 105 (e.g., using processor 910, memory 960, input device 970, output device 915, communication interface 930, GNSS receiver 980, GNSS antenna 982, etc.) can be configured according to one or more selected QoS parameters.

[0126] Location response messages can be generated based on selected QoS parameters. As described above, for example, UE 105 (e.g., using processor 910, memory 960, input device 970, output device 915, communication interface 930, GNSS receiver 980, GNSS antenna 982, etc.) can generate location response messages. Additionally or alternatively, as described herein, UE 105 (e.g., using processor 910, memory 960, input device 970, output device 915, communication interface 930, GNSS receiver 980, GNSS antenna 982, etc.) can send location response messages to network entities.

[0127] Process 700 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein.

[0128] In some implementations, obtaining the selection of one or more QoS parameters involves receiving a selection from a server for selection by the UE. Therefore, in these implementations, obtaining the selection can be performed by the UE 105.

[0129] In some implementations, the location response message includes a QoS feedback parameter indicating the QoS achievable by the UE 105. For example, if the QoS parameter for horizontal accuracy is set to 10 meters, but due to one or more other limitations (i.e., processing bandwidth, receiver signal strength, etc.) only 20 meters of accuracy is possible, the system will return a response indicating 20 meters of accuracy. The response message may include feedback parameters notifying the server or another UE system that only 20 meters of horizontal accuracy can be achieved.

[0130] In some implementations, QoS parameters include: a horizontal accuracy parameter indicating the maximum horizontal error of the location estimate at an indicated confidence level; a vertical coordinate request indicating whether vertical coordinates are required as part of a location response message; a vertical accuracy parameter indicating the maximum vertical error of the location estimate at an indicated confidence level; a response time indicating the maximum time elapsed between receiving a location request message and sending a location response message; a response time early fix parameter indicating the maximum time elapsed between receiving a location request message and sending a location response message containing early location measurements; or a speed request parameter indicating whether speed is requested; or combinations thereof. According to some embodiments, a smaller maximum horizontal error results in more accurate horizontal positioning. The vertical coordinate parameter can be binary, i.e., requested (TRUE) or not requested (FALSE). Regarding the maximum vertical error, a lower maximum vertical error results in more accurate vertical positioning. Regarding the response time early fix parameter, if the unit field is not present, it can be given in integer seconds between 1 and 128. If the unit field is present, the maximum response time can be given in units of 10 seconds between 10 seconds and 1280 seconds. Regarding the speed request parameter, this parameter can be binary, i.e., request (TRUE) or do not request (FALSE).

[0131] although Figure 7 An example block of process 700 is shown, but in some implementations, process 700 may include... Figure 7 The drawn boxes can be more, fewer, different, or arranged differently than other boxes. Alternatively, two or more boxes in process 700 can be executed in parallel.

[0132] Figure 8 This is a flowchart of an example process 800 for dynamically configuring one or more Quality of Service (QoS) parameters during a location session at a network entity, according to an embodiment. The location session may be an LTE Location Protocol (LPP) session. In some implementations, Figure 8 One or more process frames can be executed by a network entity. The network entity can be a server or another user device. In some implementations, Figure 8 One or more process frames can be executed by another device or a group of devices that are separate from or include the network entity.

[0133] In step 810, process 800 may include sending a location request message to UE 105, wherein the location request message identifies multiple QoS parameters of a location session. As described above, for example, a network entity (e.g., using processor 1010, memory 1035, input device 1015, output device 1020, communication subsystem 1030, wireless communication interface 1033, etc.) may send the location request message to UE 105. In some embodiments, as described above, the location request message identifies multiple QoS parameters of a location session.

[0134] In step 820, process 800 may include: obtaining a selection of one or more QoS parameters for a location session. For example, as described above, a network entity (e.g., using processor 1010, memory 1035, input device 1015, output device 1020, communication subsystem 1030, wireless communication interface 1033, etc.) may obtain a selection of one or more QoS parameters for a location session. As shown in the embodiments described above, obtaining a selection of one or more QoS parameters may include sending information indicating one or more QoS parameters for the location session via at least one of downlink control information (DCI) and media access control command unit (MAC-CE). Additionally or alternatively, obtaining a selection of one or more QoS parameters may include receiving a selection from the UE or making a selection using a network entity. Some embodiments may include sending at least one requested QoS parameter to be included in the selection of one or more QoS parameters from the UE to the network entity before obtaining a selection of one or more QoS parameters for the location session.

[0135] In 830, process 800 may include: receiving a location response message to a network entity, wherein the location response message: (i) is generated at least in part based on selected QoS parameters, and (ii) indicates a configuration of the UE made according to one or more selected QoS parameters. As described above, for example, a network entity (e.g., using processor 1010, memory 1035, input device 1015, output device 1020, communication subsystem 1030, wireless communication interface 1033, etc.) may receive a location response message generated by UE 105 according to one or more QoS parameters.

[0136] Process 800 may include additional implementations, such as any single implementation or any combination of implementations described below and / or in conjunction with one or more other processes described elsewhere herein.

[0137] In some implementations, the location response message includes a QoS feedback parameter indicating the QoS achievable by the UE 105. For example, if the QoS parameter for horizontal accuracy is set to 10 meters, but due to one or more other limitations (i.e., processing bandwidth, receiver signal strength, etc.) only 20 meters of accuracy is possible, the system will return a response indicating 20 meters of accuracy. The response message may include feedback parameters notifying the server or another UE that the system can only achieve a horizontal accuracy of 20 meters.

[0138] In some implementations, the location request message specifies layer-specific QoS parameters for one or more frequency layers of the PRS.

[0139] In some implementations, QoS parameters include: a horizontal accuracy parameter indicating the maximum horizontal error of the location estimate at an indicated confidence level; a vertical coordinate request indicating whether vertical coordinates are required as part of a location response message; a vertical accuracy parameter indicating the maximum vertical error of the location estimate at an indicated confidence level; a response time indicating the maximum time elapsed between receiving a location request message and sending a location response message; a response time early fixation parameter indicating the maximum time elapsed between receiving a location request message and sending a location response message containing early location measurements; or a speed request parameter indicating whether speed is requested; or combinations thereof. According to some embodiments, a smaller maximum horizontal error results in more accurate horizontal positioning. The vertical coordinate parameter can be binary, i.e., requested (TRUE) or not requested (FALSE). Regarding the maximum vertical error, a lower maximum vertical error results in more accurate vertical positioning. Regarding the response time early fixation parameter, if the unit field is not present, it can be given in integer seconds between 1 and 128. If the unit field is present, the maximum response time can be given in units of 10 seconds between 10 seconds and 1280 seconds. Regarding the speed request parameter, this parameter can be binary, i.e., request (TRUE) or do not request (FALSE).

[0140] although Figure 8 An example block of process 800 is shown, but in some implementations, process 800 may include... Figure 8 The drawn boxes can be more, fewer, different, or arranged differently than other boxes. Alternatively, two or more boxes in process 800 can be executed in parallel.

[0141] Figure 9 This can be shown as described above (e.g., refer to...). Figures 1 to 8 An embodiment of UE 105 is utilized in a specific manner. For example, UE 105 can perform... Figure 7 The functions of the UE described in the method shown and / or Figure 8The methods described herein refer to one or more of the functions of the network entities. It should be noted that... Figure 9 This is merely to provide a general description of the various components, any or all of which may be used appropriately. It can be noted that in some cases, Figure 9 The components shown can be located to a single physical device and / or distributed among various networked devices that can be arranged in different physical locations. Furthermore, as previously stated, the functionality of the UE discussed in the foregoing embodiments can be provided by… Figure 9 One or more of the hardware and / or software components shown are executed.

[0142] UE 105 is shown as including hardware elements electrically connected (or otherwise appropriately communicated) via bus 905. The hardware elements may include 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 accelerator processors, application-specific integrated circuits (ASICs), etc.), and / or other processing architectures or devices. Processor 910 may include one or more processing units, which may be housed in a single integrated circuit (IC) or multiple ICs. Figure 9 As shown, depending on the desired functionality, some embodiments may have a separate DSP 920. Location 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). UE 105 may also include: one or more input devices 970, which may include, but are not limited to, one or more keyboards, touchscreens, touchpads, 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., touchscreens), light-emitting diodes (LEDs), speakers, etc.

[0143] UE 105 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...). Devices such as IEEE 802.11 devices, IEEE 802.15.4 devices, Wi-Fi devices, WiMAX devices, WAN devices, and / or various cellular devices can enable UE 105 to communicate with other devices described in the above embodiments. As described herein, the wireless communication interface 930 can allow the transmission (e.g., sending and receiving) of data and signaling with 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 devices communicatively coupled to the TRP. 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 is capable of transmitting and receiving wireless signals using beamforming (e.g., Tx beamforming and Rx beamforming). Beamforming can be performed using digital and / or analog beamforming techniques with corresponding digital and / or analog circuitry. The wireless communication interface 930 may include such circuitry.

[0144] 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). UE 105 can communicate with various data networks, including those of various network types. For example, a wireless wide area network (WWAN) may be a 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, etc. A CDMA network may implement one or more RATs, such as... WCDMA, etc. This includes IS-95, IS-2000, and / or IS-856 standards. TDMA networks can implement GSM, Digital Advanced Mobile Phone Systems (D-AMPS), or some other RATs. OFDMA networks can employ LTE, LTE Advanced, 5G NR, etc. 5G NR, LTE, LTE Advanced, GSM, and WCDMA are described in 3GPP documents. This is described in a document from an alliance called "3rd Generation Partnership Project 2" (3GPP2). The 3GPP and 3GPP2 documents are publicly available. The wireless local area network (WLAN) can also be an IEEE 802.11x network, and the wireless personal area network (WPAN) can be a Bluetooth network, IEEE 802.15x, or some other type of network. The technologies described herein can also be used in any combination of WWAN, WLAN, and / or WPAN.

[0145] UE 105 may also include sensor 940. As described herein, 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 positioning-related measurements and / or other information.

[0146] Embodiments of UE 105 may also include a Global Navigation Satellite System (GNSS) receiver 980, which is capable of receiving signals 984 from one or more GNSS satellites using an antenna 982 (which may be identical to antenna 932). Positioning based on GNSS signal measurements may be used to supplement and / or incorporate the techniques described herein. The GNSS receiver 980 may extract the positioning of UE 105 from GNSS satellites 110 of GNSS systems such as the Global Positioning System (GPS), Galileo, GLONASS, Japan's Quasi-Zenith Satellite System (QZSS), India's IRNSS, China's BeiDou Navigation Satellite System (BDS), etc., using conventional techniques. Furthermore, the GNSS receiver 980 may be used with various augmentation systems (e.g., satellite-based augmentation systems (SBAS)), wherein the augmentation system may be associated with or used with one or more global and / or regional navigation satellite systems (e.g., Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), Multifunctional Satellite Augmentation System (MSAS), and Geographic Augmentation Navigation System (GAGAN), etc.).

[0147] It can be noted that although the GNSS receiver 980 is in Figure 9While shown as a separate component, embodiments are not so limited. As used herein, the term "GNSS receiver" can include hardware and / or software components configured to acquire GNSS measurements (measurements from GNSS satellites). Thus, in some embodiments, a GNSS receiver can include (as software) a measurement engine executed by one or more processors, such as processor 910, DSP 920, and / or a processor within a wireless communication interface 930 (e.g., in a modem). The GNSS receiver may also optionally include a positioning engine that can use GNSS measurements from the measurement engine to determine the GNSS receiver's location using an extended Kalman filter (EKF), weighted least squares (WLS), hatch filter, particle filter, etc. The positioning engine can also be executed by one or more processors, such as processor 910 or DSP 920.

[0148] UE 105 may also include and / or communicate with memory 960. 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 and flash-updateable), etc. Such storage devices can be configured to implement any suitable data storage, including but not limited to various file systems, database structures, etc.

[0149] As described herein, the memory 960 of UE 105 may also include software elements ( Figure 9 (Not shown), including operating systems, device drivers, executable libraries, and / or other code, such as one or more applications, which may include computer programs provided by various embodiments, and / or may be designed to implement methods provided by other embodiments and / or configure systems provided by other embodiments. By way of example only, one or more processes described with reference to the methods discussed above may be implemented as code and / or instructions in memory 960, which may be executed by UE 105 (and / or processor 910 or DSP 920 within UE 105). Thus, in some embodiments, such code and / or instructions may be used to configure and / or adjust a general-purpose computer (or other device) to perform one or more operations according to the described methods.

[0150] Figure 10 This is a block diagram of an embodiment of computer system 1000, wherein computer system 1000 may be used in whole or in part to provide the network entities described in the embodiments herein (e.g., Figure 1 Location server 160 Figure 2The functionality of one or more network components (including various components of 5G networks, such as NG-RAN 235, 5G CN 240, and / or similar components of other network types) of the LMF 220. Additionally or alternatively, Figure 10 One or more of the components shown can be utilized in the UE. It should be noted that... Figure 10 This is merely to provide a general description of the various components, any or all of which may be used as appropriate. Therefore, Figure 10 This roughly illustrates how the various system elements can be implemented in a relatively separate or relatively more integrated manner. Furthermore, it can be noted that... Figure 10 The components shown can be located in a single device and / or distributed among various networked devices that can be arranged in different physical or geographical locations. In some embodiments, the computer system 1000 may correspond to an LMF 220, gNB 210 (e.g., gNB 210-1), ng-eNB 214, WLAN 216, eNB, another cellular or non-cellular access node, E-SMLC, SUPLSLP, and / or some other type of locatable device.

[0151] Computer system 1000 is shown as including hardware elements electrically coupled (or otherwise suitably communicated) via bus 1005. The hardware elements may include processor 1010, which may include, but is not limited to, one or more general-purpose processors, one or more special-purpose processors (such as digital signal processing chips, graphics accelerators, etc.), and / or be configured to perform one or more methods described herein (including references to...). Figure 10 Other processing structures described in the method. The computer system 1000 may also include: one or more input devices 1015, which may include, but are not limited to, a mouse, keyboard, camera, microphone, etc.; and one or more output devices 1020, which may include, but are not limited to, display devices, printers, etc.

[0152] Computer system 1000 may also include one or more non-transitory storage devices 1025 (and / or communicate with them), which may include, but are not limited to, locally and / or network-accessible storage, and / or may include, but are not limited to, disk drives, drive arrays, optical storage devices, solid-state storage devices (such as RAM and / or ROM, which may be programmable and flash-updatable), etc. Such storage devices can be configured to implement any suitable data storage, including but not limited to various file systems, database structures, etc. As described herein, such data storage may include databases and / or other data structures for storing and managing messages and / or other information to be sent via a hub to one or more devices.

[0153] Computer system 1000 may further include a communication subsystem 1030, which may include wireless communication technologies managed and controlled by wireless communication interface 1033, as well as wired technologies (such as Ethernet, coaxial communication, Universal Serial Bus (USB), etc.). Wireless communication interface 1033 may include one or more wireless transceivers that can transmit and receive wireless signals 1055 (e.g., signals according to 5G NR or LTE) via wireless antenna 1050. Therefore, communication subsystem 1030 may include modems, network interface cards (wireless or wired), infrared communication devices, wireless communication devices, and / or chipsets, enabling computer system 1000 to communicate with any device on any or all of the communication networks described herein (including user equipment (UE), base stations and / or other TRPs, and / or any other electronic devices described herein). Therefore, communication subsystem 1030 can be used to receive and transmit data as described in the embodiments herein.

[0154] As described above, in many embodiments, the computer system 1000 will also include working memory 1035, which may include RAM or ROM devices. As described herein, software elements shown to be located within working memory 1035 may include operating system 1040, device drivers, executable libraries, and / or other code, such as one or more applications 1045, which may include computer programs provided by various embodiments and / or may be designed to implement methods provided by other embodiments and / or configure systems provided by other embodiments. By way of example only, one or more processes described with reference to the methods above may be implemented as code and / or instructions executable by a computer (and / or a processor within a computer); thus, in one aspect, such code and / or instructions may be used to configure and / or adjust a general-purpose computer (or other device) to perform one or more operations according to the described methods.

[0155] This set of instructions and / or code may be stored on a non-transitory computer-readable storage medium, such as storage device 1025 described above. In some cases, the storage medium may be incorporated into a computer system, such as computer system 1000. In other embodiments, the storage medium may be separate from the computer system (e.g., a removable medium such as an optical disc), and / or provided in an installation package, such that the storage medium can be used to program, configure, and / or tune a general-purpose computer using the instructions / code stored thereon. These instructions may take the form of executable code executable by computer system 1000, and / or may take the form of source code and / or installable code, which, after being compiled and / or installed on computer system 1000 (e.g., using any of a variety of generally available compilers, installers, compression / decompression tools, etc.), then take the form of executable code.

[0156] Figure 11 This can be shown as above (for example, see reference). Figures 1 to 9 This describes an embodiment of the base station 120 utilized in the description. It should be noted that... Figure 11 This is merely to provide a general description of the various components, any or all of which may be appropriately utilized. In some embodiments, base station 120 may correspond to a gNB, ng-eNB, and / or (more generally) TRP.

[0157] Base station 120 is shown to include hardware elements that can be electrically connected (or otherwise appropriately communicated) via bus 1105. The hardware elements may include processing unit 1110, which may include, but is not limited to, one or more general-purpose processors, one or more special-purpose processors (such as DSP chips, graphics accelerator processors, ASICs, etc.), and / or other processing architectures or devices. Figure 11 As shown, depending on the desired functionality, some embodiments may have a separate DSP 1120. According to some embodiments, location determination and / or other determinations based on wireless communication may be provided in the processor 1110 and / or the wireless communication interface 1130 (discussed below). The base station 120 may also include: one or more input devices, which may include, but are not limited to, a keyboard, display, mouse, microphone, buttons, dial, switch, etc.; and one or more output devices, which may include, but are not limited to, a display, light-emitting diodes (LEDs), speakers, etc.

[0158] Base station 120 may also include wireless communication interface 1130, which may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication devices and / or chipsets (such as... The device (such as IEEE 802.11 device, IEEE 802.15.4 device, Wi-Fi device, WiMAX device, cellular communication facility, etc.) enables base station 120 to communicate as described herein. Wireless communication interface 1130 allows data and signaling to be transmitted (e.g., sent and received) to UE, other base stations / TRPs (e.g., eNB, gNB, and ng-eNB) and / or other network components, computer systems, and / or any other electronic equipment described herein. Communication can be performed via one or more wireless communication antennas 1132 that transmit and / or receive wireless signals 1134.

[0159] Base station 120 may also include network interface 1180, which may include support for wired communication technologies. Network interface 1180 may include a modem, network interface card, chipset, etc. Network interface 1180 may include one or more input and / or output communication interfaces to allow data exchange with networks, communication network servers, computer systems, and / or any other electronic devices described herein.

[0160] In many embodiments, base station 120 may also include memory 1160. Memory 1160 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 RAM and / or ROM, which may be programmable and flash-updatable), etc. Such storage devices can be configured to implement any suitable data storage, including but not limited to various file systems, database structures, etc.

[0161] The memory 1160 of base station 120 may also include software elements ( Figure 11 (Not shown), including operating systems, device drivers, executable libraries, and / or other code, such as one or more applications, which may include computer programs provided by various embodiments, and / or may be designed to implement methods provided by other embodiments and / or configure systems provided by other embodiments. By way of example only, one or more processes described with reference to the methods discussed above can be implemented as code and / or instructions in memory 1160, which can be executed by base station 120 (and / or processing unit 1110 or DSP 1120 within base station 120). Thus, in one aspect, such code and / or instructions can be used to configure and / or adjust a general-purpose computer (or other device) to perform one or more operations according to the described methods.

[0162] It will be apparent to those skilled in the art that substantial modifications can be made to suit specific requirements. For example, custom hardware may be used, and / or specific elements may be implemented in hardware, software (including portable software such as applets), or both. Furthermore, connectivity with other computing devices (such as network input / output devices) may be employed.

[0163] Referring to the accompanying drawings, components that may include memory may include non-transitory machine-readable media. As used herein, the terms "machine-readable media" and "computer-readable media" 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 relate to providing instructions / code to a processing unit and / or other devices for execution. Additionally or alternatively, machine-readable media may be used to store and / or carry such instructions / code. In many embodiments, computer-readable media are physical and / or tangible storage media. Such media can take many forms, including but not limited to non-volatile media, volatile media, and transmission media. Common forms of computer-readable media include, for example, magnetic and / or optical media, any other physical media with a perforated pattern, RAM, programmable ROM (PROM), erasable PROM (EPROM), FLASH-EPROM, any other memory chip or cartridge, the carrier wave described below, or any other medium from which a computer can read instructions and / or code.

[0164] The methods, systems, and devices discussed herein are examples. Various embodiments may omit, substitute, or add various processes or components as appropriate. For example, features described with reference to a particular embodiment may be combined in various other embodiments. Different aspects and elements of embodiments may be combined in a similar manner. Various components of the accompanying drawings provided herein may be implemented in hardware and / or software. Furthermore, technology is constantly evolving, and therefore many elements are examples that do not limit the scope of this disclosure to these specific examples.

[0165] It has been found that, sometimes for convenience and primarily for common use, these signals are referred to as bits, information, values, elements, symbols, characters, variables, terms, numbers, or numerals. However, it should be understood that all of these or similar terms will be associated with appropriate physical quantities and are merely convenient labels. Unless otherwise specifically stated, it will become clear from the above discussion that throughout this specification, terms such as “processing,” “calculating,” “operating,” “determining,” “identifying,” “identifying,” “associating,” “measuring,” “executing,” etc., refer to the actions or processes of a particular device (such as a dedicated computer or similar dedicated electronic computing device). Therefore, in the context of this specification, a dedicated computer or similar dedicated electronic computing device is capable of manipulating or converting signals, which are generally referred to as physical electronic, electrical, or magnetic quantities within the memory, registers, or other information storage devices, transmitting devices, or display devices of the dedicated computer or similar dedicated electronic computing device.

[0166] The terms “and” and “or” as used herein can have a variety of meanings, which are expected to depend at least in part on the context in which they are used. Generally, “or” when used in a list of associations (such as A, B, or C) means A, B, and C (in the sense of inclusion) and A, B, or C (in the sense of exclusion). Furthermore, the term “one or more” as used herein can be used to describe any feature, structure, or characteristic of the singular, or can be used to describe some 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. Additionally, the term “at least one” when used in a list of associations (such as A, B, or C) can be interpreted as referring to any combination of A, B, and / or C, such as A, AB, AA, AAB, AABBCCC, etc.

[0167] Specific details are provided in the description to offer a comprehensive understanding of the example configurations, including implementations. However, the configurations can be practiced without these specific details. For example, well-known circuits, processes, algorithms, structures, and techniques have been shown without unnecessary detail to avoid obscuring the configurations. This description provides only example configurations and does not limit the scope, applicability, or configuration of the claims. Rather, the foregoing description of the configurations will provide those skilled in the art with an advantageous explanation of how to implement the described techniques. Various changes can be made to the function and arrangement of the elements without departing from the spirit or scope of this disclosure.

[0168] Furthermore, the configuration can be described as a process, depicted as a flowchart or block diagram. Although each process can be described as a sequential sequence of operations, many operations can be performed in parallel or concurrently. Moreover, the order of operations can be rearranged. A process may have additional steps not included in the accompanying drawings. Furthermore, the method example can be implemented using hardware, software, firmware, middleware, microcode, a hardware description language, or any combination thereof. When implemented using software, firmware, middleware, or microcode, the program code or code segments that perform the necessary tasks can be stored in a non-transitory computer-readable medium, such as a storage medium. The processor can execute the described tasks.

[0169] After describing several example configurations, various modifications, alternative structures, and equivalents may be used without departing from the spirit of this disclosure. For example, the foregoing elements may be components of a larger system, wherein other rules may take precedence over or otherwise modify the application of the invention. Furthermore, several steps may be taken before, during, or after considering the foregoing elements.

[0170] In view of this description, embodiments may include different combinations of features. Examples of implementations are described in the following numbered clauses:

[0171] Clause 1: A method for dynamically configuring one or more Quality of Service (QoS) parameters during a location session performed at a user equipment (UE), comprising: receiving a location request message from a network entity, wherein the location request message identifies one or more QoS parameters selectable for the location session; obtaining the selection of one or more QoS parameters for the location session; and sending a location response message to the network entity, wherein the location response message is generated at least in part based on the selected QoS parameters and indicates a configuration of the UE made according to the one or more selected QoS parameters.

[0172] Clause 2: The method described in Clause 1, wherein the positioning session includes an LTE Positioning Protocol (LPP) positioning session.

[0173] Clause 3: The method described in any one of Clauses 1 to 2, wherein the network entity includes a server or another UE.

[0174] Clause 4: The method according to any one of Clauses 1 to 3, wherein obtaining the selection of one or more QoS parameters comprises: using at least one of Downlink Control Information (DCI) and Media Access Control Command Element (MAC-CE) commands to determine one or more QoS parameters for the location session.

[0175] Clause 5: The method according to any one of Clauses 1 to 4, wherein one or more QoS parameters include one or more enumerated values ​​of at least one QoS parameter.

[0176] Clause 6: The method according to any one of Clauses 1 to 5, wherein obtaining the selection of one or more QoS parameters includes: receiving a selection from a server.

[0177] Clause 7: The method according to any one of Clauses 1 to 6 further includes: sending from the UE to the network entity a QoS parameter to be included in the selection of one or more QoS parameters of the location session before obtaining the selection of one or more QoS parameters of the location session.

[0178] Clause 8: The method according to any one of Clauses 1 to 7, wherein the location request message specifies layer-specific QoS parameters of one or more frequency layers of the Positioning Reference Signal (PRS).

[0179] Clause 9: The method according to any one of Clauses 1 to 8, wherein the location response message includes a QoS feedback parameter indicating the QoS achievable by the UE.

[0180] Clause 10: The method according to any one of Clauses 1 to 9, wherein at least one of one or more QoS parameters comprises: a horizontal accuracy parameter indicating the maximum horizontal error of the location estimate at an indicated confidence level; a vertical coordinate request indicating whether vertical coordinates are required as part of a location response message; a vertical accuracy parameter indicating the maximum vertical error of the location estimate at an indicated confidence level; a response time indicating the maximum time elapsed between receiving a location request message and sending a location response message; a response time early fixation parameter indicating the maximum time elapsed between receiving a location request message and sending a location response message containing early location measurements; or a speed request parameter indicating whether speed is requested; or a combination thereof.

[0181] Clause 11: A method for dynamically configuring one or more Quality of Service (QoS) parameters during a location session performed at a network entity, comprising: sending a location request message from the network entity to a user equipment (UE), wherein the location request message identifies one or more QoS parameters selectable for the location session; obtaining the selection of one or more QoS parameters for the location session; and receiving a location response message to the network entity, wherein the location response message is generated at least in part based on the selected QoS parameters and indicates a configuration of the UE made according to the one or more selected QoS parameters.

[0182] Clause 12: The method described in Clause 11, wherein the positioning session includes an LTE Positioning Protocol (LPP) positioning session.

[0183] Clause 13: The method according to any one of Clauses 11 to 12, wherein the network entity includes a server or another UE.

[0184] Clause 14: The method according to any one of Clauses 11 to 13, wherein obtaining the selection of one or more QoS parameters comprises: sending information indicating one or more QoS parameters of the location session via at least one of Downlink Control Information (DCI) and Media Access Control Command Element (MAC-CE) commands.

[0185] Clause 15: The method according to any one of Clauses 11 to 14, wherein one or more QoS parameters include one or more enumerated values ​​of at least one QoS parameter.

[0186] Clause 16: The method according to any one of Clauses 11 to 15, wherein obtaining the selection of one or more QoS parameters includes: selecting using network entities.

[0187] Clause 17: The method according to any one of Clauses 11 to 16 further includes: receiving, at the network entity, at the UE, at least one requested QoS parameter to be included in the selection of one or more QoS parameters before obtaining the selection of one or more QoS parameters for the location session.

[0188] Clause 18: The method according to any one of Clauses 11 to 17, wherein the location request message specifies layer-specific QoS parameters of one or more frequency layers of the Positioning Reference Signal (PRS).

[0189] Clause 19: The method according to any one of Clauses 11 to 18, wherein the location response message includes a QoS feedback parameter indicating the QoS achievable by the UE.

[0190] Clause 20: A method according to any one of Clauses 11 to 19, wherein at least one of one or more QoS parameters comprises: a horizontal accuracy parameter indicating the maximum horizontal error of the location estimate at an indicated confidence level; a vertical coordinate request indicating whether vertical coordinates are required as part of a location response message; a vertical accuracy parameter indicating the maximum vertical error of the location estimate at an indicated confidence level; a response time indicating the maximum time elapsed between receiving a location request message and sending a location response message; a response time early fixation parameter indicating the maximum time elapsed between receiving a location request message and sending a location response message containing early location measurements; or a speed request parameter indicating whether speed is requested; or a combination thereof.

[0191] Clause 21: A user equipment (UE) for dynamically configuring one or more Quality of Service (QoS) parameters during a location session, comprising: 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 perform a method according to any one of Clauses 1 to 10.

[0192] Clause 22: A network entity for dynamically configuring one or more Quality of Service (QoS) parameters during a location session, comprising: 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 perform a method according to any one of Clauses 11 to 20.

[0193] Clause 23: An apparatus for dynamically configuring one or more Quality of Service (QoS) parameters during a location session at a User Equipment (UE), comprising: means for performing the method according to any one of Clauses 1 to 20.

[0194] Clause 24: A non-transitory computer-readable medium storing instructions for dynamically configuring one or more Quality of Service (QoS) parameters during a location session, the instructions including code for performing the method according to any one of Clauses 1 to 20.

Claims

1. A method for dynamically configuring one or more Quality of Service (QoS) parameters during a location session performed at a User Equipment (UE), the method comprising: During a location session, a location request message is received from a network entity, wherein the location request message identifier can select one or more QoS parameters for the location session; During the same location session, the selection of one or more QoS parameters for the location session is obtained by receiving the selection of one or more QoS parameters for the location session from the network entity in a message other than the location request message; and During the same location session, a location response message is sent to the network entity, wherein the location response message includes: It is generated at least in part based on one or more selected QoS parameters, and Indicates the configuration of the UE, which is made based on one or more selected QoS parameters.

2. The method according to claim 1, wherein, The location session includes the LTE Location Protocol (LPP) location session.

3. The method according to claim 1, wherein, Network entities include servers or other UEs.

4. The method according to claim 1, wherein, The selection of one or more QoS parameters involves using at least one of the downlink control information (DCI) and the media access control command element (MAC-CE) to determine one or more QoS parameters for the location session.

5. The method according to claim 1, wherein, One or more QoS parameters include one or more enumerated values ​​of at least one QoS parameter.

6. The method according to claim 1, wherein, The selection of one or more QoS parameters includes receiving selections from the server.

7. The method of claim 1, further comprising, prior to obtaining the selection of one or more QoS parameters for the location session, sending from the UE to the network entity at least one requested QoS parameter to be included in the selection of one or more QoS parameters.

8. The method according to claim 1, wherein, The location request message specifies layer-specific QoS parameters for one or more frequency layers of the location reference signal (PRS).

9. The method according to claim 1, wherein, The location response message includes QoS feedback parameters that indicate the QoS achievable by the UE.

10. The method according to claim 1, wherein, At least one of one or more QoS parameters includes: The level accuracy parameter indicates the maximum level error of the position estimate at the indicated confidence level; Vertical coordinate request, which indicates whether vertical coordinates need to be included as part of the location response message; Vertical accuracy parameter, which indicates the maximum vertical error of the position estimate at the indicated confidence level; Response time, which indicates the maximum time elapsed between receiving a location request message and sending a location response message; The response time is an early fixed parameter that indicates the maximum time elapsed between receiving a location request message and sending a location response message containing early location measurements; or Speed ​​request parameters, where the speed request parameters indicate whether speed is requested; or Its combination.

11. A method for dynamically configuring one or more Quality of Service (QoS) parameters during a location session at a network entity, the method comprising: During a location session, a location request message is sent from a network entity to a user equipment (UE), wherein the location request message identifier can select one or more QoS parameters for the location session; During the same location session, the selection of one or more QoS parameters for the location session is obtained, and the selection of one or more QoS parameters for the location session is sent to the UE in a separate message other than the location request message; and During the same location session, the UE receives a location response message for a network entity, wherein the location response message includes: It is generated at least in part based on one or more selected QoS parameters, and Indicates the configuration of the UE, which is made based on one or more selected QoS parameters.

12. The method according to claim 11, wherein, The location session includes the LTE Location Protocol (LPP) location session.

13. The method according to claim 11, wherein, Network entities include servers or other UEs.

14. The method according to claim 11, wherein, The selection of one or more QoS parameters involves sending information indicating one or more QoS parameters for the location session via at least one of the downlink control information (DCI) and the media access control command element (MAC-CE) command.

15. The method according to claim 11, wherein, One or more QoS parameters include one or more enumerated values ​​of at least one QoS parameter.

16. The method according to claim 11, wherein, The selection of one or more QoS parameters includes selection using network entities.

17. The method of claim 11, further comprising receiving, at a network entity, at least one requested QoS parameter to be included in the selection of one or more QoS parameters before obtaining the selection of one or more QoS parameters for the location session.

18. The method according to claim 11, wherein, The location request message specifies layer-specific QoS parameters for one or more frequency layers of the location reference signal (PRS).

19. The method according to claim 11, wherein, The location response message includes QoS feedback parameters that indicate the QoS achievable by the UE.

20. The method according to claim 11, wherein, At least one of one or more QoS parameters includes: The level accuracy parameter indicates the maximum level error of the position estimate at the indicated confidence level; Vertical coordinate request, which indicates whether vertical coordinates need to be included as part of the location response message; Vertical accuracy parameter, which indicates the maximum vertical error of the position estimate at the indicated confidence level; Response time, which indicates the maximum time elapsed between receiving a location request message and sending a location response message; The response time is an early fixed parameter that indicates the maximum time elapsed between receiving a location request message and sending a location response message containing early location measurements; or Speed ​​request parameters, where the speed request parameters indicate whether speed is requested; or Its combination.

21. A user equipment (UE) for dynamically configuring one or more Quality of Service (QoS) parameters during a location session, comprising: At least one memory including instructions; and At least one processor is configured to execute the instructions to cause the UE to: During a location session, a location request message is received from a network entity, wherein the location request message identifier can select one or more QoS parameters for the location session; During the same location session, the selection of one or more QoS parameters for the location session is obtained by receiving the selection of one or more QoS parameters for the location session from the network entity in a message other than the location request message; and During the same location session, a location response message is sent to the network entity, wherein the location response message includes: It is generated at least in part based on one or more selected QoS parameters, and Indicates the configuration of the UE, which is made based on one or more selected QoS parameters.

22. The UE according to claim 21, wherein, The location session includes the LTE Location Protocol (LPP) location session.

23. The UE according to claim 21, wherein, Network entities include servers or other UEs.

24. The UE according to claim 21, wherein, The selection of one or more QoS parameters involves using at least one of the downlink control information (DCI) and the media access control command element (MAC-CE) to determine one or more QoS parameters for the location session.

25. The UE according to claim 21, wherein, One or more QoS parameters include one or more enumerated values ​​of at least one QoS parameter.

26. The UE according to claim 21, wherein, The at least one processor is further configured to enable the UE Before obtaining the selection of one or more QoS parameters for the location session, the UE sends at least one requested QoS parameter to the network entity to be included in the selection of one or more QoS parameters.

27. The UE according to claim 21, wherein, The at least one processor is further configured to enable the UE to include layer-specific QoS parameters of one or more frequency layers of the Location Reference Signal (PRS) in the location request message.

28. The UE according to claim 21, wherein, The location response message includes QoS feedback parameters that indicate the QoS achievable by the UE.

29. A network entity for dynamically configuring one or more Quality of Service (QoS) parameters during a location session, the network entity comprising: At least one memory including instructions; and At least one processor is configured to execute the instructions to cause the network entity to: During a location session, a location request message is sent from a network entity to a user equipment (UE), wherein the location request message identifier can select one or more QoS parameters for the location session; During the same location session, the selection of one or more QoS parameters for the location session is obtained, and the selection of one or more QoS parameters for the location session is sent to the UE in a separate message other than the location request message; and During the same location session, the UE receives a location response message for a network entity, wherein the location response message includes: It is generated at least in part based on one or more selected QoS parameters, and Indicates the configuration of the UE, which is made based on one or more selected QoS parameters.

30. The network entity according to claim 29, wherein, The location session includes the LTE Location Protocol (LPP) location session.

31. The network entity according to claim 29, wherein, Network entities include servers or other UEs.

32. The network entity according to claim 29, wherein, In order to obtain the selection of one or more QoS parameters, the at least one processor is configured to cause the network entity to send information indicating one or more QoS parameters of the location session via at least one of downlink control information (DCI) and media access control command element (MAC-CE) commands.

33. The network entity according to claim 29, wherein, One or more QoS parameters include one or more enumerated values ​​of at least one QoS parameter.

34. The network entity according to claim 29, wherein, The at least one processor is further configured to cause the network entity to receive from the UE at least one requested QoS parameter to be included in the selection of one or more QoS parameters before obtaining the selection of one or more QoS parameters for the location session.

35. The network entity according to claim 29, wherein, The location request message specifies layer-specific QoS parameters for one or more frequency layers of the location reference signal (PRS).

36. A computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 1 to 10.

37. A computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 11 to 20.

Images