Enhanced RAT dependent positioning

Abstract

Aspects of the present disclosure relate to an apparatus, a base station, a UE, a processor, a method, and a computer readable medium for performing LMF for enhanced radio access technology (RAT) dependent positioning. In one aspect, an LMF receives an update of available TRP information from a base station, determines a TRP-related error bound based on the update of the available TRP information, and sends the TRP-related error bound to a UE. In this way, integrity for RAT dependent positioning may be improved.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically, to apparatus, base station, user equipment (UE), processor, method, and computer-readable medium for performing location management functions (LMF) for enhanced radio access technology (RAT)-dependent positioning. Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Furthermore, the wireless communication system may support wireless communication across a variety of wireless access technologies, including third-generation (3G) wireless access technology, fourth-generation (4G) wireless access systems, fifth-generation (5G) wireless access technology, and other suitable wireless access technologies above 5G (e.g., sixth-generation (6G)).

[0003] Positioning integrity is defined as a measure of trust in the accuracy of location-related data provided by a positioning system, and the ability to provide timely and effective warnings to location service clients when the positioning system fails to meet the conditions for expected operation. The concept of positioning integrity was introduced and supported for Global Navigation Satellite System (GNSS) positioning in Rel-17, and the study of Radio Access Technology (RAT) dependent integrity in Rel-18 should focus as much as possible on the reuse of concepts and principles being developed for GNSS positioning integrity. Summary of the Invention

[0004] This disclosure relates to apparatus, base station, user equipment (UE), processor, method, and computer-readable medium for performing location management functions (LMF) for enhanced RAT-dependent positioning. Embodiments of this disclosure can improve the integrity of RAT-dependent positioning, including processes for ensuring the correctness of TRP-related error bounds and processes for enabling the LMF to know what has happened to the system when the UE fails to achieve requested key performance indicators (KPIs).

[0005] In some aspects, an apparatus for performing a location management function (LMF) is provided. The apparatus includes: at least one memory; and at least one processor coupled to the at least one memory and configured such that the apparatus: receives updates of available Transmit Receive Point (TRP) information from a base station; determines TRP-related error bounds based on the updates of the available TRP information; and transmits the TRP-related error bounds to a User Equipment (UE).

[0006] In some aspects, a base station is provided. The base station includes: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: acquire updates of available Transmit Receive Point (TRP) information; and transmit updates of available TRP information to a Location Management Function (LMF) via the transceiver.

[0007] In some aspects, a user equipment (UE) is provided. The UE includes: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver and from a location management function (LMF), a list of available transport receiving points (TRPs) information and TRP-related error boundaries; based on determining that the received list of TRP information differs from the list of TRP messages used for measurement, send, via the transceiver and to the LMF, a request for an update to the TRP-related error boundaries or a measurement failure message; and receive, via the transceiver and from the LMF, the updated TRP-related error boundaries.

[0008] In some aspects, a user equipment (UE) is provided. The UE includes: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive an error bound from a location management function (LMF); attempt to calculate a first protection level (PL) for a first target integrity risk (TIR) ​​associated with a key integrity performance indicator (KPI) based on the received error bound; based on the failure of calculating the first PL for the first TIR, attempt to calculate a second PL for a second TIR based on the received error bound, wherein the second TIL is different from the first TIR; and send the integrity result calculated based on the second PL to the LMF.

[0009] In some aspects, a processor for wireless communication is provided. The processor includes: at least one memory; and a controller coupled to the at least one memory and configured such that the controller: at a location management function (LMF), receives updates of available Transmit Receive Point (TRP) information from a base station; determines TRP-related error bounds based on the updates of the available TRP information; and transmits the TRP-related error bounds to a user equipment (UE) via a transceiver.

[0010] In some aspects, a processor for wireless communication is provided. The processor includes: at least one memory; and a controller coupled to the at least one memory and configured such that the controller: at a base station, acquires updates of available Transmitter Receiver Point (TRP) information; and sends updates of available TRP information to a Location Management Function (LMF).

[0011] In some aspects, a processor for wireless communication is provided. The processor includes: at least one memory; and a controller coupled to the at least one memory and configured such that the controller: receives, at a user equipment (UE) and from a location management function (LMF), a list of available Transmit Receiving Points (TRPs) information and TRP-related error boundaries; based on determining that the received list of TRP information differs from the list of TRP messages used for measurement, sends, via a transceiver and to the LMF, a request for an update to the TRP-related error boundaries or a measurement failure message; and receives, via the transceiver and from the LMF, the updated TRP-related error boundaries.

[0012] In some aspects, a processor for wireless communication is provided. The processor includes: at least one memory; and a controller coupled to the at least one memory and configured such that the controller: at a user equipment (UE), receives an error bound from a location management function (LMF); attempts to calculate a first protection level (PL) for a first target integrity risk (TIR) ​​associated with a first integrity key performance indicator (KPI) based on the received error bound; based on the determination that the calculation of the first PL for the first TIR fails, attempts to calculate a second PL for a second TIR based on the received error bound, wherein the second TIL is different from the first TIR; and transmits the integrity result calculated based on the second PL to the LMF.

[0013] In some aspects, a method for performing a location management function (LMF) is provided. The method includes: receiving an update of available transport receiving point (TRP) information from a base station; determining a TRP-related error bound based on the update of the available TRP information; and sending the TRP-related error bound to a user equipment (UE).

[0014] In some aspects, a method performed by a base station is provided. The method includes: obtaining an update of available Transmitter Receiver Point (TRP) information; and sending the update of available TRP information to a Location Management Function (LMF).

[0015] In some aspects, a method performed by a user equipment (UE) is provided. The method includes: receiving a list of available transport receiving points (TRPs) information and TRP-related error boundaries from a location management function (LMF); sending a request for an update to the TRP-related error boundaries or a measurement failure message to the LMF based on determining that the received list of TRP information differs from the list of TRP messages used for measurement; and receiving the updated TRP-related error boundaries from the LMF.

[0016] In some aspects, a method performed by a user equipment (UE) is provided. The method includes: receiving an error bound from a location management function (LMF); attempting to calculate a first protection level (PL) for a first target integrity risk (TIR) ​​associated with an integrity critical performance indicator (KPI) based on the received error bound; based on the failure to calculate the first PL for the first TIR, attempting to calculate a second PL for a second TIR based on the received error bound, wherein the second TIL is different from the first TIR; and sending the integrity result calculated based on the second PL to the LMF.

[0017] In some aspects, a computer-readable medium is provided that stores instructions that, when executed by a processor of a device, cause the device to perform the method according to any one of the ninth to twelfth aspects of this disclosure.

[0018] In some implementations of the methods and apparatus for performing LMF described herein, the apparatus may send a TRP information request to a base station before receiving an update of TRP information; receive a TRP information response from the base station including available TRP information; and derive an initial TRP-related error bound based on the available TRP information in the TRP information response from the base station.

[0019] In some implementations of the methods and apparatus for performing LMF described herein, updates to available TRP information are received based on periodic reports from the base station.

[0020] In some implementations of the methods and apparatus for performing LMF described herein, the apparatus may periodically send at least one request for available TRP information to a base station, and updates to available TRP messages are received via responses to at least one request.

[0021] In some implementations of the methods and apparatus for performing LMF described herein, the apparatus may receive a request for a TRP-related error bound from a UE; and based on the receipt of the request for the TRP-related error bound, send a request for available TRP information to a base station, wherein an update of the available TRP information is received via a response to the request for the available TRP information.

[0022] In some implementations of the methods and apparatus for performing LMF described herein, the apparatus may receive a request for a TRP-related error bound from a UE; and based on the receipt of the request for the TRP-related error bound, periodically send at least one request for available TRP information to a base station, wherein an update of the available TRP information is received via a response to at least one request.

[0023] In some implementations of the methods and apparatus for performing LMF described herein, the apparatus may send a modified or updated list of available TRP information to the UE.

[0024] In some implementations of the methods and apparatus for performing LMF described herein, the apparatus may receive from the UE one of the following: a request for an update to the TRP-related error bound, or a measurement failure message including a list of TRP information; and re-derive the TRP-related error bound based on the list of TRP information received from the UE.

[0025] In some implementations of the methods and apparatus for performing LMF described herein, the apparatus may receive a list of TRP information from the UE; and based on the TRP information from the UE, re-derive the TRP-related error bounds based on the TRP information, determining that the list of TRP information from the UE differs from the list of TRP messages received from the base station.

[0026] In some implementations of the methods and apparatus for performing LMF described herein, the apparatus may receive updates of available TRP information from a base station by: receiving a calculated integrity result and a list of TRP information from a UE; calculating the integrity result based on the list of TRP information from the UE; sending a request for available TRP information to the base station based on determining that the calculated integrity result is incorrect; and receiving available TRP information from the base station.

[0027] In some implementations of the methods and apparatus for performing LMF described herein, the apparatus may discard measurement data received from the UE; and request retransmission of measurement data from the UE.

[0028] In some implementations of the methods and apparatus for performing LMF described herein, updates to available TRP information can indicate the latest TRP information at the base station.

[0029] In some implementations of the methods and apparatus for performing LMF described herein, updating the available TRP information may include at least one of the following: a bit indicating whether there are changed available TRP messages; a changed list of TRP information; or an updated list of available TRP information.

[0030] In some implementations of the methods and apparatus for performing LMF described herein, the available TRP information includes at least one of the following: at least one TRP identifier (ID); geographic coordinates; or system frame number (SFN) initialization time.

[0031] In the methods and base station implementations described in this paper, the base station can obtain updates on available TRP information by periodically monitoring the TRP status.

[0032] In some implementations of the methods and base stations described in this paper, the base station can obtain updates to available TRP information by receiving at least one request from the LMF.

[0033] In some implementations of the methods and base stations described herein, at least one request for available TRP information can be received periodically.

[0034] In some implementations of the methods and base stations described herein, at least one request may be sent by the LMF in response to a request for an update of the TRP-related error bound from the UE.

[0035] In some implementations of the methods and base stations described in this paper, updates to available TRP information can indicate the latest TRP information at the base station.

[0036] In some implementations of the methods and base stations described herein, updating the available TRP information may include at least one of the following: bits indicating whether there are changed available TRP messages; a changed list of TRP information; or an updated list of available TRP information.

[0037] In some implementations of the methods and base stations described herein, the available TRP information may include at least one of the following: at least one TRP identifier (ID); geographic coordinates; or system frame number (SFN) initialization time.

[0038] In the methods described in this paper and in some implementations of the UE, the UE can send a list of TRP information used for measurement to the LMF.

[0039] In the methods described herein and some implementations of the UE, the UE can receive a request for retransmission of measurement data from the LMF; and perform retransmission of the measurement data to the LMF.

[0040] In the method described herein and some implementations of the UE, the UE can send an integrity result by: based on the determination that the calculation of the second PL for the second TIR is successful, sending an integrity result including the second PL and the second TIL.

[0041] In the methods described herein and some implementations of the UE, the UE may send an integrity result by sending an integrity result including an integrity flag indicating the availability of the positioning system for the UE, wherein the integrity flag is based on a comparison of a first PL or a second PL with an alarm limit (AL).

[0042] In the method described herein and some implementations of the UE, the UE may send an integrity-related error to the LMF based on the determination that the calculation of the second PL for the second TIR has failed. This integrity-related error indicates that the PL cannot be calculated based on the error boundary.

[0043] In the method described herein and some implementations of the UE, the UE may request an update to the error bound from the LMF based on the determination that the calculation of the second PL for the second TIR has failed, wherein, for the error bound, integrity-related errors result in the absence of PL calculation.

[0044] In the method described herein and some implementations of the UE, the UE may report to the LMF that the positioning system is unavailable or faulty based on the determination that the calculation of the second PL for the second TIR has failed, indicating the integrity-related error that caused the positioning system to be unavailable or faulty. Attached Figure Description

[0045] Figure 1 Examples of wireless communication systems in which some embodiments of the present disclosure may be implemented are illustrated.

[0046] Figure 2 The illustration shows an example of a processing flow in which available TRP information is updated according to some example embodiments of the present disclosure.

[0047] Figure 3 The illustration shows an example of a processing flow following a TRP information exchange process, where an update of available TRP information occurs, according to some example embodiments of the present disclosure.

[0048] Figure 4 The illustration shows an example of a processing flow during an auxiliary data transmission process, in which an update of available TRP information occurs, according to some example embodiments of the present disclosure.

[0049] Figure 5 The illustration shows an example of a processing flow during a location information transmission process, in which an update of available TRP information occurs, according to some example embodiments of the present disclosure.

[0050] Figure 6 The illustration shows an example of a processing flow for a scenario where the UE is unable to achieve the requested KPI, according to some example embodiments of the present disclosure.

[0051] Figure 7Examples of devices suitable for implementing some embodiments of the present disclosure are illustrated.

[0052] Figure 8 Examples of processors suitable for implementing some embodiments of the present disclosure are illustrated.

[0053] Figure 9 A flowchart illustrating a method performed by LMF according to various aspects of this disclosure is shown.

[0054] Figure 10 A flowchart illustrating a method performed by a base station according to various aspects of this disclosure is shown.

[0055] Figure 11 The diagram illustrates a flowchart of a method performed by a UE according to various aspects of this disclosure.

[0056] Figure 12 Another flowchart illustrating a method performed by a UE according to various aspects of this disclosure is shown.

[0057] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0058] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and are not intended to imply any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways besides those described below. In the following description and claims, unless otherwise defined, all technical and scientific terms used herein should be understood to have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0059] In this disclosure, references to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., indicate that the described embodiments(s) may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it should be understood that in conjunction with other embodiments (whether explicitly described or not) affecting such a feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0060] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms. In some examples, values, processes, or apparatus are referred to as “best,” “lowest,” “highest,” “minimum,” “maximum,” etc. It should be understood that this description is intended to indicate that a selection can be made from a number of functional alternatives used, and that such selection does not need to be better, smaller, higher, or more preferred than other options.

[0061] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well. It should also be understood that the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including,” as used herein, specify the presence of the stated features, elements, components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “comprising” and its variations should be understood as open terms that mean “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The use of terms such as “A and / or B” can mean “only A,” “only B,” or “both A and B.” Other explicit or implicit definitions may be included below.

[0062] In Rel-17, the concept of positioning integrity was introduced and supported for GNSS positioning, and the study of RAT-dependent integrity in Rel-18 should focus as much as possible on reusing the concepts and principles being developed for GNSS positioning integrity. However, unlike GNSS positioning integrity, RAT-dependent positioning technology involves entities including User Equipment (UE), Next-Generation Radio Access Network (NG-RAN) nodes (e.g., Transmitter Receiver Points (TRPs) and gNBs), and Location Management Functions (LMFs). Error sources or risk events generated by TRPs or measurements can also affect integrity performance to varying degrees. Since TRPs may not indicate their own error information to the LMF, the TRP-related error bound can be determined by deployment / implementation. Therefore, after the LMF receives auxiliary data from the gNB, the TRP-related error bound is determined by the LMF implementation. However, when one of the TRPs is damaged, malfunctioning, or blocked by buildings, the TRP-related error bound is inaccurate, and therefore, signaling procedures need to be designed to ensure the correctness of the TRP-related error bound.

[0063] Another issue is that the UE may fail to achieve the requested key performance indicators (KPIs), such as target integrity risk (TIR), because the UE cannot target... IRallocation The reasons for providing assurance regarding all possible options are as follows. Formula 8.1.1a-1 in TS38.305 (version 17) does indeed hold, or the UE can still calculate the Protection Level (PL), but only for a TIR worse than the initially requested TIR. In this case, there are two options: 1) the UE cannot simply calculate integrity, or 2) it can calculate integrity based on its best effort. Therefore, a process related to integrity result reporting needs to be designed to ensure the LMF knows what has happened.

[0064] In view of this, this disclosure focuses on the problem of improving the integrity of RAT-dependent positioning, including the process of ensuring the correctness of TRP-related error bounds, and the process of enabling LMF to know what happens to the system when the UE is unable to achieve the requested KPI.

[0065] According to embodiments of this disclosure, the LMF receives updates of available TRP information from a base station (e.g., a gNB). Based on these updates, the LMF determines TRP-related error bounds. The LMF then sends these TRP-related error bounds to the UE. This ensures the correctness of the TRP-related error bounds and improves the integrity of RAT-dependent positioning. In some embodiments, the UE can receive the error bounds from the LMF and attempt to calculate a first protection level (PL) for a first TIR associated with an integrity KPI based on the received error bounds. If the calculation for the first TIR fails, the UE can attempt to calculate a second PL for a second TIR different from the first TIR and then send the integrity result calculated based on the second PL to the LMF. This allows the LMF to know what happened to the system when the UE failed to achieve the requested KPI.

[0066] Various aspects of this disclosure are described in the context of wireless communication systems.

[0067] Figure 1 Examples of wireless communication systems 100 that may be implemented in some embodiments of this disclosure are illustrated. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various wireless access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-A network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable wireless access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support wireless access technologies beyond 5G. Additionally, the wireless communication system 100 may support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0068] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceivers, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UEs 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UEs 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface. In a 3GPP non-terrestrial network (NTN), a satellite-based network entity 102 may communicate directly with UEs 104 using an NR / LTE Uu interface. The satellite may be a transparent satellite or a regenerated satellite. For an NTN with transparent satellites, a base station on Earth may communicate with the UE via the satellite. For an NTN with regenerated satellites, the base station may be on-board and communicate directly with the UE.

[0069] Network entity 102 can provide a geographic coverage area 112 for which it can support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 can be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas 112 can be associated with different network entities 102. The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0070] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, etc. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0071] One or more UEs 104 can be devices in different forms or with different capabilities. Figure 1 The illustrations show some examples of UE 104. UE 104 can communicate with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay equipment, integrated access and backhaul (IAB) node, or another network device). Figure 1 As shown. Alternatively or additionally, UE 104 may support communication with other network entities 102 or UE 104, which may act as a relay in wireless communication system 100.

[0072] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, communication link 114 may be referred to as a side link. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0073] Network entity 102 may support communication with core network 106 or with another network entity 102, or both. For example, network entity 102 may be connected to core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs)). In some implementations, network entity 102 may include an entity for performing location management functions (LMFs).

[0074] In some implementations, network entity 102 may be configured in a decomposed architecture that can utilize protocol stacks physically or logically distributed across two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near-real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) system, or any combination thereof.

[0075] An RU can also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). In a decomposed RAN architecture, one or more components of network entity 102 can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0076] The functional division among CU, DU, and RU can be flexible and can support different functions based on the functions performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, a protocol stack functional division can be adopted between the CU and DU, allowing the CU to support one or more layers of the protocol stack, while the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer), and each of these can be at least partially controlled by the CU 160.

[0077] Alternatively or concurrently, a functional partitioning of the protocol stack can be employed between the DU and RU, allowing the DU to support one or more layers of the protocol stack, and the RU to support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional partitioning between the CU and DU, or between the DU and RU, can be within a protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer can be performed by the other of the CU, DU, or RU).

[0078] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via mid-range communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the mid-range or fronthaul communication links can be implemented based on the interfaces (e.g., channels) between layers of the protocol stack supported by the respective network entity 102 communicating via such communication links.

[0079] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include a server 117 for performing location management functions (LMF), control plane entities for managing access and mobility (e.g., mobility management entity (MME), access and mobility management functions (AMF)), and user plane entities for routing packets or interconnects to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106. LMF can be defined in core network 106 and / or network entity 102 to provide positioning functionality by determining the geographic location of UE 104 based on downlink and uplink location measurements of radio signals. Packet data network 108 may include application server 118.

[0080] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0081] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multi-frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more digital schemes.

[0082] The wireless communication system 100 may support one or more digital schemes, and the digital schemes may include subcarrier spacing and cyclic prefixes. A first digital scheme (e.g., =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and the regular cyclic prefix. In some implementations, the first digital scheme (e.g., ) associated with the first subcarrier spacing (e.g., 15 kHz) is... =0) can utilize one time slot per subframe. The second digital scheme (e.g., =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the regular cyclic prefix. The third digital scheme (e.g., =2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a regular cyclic prefix or an extended cyclic prefix. A fourth digital scheme (e.g., =3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the regular cyclic prefix. The fifth digital scheme (e.g., =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the regular cyclic prefix.

[0083] The time intervals of resources (e.g., communication resources) can be organized according to frames (also known as radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0084] Alternatively or concurrently, time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include multiple (e.g., several) time slots. The number of time slots in each subframe may also depend on one or more digital schemes supported in the wireless communication system 100. For example, a first digital scheme, a second digital scheme, a third digital scheme, a fourth digital scheme, and a fifth digital scheme (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. =0、 =1、 =2、 =3、 =4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used, respectively. Each time slot can include multiple (several) symbols (e.g., OFDM symbols). In some implementations, the number of time slots per subframe (e.g., quantity) can depend on the digital scheme. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the digital scheme. It should be understood that the first digital scheme (e.g., quantity) associated with the first subcarrier spacing (e.g., 15 kHz) is... The reference of =0 can be used interchangeably between subframes and time slots.

[0085] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR-4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, as well as other devices or multiple devices used for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other devices or multiple devices for short-range, high-data-rate capabilities.

[0086] FR1 can be associated with one or more number schemes (e.g., at least three number schemes). For example, FR1 can be associated with the following number scheme: a first number scheme (e.g., =0), which includes a 15 kHz subcarrier spacing; the second digital scheme (e.g., =1), which includes a 30 kHz subcarrier spacing; and a third digital scheme (e.g., =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more digital schemes (e.g., at least two digital schemes). For example, FR2 can be associated with the following digital scheme: a third digital scheme (e.g., =2), which includes a 60 kHz subcarrier spacing; and a fourth digital scheme (e.g., =3), which includes a subcarrier spacing of 120 kHz.

[0087] Figure 2 The illustration shows an example of a processing flow 200 in which available TRP information is updated according to some exemplary embodiments of the present disclosure. Processing flow 200 may involve UE 201, base station 202, and LMF 203. References Figure 1 The processing flow 200 can be applied to the wireless communication system 100. For example, UE 201 can be any one of the UEs 104. Base station 202 can be any one of the network entities 102. LMF 203 can be deployed at server 117 in the core network 106, or at any one of the network entities 102. It should be understood that the processing flow 200 can be applied to other communication scenarios, which will not be described in detail.

[0088] At 210, base station 202 sends an update of available TRP information 215 to LMF 203. Therefore, at 220, LMF 203 receives the update of available TRP information 215 from base station 202. In some embodiments, base station 202 may periodically monitor available TRP information and send available TRP information to LMF 203. Additionally or alternatively, base station 202 may, in response to receiving multiple TRP information requests from LMF 203, acquire available TRP information and send available TRP information to LMF 203. Multiple TRP information requests may be sent from LMF 203 periodically or by event triggering.

[0089] At 230, LMF 203 determines the TRP-related error bound based on updates to the available TRP information. In some embodiments, the TRP-related error bound may indicate the statistical distribution of the residual error associated with the positioning correction. The term "error" means the difference between the true value of a positioning parameter and its estimated and provided value in the corresponding auxiliary data. In some embodiments, the TRP-related error bound may be determined, or the TRP-related error bound may include the mean and standard deviation (stdDev) for that error.

[0090] At 240, LMF 230 sends TRP-related error bound 245 to UE 201. Therefore, at 250, UE 201 receives TRP-related error bound 245. Using the updated error bound 245, UE 201 can calculate the correct integrity result and determine whether the positioning system is timely and correctly available.

[0091] refer to Figure 2 The described process for updating available TRP information can occur in various environments. (Refer to...) Figures 3 to 5 Provide details.

[0092] Figure 3 The illustration shows an example of a processing flow following a TRP information exchange process, where an update of available TRP information occurs, according to some example embodiments of the present disclosure.

[0093] exist Figure 3 In step 1, base station 202 can receive a TRP information request from LMF 203, such as an NR Positioning Protocol A (NRPPa) TRP INFORMATION REUQEST message. This request may include an indication of which specific TRP configuration information is requested. In step 2, base station 202 can transmit a TRP information response to LMF 203, such as an NRPPa TRP INFORMATION RESPONSE message including available TRP information (e.g., a list of TRP information). In step 3, LMF 203 can derive an initial TRP-related error bound based on the available TRP information in the TRP information response.

[0094] according to Figure 3Option 1 allows base station 202 to periodically monitor and check the TRP status of those TRPs in the TRP information list in the NRPPa TRP INFORMATION RESPONSE message, including whether the TRP status is corrupted, blocked, inactive, or available. When base station 202 detects that the available TRP information is changing or has already changed, it can proactively update the list of available TRP information and send the list to LMF 203.

[0095] In step 4, base station 202 monitors for TRP issues, which can periodically alter the TRP information. These issues include whether some TRP information is corrupted or malfunctioning, whether some TRP information is blocked, or whether some TRP information is unavailable. Base station 202 periodically reports the TRP information to LMF 203. This step can occur before, after, or simultaneously with the LMF deriving the TRP-related error bounds.

[0096] At step 5, if the TRP information has not changed, base station 202 can indicate 1 bit to LMF 203 to indicate that there has been no change. When the TRP information has changed, for example, if the TRP ID, geographic coordinates (e.g., for TRP location), system frame number (SFN) initialization time, etc., the base station 202 can either report only the changed TRP information, or send an available TRP information update message to LMF 203 via a separate NRPPa message or NRPPa TRP INFORMATION RESPONSE message, where the message may include a list of updated / changed TRP information.

[0097] According to option 2, LMF 203 can periodically request updates to available TRP information. In this case, base station 202 can respond to the request during the last transmission period by sending the latest available TRP information, including the updated / changed list of TRP information, to LMF 203.

[0098] At step 6, LMF 203 can re-derive the TRP-related error bounds based on the received updated TRP information list. At step 7, LMF 203 can send the derived error bounds and the updated / modified TRP information list to UE 201 via LTE Positioning Protocol (LPP) Assistive Data Message.

[0099] Figure 4 The illustration shows an example of a processing flow during an auxiliary data transmission process, in which an update of available TRP information occurs, according to some example embodiments of the present disclosure.

[0100] When LMF 203 receives LPP request assistance data from UE 201 to request TRP-related error boundaries, LMF 203 can send an available TRP information update request to base station 202, and base station 202 responds to LMF 203 with a list of available TRP messages. For cases where LMF 203 determines TRP configuration information triggered by Operation, Administration and Maintenance (OAM) or periodic updates, a corresponding procedure is proposed, and details are as follows: Figure 4 As shown.

[0101] At step 1, LMF 203 sends an NRPPa TRP INFORMATION REQUEST message to base station 202. This request may include an indication of which specific TRP configuration information is requested. At step 2, LMF 203 receives TRP-related information from base station 202 in an NRPPa TRPINFORMATION RESPONSE message. At step 3, LMF 103 receives request assistance data from UE 201.

[0102] Option 1 can be applied when the LMF determines certain TRP configuration information required by the OAM trigger. After the LMF 203 receives the request assistance data from the UE, the LMF 203 can send an available TRP information update request to the base station 202 at step 4 using, for example, an NRPPa REQUEST message. At step 5, if the TRP information has not changed, the base station 202 can indicate to the LMF 203 with 1 bit indicating that no change has occurred. If some information has changed, incremental signaling can be reported, i.e., the base station 202 only reports the changed TRP information. Alternatively, the base station 202 can respond to the request by sending available TRP information, including a list of updated / changed TRP messages, to the LMF 203 via an NRPPa RESPONSE message.

[0103] Option 2 can be applied when the LMF determines that updating available TRP information is necessary as part of a periodic update. The LMF 203 sends an NRPPa TRP INFORMATION REQUEST message (#1) to the base station 202. This request may include an indication of which specific TRP configuration information is requested. If available at base station 202, the base station 202 may provide the requested TRP information in an NRPPa TRP INFORMATION RESPONSE message (#2 to #N). In the final transmission period, the base station 202 may respond to the request by sending the latest available TRP information, including an updated list of TRP information or a modified list of TRP messages, to the LMF 203 via NRPPa TRP INFORMATION RESPONSE.

[0104] At step 6, LMF 203 can re-derive the TRP-related error bounds based on the received updated / modified TRP information list. At step 7, LMF 203 can send the derived error bounds and the updated / modified TRP information list to UE 201 via LTE Positioning Protocol (LPP) Assistive Data Message.

[0105] Figure 5 The illustration shows an example of a processing flow during a location information transmission process, in which an update of available TRP information occurs, according to some example embodiments of the present disclosure.

[0106] When UE 201 receives the TRP information list by deriving the TRP-related error bound via auxiliary data messages provided by LPP, both UE 201 and LMF 203 can use PRS measurements to compare the received TRP information list with the actual TRP information list. Then, UE 201 sends an available TRP information update request to LMF 203. The corresponding procedure is designed, and the details are as follows: Figure 5 As shown.

[0107] In steps 1-1, 1-2, and 2, when LMF 203 receives TRP-related information from base station 202 in the NRPPa TRP INFORMATION RESPONSE message, LMF 203 can derive the TRP-related error bounds and store the values ​​of the error bounds.

[0108] In steps 3-1 and 3-2, when UE 201 sends a request for auxiliary data to LMF 203, LMF 203 sends a TRP-related error boundary to UE 201 via a Provide Auxiliary Data Information message or posSIB. In step 4, LMF 203 sends an LPP Request Location Information message to UE 201. This request may include indications of the requested measurement, including any required measurement configuration information and the required response time.

[0109] According to option 1, the UE compares the TRP information list and sends a TRP-related error boundary update request to the LMF. In step 5, after receiving the request location information message from LMF 203, UE 201 can perform a Position Reference Signal (PRS) measurement and generate a corresponding TRP information list. The UE can compare the TRP information list received in the LPP auxiliary data used to derive the TRP-related error boundary with the TRP message list used for PRS measurement.

[0110] At step 6, if the TRP list is different (i.e., the TRP information has changed), UE 201 may send an updated TRP-related error boundary request and / or measurement failure message to LMF 203. The request / measurement failure message may include a list of TRP information used for PRS measurement. At step 7, after receiving the updated TRP information list, LMF 23 can re-derive the TRP-related error boundary based on the received list of TRP messages used for PRS measurement.

[0111] According to option 2, the LMF compares the TRP information lists. At step 5, UE 201 sends an LPP Location Information Provided message to the LMF. At steps 6 and 7, the LMF 203 can compare the TRP information lists received in the Location Information Provided message (e.g., NR-DL-TDOA-SignalMeasurementInformation and NR-DL-AoD-SignalMeasurementInformation) with those received in the NRPPa TRP INFORMATION RESPONSE message. If a change exists, the LMF 203 can discard the received measurement data using the incorrect error bounds and re-derive the TRP-related error bounds based on the TRP information lists in the LPP Location Information Provided message.

[0112] According to option 3, the LMF requests TRP information from the base station after receiving / calculating the integrity result. In step 5a, LMF 203 receives the integrity result from the UE (UE-based integrity) via an LPP (Location Information Provided) message. In step 5b, LMF 202 calculates the integrity result itself (LMF-based integrity) and identifies problems with the calculated integrity result, such as TRP location-related error boundaries or TRP synchronization error boundaries in the Level of Protection (PL) calculation with large derivation deviations. In this case, in step 6a, LMF 203 sends a request to base station 202 to check available TRP information.

[0113] At step 6b, LMF 203 receives an available TRP information response from base station 202, including an updated / modified list of TRP information. At step 7, LMF 203 may re-derive the TRP-related error boundaries. At step 8, LMF 203 sends the updated TRP-related error boundaries to UE 201 via a separate LPP message or an LPP Provide Auxiliary Data message. Optionally, at step 9, LMF 203 may request UE 201 to re-provide measurement data in single-report mode.

[0114] Figure 6The illustration shows an example of a processing flow 600 for a scenario where a UE is unable to achieve a requested KPI, according to some example embodiments of the present disclosure. Processing flow 600 may involve UE 201 and LMF 203. Reference Figure 1 The processing flow 600 can be applied to the wireless communication system 100. For example, UE 201 can be any one of the UEs 104. LMF 203 can be deployed at server 117 in the core network 106, or at any one of the network entities 102. It should be understood that the processing flow 600 can be applied to other communication scenarios, which will not be described in detail.

[0115] At 610, LMF 203 sends error boundary 615 to UE 201. Therefore, at 620, UE 201 receives error boundary 615 from LMF 203.

[0116] At 630, UE 201 attempts to calculate the first protection level (PL) for the first target integrity risk (TIR) ​​associated with the integrity critical performance indicator (KPI) based on the received error bound. UE 201 can determine whether the calculation of the first PL is successful or unsuccessful. If the calculation of the first PL is successful, UE 201 can obtain the calculated first PL for the first TIR and send it to LMF 203.

[0117] At 640, based on the determination that the calculation of the first PL for the first TIR failed, UE 201 may attempt to calculate the second PL for the second TIR. The second TIR is different from the first TIR. For example, the second TIR may be greater than the first TIR. At 650, UE 201 sends integrity result 655 to LMF 203 based on the calculation of the second PL. Therefore, at 660, LMF 203 receives integrity result 655.

[0118] Target Integrity Risk (TIR) ​​is an important KPI for calculating the Protection Level (PL), and the target TIR provides the UE with the flexibility to return a PL for different TIRs. For example, the LMF requests the UE to calculate the PL for the first TIR, for example... Probability. The UE may be able to calculate PL only for the second higher TIR, for example, or This is known as an achievable TIR. If implemented KPIs are included, it enables flexibility for the UE to calculate the integrity output based on its best effort.

[0119] In some embodiments, if the calculation of the second TIR is successful, meaning that the second TIL is achievable, then UE201 can report the PL with the achievable TIR to the LMF via LPP as an integrity result. PL (e.g., horizontalProtectionLevel and verticalProtectionLevel ) and achievable TIR (e.g., achievableTargetIntegrityRisk It can be included in IE integrityInfo If missing achievableTargetIntegrityRisk Then the TIR and LPP request location information messages can be realized. targetIntegrityRisk same.

[0120] In some embodiments, UE 201 provides location information via LPP and reports an integrity event flag with a TIR achievable as an integrity result to LMF. The integrity event flag can indicate the availability of the positioning system for the UE. For example, UE 201 can determine the integrity flag based on a comparison of a calculated PL (first PL or second PL) with an alarm limit (AL). The integrity event flag (e.g., IntegrityEventFlaging ) and achievable TIR (e.g., achievableTargetIntegrityRisk It can be included in IE. integrityInfo middle.

[0121] UE 201 may report the cause of the error along with the integrity result to LMF 203. If UE 201 can calculate the PL based on the corresponding integrity auxiliary data, UE 201 should reply with the corresponding PL, and may also include an implementable TIR to LMF 203. However, if the UE cannot calculate the PL based on the integrity auxiliary data, or if the LMF can receive a flag / indication to indicate LPP... provide location information If the message does not provide the PL event, then an error cause report may be required so that the LMF can know why the system is unavailable or integrity has failed.

[0122] For some integrity-related errors, the UE cannot guarantee the accuracy of the results. IRallocation All possible choices in TS 38.305, Equation 8.1.1a-1, hold true. Therefore, the UE may not be able to calculate the corresponding PL for this error. In this case, the UE can use the following potential options to report the cause of the error and the integrity result to the LMF.

[0123] The UE can report an indication to the LMF. In some embodiments, UE 201 can send an integrity-related error to LMF 203, indicating that the PL cannot be calculated based on the error boundary. The UE can request the LMF to update the error boundary, where the error results in no PL calculation for that boundary. In this case, LMF 203 can determine whether the system is unavailable or faulty, or re-derive the error boundary of the error indicated by the UE and send that error boundary to the UE. In some embodiments, LMF 203 can update the error boundary, for example, by requesting an update of available TRP information and re-deriving the error boundary. UE 201 can then receive the updated error boundary from the LMF.

[0124] Alternatively or additionally, UE 201 may request LMF 203 to update or retransmit the error boundary via an LPP request auxiliary data message, for which integrity-related errors result in the absence of a PL calculation. Alternatively or additionally, UE 201 may report system unavailability or a failure to LMF 203, and may also indicate the integrity-related error that caused the system unavailability or failure. Subsequently, LMF 203 may trigger a restart of a new integrity procedure, or LMF may reselect a positioning method and send corresponding auxiliary data to the UE for the new integrity calculation.

[0125] According to the reference Figures 2 to 6 Some embodiments discussed present procedures to enable the correctness of TRP-related error bounds. Procedures related to integrity result reporting are proposed to enable the LMF to know what happened in the system. The LMF can know that the UE calculated integrity based on its best effort. The LMF can also know the cause of error for cases where PL / integrity event flags are missing from the integrity result report. This improves the integrity of RAT-dependent positioning.

[0126] Figure 7 Examples of devices suitable for implementing some embodiments of this disclosure are illustrated. Device 700 may be an example of an LMF as described herein. Device 700 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 700 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 702, memory 704, transceiver 706, and optionally, I / O controller 708). These components may communicate electronically or be otherwise coupled (e.g., operative ground, communicative ground, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0127] Processor 702, memory 704, transceiver 706, or various combinations thereof, or various components thereof, may be examples of components for performing aspects of the present disclosure described herein. For example, processor 702, memory 704, transceiver 706, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0128] In some implementations, processor 702, memory 704, transceiver 706, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described herein. In some implementations, processor 702 and memory 704 coupled to processor 702 may be configured to perform one or more of the functions described herein (e.g., instructions stored in memory 704 are executed by processor 702).

[0129] For example, according to the examples disclosed herein, processor 702 may support wireless communication at device 700. Device 700 may be implemented to perform LMF. Processor 702 may be configured to operate to support: components for receiving updates of available Transmitter Receive Point (TRP) information from a base station; components for determining TRP-related error bounds based on updates of available TRP information; and components for user equipment (UE) to transmit TRP-related error bounds.

[0130] Device 700 can be implemented at a base station. Processor 702 can be configured to operate to support: components for acquiring updates of available Transmitter Receiver Point (TRP) information, and components for sending updates of available TRP information to the Location Management Function (LMF).

[0131] Device 700 can be implemented at the UE. Processor 702 can be configured to support: components for receiving a list of available Transmit Receive Points (TRPs) information and TRP-related error boundaries from the Location Management Function (LMF); components for sending a request for an update to the TRP-related error boundaries or a measurement failure message to the LMF based on determining that the received list of TRP information differs from the list of TRP messages used for measurement; and components for receiving the updated TRP-related error boundaries from the LMF.

[0132] Device 700 can be implemented at the UE. Processor 702 can also be configured to support: components for receiving error bounds from the Location Management Function (LMF); components for attempting to calculate a first protection level (PL) for a first target integrity risk (TIR) ​​based on the received error bounds; components for attempting to calculate a second PL for a second TIR, wherein the second TIL is different from the first TIR, based on the failure of the calculation of the first PL; and components for sending the integrity result calculated based on the second PL to the LMF.

[0133] Processor 702 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 702 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 702. Processor 702 may be configured to execute computer-readable instructions stored in memory (e.g., memory 704) to cause device 700 to perform various functions of this disclosure.

[0134] Memory 704 may include random access memory (RAM) and read-only memory (ROM). Memory 704 may store computer-readable, computer-executable code, including instructions that, when executed by processor 702, cause device 700 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 702, but may cause a computer (e.g., at compile and execution time) to perform the functions described herein. In some implementations, memory 704 may, among other things, include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0135] I / O controller 708 can manage input and output signals for device 700. I / O controller 708 can also manage peripheral devices not integrated into device 700. In some implementations, I / O controller 708 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 708 can utilize an operating system such as iOS®, Android®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 708 can be implemented as part of a processor, such as processor 702. In some implementations, a user can interact with device 700 via I / O controller 708 or via hardware components controlled by I / O controller 708.

[0136] In some implementations, device 700 may include a single antenna 710. However, in other implementations, device 700 may have more than one antenna 710 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to transmit or receive multiple wireless transmissions simultaneously. Transceiver 706 may communicate bidirectionally via one or more antennas 710, wired or wireless links, as described herein. For example, transceiver 706 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 706 may also include a modem to modulate packets, provide modulated packets to one or more antennas 710 for transmission, and demodulate packets received from one or more antennas 710. Transceiver 706 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0137] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to a suitable power level for transmission over a wireless medium. The transmission chain may also include one or more antennas 710 for transmitting the amplified signal over the air or wireless medium.

[0138] The receiver chain can be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain may include one or more antennas 710 for receiving signals over the air or a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.

[0139] Figure 8 An example of a processor 800 suitable for implementing some embodiments of the present disclosure is illustrated. Processor 800 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 800 may include a controller 802 configured to perform various operations according to the examples described herein. Processor 800 may optionally include at least one memory 804. Additionally or alternatively, processor 800 may optionally include one or more arithmetic logic units (ALUs) 806. One or more of these components may be electronically communicated or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0140] Processor 800 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, transmit, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to the processor chipset (e.g., processor 800) or included in the processor chipset), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0141] Controller 802 can be configured to manage and coordinate various operations of processor 800 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 800 to support various operations according to the examples described herein. For example, controller 802 can operate as a control unit of processor 800, generating control signals that manage the operation of various components of processor 800. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operation timing.

[0142] Controller 802 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from memory 804 and determine subsequent instructions(s) to be executed, enabling processor 800 to support various operations according to the examples described herein. Controller 802 may be configured to track memory addresses of instructions associated with memory 804. Controller 802 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 802 may be configured to interpret instructions and determine control signals to be output to other components of processor 800, enabling processor 800 to support various operations according to the examples described herein. Additionally or alternatively, controller 802 may be configured to manage data flow within processor 800. Controller 802 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 800.

[0143] Memory 804 may include one or more caches (e.g., memory local to processor 800 or included in processor 800, or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, memory 804 may reside within or on the processor chipset (e.g., local to processor 800). In some other implementations, memory 804 may reside external to the processor chipset (e.g., remote from processor 800).

[0144] Memory 804 may store computer-readable, computer-executable code, including instructions that, when executed by processor 800, cause processor 800 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 802 and / or processor 800 may be configured to execute computer-readable instructions stored in memory 804 to cause processor 800 to perform various functions (e.g., functions or tasks supporting transmission power priority). For example, processor 800 and / or controller 802 may be coupled to or coupled to memory 804, and processor 800, controller 802, and memory 804 may be configured to perform the various functions described herein. In some examples, processor 800 may include multiple processors, and memory 804 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0145] One or more ALU 806s can be configured to support various operations according to the examples described herein. In some implementations, one or more ALU 806s may reside within or on a processor chipset (e.g., processor 800). In some other implementations, one or more ALU 806s may reside externally to a processor chipset (e.g., processor 800). One or more ALU 806s can perform one or more computations (such as addition, subtraction, multiplication, and division) on data. For example, one or more ALU 806s may receive input operands and an opcode that determines the operation to be performed. One or more ALU 806s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALU 806s may support logical operations (such as AND, OR, XOR, NOR, and NAND), thereby enabling one or more ALU 806s to handle conditional operations, comparisons, and bitwise operations.

[0146] Based on the examples disclosed herein, processor 800 can support wireless communication. Processor 800 can be implemented to perform LMF (Local Mode Function). Processor 800 can be configured or operable to support: components for receiving updates of available Transmitter Receive Point (TRP) information from a base station, components for determining TRP-related error bounds based on updates of available TRP information, and components for transmitting TRP-related error bounds to a User Equipment (UE).

[0147] The processor 800 can be implemented at the base station. The processor 800 can be configured or operable to support: components for acquiring updates of available Transmitter Receiver Point (TRP) information, and components for sending updates of available TRP information to the Location Management Function (LMF).

[0148] Processor 800 can be implemented at the UE. Processor 800 can be configured or operable to support: components for receiving a list of available Transmit Receive Points (TRPs) information and TRP-related error boundaries from the Location Management Function (LMF); components for sending a request for an update to the TRP-related error boundaries or a measurement failure message to the LMF based on determining that the received list of TRP information differs from the list of TRP messages used for measurement; and components for receiving the updated TRP-related error boundaries from the LMF.

[0149] Processor 800 may be implemented at the UE. Processor 800 may also be configured to support: components for receiving error bounds from the Location Management Function (LMF); components for attempting to calculate a first protection level (PL) for a first target integrity risk (TIR) ​​based on the received error bounds; components for attempting to calculate a second PL for a second TIR, wherein the second TIL is different from the first TIR, based on the failure to determine the first PL calculation; and components for sending the second PL and the second TIR to the LMF.

[0150] Figure 9 A flowchart illustrating method 900 performed by an LMF according to various aspects of this disclosure is shown. Operation of method 900 may be implemented by the device or components thereof described herein. For example, operation of method 900 may be performed by the LMF described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0151] At 910, the method may include receiving an update of available Transmit Receive Point (TRP) information from the base station. The operation of 910 can be performed according to the examples described herein. In some implementations, aspects of the operation of 910 may be performed by an LMF implemented in core network 106 or network entity 102, as referenced. Figure 1 As stated above.

[0152] At point 920, the method may include: determining a TRP-related error bound based on an update of available TRP information. The operation at 920 can be performed according to the examples described herein. In some implementations, aspects of the operation at 920 may be performed by an LMF implemented in core network 106 or network entity 102, as referenced. Figure 1 As stated above.

[0153] At 930, the method may include sending TRP-related error bounds to the user equipment (UE). The operation at 930 can be performed according to the examples described herein. In some implementations, aspects of the operation at 930 may be performed by an LMF implemented in core network 106 or network entity 102, as referenced. Figure 1 As stated above.

[0154] Figure 10 A flowchart illustrating a method 1000 performed by a base station according to various aspects of this disclosure is shown. Operation of method 1000 may be implemented by the device or components thereof described herein. For example, operation of method 1000 may be performed by the base station described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0155] At point 1010, the method may include: obtaining updates to available Transmitter Receiving Point (TRP) information. The operation at point 1010 can be performed according to the examples described herein. In some implementations, aspects of the operation at point 1010 can be found in the references. Figure 1 The network entity 102 is executed.

[0156] At point 1020, the method may include sending an update of available TRP information to the Location Management Function (LMF). The operation at point 1020 can be performed according to the examples described herein. In some implementations, aspects of the operation at point 1020 may be derived from references. Figure 1 The network entity 102 is executed.

[0157] Figure 11 A flowchart illustrating a method 1100 performed by a UE according to various aspects of this disclosure is shown. Operation of method 1100 may be implemented by the device or components thereof described herein. For example, operation of method 1100 may be performed by the UE described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0158] At 1110, the method may include: receiving a list of available Transmit Receiving Points (TRPs) and TRP-related error bounds from the Location Management Function (LMF). The operation of 1110 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1110 may be derived from references... Figure 1 The aforementioned UE 104 is executed.

[0159] At 1120, the method may include: sending a request for an update to the TRP-related error bound or a measurement failure message to the LMF based on determining that the received list of TRP messages differs from the list of TRP messages used for measurement. The operation at 1120 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1120 may be derived from references... Figure 1 The aforementioned UE 104 is executed.

[0160] At 1130, the method may include: receiving the updated TRP-related error bound from the LMF. The operation at 1130 can be performed according to the example described herein. In some implementations, aspects of the operation at 1130 may be derived from references. Figure 1 The aforementioned UE104 is executed.

[0161] Figure 12 A flowchart illustrating a method 1200 performed by a UE according to various aspects of this disclosure is shown. Operation of method 1200 may be implemented by the device or components thereof described herein. For example, operation of method 1200 may be performed by the UE described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0162] At 1210, the method may include receiving an error bound from the Location Management Function (LMF). The operation of 1210 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1210 may be derived from references. Figure 1 The aforementioned UE104 is executed.

[0163] At 1220, the method may include: attempting to calculate a first protection level (PL) for the first objective integrity risk (TIR) ​​based on the received error bound. The operation of 1220 can be performed according to the examples described herein. In some implementations, aspects of the operation of 1220 may be derived from references... Figure 1 The aforementioned UE 104 is executed.

[0164] At 1230, the method may include: based on the determination that the computation of the first PL has failed, attempting to compute a second PL for a second TIR, wherein the second TIR is different from the first TIR. The operation at 1230 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1230 may be derived from references... Figure 1 The aforementioned UE 104 is executed.

[0165] At 1240, the method may include: sending the integrity result calculated based on the second PL to the LMF. The operation at 1240 can be performed according to the examples described herein. In some implementations, aspects of the operation at 1240 may be derived from references. Figure 1 The aforementioned UE 104 is executed.

[0166] It should be noted that the methods described herein describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0167] The various illustrative boxes and components described herein can be implemented or executed by a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof, designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0168] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored in or transmitted via a computer-readable medium as one or more instructions or code on or through a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions may also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations.

[0169] Computer-readable media include both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, non-transitory computer-readable media can include: RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store required program code components in the form of instructions or data structures, and can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor.

[0170] As used herein, including in the claims, the article “a” preceding an element is unrestricted and is understood to refer to “at least one” element or “one or more” elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the use of “or” in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means: A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as referring to a closed set of conditions. For example, an example step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” may include one or more elements.

[0171] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for performing a location management function (LMF), the apparatus comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the device: Receive updates of available Transmission Receive Point (TRP) information from the base station; Based on the update of the available TRP information, determine the TRP-related error bound; as well as Send the TRP-related error bounds to the user equipment (UE).

2. The apparatus of claim 1, wherein the apparatus is further configured to: Before receiving the update of the TRP information, a TRP information request is sent to the base station; Receive a TRP information response from the base station, including the available TRP information; and Based on the available TRP information in the TRP information response from the base station, an initial TRP-related error bound is derived.

3. The apparatus of claim 2, wherein the update, which is available in TRP information, is received based on periodic reports from the base station.

4. The apparatus of claim 2, wherein the apparatus is further configured to: At least one request for the available TRP information is periodically sent to the base station, and the update of the available TRP message is received via a response to the at least one request.

5. The apparatus of claim 1, wherein the apparatus is further configured to: Receive a request from the UE for the TRP-related error bound; and Based on the receipt of the request regarding the TRP-related error bound, a request for the available TRP information is sent to the base station. And the update of the available TRP information is received via a response to the request for the available TRP information.

6. The apparatus of claim 1, wherein the apparatus is further configured to: Receive a request from the UE for the TRP-related error bound; and Based on the receipt of the request for the TRP-related error bound, at least one request for the available TRP information is periodically sent to the base station. And the update of the available TRP information is received via a response to the at least one request.

7. The apparatus of claim 1, wherein the apparatus is further configured to: Send the modified or updated list of available TRP information to the UE.

8. The apparatus of claim 1, wherein the apparatus is further configured to: The UE receives one of the following: a request for an update to the TRP-related error bound, or a measurement failure message including a TRP information list; and Based on the list of TRP information received from the UE, the TRP-related error bound is re-derived.

9. The apparatus of claim 1, wherein the apparatus is further configured to: Receive a list of TRP information from the UE; and Based on the determination that the TRP information list from the UE is different from the TRP message list received from the base station, the TRP-related error bound is re-derived based on the TRP information from the UE.

10. The apparatus of claim 1, wherein the apparatus is further configured to receive updates of available TRP information from the base station in the following manner: Receive the calculated integrity result and TRP information list from the UE; The integrity result is calculated based on the TRP information list from the UE; Based on the determination that the calculated integrity result is incorrect, a request for the available TRP information is sent to the base station; as well as Receive the available TRP information from the base station.

11. The apparatus of claim 1, wherein the update of the available TRP information indicates the latest TRP information at the base station.

12. The apparatus of claim 1, wherein the update of the available TRP information comprises at least one of the following: Indicates whether there are any changed bits in the available TRP information; The revised TRP information list; or Updated list of available TRP information.

13. The apparatus of claim 1, wherein the available TRP information includes at least one of the following: At least one TRP identifier (ID); Geographic coordinates; or System Frame Number (SFN) initialization time.

14. A base station, comprising: processor; as well as The transceiver is coupled to the processor. The processor is configured as follows: Get updates on available Transmit Receive Point (TRP) information; and The update of the available TRP information is sent to the Location Management Function (LMF) via the transceiver.

15. The base station of claim 14, wherein the processor is configured to obtain the update of the available TRP information by periodically monitoring the TRP status.

16. A user equipment (UE), comprising: processor; as well as The transceiver is coupled to the processor. The processor is configured as follows: The transceiver receives a list of available Transmit Receiving Points (TRPs) and TRP-related error bounds via the transceiver and from the Location Management Function (LMF). Based on the determination that the received TRP information list is different from the TRP message list used for measurement, a request for an update to the TRP-related error bound or a measurement failure message is sent via the transceiver to the LMF; and The updated TRP-related error bound is received via the transceiver and from the LMF.

17. A user equipment (UE), comprising: processor; as well as The transceiver is coupled to the processor. The processor is configured as follows: Receive error bounds from the Location Management Function (LMF); Based on the received error bound, attempt to calculate the first protection level (PL) for the first target integrity risk (TIR) ​​associated with the integrity key performance indicator (KPI). Based on the determination that the calculation of the first PL for the first TIR has failed, an attempt is made to calculate the second PL for the second TIR based on the received error bound, wherein the second TIL is different from the first TIR; as well as Send the integrity result calculated based on the second PL to the LMF.

18. The UE of claim 17, wherein the processor is configured to send the integrity result via: Based on the determination that the calculation of the second PL for the second TIR was successful, the integrity result including the second PL and the second TIL is sent.

19. The UE of claim 17 or 18, wherein the processor is configured to send the integrity result in the following manner: Send the integrity result including an integrity flag indicating the availability of the positioning system for the UE, wherein the integrity flag is based on a comparison of the first PL or the second PL with an alarm limit (AL).

20. The UE of claim 17, wherein the processor is further configured to: Based on the determination that the calculation of the second PL for the second TIR has failed, perform at least one of the following: Send an integrity-related error to the LMF, the integrity-related error indicating that PL cannot be calculated based on the error boundary; Request an update to the error bound from the LMF, where, Regarding the aforementioned error bound, integrity-related errors result in the absence of PL calculation; or The positioning system is reported to the LMF as unavailable or malfunctioning, indicating integrity-related errors that caused the positioning system to be unavailable or malfunctioning.

Images